8DG61259AAAATCZZA V1 Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 6.0 User Provisioning Guide

Title page
Alcatel-Lucent 1830
Photonic Service Switch (PSS) | Release 6.0.0
User Provisioning Guide
8DG-61259-AAAA-TCZZA
Issue 1 | June 2013
Legal notice
Legal notice
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2013 Alcatel-Lucent. All rights reserved.
Contents
About this document
xlvii
Purpose ........................................................................................................................................................................................ xlvii
Safety information ................................................................................................................................................................... xlvii
xlvii
Supported systems ................................................................................................................................................................... xlvii
xlvii
Conventions used
................................................................................................................................................................... xlviii
xlviii
Related information
Technical support
................................................................................................................................................................. xlix
xlix
........................................................................................................................................................................... li
li
How to comment ............................................................................................................................................................................ lili

1
Safety
Overview ...................................................................................................................................................................................... 1-1
1-1
General notes on safety
Overview ...................................................................................................................................................................................... 1-3
1-3
Structure of safety statements ............................................................................................................................................... 1-4
1-4
Basic safety aspects .................................................................................................................................................................. 1-7
1-7
Specific safety areas
Overview
................................................................................................................................................................................... 1-11
1-11
Potential sources of danger ................................................................................................................................................. 1-12

1-12
Laser safety ............................................................................................................................................................................... 1-13
1-13
Laser product classification ................................................................................................................................................ 1-20
1-20
Equipment grounding
........................................................................................................................................................... 1-25
1-25
Electrostatic discharge .......................................................................................................................................................... 1-26

1-26
Safety requirements in specific deployment phases
Overview
................................................................................................................................................................................... 1-34
1-34
....................................................................................................................................................................................................................................
1830 PSS
iii
8DG-61259-AAAA-TCZZA Release 6.0.0
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Transportation .......................................................................................................................................................................... 1-35

1-35
Storage ........................................................................................................................................................................................ 1-38
1-38
Installation ................................................................................................................................................................................. 1-42
1-42
Taking into operation
............................................................................................................................................................ 1-49
1-49
Operation and maintenance

Taking out of operation
................................................................................................................................................ 1-53
1-53
........................................................................................................................................................ 1-63
1-63
Event of failure ........................................................................................................................................................................ 1-66

1-66
2
Security administration procedures

Overview ...................................................................................................................................................................................... 2-1
2-1
Security management and user administration on the OCS application
Overview ...................................................................................................................................................................................... 2-5
2-5
User administration concept
................................................................................................................................................. 2-6
2-6
Security concepts
...................................................................................................................................................................... 2-7
2-7
User provisioning
................................................................................................................................................................... 2-13
2-13
Security management and user administration on the WDM application

Overview
................................................................................................................................................................................... 2-14
2-14
User accounts and privileges .............................................................................................................................................. 2-15

2-15
Configuring user accounts
Login sessions
......................................................................................................................................................................... 2-24
2-24
System security features

Authentication
.................................................................................................................................................. 2-20
2-20
...................................................................................................................................................... 2-26
2-26
......................................................................................................................................................................... 2-35
2-35
Administer user logins on the OCS application using the Alcatel-Lucent 1830 PSS ZIC
Overview
................................................................................................................................................................................... 2-40
2-40
Procedure 2-1: Create a user login ................................................................................................................................... 2-42

2-42
Procedure 2-2: Set system-wide user security parameters ...................................................................................... 2-45
2-45
Procedure 2-3: Display system-wide user security parameters ............................................................................. 2-49
2-49
....................................................................................................................................................................................................................................
1830 PSS
iv
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
System-wide user security parameters ............................................................................................................................ 2-50

2-50
Procedure 2-4: Delete a user login ................................................................................................................................... 2-52
2-52
Procedure 2-5: Inhibit a user login ................................................................................................................................... 2-53
2-53
Procedure 2-6: Allow a user login .................................................................................................................................... 2-54
2-54
Procedure 2-7: Display user property information ..................................................................................................... 2-55
2-55
Procedure 2-8: Edit user logins ......................................................................................................................................... 2-56
2-56
Procedure 2-9: Log off user ................................................................................................................................................ 2-59
2-59
Procedure 2-10: Retrieve information on all active user logins ............................................................................ 2-60
2-60
Procedure 2-11: Change password ................................................................................................................................... 2-61
2-61
Procedure 2-12: Send a short free form text message to other users ................................................................... 2-63
2-63
Procedure 2-13: Modify command access security level assigned to a TL1 command. .............................. 2-65
2-65
Procedure 2-14: Display command access security level assigned to a TL1 command
.............................. 2-67
2-67
Command access security level assigned to a TL1 command ............................................................................... 2-68

2-68
Procedure 2-15: Copy security sensible files or data from/to an NE to/from a remote file server ........... 2-69
2-69
Security File Transfer ........................................................................................................................................................ 2-73
2-73
Procedure 2-16: Configure SSL authentication for ZIC to NE communication (high-level

procedure) ........................................................................................................................................................................ 2-75
2-75
Procedure 2-17: Install a certificate for SSL authentication
.................................................................................. 2-76
2-76
Procedure 2-18: Generate a new SSL key for SSL authentication
...................................................................... 2-77
2-77
Procedure 2-19: Request a new certificate for SSL authentication
..................................................................... 2-79
2-79
Certificate for SSL authentication
................................................................................................................................... 2-80
2-80

Current NE Public Key.
...................................................................... 2-81
2-81
...................................................................................................................................................... 2-82
2-82
Procedure 2-21: Configure RADIUS server attributes

Procedure 2-22: Modify RADIUS server attributes
............................................................................................ 2-83
2-83
................................................................................................. 2-86
2-86
Procedure 2-23: Set RADIUS server authentication parameters

Procedure 2-24: Delete a RADIUS server
......................................................................... 2-88
2-88
................................................................................................................... 2-90
2-90
....................................................................................................................................................................................................................................
1830 PSS
v
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
User management and administration procedures on the WDM application using the WebUI
Overview
................................................................................................................................................................................... 2-91
2-91
Procedure 2-25: Create a user ............................................................................................................................................ 2-93

2-93
The Create User window
.................................................................................................................................................. 2-94
2-94
Procedure 2-26: View or modify user details ............................................................................................................... 2-97

2-97
The User Security Administration screen
.................................................................................................................. 2-98
2-98
Procedure 2-27: Delete a user ............................................................................................................................................ 2-99

2-99
Procedure 2-28: Change password
................................................................................................................................ 2-100
2-100
Procedure 2-29: View / terminate sessions ................................................................................................................. 2-101

2-101
The Sessions screen
........................................................................................................................................................... 2-102
2-102
Procedure 2-30: View SNMP v3 users ......................................................................................................................... 2-104

2-104
Procedure 2-31: Create SNMP v3 user ........................................................................................................................ 2-105
2-105
Procedure 2-32: Modify SNMP v3 user ...................................................................................................................... 2-106
2-106
The SNMP v3 Users screen
.............................................................................................................................................. 2-107
2-107
Procedure 2-33: View / modify system security attributes ................................................................................... 2-108

2-108
Procedure 2-34: Setting / viewing syslog properties
.............................................................................................. 2-109
2-109
Syslog Administration ........................................................................................................................................................ 2-110

2-110
Procedure 2-35: Setting / viewing CLI user activity logging properties
CLI Logging
......................................................... 2-111
2-111
.......................................................................................................................................................................... 2-112
2-112
Procedure 2-36: Setting / viewing SNMP user activity logging properties .................................................... 2-113
2-113
SNMP Logging
..................................................................................................................................................................... 2-114
2-114
Procedure 2-37: View security log ................................................................................................................................. 2-115

2-115
The Security Log screen
.................................................................................................................................................. 2-116
2-116
Procedure 2-38: View all logs

The All Logs screen
......................................................................................................................................... 2-117
2-117
............................................................................................................................................................ 2-118
2-118
Procedure 2-39: Save a retrieved log to a file ............................................................................................................ 2-119

2-119
Procedure 2-40: Set/view user preferences
................................................................................................................ 2-120
2-120
....................................................................................................................................................................................................................................
1830 PSS
vi
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
User Preferences ................................................................................................................................................................... 2-121

2-121
Procedure 2-41: Create RADIUS server
..................................................................................................................... 2-122
2-122
Create RADIUS Server ...................................................................................................................................................... 2-123

2-123
Procedure 2-42: View/modify RADIUS server ........................................................................................................ 2-124
2-124
Modify RADIUS Server .................................................................................................................................................... 2-125
2-125
Procedure 2-43: Delete RADIUS server
..................................................................................................................... 2-126
2-126
Procedure 2-44: Provision RADIUS properties
....................................................................................................... 2-127
2-127
RADIUS Properties ............................................................................................................................................................. 2-128

2-128
Procedure 2-45: Create trap destinations
.................................................................................................................... 2-129
2-129
The Create SNMP Trap Destinations screen

Procedure 2-46: Delete trap destinations
............................................................................................................ 2-130
2-130
.................................................................................................................... 2-131
2-131
Procedure 2-47: View trap destinations ....................................................................................................................... 2-132

2-132
The SNMP Trap Destinations screen
........................................................................................................................... 2-133
2-133
Procedure 2-48: View/modify community strings ................................................................................................... 2-135

2-135
The SNMP Community Strings screen
3
........................................................................................................................ 2-136
2-136
Data communication setup procedures

Overview ...................................................................................................................................................................................... 3-1
3-1
Data communication on the OCS application
Overview ...................................................................................................................................................................................... 3-4
3-4
Basic DCN principles .............................................................................................................................................................. 3-5
3-5
DCN configuration guidelines
............................................................................................................................................. 3-8
3-8
DCN protocols and services .................................................................................................................................................. 3-9

3-9
General Communication Channel .................................................................................................................................... 3-10
3-10
NE firewall with provisionable IP access control lists (IP ACL)
......................................................................... 3-11
3-11
Data communication on the WDM application

Overview
................................................................................................................................................................................... 3-12
3-12
....................................................................................................................................................................................................................................
1830 PSS
vii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
User interfaces ......................................................................................................................................................................... 3-13

3-13
Communications network
................................................................................................................................................... 3-18
3-18
Gateway NE (GNE) management .................................................................................................................................... 3-21

3-21
CIT port ...................................................................................................................................................................................... 3-24
3-24
OCS Setup procedures
Overview
................................................................................................................................................................................... 3-25
3-25
Procedure 3-1: Change the Site Identifier (SID) ......................................................................................................... 3-27

3-27
Procedure 3-2: Retrieve IP and MAC addresses ......................................................................................................... 3-29
3-29
View IP Addresses
................................................................................................................................................................ 3-30
3-30
Procedure 3-3: Set the FLC IP Addresses of the NE ................................................................................................. 3-31

3-31
Procedure 3-4: Set the loopback IP address of the NE ............................................................................................. 3-34
3-34
Procedure 3-5: Set the control plane IP addresses of the NE ................................................................................. 3-36
3-36
Procedure 3-6: Modify the TCP/IP stack parameters ................................................................................................ 3-38
3-38
Procedure 3-7: Create an access control rule
.............................................................................................................. 3-41
3-41
Procedure 3-8: Modify an existing access control rule
........................................................................................... 3-42
3-42
Procedure 3-9: Delete an internet protocol access rule
........................................................................................... 3-43
3-43
Procedure 3-10: Retrieve internet protocol access list
............................................................................................ 3-44
3-44
Internet Protocol Access Control Lists
.......................................................................................................................... 3-45
3-45
Procedure 3-11: Modify the ASAP of the Customer LAN interface ................................................................... 3-57
3-57
Procedure 3-12: Configure LAN interfaces to form a multi-shelf compound ................................................. 3-59
3-59
Procedure 3-13: Create a network interface on the embedded communication channels (ECCs)
Procedure 3-14: Modify the ASAP of a network interface
........... 3-63
3-63
..................................................................................... 3-66
3-66
Procedure 3-15: Add a GCC leg to an ECC protection group
............................................................................... 3-67
3-67
Procedure 3-16: Remove GCC legs from the ECC protection group
................................................................. 3-69
3-69
Procedure 3-17: Enable or disable a network interface ............................................................................................ 3-71

3-71
Procedure 3-18: Delete a network interface and an ECC protection group ...................................................... 3-73
3-73
Procedure 3-19: Create an IP-in-IP tunnel
.................................................................................................................... 3-75
3-75
....................................................................................................................................................................................................................................
1830 PSS
viii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Procedure 3-20: Set the alarm severity profile of an IP-in-IP tunnel

Procedure 3-21: Delete an IP-in-IP tunnel
.................................................................. 3-78
3-78
.................................................................................................................... 3-80
3-80
Procedure 3-22: Enter (add) a new static IP route in the IP routing table
......................................................... 3-81
3-81
Procedure 3-23: Delete a static IP route from the IP routing table ....................................................................... 3-85
3-85
Procedure 3-24: Create the NTP Server address ......................................................................................................... 3-87
3-87
Procedure 3-25: Manage the NTP server address ....................................................................................................... 3-89
3-89
Procedure 3-26: Retrieve the NTP sync state ............................................................................................................... 3-91
3-91
Procedure 3-27: Configure the global OSPF parameters ......................................................................................... 3-93
3-93
Procedure 3-28: Create an OSPF area
............................................................................................................................ 3-96
3-96
Procedure 3-29: Modify an OSPF area
.......................................................................................................................... 3-98
3-98
Procedure 3-30: Delete an OSPF area .......................................................................................................................... 3-100

3-100
Parameters of a OSPF Area .............................................................................................................................................. 3-101
3-101
Procedure 3-31: Configure the IP address range for the OSPF area ................................................................. 3-102
3-102
Procedure 3-32: Delete the IP address range of an OSPF area
........................................................................... 3-104
3-104
Procedure 3-33: Configure OSPF interface parameters ......................................................................................... 3-106

3-106
Procedure 3-34: Modify OSPF Authentication settings
........................................................................................ 3-109
3-109
WDM setup procedures

Overview
................................................................................................................................................................................. 3-111
3-111
Procedure 3-35: View network (NE name, NE IP, software release) map information
............................. 3-113
3-113
Network Map ......................................................................................................................................................................... 3-114

3-114
Procedure 3-36: View / modify IP route metric settings ........................................................................................ 3-115
3-115
IP Route Redistribute Metric Settings .......................................................................................................................... 3-116
3-116
Procedure 3-37: Create IP static route .......................................................................................................................... 3-117
3-117
Create Static IP Route ......................................................................................................................................................... 3-118
3-118
Procedure 3-38: View all IP routes ................................................................................................................................ 3-119
3-119
IP Routes ................................................................................................................................................................................. 3-120
3-120
Procedure 3-39: Delete IP static route .......................................................................................................................... 3-121
3-121
....................................................................................................................................................................................................................................
1830 PSS
ix
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Procedure 3-40: Create OSPF area ................................................................................................................................ 3-122

3-122
Create OSPF Area ................................................................................................................................................................ 3-123
3-123
Procedure 3-41: View OSPF areas
................................................................................................................................ 3-127
3-127
OSPF Areas ............................................................................................................................................................................ 3-128

3-128
Procedure 3-42: View/modify OSPF details .............................................................................................................. 3-132
3-132
OSPF Area Details ............................................................................................................................................................... 3-133
3-133
Procedure 3-43: Delete OSPF area ................................................................................................................................ 3-137
3-137
Procedure 3-44: Configure orderwire function ......................................................................................................... 3-138
3-138
Procedure 3-45: Create / view NTP server ................................................................................................................. 3-140
3-140
Create NTP Server ............................................................................................................................................................... 3-142
3-142
Procedure 3-46: View NTP properties
......................................................................................................................... 3-143
3-143
NTP Properties ...................................................................................................................................................................... 3-145

3-145
Procedure 3-47: Create/view NTP keys ....................................................................................................................... 3-146
3-146
Create NTP Key
................................................................................................................................................................... 3-147
3-147
Procedure 3-48: Set date and time manually
............................................................................................................. 3-148
3-148
Date and Time Administration ........................................................................................................................................ 3-149

3-149
4
Converged node set up procedures

Overview ...................................................................................................................................................................................... 4-1
4-1
Procedure 4-1: Connect OCS application to WDM application .............................................................................. 4-2
4-2
Equipment provisioning procedures

Overview ...................................................................................................................................................................................... 5-1
5-1
OCS equipment provisioning
Overview ...................................................................................................................................................................................... 5-5
5-5
Different kinds of equipment provisioning
..................................................................................................................... 5-6
5-6
Summary of important configuration rules ................................................................................................................... 5-15

5-15
....................................................................................................................................................................................................................................
1830 PSS
x
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
WDM equipment provisioning

Overview
................................................................................................................................................................................... 5-18
5-18
WDM equipment management specifics ....................................................................................................................... 5-19

5-19
OCS Provisioning Procedures
Overview
................................................................................................................................................................................... 5-43
5-43
Procedure 5-1: Define general properties of the system .......................................................................................... 5-44

5-44
Procedure 5-2: Create an extension shelf
...................................................................................................................... 5-46
5-46
Procedure 5-3: Remove an extension shelf ................................................................................................................... 5-50

5-50
Procedure 5-4: Provision or pre-provision I/O cards
............................................................................................... 5-53
5-53
Procedure 5-5: Provision or pre-provision optical modules

Procedure 5-6: Set a board/module out of service
.................................................................................. 5-57
5-57
..................................................................................................... 5-61
5-61
Procedure 5-7: Deprovision equipment .......................................................................................................................... 5-64

5-64
Procedure 5-8: Perform a matrix card upgrade
........................................................................................................... 5-66
5-66
Procedure 5-9: Configure an optical interface port .................................................................................................... 5-70

5-70
Procedure 5-10: Configure Optical Channel parameters ......................................................................................... 5-72
5-72
Procedure 5-11: Perform remote laser shutdown on OTH network ports
Procedure 5-12: Create an ODUn path termination
......................................................... 5-74
5-74
.................................................................................................. 5-76
5-76
Procedure 5-13: Configure an ODU path termination .............................................................................................. 5-84

5-84
Procedure 5-14: Changing the payload type of an ODU path termination
...................................................... 5-89
5-89
Procedure 5-15: Changing the sub-structure of an ODU path termination
...................................................... 5-92
5-92
Procedure 5-16: Deprovision an ODUk path termination function ..................................................................... 5-95

5-95
Procedure 5-17: Provision an optical SDH/SONET port
Procedure 5-18: Provision an GBE/GBE10
........................................................................................ 5-97
5-97
................................................................................................................. 5-99
5-99
Procedure 5-19: Provision a Tandem Connection Monitoring (TCM) entity
............................................... 5-101
5-101
Procedure 5-20: Remove a facility ................................................................................................................................ 5-107

5-107
Procedure 5-21: Restore a facility
................................................................................................................................. 5-109
5-109
Procedure 5-22: Allow equipment protection switching
....................................................................................... 5-111
5-111
....................................................................................................................................................................................................................................
1830 PSS
xi
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Procedure 5-23: Inhibit equipment protection switching ...................................................................................... 5-113

5-113
Procedure 5-24: Initiate an equipment protection switch manually .................................................................. 5-115
5-115
Procedure 5-25: Initiate a circuit pack reset ............................................................................................................... 5-117
5-117
WDM Provisioning Procedures
Overview ................................................................................................................................................................................. 5-123
5-123
Procedure 5-26: View or modify NE parameters ..................................................................................................... 5-125
5-125
System Properties
................................................................................................................................................................ 5-126
5-126
Procedure 5-27: Reboot NE ............................................................................................................................................. 5-129

5-129
Reboot Options ..................................................................................................................................................................... 5-130
5-130
Procedure 5-28: Configure the firmware
.................................................................................................................... 5-131
5-131
Firmware ................................................................................................................................................................................. 5-134

5-134
Procedure 5-29: View the firmware
.............................................................................................................................. 5-135
5-135
Firmware ................................................................................................................................................................................. 5-136

5-136
Shelf provisioning ................................................................................................................................................................ 5-137
5-137
Procedure 5-30: Create (pre-provision) a shelf ......................................................................................................... 5-142
5-142
Create Shelf ............................................................................................................................................................................ 5-143
5-143
Procedure 5-31: View/modify shelf properties
Shelf Properties
......................................................................................................... 5-146
5-146
................................................................................................................................................................... 5-147
5-147
Procedure 5-32: Delete a shelf ........................................................................................................................................ 5-151

5-151
Procedure 5-33: Test LEDs
.............................................................................................................................................. 5-152
5-152
Shelf LEDs ............................................................................................................................................................................. 5-153

5-153
OT slot/card provisioning
................................................................................................................................................. 5-154
5-154
Procedure 5-34: Create a card ......................................................................................................................................... 5-175

5-175
Provision Card
...................................................................................................................................................................... 5-176
5-176
Procedure 5-35: View / modify card properties ........................................................................................................ 5-177

5-177
Procedure 5-36: View card inventory ........................................................................................................................... 5-178
5-178
Card Inventory
...................................................................................................................................................................... 5-179
5-179
....................................................................................................................................................................................................................................
1830 PSS
xii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Procedure 5-37: View pluggable module inventory ................................................................................................ 5-180

5-180
Pluggable Module Inventory
........................................................................................................................................... 5-181
5-181
Procedure 5-38: Controller Protection Switch (EC/MTC1T9)
........................................................................... 5-182
5-182
Controller Protection Switch Settings .......................................................................................................................... 5-184

5-184
Procedure 5-39: Upgrade EC (in-service upgrade from simplex to duplex) .................................................. 5-185
5-185
Procedure 5-40: Reboot card
........................................................................................................................................... 5-186
5-186
Reboot Options [Card] ....................................................................................................................................................... 5-187

5-187
Procedure 5-41: Delete a card ......................................................................................................................................... 5-188
5-188
Delete Card ............................................................................................................................................................................. 5-189
5-189
Port/facility provisioning
.................................................................................................................................................. 5-190
5-190
Procedure 5-42: Port provisioning procedures .......................................................................................................... 5-402

5-402
Information retrieval on the OCS application
Overview ................................................................................................................................................................................. 5-446
5-446
Procedure 5-43: Retrieve general properties of the system .................................................................................. 5-447
5-447
Procedure 5-44: Retrieve current conditions for a system component ............................................................. 5-448
5-448
View Current Conditions ................................................................................................................................................... 5-449
5-449
Procedure 5-45: Retrieve remote inventory for a system component
Retrieve remote inventory
.............................................................. 5-451
5-451
................................................................................................................................................ 5-453
5-453
Procedure 5-46: Retrieve network element TL1 parameters
............................................................................... 5-456
5-456
Procedure 5-47: Retrieve information related to equipment protection groups ............................................ 5-457
5-457
Procedure 5-48: Retrieve and edit optical channel parameters ........................................................................... 5-459
5-459
Procedure 5-49: Diagnose equipment
.......................................................................................................................... 5-460
5-460
Procedure 5-50: Perform LED test ................................................................................................................................ 5-462

5-462
Procedure 5-51: Check shelf cabling
........................................................................................................................... 5-463
5-463
Procedure 5-52: Retrieval analog optical parameters from optical modules
................................................. 5-465
5-465
Parameter descriptions (OCS application)

Overview ................................................................................................................................................................................. 5-469
5-469
....................................................................................................................................................................................................................................
1830 PSS
xiii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
General properties of the system as a whole .............................................................................................................. 5-470

5-470
General properties of a shelf ............................................................................................................................................ 5-480
5-480
General properties of a TRU ............................................................................................................................................ 5-482
5-482
General properties of an I/O card ................................................................................................................................... 5-483
5-483
General properties of an optical SDH/SONET port ................................................................................................ 5-484
5-484
General properties of an OTU port facility
General properties of an optical module
................................................................................................................ 5-489
5-489
..................................................................................................................... 5-497
5-497
General properties of a GBE / GBE10 port ................................................................................................................ 5-501

5-501
General properties of an ODU path termination facilty ......................................................................................... 5-509
5-509
Properties of a Tandem Connection Monitoring (TCM) entity
General properties of an optical
......................................................................... 5-520
5-520
.................................................................................................................................... 5-531
5-531
Parameters of equipment protection groups ............................................................................................................... 5-539

5-539
Primary and secondary states of system components ............................................................................................. 5-541
5-541
Overview of access identifiers
........................................................................................................................................ 5-548
5-548
TL1 parameters ..................................................................................................................................................................... 5-579

5-579
6
11QPE24 L2 Features
Overview ...................................................................................................................................................................................... 6-1
6-1
11QPE24 Quality of Service (QOS) .................................................................................................................................. 6-3
6-3
11QPE24 QOS CLI commands ........................................................................................................................................... 6-5
6-5
11QPE24 Ethernet Ring Protection .................................................................................................................................... 6-9
6-9
11QPE24 ERP CLI commands .......................................................................................................................................... 6-14
6-14
11QPE24 Ethernet OAM ..................................................................................................................................................... 6-15
6-15
11QPE24 Ethernet OAM CLI commands ..................................................................................................................... 6-27
6-27
11QPE24 Port Mirroring
..................................................................................................................................................... 6-29
6-29
11QPE24 Port Mirroring CLI commands
..................................................................................................................... 6-32
6-32
11QPE24 Services .................................................................................................................................................................. 6-33

6-33
11QPE24 Services CLI commands .................................................................................................................................. 6-40
6-40
....................................................................................................................................................................................................................................
1830 PSS
xiv
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
11QPE24 Link Aggregation Group (LAG) ................................................................................................................... 6-44

6-44
11QPE24 LAG CLI commands
........................................................................................................................................ 6-47
6-47
11QPE24 MC-LAG CLI commands ............................................................................................................................... 6-48

6-48
11QPE24 PMON CLI commands
.................................................................................................................................... 6-49
6-49
11QPE24 Remote Managed Device CLI commands ................................................................................................ 6-51

6-51
11QPE24 Port CLI commands
.......................................................................................................................................... 6-53
6-53
11QPE24 Clear CLI commands ........................................................................................................................................ 6-55

6-55
11QPE24 Tools CLI commands ........................................................................................................................................ 6-56
6-56
11QPE24 General CLI commands ................................................................................................................................... 6-57
6-57
Procedure 6-1: Configure Ethernet-Ring (one node)
7
................................................................................................ 6-58
6-58
Alarm management procedures

Overview ...................................................................................................................................................................................... 7-1
7-1
OCS alarm management procedures
Procedure 7-1: View NE alarms .......................................................................................................................................... 7-3
7-3
View Current Alarms And Conditions
............................................................................................................................. 7-5
7-5
Procedure 7-2: Create an Alarm Severity Assignment Profile (ASAP) ................................................................ 7-7
7-7
Procedure 7-3: Display Alarm Assignment Profiles .................................................................................................. 7-10
7-10
Procedure 7-4: Display Alarm Assignment Profiles assigned to specific entities
Procedure 7-5: Manage ASAP profile
............................................................................................................................ 7-12
7-12
Procedure 7-6: Manage ASAP profile assigned to a specific entity

Procedure 7-7: Edit notification code
Procedure 7-8: Delete ASAP profile
.......................................... 7-11
7-11
.................................................................... 7-14
7-14
............................................................................................................................. 7-16
7-16
............................................................................................................................... 7-18
7-18
WDM alarm management procedures

Introduction
.............................................................................................................................................................................. 7-19
7-19
Procedure 7-9: Display active alarm list ........................................................................................................................ 7-23

7-23
Alarm List
................................................................................................................................................................................. 7-24
7-24
....................................................................................................................................................................................................................................
1830 PSS
xv
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Procedure 7-10: View condition list
............................................................................................................................... 7-25
7-25
Procedure 7-11: Display active alarms or alarm level on a shelf or slot/card .................................................. 7-26
7-26
Procedure 7-12: View alarms history log
...................................................................................................................... 7-27
7-27
Alarms Log ............................................................................................................................................................................... 7-28

7-28
Procedure 7-13: View events history log ....................................................................................................................... 7-29
7-29
General Events Log
............................................................................................................................................................... 7-30
7-30
Procedure 7-14: Modify alarm configuration
.............................................................................................................. 7-31
7-31
Alarmable Conditions ........................................................................................................................................................... 7-32

7-32
Procedure 7-15: Provision environmental (housekeeping) alarms ....................................................................... 7-35
7-35
Environmental Alarms .......................................................................................................................................................... 7-36
7-36
8
TDM timing provisioning procedures

Overview ...................................................................................................................................................................................... 8-1
8-1
Procedure 8-1: Configure the timing references
.......................................................................................................... 8-3
8-3
General properties of a timing node within a shelf
..................................................................................................... 8-5
8-5
Procedure 8-2: Configure external timing input ports

General properties of external timing input ports
............................................................................................... 8-8
8-8
..................................................................................................... 8-12
8-12
Procedure 8-3: Configure external timing references
.............................................................................................. 8-15
8-15
General properties of a external timing reference
..................................................................................................... 8-18
8-18
Procedure 8-4: Perform a timing reference switch
................................................................................................... 8-22
8-22
Procedure 8-5: Switch external timing reference

Procedure 8-6: Clear a timing reference switch
...................................................................................................... 8-24
8-24
......................................................................................................... 8-27
8-27
Procedure 8-7: Take an external timing reference out of service for maintenance purposes
Procedure 8-8: Take an external timing input port out (BITS) out-of-service
Procedure 8-9: Restore timing reference
.................... 8-30
8-30
................................................ 8-32
8-32
...................................................................................................................... 8-34
8-34
Procedure 8-10: Retrieve the current timing configuration
................................................................................... 8-36
8-36
Procedure 8-11: Retrieve provisioning and state information of external timing references
.................... 8-38
8-38
Procedure 8-12: Retrieve provisioning and state information of external timing input ports
................... 8-39
8-39
....................................................................................................................................................................................................................................
1830 PSS
xvi
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Synchronization characteristics -External timing inputs

Synchronization characteristics Timing references
9
........................................................................................ 8-41
8-41
............................................................................................... 8-43
8-43
TDM network configuration procedures

Overview ...................................................................................................................................................................................... 9-1
9-1
Introduction
Create Cross Connections window ..................................................................................................................................... 9-3
9-3
Manage Cross Connections window .................................................................................................................................. 9-6
9-6
Provisioning procedures
Procedure 9-1: Add a protection leg to a cross-connection ..................................................................................... 9-10
9-10
Procedure 9-2: Remove a protection leg from a cross-connection
...................................................................... 9-16
9-16
Procedure 9-3: Create an SNCP protection group ...................................................................................................... 9-20

9-20
Procedure 9-4: Modify an SNCP protection group .................................................................................................... 9-27
9-27
Procedure 9-5: Delete an SNC protection group
........................................................................................................ 9-30
9-30
Procedure 9-6: Initiate an SNC protection switch ...................................................................................................... 9-32

9-32
Procedure 9-7: Release an SNC protection switch
.................................................................................................... 9-34
9-34
Procedure 9-8: Retrieve configuration parameters and status information of an SNC protection
group ................................................................................................................................................................................... 9-36
9-36
10
WDM network configuration procedures

Overview
................................................................................................................................................................................... 10-1
10-1
Introduction
Protection
.................................................................................................................................................................................. 10-4
10-4
Procedure 10-1: Create protection group
.................................................................................................................... 10-16
10-16
Create APS Group
............................................................................................................................................................... 10-17
10-17
Create APS Group
............................................................................................................................................................... 10-19
10-19
Procedure 10-2: View all protection groups ............................................................................................................... 10-22

10-22
....................................................................................................................................................................................................................................
1830 PSS
xvii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Automatic Protection Switch Groups ........................................................................................................................... 10-23

10-23
Procedure 10-3: View/modify protection group ....................................................................................................... 10-26
10-26
Procedure 10-4: Delete protection group
.................................................................................................................... 10-27
10-27
Procedure 10-5: Request protection switch ................................................................................................................ 10-28

10-28
Procedure 10-6: Configure OMSP protection
........................................................................................................... 10-29
10-29
Procedure 10-7: Configure E-SNCP protection ........................................................................................................ 10-34

10-34
Procedure 10-8: Configure OPS client side protection .......................................................................................... 10-36
10-36
Procedure 10-9: Configure OLP protection
Wavelength Tracker
............................................................................................................... 10-40
10-40
............................................................................................................................................................ 10-50
10-50
Procedure 10-10: Provision wave keys on an encoder port to support dangling OT procedure ............. 10-55
10-55
Wave Key Encoder .............................................................................................................................................................. 10-57
10-57
Procedure 10-11: Set expected network output power ........................................................................................... 10-58
10-58
Procedure 10-12: View wave keys (decoder ports) ................................................................................................. 10-59
10-59
Wave Key Decoder .............................................................................................................................................................. 10-60
10-60
Procedure 10-13: Clear wave keys ................................................................................................................................ 10-62
10-62
Procedure 10-14: Set power ............................................................................................................................................. 10-63
10-63
Set Power ................................................................................................................................................................................ 10-64
10-64
Procedure 10-15: View channel power summary
.................................................................................................... 10-65
10-65
Wavelength Tracker Power Summary .......................................................................................................................... 10-66

10-66
Procedure 10-16: View unexpected wave keys ......................................................................................................... 10-67
10-67
Unexpected Wave Keys ..................................................................................................................................................... 10-68
10-68
Procedure 10-17: View wave key data at NE level
................................................................................................. 10-69
10-69
Wave Keys .............................................................................................................................................................................. 10-70

10-70
Procedure 10-18: View unexpected/missing wave keys at NE level
................................................................ 10-72
10-72
Unexpected Wave Keys ..................................................................................................................................................... 10-73

10-73
Missing Wave Keys ............................................................................................................................................................. 10-74
10-74
Procedure 10-19: Provision optical line's monitoring (WT mode or WTOCM mode) .............................. 10-75
10-75
....................................................................................................................................................................................................................................
1830 PSS
xviii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Port Power Management ................................................................................................................................................... 10-76

10-76
Procedure 10-20: Add a service to a FOADM system or mixed FOADM-TOADM system .................. 10-78
10-78
Procedure 10-21: Add an Anydirection Add/Drop block to ROADM
Power settings
............................................................. 10-83
10-83
....................................................................................................................................................................... 10-86
10-86
Procedure 10-22: Power management .......................................................................................................................... 10-89

10-89
Port Power Management ................................................................................................................................................... 10-90
10-90
Procedure 10-23: Power adjustment ............................................................................................................................. 10-92
10-92
Power Adjustment
.............................................................................................................................................................. 10-94
10-94
Procedure 10-24: View/modify power commissioning values ............................................................................ 10-96

10-96
Power Commissioning
...................................................................................................................................................... 10-97
10-97
A2P2125 Power Commissioning
............................................................................................................................... 10-109
10-109
Procedure 10-25: LD power adjustment

Power Adjustment
................................................................................................................... 10-114
10-114
............................................................................................................................................................. 10-115
10-115
Procedure 10-26: GMRE settings ................................................................................................................................ 10-116

10-116
Procedure 10-27: GMRE Feasibility File Transfer
............................................................................................... 10-117
10-117
Procedure 10-28: GMRE OMS line parameters ..................................................................................................... 10-118

10-118
Procedure 10-29: GMRE optical impairment parameters
.................................................................................. 10-119
10-119
Procedure 10-30: Cross-phase modulation allowed wavelength set

11
.............................................................. 10-120
10-120
TDM traffic provisioning procedures

Overview
................................................................................................................................................................................... 11-1
11-1
Introduction
Cross-connection types ......................................................................................................................................................... 11-2
11-2
Different ways to create a cross-connection ................................................................................................................. 11-7
11-7
Different ways to modify a cross-connection ............................................................................................................... 11-8
11-8
Overview
................................................................................................................................................................................... 11-9
11-9
....................................................................................................................................................................................................................................
1830 PSS
xix
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Procedure 11-1: Create a cross-connection
................................................................................................................ 11-10
11-10
Procedure 11-2: Modify a cross-connection

Procedure 11-3: Delete a cross-connection
.............................................................................................................. 11-15
11-15
................................................................................................................ 11-18
11-18
Procedure 11-4: Retrieve a list of cross-connections .............................................................................................. 11-21

11-21
12
WDM traffic provisioning procedures

Overview
................................................................................................................................................................................... 12-1
12-1
Description ................................................................................................................................................................................ 12-3

12-3
Procedure 12-1: Display NE physical topology .......................................................................................................... 12-8
12-8
Physical Topology .................................................................................................................................................................. 12-9
12-9
Procedure 12-2: Display NE logical topology
.......................................................................................................... 12-10
12-10
Procedure 12-3: Provision OCH cross-connects

OCH Cross-Connects
...................................................................................................... 12-11
12-11
......................................................................................................................................................... 12-13
12-13
Create OCH Cross-Connect ............................................................................................................................................. 12-15

12-15
Procedure 12-4: Create OCH cross-connect group
Procedure 12-5: Provision ODUk cross-connects
ODUk Cross-Connects
................................................................................................. 12-17
12-17
................................................................................................... 12-19
12-19
...................................................................................................................................................... 12-20
12-20
Create ODUk Cross-Connect
.......................................................................................................................................... 12-21
12-21
Procedure 12-6: Provision EVPL connections .......................................................................................................... 12-22

12-22
Create EVPL Connection (FullRate)
............................................................................................................................ 12-23
12-23
Create EVPL Connection (SubRate) ............................................................................................................................. 12-24

12-24
Create EVPL Connection (QinQ)
.................................................................................................................................. 12-26
12-26
Procedure 12-7: Display the cross connect topology .............................................................................................. 12-28

12-28
Cross Connect Topology
................................................................................................................................................... 12-29
12-29
Procedure 12-8: Display the NE power trace
............................................................................................................ 12-30
12-30
Cross-Connect Power Trace ............................................................................................................................................. 12-31

12-31
Procedure 12-9: Display network power trace .......................................................................................................... 12-32
12-32
Network Power Trace ......................................................................................................................................................... 12-33
12-33
....................................................................................................................................................................................................................................
1830 PSS
xx
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Procedure 12-10: Connect Alcatel-Lucent 1830 PSS-1 to 1830 PSS-32/PSS-16/PSS-32S ..................... 12-34
12-34
13
TDM traffic maintenance procedures

Overview
................................................................................................................................................................................... 13-1
13-1
Procedure 13-1: Configure port loopback ..................................................................................................................... 13-2

13-2
Procedure 13-2: Release Loopback
................................................................................................................................. 13-7
13-7
Procedure 13-3: View loopback ........................................................................................................................................ 13-9

13-9
View Loopback ..................................................................................................................................................................... 13-10
13-10
14
WDM traffic maintenance procedures

Overview
................................................................................................................................................................................... 14-1
14-1
Loopbacks ................................................................................................................................................................................. 14-2

14-2
Procedure 14-1: Display, set, release loopbacks ......................................................................................................... 14-4
14-4
Port Loopback Control ......................................................................................................................................................... 14-6
14-6
15
TDM Ethernet/Data traffic maintenance procedures

Overview
................................................................................................................................................................................... 15-1
15-1
Procedure 15-1: Configure port loopback ..................................................................................................................... 15-2

15-2
Procedure 15-2: Release loopback ................................................................................................................................... 15-5
15-5
Procedure 15-3: View loopback ........................................................................................................................................ 15-7
15-7
The View Loopback window
16
............................................................................................................................................ 15-8
15-8
Performance monitoring procedures

Overview
................................................................................................................................................................................... 16-1
16-1
OCS performance monitoring

Overview
................................................................................................................................................................................... 16-3
16-3
The performance monitoring process
............................................................................................................................. 16-6
16-6
Performance measurements ................................................................................................................................................ 16-8

16-8
SES declaration threshold ................................................................................................................................................. 16-15
16-15
Thresholding .......................................................................................................................................................................... 16-17
16-17
....................................................................................................................................................................................................................................
1830 PSS
xxi
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Impact of configuration changes on performance monitoring
............................................................................ 16-25
16-25
WDM performance monitoring

WDM performance monitoring ...................................................................................................................................... 16-27
16-27
OCS performance monitoring procedures
Overview ................................................................................................................................................................................. 16-38
16-38
Procedure 16-1: Enable or disable PM data collection .......................................................................................... 16-39
16-39
Procedure 16-2: Retrieve PM activation status ......................................................................................................... 16-43
16-43
Procedure 16-3: Retrieve PM data ................................................................................................................................. 16-47
16-47
Procedure 16-4: Initialize PM registers
....................................................................................................................... 16-52
16-52
Procedure 16-5: Upload the NE PM data to a remote file server

Procedure 16-6: Create a new TCA profile
Procedure 16-7: Rename a TCA profile
...................................................................... 16-55
16-55
............................................................................................................... 16-58
16-58
..................................................................................................................... 16-61
16-61
Procedure 16-8: Modify the threshold settings of a TCA profile ....................................................................... 16-63
16-63
Procedure 16-9: Retrieve the threshold settings of a TCA profile ..................................................................... 16-65
16-65
Procedure 16-10: Delete a TCA profile ....................................................................................................................... 16-66
16-66
Procedure 16-11: Retrieve a list of facilities that use a particular TCA profile
............................................ 16-67
16-67
WDM performance monitoring procedures

Overview ................................................................................................................................................................................. 16-68
16-68
Procedure 16-12: Display PM data for EC/MTC1T9 card ................................................................................... 16-69
16-69
PM Data [Card]
.................................................................................................................................................................... 16-70
16-70
Procedure 16-13: Set bins for EC/MTC1T9 card
.................................................................................................... 16-72
16-72
Clear Bins [Card] ................................................................................................................................................................. 16-73

16-73
Procedure 16-14: Display all TCA profile assignments
TCA Profile Assignment
........................................................................................ 16-74
16-74
................................................................................................................................................... 16-75
16-75
Procedure 16-15: Modify TCA profile ......................................................................................................................... 16-76

16-76
Procedure 16-16: Display PM data for port
............................................................................................................... 16-77
16-77
....................................................................................................................................................................................................................................
1830 PSS
xxii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
PM Data ................................................................................................................................................................................... 16-78

16-78
Procedure 16-17: Set bins for port ................................................................................................................................. 16-80
16-80
Clear Bins
............................................................................................................................................................................... 16-81
16-81
Procedure 16-18: Set baseline values for port ........................................................................................................... 16-82

16-82
Port Baseline .......................................................................................................................................................................... 16-84
16-84
OCS Performance monitoring reports
Overview ................................................................................................................................................................................. 16-86
16-86
Configuration parameters related to performance monitoring ............................................................................ 16-87
16-87
PM reports General .......................................................................................................................................................... 16-89
16-89
PM reports SDH Regenerator Section ...................................................................................................................... 16-92
16-92
PM reports SDH higher order path
PM reports SONET Section
PM reports SONET path
PM reports Ethernet
........................................................................................................................... 16-93
16-93
......................................................................................................................................... 16-94
16-94
.............................................................................................................................................. 16-95
16-95
........................................................................................................................................................ 16-96
16-96
PM reports OTUk Section
............................................................................................................................................ 16-97
16-97
PM reports ODUk Path .................................................................................................................................................. 16-98

16-98
PM reports ODUk TCM Layer
................................................................................................................................... 16-99
16-99
PM reports OCH section near end PM parameters

17
........................................................................................... 16-100
16-100
Database backup and restore procedures

Overview
................................................................................................................................................................................... 17-1
17-1
Backup and restore on the OCS application

Overview
................................................................................................................................................................................... 17-3
17-3
Configuration backup and restoration ............................................................................................................................. 17-4

17-4
Backup and restore principle .............................................................................................................................................. 17-5
17-5
Backup and restore on the WDM application
Overview
................................................................................................................................................................................... 17-6
17-6
....................................................................................................................................................................................................................................
1830 PSS
xxiii
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Database management .......................................................................................................................................................... 17-7

17-7
Database backup ................................................................................................................................................................... 17-12
17-12
Database restore
................................................................................................................................................................... 17-14
17-14
OCS backup and restore procedures

Overview ................................................................................................................................................................................. 17-16
17-16
Procedure 17-1: Backup the active database to the standby database .............................................................. 17-17
17-17
Procedure 17-2: Transfer the NE standby database to a remote file server .................................................... 17-18
17-18
Procedure 17-3: Retrieve information related to transferred files on a remote file server ........................ 17-22
17-22
Information related to database backups stored on a remote file server. ......................................................... 17-24
17-24
Procedure 17-4: Download a database from a remote file server to the standby database ....................... 17-27
17-27
Procedure 17-5: Restore database .................................................................................................................................. 17-30
17-30
WDM backup and restore procedures using WebUI
Overview ................................................................................................................................................................................. 17-32
17-32
Procedure 17-6: Backup database .................................................................................................................................. 17-33
17-33
Database Backup and Restore ......................................................................................................................................... 17-34
17-34
Procedure 17-7: Restore database .................................................................................................................................. 17-36
17-36
18
Software installation and upgrade procedures

Overview
................................................................................................................................................................................... 18-1
18-1
OCS software installation and upgrade procedures

....................................................................................................................................................................................................... 18-2
18-2
Procedure 18-1: Upgrade to a new release of the NE software ............................................................................. 18-3

18-3
Procedure 18-2: Download a software generic from a remote file server to the standby software
load ...................................................................................................................................................................................... 18-9
18-9
Procedure 18-3: Software download for disaster recovery
................................................................................. 18-14
18-14
Procedure 18-4: Switch from the current release to the new release ................................................................ 18-18
18-18
Procedure 18-5: Switch back from the current release and database to previous release
......................... 18-20
18-20
Procedure 18-6: Make the current release software the permanent active software ................................... 18-22
18-22
....................................................................................................................................................................................................................................
1830 PSS
xxiv
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
WDM software installation and upgrade procedures

.................................................................................................................................................................................................... 18-24
18-24
Procedure 18-7: Software upgrade procedure ........................................................................................................... 18-25

18-25
FTP Server Settings ............................................................................................................................................................. 18-27
18-27
Software Upgrade ................................................................................................................................................................ 18-28
18-28
Procedure 18-8: Modify/view software NE attributes procedure
19
...................................................................... 18-31
18-31
Routine procedures
Overview
................................................................................................................................................................................... 19-1
19-1
Maintaining OCS parts of the system.

Overview
................................................................................................................................................................................... 19-2
19-2
Procedure 19-1: Replace the dust filter .......................................................................................................................... 19-3

19-3
Procedure 19-2: Replace a Fan Unit (FAN3T8) .......................................................................................................... 19-6
19-6
Procedure 19-3: Common card mounting rules ........................................................................................................ 19-10
19-10
20
Supporting procedures
Overview
................................................................................................................................................................................... 20-1
20-1
The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC)

....................................................................................................................................................................................................... 20-3
20-3
General information
.............................................................................................................................................................. 20-5
20-5
The Alcatel-Lucent 1830 PSS ZIC management window

Navigation pane
...................................................................................... 20-6
20-6
...................................................................................................................................................................... 20-8
20-8
Toolbar ..................................................................................................................................................................................... 20-10

20-10
Context menu ......................................................................................................................................................................... 20-11
20-11
Property window .................................................................................................................................................................. 20-12
20-12
Configurable dialog box .................................................................................................................................................... 20-13
20-13
Response Dialog Box
........................................................................................................................................................ 20-14
20-14
Confirmation Dialog Box
................................................................................................................................................ 20-15
20-15
....................................................................................................................................................................................................................................
1830 PSS
xxv
Issue 1 June 2013
Contents
....................................................................................................................................................................................................................................
Tool tip
.................................................................................................................................................................................... 20-16
20-16
Error dialog box
.................................................................................................................................................................. 20-17
20-17
Common Commands
......................................................................................................................................................... 20-18
20-18
Search function ..................................................................................................................................................................... 20-19

20-19
Go To menu ............................................................................................................................................................................ 20-21
20-21
View menu .............................................................................................................................................................................. 20-22
20-22
Show Alarms menu
............................................................................................................................................................. 20-23
20-23
Basic Alcatel-Lucent 1830 PSS ZIC procedures

Overview ................................................................................................................................................................................. 20-24
20-24
Concepts for connecting the Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) to
the NE .............................................................................................................................................................................. 20-25
20-25
Combined Alcatel-Lucent 1830 PSS ZIC / WebUI ................................................................................................. 20-26
20-26
Procedure 20-1: Initialize the NE using EZ setup tool ........................................................................................... 20-27
20-27
Procedure 20-2: Call up the Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC)
............ 20-37
20-37
Procedure 20-3: Logout from Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC)
........ 20-41
20-41
The Alcatel-Lucent 1830 PSS WebUI

Overview ................................................................................................................................................................................. 20-42
20-42
Using the WebUI .................................................................................................................................................................. 20-43
20-43
Basic Alcatel-Lucent 1830 PSS WebUI procedures
Overview ................................................................................................................................................................................. 20-45
20-45
Procedure 20-4: Log into the WebUI ............................................................................................................................ 20-46
20-46
Procedure 20-5: Exit the WebUI
.................................................................................................................................... 20-48
20-48
Procedure 20-6: Initial NE configuration .................................................................................................................... 20-49

20-49
Procedure 20-7: Submit ping request
........................................................................................................................... 20-51
20-51
Procedure 20-8: Submit traceroute request
................................................................................................................ 20-52
20-52
Glossary
Index
....................................................................................................................................................................................................................................
1830 PSS
xxvi
Issue 1 June 2013
List of tables
1
Information products related to Alcatel-Lucent 1830 PSS
...................................................................... xlix
1-1
FDA/CDRH laser classifications ....................................................................................................................... 1-21
1-2
OFCS hazard levels
1-3
Temperature and humidity levels for transportation (ETSI market)
1-4
Environmental conditions for transportation (ANSI market)
1-5
Temperature and humidity levels for storage (ETSI market) .................................................................. 1-39
1-6
Environmental conditions for storage (ANSI market)
1-7
Temperature and humidity levels for operation (ETSI market)
............................................................. 1-59
1-8
Temperature and humidity levels for operation (ANSI market)
............................................................ 1-60
2-1
Predefined user types
2-2
Default user types for internal purpose
2-3
User privilege levels ............................................................................................................................................... 2-16

2-16
2-4
Ports that support ACL filtering ......................................................................................................................... 2-31
2-5
System-defined port/filter associations
2-6
RADIUS authentication - VSA information
3-1
Maximum number of ECC channels supported per shelf
3-2
Communications Network Sizing
3-3
Parameters for static IP routes
5-1
Port groups ................................................................................................................................................................. 5-10

5-10
5-2
Port group modes and client selection modes ............................................................................................... 5-11
5-3
Client selection modes and compatible interface modules
5-4
Alcatel-Lucent 1830 PSS-32 Circuit Pack Slot Allocation ...................................................................... 5-27
5-5
Alcatel-Lucent 1830 PSS-32S Circuit Pack Slot Allocation ................................................................... 5-33
................................................................................................................................................ 1-21
1-21
.................................................... 1-36
................................................................. 1-37
.............................................................................. 1-41
............................................................................................................................................. 2-13
2-13
........................................................................................................... 2-13
........................................................................................................... 2-32
................................................................................................. 2-35
........................................................................... 3-6
..................................................................................................................... 3-19
............................................................................................................................ 3-81
...................................................................... 5-13
....................................................................................................................................................................................................................................
1830 PSS
xxvii
Issue 1 June 2013
List of tables
....................................................................................................................................................................................................................................
5-6
Alcatel-Lucent 1830 PSS-16 Circuit Pack Slot Allocation ...................................................................... 5-34
5-7
Applicability of restart types to circuit packs
5-8
1830 PSS Shelf Combinations
5-9
General parameters of an optical SDH/SONET port ............................................................................... 5-484
5-10
AINS parameters of an optical SDH/SONET port
5-11
Trace Messaging parameters of an optical SDH/SONET port ............................................................. 5-487
5-12
General parameters of an OTU port facility
5-13
AINS parameters of an OTU port facility
5-14
Trace Messaging parameters of an OTU port facility
5-15
Ingress error monitoring parameters of an OTU port facility
5-16
Value ranges for the shelf field in the AID depending on the shelf type
5-17
Relation of equipment name/equipment AID prefix to supported PROVISIONEDTYPES
5-18
Examples of equipment AIDs
5-19
Examples of facility AIDs
5-20
Timing reference AIDs
5-21
Examples of ASAP (Alarm Severity Assigned Profile) AIDs
5-22
Examples of THP (Threshold Profile) AIDs ............................................................................................... 5-574
5-23
Examples of common AIDs
5-24
Examples of firewall filter chain AIDs
8-1
Fields and parameters of the Edit BITS window ......................................................................................... 8-12
8-2
External timing input signal format .................................................................................................................. 8-41
8-3
SSM support settings .............................................................................................................................................. 8-41

8-41
10-1
Technology Type index table ............................................................................................................................ 10-87
16-1
Performance monitoring - Available bins ....................................................................................................... 16-7
16-2
Autonomous creation of PM registers
16-3
SDH/SONET near-end performance parameters ......................................................................................... 16-9
16-4
Ethernet performance parameters
............................................................................................. 5-119
......................................................................................................................... 5-137
................................................................................... 5-486
............................................................................................... 5-489
................................................................................................... 5-491
............................................................................. 5-492
.............................................................. 5-494
.......................................... 5-549
.... 5-549
.......................................................................................................................... 5-550
................................................................................................................................. 5-555
....................................................................................................................................... 5-571
.............................................................. 5-571
.............................................................................................................................. 5-576
........................................................................................................ 5-577
............................................................................................................. 16-8
................................................................................................................... 16-10
....................................................................................................................................................................................................................................
1830 PSS
xxviii
Issue 1 June 2013
List of tables
....................................................................................................................................................................................................................................
16-5
OTH performance parameters .......................................................................................................................... 16-12
16-6
SDH performance parameters
16-7
SONET performance parameters
16-8
OTH performance parameters .......................................................................................................................... 16-14
16-9
SES declaration thresholds (SDH)
......................................................................................................................... 16-13
.................................................................................................................... 16-13
................................................................................................................. 16-15
16-10 SES declaration thresholds (SONET)

16-11 SES declaration thresholds (OTH)
........................................................................................................... 16-15
................................................................................................................. 16-16
16-12 Default thresholds - SDH Regenerator Section

16-13 Default thresholds - SDH higher order path
16-14 Default thresholds - SONET Section
......................................................................................... 16-21
............................................................................................... 16-21
............................................................................................................ 16-22
16-15 Default thresholds - SONET path ................................................................................................................... 16-23

16-16 Default thresholds - ODUk
............................................................................................................................... 16-23
16-17 Default thresholds - OTUk ................................................................................................................................ 16-24

16-18 Cards and Ports that Support PM Data
16-19 PSS-32S Facilities
................................................................................................................................................ 16-36
16-36
16-20 Elements of a PM report

16-21 Validity indication
......................................................................................................... 16-28
.................................................................................................................................... 16-49
................................................................................................................................................ 16-51
16-51
16-22 Parameters for the PM mode settings ............................................................................................................ 16-87

16-23 Parameters for the PM data selection
............................................................................................................ 16-89
18-1
USB flash drive specifications
....................................................................................................................... 18-15
20-1
20-2
Minimum hardware/software requirements
.......................................................................................................................................... 20-30
................................................................................................ 20-37
....................................................................................................................................................................................................................................
1830 PSS
xxix
Issue 1 June 2013
List of tables
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
xxx
Issue 1 June 2013
List of figures
1-1
Warning symbols defined for safety instructions:
......................................................................................... 1-6
1-2
Multilabel (1830 PSS-16/PSS-32)
1-3
Multilabel (1830 PSS-32S)
1-4
Multilabel (1830 PSS-36)
1-5
Multilabel (PSS-64)
1-6
ESD bonding point at the Alcatel-Lucent 1830 PSS-64 subrack
.......................................................... 1-28
1-7
.......................................................... 1-29
1-8
.......................................................... 1-30
1-9
ESD bonding point at the Alcatel-Lucent 1830 PSS-32S subrack
1-10
1-11
ESD bonding point at the ETSI One Rack
1-12
Temperature and humidity levels for storage (ETSI market) .................................................................. 1-40
1-13
............................................................. 1-60
1-14
............................................................ 1-61
3-1
Dual GNE configurations ..................................................................................................................................... 3-23
4-1
Converged node view (card level)
5-1
Shelf interconnection
............................................................................................................................................. 5-47
5-47
5-2
Shelf interconnection
............................................................................................................................................. 5-51
5-51
5-3
Example for the representation of an ODU3 NIM ...................................................................................... 5-79
5-4
Example for the representation of facilities ................................................................................................... 5-98
5-5
Example for the representation of facilities
5-6
Examples .................................................................................................................................................................. 5-102

5-102
5-7
Example for the representation of an ODU3 NIM
.................................................................................................................... 1-14
................................................................................................................................ 1-15
................................................................................................................................... 1-16
.............................................................................................................................................. 1-17
1-17
...................................................... 1-31
.......................................................... 1-32
.................................................................................................... 1-33
..................................................................................................................... 4-3
................................................................................................ 5-100
................................................................................... 5-104
....................................................................................................................................................................................................................................
1830 PSS
xxxi
Issue 1 June 2013
List of figures
....................................................................................................................................................................................................................................
5-8
Example for highlighted cards in the display pane of the Alcatel-Lucent 1830 PSS ZIC
........ 5-122
5-9
11STMM10 OT signal processing from client port to DWDM line port
6-1
G.8032 Ring in the Initial State
6-2
G.8032 Ring in the Protecting State
9-1
Overview of available network protection mechanisms
9-2
Adding a protection leg to a one way protection
9-3
Adding a protection leg to a two way protection ......................................................................................... 9-11
9-4
Removing a protection leg from a one way protection
............................................................................. 9-16
9-5
Removing a protection leg from a two way protection
............................................................................. 9-17
11-1
Navigating directly from a facility to the Create Cross Connections window
14-1
Loopback Types ....................................................................................................................................................... 14-3

14-3
16-1
Performance monitoring of a bidirectional path (example) ..................................................................... 16-3
16-2
Performance monitoring process
16-3
Thresholding - Transient condition method
16-4
Thresholding - Standing condition method ................................................................................................. 16-20
16-5
Performance monitoring points in an 1830 PSS NE ................................................................................ 16-31
16-6
Analog parameter TCA
16-7
................................................................................................ 16-40
16-8
................................................................................................ 16-44
16-9
................................................................................................ 16-48
16-10 Example for the representation of facilities
................................................................................................ 16-53
....................................... 5-166
......................................................................................................................... 6-10
................................................................................................................. 6-11
............................................................................. 0-1
......................................................................................... 9-10
............................... 11-14
....................................................................................................................... 16-6
................................................................................................ 16-19
...................................................................................................................................... 16-33
19-1
Fan Unit positions
................................................................................................................................................... 19-6
19-6
19-2
Fan Unit fixing screws
19-3
Fan Unit extraction
19-4
Fan Unit insertion
19-5
Fan Unit fastening ................................................................................................................................................... 19-9

19-9
19-6
Correct insert operations
.......................................................................................................................................... 19-8
................................................................................................................................................. 19-8
19-8
................................................................................................................................................... 19-9
19-9
.................................................................................................................................... 19-11
....................................................................................................................................................................................................................................
1830 PSS
xxxii
Issue 1 June 2013
List of figures
....................................................................................................................................................................................................................................
19-7
Forbidden insertion operations
........................................................................................................................ 19-13
19-8
Slide latch usage
19-9
Correct card extraction
20-1
Alcatel-Lucent 1830 PSS ZIC Management Window ............................................................................... 20-7
20-2
Example: Context menu
20-3
Example: Properties window
20-4
Example: Configurable dialog box
20-5
Example: Response dialog box
20-6
Example: Confirmation dialog box ................................................................................................................ 20-15
20-7
Example: Tool tip
20-8
Example: Error dialog box
20-9
Example: General properties window
................................................................................................................................................... 19-14
19-14
....................................................................................................................................... 19-16
..................................................................................................................................... 20-11
........................................................................................................................... 20-12
................................................................................................................ 20-13
....................................................................................................................... 20-14
................................................................................................................................................. 20-16
20-16
............................................................................................................................... 20-17
........................................................................................................... 20-18
20-10 Example: Search command ............................................................................................................................... 20-19

20-11 Example: Search dialog ...................................................................................................................................... 20-20
20-12 Example: Search result
....................................................................................................................................... 20-20
20-20
20-13 Example: Go to ...................................................................................................................................................... 20-21

20-21
20-14 Example: View menu
.......................................................................................................................................... 20-22
20-15 Equipment tree hierarchy ................................................................................................................................... 20-44
....................................................................................................................................................................................................................................
1830 PSS
xxxiii
Issue 1 June 2013
List of figures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
xxxiv
Issue 1 June 2013
List of procedures
2

2-1
Create a user login
2-2
Set system-wide user security parameters
2-3
Display system-wide user security parameters
2-4
Delete a user login
.................................................................................................................................................. 2-52
2-52
2-5
Inhibit a user login
.................................................................................................................................................. 2-53
2-53
2-6
Allow a user login ................................................................................................................................................... 2-54

2-54
2-7
Display user property information
2-8
Edit user logins
2-9
Log off user
2-10
Retrieve information on all active user logins .............................................................................................. 2-60
2-11
Change password
2-12
Send a short free form text message to other users ..................................................................................... 2-63
2-13
Modify command access security level assigned to a TL1 command. ................................................ 2-65
2-14
Display command access security level assigned to a TL1 command
2-15
Copy security sensible files or data from/to an NE to/from a remote file server
2-16
Configure SSL authentication for ZIC to NE communication (high-level procedure)
2-17
Install a certificate for SSL authentication
2-18
Generate a new SSL key for SSL authentication
........................................................................................ 2-77
2-19
Request a new certificate for SSL authentication
...................................................................................... 2-79
2-20
Generate a new SSL key for SSL authentication
........................................................................................ 2-81
2-21
Configure RADIUS server attributes
2-22
Modify RADIUS server attributes
.................................................................................................................................................. 2-42
2-42
..................................................................................................... 2-45
............................................................................................ 2-49
.................................................................................................................... 2-55
........................................................................................................................................................ 2-56
2-56
............................................................................................................................................................... 2-59
2-59
.................................................................................................................................................... 2-61
2-61
................................................ 2-67
............................ 2-69
................ 2-75
................................................................................................... 2-76
............................................................................................................. 2-83
................................................................................................................... 2-86
....................................................................................................................................................................................................................................
1830 PSS
xxxv
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
2-23
Set RADIUS server authentication parameters
........................................................................................... 2-88
2-24
Delete a RADIUS server
2-25
Create a user .............................................................................................................................................................. 2-93

2-93
2-26
View or modify user details
2-27
Delete a user .............................................................................................................................................................. 2-99

2-99
2-28
Change password
2-29
View / terminate sessions ................................................................................................................................... 2-101
2-30
View SNMP v3 users
.......................................................................................................................................... 2-104
2-31
Create SNMP v3 user
.......................................................................................................................................... 2-105
2-32
Modify SNMP v3 user
2-33
View / modify system security attributes
2-34
Setting / viewing syslog properties
2-35
Setting / viewing CLI user activity logging properties
2-36
Setting / viewing SNMP user activity logging properties ...................................................................... 2-113
2-37
View security log
2-38
View all logs
2-39
Save a retrieved log to a file
2-40
Set/view user preferences
2-41
Create RADIUS server
2-42
View/modify RADIUS server
2-43
Delete RADIUS server
2-44
Provision RADIUS properties
2-45
Create trap destinations
...................................................................................................................................... 2-129
2-129
2-46
Delete trap destinations
...................................................................................................................................... 2-131
2-131
2-47
View trap destinations ......................................................................................................................................... 2-132

2-132
2-48
View/modify community strings ..................................................................................................................... 2-135
..................................................................................................................................... 2-90
................................................................................................................................ 2-97
.................................................................................................................................................. 2-100
2-100
........................................................................................................................................ 2-106
..................................................................................................... 2-108
................................................................................................................ 2-109
........................................................................... 2-111
.................................................................................................................................................. 2-115
2-115
........................................................................................................................................................... 2-117
2-117
............................................................................................................................. 2-119
.................................................................................................................................. 2-120
....................................................................................................................................... 2-122
.......................................................................................................................... 2-124
....................................................................................................................................... 2-126
......................................................................................................................... 2-127
....................................................................................................................................................................................................................................
1830 PSS
xxxvi
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................

3-1
Change the Site Identifier (SID)
........................................................................................................................ 3-27
3-2
Retrieve IP and MAC addresses
........................................................................................................................ 3-29
3-3
Set the FLC IP Addresses of the NE
3-4
Set the loopback IP address of the NE
3-5
Set the control plane IP addresses of the NE
3-6
Modify the TCP/IP stack parameters
3-7
Create an access control rule
3-8
Modify an existing access control rule
.......................................................................................................... 3-42
3-9
Delete an internet protocol access rule
.......................................................................................................... 3-43
3-10
Retrieve internet protocol access list
3-11
Modify the ASAP of the Customer LAN interface ..................................................................................... 3-57
3-12
Configure LAN interfaces to form a multi-shelf compound
3-13
Create a network interface on the embedded communication channels (ECCs)
3-14
Modify the ASAP of a network interface
3-15
Add a GCC leg to an ECC protection group ................................................................................................. 3-67
3-16
Remove GCC legs from the ECC protection group
3-17
Enable or disable a network interface .............................................................................................................. 3-71
3-18
Delete a network interface and an ECC protection group ........................................................................ 3-73
3-19
Create an IP-in-IP tunnel
3-20
Set the alarm severity profile of an IP-in-IP tunnel
3-21
Delete an IP-in-IP tunnel
3-22
Enter (add) a new static IP route in the IP routing table
3-23
Delete a static IP route from the IP routing table
3-24
Create the NTP Server address ........................................................................................................................... 3-87
3-25
Manage the NTP server address
3-26
Retrieve the NTP sync state
................................................................................................................ 3-31
............................................................................................................ 3-34
................................................................................................ 3-36
............................................................................................................... 3-38
............................................................................................................................. 3-41
.............................................................................................................. 3-44
................................................................... 3-59
............................. 3-63
....................................................................................................... 3-66
................................................................................... 3-69
...................................................................................................................................... 3-75
.................................................................................... 3-78
...................................................................................................................................... 3-80
........................................................................... 3-81
........................................................................................ 3-85
........................................................................................................................ 3-89
................................................................................................................................ 3-91
....................................................................................................................................................................................................................................
1830 PSS
xxxvii
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
3-27
Configure the global OSPF parameters
3-28
Create an OSPF area
3-29
Modify an OSPF area
3-30
Delete an OSPF area ............................................................................................................................................ 3-100

3-100
3-31
Configure the IP address range for the OSPF area
3-32
Delete the IP address range of an OSPF area
3-33
Configure OSPF interface parameters
.......................................................................................................... 3-106
3-34
Modify OSPF Authentication settings
.......................................................................................................... 3-109
3-35
View network (NE name, NE IP, software release) map information
3-36
View / modify IP route metric settings
3-37
Create IP static route ............................................................................................................................................ 3-117

3-117
3-38
View all IP routes .................................................................................................................................................. 3-119

3-119
3-39
Delete IP static route ............................................................................................................................................ 3-121

3-121
3-40
Create OSPF area .................................................................................................................................................. 3-122

3-122
3-41
View OSPF areas
3-42
View/modify OSPF details ................................................................................................................................ 3-132
3-43
Delete OSPF area .................................................................................................................................................. 3-137

3-137
3-44
Configure orderwire function ........................................................................................................................... 3-138
3-45
Create / view NTP server
3-46
View NTP properties
3-47
Create/view NTP keys
3-48
Set date and time manually
.............................................................................................................................................. 3-96
3-96
............................................................................................................................................ 3-98
................................................................................... 3-102
............................................................................................. 3-104
............................................... 3-113
......................................................................................................... 3-115
.................................................................................................................................................. 3-127
3-127
................................................................................................................................... 3-140
........................................................................................................................................... 3-143
........................................................................................................................................ 3-146
............................................................................................................................... 3-148

4-1
.......................................................................................................... 3-93
Connect OCS application to WDM application
............................................................................................. 4-2

5-1
Define general properties of the system
......................................................................................................... 5-44
....................................................................................................................................................................................................................................
1830 PSS
xxxviii
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
5-2
Create an extension shelf ...................................................................................................................................... 5-46
5-3
Remove an extension shelf
5-4
Provision or pre-provision I/O cards
5-5
Provision or pre-provision optical modules
5-6
Set a board/module out of service ..................................................................................................................... 5-61
5-7
Deprovision equipment
5-8
Perform a matrix card upgrade ........................................................................................................................... 5-66
5-9
Configure an optical interface port
5-10
Configure Optical Channel parameters
5-11
Perform remote laser shutdown on OTH network ports
5-12
Create an ODUn path termination
5-13
Configure an ODU path termination ................................................................................................................ 5-84
5-14
Changing the payload type of an ODU path termination
........................................................................ 5-89
5-15
Changing the sub-structure of an ODU path termination
....................................................................... 5-92
5-16
Deprovision an ODUk path termination function
5-17
Provision an optical SDH/SONET port
5-18
Provision an GBE/GBE10
5-19
Provision a Tandem Connection Monitoring (TCM) entity
5-20
Remove a facility
.................................................................................................................................................. 5-107
5-107
5-21
Restore a facility
................................................................................................................................................... 5-109
5-109
5-22
Allow equipment protection switching
......................................................................................................... 5-111
5-23
Inhibit equipment protection switching
........................................................................................................ 5-113
5-24
Initiate an equipment protection switch manually
5-25
Initiate a circuit pack reset ................................................................................................................................. 5-117

5-117
5-26
View or modify NE parameters
5-27
Reboot NE
5-28
Configure the firmware
.................................................................................................................................. 5-50
.............................................................................................................. 5-53
................................................................................................. 5-57
......................................................................................................................................... 5-64
................................................................................................................... 5-70
........................................................................................................... 5-72
........................................................................... 5-74
.................................................................................................................... 5-76
....................................................................................... 5-95
.......................................................................................................... 5-97
................................................................................................................................... 5-99
................................................................. 5-101
.................................................................................... 5-115
....................................................................................................................... 5-125
............................................................................................................................................................... 5-129
5-129
...................................................................................................................................... 5-131
....................................................................................................................................................................................................................................
1830 PSS
xxxix
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
5-29
View the firmware
................................................................................................................................................ 5-135
5-135
5-30
Create (pre-provision) a shelf ........................................................................................................................... 5-142
5-31
View/modify shelf properties
5-32
Delete a shelf
5-33
Test LEDs
5-34
Create a card
5-35
View / modify card properties .......................................................................................................................... 5-177
5-36
View card inventory ............................................................................................................................................. 5-178
5-37
View pluggable module inventory
5-38
Controller Protection Switch (EC/MTC1T9)
5-39
Upgrade EC (in-service upgrade from simplex to duplex)
5-40
Reboot card
5-41
Delete a card
5-42
Port provisioning procedures
5-43
Retrieve general properties of the system .................................................................................................... 5-447
5-44
Retrieve current conditions for a system component
.............................................................................. 5-448
5-45
Retrieve remote inventory for a system component
................................................................................ 5-451
5-46
Retrieve network element TL1 parameters
5-47
Retrieve information related to equipment protection groups .............................................................. 5-457
5-48
Retrieve and edit optical channel parameters
5-49
Diagnose equipment
5-50
Perform LED test .................................................................................................................................................. 5-462

5-462
5-51
Check shelf cabling
5-52
Retrieval analog optical parameters from optical modules
........................................................................................................................... 5-146
.......................................................................................................................................................... 5-151
5-151
................................................................................................................................................................ 5-152
5-152
........................................................................................................................................................... 5-175
5-175
................................................................................................................. 5-180
............................................................................................. 5-182
................................................................... 5-185
............................................................................................................................................................. 5-186
5-186
........................................................................................................................................................... 5-188
5-188
........................................................................................................................... 5-402
................................................................................................. 5-456
............................................................................................. 5-459
............................................................................................................................................ 5-460
............................................................................................................................................ 5-463
................................................................... 5-465
11QPE24 L2 Features
6-1
Configure Ethernet-Ring (one node) ................................................................................................................ 6-58
....................................................................................................................................................................................................................................
1830 PSS
xl
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................

7-1
View NE alarms
7-2
Create an Alarm Severity Assignment Profile (ASAP)
7-3
Display Alarm Assignment Profiles
7-4
Display Alarm Assignment Profiles assigned to specific entities .......................................................... 7-11
7-5
Manage ASAP profile ............................................................................................................................................ 7-12
7-6
Manage ASAP profile assigned to a specific entity .................................................................................... 7-14
7-7
Edit notification code ............................................................................................................................................. 7-16

7-16
7-8
Delete ASAP profile ............................................................................................................................................... 7-18

7-18
7-9
Display active alarm list
7-10
View condition list
7-11
Display active alarms or alarm level on a shelf or slot/card .................................................................... 7-26
7-12
View alarms history log
7-13
View events history log ......................................................................................................................................... 7-29
7-14
Modify alarm configuration
7-15
Provision environmental (housekeeping) alarms
......................................................................................................................................................... 7-3
7-3
............................................................................... 7-7
................................................................................................................. 7-10
....................................................................................................................................... 7-23
7-23
................................................................................................................................................. 7-25
7-25
........................................................................................................................................ 7-27
................................................................................................................................ 7-31
........................................................................................ 7-35

8-1
Configure the timing references
8-2
Configure external timing input ports
............................................................................................................... 8-8
8-3
Configure external timing references
............................................................................................................. 8-15
8-4
Perform a timing reference switch
8-5
Switch external timing reference
8-6
Clear a timing reference switch
8-7
Take an external timing reference out of service for maintenance purposes
8-8
Take an external timing input port out (BITS) out-of-service
8-9
Restore timing reference
8-10
Retrieve the current timing configuration
.......................................................................................................................... 8-3
................................................................................................................... 8-22
..................................................................................................................... 8-24
........................................................................................................................ 8-27
................................... 8-30
............................................................... 8-32
..................................................................................................................................... 8-34
..................................................................................................... 8-36
....................................................................................................................................................................................................................................
1830 PSS
xli
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
10
8-11
Retrieve provisioning and state information of external timing references
..................................... 8-38
8-12
Retrieve provisioning and state information of external timing input ports
.................................... 8-39

9-1
Add a protection leg to a cross-connection .................................................................................................... 9-10
9-2
Remove a protection leg from a cross-connection ...................................................................................... 9-16
9-3
Create an SNCP protection group
9-4
Modify an SNCP protection group
9-5
Delete an SNC protection group ........................................................................................................................ 9-30
9-6
Initiate an SNC protection switch
..................................................................................................................... 9-32
9-7
Release an SNC protection switch
.................................................................................................................... 9-34
9-8
Retrieve configuration parameters and status information of an SNC protection group
..................................................................................................................... 9-20
................................................................................................................... 9-27
.............. 9-36

10-1
Create protection group
10-2
View all protection groups
10-3
View/modify protection group ......................................................................................................................... 10-26
10-4
Delete protection group
10-5
Request protection switch .................................................................................................................................. 10-28
10-6
Configure OMSP protection
10-7
Configure E-SNCP protection
10-8
Configure OPS client side protection
10-9
Configure OLP protection
...................................................................................................................................... 10-16
................................................................................................................................ 10-22
...................................................................................................................................... 10-27
............................................................................................................................. 10-29
......................................................................................................................... 10-34
............................................................................................................ 10-36
................................................................................................................................. 10-40
10-10 Provision wave keys on an encoder port to support dangling OT procedure

10-11 Set expected network output power
10-12 View wave keys (decoder ports)
10-13 Clear wave keys
10-14 Set power
................................. 10-55
............................................................................................................... 10-58
..................................................................................................................... 10-59
.................................................................................................................................................... 10-62
10-62
................................................................................................................................................................. 10-63
10-63
....................................................................................................................................................................................................................................
1830 PSS
xlii
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
10-15 View channel power summary ......................................................................................................................... 10-65

10-16 View unexpected wave keys ............................................................................................................................. 10-67
10-17 View wave key data at NE level
..................................................................................................................... 10-69
10-18 View unexpected/missing wave keys at NE level
.................................................................................... 10-72
10-19 Provision optical line's monitoring (WT mode or WTOCM mode)
.................................................. 10-75
10-20 Add a service to a FOADM system or mixed FOADM-TOADM system

10-21 Add an Anydirection Add/Drop block to ROADM
...................................... 10-78
................................................................................. 10-83
10-22 Power management .............................................................................................................................................. 10-89

10-89
10-23 Power adjustment
................................................................................................................................................. 10-92
10-92
10-24 View/modify power commissioning values
................................................................................................ 10-96
10-25 LD power adjustment ........................................................................................................................................ 10-114

10-26 GMRE settings
.................................................................................................................................................... 10-116
10-116
10-27 GMRE Feasibility File Transfer .................................................................................................................... 10-117

10-28 GMRE OMS line parameters ......................................................................................................................... 10-118
10-29 GMRE optical impairment parameters ....................................................................................................... 10-119
10-30 Cross-phase modulation allowed wavelength set ................................................................................... 10-120
11
12

11-1
Create a cross-connection
11-2
Modify a cross-connection
11-3
Delete a cross-connection
11-4
Retrieve a list of cross-connections ................................................................................................................ 11-21
.................................................................................................................................. 11-10
................................................................................................................................ 11-15
.................................................................................................................................. 11-18

12-1
Display NE physical topology ............................................................................................................................ 12-8
12-2
Display NE logical topology
12-3
Provision OCH cross-connects
12-4
Create OCH cross-connect group
............................................................................................................................ 12-10
........................................................................................................................ 12-11
................................................................................................................... 12-17
....................................................................................................................................................................................................................................
1830 PSS
xliii
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
12-5
Provision ODUk cross-connects
..................................................................................................................... 12-19
12-6
Provision EVPL connections ............................................................................................................................ 12-22
12-7
Display the cross connect topology
12-8
Display the NE power trace
12-9
Display network power trace ............................................................................................................................ 12-32
............................................................................................................... 12-28
.............................................................................................................................. 12-30
12-10 Connect Alcatel-Lucent 1830 PSS-1 to 1830 PSS-32/PSS-16/PSS-32S

13
14

13-1
Configure port loopback ....................................................................................................................................... 13-2
13-2
Release Loopback
13-3
View loopback .......................................................................................................................................................... 13-9

13-9
16
................................................................................................................................................... 13-7
13-7

14-1
15
......................................... 12-34
Display, set, release loopbacks
........................................................................................................................... 14-4

15-1
Configure port loopback ....................................................................................................................................... 15-2
15-2
Release loopback ..................................................................................................................................................... 15-5

15-5
15-3
View loopback .......................................................................................................................................................... 15-7

15-7

16-1
Enable or disable PM data collection
16-2
Retrieve PM activation status ........................................................................................................................... 16-43
16-3
Retrieve PM data
16-4
Initialize PM registers
16-5
Upload the NE PM data to a remote file server
16-6
Create a new TCA profile
16-7
Rename a TCA profile
16-8
Modify the threshold settings of a TCA profile ......................................................................................... 16-63
16-9
Retrieve the threshold settings of a TCA profile
............................................................................................................ 16-39
.................................................................................................................................................. 16-47
16-47
......................................................................................................................................... 16-52
16-52
....................................................................................... 16-55
................................................................................................................................. 16-58
....................................................................................................................................... 16-61
....................................................................................... 16-65
....................................................................................................................................................................................................................................
1830 PSS
xliv
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
16-10 Delete a TCA profile
........................................................................................................................................... 16-66
16-66
16-11 Retrieve a list of facilities that use a particular TCA profile

16-12 Display PM data for EC/MTC1T9 card
................................................................ 16-67
....................................................................................................... 16-69
16-13 Set bins for EC/MTC1T9 card ......................................................................................................................... 16-72

16-14 Display all TCA profile assignments ............................................................................................................. 16-74
16-15 Modify TCA profile
............................................................................................................................................. 16-76
16-16 Display PM data for port

16-17 Set bins for port
................................................................................................................................... 16-77
..................................................................................................................................................... 16-80
16-80
16-18 Set baseline values for port

17
18
............................................................................................................................... 16-82

17-1
Backup the active database to the standby database
17-2
Transfer the NE standby database to a remote file server ...................................................................... 17-18
17-3
Retrieve information related to transferred files on a remote file server
17-4
Download a database from a remote file server to the standby database ......................................... 17-27
17-5
Restore database .................................................................................................................................................... 17-30

17-30
17-6
Backup database .................................................................................................................................................... 17-33

17-33
17-7
Restore database .................................................................................................................................................... 17-36

17-36
................................................................................ 17-17
......................................... 17-22

18-1
Upgrade to a new release of the NE software ............................................................................................... 18-3
18-2
Download a software generic from a remote file server to the standby software load .................. 18-9
18-3
Software download for disaster recovery
18-4
Switch from the current release to the new release
18-5
Switch back from the current release and database to previous release
18-6
Make the current release software the permanent active software
18-7
Software upgrade procedure
18-8
Modify/view software NE attributes procedure
................................................................................................... 18-14
.................................................................................. 18-18
........................................... 18-20
..................................................... 18-22
............................................................................................................................. 18-25
........................................................................................ 18-31
....................................................................................................................................................................................................................................
1830 PSS
xlv
Issue 1 June 2013
List of procedures
....................................................................................................................................................................................................................................
19
20
Routine procedures
19-1
Replace the dust filter
19-2
Replace a Fan Unit (FAN3T8)
19-3
Common card mounting rules .......................................................................................................................... 19-10
............................................................................................................................................ 19-3
19-3
........................................................................................................................... 19-6
20-1
Initialize the NE using EZ setup tool
20-2
Call up the Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC)
20-3
Logout from Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC)
20-4
Log into the WebUI
20-5
Exit the WebUI
20-6
Initial NE configuration
20-7
Submit ping request
20-8
Submit traceroute request
............................................................................................................ 20-27
............................. 20-37
.......................... 20-41
............................................................................................................................................. 20-46
...................................................................................................................................................... 20-48
20-48
..................................................................................................................................... 20-49
............................................................................................................................................. 20-51
.................................................................................................................................. 20-52
....................................................................................................................................................................................................................................
1830 PSS
xlvi
Issue 1 June 2013
About this document

About this document
Purpose
This User Provisioning Guide (UPG) provides operations, administration, and

maintenance information about the Alcatel-Lucent 1830 Photonic Service Switch (PSS).
This document describes the procedures for provisioning and operating a Alcatel-Lucent
1830 PSS system by using the Alcatel-Lucent 1830 PSS ZIC and the WebUI.
Depending on the configuration of the Alcatel-Lucent 1830 PSS system either the
Alcatel-Lucent 1830 PSS ZIC or the WebUI is to be used.
If the system is a WDM only application the WebUI is to be used (see The
Alcatel-Lucent 1830 PSS WebUI (p. 20-42)).
If the system is a OCS only application the Alcatel-Lucent 1830 PSS ZIC is to be
used (see The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC)
(p. 20-3)).
If the system is a mixed application the Alcatel-Lucent 1830 PSS ZIC is to be used.
For configuring WDM specific parts the WebUI is to be started from the
Alcatel-Lucent 1830 PSS ZIC (see The Alcatel-Lucent 1830 PSS Zero Installation
Craft Terminal (ZIC) (p. 20-3)).
Safety information
For your safety, this document contains safety statements. Safety statements are given at
points where risks of damage to personnel, equipment, and operation may exist. Failure to
follow the directions in a safety statement may result in serious consequences.
Supported systems
The Alcatel-Lucent 1830 Photonic Service Switch (PSS) supports WDM functionality
and OCS functionality within one node. The node consists of one WDM main shelf with
optional extension shelves and/or one OCS main shelf with optional extension shelves.
The WDM functionality is supported by Alcatel-Lucent 1830 PSS-16, Alcatel-Lucent
1830 PSS-32, and Alcatel-Lucent 1830 PSS-32S shelves. The OCS functionality is
supported by Alcatel-Lucent 1830 PSS-36 and Alcatel-Lucent 1830 PSS-64 shelves.
...................................................................................................................................................................................................................................
1830 PSS
xlvii
Issue 1 June 2013
About this document

....................................................................................................................................................................................................................................
Conventions used
These conventions are used in this document:

Numbering
The chapters of this document are numbered consecutively. The page numbering restarts
at 1 in each chapter. To facilitate identifying pages in different chapters, the page
numbers are prefixed with the chapter number. For example, page 2-3 is the third page in
chapter 2.
Cross-references
Cross-reference conventions are identical with the conventions used for page numbering
The first number in a reference to a particular page refers to the corresponding chapter.
Keyword blocks
This document contains so-called keyword blocks to facilitate the location of specific text
passages. The keyword blocks are placed to the left of the main text and indicate the
contents of a paragraph or group of paragraphs.
Typographical conventions
Special typographical conventions apply to elements of the graphical user interface

(GUI), file names and system path information, keyboard entries, alarm messages, and so
on:
Text appearing on a graphical user interface (GUI), such as menu options, window
titles or push buttons:
Provision, Delete, Apply, Close, OK (push-button)
Provision Timing/Sync (window title)
Administration Security User Provisioning (path for invoking a window)
File names and system path information:

setup.exe
C:/Program Files/Alcatel-Lucent
Keyboard entries:
F1, Esc X, Alt-F, Ctrl-D, Ctrl-Alt-Del (simple keyboard entries)
A hyphen between two keys means that you have to press both keys. Otherwise,
you have to press a single key, or a number of keys in sequence.
copy abc xyz (command)
A complete command that you enter.
Alarms and error messages:

Loss of Signal
HP-UNEQ, MS-AIS, LOS, LOF
....................................................................................................................................................................................................................................
1830 PSS
xlviii
Issue 1 June 2013
About this document

....................................................................................................................................................................................................................................
Abbreviations
Abbreviations used in this document can be found in the Glossary unless it can be
assumed that the reader is familiar with the abbreviation.
Related information
Table 1
Document title
Document code
Alcatel-Lucent 1830 PSS Safety Guide
8DG-61259-AAAA-TAZZQ
Provides users of Alcatel-Lucent 1830 PSS systems with the relevant information
and safety guidelines to safeguard against personal injury. Furthermore, the Safety
Guide is useful to prevent material damage to the equipment. The Safety Guide
must be read by the responsible technical personnel before performing relevant
work on the system. The valid version of the document must always be kept close
to the equipment.
Alcatel-Lucent 1830 PSS Product Information and Planning Guide
8DG-61259-AAAA-TQZZA
Presents a detailed overview of the system, describes its applications, gives

planning requirements, engineering rules, ordering information, and technical
specifications.
Alcatel-Lucent 1830 PSS User Provisioning Guide
8DG-61259-AAAA-TCZZA
Provides step-by-step information for use in daily system operations. The manual
demonstrates how to perform system provisioning, operations, and administrative
tasks.
Alcatel-Lucent 1830 PSS Maintenance and Trouble-Clearing Guide
8DG-61259-AAAA-TMZZA
Gives detailed information on each possible alarm message. Furthermore, it

provides procedures for routine maintenance, troubleshooting, diagnostics, and
component replacement.
Alcatel-Lucent 1830 PSS Installation and System Turn-Up Guide (Alcatel-Lucent
1830 PSS-36)
8DG-61259-AAAA-TKZZA
A step-by-step guide to system installation and set up. It also includes information
needed for pre-installation site planning and post-installation acceptance testing.
1830 PSS-64)
8DG-61259-AAAA-TLZZA
1830 PSS-16 and PSS-32)
8DG-61259-AAAA-TJZZA
Alcatel-Lucent 1830 PSS CLI Command Guide
8DG-61259-AAAA-THZZA
Provides information about the Command Line Interface (CLI) for Alcatel-Lucent
1830 PSS and describes the CLI attributes and commands.
....................................................................................................................................................................................................................................
1830 PSS
xlix
Issue 1 June 2013
About this document

....................................................................................................................................................................................................................................
Table 1
Document title
Document code
Alcatel-Lucent 1830 PSS Engineering and Planning Tool User Guide
8DG-61259-AAAA-TEZZA
(continued)
Provides step-by-step information for use in daily system operations for the EPT.
The manual demonstrates how to perform system provisioning, operations, and
commissioning tasks.
Alcatel-Lucent 1830 PSS OCS TL1 Command Guide
8DG-61259-AAAA-TFZZA
Describes the external TL1 interface for Alcatel-Lucent 1830 PSS in terms of TL1
command, responses, and notification definitions.
Alcatel-Lucent 1830 PSS Photonics TL1 Command Guide
8DG-61259-AAAA-TGZZA
Describes the external TL1 interface for Alcatel-Lucent 1830 PSS in terms of TL1
command, responses, and notification definitions.
Alcatel-Lucent 1830 PSS GMPLS/GMRE Guide
8DG-61259-AAAA-TWZZA
Contains information about the GMPLS Routing Engine (GMRE) of the

Alcatel-Lucent 1830 PSS; it provides a high-level functional overview of the
GMRE and describes the steps to plan and set up a GMRE-controlled network.
Alcatel-Lucent 1830 PSS Quick Reference Guide
8DG-61259-AAAA-TNZZA
Provides users of Alcatel-Lucent 1830 PSS a streamlined, easy-to-use navigation

aid to facilitate the use of the system.
Alcatel-Lucent 1354 RM-PhM Photonic Manager EMS Reference Guide
8DG-61259-AAAA-TXZZA
Provides information for accessing the 1354 RM-PhM and using it to configure
and manage the Alcatel-Lucent 1830 PSS network.
Alcatel-Lucent 1830 PSS DCN Planning and Engineering Guide (Photonic
applications)
8DG-61259-AAAA-TPZZA
Provides information for the planning and configuration of a Data Communication

Network (DCN) for photonic applications, that is for Alcatel-Lucent 1830 PSS-16
and Alcatel-Lucent 1830 PSS-32 systems (WDM).
Alcatel-Lucent 1830 PSS DCN Planning and Engineering Guide (Switching
applications)
8DG-61259-AAAA-TRZZA
Provides information for the planning and configuration of a Data Communication

Network (DCN) for switching applications, that is for Alcatel-Lucent 1830 PSS-36
and Alcatel-Lucent 1830 PSS-64 systems (OCS).
Alcatel-Lucent 1830 PSS Smart Compact Ethernet Demarcation Device (Smart
cEDD) User Guide
8DG-61259-AAAA-TYZZA
Provides instructions for use and descriptions of the features of the Smart Compact
Ethernet Demarcation Device (Smart cEDD).
Alcatel-Lucent 1830 PSS Commissioning and Power Balancing Tool User Guide
8DG-61259-AAAA-TBZZA
Provides instructions for use and descriptions of the features of the Commissioning
and Power Balancing (CPB) Tool.
Alcatel-Lucent 1830 PSS Electronic Documentation Library
8DG-61259-AAAA-TZZZA
Contains all documents related to Alcatel-Lucent 1830 PSS in electronic formats.

Alcatel-Lucent 1830 PSS Software Release Description
This document is delivered with the NE software.
....................................................................................................................................................................................................................................
1830 PSS
l
Issue 1 June 2013
About this document

....................................................................................................................................................................................................................................
These documents can be downloaded from the Alcatel-Lucent Online Customer Support
Site (OLCS) (https://support.alcatel-lucent.com) or through your Local Customer
Support.
Technical support
For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
How to comment
To comment on this document, go to the Online Comment Form (http://infodoc.alcatellucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).
....................................................................................................................................................................................................................................
1830 PSS
li
Issue 1 June 2013
About this document

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
lii
Issue 1 June 2013
Safety
1
Overview
Purpose
This chapter on safety provides users of Alcatel-Lucent 1830 PSS systems with the
relevant information and safety guidelines to safeguard against personal injury.
Furthermore, this chapter may be useful to prevent material damage to the equipment.
This chapter on safety must be read by the responsible technical personnel before carrying
out relevant work on the system. The valid version of this document must always be kept
close to the equipment.
Contents
1-3
Structure of safety statements
1-4
Basic safety aspects
1-7
1-11
Potential sources of danger
1-12
Laser safety
1-13
Laser product classification
1-20
Equipment grounding
1-25
Electrostatic discharge
1-26
1-34
Transportation
1-35
Storage
1-38
Installation
1-42
1-49
1-53
...................................................................................................................................................................................................................................
1830 PSS
1-1
Issue 1 June 2013
Safety
Overview
....................................................................................................................................................................................................................................
1-63
Event of failure
1-66
....................................................................................................................................................................................................................................
1830 PSS
1-2
Issue 1 June 2013
Safety
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides general information on the structure of safety instructions and
summarizes general safety requirements.
Contents
1-4
1-7
....................................................................................................................................................................................................................................
1830 PSS
1-3
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................

Overview
This topic describes the components of safety statements that appear in this document.
General structure
Safety statements include the following structural elements:
E
L
MP
CAUTION
Lifting hazard
SA
Lifting this equipment by yourself can result in injury

due to the size and weight of the equipment.
Always use three people or a lifting device to transport

and position this equipment.
[ABC123]
F
G
H
Item
Structure element
Purpose
Safety alert symbol
Indicates the potential for personal injury

(optional)
Safety symbol
Indicates hazard type (optional)
Signal word
Indicates the severity of the hazard
Hazard type
Describes the source of the risk of damage or

injury
Safety message
Consequences if protective measures fail
Avoidance message
Protective measures to take to avoid the hazard
Identifier
The reference ID of the safety statement

(optional)
....................................................................................................................................................................................................................................
1830 PSS
1-4
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Signal words
The signal words identify the hazard severity levels as follows:

Signal word
Meaning
DANGER
Indicates an extremely hazardous situation which, if not avoided, will

result in death or serious injury.
WARNING
Indicates a hazardous situation which, if not avoided, could result in

death or serious injury.
CAUTION
Indicates a hazardous situation which, if not avoided, could result in

minor or moderate injury.
NOTICE
Indicates a hazardous situation not related to personal injury.
....................................................................................................................................................................................................................................
1830 PSS
1-5
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Warning symbols
Figure 1-1 Warning symbols defined for safety instructions:
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
g_sfg_0001
Legend
1
General warning of danger
13
Noxious substance
Electric shock
14
Explosion hazard
Hazard of laser radiation
15
Falling object hazard
Components sensitive to electrostatic discharge (ESD)
16
Risk of suffocation
Electromagnetic radiation
17
Pinch hazard
Flammable material / Risk of fire
18
Lifting hazard, heavy object
Service disruption hazard
19
Inhalation hazard
Laceration hazard
20
Slip hazard
Corrosive substance
21
Trip hazard
10
Hazard caused by batteries
22
Hazard of falling
11
Hot surface
23
Arc-flash hazard
12
Heavy overhead load
24
Equipment damage hazard
....................................................................................................................................................................................................................................
1830 PSS
1-6
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................

Purpose
This topic covers basic safety aspects relating to the Alcatel-Lucent 1830 Photonic
Service Switch (PSS) with which you must be familiar prior to installing or using the
product.
General safety requirements
To reduce the risk of personal injury or damage to equipment, ensure that you read,
understand, and follow the following general safety requirements prior to installing or
using the Alcatel-Lucent 1830 Photonic Service Switch (PSS).
Ensure that transport, storage, installation, and operation of the system are conducted
only under specified permissible conditions. See the accompanying documentation
and information on the system.
Ensure that installation, configuration, and disassembly of the system are conducted
only by suitably qualified personnel and with reference to the appropriate
documentation. Due to the complexity of the system, personnel require special
training.
Identify potential hazards prior to starting the installation.

Ensure that the system is operated only by trained and authorized users. The user must
operate the system only after having read and understood the chapter on safety and the
parts of the documentation relevant to operation. For complex systems, additional
training is recommended. Any obligatory training for operating and service personnel
must be completed and documented.
Follow all instructions marked on the product, including both general instructions and
the stated methods for avoiding hazards.
Do not operate the system unless all appropriate safety measures, precautions, and
instructions have been taken or followed. Any faults and errors that might affect
safety must be reported immediately by the user to appropriate personnel responsible
for safety.
Operate the system only under the environmental conditions and with the connections
described in the documentation.
Modifications to any part of the system, including software, should be conducted only
by trained and qualified personnel and only in a manner as authorized by
Alcatel-Lucent. Alcatel-Lucent disclaims liability for any damages arising from
unauthorized modifications, and unauthorized modifications may lead to a voiding of
any and all warranties.
Ensure that only components that are recommended by the manufacturer and are
listed in the procurement documents are used.
Avoid use of non-system software. The use or installation of non-system software can
adversely affect the normal functioning of the system.
....................................................................................................................................................................................................................................
1830 PSS
1-7
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Use tested and virus-free data carriers (memory sticks, DVDs, CDs, ) only.
Ensure that any work that has any impact on safety facilities, the clearance of faults,
and the maintenance of equipment are carried out only by trained and qualified
personnel and in conjunction with the appropriate documentation. Use only approved
measuring and test equipment.
Ensure that calibrations, special tests after repairs, and regular safety checks are
conducted, documented, and archived.
Use only specified chemicals or materials.
Consult material safety data sheets (MSDSs) or the equivalent information when
working with hazardous chemicals.
Summary of important safety instructions
Observe the following safety instructions, which are of particular importance for
Alcatel-Lucent 1830 PSS systems:
The equipment is to be installed only in Restricted Access Areas in business and

customer premises for applications in accordance with Articles 110-18, 110-26 and
110-27 of the National Electrical Code, ANSI/NFPANo.70, IEC 60950-1, IEC
60825-2, EN 60950-1 and EN 60825-2. Other installations exempt from the
enforcement of the National Electrical Code may be engineered according to the
accepted practices of the local telecommunications utility.
1830 PSS-36 and 1830 PSS-64 are also compliant to UL60950-1 and CSA60950-1.
Alcatel-Lucent 1830 PSS systems contain optical circuit packs that can emit laser
radiation assessed as IEC Hazard Level 1M.
Therefore, Alcatel-Lucent 1830 PSS systems must be installed in restricted locations,
according to IEC 60825-2 and EN 60825-2, where there is no ready access to the
general public, but only to authorized persons who have received adequate training in
laser safety.
This product should be operated only from the type of power source indicated on the
marking label.
This equipment must be provided with a readily accessible disconnect device as part
of the building installation.
This equipment is intended to be provided with an appropriate branch circuit
protection on both the A and B 48/60 V DC input feeds as follows:
40 A (max.) for the 1830 PSS-16 system
80 A (max.) for the 1830 PSS-32 system

3 50 A (max.) for the 1830 PSS-32S system
3 50 A (max.) for the 1830 PSS-36 system

3 100 A (max.) for the 1830 PSS-64 system
....................................................................................................................................................................................................................................
1830 PSS
1-8
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Disconnect up to six (6) power supply connections when removing power from the
system.
Installation must include an independent frame ground drop to the building ground.
Refer to the Alcatel-Lucent 1830 PSS Installation and System Turn-Up Guides which
are available for PSS-16/32/32S, PSS-36, and PSS-64.
During installation and handling (for example transport), heavy equipment like racks
or pre-installed subracks must be secured to avoid tipping over.
For information on proper mounting instructions, consult the Alcatel-Lucent 1830 PSS
Installation and System Turn-Up Guides which are available for PSS-16/32/32S,
PSS-36, and PSS-64.
Install only equipment identified in the Alcatel-Lucent 1830 PSS Installation and
System Turn-Up Guides for PSS-16/32/32S, PSS-36, and PSS-64 provided with this
product. Use of other equipment may result in improper connection of circuitry
leading to fire or injury to persons.
To reduce the risk of electrical shock, do not disassemble this product. Installation and
service should be performed by trained personnel only. Opening or removing covers
or circuit boards may expose you to dangerous voltages or other risks. Incorrect
re-assembly can cause electrical shock when the unit is subsequently used.
If a system with dual power feed is operated with only one Power Supply, Filter, and
Clock Interface Card (PSF3T8) and Fan Unit (FAN3T8), electrical connectors on the
backplane carrying a voltage of 48 V DC can be touched. This can cause electric
shocks. Always use both Power Supply, Filter, and Clock Interface Cards (PSF3T8)
and Fan Units (FAN3T8) to ensure safe operation.
Slots and openings in this product are provided for ventilation. To protect the product
from overheating, these openings must not be blocked or covered. This product
should not be placed in a built-in installation unless proper ventilation is provided.
Never push objects of any kind into this product through slots as they may touch
dangerous voltage points or short-out parts, which could result in a risk of fire or
electrical shock.
Never spill liquids of any kind on the product.
Never install telecommunication wiring during a lightning storm.

Never install telecommunication connections in wet locations.
....................................................................................................................................................................................................................................
1830 PSS
1-9
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Personal protective equipment

Protection against hazardous laser radiation
In DWDM systems which use Raman amplifiers hazard
levels in excess of 1M are very likely to occur, and the
use of appropriate protective glasses is strongly
recommended.
Protection against acoustic noise

Alcatel-Lucent 1830 PSS systems are designed for the
operation in unattended offices. However, in lab
environments, where multiple systems are operated in
parallel, based on national regulations hearing protection
may be necessary.
To protect yourself against acoustic noise, wear hearing
protection.
....................................................................................................................................................................................................................................
1830 PSS
1-10
Issue 1 June 2013
Safety
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
The aspects of laser safety and handling of components sensitive to electrostatic

discharge (ESD) are of vital importance for the Alcatel-Lucent 1830 PSS equipment.
Therefore, the key safety instructions for these subjects are summarized in the following.
Contents
1-12
Laser safety
1-13
1-20
Equipment grounding
1-25
1-26
....................................................................................................................................................................................................................................
1830 PSS
1-11
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................

The Alcatel-Lucent 1830 PSS equipment fulfils all national and international safety
requirements in the countries where the product is sold. The system is provided with a
high degree of operational safety resulting from many years of development experience
and continuous stringent quality checks in our company.
The equipment is safe in normal operation. There are, however, some potential sources of
danger that cannot be completely eliminated. In particular, these arise during the:
opening of housings or equipment covers

manipulation of any kind within the equipment, even if it has been disconnected from
the power supply
transportation of subracks and racks

disconnection of optical or electrical connections.
through the following:
contact with live parts

laser light
contact with hot surfaces
contact with sharp edges
acoustic noise.
....................................................................................................................................................................................................................................
1830 PSS
1-12
Issue 1 June 2013
Safety
Laser safety
....................................................................................................................................................................................................................................
Laser safety
System design
The Alcatel-Lucent 1830 PSS system complies with the regulations FDA/CDRH 21 CFR
1040.10 and 1040.11 issued by the Center for Devices and Radiological Health (CDRH)
of the Food and Drug Administration (FDA) as a Class I laser product and with the
IEC/UL/CSA/EN 60825-1 standards as a Class 1 Optical Fiber Telecommunication laser
product.
The system has been designed to help ensure that the operating personnel are not
endangered by laser radiation during normal system operation. The safety measures
specified in the FDA/CDRH regulations and the international standards IEC 60825-Part 1
and 2, respectively, are met.
....................................................................................................................................................................................................................................
1830 PSS
1-13
Issue 1 June 2013
Safety
Laser safety
....................................................................................................................................................................................................................................
Labels
1830 PSS-16/PSS-32
The following figure shows the multilabel affixed on the rear of the Alcatel-Lucent
1830 PSS-16 and Alcatel-Lucent 1830 PSS-32 subrack. It includes the laser warning
label.
Figure 1-2 Multilabel (1830 PSS-16/PSS-32)
Note: Here, the Alcatel-Lucent 1830 PSS-16 shelf label is shown. Safety information
on shelf labels for 1830 PSS-16 and PSS-32 is identical, only the list of supported
power supplies is different.
....................................................................................................................................................................................................................................
1830 PSS
1-14
Issue 1 June 2013
Safety
Laser safety
....................................................................................................................................................................................................................................
1830 PSS-32S
1830 PSS-32S subrack. It includes the laser warning label.
Figure 1-3 Multilabel (1830 PSS-32S)
....................................................................................................................................................................................................................................
1830 PSS
1-15
Issue 1 June 2013
Safety
Laser safety
....................................................................................................................................................................................................................................
1830 PSS-36
1830 PSS-36 subrack. It includes the laser warning label.
Figure 1-4 Multilabel (1830 PSS-36)
....................................................................................................................................................................................................................................
1830 PSS
1-16
Issue 1 June 2013
Safety
Laser safety
....................................................................................................................................................................................................................................
1830 PSS-64
1830 PSS-64 subrack. It includes the laser warning label.
Figure 1-5 Multilabel (PSS-64)
....................................................................................................................................................................................................................................
1830 PSS
1-17
Issue 1 June 2013
Safety
Laser safety
....................................................................................................................................................................................................................................
Beware of the following potential sources of danger which will remain despite all safety
measures taken:
Laser radiation can cause damage to the skin and eyes.

Laser radiation from optical transmission systems is in a wavelength range that is
invisible to the human eye.
Laser classes
The maximum output power of laser radiation depends on the type of laser diode used.
The international standards IEC/UL/CSA/EN 60825-1, respectively, as well as the
FDA/CDRH regulations define the maximum output power of laser radiation for each
laser class in accordance with the wavelength.
The classification scheme is based on the ability of the laser emission or the reflected
laser emission to cause injury to the eye or skin during normal operating conditions.
Laser safety instructions
During service, maintenance, or restoration, an optical fiber telecommunication system is

considered unenclosed.
When working at an unenclosed system, observe the following instructions to avoid
exposing yourself and others to risk:
Only authorized, trained personnel must be permitted to do service, maintenance, and

restoration. All unauthorized personnel must be excluded from the immediate area of
the optical fiber telecommunication systems during installation and service.
Read the relevant descriptions in the manuals before taking equipment into operation
or carrying out any installation and maintenance work on the optical port units, and
follow the instructions. Ignoring the instructions may result in hazardous laser
radiation exposure.
Do not view directly into the laser beam with optical instruments such as a fiber
microscope, because viewing of laser emission in excess of Class 1 limits
significantly increases the risk of eye damage.
Never look into the end of an exposed fiber or an open connector as long as the
optical source is still switched on.
Ensure that the optical source is switched off before disconnecting optical fiber
connectors.
If you are not sure that the optical source is switched off, check to ensure that the
optical switch is switched off by measuring the output power with an optical power
meter.
....................................................................................................................................................................................................................................
1830 PSS
1-18
Issue 1 June 2013
Safety
Laser safety
....................................................................................................................................................................................................................................
Laser radiation
WARNING
Laser hazard
Devices that are designated as having hazard level 1M laser radiation can cause damage
to eyes.
Do not view directly with non-attenuating optical instruments.
WARNING
Laser hazard
Use of controls, adjustments, and procedures other than those specified herein may result
in hazardous laser radiation exposure.
WARNING
Laser hazard
Alcatel-Lucent 1830 PSS-36 MDIO connections are not protected and may defeat the
Automatic (Optical) Power Reduction (APR) when a fault occurs in the power filter or
associated circuitry, and when repairs are being made to the power filter module on
which the MDIO connector is located.
....................................................................................................................................................................................................................................
1830 PSS
1-19
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................

Standards compliance
The Alcatel-Lucent 1830 PSS product complies with the applicable IEC standards and the
Food and Drug Administrations Center for Devices and Radiological Health
(FDA/CDRH) regulations. The Alcatel-Lucent 1830 PSS product conforms to Class 1
Laser Product according to IEC standards and FDA/CDRH regulations.
FDA/CDRH regulations
Laser products are classified in accordance with the FDA/CDRH - 21 CFR 1010 and
1040. The classification scheme is based on the ability of the laser emission to cause
injury to the eye or skin during normal operating conditions.
In the United States, lasers and laser systems in the infrared wavelength range (greater
than 700 nm) are assigned to one of the following classes. Please refer to FDA/CDRH
laser classification (p. 1-20):
Class I
Class IIIb
Class IV
Laser classification is dependent upon operating wavelength, output power and fiber
mode field diameter (core diameter).
IEC requirements
The International Electro-Technical Commission (IEC) establishes standards for the

electrical and electronic industries. The IEC 60825-Part 1 and 2 have been established for
the worldwide safety of laser products.
According to the IEC classification, lasers and laser systems in the infrared wavelength
range (greater than 700 nm) are assigned to one of the following classes. Refer to OFCS
hazard levels (p. 1-21):
Class 1
Class 1M
Class 3R
Class 3B
Class 4
FDA/CDRH laser classification
Laser classification is dependent upon the following: operating wavelength, output power,
fiber core/mode field diameter, and time base. Other parameters may be required for
non-fibered laser products, such as beam divergence/diameter.
....................................................................................................................................................................................................................................
1830 PSS
1-20
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
The following table cites the FDA/CDRH classification of typical Alcatel-Lucent laser
products at the designated wavelengths that terminate into a single-mode 8.8 m mode
field diameter fiber. Different mode field diameters and multimode fibers will yield
different optical power levels.
Table 1-1
FDA/CDRH laser classifications
Laser class
Wavelength
Max. output power of laser radiation
1310 nm
1.53 mW
+1.85 dBm
1550 nm
8.52 mW
+9.3 dBm
1310 nm
500 mW
+27 dBm
1550 nm
500 mW
+27 dBm
1310 nm
> 500 mW
> +27 dBm
1550 nm
> 500 mW
> +27 dBm
IIIb
IV
Explanatory note: In the United States, lasers and laser systems are assigned to one of the
following classes: Roman numerals I, IIa, II, IIIa, IIIb, and IV. Classes I, IIIb and IV
apply to lasers of all wavelengths. Classes IIa, II and IIIa apply only to those lasers
operating within the visible wavelength range (400-700 nm). Alcatel-Lucent laser
products typically operate in the infrared wavelength range (greater than 700 nm) and,
therefore, are primarily in the Class I or Class IIIb classifications.
OFCS hazard levels
The maximum mean power for each hazard level for the most important wavelengths and
optical fiber types used in optical fiber communications (OFCS) (see Hazard level
assignment (p. 1-22)) is presented in the following table from IEC 60825-2 standard. For
an OFCS, the hazard level from IEC 60825-2 is closely related to the laser classification
procedure in IEC 60825-1.
Table 1-2
OFCS hazard levels
Wavelength and
fiber type
633 nm (MM)
Hazard level
1
1M
2M
0,39 mW
3,9 mW
1 mW
10 mW
(-4,1 dBm)
(+5,9 dBm)
(0 dBm)
(+ 10 dBm)
3R
See Terms and
Definitions 3.9 in
3B
500 mW
(+27 dBm)
the Standard
780 nm (MM)
850 nm (MM)
0,57 mW
5,6 mW
(-2,5 dBm)
(+7,5 dBm)
0,78 mW
7,8 mW
(-1,1 dBm)
(+8,9 dBm)
500 mW
(+27 dBm)
500 mW
(+27 dBm)
....................................................................................................................................................................................................................................
1830 PSS
1-21
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Table 1-2
OFCS hazard levels
(continued)
Wavelength and
Hazard level
fiber type
980 nm (MM)
1M
1,42 mW
14,1 mW
(+1,53 dBm)
(+11,5 dBm)
1,42 mW
2,66 mW
(+1,53 dBm)
(+4,2 dBm)
15,6 mW
156 mW
(+12 dBm)
(+21,9 dBm)
15,6 mW
42,8 mW
(+12 dBm)
(+16,3 dBm)
1400 nm ... 1600

nm (MM)
10 mW
384 mW
(+10 dBm)
(+25,8 dBm)
1420 nm (SM)
10 mW
115 mW
(+10 dBm)
(+20,6 dBm)
10 mW
136 mW
(+10 dBm)
(+21,3 dBm)
980 nm (SM)
1310 nm (MM)
1310 nm (SM)
1550 nm (SM)
2M
3R
3B
500 mW
(+27 dBm)
7,26 mW
500 mW
(+8,6 dBm)
(+27 dBm)
500 mW
(+27 dBm)
80 mW
500 mW
(+19 dBm)
(+27 dBm)
500 mW
(+27 dBm)
500 mW
(+27 dBm)
500 mW
(+27 dBm)
Notes:
1.
Class 3R only exists if the maximum power is within five times the Accessible Emission Limit (AEL) of
Class 1. Please refer to the IEC 60825-1 Ed. 2.0 (2007) and IEC 60825-2 Ed. 3.1 (2007) standards for
detailed information.
2.
The fibre parameters used are the most conservative case. Listed figures for the = 1310 and 1550 nm are
calculated for a fibre 11 microns mode field diameter (MFD) and those for = 980 nm are for 7 microns
MFD.
3.
Many systems operating at 1550 nm with the use of erbium doped fibre amplifiers (EDFAs) pumped by 1480
nm or 980 nm lasers use transmission fibres with smaller MFDs. For example, 1550 nm dispersion shifted
fibre cables have upper limit values of MFD of 9,1 microns.
Hazard level assignment
Hazard level refers to the potential hazard from laser emission at any location in an
end-to-end optical fiber communication system that may be accessible during service or
in the event of a failure. The assignment of hazard level uses the AELs for the classes.
....................................................................................................................................................................................................................................
1830 PSS
1-22
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Hazard levels for optical transmission equipment are assigned in either of the following
two ways:
The actual output power from the connector or the fiber cut.
If automatic power reduction is used, the output power at the connector or fiber cut at
one second after automatic power reduction takes place, provided that maximum
output and restart conditions are met.
Classification of optical telecommunication equipment
Optical telecommunication equipment is generally classified as IEC Class 1 or

FDA/CDRH Class I, because under normal operating conditions the transmitter ports
terminate on optical fiber connectors. These are covered by a front panel to ensure
protection against emissions from any energized, unterminated transmitter.
The circuit packs themselves, however, may be IEC Class 1 or 1M or FDA/CDRH Class I
or Class IIIb. The laser class is used to determine the assignment of the hazard level.
According to IEC 60825-1 Edition 2.0 (2007) standard, Class 1 laser products are safe
under reasonably foreseeable conditions, and according to the FDA/CDRH - 21 CFR
1040 standard, Class I levels of laser radiation are not considered to be hazardous.
Alcatel-Lucent 1830 PSS WDM circuit pack classification
Classifications for the following Alcatel-Lucent 1830 PSS WDM circuit packs are IEC
Class 1M and FDA/CDRH Class IIIB:
ALPHG
AHPHG
AHPLG
CWR8
CWR8B
CWR8-88
WR8-88A
WR8-88AF
WR2-88
AM2325A
ALPFGT
AM2125A
AM2125B
AM2318A
A2P2125 Hybrid Amplifier
....................................................................................................................................................................................................................................
1830 PSS
1-23
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
MESH4
RA2P
Based on the above, individual packs are affixed with a small Hazard Level 1M label
shown in the following illustration. Additional laser safety warnings are listed on product
shelf labeling, see Figure 1-5, Multilabel (PSS-64) (p. 1-17) and Figure 1-2,
Multilabel (1830 PSS-16/PSS-32) (p. 1-14).
All other Alcatel-Lucent 1830 PSS WDM circuit packs are IEC Class 1 and FDA/CDRH
Class I and, therefore, are assigned a hazard level 1.
Alcatel-Lucent 1830 PSS TDM circuit pack and module classification
Classifications for the following Alcatel-Lucent 1830 PSS TDM circuit packs and
modules are IEC Class 1M and FDA/CDRH Class IIIB:
130SCUP
11QCUPC
24ANMB
24ET1GB
8ET1GB
10SD10G
24SDM
XS-64.2b
CFP Single Rate 10x10G over ribbon cable

X11MDTSZC
SFP+ 10GE (5/85C) over MMF
SFP+ 10GE (5/85C) over 10 km MMF
All other Alcatel-Lucent 1830 PSS TDM circuit packs are IEC Class 1 and FDA/CDRH
Class I and, therefore, are assigned a hazard level 1.
....................................................................................................................................................................................................................................
1830 PSS
1-24
Issue 1 June 2013
Safety
Equipment grounding
....................................................................................................................................................................................................................................
Equipment grounding
Importance of proper grounding
An essential aspect for both personal safety and equipment integrity is proper grounding.
To avoid differences of potential, a common ground (GRD) is used for all system part
including peripheral equipment, such as a craft terminal for example.
For safety reasons, each touchable metallic part is connected to GRD by design.
See the Alcatel-Lucent 1830 PSS Installation and System Turn-Up Guide for more
detailed information regarding grounding.
CAUTION
Electric-shock hazard
If the system is not installed in MESH-BN grounding environment but in a star grounding
scheme, all electrical cables such as LAN or timing cables can carry dangerous electrical
current on their shielding.
Take extreme care when plugging or unplugging electrical cables in installations with
star grounding. Never touch grounded parts of the system with one hand when plugging
or unplugging electrical cables with the other hand.
NOTICE
The Alcatel-Lucent 1830 PSS system is designed to permit the connection of the grounded
conductor of the DC supply circuit to the grounding conductor at the equipment.
1. This equipment must be connected directly to the DC supply system grounding
electrode conductor or to a bonding jumper from a grounding terminal bar or bus to
which the DC supply system grounding electrode conductor is connected.
2. This equipment must be located in the same immediate area (such as, adjacent
cabinets) as any other equipment that has a connection between the grounded
conductor of the same DC supply circuit and the grounding conductor, and also the
point of grounding of the DC system. The DC system shall not be grounded elsewhere.
3. The DC supply source is to be located within the same premises as this equipment.
4. There must be no switching or disconnection devices in the grounded circuit
conductor between the DC source and the point of connection of the grounding
electrode conductor.
....................................................................................................................................................................................................................................
1830 PSS
1-25
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Introduction
Electrostatic discharge (ESD), caused by touching with the hand for example, can destroy
semiconductor components. The correct operation of the complete system is then no
longer assured.
Industry experience has shown that all semiconductor components can be damaged by
static electricity that builds up on work surfaces and personnel. The electrostatic
discharge can also affect the components indirectly via contacts or conductor tracks. The
electrostatic charges are produced by various charging effects of movement and contact
with other objects. Dry air allows greater static charges to accumulate. Higher potentials
are measured in areas with low relative humidity, but potentials high enough to cause
damage can occur anywhere.
The barred-hand symbol
Circuit packs containing components that are especially sensitive to electrostatic

discharge are identified by warning labels bearing the barred-hand symbol.
....................................................................................................................................................................................................................................
1830 PSS
1-26
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
ESD instructions
NOTICE
ESD hazard
Electrostatic discharge (ESD) can permanently destroy semiconductor components.
Observe the following ESD instructions to avoid damage to electrostatic-sensitive
components:
Assume that all solid-state components and assemblies are sensitive to ESD.
Wear working garment made of 100% cotton to avoid electrostatic charging.
Touch the circuit packs at the edges or the insertion and removal facilities only.
Touch the SFP or XFP modules at the edges only.
Ensure that the rack is grounded.
Wear a properly grounded ESD wrist strap (connected to the rack ESD bonding point,
for example).
Work in an ESD safe work area or workstation. An ESD safe work area should be
equipped with a grounded ESD wrist strap and a grounded ESD mat or ESD
dissipative work surface.
A grounded ESD mat or work surface must have a ground cord with one end attached
to the mat or surface and the other end connected to a ground point (the rack ESD
bonding point, for example). Do not work with ESD sensitive devices unless the area
is properly equipped.
Conductively connect all test equipment and trolleys to the rack ESD bonding point.
Store and ship circuit packs and components in their shipping packaging. Circuit
packs and components must be packed and unpacked only at workplaces suitably
protected against build-up of charge.
Whenever possible, maintain the relative humidity of air above 20%.
NOTICE
Service-disruption hazard
At the Alcatel-Lucent 1830 PSS-32S subrack, if there is any damage on the cable jackets
(e.g. cutting or scratching due to vibration or installation) there is the risk to short cut
48VDC with RTN or GND.
Always check the cable jackets at the strain relief brackets at the Alcatel-Lucent 1830
PSS-32S power supply filters.
....................................................................................................................................................................................................................................
1830 PSS
1-27
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Electric shock
DANGER
The 4-mm banana plug at the end of the ESD wrist-strap cord is intended to be only used
for connecting to the ESD jack on the rack/subrack ESD bonding point. Connecting the
banana plug to AC or DC wall sockets or any type of power supply units may lead to the
risk of electric shock.
Never connect the banana plug to AC or DC wall sockets or any type of power supply
units.
Figure 1-6 ESD bonding point at the Alcatel-Lucent 1830 PSS-64 subrack
Legend:
A
ESD bonding point
....................................................................................................................................................................................................................................
1830 PSS
1-28
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Legend:
A
ESD bonding point
....................................................................................................................................................................................................................................
1830 PSS
1-29
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Legend:
A
ESD bonding point
....................................................................................................................................................................................................................................
1830 PSS
1-30
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Figure 1-9 ESD bonding point at the Alcatel-Lucent 1830 PSS-32S subrack
Legend:
A
ESD bonding point
....................................................................................................................................................................................................................................
1830 PSS
1-31
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Legend:
A
ESD bonding point
....................................................................................................................................................................................................................................
1830 PSS
1-32
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Figure 1-11 ESD bonding point at the ETSI One Rack
A
A
Legend:
2
ETSI One Rack bottom frame
ESD bonding point
Note: For working on ANSI installation (SNBF rack) use the ESD bonding point at
the Alcatel-Lucent 1830 PSS subrack.
....................................................................................................................................................................................................................................
1830 PSS
1-33
Issue 1 June 2013
Safety
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
To enable rapid orientation, safety instructions are given on the following pages, which
are assigned to various stages in the life cycle of the Alcatel-Lucent 1830 PSS equipment
(deployment phases).
Deployment phases
The instructions are arranged according to the following deployment phases:
Transportation (p. 1-35)
Storage (p. 1-38)
Installation (p. 1-42)
Taking into operation (p. 1-49)
Operation and maintenance (p. 1-53)
Taking out of operation (p. 1-63)
Event of failure (p. 1-66)
Contents
Transportation
1-35
Storage
1-38
Installation
1-42
1-49
1-53
1-63
Event of failure
1-66
....................................................................................................................................................................................................................................
1830 PSS
1-34
Issue 1 June 2013
Safety
Transportation
....................................................................................................................................................................................................................................
Transportation
Weight
WARNING
Risk of injury due to unsecured rack or subrack
A fully equipped Alcatel-Lucent 1830 PSS-64 subrack weighs up to 125 kg (276 lbs), a
fully equipped rack up to 215 kg (474 lbs). A fully equipped Alcatel-Lucent 1830 PSS-36
or Alcatel-Lucent 1830 PSS-32S subrack weighs up to 84.5 kg (186.3 lbs). A rack
equipped with two Alcatel-Lucent 1830 PSS-36 or Alcatel-Lucent 1830 PSS-32S subracks
weighs up to 259 kg (571 lbs). Although Alcatel-Lucent 1830 PSS-16 and Alcatel-Lucent
1830 PSS-32 subracks weigh less, a fully equipped subrack can still weigh more than
30 kg (66 lbs).
Such a fully equipped rack or subrack can cause considerable injuries if it is knocked
over or dropped.
Use a sturdy vehicle for transportation and secure the rack or subrack against dropping.
Always use a sufficient number of people and/or a lifting device to transport and position
the rack or subrack.
NOTICE
Damage to system components due to unsecured rack or subrack
A fully equipped rack or subrack can cause serious damage to the rack or subrack if it is
knocked over or dropped.
Always use a sufficient number of people or a lifting device to transport and position the
rack or subrack.
Packaging
NOTICE
Adverse effect on operation due to incorrect packaging
Dampness and soiling can cause corrosion or tracking paths which can result in
malfunctioning of the system components. Shocks can cause damage.
Protect the system components against dampness, soiling, and shocks. Use the original
dissipative packaging if possible.
....................................................................................................................................................................................................................................
1830 PSS
1-35
Issue 1 June 2013
Safety
Transportation
....................................................................................................................................................................................................................................
Environmental conditions
NOTICE
Damage to system components under extreme environmental conditions
Extreme environmental conditions can damage system components and cause
malfunctioning.
Ensure that the climatic limits for transportation and storage of Alcatel-Lucent 1830 PSS
equipment are complied with during transportation; please see Environmental
conditions for transportation (p. 1-36).
Environmental conditions for transportation
ETSI market
For the transportation phase, the requirements according to the ETSI Standard
EN 300 019-1-2, class 2.3 Public transportation are met. This class applies to
transportation where no special precautions have been taken. The conditions covered
include transportation in unventilated enclosures and in non-weather-protected conditions
with restrictions on the general open-air climates, excluding cold climates.
For quick reference, Table 1-3, Temperature and humidity levels for transportation
(ETSI market) (p. 1-36) shows the most important climatic values specified in the
requirement.
Table 1-3
Temperature and humidity levels for transportation (ETSI market)
Conditions
Limits
Low air temperature
40C (40F)
High air temperature in unventilated enclosures
70C (158F)
High air temperature in ventilated enclosures or outdoor

air
40C (104F)
Relative humidity not combined with rapid temperature

changes
95% at 45C (113F)
Relative humidity combined with rapid temperature

changes air/air
95% at 40C to 30C (40 to 86F)
Absolute humidity combined with rapid temperature

changes air/air
60 g/m3 at 70C to 15C (158 to 58F)
ANSI market
For the transportation phase, the following specifics of Telcordia Requirement

GR-63-CORE are met:
R4-3 [69]: Low-temperature exposure and shock (packaged equipment)

R4-4 [71]: High relative humidity exposure (packaged)
....................................................................................................................................................................................................................................
1830 PSS
1-36
Issue 1 June 2013
Safety
Transportation
....................................................................................................................................................................................................................................
R4-5 [70]: High-temperature exposure and thermal shock (packaged equipment)

R4-65 [107]: Category A containers (<100 kg), packaged shock/drop criteria
R4-66 [108]: Category B containers (>100 kg), shock/drop criteria
R4-67 [109]: Unpackaged shock/drop criteria

R4-83 [124]: Transportation vibration, no physical damage
For quick reference, Table 1-4, Environmental conditions for transportation (ANSI
market) (p. 1-37) shows the most important limits specified in the requirement.
Table 1-4
Environmental conditions for transportation (ANSI market)
Conditions
Limits
Low air temperature (uncontrolled humidity)
40C (40F)
Low air temperature change (uncontrolled humidity)
23C to 40C (73F to 40F) with a change rate of

30C (54F) per hour
40C to 23C (40 F to 73F) within less than 5
minutes
High air temperature (uncontrolled humidity)
70C (158F)
High air temperature change (uncontrolled humidity)
23C to 70C (73F to 158F) with a change rate of 30C

(54F) per hour
70C to 23C (158F to 73F) within less than 5 minutes
Air temperature change (at a relative humidity of 50%)

(54F) per hour
(54F) per hour

changes
93% at 40C (104F)
Relative humidity change
93% to 50% at 40C (104F) within less than 2 hours

Robustness against mechanical shocks (fully equipped

rack or subrack)
Permissible drop height for packaged equipment: 100

mm (3.9 in)
Permissible drop height for unpackaged equipment: 2.5
mm (1 in)
Vibration levels which can typically be expected during
transportation.
....................................................................................................................................................................................................................................
1830 PSS
1-37
Issue 1 June 2013
Safety
Storage
....................................................................................................................................................................................................................................
Storage
Weight
WARNING
30 kg (66 lbs).
over or dropped.
NOTICE
rack or subrack.
Electrostatic discharge (ESD)
NOTICE
ESD hazard
Electronic components can be destroyed by electrostatic discharge.
Circuit packs must therefore always be kept in antistatic covers. Use the original
dissipative packaging if possible. Always observe the ESD instructions (see Electrostatic
discharge (p. 1-26)).
....................................................................................................................................................................................................................................
1830 PSS
1-38
Issue 1 June 2013
Safety
Storage
....................................................................................................................................................................................................................................
Packaging
NOTICE
Adverse effect on operation due to incorrect packaging
Dampness and soiling can cause corrosion or tracking paths which can result in
malfunctioning of the system components. Shocks can cause damage.
Protect the system components against dampness, soiling, and shocks. Use the original
dissipative packaging if possible.
Environmental conditions
NOTICE
malfunctioning.
Ensure that the climatic limits for transportation and storage of Alcatel-Lucent 1830 PSS
equipment are complied with during storage; please see Environmental conditions for
storage (p. 1-39).
Environmental conditions for storage
ETSI market
For the storage phase, the requirements according to the ETSI Standard EN 300 019-1-1,
class 1.2 Weather-protected, not temperature-controlled storage locations are met. This
class applies to weather-protected storage having neither temperature nor humidity
control. The location may have openings directly to the open air, that means, it may be
only partly weather-protected.
For quick reference, Table 1-5, Temperature and humidity levels for storage (ETSI
market) (p. 1-39) shows the most important climatic values specified in the requirement.
The related climatogram is shown in Figure 1-12, Temperature and humidity levels for
storage (ETSI market) (p. 1-40).
Table 1-5
Temperature and humidity levels for storage (ETSI market)
Conditions
Limits
Low air temperature
25C (13F)
High air temperature
55C (131F)
Low relative humidity
10%
....................................................................................................................................................................................................................................
1830 PSS
1-39
Issue 1 June 2013
Safety
Storage
....................................................................................................................................................................................................................................
Table 1-5
Temperature and humidity levels for storage (ETSI market)

(continued)
Conditions
Limits
High relative humidity
100%
Rate of temperature change
0.5 K/min (0.9F/min)
Figure 1-12 Temperature and humidity levels for storage (ETSI market)
o
F
194
176
158
140
C
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
122
104
86
68
50
32
14
4
22
40
58
29
0.5
10
20
30
40
50
60
70
80
90
100
g-pipg-0281
Legend:
1
Air temperature
Relative air humidity [%]
Absolute air humidity [g/m3]
Conditions for storage
ANSI market
For the storage phase, the following specifics of Telcordia Requirement GR-63-CORE
are met:
R4-3 [69]: Low-temperature exposure and shock (packaged equipment)

R4-4 [71]: High relative humidity exposure (packaged)
R4-5 [70]: High-temperature exposure and thermal shock (packaged equipment)
....................................................................................................................................................................................................................................
1830 PSS
1-40
Issue 1 June 2013
Safety
Storage
....................................................................................................................................................................................................................................
For quick reference, Table 1-6, Environmental conditions for storage (ANSI market)
(p. 1-41) shows the most important limits specified in the requirement.
Table 1-6
Environmental conditions for storage (ANSI market)
Conditions
Limits
Low air temperature (uncontrolled humidity)
40C (40F)
Low air temperature change (uncontrolled humidity)
23C to 40C (73F to 40F) with a change rate of

30C (54F) per hour
40C to 23C (40 F to 73F) within less than 5
minutes
High air temperature (uncontrolled humidity)
70C (158F)
High air temperature change (uncontrolled humidity)

(54F) per hour
70C to 23C (158F to 73F) within less than 5 minutes
Air temperature change (at a relative humidity of 50%)

(54F) per hour
(54F) per hour

changes
93% at 40C (104F)
Relative humidity change

....................................................................................................................................................................................................................................
1830 PSS
1-41
Issue 1 June 2013
Safety
Installation
....................................................................................................................................................................................................................................
Installation
Risk of electric shock
WARNING
Risk of short circuits when power is supplied to the High Power Connection, Fuse &
Alarm Panel (HPCFAP) during the installation of subrack power cables. Contact with
energized parts can cause serious personal injury.
Before connecting any subrack power cables be sure that all circuit breakers that are
located in the HPCFAP are in the OFF position.
Weight
WARNING
30 kg (66 lbs).
over or dropped.
NOTICE
rack or subrack.
....................................................................................................................................................................................................................................
1830 PSS
1-42
Issue 1 June 2013
Safety
Installation
....................................................................................................................................................................................................................................
Laser warning labels
WARNING
Laser hazard
Warning labels on the system and especially on the optical components warn of the
dangers of invisible laser radiation. Removed, concealed or illegible labels can lead to
incorrect action and thus cause serious injuries to the eyes of operating staff.
Ensure that the laser warning labels are not removed or concealed and are always clearly
legible.
Acoustic noise
WARNING
Acoustic noise hazard
The operation of more than one system could cause noise levels in working environments
(for example system test floors) that are harmful to human beings.
The infrastructure of such facilities needs to take care for the protection of work force in
that environment. National laws and regulations for safe working places need to be taken
into account.
NOTICE
ESD hazard
Hold circuit packs only at the edges or on the insertion and removal facilities. Always
observe the ESD instructions (see Electrostatic discharge (p. 1-26)).
....................................................................................................................................................................................................................................
1830 PSS
1-43
Issue 1 June 2013
Safety
Installation
....................................................................................................................................................................................................................................
Condensation
NOTICE
Condensation can occur in the network element or its components during transport,
especially on moving from outside to closed rooms; this can cause malfunctioning,
short-circuits or other damages of the circuit packs.
Ensure that circuit packs and subracks have reached at least the cold start temperature of
the system and are dry before taking them into operation. The cold start temperature of
the system is 5C (+23F); see the section Climatic conditions for stationary
operation (p. 1-58).
Electric shock
DANGER
units.
Risk of pinching
CAUTION
Pinch hazard
Your fingers can be pinched when sliding in the fan unit.
Do not place your fingers on top/bottom of the fan unit when sliding it into the subrack.
....................................................................................................................................................................................................................................
1830 PSS
1-44
Issue 1 June 2013
Safety
Installation
....................................................................................................................................................................................................................................
Overcurrent protecting device
NOTICE
If the wrong type of circuit breaker is used with this equipment, the equipment may be
severely damaged due to overcurrent.
Always ensure that the Alcatel-Lucent 1830 PSS-36 subrack is installed in combination
with a Power Distribution Unit - ETSI or Power Distribution Unit - ANSI (PDU1C,
PDU2C), respectively. The circuitbreakers used in the PDU1C/PDU2C allow a maxium
current of 50 A.
Never install the Alcatel-Lucent 1830 PSS-36 subrack in combination with a High Power
Connection Fuse and Alarm Panel (HPCFAP). The circuitbreakers used in the HPCFAP
allow a maxium current of 100 A.
Over-voltage damage
NOTICE
Potential over-voltage damage to equipment from OSP (outside plant) connections
The intra-building ports of the equipment or subassembly are suitable for connection to
intra-building or unexposed wiring or cabling only. The intra-building ports of the
equipment or subassembly MUST NOT be metallically connected to interfaces that
connect to the OSP or its wiring. These interfaces are designed for use as intra-building
interfaces only (Type 2 or Type 4 ports as described in GR-1089) and require isolation
from the exposed OSP cabling. The addition of Primary Protectors is not sufficient
protection in order to connect these interfaces metallically to OSP wiring.
NOTICE
The intra-building ports of the equipment or subassembly must use shielded
intra-building cabling/wiring that is grounded at both ends.
If Type 2, 3a/5a, 4, or 4a ports of the equipment, or subassembly require a shielded cable,
intra-building ports of the equipment, or subassembly, are suitable only for connection to
shielded intra-building cabling that is grounded at both ends. This requirement applies to
paired conductor interfaces as well as coaxial interfaces.
....................................................................................................................................................................................................................................
1830 PSS
1-45
Issue 1 June 2013
Safety
Installation
....................................................................................................................................................................................................................................
NOTICE
If the wrong type of circuit breaker is used with this equipment, the equipment may be
severely damaged due to overcurrent.
Always ensure that the system is installed in combination with the correct Power
Distribution Unit - ETSI or Power Distribution Unit - ANSI (PDU1C, PDU2C),
respectively. The circuit breakers used in the PDU1C/PDU2C allow a maxium current of
50 A.
Never install the Alcatel-Lucent 1830 PSS-36 subrack in combination with a High Power
Connection Fuse and Alarm Panel (HPCFAP). The circuitbreakers used in the HPCFAP
allow a maxium current of 100 A.
....................................................................................................................................................................................................................................
1830 PSS
1-46
Issue 1 June 2013
Safety
Installation
....................................................................................................................................................................................................................................
Risk of fire due to overheating
NOTICE
Fire hazard
Inadequate heat dissipation can cause heat accumulation or even a fire in the network
element.
You must therefore ensure that:
All the required fan units are installed (Alcatel-Lucent 1830 PSS-16, Alcatel-Lucent
1830 PSS-32, Alcatel-Lucent 1830 PSS-32S, and Alcatel-Lucent 1830 PSS-36: one,
Alcatel-Lucent 1830 PSS-64: two)
The individual fans are not obstructed

That all of the following aids for cooling air flow are installed as needed for their
respective subracks:
The Alcatel-Lucent 1830 PSS-16 air deflector (left side the subrack)
The Alcatel-Lucent 1830 PSS-32/Alcatel-Lucent 1830 PSS-32S/Alcatel-Lucent

1830 PSS-36 air deflector (above the subrack)
The Alcatel-Lucent 1830 PSS-36 subrack bottom plate
The Alcatel-Lucent 1830 PSS-64 air deflector (beneath the subrack)
All empty slots are covered with the correct blank front plates; for details about the
recommended face plates for the different subrack types refer to the Product
Information and Planning Guide
The covers and cable ducts are mounted (only valid in the case of BT/BTC removal)
The dust filter is not clogged
That for Alcatel-Lucent 1830 PSS-64 the orientation of the dust filter is correct, such
that the dust filter carrier prevents the dust filter from being sucked into the fan unit
(see the Alcatel-Lucent 1830 PSS Installation and System Turn-Up Guide).
For the installation of the half-slot adapter (8DG09811AAAA), the half-slot adapter
tool (8DG07796AA) must be used to avoid short cuts during half-slot adapter
insertion and installation.
Detector diodes
NOTICE
Destruction of the detector diodes caused by too high an input power
Connecting the output and input of optical circuit packs with a transmit power in excess
of 3 dBm over short distances will cause the destruction of the detector diodes, as the
input power is then too high.
Use an optical attenuator pad of approximately 10 to 20 dB when establishing
....................................................................................................................................................................................................................................
1830 PSS
1-47
Issue 1 June 2013
Safety
Installation
....................................................................................................................................................................................................................................
connections over short distances for test purposes.

Receiver sensitivities
You can find the receiver sensitivities and the minimum overload thresholds in the
Technical Specifications chapter in the Alcatel-Lucent 1830 PSS Product Information
and Planning Guide.
....................................................................................................................................................................................................................................
1830 PSS
1-48
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................

Invisible laser radiation
WARNING
Laser hazard
Alcatel-Lucent 1830 PSS systems operate with invisible laser radiation. Laser radiation
can cause considerable injuries to the eyes.
Never look into the end of an exposed fiber or into an open optical connector as long as
the optical source is switched on. Always observe the laser warning instructions (see
Laser safety (p. 1-13)).
Acoustic noise
WARNING
into account.
Power wiring
NOTICE
Destruction of components due to incorrect power wiring
Incorrect power wiring can cause equipment damage.
All power wires must be properly connected before powering up the system by switching
on the circuit breakers. For details see Alcatel-Lucent 1830 PSS Installation and System
Turn-Up Guide.
....................................................................................................................................................................................................................................
1830 PSS
1-49
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Arcing
WARNING
Power Interface: Arcing on removing or inserting a live power supply
plug
Arcing can cause burns to the hands and damage to the eyes.
Alcatel-Lucent 1830 PSS-32, Alcatel-Lucent 1830 PSS-32S, Alcatel-Lucent 1830 PSS-36:
Before removing or connecting the power supply lugs at the Power Interface, ensure that
the line circuit breakers on the PDU1C/PDU2C are in the OFF position.
Alcatel-Lucent 1830 PSS-64: Before removing the power supply cable at a Power Supply,
Filter, and Clock Interface Card (PSF3T8), ensure that all associated circuit breakers
that are located in the external High Power Connection, Fuse & Alarm Panel (HPCFAP)
are in the OFF position.
....................................................................................................................................................................................................................................
1830 PSS
1-50
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Electric shock
DANGER
Alcatel-Lucent 1830 PSS-36: If the system is operated with only one Power Interface
Card (PFC), electrical connectors on the backplane carry a voltage of 48 V DC which
can cause electric shocks if accidentally touched.
Alcatel-Lucent 1830 PSS-64: If the system is operated with only one Power Supply,
Filter, and Clock Interface Card (PSF3T8) and Fan Unit (FAN3T8), electrical connectors
on the backplane carry a voltage of 48 V DC which can cause electric shocks if
accidentally touched.
Always use the correct system configuration to ensure safe operation:
Alcatel-Lucent 1830 PSS-36: Two Power Interface Cards (PFC), one Fan module
Alcatel-Lucent 1830 PSS-64: Two Power Supply, Filter, and Clock Interface Cards
(PSF3T8), two Fan Units (FAN3T8).
Alcatel-Lucent 1830 PSS-16, Alcatel-Lucent 1830 PSS-32, Alcatel-Lucent

1830 PSS-32S: Two PFDC DC Power Filters of the appropriate capacity.
Supply voltage
NOTICE
Destruction of components due to a supply voltage of incorrect polarity or
too high
Alcatel-Lucent 1830 PSS equipment operates at a nominal voltage of 48 V (40.5 V to
57 V) or 60 V (50.0 V to 72.0 V) . A supply voltage outside these specifications or of
incorrect polarity can lead to permanent damage of system components.
Ensure that the supply voltage has the correct range and polarity before connecting the
voltage. Ensure also the correct polarity (sequence) of both power feeders.
....................................................................................................................................................................................................................................
1830 PSS
1-51
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Fusing
NOTICE
Fire hazard
If the system is not secured by appropriate circuit breakers, a short-circuit can cause
severe damage to the system, for example a fire in the network element.
Protect all supply lines with line circuit breakers matched to the load of the subrack
equipment. Note the relevant guide values in the Alcatel-Lucent 1830 PSS Installation
and System Turn-Up Guide.
Condensation
NOTICE
Condensation can occur in the network element or its components during transport,
especially on moving from outside to closed rooms; this can cause malfunctioning,
short-circuits or other damages of the circuit packs.
Ensure that circuit packs and subracks have reached at least the cold start temperature of
the system and are dry before taking them into operation. The cold start temperature of
the system is 5C (+23F); see the section Climatic conditions for stationary
operation (p. 1-58).
....................................................................................................................................................................................................................................
1830 PSS
1-52
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................

WARNING
Laser hazard
Arcing
WARNING
plug
....................................................................................................................................................................................................................................
1830 PSS
1-53
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Electric shock
DANGER
Alcatel-Lucent 1830 PSS-36: If the system is operated with only one Power Interface
Card (PFC), electrical connectors on the backplane carry a voltage of 48 V DC which
can cause electric shocks if accidentally touched.
Alcatel-Lucent 1830 PSS-64: If the system is operated with only one Power Supply,
Filter, and Clock Interface Card (PSF3T8) and Fan Unit (FAN3T8), electrical connectors
on the backplane carry a voltage of 48 V DC which can cause electric shocks if
accidentally touched.
Always use the correct system configuration to ensure safe operation:
Alcatel-Lucent 1830 PSS-36: Two Power Interface Cards (PFC), one Fan module
Alcatel-Lucent 1830 PSS-64: Two Power Supply, Filter, and Clock Interface Cards
(PSF3T8), two Fan Units (FAN3T8).
Alcatel-Lucent 1830 PSS-16, Alcatel-Lucent 1830 PSS-32, Alcatel-Lucent

1830 PSS-32S: Two PFDC DC Power Filters of the appropriate capacity.
Laser warning labels
WARNING
Laser hazard
Warning labels on the system and especially on the optical components warn of the
dangers of invisible laser radiation. Removed, concealed or illegible labels can lead to
incorrect action and thus cause serious injuries to the eyes of operating staff.
Ensure that the laser warning labels are not removed or concealed and are always clearly
legible.
Acoustic noise
WARNING
into account.
....................................................................................................................................................................................................................................
1830 PSS
1-54
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Risk of burns due to hot surfaces
CAUTION
Hot-surface hazard
Hot surfaces of system components can cause burns to the hands.
Do not touch system components that are marked with the hot surfaces warning label.
NOTICE
ESD hazard
Electric shock
DANGER
units.
Risk of pinching
CAUTION
Pinch hazard
Do not place your fingers on top/bottom of the fan unit when sliding it into the subrack.
....................................................................................................................................................................................................................................
1830 PSS
1-55
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Risk of fire due to overheating
NOTICE
Fire hazard
Inadequate heat dissipation can cause heat accumulation or even a fire in the network
element.
You must therefore ensure that:
All the required fan units are installed (Alcatel-Lucent 1830 PSS-16, Alcatel-Lucent
1830 PSS-32, Alcatel-Lucent 1830 PSS-32S, and Alcatel-Lucent 1830 PSS-36: one,
Alcatel-Lucent 1830 PSS-64: two)
The individual fans are not obstructed

That all of the following aids for cooling air flow are installed as needed for their
respective subracks:
The Alcatel-Lucent 1830 PSS-16 air deflector (left side the subrack)
The Alcatel-Lucent 1830 PSS-32/Alcatel-Lucent 1830 PSS-32S/Alcatel-Lucent

1830 PSS-36 air deflector (above the subrack)
The Alcatel-Lucent 1830 PSS-36 subrack bottom plate
The Alcatel-Lucent 1830 PSS-64 air deflector (beneath the subrack)
All empty slots are covered with the correct blank front plates; for details about the
recommended face plates for the different subrack types refer to the Product
Information and Planning Guide
The covers and cable ducts are mounted (only valid in the case of BT/BTC removal)
The dust filter is not clogged
That for Alcatel-Lucent 1830 PSS-64 the orientation of the dust filter is correct, such
that the dust filter carrier prevents the dust filter from being sucked into the fan unit
(see the Alcatel-Lucent 1830 PSS Installation and System Turn-Up Guide).
For the installation of the half-slot adapter (8DG09811AAAA), the half-slot adapter
tool (8DG07796AA) must be used to avoid short cuts during half-slot adapter
insertion and installation.
Risk of system shut-down during maintenance activities
NOTICE
System shut-down when switching off all power supply feeders
Bringing the circuit breakers of all power supply feeders in the OFF position leads to a
shut-down of the complete system.
Alcatel-Lucent 1830 PSS-64: When carrying out maintenance work at one of the two
Power Supply, Filter, and Clock Interface Cards (PSF3T8) A or B, switch off only those
....................................................................................................................................................................................................................................
1830 PSS
1-56
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
circuit breakers that are directly associated to the corresponding PSF3T8. For each
PSF3T8 there are three power supply feeders, and each power supply feeder has an
associated circuit breaker. The circuit breakers are located in the High Power
Connection, Fuse & Alarm Panel (HPCFAP).
Risk of equipment damage during maintenance activities
NOTICE
Equipment can be damaged during in-service replacement of components
Alcatel-Lucent 1830 PSS-36: During in-service replacement of system components above
the Fan Unit, there is a risk that nuts, cable ends, or other objects may fall into the Fan
Unit.
Alcatel-Lucent 1830 PSS-64: During in-service replacement of the upper Power Supply,
Filter, and Clock Interface Card (PSF3T8) A, there is a risk that nuts, cable ends, or other
objects may fall into the upper fan tray (Fan Unit A).
Take utmost care to prevent nuts or cable ends from falling into the system.
Detector diodes
NOTICE
Destruction of the detector diodes caused by too high an input power
Connecting the output and input of optical circuit packs with a transmit power in excess
of 3 dBm over short distances will cause the destruction of the detector diodes, as the
input power is then too high.
Use an optical attenuator pad of approximately 10 to 20 dB when establishing
connections over short distances for test purposes.
Receiver sensitivities
You can find the receiver sensitivities and the minimum overload thresholds in the
Technical Specifications chapter in the Alcatel-Lucent 1830 PSS Product Information
and Planning Guide.
....................................................................................................................................................................................................................................
1830 PSS
1-57
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Short-circuit
NOTICE
Destruction of circuit packs in the event of a short-circuit
A short-circuit in the network element can cause destruction of electronic components
and thus malfunctioning of the complete system.
You must therefore not handle objects such as a screwdriver in the circuit pack area of the
subrack.
Alcatel-Lucent 1830 PSS-36: Always use the special extraction tool for the insertion and
the removal of bus termination cards.
Climatic conditions
NOTICE
malfunctioning.
Ensure that the Climatic conditions for stationary operation (p. 1-58) are complied
with during operation.
Climatic conditions for stationary operation
The cold start temperature of the Alcatel-Lucent 1830 PSS is 5C (+23F).

ETSI market
For the stationary operation phase, the requirements according to the ETSI Standard EN
300 019-1-3, class 3.1E, Temperature-controlled location with exceptional conditions
are met. This class applies to a permanently temperature-controlled enclosed location.
Humidity is usually not controlled.
For quick reference, Table 1-7, Temperature and humidity levels for operation (ETSI
market) (p. 1-59) shows the most important climatic values specified in the requirement.
The related climatogram is shown in Figure 1-13, Temperature and humidity levels for
operation (ETSI market) (p. 1-60).
....................................................................................................................................................................................................................................
1830 PSS
1-58
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Table 1-7
Conditions
Limits
Rack level (Alcatel-Lucent 1830 PSS-64)
Subrack level (Alcatel-Lucent

1830 PSS-36)
Minimum air temperature
Maximum air temperature
Normal operating:
Normal operating:
5C (41F)
5C (41F)
Short term (extended):
5C (28F)
5C (28F)
Normal operating:
Normal operating:
40C (104F)
45C (113F)
50C (122F)
55C (131F)
Low relative humidity
5%
High relative humidity
85% (90% for short term)
0.5 K/min (0.9F/min)
Figure 1-13 Temperature and humidity levels for operation (ETSI market)
o
140
60
122
50
104
40
86
30
68
20
50
10
32
14
10
20
22
30
25
20
1.5
1.0
10
20
30
40
50
60
70
80
90
100
1
2
g-pipg-0282
....................................................................................................................................................................................................................................
1830 PSS
1-59
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Legend:
1
Air temperature
Values outside of this field have a probability of occurrence of less than 10%
Normal operating conditions: values outside of this field have a probability of occurrence of less than 1%
Exceptional climatic limits
ANSI market
For the stationary operation phase, the following specifics of Telcordia Requirement
GR-63-CORE are met:
R4-6 [72]: Ambient temperature and humidity limits as shown in Table 1-8,
Temperature and humidity levels for operation (ANSI market) (p. 1-60) and Figure
1-14, Temperature and humidity levels for operation (ANSI market) (p. 1-61)
R4-8 [74], R4-9 [136], R4-10 [75]: Requirements for altitude
R4-68 [110], R4-69 [111], R4-70 [112], R4-72 [114], R4-75 [117], R4-81 [122],
R4-82 [123]: Requirements for dynamic shock, vibration, and earthquake. The chassis
resistance of Alcatel-Lucent 1830 PSS is compliant with zone 4 earthquake and office
vibrations.
Table 1-8
Conditions

Limits
Rack level (Alcatel-Lucent 1830 PSS-64)
Subrack level (Alcatel-Lucent

1830 PSS-36)
Ambient1 temperature
Range
Range
Operating (up to 1800 m)
5C to 40C (41F to 104F)
5C to 45C (41F to 113F)
Short-term2
5C to 50C (23F to 122F)
5C to 55C (23F to 131F)

1
30 K/h (54F/min)
Ambient relative humidity
Range
Operating
5% to 85%
Short-term
5% to 90%, but not to exceed 0.024 kg water/kg of dry air
....................................................................................................................................................................................................................................
1830 PSS
1-60
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Notes:
1.
Ambient refers to conditions at a location 1.5 m (59 in) above the floor and 400 mm (15.8 in) in front of
the equipment.
2.
Short-term refers to a period of not more than 96 consecutive hours and a total of not more than 15 days in
1 year. This refers to a total of 360 hours in any given year, but no more than 15 occurrences during that
1-year period. The long-term operating temperature range is 0C to 40C (32F to 104F) on rack level and
0C to 45C (32F to 113F) on shelf level (see Frame/Shelf level according to Telcordia and ETSI
(p. 1-61)). It is given for the purposes of reliability assessment.
Figure 1-14 Temperature and humidity levels for operation (ANSI market)
o
158
70
140
60
122
50
104
40
86
30
68
20
50
10
32
14
10
24
10
20
30
40
50
60
70
80
90
100
g-pipg-0280
Legend:
1
Air temperature
Normal operating conditions
Short-term conditions
Frame/Shelf level according to Telcordia and ETSI
The following describes the Frame/Shelf level according to Telcordia and ETSI
Telcordia frame-level (subrack is more than 36 [=914.4 mm] in height)

All Telcordia GR-63-CORE environmental conditions apply to a 12" or 14 deep
SNBF (ANSI rack) with one installed subrack (Alcatel-Lucent 1830 PSS-64),
including subrack covers.
Telcordia shelf-level (subrack is less than or equal to 36 [=914.4 mm] in height)
....................................................................................................................................................................................................................................
1830 PSS
1-61
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
All Telcordia GR-63-CORE environmental conditions apply to a stand-alone subrack

(Alcatel-Lucent 1830 PSS-36). For certain tests the subrack may have to be mounted
into an open rack.
ETSI rack-level
All ETSI EN 300 019 environmental conditions apply to a 300 mm ETSI rack with
one installed subrack (Alcatel-Lucent 1830 PSS-64), including optional rack doors
and side-panels.
ETSI subrack-level
All ETSI EN 300 019 environmental conditions apply to a stand-alone subrack
(Alcatel-Lucent 1830 PSS-36). For certain tests the subrack may have to be mounted
into an open rack.
....................................................................................................................................................................................................................................
1830 PSS
1-62
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................

WARNING
Laser hazard
Arcing
WARNING
plug
....................................................................................................................................................................................................................................
1830 PSS
1-63
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
Weight
WARNING
30 kg (66 lbs).
over or dropped.
NOTICE
rack or subrack.
Risk of burns due to hot surfaces
CAUTION
Hot-surface hazard
....................................................................................................................................................................................................................................
1830 PSS
1-64
Issue 1 June 2013
Safety
....................................................................................................................................................................................................................................
NOTICE
ESD hazard
Electric shock
DANGER
units.
Disposal
The equipment in the Alcatel-Lucent 1830 PSS system series must be disposed of at the
end of its lifetime. Please contact us in this case and we will arrange for proper and
environment-friendly disposal of your equipment (most parts of the system can be
recycled).
....................................................................................................................................................................................................................................
1830 PSS
1-65
Issue 1 June 2013
Safety
Event of failure
....................................................................................................................................................................................................................................
Event of failure
Hazard levels
In the event of failure, the hazard levels given in the Alcatel-Lucent 1830 PSS Product
Information and Planning Guide apply. The hazard levels define the potential optical
hazard at any accessible location within an optical fiber telecommunication system. See
Alcatel-Lucent 1830 PSS Product Information and Planning Guide.
WARNING
Laser hazard
....................................................................................................................................................................................................................................
1830 PSS
1-66
Issue 1 June 2013
S2ecurity administration
procedures
Overview
Purpose
This chapter describes the security administration tasks.

Contents
Security management and user administration on the OCS
application
2-5
2-6
Security concepts
2-7
User provisioning
2-13
Security management and user administration on the WDM

application
2-14
User accounts and privileges
2-15
2-20
Login sessions
2-24
2-26
Authentication
2-35
Administer user logins on the OCS application using the

Alcatel-Lucent 1830 PSS ZIC
2-40
Procedure 2-1: Create a user login
2-42
Procedure 2-2: Set system-wide user security parameters
2-45
Procedure 2-3: Display system-wide user security parameters
2-49
System-wide user security parameters
2-50
Procedure 2-4: Delete a user login
2-52
Procedure 2-5: Inhibit a user login
2-53
...................................................................................................................................................................................................................................
1830 PSS
2-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 2-6: Allow a user login
2-54
Procedure 2-7: Display user property information
2-55
Procedure 2-8: Edit user logins
2-56
Procedure 2-9: Log off user
2-59
Procedure 2-10: Retrieve information on all active user logins
2-60
2-61
Procedure 2-12: Send a short free form text message to other users
2-63
Procedure 2-13: Modify command access security level assigned to a TL1

command.
2-65
Procedure 2-14: Display command access security level assigned to a TL1

command
2-67
Command access security level assigned to a TL1 command
2-68
Procedure 2-15: Copy security sensible files or data from/to an NE to/from a

remote file server
2-69
Security File Transfer
2-73
Procedure 2-16: Configure SSL authentication for ZIC to NE communication

(high-level procedure)
2-75
2-76
2-77
2-79
2-80
2-81
2-82
2-83
2-86
2-88
2-90
User management and administration procedures on the WDM

application using the WebUI
2-91
Procedure 2-25: Create a user
2-93
2-94
Procedure 2-26: View or modify user details
2-97
2-98
Procedure 2-27: Delete a user
2-99
....................................................................................................................................................................................................................................
1830 PSS
2-2
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
2-100
Procedure 2-29: View / terminate sessions
2-101
The Sessions screen
2-102
Procedure 2-30: View SNMP v3 users
2-104
Procedure 2-31: Create SNMP v3 user
2-105
Procedure 2-32: Modify SNMP v3 user
2-106
2-107
Procedure 2-33: View / modify system security attributes
2-108
2-109
Syslog Administration
2-110
2-111
CLI Logging
2-112
Procedure 2-36: Setting / viewing SNMP user activity logging properties
2-113
SNMP Logging
2-114
Procedure 2-37: View security log
2-115
2-116
2-117
The All Logs screen
2-118
Procedure 2-39: Save a retrieved log to a file
2-119
2-120
User Preferences
2-121
2-122
Create RADIUS Server
2-123
Procedure 2-42: View/modify RADIUS server
2-124
Modify RADIUS Server
2-125
2-126
2-127
RADIUS Properties
2-128
2-129
2-130
2-131
Procedure 2-47: View trap destinations
2-132
2-133
....................................................................................................................................................................................................................................
1830 PSS
2-3
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 2-48: View/modify community strings
2-135
2-136
....................................................................................................................................................................................................................................
1830 PSS
2-4
Issue 1 June 2013

Overview
application
....................................................................................................................................................................................................................................
Security management and user administration on

the OCS application
Overview
Purpose
This section provides descriptive information concerning the Alcatel-Lucent 1830 PSS
Security management and user administration on the OCS application.
Contents
2-6
Security concepts
2-7
User provisioning
2-13
....................................................................................................................................................................................................................................
1830 PSS
2-5
Issue 1 June 2013

application
....................................................................................................................................................................................................................................

Overview
User administration comprises the following:
Creating, modifying, or deleting user logins,

Specifying associated passwords,
Assigning access privileges,
Enabling users
Disabling users,
Logging out users,

Viewing user details.
User permission
Administration on the security databases can only be performed by a security

administrator, that means a super user login is required.
....................................................................................................................................................................................................................................
1830 PSS
2-6
Issue 1 June 2013

Security concepts
application
....................................................................................................................................................................................................................................
Security concepts
Overview
Alcatel-Lucent 1830 PSS uses logins, passwords, authentication, and access levels to
protect against unauthorized access. It also keeps a security log.
RADIUS server support for user authentication
Remote Authentication Dial In User Service (RADIUS) provides a centralized way of

user login/authentication and management. A RADIUS server is an external entity
(server) that keeps a centralized database of user login, password and privilege
information. Each NE in the network acts as RADIUS client and delegates user
authentication to the RADIUS server.
For resiliency purposes, the NE supports a primary and a secondary RADIUS server.
After the maximum of retries per server is reached on the primary server a connection to
the secondary server is attempted. Special local (maintenance) accounts can be optionally
activated by the customer for troubleshooting in case that RADIUS is not available.
Successful and unsuccessful access attempts via RADIUS are logged (SECULOG). The
information of the log follows User Activity Log (UAL) principles. In case that local
accounts are also configured as RADIUS backup, the access attempts through these
accounts are also logged.
RADIUS allows the optional use of the MD5 hashing algorithm to encrypt the
User-Password and other attributes such as Tunnel-Password.
NTP server authentication
The NTPv4 protocol supports authentication using either symmetric key or public key
cryptography. Alcatel-Lucent 1830 PSS implements authentication using the symmetric
key cryptography feature. This method ensures an unbroken chain of trust between the
client system and the primary servers at the root of the timing distribution network. This
chain is known as the provenance of the client. The protocol provides the credentials to
ensure that the source of the timing signal is not being spoofed since the attacker does not
have the cryptographic key information to provide authentic credentials.
When authentication is in use, every message contains a message authentication code
(MAC) appended to the NTP header in the message. The MAC is calculated using a
cryptographic hashing algorithm (in the form of SHA-1 or MD5) to produce a
mathematical fingerprint that uniquely identifies each message. The hashing algorithm
used is up to the user. Under the symmetric key method, both the server and the client
share a key, that is distributed outside this protocol. The server uses the key to create the
MAC. When the message arrives, the client uses the key to create its own version of the
....................................................................................................................................................................................................................................
1830 PSS
2-7
Issue 1 June 2013

Security concepts
application
....................................................................................................................................................................................................................................
MAC. The client then compares its calculation to the MAC inserted in the message.
When the two codes match the client concludes that the message was indeed sent from
the intended server.
User identifiers
Alcatel-Lucent 1830 PSS users are required to log in with a user identifier and a password
at the start of a session. To ensure security, they should log out at the end of a session. If a
user is inactive for a configurable period of time, the user is logged off automatically.
This period can be set up by the administrator in a range from 0 to 999 min. The default
value is 60 min.
The system supports up to 512 different user IDs. The user management is performed by
a user with administrative privileges. User management includes addition and deletion of
users as well as assigning privileges to them. Multiple logins with the identical user
identifier will be denied.
Alcatel-Lucent 1830 PSS has five pre-installed default users for external TL1 login which
cannot be deleted: SERVICE, EML001, EML002, USER05, and Unprvlgd.
For internal purposes Alcatel-Lucent 1830 PSS supports the following default users
which cannot be deleted: WDMUSER1, ZICUSR, OMSREAD{1,2},
OMSPROV{1,2}, OMSCONF{1,2}, OMSNETADMIN{1,2}, and
OMSSEC{1,2}.
The SERVICE user allows an Alcatel-Lucent technician to log-in to the NE. The initial
password for this user is contained in the persistent database and can be modified. The
User Security Level of this user is 5, as well any security administrator user. The
SERVICE user cannot be deleted, but can be disabled and enabled.
The ZICUSR is for internal use only and cannot be used for logins from outside.
User identifiers that are strings of 5 to 12 case-sensitive alphanumeric characters where
the first character is an alphabetic character. The following special characters are also
valid: % (percent), + (plus sign), # (number sign), and _ (underscore).
Dormant account management
Dormant accounts are those users that have not logged on for a period of time. A user
with sufficient security privileges is able to provision per User ID a User ID aging
interval expressed in days. At the end of this interval, a User ID is disabled and inhibited
from logging in if during this interval it has never been used to login. The longest interval
allowed is 999 days with a minimum of 1 day. The default for the system-wide user
identifier aging interval is 60 days.
The system allows to disable the User ID aging per user by setting the User ID aging
interval to 0. After a user's User ID has been disabled, the system allows a privileged user
to reactivate (enable) the disabled User ID.
....................................................................................................................................................................................................................................
1830 PSS
2-8
Issue 1 June 2013

Security concepts
application
....................................................................................................................................................................................................................................
The system resets the User ID aging interval per user when
the User ID aging interval changes
the user account is created

the user logs in to the system
the user is enabled by a privileged user after the User ID has been disabled
User ID aging is not applicable to system default users and super users.
User community authorization level (UCAL)
The system supports user privilege categories for accessing functionality on the system.
A user community authorization level (UCAL) is assigned to each user ID by the
administrator when the user ID is created. This numerical value between 1 and 5 defines
the access privileges for the user. A user community authorization level of 5 stands for
administrative privileges.
For each possible transaction with the system, that means for each TL1 command, a
command community authorization level (CCAL) is defined. A user can only perform a
transaction if his or her UCAL is greater or equal to the CCAL of the transaction.
A super user (that means a system administrator with security administration privileges,
indicated by UCAL equal to 5) is able to:
Add users to the NE

Delete users from the NE
Edit the security information of any user

Retrieve security information about users (not password)
Change the password of other users without entering the old password
Logoff a particular user (included a User with security administration privileges)

Obtain user info about the user currently logged on to the NE
Inhibit and allow users
Set system wide user security attributes

Retrieve security information about authenticated (logged on) and unauthenticated
(not logged on) sessions
Set command privilege partitioning

Do anything that a normal user can do
A normal user (that means a user without administration privileges, indicated by UCAL
less than 5) is able to:
Establish a session with the NE (logon)

Change own user password
Obtain own user info
....................................................................................................................................................................................................................................
1830 PSS
2-9
Issue 1 June 2013

Security concepts
application
....................................................................................................................................................................................................................................
Retrieve system wide user security attributes

Retrieve command privilege partitioning
Terminate the session (logoff)
Execute accessible/privileged NE command language requests
Passwords
A password is a case-sensitive string of 8 to 12 alphanumeric characters with at least three

of the following: at least one uppercase alphabetic character, at least one lowercase
alphabetic character, at least one numeric character, at least one special character. The
following special characters are valid: % (percent), + (plus sign), # (number sign),
_ (underscore), ! (exclamation mark), @ (at sign), $ (dollar sign), (double
quotation mark), & (ampersand), '(apostrophe), ( (left parenthesis), ) (right
parenthesis), * (asterisk), and . (period). The first character of the password can be
any alphabetic, numeric, or a valid special character.
The password must not have more than 3 consecutive identical characters, for example,
User_00001 will be denied. The password must not be the same as the associated user
ID. The password must not be the reverse of the associated user ID. More than one user
can have the same password.
All passwords are stored and transported only encrypted throughout Alcatel-Lucent
1830 PSS and the management systems.
If specified by the administrator, users can change their own passwords at their discretion,
following a configurable minimum interval since the last change.
Password aging can be configured. The system notifies in advance and, upon expiration,
forces users to change their passwords by the following actions:
The system informs the user when the password expiry date is nearly reached. Default
is 7 days before the expiration.
The system forces the user to enter a new password at the login attempt after
password expiration, if the user has the ability to change the password.
For a user updating a password, there is a specified minimum period of waiting before
an existing password can be updated.
For a user updating a password, the system does not allow the reuse of a specified
number of most recently used passwords. This discourages password flipping.
Access control lists for IP addresses and ports
The Alcatel-Lucent 1830 PSS system supports the configuration of access control lists
(ACL) or filters to limit the access to the administration and other management protocols
only to certain ranges of authorized source IP addresses and ports. It is also possible to
configure multiple disjoint ranges specified through IP network and mask. IP access
....................................................................................................................................................................................................................................
1830 PSS
2-10
Issue 1 June 2013

Security concepts
application
....................................................................................................................................................................................................................................
control lists can be configured for filtering traffic, which is forwarded by the network
element. One use-case for this is to prevent attacks to the network from hijacked CPE
boxes.
Firewall traversal
The NE or the underlying protocols used by the NE do not pose any restriction for
firewalls in the management or control plane. For instance:
Firewall-friendly protocols are used

Server ports are on server side
The number of server ports is reduced to a small range and documented
System log
The NE maintains a system log with a size of up to 50 MB. Among all other commands
and responses, also the ones related to security are stored. A filter capability is available
to retrieve only security events. The events/responses are kept in a non-volatile memory.
The log can be retrieved from the NE. The logs are stored in a file that can be retrieved by
the management system via SFTP, to optimize bandwidth and simplify the request
mechanism.
Secure shell
Alcatel-Lucent 1830 PSS provides a way to secure the traffic between the operator and
the network element with strong encryption and cryptographic protection to provide
confidentiality, integrity, and replay protection. The system supports secure shell 2
(SSH-2) encryption for TL1 communication, also on the debug port.
For host authentication, Alcatel-Lucent 1830 PSS supports the following:
Initialization of the supported public key
Distribution of the supported public key

Retrieval of the fingerprint (a cryptographic hashing of the supported public key)
Alcatel-Lucent 1830 PSS supports secure file transfers from and to other hosts.
NE-NE and NMS-GNE IPoIP (IP over IP) tunneling
Alcatel-Lucent 1830 PSS supports tunneling IP packets through an IP network (IP in IP

Tunnels, IPIPT). So the NEs can interconnect management systems and NEs via an
out-of-band (OoB) DCN, which is managed as an independent IP routing domain or
control plane nodes can build out-of-band protection links for in-band (ECC) links used
by the control plane. The transport part is accomplished by encapsulating IP datagrams in
IP packets and route them through an IP tunnel on the OoB DCN to the node that
....................................................................................................................................................................................................................................
1830 PSS
2-11
Issue 1 June 2013

Security concepts
application
....................................................................................................................................................................................................................................
represents their next-hop IP address towards their destination. IP-in-IP encapsulation

according to RFC 2003is supported. IP-in-GRE-in-IP encapsulation according to RFC
2784is supported.
Inter-compound communication
The NE internal communication security applies for multi-shelf network elements with
compound architecture. Inter-compound communication is required when uplink cards
are successfully provisioned in the OCS compound . The system provides a default user
for TL1 based communication between the WDM application and the OCS application.
Only one session at a time is allowed for this user. The list of allowed IP addresses can be
set for this user to allow only logins from the IP address of the WDM compound.
SSL/TLS
The Alcatel-Lucent 1830 PSS system supports SSL/TLS secured HTML communication
for access of the Alcatel-Lucent 1830 PSS ZIC . All communication associated with
Alcatel-Lucent 1830 PSS ZIC uses separate SSL/TLS connections.
Host-to-host authentication between the NMS and the NE, and between the ZIC and the
NE is done using a certificate distribution based on SSL. The Alcatel-Lucent 1830 PSS
system supports a management for the certificates that are used by SSL and TLS for
server authentication.
Secure mode for open ports
The Alcatel-Lucent 1830 PSS system is configured in a way that non-essential ports and
services are avoided:
Only logical ports that are needed to manage the equipment are open
Only physical ports that are needed to manage the equipment are open
Ports needed for example for debug access are only opened on user request.
All logical ports are secure interfaces (SSH, SSL/TLS or SFTP).

User activity logs
The Alcatel-Lucent 1830 PSS system supports user activity logs (UAL, also known as
command logs) that are compatible with the Alcatel-Lucent 1350 OMS format:
The Alcatel-Lucent 1350 OMS user is supported in the UAL: The logs report the
name of Alcatel-Lucent 1350 OMS user as configured
File transfer of UAL: The logs are transferred from the NE to the Alcatel-Lucent
1350 OMS via SFTP.
....................................................................................................................................................................................................................................
1830 PSS
2-12
Issue 1 June 2013

User provisioning
application
....................................................................................................................................................................................................................................
User provisioning
Predefined user profiles
Table 2-1
Default User
USER05
EML001
EML002
Unprvlgd
Default Password
identifier
ADMIn005
Eml__001
Eml__002
Only4ReadXX
Default User Profiles for internal purpose
The users described here are intended for NE internal communication purposes. They are
all used internally and not configureable.
Table 2-2
Default user types for internal purpose
Default User
for OMS
for ZIC
for WDM
compound
OMSREAD1
ZICUSR
WDMUSER1
OMSREAD2
OMSPROV1
OMSPROV2
OMSCONF1
OMSCONF2
OMSNETADMIN1
OMSNETADMIN2
OMSSEC1
OMSSEC2
The OMS user for OMS accessing the ZIC.

The ZICUSR is used for the internal ZIC server to establish a TL1 user session via the
TCP/IP protocol stack in order to support TL1 transaction-oriented messages between the
server and the NE.
The system provides the default user WDMUSER1 for TL1 based communication between
the WDM compound and the OCS compound
....................................................................................................................................................................................................................................
1830 PSS
2-13
Issue 1 June 2013

Overview
application
....................................................................................................................................................................................................................................
Security management and user administration on

the WDM application
Overview
Purpose
This section provides descriptive information concerning the Alcatel-Lucent 1830 PSS
Security management and user administration on the WDM application.
Contents
2-15
2-20
Login sessions
2-24
2-26
Authentication
2-35
....................................................................................................................................................................................................................................
1830 PSS
2-14
Issue 1 June 2013

application
....................................................................................................................................................................................................................................

The purpose of security administration is to manage user accounts (logins, passwords,
authorization levels, external links) and to monitor system security so that only valid
users can perform permitted actions and receive authorized information from the system.
The NE provides the ability to create, modify, delete, and view user profiles and
associated security levels. Each level has distinct privileges for accessing and executing
the commands and performing administrative functions on the NE. The description of
each function or command is listed in the Alcatel-Lucent 1830 Photonic Service Switch
(PSS) Release 6.0 Command Line Interface Guide and/or Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 6.0 Photonics TL1 Command Guide including the user
levels that are able to access and execute each specific command (see System access
control (p. 2-30)).
The system does not provide an unsecure user external port. To gain access to an NE
you need a user account with login and password. The user account name, privilege level
and password is created and defined by the Admin user, and is unique for each network
element in the network.
Important! The Alcatel-Lucent 1830 PSS is delivered with two default users as part
of the factory software load: one Admin user (with administration privilege) and one
Service user (with service privilege).
The login ID and passwords are:
For Admin user: admin/admin
For Service user: service/AlcaLu-1830!
Note: The administration of all security functions is only accessible to Admin and
Service users (i.e. the system will only allow access to these security functions to
users with appropriate security administration privileges). The Service user is not
capable of creating/deleting/modifying user profiles. The NE does not allow deletion
of the default users.
....................................................................................................................................................................................................................................
1830 PSS
2-15
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
The user levels, the privileges assigned to each level, and their intended use are
summarized in Table 2-3, User privilege levels (p. 2-16).
Table 2-3
User privilege levels
Level
Privileges and use
Service
This is the highest level, and is meant for Alcatel-Lucent

technicians. This user has all the Admin privilege (except the
ability to create/delete/modify user profiles), plus the ability to
utilize the debugging and software development tools. The
following applies:
Admin
a maximum of one Service user per NE, created by default, as

part of the SW load. (There is no mechanism to create another
Service user profile or to delete the Service user profile). Only
the Service user can change his/her password
The Admin user can peform all functions accessible via WebUI,
CLI and TL1. The Admin user cannot utilize debugging and
software development tools.
....................................................................................................................................................................................................................................
1830 PSS
2-16
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Table 2-3
(continued)
Level
Privileges and use
Provisioner
The WebUI restricts access for a user with Provisioner privilege

level as follows:
A Provisioner user cannot access the following Administrative

functions: User Panel Replacement, Security (with exceptions
below), SNMP, Syslog, Power Commissioning and GMRE
Commissioning.
For the following administrative functions, the Provisioner user

can view the current values, but cannot edit them:
Date/Time and Timezone
System-wide security settings
NTP settings
Database backup/restore
Software upgrade, including Software NE and FTP server

settings
The users own user profile
List of user sessions
GMRE settings, Feasibility file transfer
Access Control Lists
Log file transfer
Technology Types
For the following administrative functions, the Provisioner user

can view and edit:
IP routes
OSPF areas
Change his own password
User Preferences
Ping and Traceroute
A Provisioner user cannot do the following:
A Provisioner user cannot perform a system reboot.
A Provisioner user cannot perform a card-level cold reboot.
A Provisioner user cannot modify OPSA A and B port

switching attributes.
A Provisioner user cannot view the Security Log.
A Provisioner user cannot modify LD/OSCT SIG and LINE

port attributes
A Provisioner user cannot modify Power Management port

attributes
A Provisioner user cannot modify Dynamic Tilt Adjustment
....................................................................................................................................................................................................................................
attributes
1830 PSS
2-17
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Table 2-3
(continued)
Level
Privileges and use
Provisioner (continued)
A Provisioner user cannot view or modify Optical Intrusion

Detection parameters
A Provisioner user cannot modify Per-Channel Target Power

Offset attributes
A Provisioner user cannot modify Target Power Offset

attributes
A provisioner user cannot modify or view the Encryption

Attributes on the 11QPEN4 line ports.
A Provisioner user cannot modify UI Mode or OCS IP
A Provisioner user cannot modify WSS attenuation attributes
....................................................................................................................................................................................................................................
1830 PSS
2-18
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Table 2-3
(continued)
Level
Privileges and use
Observer
The WebUI restricts access for a user with Observer privilege

level. In addition to the restrictions defined for the Provisioner
user, the Observer user is restricted as follows:
An Observer user cannot initialize the database during NE

configuration.
An Observer user cannot access the functions under the

Test/Analysis buttons. This includes: test LED and loopback.
An Observer user cannot access the alarm configuration

functions under the Fault button.
An Observer user cannot select Alarm Cutoff on the alarm

toolbar.
An Observer user cannot create, modify or delete any

equipment-related items or perform any action on the NE that
will change its status.
For Connections:
An Observer user can view all cross-connects and details, but

cannot create, modify or delete cross-connects.
An Observer user can view all EVPL connections, but cannot

create or delete connections.
An Observer user can view the Physical Topology, but cannot

create or delete a connection.
An Observer can view the Logical Topology with no

restrictions.
For the following administrative functions, the Observer user can

view but cannot edit:
IP routes
OSPF areas
For the following administrative functions, the Observer user

cannot view or edit:
Database backup/restore
Ping and Traceroute
....................................................................................................................................................................................................................................
1830 PSS
2-19
Issue 1 June 2013

application
....................................................................................................................................................................................................................................

Introduction
Login security controls access to the NE(s) by individual users. Client Authentication for
logging in and auditing on each NE requires a user ID (UID) and a complex password.
Security administration enables the system to deny a user access to the NE. The NE
authenticates the user ID against the NE's local security database. Based on this, the NE
either accepts or denies login access to the NE. Access may be denied during one of the
following points in time:
When the user first attempts to log in and the login attempt is denied.
During an active session and the user is disconnected by the NE.
After the user logs into an NE with a valid user ID and Password, user functions can be
performed based on the assigned User Access Privilege (UAP).
User identification and user password definition
User identifier (UID)
User identity is specified using a UID that is a unique identifier used by an NE for
security management. A UID code is a non-confidential, unique, and auditable
representation of a user such as the login name. The NE supports UIDs that are strings of
5 to 12 case-sensitive characters including upper-case letters [A-Z], lower-case letters
[a-z], numbers, and special characters. The first character must be alphabetic. For User
ID, the following special characters are accepted as valid characters for the User ID: %
(percent sign), + (plus sign), # (pound sign) and _ (underscore).
The following conditions apply to UIDs:
Each authorized user (a person, device or a software process having operations related
command inputs access) must have a UID. Each UID must be unique on the NE (i.e.
the system does not support 2 UIDs that are the same).
At any given instant in time, the NE internally maintains the identity of all UIDs
logged on at that time.
The NE supports a maximum of 255 unique UIDs.
Password identifier (PID)
A PID is a case sensitive string of 8 to 32 upper-case letters [A-Z], lower-case letters

[a-z], numbers, and special characters. A valid password must contain at least 1
alphabetic, 1 numeric, and 1 special character. The following special characters are
accepted as valid: % (percent sign), + (plus sign), # (pound sign), _ (underscore) !
(exclamation mark), @ (at sign), $ (dollar sign), (double quotation mark), &
....................................................................................................................................................................................................................................
1830 PSS
2-20
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
(ampersand), (apostrophe), ( (left parenthesis), ) (right parenthesis), * (asterisk), and .

(period). The first character of the PID can be any alphabetic, numeric, or valid special
character.
Note: , (comma) and : (colon) are not valid special characters.
The following conditions apply to PIDs:
The PID cannot be the same as the associated UID, nor can it be the reverse of the
associated UID.
The password must not have three consecutive identical characters.
The NE will not prevent a user from choosing an already existing password (more
than one user can have the same password).
Note: For all Password attributes, if a value exists, the WebUI displays it as
******** (8 asterisks). This allows the user to know that a value exists.
Password administration
The NE supports the ability for a user with security administration privileges to specify
the following user password attributes: the password age (in days); the number of days
that the existing password can continue to be used before a new password becomes
mandatory; the number of times that the existing password can continue to be used before
a new password becomes mandatory; the password obsolescence interval that must elapse
before an obsolete password can be reused.
A user with security administration privileges can provision a system-wide password
aging interval to encourage users to change passwords periodically. The following
applies:
The default for system-wide password aging interval is 30 days. The allowed range is
from 1 to 999 days.
The system allows the ability to disable the system-wide password aging interval, by
assigning a value of 0 (zero) days.
A password grace period and number of logins allowed after password expiration can also
be provisioned. The following applies:
The default for the password grace period is 7 days.
The default for the number of logins allowed after password expiration is 3.
A password is expired when one of the following events occurs:
the password is expired and neither a grace period nor number of logins is permitted
after password expiration
the password is expired and either a grace period or a number of logins is permitted
after password expiration, but the provisioned value(s) is expired (i.e., the user has no
more days to use the expired password, or no more logins allowed with the expired
password).
....................................................................................................................................................................................................................................
1830 PSS
2-21
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Users have the ability to change their own password on demand. To change a password,
the user must enter the current password, the new password, and the confirmed new
password (Note: For an Admin user changing another users password, only the new
password value needs to be entered). The NE checks the password for proper length and
syntax in accordance with established password requirements. Before updating the NE's
database, the NE ensures that the current password is different from the new password
and that the new password and confirmed new password are the same. An error message
is generated to notify the user if any of the password requirements are not met.
Adding a User
A user with appropriate security level privileges (Admin user) can add new users to the
User Security Database and to specify for each user his/her User Access Privilege (UAP).
The UAP specifies the set of commands a user can execute based on the access privilege
of the user and of the command.
Note: A maximum of only 1 Service user is allowed in the NE. Multiple users of the
other user levels are allowed.
The NE provides the ability to specify an initial password pertaining to the new user. The
user is prompted to change the password when one of the following conditions occurs:
when that user establishes a session for the first time after the initial password is
assigned
when that user establishes a session for the first time after a user password has been
reset by an administrative action.
The NE denies the session if the user does not comply.

Deleting a user
A user with appropriate security level privileges can delete existing user profiles from the
User Security Database. If the specified user is currently logged on, then the user is also
logged off. Users with security administration privileges can delete any existing user
profile except default users' profiles.
Note: A user with administration or service privileges cannot delete his/her own user
profile. The Admin user cannot delete the Service user, and the Service user cannot
delete himself.
....................................................................................................................................................................................................................................
1830 PSS
2-22
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Retrieving and editing user privileges
The ability to edit an existing user profile entry (created when entering a user) is provided
to users with appropriate security level privileges. The following conditions apply:
Only users with appropriate administration privileges can change a user profile
database entry for another user.
Only users with administrator privileges can edit the User Security Level User
attributes that exist for each user's profile. The security level user attributes are: user
privilege level, link timeout, and user-id status. It is not possible to modify the UID or
user security level of factory default users.
Any change to the privilege(s) granted to a user do not apply to the user if the user is
currently logged in. Any such change will take effect after the next login.
A user with security administration privileges can retrieve any or all user profile
entries.
Only those parameter values that are actually applied for the specified UID are
reported. This means that those system-wide parameters that have been modified, but
still not applied to the specified UID, are reported with their previous values.
Enabling/disabling a user
A user with appropriate security level privileges can disable existing user profiles in the
User Security Database. If the specified user is logged on, then the user is also logged off.
A user cannot disable himself/herself. A user cannot disable his own user profile.
A user with appropriate security level privileges can enable existing and previously
disabled user profiles in the User Security Database for a specified user(s).
Note: The Admin user can disable and enable all users including the Service user.
....................................................................................................................................................................................................................................
1830 PSS
2-23
Issue 1 June 2013

Login sessions
application
....................................................................................................................................................................................................................................
Login sessions
Overview
There is no limit to the number of simultaneous active sessions per user ID. One user ID
can log into the NE multiple times (via WebUI, TL1, CLI, and SNMP), the maximum of
which is restricted by the number of sessions supported by the NE. The NE creates an
entry in the Security log when a user logs into and logs off from the NE indicating the
UID and the established User Session Number.
The ability to authenticate a session (i.e., activate a user session) is established with the
NE by logging in an existing user through a UID and a PID. The NE will deny the
activation of a user session if authentication for the user cannot be established (e.g. the
specified password does not match the user's password on the NE, the user profile does
not exist on the NE, etc.).
The NE allows a user to cancel a current session which was previously authenticated by a
login request by providing a logoff function for the current session.
The following applies to canceling a user session:
Only users with appropriate administration privileges are able to logoff other users.
Otherwise users can only logoff themselves.
Users with administration privileges and also the Service user can logoff other users
with administration privileges.
A command request to cancel a session will terminate a single active user session on
the addressed NE. In addition any supporting connection which after the termination
of this session is no longer supporting other sessions or connections, is also
terminated.
Session timeout
The NE supports auto log out and auto disconnect of user sessions based upon user link
inactivity (i.e. an idle user). Inactivity is defined as lack of user input. The inactivity
interval (period which triggers log out) is provisionable on a system basis. The longest
such interval allowed for an idle user is 999 minutes, with a minimum of 1 minute and a
default of 60 minutes. The system allows the ability to disable the User Session Link
Timer attribute, on a system basis, by assigning the zero value. A value of 0 implies no
idle timeout, (i.e. the user can remain idle forever).
When the session timer expires, the NE logs out and disconnects a user's session to the
NE. The session timer is reset/restarted by successful user login and user session link
communication input activity after the login occurs.
Each properly logged-in session will either be logged out by the user or by system
inactivity or by connection interruption. When a session is terminated (e.g., normal
logoff, power failure, a break in the physical or logical connection), the NE ensures that
....................................................................................................................................................................................................................................
1830 PSS
2-24
Issue 1 June 2013

Login sessions
application
....................................................................................................................................................................................................................................
the port drops immediately and terminates the user processes running at the time of
logoff. When the next user attempts to log on to that physical or logical port, the user is
required to go through the entire login procedure including identification and
authentication.
The admin user may configure unique per user session timeout, based on the UID profile.
If provisioned, the timeout value may take on any value up to the system maximum. If
provisioned, the user-defined session timeout takes precedence over the system-wide
session timeout value provisioned.
....................................................................................................................................................................................................................................
1830 PSS
2-25
Issue 1 June 2013

application
....................................................................................................................................................................................................................................

Encrypted and normal mode
The system supports the ability to set the NE to function in an encrypted or normal mode.
Encrypted or normal mode should be set during initial commissioning. There is no default
mode. Only the administrative user can invoke the security mode on the NE. Changing
the mode from encrypted to normal, or vice versa, causes a warm reboot of the active
Main EC. All current user sessions will be logged off as a result.
The NE does not allow the encrypted mode setting if there is no SSH key initialized on
the system. Encrypted mode can only be turned on after the NE has already generated an
SSH key. The NE applies the following guidelines when setting the mode to either
encrypted or normal. These settings apply to the OAMP port only.
In encrypted mode:
SSH is enabled
telnet is disabled to ports 23, 3082, 3083

SSH is enabled to port 22
SNMP ports (161, 162) are allowed to be enabled
port 69 (tftp) remains open for the internal transfers from the main EC to other circuit
packs on the local NE
NTP port (123) is allowed to be enabled
SNMPv1, SNMPv2c, SNMPv3 (without authentication and privacy) requests to the
NE are disabled
SNMPv3 (with authentication and privacy) requests are allowed by the NE
In normal mode:
SSH is enabled (SSH can be used in both modes)

telnet is enabled to all ports TL1 (3082, 3083) and CLI (22, 23) ports
SNMP ports (161, 163) are allowed to be enabled
NTP port (123) is allowed to be enabled
HTTP (Web interface available) is enabled for remote management

The port 69 (tftp) remains open for the internal transfers from the main EC to other
circuit packs on the local NE
SNMPv1, SNMPv2c requests are allowed by the NE
SNMPv3 (without authentication and privacy) requests are not allowed by the NE
SNMPv3 (with authentication and privacy) requests are allowed by the NE
CLI over the craft serial port is not encrypted
....................................................................................................................................................................................................................................
1830 PSS
2-26
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
The NE supports the enabling and disabling of the following external ports: OAMP, VoIP,
E1, E2, ES1 and ES2 for extension shelves. Only an administrative user has the ability to
enable/disable these interfaces. The serial/console port cannot be disabled.
Note: The two external LAN ports, E1 and E2, connect to externally managed
devices, like RAMAN power booster amplifiers. One User Panel is supported on the
Master Shelf of an NE to provide a maximum of 2 LAN ports for external RAMAN
or Booster devices per NE.
TFTP, FTP, and SFTP
TFTP, FTP, and SFTP file transfer protocols are supported for both encrypted mode and
normal mode.
The following applies:
for PM file transfer TFTP must be used

for software download FTP or SFTP can be used
for database file transfer FTP, SFTP or TFTP can be used

for log file transfer FTP or SFTP can be used
for SSL certificate transfer FTP or SFTP can be used
SFTP (secure FTP) is a program that uses SSH to transfer files. Unlike standard FTP, it
encrypts both commands and data, preventing passwords and sensitive information from
being transmitted in the clear over the network. It is functionally similar to FTP, but
because it uses a different protocol, standard FTP client can't be used to talk to an SFTP
server, nor an FTP server can be connected with a client that supports only SFTP.
FTP and SFTP passwords are stored in the database using AES encryption.
No user interface displays the password for the FTP and SFTP server.
SFTP or TFTP are used regardless of whether the NE is in encrypted or in normal
mode.
Note: Only one tftp transfer can be initiated at a time.
Secure Shell (SSH)
Secure Shell (SSH) is a network protocol that allows data to be exchanged using a secure
channel between two network devices. SSH is designed as a replacement for telnet and
other unsecure remote shells which send information (notably passwords) in plaintext,
leaving them open to interception. The encryption used by SSH provides confidentiality
and integrity of data over an unsecure network, such as Internet. SSH allows a trusted
path of communication between two ends (e.g., NE and EMS) using encryption of the
data stream.
....................................................................................................................................................................................................................................
1830 PSS
2-27
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
The 1830 NE supports SSHv2. This applies to 1830 PSS-32/PSS-16/PSS-32S and the
Alcatel-Lucent 1830 PSS-1 (Edge Device).
The NE supports the generation of the SSH crypto Key. This crypto key needs to be
generated before the NE is set to encrypted mode. The NE allows the generation of
the crypto key when the NE mode is normal or encrypted.
SSH Keys can be zeroized (regenerated) in encrypted mode.
The NE supports AES encryption. SSH key must be encrypted with AES before
storing in the disk.
Note: Security mode can only be changed to encypted when:
SSH key exists
Security event log
For security purposes, the system generates a security log to provide an audit trail record
that supports after-the-fact investigation of specific activities (e.g., logins, modification of
critical system resources). The security log provides a means for the Security
Administrator to investigate, audit, detect, and analyze security events in order that proper
remedial actions can be taken. Security logs are protected from unauthorized access and
no modification by any user or process, even debug tools, is allowed.
The system provides the ability to a user with sufficient security level privileges to
retrieve security event log reports that were generated by the system for a given UserID
and between a specified From Date and Time and To Date and Time.
The following applies to the security log:
The security log has a circular (or equivalent) recording mechanism (i.e., oldest
record overwritten by newest), and an appropriate administrator has the capability to
retrieve, print, copy, and upload the security log for long-term storage.
When the security log has reached 90% of its maximum size, the NE sends an
appropriate event to the security administrator.
The security event log file is protected from tampering by any user defined in the user
security database and cannot be deleted by any user defined in the user security
database.
The security event log file is stored in non-volatile memory and survives system
restarts/resets.
The security event log file does not survive software generic upgrades and power
reset.
....................................................................................................................................................................................................................................
1830 PSS
2-28
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Security log contents
Each NE is able to log the following classes of information in the security log:
any action that changes the security attributes and services

any action that changes access controls
any action that changes configuration parameters of the device
each login attempt and its result
each logout or session termination (whether remote or console, whether requested or
due to inactivity timeout)
A security log entry contains the following information:
the identification, address and security level of the user that initiated the action that is
being logged
the actual attempted action that is being logged (the echo of the command/response
message)
an indication of the success or failure of the activity (command completion code)
the date and the time the action (i.e. the command or the message) occurred
Note: The security event log file does not record actual or attempted passwords that
are entered in as passwords.
User activity log
Alcatel-Lucent 1830 PSS supports logging of user activities. Activities are collected in a
user activity log (UAL) in a user-readable format. All user actions via the WebUI are
logged and stored in this UAL along with the time and date of the action, the source IP
address and or user name of the operator, and the action itself. One entry is captured for
each user action. The purpose of this log is to provide non-repudiation.
The administrator can also transfer the UAL log to a remote file server (RFS). The RFS
can be the management system itself, or some other server - the choice is up to the
operator. This transfer mechanism can be performed using FTP or SFTP.
Log file transfer
The WebUI can retrieve and display parameters related to the last log transfer request.
The WebUI also allows the user to modify and view server information for the log file
transfer. When the user initiates a log file transfer, after receiving a successful response
from the NE, the WebUI displays a message to the user indicating that the file transfer has
been initiated. The WebUI then allows the user to navigate to other WebUI screens. The
user can then go back to the Log File Transfer screen to view the status of the transfer.
Note: Log file transfer can also be done via CLI.
....................................................................................................................................................................................................................................
1830 PSS
2-29
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
System access control
System access control prevents an otherwise authenticated (valid) user from unauthorized
access. Not all system resources are available to every user, and restricting resource
availability is extremely important to securing a safe and trusted network. System access
control allows only authorized users access to the NE. Access control level is associated
with each user and is maintained through the User Security Level attribute.
To execute any command, a user needs a User Security Level (User Access Privilege)
including the Command Security Level (Command Access Privilege) assigned to the
command being executed. If the user is denied the privilege of executing a command due
to an insufficient User Security Level, the system indicates to the user that the command
request is invalid due to insufficient privileges.
All physical ports of the NE exercise system access control. This includes direct access
serial and LAN ports (CIT, external OAMP network access, etc.) and access via an
Embedded Communications Channel (ECC) as in the case of GCC between the 1830-PSS
and the 1830-PSS1 (Edge Device).
Any failed login attempt immediately reports to the user that the login process has failed
or is invalid. Information such as invalid user ID or invalid password is not reported.
The NE performs the entire user authentication procedure even if the UID that is entered
is not valid. After a failed login attempt, the system delays for 2 seconds prior to
presenting the next login prompt. This applies to human interaction interfaces (e.g. CLI,
TL1, WebUI).
After the maximum number of consecutive invalid login attempts for a session has been
reached, the system records in the security log the IP address of the source along with the
UID and an intrusion transient condition is reported.
Access control lists (ACL)
The system supports access control lists (ACL) functions.

Filters
The WebUI supports viewing a list of all filters and their associated patterns. Each filter
may be associated with up to 256 patterns. The WebUI also supports creating a new filter.
Up to 100 filters may be defined on the system
The WebUI supports adding a pattern to an existing Filter ID. When adding a pattern, the
WebUI displays a picklist of existing patterns that are not already associated with this
filter to choose from. The user must specify a Pattern Index with each selected pattern.
The WebUI also supports deleting a pattern from an existing Filter ID. A filter can only be
deleted when all patterns have been removed for this filter.
Note: If the user specifies a Pattern Index that is already associated with this Filter ID,
the WebUI will delete the existing Pattern/Filter pair and create a new one with the
specified Pattern ID/Index.
....................................................................................................................................................................................................................................
1830 PSS
2-30
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Patterns
The WebUI supports viewing a list of all patterns used for IP access control. The WebUI
also supports creating, modifying, deleting, and viewing of patterns. A pattern can only be
deleted if it is not associated wth a filter.
Ports
The WebUI supports viewing a list of all port to ACL filter associations.
The WebUI allows a user to create, modify, and view an association between an ACL
filter and a specified port and direction. When creating or modifying an association, the
WebUI displays a picklist of existing filters to choose from. An association between a
filter and port/direction can also be deleted.
Note: Up to 2 filters can be associated with each port, one in the Receive direction
and one in the Transmit direction. If a filter/port association already exists in a
direction, the WebUI will not allow the creation of another association to this port in
the same direction.
The following ports support ACL filtering.
Table 2-4
Ports that support ACL filtering
Card
Port
Signal Rate
112PDM11
L1
OTL4.4
11DPE12
L{1-2}
OTU2
11DPE12A, 11DPE12E
L{1-2}
OTU2
11DPM12
L{1-2}
OTU2
11QPA4, 11QPEN4
L{1-4}
OTU2
11QPA4, 11QPEN4
C{1-4}
OTU2
11QPE24
X{1-4}
OTU2, 10GbE
11STAR1, 11STAR1A
L1
OTU2
11STAR1, 11STAR1A
C1
OTU2
11STMM10
C{1-10}
OTU1
4DPA4
L{1-2}
OTU1
A2325A, AHPHG, AHPLG,

ALPHG,
OSC
A2P2125, AM2125A,
AM2318A, OSCT
OSCSFP
MTC1T9
E1, E2, OAMP
USRPNL
E1, E2, OAMP, VOIP
....................................................................................................................................................................................................................................
1830 PSS
2-31
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
For the following ports, the user can view the system-defined port/filter associations. The
user may not edit the associations for these ports.
Table 2-5
System-defined port/filter associations
Card
Port
EC
CIT
EC (PSS-16, PSS-32 only)
AUX
EC
LAN-PPP
EC
LAN-NODE
MTC1T9
CIT
MXEC320H
MTC1T9
LAN-PPP
MXEC320H
MTC1T9
LAN-NODE
MXEC320H
Optical intrusion detection
The optical intrusion detection feature gives the user the ability to have an optical
intrusion alarm raised upon detection of an outside plant fiber loss. A span loss could be
due to a hacker stripping away the fiber cladding and bending the fiber to cause light
leakage.
The system allows the user the ability to set the threshold values and retrieve baseline
values and threshold values for each optical line. Provisioning of optical intrusion
detection settings is supported on the following cards: A2325A, AHPHG, AHPLG,
ALPHG, AM2125A, AM2125B, AM2318A and OSCT.
The WebUI allows the user to set the Optical Intrusion Loss Threshold value. The
system will raise a MAJ alarm Optical Intrusion Detected against the optical line (OTS)
if the loss detected is equal to or greater than the specified threshold limit during a given
interval. The system also allows a user to clear an optical intrusion detected alarm.
The WebUI supports modifying and viewing of the following optical intrusion detection
attributes
Monitoring Enabled
Span Loss (dB)

Baseline Span Loss (dB)
Loss Theshold (dB)
Polling Period (seconds).
....................................................................................................................................................................................................................................
1830 PSS
2-32
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
Data Center Connect (DCC)
General risks can be related to inadequate security policies or human factors. Security
processes often rely on well-designed controls that ensure the confidentiality, integrity,
and availability of data and services for the data center. TheAlcatel-Lucent 1830 Photonic
Service Switch (PSS) DWDM platform provides integrated physical layer encryption that
lowers data center security risks and increases data confidentiality, integrity, and
availability, based on security best practices and common security frameworks used in
data center environments.
Data integrity means detecting and avoiding unauthorized access to, or modification of,
data. The Alcatel-Lucent 1830 PSS provides several security mechanisms to ensure the
integrity of data communication services across the DCC, and the integrity of the
equipment itself. Comprehensive security logs allow an administrator to detect
non-authorized changes to device configuration, complemented by real-time intrusion
prevention alarms. Optical intrusion detection (OID) constantly checks the status of each
optical fiber by monitoring changes in optical loss. A threshold value can be set to raise
an alarm for possible optical intrusion when the optical loss changes beyond the
configured level.
DCC transport risks are related to the uncertainty that vulnerabilities could be exploited to
damage or remove sensitive data assets. To reduce the opportunity for attack, and
therefore the security risk, the Alcatel-Lucent 1830 PSS can be enabled to function in
secure mode, which provides a hardened device configuration with the following
restrictions:
Only the essential logical and physical ports needed to manage the system are open
Software debug functions are disabled
Services of the embedded OS are disabled, as well as any interactive OS access
Only secure NE management protocols such as Secure Sockets Layer (SSL) and
SNMPv3 are supported
Alcatel-Lucent 1830 PSS also supports the security of the optical links within the DCC
with the following capabilities:
Optical intrusion detection (OID) on spans with threshold alarms
Layer 1 hardware encryption @ 10G line rate providing:

Lower latency
Lower cost per encrypted bit

Protocol independence
AES256 + FIPS & Common Criteria compliance
Dynamic key management for private and hybrid/private clouds
....................................................................................................................................................................................................................................
1830 PSS
2-33
Issue 1 June 2013

application
....................................................................................................................................................................................................................................
The Alcatel-Lucent 1830 PSS supports the following interface types for DCC
applications:
Fast Ethernet, Gigabit Ethernet, 10GigE (LAN andWAN), and 100GigE

4x10GigE Muxponder (40G) and 10x10GigE Muxponder (100G)
Fiber Channel 1G, 2G, 4G, 8G, and 10G
FICON 1G, and 2G; and FICON-Express

BM Intersystem Channel ISC-3 peer-mode
Video: SD-SDI, HD-SDI, DVB-ASI
Transponderless (direct connection) support of ITU-grid wavelengths from external
equipment
For additional details of the Secure Data Center Connect (DCC) application, see the
Alcatel-Lucent 1830 PSS Product Information and Planning Guide.
....................................................................................................................................................................................................................................
1830 PSS
2-34
Issue 1 June 2013

Authentication
application
....................................................................................................................................................................................................................................
Authentication
Overview
Authentication is the act of verifying a claimed identity, providing a basis for setting up
private communications with full data integrity and logging management activity. The
system supports the following different methods of authentication.
RADIUS authentication
Local NE Authentication
SNMP
RADIUS authentication
RADIUS allows the user to be authenticated and authorized at the same time. The
RADIUS server is provisioned with one or more user profile or profiles. Based on the
user profile and user class definitions, the RADIUS server not only allows the user to
have access to the NE, but also grants the user the user's privilege level. The RADIUS
client works with Steel-Belted RADIUS, WinRADIUS, and FreeRadius servers. The NE
supports provisioning of up to 2 RADIUS Servers. The administrative privilege user can
add/delete the specific RADIUS server.
The administrative privilege user can Enable/Disable the RADIUS servers without
deleting their configuration.
When two servers are configured and enabled, the NE queries the second RADIUS
server (RAD2) only if the first server (RAD1) does not respond after the appropriate
timeout and retries.
Web users are authenticated from the local stored database regardless of whether
RADIUS is enabled.
SNMP users are not authenticated by RADIUS.
RADIUS functionality can be used regardless of whether the NE is in encrypted or
normal mode.
A login by the Service user is never authenticated using RADIUS for any user
interfaces (CLI, TL1, WebUI). The authentication for the Service user is always local.
Table 2-6
Vendor Code
7483
Conforms to RADIUS RFC
Yes
Vendor-assigned attribute number
2 for NMS
Attribute format
Decimal
....................................................................................................................................................................................................................................
1830 PSS
2-35
Issue 1 June 2013

Authentication
application
....................................................................................................................................................................................................................................
Table 2-6
Attribute value
(continued)
0 for observer
1 for provisioner
2 for admin
RADIUS attributes
The NE supports configuring the following general RADIUS attributes:
Timeout: This is the timeout (in seconds) for the NE to wait for a response from the
RADIUS server. A failure is declared after the timeout is elapsed. The supported value
range for timeout is 1 to 1000. The default value is 5.
Retries: This is the number of attempts that the NE will try to contact the specified
RADIUS server that has failed to respond during the previous request(s). If there is no
response from the server after the specified tries, then the NE will try to contact the
second RADIUS server if one is provisioned. The supported value range for retries is
1 to 100. The default value is 3.
The NE supports the following RADIUS server attributes. The RADIUS attributes can be
configured, edited, deleted, and retrieved by a user with appropriate administrative
privilege. The "sharedSecret" parameter cannot be retrieved.
ServerNum: This is the AID for the RADIUS server. The acceptable values are RAD1
and RAD2.
IPAddr: This is the IP address of the specified RADIUS server.
Port: This is the authentication port of the RADIUS server. The valid value is from 1
to 65000. The default port value is 1812.
sharedSecret: This is the shared secret key between the NE and the target RADIUS
server. This key is an ascii string between 5 to 32 characters.
Status: This is RADIUS server status. The valid values are the following
Enabled - The RADIUS server is online. This is the default value.
Disabled - The RADIUS server is offline.
The NE supports configuring the following authentication ordering behavior options that
can be configured and retrieved by a user with appropriate administrative privilege.
LOCAL: Authentication is based on the local NE's security database. This is the
default.
RADIUS: Authentication is based on the RADIUS server's database.
RADIUS-THEN-LOCAL: The authentication is attempted first using the RADIUS
server's database. If the RADIUS server is not reachable then authentication is based
on local NE's security database.
Note: If the RADIUS server is reachable and the user profile does not exist in
RADIUS server's database, then the authentication fails and the user is denied access.
....................................................................................................................................................................................................................................
1830 PSS
2-36
Issue 1 June 2013

Authentication
application
....................................................................................................................................................................................................................................
Local NE authentication
Local NE Authentication is accomplished via the UID and PID pair created and stored on
the local NE.
Note: The access to the database (for authentication) of the NE where user profiles
are stored, is allowed only on a local connection. This is for the Service user to access
locally via connection to RS232 or local CIT port.
SNMP authentication
The local NE can authenticate and authorize users based on SNMP. SNMP provides for
both security versions and security levels. A security version is an authentication strategy
that is set up for a user and the group in which the user resides. A security level is the
permitted level of security within a security version. A combination of a security version
and a security level will determine which security mechanism is employed when handling
an SNMP packet. Three security versions are available: SNMPv1, SNMPv2c, and
SNMPv3.
The following applies to SNMP:
The NE supports separate DB records for SNMPv3 users. SNMPv3 users are different
from the CLI/TL1/WebUI users. SNMPv3 users can be provisioned via 1354
RM-PhM or WebUI.
The system supports creation of a default SNMP user at initial startup with a known
password. This known password permits 1354 RM-PhM to perform auto-discovery of
NEs. The default SNMP user cannot be deleted. It can only be disabled.
The NE supports changing SNMPv3 users' authentication (auth) and privacy (priv)
passwords.
The system supports enabling and disabling SNMP users.
The NE supports sending Authentication Failure traps and supports enabling and
disabling the sending of Authentication Failure Traps.
The system allows cloning a new SNMP user from an existing user.
Even if RADIUS authentication is enabled on the system, login access to the NE via
SNMP is always based on the UID and PID pair resident on the NE.
Note: Following are two scenarios when the user must update SNMPv3 passwords:
1. Upgrading from a previous release.
After the upgrade, the authentication (auth) and privacy (priv) passwords for
SNMPv3 default user (v3DefaultUser) must be updated.
2. Following a change to the loopback IP address (including the initial loopback IP
address provisioning from its default value).
After the warm restart, the authentication (auth) and privacy (priv) passwords for
all SNMPv3 users, including the ones for SNMPv3 default user (v3DefaultUser).
must be updated.
....................................................................................................................................................................................................................................
1830 PSS
2-37
Issue 1 June 2013

Authentication
application
....................................................................................................................................................................................................................................
Note: If loopback IP address change is followed immediately with clearing

database (without also clearing IP addresses), there is no need to update SNMPv3
passwords.
NTP server authentication
The NTPv4 protocol supports authentication using either symmetric key or public key
cryptography. Alcatel-Lucent 1830 PSS implements authentication using the symmetric
key cryptography feature. This method ensures an unbroken chain of trust between the
client system and the primary servers at the root of the timing distribution network. This
chain is known as the provenance of the client. The protocol provides the credentials to
ensure that the source of the timing signal is not being spoofed since the attacker does not
have the cryptographic key information to provide authentic credentials.
When authentication is in use, every message contains a message authentication code
(MAC) appended to the NTP header in the message. The MAC is calculated using a
cryptographic hashing algorithm (in the form of SHA-1 or MD5) to produce a
mathematical fingerprint that uniquely identifies each message. The hashing algorithm
used is up to the user. Under the symmetric key method, both the server and the client
share a key, that is distributed outside this protocol. The server uses the key to create the
MAC. When the message arrives, the client uses the key to create its own version of the
MAC. The client then compares its calculation to the MAC inserted in the message.
When the two codes match the client concludes that the message was indeed sent from
the intended server.
SNMP trap destinations
The system supports editing and retrieval of SNMP trap destinations. Trap destinations
are SNMP managers provisioned to listen to traps coming from the NE. These SNMP
managers may or may not also be actively managing the NE.
The following SNMP trap server attributes are supported:
ID - this is the ID of the SNMP trap server. The system supports up to 10 remote trap
servers. This value is required to discern which trap server the user is addressing.
Possible values are 1 thru 10.
Destination IP - this is the IP address of the SNMP trap server. Specifies the IP
address of the server that serves as the trap destination.
String - this is the community string sent to the SNMP trap server. It is an ascii string
from 1 to 32 characters.
Port - this is the (IP address) port of the SNMP trap server. Specifies the IP address
port of the server that serves as the trap destination.
Timeout - Specifies the time (round trip), in hundreths of a second, after which the
connection times out if no reply is received. Following a timeout, a retry is attempted,
up to the number of retries specified by the retry variable.
....................................................................................................................................................................................................................................
1830 PSS
2-38
Issue 1 June 2013

Authentication
application
....................................................................................................................................................................................................................................
Retry Count - Specifies an integer value for the number of times the network element
will attempt to retry the connection in the event of a timeout.
SNMP version - the SNMP version to use when formatting the trap. Valid versions are
v1, v2c, and v3.
NMS Station Group ID - Specifies an integer value that uniquely identifies the NMS
workstation serving as the trap destination. (Use 0 for all third party SNMP trap
servers).
Note: Traps are sent in SNMPv2 or SNMPv3 format, depending on the security level
of the NE. If the NE is encrypted, then all traps are encrypted, so the traps will be in
v3 format. All SNMPv3 traps are sent with the SNMPv3 default user. In normal
mode, the version can be v2 or v3.
SNMP community strings
The system supports creation, editing, deletion, and retrieval of SNMP community
strings. Community strings are necessary for authentication (e.g. if the manager comes
into the NE via SNMPv2). Provisioning of these tasks is accomplished via CLI, WebUI,
and SNMP.
Note: If the NE is in encrypted mode, the user can still configure these community
strings, but the remote SNMP manager will connect via SNMPv3.
The following SNMP community attributes are supported:
SNMPComID this is the ID of the SNMP community. The system supports up to 5

pre-configured communities, one for each of the user privilege classes. Possible
values are: admin, provisioner, observer, nms, and 3rdpnms. This parameter requires a
value.
String this is the community string sent from the SNMP manager to the NE. It is an
ascii string from 1 to 32 characters. Based on the string and the privilege level
inherited from the SNMPComID, the NE will either process or deny the SNMP
request. The string must be unique (there cannot be duplicate strings) and the string
cannot start or end with a blank space.
The SNMP string is checked every time an SNMP request is processed by the NE. If
there is a match, then the NE will further check the privilege level of that string to
ensure that the request can be granted given the command privilege level. If the string
does not match any string defined in the NE, the request fails and the NE returns a
failure message. If the privilege level is inadequate for the request being asked, then
the NE returns a failure message, otherwise, the request is processed.
....................................................................................................................................................................................................................................
1830 PSS
2-39
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
Administer user logins on the OCS application

using the Alcatel-Lucent 1830 PSS ZIC
Overview
Purpose
The following procedures are to be used for user management. It is suggested to use
User administration concept (p. 2-6) as an entry point for user administration activities.
Furthermore, it is recommended to have a list prepared of all the users that probably will
need to have access to the Alcatel-Lucent 1830 PSS ZIC and the NEs, especially if
several user logins are to be created or modified for different NEs. The list should contain
the designated user IDs, associated passwords, access privileges and other related security
parameters, and should be as complete as possible.
Contents
2-42
2-45
2-49
2-50
2-52
2-53
2-54
2-55
2-56
2-59
2-60
2-61
Procedure 2-12: Send a short free form text message to other users
2-63
Procedure 2-13: Modify command access security level assigned to a TL1

command.
2-65
Procedure 2-14: Display command access security level assigned to a TL1

command
2-67
2-68
....................................................................................................................................................................................................................................
1830 PSS
2-40
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
Procedure 2-15: Copy security sensible files or data from/to an NE to/from a

remote file server
2-69
2-73
Procedure 2-16: Configure SSL authentication for ZIC to NE communication

(high-level procedure)
2-75
2-76
2-77
2-79
2-80
2-81
2-82
2-83
2-86
2-88
2-90
....................................................................................................................................................................................................................................
1830 PSS
2-41
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create a user login.

Important! Please note that any user administration changes will not take effect until
the next login session.
Each new created user has to change his password at first log in. After changing his
password the user has to exit the Alcatel-Lucent 1830 PSS ZIC and to relaunch a new
session using the new password.
Related TL1 commands
The following TL1 commands are related to this procedure:
ENT-USER-SECU
Before you begin

Required privileges
You must have a User Community Authorization Level of 5 to perform this task.
Required equipment
The following equipment is required to perform this task:
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC navigation pane, select System NE Security
Users.
Then select Create User, either by selecting Action from the main menu or by using the
context menu opened with the right mouse button.
Result: The Alcatel-Lucent 1830 PSS ZIC Create User window opens.
...................................................................................................................................................................................................
Place the cursor in the User Identifier text box, then type in the User Identifier assigned
to the new user.
Reference: See User identifiers (p. 2-8).
...................................................................................................................................................................................................
Place the cursor in the Password text box, then type in the password assigned to the new
user.
....................................................................................................................................................................................................................................
1830 PSS
2-42
Issue 1 June 2013

....................................................................................................................................................................................................................................
The password may be preliminary. Each user is permitted to change her/his own
password.
Reference: See Passwords (p. 2-10).
...................................................................................................................................................................................................
Place the cursor in the Re-EnterPassword text box, then type in the password again.
The password may be preliminary. Each user is permitted to change her/his own
password.
...................................................................................................................................................................................................
Place the cursor in the User Community Authorization Level text box and enter the
respective User Community Authorization Level for the new user.
Reference: See User community authorization level (UCAL) (p. 2-9).
...................................................................................................................................................................................................
Place the cursor in the User Name text box, then type in the User Name assigned to the
new user.
...................................................................................................................................................................................................
In the field Link Timer select the respective value.

The User Session Activity Link Timer specifies the amount of time (in minutes) that the
User Session link must be inactive with regards to user input before a user session link
timeout occurs.
0
Disabled, no user session link timeout will occur.
1 to 999
Time in minutes, indicates the LNKTMR time interval. A user session link timeout
occurs if the user session link is inactive with regards to user TL1 input for the time,
in minutes, indicated.
...................................................................................................................................................................................................
In the field Fixed Password you can specify whether the user is created with the ability to
change his/her password.
Yes. The password is fixed and cannot be changed by the user.
No. The password is not fixed and can be changed by the user.
....................................................................................................................................................................................................................................
1830 PSS
2-43
Issue 1 June 2013

....................................................................................................................................................................................................................................
Users with fixed password is cannot login multiple times despite the MAXSESSION
setting.
...................................................................................................................................................................................................
Make sure that the settings in the Create User window are correct.
...................................................................................................................................................................................................
10
Click Apply to add the new user login.

Result: The user is added into the list of users.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-44
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to set system-wide user security parameters.

Note: You must have security administrator privileges.
SET-ATTR-SECUDFLT
Before you begin
Prior to performing this task, you must be logged into the Alcatel-Lucent 1830 PSS ZIC
and the respective network element.
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System NE Security
Users.
...................................................................................................................................................................................................
Either by selecting Action from the main menu bar or by using the context menu opened
with the right mouse button, select Properties General.
Result: The Properties General window opens.
...................................................................................................................................................................................................
In the Password Aging Interval spin box select the desired value. You can also enter the
value directly.
Additional information The Password Aging Interval indicates the number of days
that a user password (PID) is aged before the system prompts the user to change to a
new password.
Zero, Password aging on user accounts is disabled. User passwords are not
deactivated/disabled by password aging.
1-360
....................................................................................................................................................................................................................................
1830 PSS
2-45
Issue 1 June 2013

....................................................................................................................................................................................................................................
Password Aging Interval in days.

...................................................................................................................................................................................................
In the Minimum Password Aging Interval spin box select the desired value. You can also
enter the value directly.
Additional information The Minimum Password Aging Interval indicates the
number of days that a user password (PID) is aged before the user is allowed to
change to a new password.
Zero, Minimum Password aging on user accounts is disabled. User passwords can
be changed without a minimum aging.
1-360

...................................................................................................................................................................................................
In the Pre Expiration Password Interval spin box select the desired value. You can also
enter the value directly.
Additional information The Pre Expiration Password Interval indicates the number
of days that an NE sends a message to a user for alerting of the next password
expiration.
0 Zero, Pre Expiration on user accounts is disabled. No alert message will be sent.
1-7
Pre Expiration Password Interval in days.

...................................................................................................................................................................................................
In the Max Failed Attempts spin box select the desired value. You can also enter the
value directly.
Additional information The Max Failed Attempts indicates the maximum number of
failed login attempts before an NE logs out a user and locks out the user channel.
Zero, Max Failed Attempts on user accounts is disabled. No limit to the failed
login attempts.
1-15
Max Failed Attempts.

...................................................................................................................................................................................................
In the Password History spin box select the desired value. You can also enter the value
directly.
....................................................................................................................................................................................................................................
1830 PSS
2-46
Issue 1 June 2013

....................................................................................................................................................................................................................................
Additional information The Password History indicates the number of last used
password to be used for the comparison with the new password, when entered for
changing. The new password must be different from all of the passwords in the
history.
Zero, Password History on user accounts is disabled.
1-15
Number of passwords stored in the password history.

...................................................................................................................................................................................................
In the Keep Alive Message Interval spin box select the desired value. You can also enter
the value directly.
Additional information The Keep Alive Message Interval indicates the time interval
in minutes after which the NE sends a KEEPÂLIVE^MESSAGE on a TCP

connection inactivity.
Zero, KEEPÂLIVE^MESSAGE sending is disabled.
1-240
KEEPÂLIVE^MESSAGE timeout value, in minutes.

...................................................................................................................................................................................................
In the Maximum Sessions spin box select the desired value. You can also enter the value
directly.
Additional information The Maximum Number of Simultaneous Sessions defines
the number of simultaneous sessions allowed per UID. Attempts to activate more
sessions for a given UID than allowed by this parameter are denied. The value can be
provisioned using this parameter, on a system-wide basis for accounts where the user
is able to change their password. For users who are unable to change their password,
the maximum number of simultaneous sessions is limited to 1.
1-6
The number of simultaneous sessions allowed on the NE for any user that is able
to change their password. Only 1 session is allowed for users that are unable to
change their password.
...................................................................................................................................................................................................
10
In the User Session Activity Link Timer Defaul spin box select the desired value. You
can also enter the value directly.
....................................................................................................................................................................................................................................
1830 PSS
2-47
Issue 1 June 2013

....................................................................................................................................................................................................................................
Additional information The User Session Activity Link Timer Default specifies
system's default value for the amount of time (in minutes) that the User Session link is
inactive with regards to user TL1 input/output, before a user session link time-out
occurs.
Disabled, no user session link time-out will occur.
1-999
Time in minutes, indicates the LNKTMR time interval. A user session link
time-out occurs if the user session link is inactive with regards to user TL1
input/output for the time, in seconds, indicated.
...................................................................................................................................................................................................
11
Make sure that the settings in the window are correct.

...................................................................................................................................................................................................
12
Click Apply to apply your settings.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-48
Issue 1 June 2013

Procedure 2-3: Display system-wide user security
parameters
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................

When to use
Use this procedure to display system-wide user security parameters.

RTRV-DFLT-SECU
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Users.
...................................................................................................................................................................................................
Result: The Properties General window opens displaying system-wide user security
parameters.
Reference: See System-wide user security parameters (p. 2-50).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-49
Issue 1 June 2013

....................................................................................................................................................................................................................................

Parameter description
The following parameters are available:

Parameter ...
Meaning...
Password Aging Interval
The Password Aging Interval indicates the number of days that a

user password (PID) is aged before the system prompts the user to
Zero, Password aging on user accounts is disabled. User

passwords are not deactivated/disabled by password aging.
1-360

Minimum Password
Aging Interval
The Minimum Password Aging Interval indicates the number of

days that a user password (PID) is aged before the user is allowed to
Zero, Minimum Password aging on user accounts is disabled.

User passwords can be changed without a minimum aging.
1-360

Pre Expiration
Password Interval
The Pre Expiration Password Interval indicates the number of days

that an NE sends a message to a user for alerting of the next
password expiration.
0 Zero, Pre Expiration on user accounts is disabled. No alert

message will be sent.
1-7
Pre Expiration Password Interval in days.

Max Failed Attempts
The Max Failed Attempts indicates the maximum number of failed

login attempts before an NE logs out a user and locks out the user
channel.
Zero, Max Failed Attempts on user accounts is disabled. No

limit to the failed login attempts.
1-15
Max Failed Attempts.
....................................................................................................................................................................................................................................
1830 PSS
2-50
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter ...
Meaning...
Password History
The Password History indicates the number of last used password to

be used for the comparison with the new password, when entered
for changing. The new password must be different from all of the
passwords in the history.
Zero, Password History on user accounts is disabled.
1-15
Number of passwords stored in the password history.

Keep Alive Message
Interval
The Keep Alive Message Interval indicates the time interval in

minutes after which the NE sends a KEEPÂLIVE^MESSAGE on a
TCP connection inactivity.
Zero, KEEPÂLIVE^MESSAGE sending is disabled.
1-240
KEEPÂLIVE^MESSAGE timeout value, in minutes.

Maximum Sessions
The Maximum Number of Simultaneous Sessions defines the

number of simultaneous sessions allowed per UID. Attempts to
activate more sessions for a given UID than allowed by this
parameter are denied. The value can be provisioned using this
parameter, on a system-wide basis for accounts where the user is
able to change their password. For users who are unable to change
their password, the maximum number of simultaneous sessions is
limited to 1.
1-36
The number of simultaneous sessions allowed on the NE for any

user that is able to change their password. Only 1 session is
allowed for users that are unable to change their password.
User Session Activity
Link Timer Default
The User Session Activity Link Timer Default specifies system's

default value for the amount of time (in minutes) that the User
Session link is inactive with regards to user TL1 input/output, before
a user session link time-out occurs.
Disabled, no user session link time-out will occur.
1-999
Time in minutes, indicates the LNKTMR time interval. A user

session link time-out occurs if the user session link is inactive
with regards to user TL1 input/output for the time, in seconds,
indicated.
....................................................................................................................................................................................................................................
1830 PSS
2-51
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete a user login. Please note that default users cannot be deleted.
DLT-USER-SECU
Important! Any user administration changes will not take effect until the next login
session. If you delete a logged in user, he will be logged out.
Before you begin
The procedure itself is limited to the necessary steps to delete an existing user login using
the NE User Provisioning window.
Required privileges
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectSystem NE Security

Users.
Select a user in the list displayed in the right part of the Alcatel-Lucent 1830 PSS ZIC
main window.
...................................................................................................................................................................................................
with the right mouse button, select Delete.
Result: A confirmation window opens.
...................................................................................................................................................................................................
Click on Yes in the confirmation window.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-52
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to inhibit a user to log in to the system.

INH-USER-SECU
session. If you delete a logged in user, he will be logged out.
Before you begin
Prior to performing this task, you must be logged in to the Alcatel-Lucent 1830 PSS ZIC
Required equipment
Instructions
...................................................................................................................................................................................................
Users.
main menu.
...................................................................................................................................................................................................
with the right mouse button, select Inhibit User Login.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-53
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to allow reinstatement of a user that has been disabled by Procedure
2-5: Inhibit a user login (p. 2-53) or if the user has been inhibited due to exceeding the
number of failed login attempts (security INTRUSION alarm will be raised in such case)
and if the user has not logged in for a time longer than his individual User ID Aging
period.
ALW-USER-SECU
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................

Users.
main menu.
...................................................................................................................................................................................................
with the right mouse button, select Allow User Login.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-54
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to display user property information.

RTRV-USER-SECU
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Users.
main menu.
...................................................................................................................................................................................................
Result: The Properties General window opens, displaying user profile information.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-55
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to edit the existing user profile entries, identified by the User Identifier
(UID), in the User Security Database.
ED-USER-SECU
session. Only a logged out user can be modified.
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Users.
main menu.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
To modify the User Community Authorization Level select the desired value in the User
Community Authorization Level spin box.
....................................................................................................................................................................................................................................
1830 PSS
2-56
Issue 1 June 2013

....................................................................................................................................................................................................................................
Reference: A user can be assigned a security level from 1 through 5. Level 5 is
reserved for users needing system administrator privileges.

...................................................................................................................................................................................................
Place the cursor in the User Name text box, then type in the User Name assigned to the
new user.
...................................................................................................................................................................................................
In the field User Session Activity Link Timer select the respective value.
The User Session Activity Link Timer specifies the amount of time (in minutes) that the
User Session link must be inactive with regards to user input before a user session link
timeout occurs.
0
Disabled, no user session link timeout will occur.
1 to 999
Time in minutes, indicates the LNKTMR time interval. A user session link timeout
occurs if the user session link is inactive with regards to user TL1 input for the time,
in minutes, indicated.
...................................................................................................................................................................................................
In the field User ID Aging Interval select the respective value.

The User ID Aging Interval specifies the aging or expiry interval of a particular User Id.
At the end of this interval, the UID is disabled if during this interval it has never been
used to set up a session.
0
UID aging is disabled.
1 to 999
Number of days left for the user to log in, before UID expiration.
...................................................................................................................................................................................................
In the field Fixed Password you can specify whether the user is created with the ability to
change his/her password.
Yes
Yes. The password is fixed and cannot be changed by the user.
No
No. The password is not fixed and can be changed by the user.
....................................................................................................................................................................................................................................
1830 PSS
2-57
Issue 1 June 2013

....................................................................................................................................................................................................................................
Users with fixed password is cannot login multiple times despite the MAXSESSION
setting.
...................................................................................................................................................................................................
In the field Allowed IP you can enter a &-separated list of allowed source IP addresses for
login with the User Identifier.
An empty list indicates that login to UID is allowed from all IP addresses.
If the parameter is specified without value, then the IP address list is cleared (empty
list).
...................................................................................................................................................................................................

...................................................................................................................................................................................................
10

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-58
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to log off a specified user.

CANC-USER-SECU
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Users.
main menu.
...................................................................................................................................................................................................
with the right mouse button, select Loggoff.
Result: The Logoff User window opens.
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-59
Issue 1 June 2013

Procedure 2-10: Retrieve information on all active user
logins
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve information on all active (connected) and/or authenticated
(logged on) users.
RTRV-STATUS
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................

Users.
...................................................................................................................................................................................................
with the right mouse button, select View Users Status.
Result: The View User Status window opens.
The retrieved information consists of:
the Session number
the User Identifier
the IP Address,
indicating where the user is connecting from. If the user is connected to the NE by
means of a TCP/IP connection the address is in the form {0-255}-{0-255}-{0-255}{0-255}. If the user is connected by the OSI stack the address is ECC, and if the user is
connected on the CIT LAN port, the address is FDBGLAN.
OMSID, the 1350 OMS operator name, in the case of login from OMS (ZIC).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-60
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to change a user password.

Actually, this covers two scenarios:
Normal
The user changes his/her own password, when required, unless the user has UCAL=5
or has fixed password.
The user Password Identifier (PID) must be changed periodically, depending on the
password aging period, minimum password aging period and password history of the
old last passwords not to be reused.
When a PID is changed, the new password must differ from the old password(s). In
order to avoid that a password can get accidentally echoed if invalid syntax is used,
the responsemessage echoes only the TL1 command name without any parameter.
The new password is to be entered twice, to avoid mis-typed password, with
consequent impossibility of logging in.
Forced
The administrator user changes another users password. This can only be done when
the other user is logged out (-> CANC-USER-SECU procedure). Password History
and Minimum Password Age do not apply to this case. Entry of the old password is
not required.
ED-PID
ED-USER-SECU
Before you begin
Prior to performing this task, you must:
Have a valid user login and password,

Be connected to the subject NE,
Have proper User Community Authorization Level to perform this task.
Required equipment
....................................................................................................................................................................................................................................
1830 PSS
2-61
Issue 1 June 2013

....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................

Users.
main menu.
...................................................................................................................................................................................................
If
then
you want to change your own password,
Either by selecting Action from the main menu

bar or by using the context menu opened with
the right mouse button, select Change
Password Normal.
you want to change the password of another

user,
Either by selecting Action from the main menu

the right mouse button, select Change
Password Forced.
Result: The Edit Password window opens.

...................................................................................................................................................................................................
Place the cursor in the Old Password text box, then type in the old password.
...................................................................................................................................................................................................
Place the cursor in the New Password text box, then type in your new password.
...................................................................................................................................................................................................
Place the cursor in the Re-Enter New Password text box, then type in your new password
again.
...................................................................................................................................................................................................
Click on OK.
Important! Please note that any user administration changes will not take effect until
the next login session.
After changing your password you have to exit the Alcatel-Lucent 1830 PSS ZIC and
to relaunch a new session using your new password.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-62
Issue 1 June 2013

Procedure 2-12: Send a short free form text message to
other users
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Procedure 2-12: Send a short free form text message to other

users
When to use
Use this procedure to send a short free form text message to other users.
SEND-USER-MSG::ALL
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Users.
...................................................................................................................................................................................................
If you want to sent a

message
Then
to all users
Either by selecting Action from the main menu bar or by using

the context menu opened with the right mouse button, select
Send Message All.
to a single user
Select a user in the list displayed in the right part of the

Alcatel-Lucent 1830 PSS ZIC main menu.
Either by selecting Action from the main menu bar or by using
the context menu opened with the right mouse button, select
Send Message.
....................................................................................................................................................................................................................................
1830 PSS
2-63
Issue 1 June 2013

Procedure 2-12: Send a short free form text message to
other users
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Result: The Send User Message window opens.

...................................................................................................................................................................................................
Place the cursor in the Message text box, then type in the message to be submitted.
...................................................................................................................................................................................................
Click on Apply.
Result: If you have sent a message to all users, a User Message screen pops showing
your message. You can close this screen by clicking on Close.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-64
Issue 1 June 2013

Procedure 2-13: Modify command access security level
assigned to a TL1 command.
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................

When to use
Use this procedure to change the command access security level (CCAL - Command
Community Authorization Level) assigned to a TL1 command.
ED-CMD-SECU
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System NE Security TL1
Commands.
Select a TL1 Commands in the list displayed in the right part of the Alcatel-Lucent
1830 PSS ZIC main window.
You can select any one of the TL1 command codes excluding the following TL1
command codes (i.e. the following commands keep always the factory default value):
ACT-USER
CANC-USER
CANC-USER-SECU
DLT-USER-SECU
ENT-USER-SECU
ED-USER-SECU
ALW-USER-SECU
INH-USER-SECU
ED-CMD-SECU
....................................................................................................................................................................................................................................
1830 PSS
2-65
Issue 1 June 2013

Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
SET-ATTR-SECUDFLT
SET-ATTR-SECULOG
INIT-SSH-KEY
...................................................................................................................................................................................................
...................................................................................................................................................................................................
In the Command Community Authorization Level spin box select the desired value.
Additional information The Command Community Authorization Level, specifies
the command security level assigned to the specified TL1 command.
1-5
...................................................................................................................................................................................................

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-66
Issue 1 June 2013

Procedure 2-14: Display command access security level
assigned to a TL1 command
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Procedure 2-14: Display command access security level

assigned to a TL1 command
When to use
Use this procedure to display command access security level assigned to a TL1 command.
RTRV-CMD-SECU
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Users.
...................................................................................................................................................................................................
Result: The Properties General window opens displaying the command access
security level assigned to the TL1 command.

Reference: See Command access security level assigned to a TL1 command
(p. 2-68).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-67
Issue 1 June 2013

....................................................................................................................................................................................................................................


Parameter ...
Meaning...
Command
TL1 Command Code, specifies the TL1 command code for which
the security level is assigned.
The value can be any one of the TL1 command codes excluding the
following TL1 command codes (i.e. the following commands keep
always the factory default value):
Command Community
Authorization Level
ACT-USER
CANC-USER
CANC-USER-SECU
DLT-USER-SECU
ENT-USER-SECU
ED-USER-SECU
ALW-USER-SECU
INH-USER-SECU
ED-CMD-SECU
SET-ATTR-SECUDFLT
SET-ATTR-SECULOG
INIT-SSH-KEY
Specifies the command security level assigned to the specified TL1

command.
0-5
....................................................................................................................................................................................................................................
1830 PSS
2-68
Issue 1 June 2013

Procedure 2-15: Copy security sensible files or data from/to
an NE to/from a remote file server
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................

When to use
Use this procedure to copy security sensible files or data from/to an NE from/to a remote
file server.
Note: This procedure is allowed to security administrators only.
The following types of file transfer are supported:
NE Public SSH Key from NE to remote file server

NE Public SSL Key in PEM format from NE to remote file server
NE CSR file in PEM format from NE to remote file server

NE X509 Certificate file in PEM format from remote file server to NE
OMS X509 CA Root Certificate file in PEM format from remote file server to NE
User Activity Log (UAL) File in zipped text format from NE to remote file server
The following file names, for the files to be transferred, shall be applied:
id_rsa.pub, for the file with the NE Public SSH Key, generated by RSA, to be
transferred from NE to remote file server
id_dsa.pub, for the file with the NE Public SSH Key, generated by DSA, to be
transferred from NE to remote file server
sslcsr.pem, for the NE CSR file in PEM format, to be transferred from NE to RFS
sslcert.pem, for the NE X509 Certificate file in PEM format, to be transferred from
RFS to NE
COPY-RFILE-SECU
Before you begin
Required equipment
....................................................................................................................................................................................................................................
1830 PSS
2-69
Issue 1 June 2013

Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System Log File Transfer
Start Copy.
...................................................................................................................................................................................................
Result: The Security File Transfer window opens.
...................................................................................................................................................................................................
In the FROM spin box select the entity to be transferred.

The following types are supported:
LOCSSHKEY
Local NE SSH Public Key
LOCSSLKEY
Local NE SSL Public Key in PEM format
LOCCSRPEM
Local NE CSR File in PEM format
RFSX509PEM
Remote X509 Certificate File in PEM format
LOCALUAL
Local NE User Activity Log File in zipped text format

Additional information
...................................................................................................................................................................................................
In the TO spin box specify the entity that gets created as the result of the command
completion:
RFSSSHKEY
Remote NE SSH Public Key
RFSSSLKEY
Remote NE SSL Public Key in PEM format
RFSCSRPEM
Remote NE CSR File in PEM format
LOCX509PEM
....................................................................................................................................................................................................................................
1830 PSS
2-70
Issue 1 June 2013

Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Local X509 Certificate File in PEM format
RFSUAL
Remote File Server User Activity Log File in Text Zipped format)
The following table shows the allowed combinations for the parameters FROM and TO
FROM
TO
LOCSSHKEY
RFSSSHKEY
LOCALUAL
RFSUAL
...................................................................................................................................................................................................
In the field Protocol specify the protocol to be used.

Note: Only sftp is supported.
...................................................................................................................................................................................................
In the field LOCATION:User ID enter the user identifier used for the connection on the
RFS.
...................................................................................................................................................................................................
In the field LOCATION:Password enter the user password used for the connection on the
RFS.
...................................................................................................................................................................................................
In the field LOCATION:FtpHost enter the IP address of the host (the Remote File Server).
...................................................................................................................................................................................................
In the field LOCATION:Port enter the port number to connect to.

Most schemes designate protocols that have a default port number.
The default port number for sftp is 22.
...................................................................................................................................................................................................
10
In the field LOCATION:Url-Path specify the details of how the specified resource (i.e. the
directory where the file(s) reside) can be accessed.
The following syntax has to be used:
[/]<cwd1;>/<cwd2;>/.../<cwdN;>
where <cwd1;> through <cwdN;> are strings that identify directories.

With a leading '/' character, the path is interpreted as an absolute file path inside the RFS's
file system.
....................................................................................................................................................................................................................................
1830 PSS
2-71
Issue 1 June 2013

Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Without the optional leading `/` character, the path is interpreted as a file path relative to
the users's login directory.
...................................................................................................................................................................................................
11
In the field From Date and Time specify the beginning date and time used to filter the
logged events from the seculog buffer.
{03-37}-{01-12}-{01-31}-{00-23}-{00-59}- {00-59}
...................................................................................................................................................................................................
12
In the field To Date and Time specify the ending date and time used to filter the logged
events from the seculog buffer.
{03-37}-{01-12}-{01-31}-{00-23}-{00-59}- {00-59}
...................................................................................................................................................................................................
13
Click on Send.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-72
Issue 1 June 2013

....................................................................................................................................................................................................................................


Parameter ...
Meaning...
FROM
Specifies the entity to be transferred.

The following types are supported:
LOCSSHKEY
Local NE SSH Public Key
LOCALUAL
Local NE User Activity Log File in zipped text format

TO
Specifies the entity that gets created as the result of the command
completion:
RFSSSHKEY
Remote NE SSH Public Key
LOCALUAL
Remote File Server User Activity Log File in zipped text format
The following list shows the allowed combinations for the
parameters FROM and TO
LOCSSHKEY RFSSSHKEY
LOCALUAL RFSUAL
Protocol
Specifies the protocol to be used. Only sftp is supported.
LOCATION:User ID
Specifies the user identifier used for the connection on the RFS.
LOCATION:Password
Specifies the user password used for the connection on the RFS.
LOCATION:FtpHost
Specifies the IP address of the host (the Remote File Server).
LOCATION:Port
Specifies the port number to connect to.

....................................................................................................................................................................................................................................
1830 PSS
2-73
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter ...
Meaning...
LOCATION:Url-Path
Specifies the details of how the specified resource (i.e. the directory
where the file(s) reside) can be accessed.
[/]<cwd1>/<cwd2>/.../<cwdN>
[/]<cwd1;>/<cwd2;>/.../<cwdN;>
where <cwd1;> through <cwdN;> are strings that identify

directories.
With a leading '/' character, the path is interpreted as an absolute file
path inside the RFS's file system.
Without the optional leading `/` character, the path is interpreted as a
file path relative to the users's login directory.
From Date and Time
Specifies the beginning date and time used to filter the logged
events from the seculog buffer.
{03-37}-{01-12}-{01-31}-{00-23}-{00-59}- {00-59}
To Date and Time
Specifies the ending date and time used to filter the logged events
from the seculog buffer.
{03-37}-{01-12}-{01-31}-{00-23}-{00-59}- {00-59}
....................................................................................................................................................................................................................................
1830 PSS
2-74
Issue 1 June 2013

Procedure 2-16: Configure SSL authentication for ZIC to NE
communication (high-level procedure)
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Procedure 2-16: Configure SSL authentication for ZIC to NE

communication (high-level procedure)
When to use
Use this procedure to configure SSL authentication for ZIC to NE communication.

This task description serves as an overview of the individual procedures that must be
carried out.
Before you begin
Please refer to the individual procedures for information about the required privileges.
Required equipment
Instructions
Configuring the SSL authentication consists of the procedures listed below.

...................................................................................................................................................................................................
Procedure 2-18: Generate a new SSL key for SSL authentication (p. 2-77)
...................................................................................................................................................................................................
Procedure 2-19: Request a new certificate for SSL authentication (p. 2-79)
...................................................................................................................................................................................................
To upload certificate request, see Procedure 2-15: Copy security sensible files or data
from/to an NE to/from a remote file server (p. 2-69)
...................................................................................................................................................................................................
Download certificate, see Procedure 2-15: Copy security sensible files or data from/to
an NE to/from a remote file server (p. 2-69).
...................................................................................................................................................................................................
Procedure 2-17: Install a certificate for SSL authentication (p. 2-76)

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-75
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to install a new X.509 certificate generated and signed by NMS client,
in accordance to a CSR previously generated, onto the NE.
Once issued, this will trigger the NE to perform some consistency check on the certificate
file to be installed and, in case of successful validation, the certificate will be actually
installed on the NE.
Important! This is allowed to a security administrator only.
INIT-SSL-CERT
Before you begin
Prior to performing this task,
you must be logged into the Alcatel-Lucent 1830 PSS ZIC and the respective network
element.
in accordance to a CSR previously generated and submitted by the NE by means of
INIT-SSL-CSR command.
the X.509 certificate file (PEM format) to be installed, has to be preliminary
downloaded from NMS machine to the NE, see Procedure 2-15: Copy security
sensible files or data from/to an NE to/from a remote file server (p. 2-69).
Required equipment
Instructions
...................................................................................................................................................................................................
SSL&Certificates.
...................................................................................................................................................................................................
with the right mouse button, select Install Signed Certif..
Result: The access control rule is configured accordingly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-76
Issue 1 June 2013

Procedure 2-18: Generate a new SSL key for SSL
authentication
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................

authentication
When to use
Use this procedure to trigger the NE to generate a new Public/Private key pair associated
to the NE itself, and to be used in the context of SSL authentication.
A new SSL key is generated to replace the default SSL key and certificate, or to renew the
SSL key e.g. in the case that the security of the current SSL key can no longer be
guaranteed.
The generated key has to be embedded in a X.509 certificate, either self signed or issued
by a Certification Authority, to be installed onto the NE and used during the SSL
authentication phase. See Procedure 2-19: Request a new certificate for SSL
authentication (p. 2-79).
INIT-SSL-KEY
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Access Control Lists.
...................................................................................................................................................................................................
with the right mouse button, select Start SSL key generation.
....................................................................................................................................................................................................................................
1830 PSS
2-77
Issue 1 June 2013

authentication
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Result: The SSL key generation window opens.

...................................................................................................................................................................................................
Using the field Key Type specify the algorithm to generate the specified new NE key pair.
RSA
DSA
...................................................................................................................................................................................................
Using the field Key Length specify the length of the new NE key pair to be generated.
{512-4096}
...................................................................................................................................................................................................

Result: The new NE key pair is generated accordingly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-78
Issue 1 June 2013

Procedure 2-19: Request a new certificate for SSL
authentication
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
Procedure 2-19: Request a new certificate for SSL

authentication
When to use
Use this procedure to request a new certificate for SSL authentication.

INIT-SSL-CSR
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
with the right mouse button, select Start SSL key generation.
Result: The Request SSL Certificate window opens.
Reference: See Certificate for SSL authentication (p. 2-80).
...................................................................................................................................................................................................
Enter the needed parameters as described.

...................................................................................................................................................................................................

Result: The new certificate for SSL authentication is requested.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-79
Issue 1 June 2013

....................................................................................................................................................................................................................................

Fields and parameters
The following fields/parameters are available:

Field/parameter ...
Meaning...
TID
identifies the network node TID for the command.
CN
represents the domain name of the server. It is expected to be the NE

IP Address. e.g.: CN=151-98-32-56
Value:
ORG
{0-255}-{0-255}-{0-255}-{0-255}
represents the legal name the organization. e.g.: Alcatel Lucent.

Value:
ORGUNI
<Valid Organization Name>
represents the division of your organization handling the certificate.

e.g.: Optics Division.
Value:
LOC
<Valid Organization Unit Name>
represents the city where your organization is located. e.g.: Milan.

Value:
STATE
<Valid Location Name>
represents the state/region where your organization is located. This

shouldn't be abbreviated. e.g.: Italy.
Value:
COUNTRY
<Valid State/Region Name>
represents the two-letter ISO code for the country where your
organization is location, e.g.: IT.
Value:
MAIL
<Valid Two Letter Country ISO Code>
represents an email address used to contact your organization.

Quoted string.
Value:
<Valid Email Address>
....................................................................................................................................................................................................................................
1830 PSS
2-80
Issue 1 June 2013

authentication
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................

authentication
When to use
Use this procedure to to retrieve the current NE Public Key.

RTRV-SSL-KEY
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
with the right mouse button, select Retrieve SSL key .
Result: The SSL key window opens.
Reference: See Current NE Public Key. (p. 2-82).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-81
Issue 1 June 2013

....................................................................................................................................................................................................................................


Field/parameter ...
Meaning...
Key Type
The field Key Type specify the algorithm to generate the specified
new NE key pair.
Key Length
RSA
DSA
Specifies the length of the NE key pair.

Value:
NE SSL Public Key
{512-4096}
The currently active SSL Public Key for the NE (SSL Server) The
parameter is reported as a quoted string with PEM format
Value:
< NE SSL PUBLIC KEY CHARACTERS >
....................................................................................................................................................................................................................................
1830 PSS
2-82
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to configure RADIUS server attributes so that the client can
communicate with a server for authentication.
ENT-RADIUS-SERVER
RTRV-RADIUS-SERVER
Radius server
have access to the NE, but also grants the user the user's Privilege Level.
RADIUS is a networking protocol, based on RADIUS servers, that provides centralized
Authentication, Authorization and Accounting (AAA) services. The user sends a
connection request to a Network Access Server (NAS), which acts as RADIUS client and
sends a RADIUS access request to the RADIUS server.
The RADIUS server is provisioned with one or more user profiles. Based on the user
profile and user class definitions, the RADIUS server accepts or rejects the NAS request.
In turn the NAS accepts or, respectively, rejects the user connection.
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Radius server.
....................................................................................................................................................................................................................................
1830 PSS
2-83
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
with the right mouse button, select Create RADIUS Server Configuration.
Result: The Create RADIUS Server window opens.
...................................................................................................................................................................................................
Using the field Server Number select the RADIUS server to be used.
The valid values are the following:
RAD1
is first server name.
RAD2
is the second server name.

...................................................................................................................................................................................................
In the field IP Address enter the IP address of the specified RADIUS server (RAD1 or
RAD2).
{1-99, 101-126,128-223}-{0-255}-{0-255}-{0-25 5}
...................................................................................................................................................................................................
In the field Port enter the authentication port of the RADIUS server.
Valid values are from 1 to 65000. The default port value is 1812.
...................................................................................................................................................................................................
In the field Secret Key enter the shared secret key between the NE and the target
RADIUS server.
This key is an ascii string between 5 to 32 characters. The secret key is encrypted on the
NE using AES or 3DES..
<5-32 VALID PID CHARACTERS>
...................................................................................................................................................................................................
Using the field Status select the RADIUS server status to be used.
The server status refers to the NE configuration, i.e. whether the NE shall attempt to use
the specified server or not. It does not reflect the servers operational state and
reachability.
ENABLE
The RADIUS server is on-line.
DISABLE
....................................................................................................................................................................................................................................
1830 PSS
2-84
Issue 1 June 2013

....................................................................................................................................................................................................................................
The RADIUS server is off-line

...................................................................................................................................................................................................

Result: The Radius server is configured accordingly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-85
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify RADIUS server attributes.

ED-RADIUS-SERVER
RTRV-RADIUS-SERVER
Radius server
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Radius server.
....................................................................................................................................................................................................................................
1830 PSS
2-86
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select a RADIUS Server in the list displayed in the right part of the Alcatel-Lucent 1830
PSS ZIC main menu and click on Modify.
Result: The Modify RADIUS Server window opens.
...................................................................................................................................................................................................
In the field IP Address enter the IP address of the specified RADIUS server (RAD1 or
RAD2).
{1-99, 101-126,128-223}-{0-255}-{0-255}-{0-25 5}
...................................................................................................................................................................................................
In the field Port enter the authentication port of the RADIUS server.
Valid values are from 1 to 65000. The default port value is 1812.
...................................................................................................................................................................................................
In the field Secret Key enter the shared secret key between the NE and the target
RADIUS server.
This key is an ascii string between 5 to 32 characters. The secret key is encrypted on the
NE using AES or 3DES..
<5-32 VALID PID CHARACTERS>
...................................................................................................................................................................................................
Using the field Status select the RADIUS server status to be used.
The server status refers to the NE configuration, i.e. whether the NE shall attempt to use
the specified server or not. It does not reflect the servers operational state and
reachability.
ENABLE
The RADIUS server is on-line.
DISABLE
The RADIUS server is off-line

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-87
Issue 1 June 2013

Procedure 2-23: Set RADIUS server authentication
parameters
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................

When to use
Use this procedure to set the authentication parameters which are used during access to
the RADIUS servers.
SET-RADIUS-AUTH
RTRV-RADIUS-AUTH
Radius server
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Radius server.
....................................................................................................................................................................................................................................
1830 PSS
2-88
Issue 1 June 2013

Procedure 2-23: Set RADIUS server authentication
parameters
Alcatel-Lucent
1830
PSS
ZIC
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
with the right mouse button, select Set RADIUS Server Authentication.
Result: The Set RADIUS Server Authentication window opens.
...................................................................................................................................................................................................
Select the Radius Server to be modified and click Modify.

...................................................................................................................................................................................................
Using the field Authentication Order specify the authentication criteria for the user
when logging to NE.
Valid values are:
LOCAL
Authentication is based only on the local NE's security database.
RADIUS
The NE shall first search for the user ID in the local NE database. If the user ID is
found in the local database, then the user shall be authenticated via the local database.
Otherwise, the NE shall authenticate the user via RADIUS..
...................................................................................................................................................................................................
In the field Retries define the number of attempts that the NE will try to contact the
specified RADIUS server that has failed to respond to the initial request. If there is no
response from the server after the specified number of retries then the NE will try to
contact the second RADIUS server if one is provisioned (status: "Enabled").
The supported value range for retries is 0 to 100. The default value is 3.
...................................................................................................................................................................................................
In the field Timeout define the timeout (in seconds) for the NE to wait for a response
from the RADIUS server. The failure is declared after the timeout is elapsed.
The supported value range for timeout is 1 to 1000. The default value is 5.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-89
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete a RADIUS server.

DLT-RADIUS-SERVER
RTRV-RADIUS-SERVER
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Radius server.
...................................................................................................................................................................................................
Select the RADIUS Server to be deleted in the list displayed in the right part of the
Alcatel-Lucent 1830 PSS ZIC main menu and change it's status to Disabled. See
Procedure 2-22: Modify RADIUS server attributes (p. 2-86).
...................................................................................................................................................................................................
Select the RADIUS Server in the list displayed in the right part of the Alcatel-Lucent
1830 PSS ZIC main menu and click on Delete.
...................................................................................................................................................................................................
Click Apply to confirm.

Result: The Radius server is deleted.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-90
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
User management and administration procedures

on the WDM application using the WebUI
Overview
Purpose
The following procedures are to be used for user management. It is suggested to use
Security management and user administration on the WDM application (p. 2-14) as an
entry point for user administration activities.
Furthermore, it is recommended to have a list prepared of all the users that probably will
need to have access to the WebUI and the NEs, especially if several user logins are to be
created or modified for different NEs. The list should contain the designated user IDs,
associated passwords, access privileges and other related security parameters, and should
be as complete as possible.
Contents
2-93
2-94
2-97
2-98
2-99
2-100
2-101
The Sessions screen
2-102
2-104
2-105
2-106
2-107
2-108
2-109
2-110
2-111
CLI Logging
2-112
....................................................................................................................................................................................................................................
1830 PSS
2-91
Issue 1 June 2013

Overview
User management and administration procedures on the
WDM application using the WebUI
....................................................................................................................................................................................................................................
Procedure 2-36: Setting / viewing SNMP user activity logging properties
2-113
SNMP Logging
2-114
2-115
2-116
2-117
The All Logs screen
2-118
2-119
2-120
User Preferences
2-121
2-122
2-123
2-124
2-125
2-126
2-127
RADIUS Properties
2-128
2-129
2-130
2-131
2-132
2-133
2-135
2-136
....................................................................................................................................................................................................................................
1830 PSS
2-92
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create a user.

Before you begin
The following procedure are available via the WebUI after the user initially connects to
the NE and logs into the system (see The Alcatel-Lucent 1830 PSS WebUI (p. 20-42)).
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > Users.

...................................................................................................................................................................................................
Click Create.
Result: The Create User screen is displayed (see The Create User window
(p. 2-94)).
...................................................................................................................................................................................................
Enter appropriate information (see Configuring user accounts (p. 2-20) and The
Create User window (p. 2-94)) and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-93
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
User ID
<5-12 chars>
Indicates the unique user ID.

The first character must be an
alphabetic character.
Access Privilege
Observer
Provisioner
Level of access privilege

granted to this user.
Administrator
Status
Enabled
Disabled
Session Inactivity Timeout

(minutes)
{1-999}
Disabled (uncheck)
Indicates whether the user

access for this User ID is
enabled or disabled.
The amount of time that a
user session may remain
inactive before the user is
logged out and the session is
closed.
If disabled, the system-level
timeout value is used.
....................................................................................................................................................................................................................................
1830 PSS
2-94
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Password
Values/Format
Additional Info
Valid values for the Password
are 8 to 32 case-sensitive
alphabetic [a-z, A-Z], numeric
[0-9] or special characters.
A valid password must
contain at least 1 lowercase
alphabetic, 1 uppercase
alphabetic, 1 numeric and 1
special character. The
following special characters
are accepted as valid
characters for the Password:
% (percent sign), + (plus
sign), # (pound sign)_
(underscore) ! (exclamation
point), @ (at sign), $ (dollar
sign), (double quotation
mark), & (ampersand),
(apostrophe), ( (left
parenthesis), ) (right
parenthesis), * (asterisk), and
. (period). The first character
can be any alphabetic,
numeric or valid special
character, except the # (pound
sign).
In addition, the following
rules apply to the Password
value:
The password must not be

the same as the associated
User ID.
The password must not be

the reverse of the
associated User ID.
The password must not

have three consecutive
identical characters.
When modifying the

password, the new
password must not match
the old password.
....................................................................................................................................................................................................................................
1830 PSS
2-95
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Confirm Password
Values/Format
Additional Info
Must have the same value as
Password.
....................................................................................................................................................................................................................................
1830 PSS
2-96
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view or modify user details.

Before you begin
Instructions
Note: Appropriate privilege level is required to configure user accounts.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the desired user and click Details.

Result: User details are displayed. You can change privilege level or password, or
enable or disable the account.

...................................................................................................................................................................................................
Modify available fields (see Configuring user accounts (p. 2-20)and The User
Security Administration screen (p. 2-98)) and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-97
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
User ID
<5-12 chars>
Indicates the unique user ID.
Access Privilege
Service
Indicates the level of access

privilege granted to this user.
Administrator
Provisioner
Observer
Status
Enabled
Disabled
Session Inactivity Timeout

(minutes)
{1-999}
Disabled

The amount of time that a
user session may remain
inactive before the user is
logged out and the session is
closed.
If disabled, the system-level
timeout value is used.
Login Failures
<integer>
Number of login failures

since the last successful login
by this user.
Last Login
<date time>
Date and Time that the user

last logged into the NE.
Create
Displays a window for

entering data to create a new
user account.
Details
Displays details of the

selected user account.
Delete
Deletes the selected user

account.
....................................................................................................................................................................................................................................
1830 PSS
2-98
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to delete a user.

Before you begin
Instructions
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the desired user and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-99
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to change user passwords.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > Change Password.

...................................................................................................................................................................................................
Enter the old password and the new password, and confirm the new password. Then click
Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-100
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view or terminate user sessions.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > Sessions.

Result: All active sessions are displayed (see The Sessions screen (p. 2-102)).
...................................................................................................................................................................................................
To terminate a session, select the desired session and click Terminate.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-101
Issue 1 June 2013

The Sessions screen
....................................................................................................................................................................................................................................
The Sessions screen

Attribute
Values/Format
User ID
Additional Info
ID of the user that
successfully logged in and
started the session.
If there is no value, the
session has not been
successfully authenticated
with a valid login.
User Type
Unknown
Indicates the type of user.
CLI (Telnet)
CLI (SSH)
CLI (Console)
WebUI
Secure WebUI
TL1 (Raw)
TL1 (Telnet)
TL1 (SSH)
SNMP
Source
<PortName> or <IP
address>
Address indicating where the

user is connecting from. If the
connection was made over the
OAMP port, the value will be
the source IP address and port
number. Otherwise, the value
shall be GCC (if the
originator came over the
GCC), CIT (if the originator
was authenticated over the
CIT), OSC (if the originator
came over the OSC), or
RS232 (if the user is
connected over the serial link)
Login Time
<date/time>
Date and time that the user

logged in and the session was
started.
....................................................................................................................................................................................................................................
1830 PSS
2-102
Issue 1 June 2013

The Sessions screen
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Session ID
Unique identifier for the

session.
Terminate
Terminates the selected user

session.
....................................................................................................................................................................................................................................
1830 PSS
2-103
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view SNMP v3 users.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > SNMP v3 Users.

Result: All current SNMP v3 users are displayed (see The SNMP v3 Users screen
(p. 2-107)).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-104
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create SNMP v3 users.

Before you begin
Instructions
...................................................................................................................................................................................................

(p. 2-107)).
...................................................................................................................................................................................................
To create an SNMP v3 user, click Create.

Result: The Create SNMP v3 User window is displayed.
...................................................................................................................................................................................................
Enter User ID, Password, and Access Privilege information. and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-105
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to modify SNMP v3 users.

Before you begin
Instructions
...................................................................................................................................................................................................

(p. 2-107)).
...................................................................................................................................................................................................
To modify an SNMP v3 user, select the user and click Details.

Result: The SNMP v3 User Details window is displayed.
...................................................................................................................................................................................................
Enter the desired parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-106
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
User ID
<1-32 chars>
Unique identifier for the user.
Access Privilege
NMS
Level of access privilege

granted to this user.
Admin
Provisioner
Observer
Status
Enabled
Disabled

Create

entering data to provision a
new SNMP v3 user.
Details
Displays details of the

selected SNMP v3 user.
Delete
Deletes the selected SNMP v3

user.
....................................................................................................................................................................................................................................
1830 PSS
2-107
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view or modify system security attributes (see System
security features (p. 2-26)).
Before you begin
The following procedure is available via the WebUI after the user initially connects to the
NE and logs into the system (see The Alcatel-Lucent 1830 PSS WebUI (p. 20-42)).
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > System.

Result: The System Security Administration window with current settings is
displayed.
...................................................................................................................................................................................................
To modify existing value(s), enter desired value(s) and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-108
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view syslog properties.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Syslog> Properties.

Result: The Syslog Administration screen is displayed.
...................................................................................................................................................................................................
Enter syslog administration parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-109
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Server IP
<IP address>
Specifies the IP address of the

syslog server.
Port
{1-65535}
Specifies the port on the

syslog server used for system
logging.
Logging Threshold
Emergency
Specifies the minimum

priority level of the messages
to log in the system log.
Alert
Critical
Error
Warning
Notice
Info
Debug
Logging Enabled
(checkbox)
Enable or disable system

logging.
....................................................................................................................................................................................................................................
1830 PSS
2-110
Issue 1 June 2013

Procedure 2-35: Setting / viewing CLI user activity logging
properties
WDM
application
using
the
WebUI
....................................................................................................................................................................................................................................
Procedure 2-35: Setting / viewing CLI user activity logging

properties
When to use
Use the following procedure to set/view CLI user activity logging properties.
Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Syslog > CLI Logging.

Result: The CLI Logging screen is displayed.
...................................................................................................................................................................................................
Select CLI logging properties and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-111
Issue 1 June 2013

CLI Logging
....................................................................................................................................................................................................................................
CLI Logging
Attribute
Additional Info
Disable All Logging
Enables or disables activity logging for all

users accessing the network element from the
CLI, web interface, or TL1 session..
Admin
Configure the CLI user activity logging

options for admin-level users.
Read
Write
Provisioner
Read
Write
Service
Read
Write
Observer
Read
Write

options for provisioner-level users.

options for the service user ID.

options for observer-level users.
....................................................................................................................................................................................................................................
1830 PSS
2-112
Issue 1 June 2013

Procedure 2-36: Setting / viewing SNMP user activity
logging properties
WDM
application
using
the
WebUI
....................................................................................................................................................................................................................................
Procedure 2-36: Setting / viewing SNMP user activity logging

properties
When to use
Use the following procedure to set/view SNMP user activity logging properties.
Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Syslog > SNMP Logging.

Result: The SNMP Logging screen is displayed.
...................................................................................................................................................................................................
Select SNMP logging properties and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-113
Issue 1 June 2013

SNMP Logging
....................................................................................................................................................................................................................................
SNMP Logging
Attribute
Additional Info
Disable All Logging
Enables or disables activity logging for all

users accessing the network element via
SNMP.
Admin
Configure the SNMP user activity logging

options for admin-level users.
Read
Write
Provisioner
Read
Write
Service
Read
Write
Observer
Read
Write
NMS
Read
Write

options for provisioner-level users.

options for the service user ID.

options for observer-level users.

options for the NMS user ID.
....................................................................................................................................................................................................................................
1830 PSS
2-114
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view the security log.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Security.

Result: The Security Log is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-115
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Number
{1-2,147,483,647}
Number representing the

sequence when the
alarm/event was received by
the NE.
Time
<date time>
The date and time at which

the security event occurred.
Source IP
<IP address>
IP address of the user that

originated the security event.
Description
<0-255 chars>
Text description of the

security event.
Data
<0-255 chars>
Additional data about the

security event.
....................................................................................................................................................................................................................................
1830 PSS
2-116
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view all logs.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > All Logs.

Result: The All Logs window is displayed.
Note: All Logs includes not reported alarms.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-117
Issue 1 June 2013

The All Logs screen
....................................................................................................................................................................................................................................
The All Logs screen

Attribute
Value/Format
Additional Info
Number
{1-2,147,483,647}
Chronologically-ordered log
entry.
Time
<date time>

the alarm or event was raised.
Source
<shelf/slot/port>
Identifier of the component

on which the alarm/event
occurred.
Card
The type of card on which the

alarm/event occurred.
Category
Indicates the category of the

component where the
alarm/event occurred.
Alarm/Event Type
Critical
The type of alarm or event.
Major
Minor
State Change
User Action
General Event
Not Alarmed
None
Unknown
Not Reported
Security
Warning
Description
<0-255 chars>
Condition
SA
Identifies the type of

alarm/event being reported.
Yes
No
Data

reported alarm/event.
<0-255 chars>
Indicates if the alarm/event

affects service.
alarm/event.
....................................................................................................................................................................................................................................
1830 PSS
2-118
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to save a retrieved log to a file.

Before you begin
Instructions
...................................................................................................................................................................................................
When the log is retrieved (see previous procedures), click the Export to Excel symbol.
Note: To use the Export to Excel feature, Internet Explorer must be configured as
follows:
1. In the IE tools menu select Internet Options -> Connections - > LAN Settings ->
Advanced (under Proxy server options)-> Exceptions (add IP address of NE to
Exceptions)
2. Close all IE instances (windows) and re-establish the WebUI connection to the
NE.
Note: The user should also ensure the following in the Internet Browser: Under
Internet Explorer ->Tools ->Internet Options -> Security tab select the Customer
Level button; Scroll down to the ActiveX controls and plug-ins and set Initialize and
Script ActiveX controls not marked as safe for scripting to either Enable or Prompt.
Click OK, and when prompted Are you sure? click Yes. Click OK to close out the
Internet Properties window. When the Excel button is pressed from the WebUI, if
Prompt was selected in the ActiveX controls, a popup for an ActiveX control on this
page might be unsafe to interact with other parts of the page. Do you want to allow
this interaction? will appear. Click Yes and Excel will launch, opening a file with the
retrieved log info.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-119
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to set / view user preferences

Before you begin
Setting/viewing user preferences
Note: User preferences are stored on the local PC for each user and are remembered
from session to session; they are not stored on the NE.
...................................................................................................................................................................................................
In the WebUI, select Administration > User Preferences.

Result: The User Preferences screen is displayed.
...................................................................................................................................................................................................
Enter user preference parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-120
Issue 1 June 2013

User Preferences
....................................................................................................................................................................................................................................
User Preferences
Attribute
Value/Format
Additional Info
Alarm Auto-Refresh
(checkbox)
Indicates whether the Active

Alarm List will automatically
update when alarms raise or
clear.
Date and Time Format
mm/dd/yy HH:MM:SS
Indicates the format for

displaying date/time values.
AM/PM
dd-mm-yy HH:MM:SS
Date and Time Display
Use NE Date/Time (default)

Convert to Local PC
Date/Time
The default value retains the

NE date and time without
converting to the local time
on the PC. If you choose
Convert to Local PC
Date/Time, the setting is
saved on the PC for future

logins.
Display Shelf Description On
Equipment Tree
(checkbox)
Indicates if the text entered

for Shelf Description will be
displayed on the Equipment
Tree.
....................................................................................................................................................................................................................................
1830 PSS
2-121
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create a RADIUS server. Refer to RADIUS

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > RADIUS > Servers.
Result: The RADIUS Server screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create RADIUS Server screen is displayed.
...................................................................................................................................................................................................
Enter parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-122
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Server
RAD1
Identifier of the RADIUS

server.
RAD2
Server IP
<IP address>
IP address of the RADIUS

server.
Port
1-65000
Authentication port of the

RADIUS server.
1812 (default)
Shared Secret
<5-32 chars>
The shared secret key

between the NE and the
RADIUS server. The secret
key is encrypted on the NE.
Confirm Shared Secret
<5-32 chars>

Shared Secret.
Status
Enabled
Enable or disable the

RADIUS server.
Disabled
....................................................................................................................................................................................................................................
1830 PSS
2-123
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view/modify a RADIUS server. Refer to RADIUS

Before you begin
Instructions
...................................................................................................................................................................................................
Result: The RADIUS Servers screen is displayed.
...................................................................................................................................................................................................
Select the RADIUS server and click Details.

Result: The RADIUS server details are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-124
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Server
Values/Format
RAD1
RAD2
Additional Info
Identifier of the RADIUS
server.
Server IP
<IP address>
IP address of the RADIUS

server.
Port
Range: {1-65000}
Authentication port of the

RADIUS server.
1812 (default)
Shared Secret
<5-32 chars>
The shared secret key

between the NE and the
RADIUS server. The secret
key is encrypted on the NE.
Confirm Shared Secret
<5-32 chars>

Shared Secret.
Server Enabled
(checkbox)
Enable or disable the

RADIUS server.
....................................................................................................................................................................................................................................
1830 PSS
2-125
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to delete a RADIUS server. Refer to RADIUS

Before you begin
Instructions
...................................................................................................................................................................................................
Result: The RADIUS Servers screen is displayed.
...................................................................................................................................................................................................
Select the RADIUS server and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-126
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision RADIUS properties. Refer to RADIUS

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Security > RADIUS > Properties
Result: The RADIUS Properties screen is displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-127
Issue 1 June 2013

RADIUS Properties
....................................................................................................................................................................................................................................
RADIUS Properties
Attribute
Values/Format
Additional Info
Timeout (seconds)
{1-1000}
This is the timeout for the NE

to wait for a response from
the RADIUS server.
Retries
{1-100}
If there is no response from

the server after the specified
retries, the NE will try to
contact the second RADIUS
server if one is provisioned
and has Status = Enabled.
Authentication Order
Local
Local authentication is
RADIUS
based on the local NEs

security database
RADIUS, then Local
RADIUS authentication is
based on the RADIUS

servers database
RADIUS, then Local
authentication is attempted
first using the RADIUS server
database. If the RADIUS
server is not reachable, then
authentication is based on the
NEs security database.
....................................................................................................................................................................................................................................
1830 PSS
2-128
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to create trap destinations. Refer to SNMP authentication
(p. 2-37).
Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > SNMP > Trap Destinations

Result: The SNMP Trap Destinations screen is displayed (see The SNMP Trap
Destinations screen (p. 2-133)).

...................................................................................................................................................................................................
Click Create.
Result: The Create SNMP Trap Destinations screen is displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-129
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
ID
<1-32 chars>
Unique identifier for the trap

destination.
Destination IP
<IP address>

server that serves as the trap
destination.
Port
Specifies the port of the

destination.
Timeout
1500 (default)
Specifies the time (round

trip), in hundredths of a
second, after which the
connection times out if no
reply is received. Following a
timeout, a retry is attempted,
up to the number of retries
specified by Retry Count.
Retry Count
{0-255}
Specifies an integer value for

the number of times the
network element will attempt
to retry the connection in the
event of a timeout.
3 (default)
SNMP Version
v1
v2c (default)
v3
NMS Station Group ID
{0-65535}
Specifies the SNMP version

to use when formatting the
trap.
Specifies an integer value that
uniquely identifies the NMS
workstation serving as the
trap destination. Use 0 for all
third party SNMP trap
servers.
....................................................................................................................................................................................................................................
1830 PSS
2-130
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to delete trap destinations. Refer to SNMP authentication
(p. 2-37).
Before you begin
Instructions
...................................................................................................................................................................................................

Result: The SNMP Trap Destinations screen is displayed.
...................................................................................................................................................................................................
Select the Trap Destination and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-131
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to view trap destinations. Refer to SNMP authentication
(p. 2-37).
Before you begin
Instructions
...................................................................................................................................................................................................

Result: The SNMP Trap Destinations screen is displayed.
...................................................................................................................................................................................................
Select the trap destination and click Details.

Result: The Trap Destination details are displayed
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-132
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
ID
<1-32 chars>
Unique identifier for the trap

destination.
Destination IP
<IP address>

destination.
Port
Specifies the port of the

destination.
Timeout
1500 (default)
Specifies the time (round

trip), in hundredths of a
second, after which the
connection times out if no
reply is received. Following a
timeout, a retry is attempted,
up to the number of retries
specified by Retry Count.
Retry Count
{0-255}
Specifies an integer value for

the number of times the
network element will attempt
to retry the connection in the
event of a timeout.
3 (default)
SNMP Version
v1
v2c (default)
v3
NMS Station Group ID
Create
Range: {0-65535}
Specifies the SNMP version

to use when formatting the
trap.
Specifies an integer value that
uniquely identifies the NMS
workstation serving as the
trap destination. Use 0 for all
third party SNMP trap
servers.
trap destination.
....................................................................................................................................................................................................................................
1830 PSS
2-133
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Delete
Value/Format
Additional Info
Delete a selected trap
destination.
NOTE:Traps are not sent to a
deleted destination. Ensure
that other destinations are
available and operational
before deleting an existing
destination.
....................................................................................................................................................................................................................................
1830 PSS
2-134
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to view/modify community strings. Refer to SNMP

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > SNMP > Community Strings

Result: The SNMP Community Strings are displayed.
...................................................................................................................................................................................................
To modify Community Strings, enter appropriate values in the respective fields and click
Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
2-135
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Administrator
<1-20 chars>
Community string for the

administrator community.
SNMP community strings
function as passwords that are
embedded in every SNMP
packet to authenticate access
to the Management
Information Base (MIB) on
the network element.
admin_snmp (default)
Observer
<1-20 chars>
observer_snmp (default)
Provisioner
<1-20 chars>
provisioner_snmp (default)
NMS
<1-20 chars>
nms_snmp (default)
3rd Party NMS
<1-20 chars>
3rdpnms_snmp (default)

observer community.
provisioner community.
NMS community.
Community string for a 3rd
party NMS community.
....................................................................................................................................................................................................................................
1830 PSS
2-136
Issue 1 June 2013
3 ata communication setup

D
procedures
Overview
Purpose
This chapter describes the procedures which have to be performed for the data
communication setup.
Contents
3-4
Basic DCN principles
3-5
3-8
DCN protocols and services
3-9
General Communication Channel
3-10
3-11
3-12
User interfaces
3-13
3-18
Gateway NE (GNE) management
3-21
CIT port
3-24
3-25
Procedure 3-1: Change the Site Identifier (SID)
3-27
Procedure 3-2: Retrieve IP and MAC addresses
3-29
View IP Addresses
3-30
Procedure 3-3: Set the FLC IP Addresses of the NE
3-31
Procedure 3-4: Set the loopback IP address of the NE
3-34
Procedure 3-5: Set the control plane IP addresses of the NE
3-36
...................................................................................................................................................................................................................................
1830 PSS
3-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 3-6: Modify the TCP/IP stack parameters
3-38
3-41
3-42
3-43
3-44
3-45
Procedure 3-11: Modify the ASAP of the Customer LAN interface
3-57
Procedure 3-12: Configure LAN interfaces to form a multi-shelf compound
3-59
Procedure 3-13: Create a network interface on the embedded communication

channels (ECCs)
3-63
3-66
3-67
3-69
Procedure 3-17: Enable or disable a network interface
3-71
Procedure 3-18: Delete a network interface and an ECC protection group
3-73
3-75
3-78
3-80
3-81
Procedure 3-23: Delete a static IP route from the IP routing table
3-85
Procedure 3-24: Create the NTP Server address
3-87
Procedure 3-25: Manage the NTP server address
3-89
Procedure 3-26: Retrieve the NTP sync state
3-91
Procedure 3-27: Configure the global OSPF parameters
3-93
3-96
3-98
Procedure 3-30: Delete an OSPF area
3-100
Parameters of a OSPF Area
3-101
Procedure 3-31: Configure the IP address range for the OSPF area
3-102
3-104
Procedure 3-33: Configure OSPF interface parameters
3-106
3-109
3-111
....................................................................................................................................................................................................................................
1830 PSS
3-2
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 3-35: View network (NE name, NE IP, software release) map
information
3-113
Network Map
3-114
Procedure 3-36: View / modify IP route metric settings
3-115
IP Route Redistribute Metric Settings
3-116
Procedure 3-37: Create IP static route
3-117
Create Static IP Route
3-118
Procedure 3-38: View all IP routes
3-119
IP Routes
3-120
Procedure 3-39: Delete IP static route
3-121
Procedure 3-40: Create OSPF area
3-122
Create OSPF Area
3-123
3-127
OSPF Areas
3-128
Procedure 3-42: View/modify OSPF details
3-132
OSPF Area Details
3-133
Procedure 3-43: Delete OSPF area
3-137
Procedure 3-44: Configure orderwire function
3-138
Procedure 3-45: Create / view NTP server
3-140
Create NTP Server
3-142
3-143
NTP Properties
3-145
Procedure 3-47: Create/view NTP keys
3-146
Create NTP Key
3-147
3-148
Date and Time Administration
3-149
....................................................................................................................................................................................................................................
1830 PSS
3-3
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This chapter deals with the basic theoretical background of Data Communication
Networks (DCNs) and provides DCN configuration guidelines for Alcatel-Lucent
1830 PSS systems.
Contents
3-5
3-8
3-9
3-10
3-11
....................................................................................................................................................................................................................................
1830 PSS
3-4
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
This subsection serves as an entry point, it describes the basic DCN principles.
Purpose of a data communication network
A Data Communication Network (DCN) is used for the exchange of management data.
This section provides an overview of the Data Communication Network and describes the
type of communication between the nodes in the network and the used protocols.
OTN management network
The OTN management network is an overlay network of the transmission network. A

management system and the network elements together are the nodes of this network. The
customer LAN, Generic Communication Channels (GCCs; see General Communication
Channel (p. 3-10)) provide the physical connection between the nodes.
External DCN Interfaces
Fast Ethernet LAN ports (OAMP) provide the interface between the OTN management
network and the External (outband) DCN Topology towards the management system.
OAMP LAN redundancy is ensured when connecting both OAMP LAN ports from the
two FLC cards to LAN switches that support Rapid Spanning Tree protocol (RSTP)
according to IEEE802.1D-2004.
For initial configuration the Zero Installation Craft application (ZIC) can be accessed via
the CIT LAN ports on each FLC card while afterwards the OAMP LAN ports have to be
used. In addition the CIT LAN ports can be used for debug access. In case the network
element consist of main and extension shelves only the LAN ports on the main shelf FLC
cards provide management and ZIC access.
Embedded Communication Channels ECC
The Embedded Communication Channels (ECC) are part of the OTN line signal (GCC)
and are used for inband transport of management information. The ECC terminate on the
OTN port cards that are connected via shelf internal links (ECC Link) or inter-shelf LAN
connections (ILAN) to the First-Level-Controller (FLC) where the communication stack
is running.
The physical communication between each OTN port card and the first level controller in
the same shelf is based on TDM full duplex point-to-point links operating at 19.44 Mb/s
bitrate as a point-to-point serial link. Each ECC link pair from the OTN port cards are
duplicated to both shelf FLC_A and FLC_B as a double star topology.
....................................................................................................................................................................................................................................
1830 PSS
3-5
Issue 1 June 2013

....................................................................................................................................................................................................................................
For multishelf configuration, ECC traffic from extension shelves is transported from
extension shelf FLC to main shelf FLC via GbE ILAN.
Per system, there is a maximum number of ECC channels of 512, independent of
bandwidth.
Table 3-1
Maximum number of ECC channels supported per shelf
ECC Channel
Type
ECC Bandwidth Equivalents
Number of supported Channels

per shelf
GCC
(OTU2/ODU2)
256
GCC
(OTU2e/ODU2e)
168
GCC
(OTU3/ODU3)
64
GCC
(OTU3e2/
ODU3e2)
64
GCC
(OTU4/ODU4)
20
64
DCN protocols
The following table shows the TCP/IP protocol stack:

Layer
Name
Service / Protocol
Application
TL1 over SSH, SSH for debug access, control plane CLI over SSH,
SSH file transfer (SFTP), ntp, HTTPS (ZIC), RMI over SSL/TLS
(ZIC), CORBA-MTNM (ASON Mgmt of control plane)
Presentation
Session
Transport
TCP, UDP
Network
IPv4, ICMP, OSPF, ARP or IPv4 encapsulated in IPv4 (RFC2003 or

RFC2784)
Data Link
PPP over HDLC (RFC 1662),

IPCP (RFC 1332), LCP (RFC
1661),
MAC (802.1D),
Physical
GCC
802.3 Ethernet
....................................................................................................................................................................................................................................
1830 PSS
3-6
Issue 1 June 2013

....................................................................................................................................................................................................................................
Management protocol: TL1
The management of Alcatel-Lucent 1830 PSS s based on the use of the Transaction
Language 1 (TL1, defined by Telcordia Technologies standards (formerly Bellcore).
....................................................................................................................................................................................................................................
1830 PSS
3-7
Issue 1 June 2013

....................................................................................................................................................................................................................................

Background information
Guidelines
Please observe the following engineering guidelines when configuring a DCN with
Alcatel-Lucent 1830 PSS systems involved:
TL1 is supported via the following TCP ports:

Telnet encoded TL1 over SSH on port 6085
Raw encoded TL1 over SSH on port 6084
Raw encoded TL1 on port 3082 (unencrypted)
75 simultaneous telnet encoded connections are supported (all over port 6085)
75 simultaneous raw encoded connections are supported (each either over port 6084
or over port 3082)
The NE supports 1 user session per TCP connection

The NE supports up to 512 ECC in total over all shelves
The NE supports up to 512 ECC bandwidth equivalents per shelf, which can be
grouped to form ECCs.
An OTU2/ODU2 GCC uses two (2) ECC bandwidth equivalent.

An OTU2e/ODU2e GCC uses three (3) ECC bandwidth equivalent.
An OTU3/ODU3 GCC uses eight (8) ECC bandwidth equivalent.
An OTU3E2/ODU3E2 GCC uses eight (8) ECC bandwidth equivalent.
An OTU4/ODU4 GCC uses eight (20) ECC bandwidth equivalent.

As a gateway network element (GNE), the NE supports ECC communications to at
least 1500 nodes distributed over 32 separate pairs of ECCs on 32 ring or APS
subnetworks.
Note: Normally, for large networks it is desirable to configure an additional GNE for
every 30-40 managed nodes.
Max number of IP-in-IP tunnels supported is 64.

The NE can be connected to up to three non-backbone OSPF areas, plus the backbone
OSPF area.
The NE supports up to 500 nodes in an OSPF area.
Related information
For related information please refer to:
General Communication Channel (p. 3-10)
....................................................................................................................................................................................................................................
1830 PSS
3-8
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
Alcatel-Lucent 1830 PSS network elements support the exchange of management

information over GCC and Ethernet over LAN.
The Alcatel-Lucent 1830 PSS OS interfaces supported include the following:
TL1 over SSH (for system management function)

SFTP over SSH (for software download, database backup and restore).
CORBA-MTNM (Control Plane (GMRE) management)
Linux Root Access over SSH

Secure ZIC access via SSL/TLS (HTTPS)
GMRE CLI management via SSH
....................................................................................................................................................................................................................................
1830 PSS
3-9
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The General Communication Channel (GCC) was defined by ITU-T Recommendation

G.709 as in-band channel used to carry management and signaling information between
OTN elements.
Two types of GCC are available:
GCC0 - two bytes within OTUk overhead. GCC0 can be used to carry management
information.
GCC1/GCC2- four bytes (each of two bytes) within ODUk overhead. These bytes can
be used for management information or for control-plane signaling information
(GCC2 is not supported in current relase).
GCC bandwidth depends on line rate. For example GCC0 bandwidth in case of OTU2 is
about 1.3 Mbit/s as for OTU3 its bandwidth is about 5.2 Mbit/s.
....................................................................................................................................................................................................................................
1830 PSS
3-10
Issue 1 June 2013

NE firewall with provisionable IP access control lists (IP

ACL)
....................................................................................................................................................................................................................................

Overview
The Alcatel-Lucent 1830 PSS supports Internet Protocol Access Control Lists.
The Internet Protocol Access Control Lists are administered on a per NE basis. They meet
U.S. Government security requirements and corporate security requirement. IP ACLs
cover source and/ or destination IP addresses, protocols and ports. They include blocking
source/destination IP addresses, ports and protocol IDs.
For detailed information refer to the Alcatel-Lucent 1830 PSS DCN Planning and
Engineering Guide (Photonic applications), chapter DCN configuration, Security, NE
firewall with provisionable IP access control lists (IP ACL).
....................................................................................................................................................................................................................................
1830 PSS
3-11
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section deals with the basic theoretical background of Data Communication
Networks (DCNs) on the WDM application.
Contents
User interfaces
3-13
3-18
3-21
CIT port
3-24
....................................................................................................................................................................................................................................
1830 PSS
3-12
Issue 1 June 2013

User interfaces
....................................................................................................................................................................................................................................
User interfaces
Overview
The NE hosts LAN, serial, and debug interfaces sufficient to support EMS, local craft
terminal and serial or LAN based processor access for debug purposes. The NE supports
a single LAN IP address (Router ID) for all LAN functions. This address is provisionable
and is required when bringing up the system. This is the IP address used for all IP
communications over the OSC, GCC0, and OAMP if the OAMP port assumes the Router
ID.
A Craft Interface Terminal (CIT) interface provides access for local craft workers to
WebUI, CLI, and TL1 interfaces via local craft PCs. The WebUI interface provides a
graphical user interface to the node software using HTML, JavaScript, and Java. The
application runs on the NE and is controlled and viewed through a standard web browser
that is provided by the PC.
A local craft terminal (laptop or PC) connected either through a serial or a LAN interface
can establish TL1 or CLI connections to any NE reachable via the local NE. In addition,
the LAN interfaces can establish SNMP connections to any SNMP management system
that is reachable via the local NE.
On initial turn-up, the systems IP address (Router ID) is 172.16.0.1. The Router ID can
be provisioned via a connection to the serial craft port using the appropriate CLI or TL1
command. The Router ID can also be provisioned via the CIT port, whereby the user
simply connects his laptop to the CIT port of the master Equipment Controller (EC) and
accesses the WebUI.
Note: The following applies to the CIT:
When a user manually configures the CIT Port Admin State, the CIT Auto State is
disabled
When a user manually disables the CIT Auto State the CIT Port Admin State is
automatically set to the default value of Enabled.
Web User Interface (WebUI)
The web user interface (WebUI) provides web-based access to the network element (NE).
The WebUI interface is accessed using a web browser running on a computer that is
connected via Ethernet to the NE, either directly or over a LAN. The WebUI supports
provisioning, administration, performance monitoring, and display of alarms and
conditions from the NE. It provides an intuitive, easy-to-use tool to assist in the initial
installation and troubleshooting of NEs.
....................................................................................................................................................................................................................................
1830 PSS
3-13
Issue 1 June 2013

User interfaces
....................................................................................................................................................................................................................................
Command Language Interface (CLI)
The Command Line Interface (CLI) is a line-oriented user interface that runs on the NE.
A user can access the CLI using a terminal device connected to the NE. The CLI provides
commands that allow the user to configure, manage, and monitor the NE, the NE
interfaces, and the services running on the NE.
Transaction Language 1 (TL1)
TL1 is a common protocol for NE management. The Alcatel-Lucent 1830 PSS TL1
interface is a text-based command line interface that allows the operator to configure and
manage Alcatel-Lucent 1830 PSS hardware, software, and services.
Note: TL1 is functionally and structurally defined by Telcordia documents such as
GR-831, GR-199 & GR-474.
Simple Network Management Protocol (SNMP)
SNMP is used in the management of various types of networks. The SNMP

communications occur over the Alcatel-Lucent 1830 PSS control network. SNMP has two
types of entities: management network elements (managers) and managed network
elements (agents). There are instances when the agent must notify the manager of an
event it has experienced without first having received a request from the manager. The
agent does this through traps. SNMP traps, therefore, are asynchronous messages from a
network element agent to a network manager that signals an event that may require user
attention.
In an Alcatel-Lucent 1830 PSS network, the 1354 RM-PhM or other external operations
system (such as surveillance center) acts as the management network element or manager.
The Alcatel-Lucent 1830 PSS network element acts as a managed network element or
network element agent. Traps are messages that the Alcatel-Lucent 1830 PSS network
element sends to the 1354 RM-PhM or external management system on an as-needed
basis to notify the manager of events the network element has experienced. Besides
autonomous messages (such as traps), the SNMP manager can retrieve or modify the NE
configuration (using GET or SET functions).
Note: Alcatel-Lucent 1830 PSS supports SNMP versions v1, v2c, and v3 of the
protocol.
User Panel (USRPNL)
The Alcatel-Lucent 1830 PSS provides a User Panel (USRPNL) located on the main
shelf, which supports the majority of communication connections for the NE. This user
panel includes the following ports:
Craft serial connection via DB9

Craft serial connection via USB-B
OAMP LAN connection via RJ45
....................................................................................................................................................................................................................................
1830 PSS
3-14
Issue 1 June 2013

User interfaces
....................................................................................................................................................................................................................................
VoIP LAN connection via RJ45

E1/E2 LAN connection via RJ45
Note: The user panel OAMP port was meant to connected to a router/switch. In a
fixed configuration. When connected to a PC/laptop, a crossover cable must be used.
In auto-negotiation mode, either straight or crossover cable can be used.
There are four (4) general purpose switched auto-sensing LAN ports (10/100BaseTX), for
connection to EMS/NMS, VoIP, and externally managed devices. The four general
purpose switched auto-sensing LAN ports on the user panel are as follows:
The OAMP port is used to connect to the External Management System (EMS) and is
the main control interface to the NE. The signaling format is 10/100BaseT. By
default, the OAMP LAN inherits the Router ID IP address when the OAMP LAN port
is enabled for service. However, the user is free to change the IP address of the
OAMP LAN port.
The VoIP port is used to connect to an IP phone. With IP phones at every site,
customers/field technicians can talk to one another simply by dialing the IP address of
the destination phone. The IP address and status of the port can be user provisioned.
There are two External LAN ports (which can be used to connect to externally
managed devices), labeled E1-LAN and E2-LAN. These ports are auto-sensing, so
either a cross-over or straight-thru Ethernet cable can be used.
The ports designated as the OAMP and Craft ports on the USRPNL, support access to the
CLI and TL1 commands. Further, the serial craft port (which is the DB-9/USB-B port)
supports only CLI and TL1, and the OAMP port also supports SNMP management. The
VoIP port on the USRPNL is disabled by default. External IP address and MAC address
remain fixed and follow the active LAN ports on the USRPNL. There is one MAC for the
OAMP port and one MAC for the VoIP port. The Alcatel-Lucent 1830 PSS NE's MAC
addresses associated with the LAN ports on the USRPNL are installed/assigned at the
factory.
Note: The USRPNL status LED reflects status of the USRPNL itself rather than shelf
status.
Attention: The OAMP port supports both fixed configuration and auto mode. It is
provisionable via CLI or WebUI. It is not recommended to have one side as auto and
other as fixed configuration. The configuration should match on either side.
The user panel OAMP port was meant to connected to a router/switch. In a fixed
configuration, when connected to a PC/laptop, a crossover cable must be used. In
auto-negotiation mode, either straight or crossover cable can be used.
User panel replacement
After an in-service replacement of the User Interface Panel, it is necessary to synchronize

the USRPNL with the Network Element database in order to avoid a "database invalid
alarm". This can be done via the WebUI using the following procedure.
....................................................................................................................................................................................................................................
1830 PSS
3-15
Issue 1 June 2013

User interfaces
....................................................................................................................................................................................................................................
Synchronize the USRPNL with the Network Element database

1. From the WebUI menu, select Administration > Database > USRPNL Replacement
Update.
2. In the USRPNL Replacement Update window, select Synchronize USRPNL with
Network Element Database: and click Apply.
Note: For detailed procedure on Replacing User Panel and detailed procedure for
User Panel replacement interrupted by a restart, see the Alcatel-Lucent 1830
Photonic Service Switch (PSS) Release 6.0 Maintenance and Trouble-Clearing Guide.
Craft interface
The NE supports two craft ports including a female (DB9) and a USB-B port. Both ports
support local RS-232C serial interface for connection to a CIT via serial link.
Either the DB9 port or the USB-B port can be used to connect serially to the NE.
However, only one port can be active at any given time. The NE automatically detects the
presence of a laptop (or any equivalent active device) when it is connected to the USB-B
port on the USRPNL. When both USB-B port and DB9 ports are simultaneously
connected, preference is given to the USB-B port. The USB-B port becomes active, and
the DB9 port is rendered inactive.
Note: The parity setting for the USB port must be set to Odd. The parity setting for
the DB9 interface must be set to None.
Equipment controller (EC)
Every PSS-32 and PSS-16 shelf contains one or two ECs (depending on whether
redundancy is desired). The EC provides four auto-sensing RJ45 LAN ports. The first
port (labeled CIT) located at the topmost of the EC, is dedicated for CIT connection. The
CIT port is active for ECs residing on the master shelf and disabled for ECs residing on
sub-shelves. The user may plug the CIT laptop into either of the Master ECs CIT port
and the SW will auto switch to the active EC.
Configurable attribute values on the two Master CIT ports are always the same; updating
the values on one port will automatically update the values on the other port. However,
when a newly introduced redundant EC is installed, CIT port data from the first EC would
need to be copied to the CIT port on the new EC.
The CIT port supports DHCP server. When a connection (e.g. using a laptop) is detected,
the NE provides an IP address in response to the DHCP request from the laptop. The CIT
port allows the client to connect locally to manage the NE, and it can also allow the client
to connect to any remote NE reachable by the local NE. The port also supports SNMP
(via 1354 RM-PhM) and FTP.
....................................................................................................................................................................................................................................
1830 PSS
3-16
Issue 1 June 2013

User interfaces
....................................................................................................................................................................................................................................
The available addresses start at the beginning of the network address range as long as
they don't conflict with either the broadcast or local address. The DHCP server assigns the
IP to the client PC when connected to CIT port in the following manner:
If assign 192.168.5.1/24, and the dhcp_range is 5, the available addresses are

192.168.5.2,3,4,5,6

192.168.5.1,2,3,4,6
192.168.5.1,2,3,4,5
192.168.5.1,2,3,4,6
Note: The WebUI does not run the full features like the 1354 RM-PhM. The CIT port
will only provide basic NE management (for local and remote management via
SNMP). IP Routing functions in 1830 PSS-32/PSS-16/PSS-32S and Alcatel-Lucent
1830 PSS-1 have to be configured so that all NEs intended to be managed, are
reachable from the local NE. In other words, IP applications from any external DCN
network will work only when there is full IP reach capability to every GNE and RNE
in the network.
The bottom two ports on the EC (labeled ES1 and ES2) are used to connect to
Alcatel-Lucent 1830 PSS extension shelves (sub-shelves). The 1830 PSS NE may be
comprised of multiple 1830 shelves. In order to enable protected communication between
1830 PSS shelves which comprise one NE (single TID), ES1/ES2 ports on these shelves
need to be connected in a daisy-chain fashion.
Note: Direct cabling of ES1/ES2 ports between two different 1830PSS nodes may
impact the ethernet connectivity of all XCOM ports such as OAMP, VOIP, E1, E2 &
CIT.
Failure of any EC in a duplex controller configuration does not prohibit communication
between the affected sub-shelf and the main shelf. Likewise, failure of any EC in a
simplex controller configuration does not prohibit communication between the main shelf
and all other sub-shelves, unless the simplex EC is the controller for the master Shelf.
Note: For detailed procedure on Replacing Equipment Controller, see the
Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 6.0 Maintenance and
Trouble-Clearing Guide.
Matrix and Controller Card (MTC1T9)
Every Alcatel-Lucent 1830 PSS-32S shelf contains two MTC1T9 cards. Like the EC, it
has CIT, ES1 and ES2 ports. Since the PSS-32S is always configured as an extension
shelf, the CIT port is disabled. The ES1 and ES2 ports are used to connect to the main
shelf and other extension shelves.
....................................................................................................................................................................................................................................
1830 PSS
3-17
Issue 1 June 2013

....................................................................................................................................................................................................................................
The basic communications network architecture for the Alcatel-Lucent 1830 PSS includes
all LAN interfaces, OSC interfaces, and GCC interfaces. LAN interfaces include the
OAMP, VoIP, E1, E2, CIT, and Extension Shelf (ES) connections. The OSC interfaces can
vary from one up to 8, one for each degree. The OSC carries node-to-node
communication, sharing of OSPF LSAs, wavetracker keys, SCOT messages, etc.
Note: Wave key opaque LSAs can only be enabled in one OSPF Area.
Note: The external communication (Voice/data) through the LAN ports (VoIP, OAMP,
E1, E2) in the User Interface Panel (USRPNL) are lost (dropped) when the active
controller (EC) fails (by autonomous or manual switchover command). The
communication will be established again when the EC becomes active. This also
applies to OSC and GCC as well.
For the communications network, static routes or OSPF must be used.
The GCC interfaces can vary from 1 up to 32, depending on the number of supported
Optical Transponders (OT's) that are provisioned for GCC0 termination.
Note: GCC0 terminations on the Alcatel-Lucent 1830 PSS system are supported by
the following:
112PDM11 OTL4.4 line port
11DPE12(A/E) OTU2 line port

11DPM12 OTU2 line port
11QPA4 OTU2 client port
11QPA4 OTU2 line port
11QPE24 OTU2 X port

11QPEN4 OTU2 client port
11QPEN4 OTU2 line port
11STAR1 OTU2 client port
11STAR1 OTU2 line port

11STAR1A OTU2 client port
11STAR1A OTU2 line port

11STMM10 OTU1 client port
4DPA4 OTU1 line port
These ports are used for connecting with the Alcatel-Lucent 1830 PSS-1 (Edge
Device), Alcatel-Lucent 1830 PSS-4 or other Alcatel-Lucent 1830 PSS NEs.
For newly added GCC interfaces in new or existing installations it is highly
recommended to immediately set the interface GCC to standard mode of operation.
....................................................................................................................................................................................................................................
1830 PSS
3-18
Issue 1 June 2013

....................................................................................................................................................................................................................................
For existing GCC interfaces in existing installations it is highly recommended to plan

to upgrade ALL GCC interfaces to standard mode of operation. This must be a
planned action as changing the GCC standard mode of operation will cause the
interface data link to go DOWN until the GCC standard mode of operation on the
opposite end is changed to match.
Note: GCC is not supported on IO & Uplink packs.
Note: For newly added OSC/GCC interfaces in new or existing installations it is
highly recommended to immediately set the interface MTU size to 1500 bytes.
For existing OSC/GCC interfaces in existing installations it is highly recommended to
plan to upgrade ALL OSC/GCC interface MTU size to 1500. This must be a planned
action as changing the MTU size on one side of the OSC/GCC interface may cause
the interface data link to go DOWN until the MTU size on the opposite end is
changed to match.
Changing the MTU size to 1500 bytes allows for the remote management of
RAMAN/EDFA boxes through an 1830 network as well as increased throughput due
to minimized packet fragmentation.
Table 3-2, Communications Network Sizing (p. 3-19) provides a communications
network sizing summary.
Table 3-2
Connection Type
Maximum Value
Comment
TL1 (ports 3082, 3083)
20 sessions (see table note)
Multiple TL1 user sessions to

any NE
WebUI
16 sessions
This is for Craft Interface

Terminal (CIT) from the local
craft, or remotely connected
CLI
10 sessions
From the local craft or remote
SNMP
10 sessions
Management from 1354

RM-PhM or equivalent
SNMP manager
GCC0
32
For management connection

extension to SPB
OSC
20
Maximum of 8 fiber pairs
RNEs managed from one

GNE
128
Size of TID-IP map per GNE
256
TID to IP mapping over the

OSC and GCC0
....................................................................................................................................................................................................................................
1830 PSS
3-19
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 3-2
(continued)
Connection Type
Maximum Value
Comment
Active users
32
Combinations of TL1,
WebUI, CLI, and SNMP users
Number of degrees supported

by one NE
52
32 GCC0 + 20 OSC
Number of NEs in one OSPF

area
256
Default OSPF area is 0
Number of provisionable
OSPF areas supported on the
NE
Note: Once the maximum allowed count of 20 TL1 sessions are open, the user needs
to cancel the current TL1 log-in session(s) to allow any new users. A new user needs
to wait for 2 minutes to log-in after cancelling any of the already logged-in users.
....................................................................................................................................................................................................................................
1830 PSS
3-20
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
A Gateway Network Element (GNE) is defined as an NE that provides user access to all
NEs within the maintenance subnetwork. Any Alcatel-Lucent 1830 PSS can function as a
gateway NE. The GNE is able to send over the ECC (OSC and GCC0) the TL1
commands which are destined for a Remote NE. The GNE routes the messages between
members of the maintenance subnetwork.
The NE maintains a Gateway mapping table which contains mapping entries for every
reachable NE on the network. Each entry in the table contains the TID of the NE and its
corresponding IP address. The table contains entries for every reachable NE (over the
OSC for the Alcatel-Lucent 1830 PSS , as well as over the GCC for the Alcatel-Lucent
1830 PSS-1). The gateway mapping table is capable of holding a maximum of 128
entries.
Note: Upon reaching the maximum of 128 entries, the NE will raise an alarm to
indicate that the maximum size has been reached.
The NE supports creating and deleting system-level OSPF areas. The NE can be part of
up to 3 OSPF areas, in addition to the default backbone area (0-0-0-0). After an OSPF
Area is created, it can then be assigned to an OAMP, VOIP, E1, E2, OSC or GCC
interface. Opaque LSAs are used to advertise/distribute association parameters.
Note: OSPF does not need to run on the CIT, since this port is meant to be local LAN
(i.e. a stub network, not one where routes need to be discovered).
When OSPF is enabled on the OAMP or GCC0 interfaces, the default area for those
interfaces is 0. When OSPF is enabled on the OSC interface, the default area for this
interface is also 0. However, the system supports configuration of different areas on
these supported interfaces.
The GNE functionality supported in the Alcatel-Lucent 1830 PSS comes in handy if a
customer does not want to enable OSPF on the OAMP interface. Without OSPF to
discover the internal network and distribute this network to the management DCN, the
EMS is not able to directly connect to any remote NE (RNE). Connection method must
then be made thru the GNE. For example, in order to connect to an RNE, the customer
must first telnet to the GNE and from there, connect to the desired RNE.
Note: If any NEs are GNEs using static IP routing and then are reconfigured as
non-GNEs, any routers on the local subnet should have their ARP entries cleared so
that re-routing may take place immediately.
....................................................................................................................................................................................................................................
1830 PSS
3-21
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: In a network design where OSPF is enabled on the GNE OAMP management
ports or static routes are configured such that an alternate path for the 1830 NEs is
available via the customer DCN in addition to inter-NE paths via OSC/GCC
interfaces the following should be adhered too:
1. At the GNE NEs the Loopback IP should be provisioned with the snmp_src option
such that all SNMP requests to the NE must use only the Loopback IP of the NE
(the OAMP IP address will not be valid for SNMP requests). Likewise any SNMP
traps from the NE will contain the Loopback IP as the source IP address.
2. When OSPF is enabled at the OAMP port the OSPF metric should be provisioned
to be greater than the largest Inter-NE path cost. This will allow for NE-NE
application data messages to prefer inter-NE paths over customer DCN paths.
3. When static routes are configured at the GNE in order to provide an alternate path
for the 1830 NEs via the customer DCN in addition to inter-NE paths via
OSC/GCC interfaces - the distance value provisioned for each static route should
be greater than 110. This will allow for NE-NE application data messages to
prefer inter-NE paths over customer DCN paths.
For applications based on IP stack (i.e. SNMP, ftp, telnet), the EMS directly
communicates with the RNE, without using any translation function on the GNE. In this
case, all IP packets are routed to the appropriate destination, and the GNE does not need
to perform any association or mediation services.
To provide redundant paths between NMS and Alcatel-Lucent 1830 PSS network, dual
GNE configurations may be used (two examples of dual GNE configurations are shown
in Figure 3-1, Dual GNE configurations (p. 3-23).
....................................................................................................................................................................................................................................
1830 PSS
3-22
Issue 1 June 2013

....................................................................................................................................................................................................................................
Figure 3-1 Dual GNE configurations
For NE-to-EMS messages, the GNE routes the TL1 message over an IP address to the
appropriate EMS based on the connection on which the message was received.
Note: Enabling and disabling of TL1 autonomous messaging is supported via the
WebUI. The default state is for messages to be suppressed. To enable TL1
autonomous messaging, check TL1 Autonomous Messages Enabled in the System
Properties window display.
....................................................................................................................................................................................................................................
1830 PSS
3-23
Issue 1 June 2013

CIT port
....................................................................................................................................................................................................................................
CIT port
Remote NE management via the CIT port(s) can be supported, but only if the operator
assigns unique IP addresses to these CIT ports. Either CIT port on the active EC or
standby EC (if equipped) can be used to connect to the external device (e.g. laptop).
The system allows a user (Admin or Service user) to auto-disable the CIT port status.
Disable Port Automatically can only be set to Yes if Source IP is configured (does not
equal 0.0.0.0).
Note: Configurable attribute values on the two CIT ports are always the same;
updating the values on one port will automatically update the values on the other port.
When a redundant EC is installed, CIT port data from the first EC would need to be
copied to the CIT port on the new EC.
Once the laptop verifies that it can talk to its gateway, then the user can run the CIT,
telnet to the TL1 port, or telnet into the CLI. From the locally connected-to-CIT-port
laptop the NE will respond as follows:
If the user runs the WebUI, the NE responds with a login screen.
If the user runs the telnet session to the TL1 port the NE responds with a TL1
command prompt.
If the user runs the telnet session to the CLI, the NE responds with a CLI login
prompt.
The SNMP function is fully supported over the CIT, so the CIT can be used to
manage the entire Alcatel-Lucent 1830 PSS network if needed.
....................................................................................................................................................................................................................................
1830 PSS
3-24
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section describes procedures which have to be performed for data communication
setup in a OCS application.
Contents
3-27
3-29
View IP Addresses
3-30
3-31
3-34
3-36
3-38
3-41
3-42
3-43
3-44
3-45
Procedure 3-11: Modify the ASAP of the Customer LAN interface
3-57
Procedure 3-12: Configure LAN interfaces to form a multi-shelf compound
3-59
Procedure 3-13: Create a network interface on the embedded communication

channels (ECCs)
3-63
3-66
3-67
3-69
3-71
Procedure 3-18: Delete a network interface and an ECC protection group
3-73
3-75
3-78
....................................................................................................................................................................................................................................
1830 PSS
3-25
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
3-80
3-81
Procedure 3-23: Delete a static IP route from the IP routing table
3-85
3-87
3-89
3-91
3-93
3-96
3-98
3-100
3-101
Procedure 3-31: Configure the IP address range for the OSPF area
3-102
3-104
3-106
3-109
....................................................................................................................................................................................................................................
1830 PSS
3-26
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to change an already provisioned NE name (also referred to as the Site
Identifier (SID)).
NE names
NE names must be unique within a network to guarantee the reachability by management

systems and the proper interworking of NEs.
SET-SID
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectSystem.

...................................................................................................................................................................................................
Then select System Commands Set Site Identifier, either by selecting Action from
the main menu bar or by using the context menu opened with the right mouse button.
....................................................................................................................................................................................................................................
1830 PSS
3-27
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Set Site Identifier window opens.
...................................................................................................................................................................................................
Place the cursor in the SID text box and key in the new SID observing the following
configuration rules:
Each NE name must be unique within the network.

The following characters are allowed in an NE name:
Uppercase letters (A .. Z),
Lowercase letters (a .. z),

Special characters (-),
Digits (0 .. 9).
Each NE name must be at most 20 characters in length.
The SID must start with a letter and must end with an alphanumeric character.
Consecutive hyphens (-) are not allowed.
Number of hyphens must not be greater than 4.
If a lower-case character string is entered for the SID, it is automatically converted to

an uppercase character string for comparison to any TID value entered in a command.
Please note that NE names are case-insensitive.

...................................................................................................................................................................................................
Click Apply to assign the new SID and to dismiss the window.
...................................................................................................................................................................................................
Confirm the resulting system message by clicking OK.

Attention: Change of SID causes the active user session to become closed.
...................................................................................................................................................................................................
Exit the Alcatel-Lucent 1830 PSS ZIC. Then restart the Alcatel-Lucent 1830 PSS ZIC.
Repeat a refresh of the 1830 PSS ZIC page in the browser window until the new NE
name is present in NE TID field and ZIC SERVER state is ALIGNED. Then launch ZIC
application again.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-28
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure if you want to view the IP and MAC addresses of an NE.
RTRV-IP-ADDR
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectSystem Networking.

Then select IP Addresses IP Addresses , either by selecting Action from the main menu
bar or by using the context menu opened with the right mouse button.
Result: The Alcatel-Lucent 1830 PSS ZIC IP Address window opens. See View IP
Addresses (p. 3-30).

...................................................................................................................................................................................................
Click on Close to exit to the IP Address window.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-29
Issue 1 June 2013

View IP Addresses
....................................................................................................................................................................................................................................
View IP Addresses
Purpose
This window is used to display the TCP/IP addresses in the network element NE).

Parameter
Meaning
Active FLC IP
Displays the Internet Protocol address configured on the currently

active FLC.
Configured on the OAMP LAN.
Control Plane IP
Displays the control plane node IP address of the NE.
FLC A IP
Displays the Internet Protocol address configured on the left FLC

card.
FLC B IP
Displays the Internet Protocol address configured on the right FLC

card.
LAN Gateway
Displays the Internet Protocol address of the gateway router,

connected to the OAMP LAN.
Loopback IP
Displays the loopback IP address of the NE. Used by several

network interfaces (ECCs, and IPIPTs), and used as OSPF router Id.
IP Mask
Displays the subnet mask of the network the NE is connected to.

MAC Address
Displays the MAC address.
....................................................................................................................................................................................................................................
1830 PSS
3-30
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify the FLC IP Addresses of the NE.

Note: This IP address can also be set using Procedure 20-1: Initialize the NE using
EZ setup tool (p. 20-27).
ED-IP-ADDR
RTRV-IP-ADDR.
Before you begin
Have a valid user login and password

Be connected to the subject NE
Required equipment
Alcatel-Lucent 1830 PSS ZIC.
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectSystem Networking.

Then select IP Addresses, either by selecting Action from the main menu bar or by using
the context menu opened with the right mouse button.
Result: The Alcatel-Lucent 1830 PSS ZIC IP Address window opens.
...................................................................................................................................................................................................
Select the list entry you want to modify.

...................................................................................................................................................................................................
Click Edit FLCIP Addresses.

Result: TheEdit FLC IP Addresses window opens.
...................................................................................................................................................................................................
In the field Active FLC IP Address enter the IP address for the currently active FLC.
....................................................................................................................................................................................................................................
1830 PSS
3-31
Issue 1 June 2013

....................................................................................................................................................................................................................................
Additional information: {1-99,101-126,128-223} - {0-255} - {0-255} - {0-255}.
Neither the network nor the host portion of the address (with respect to the value of
the MASK parameter) when viewed in binary format may be all 0s or all 1s.
This address follows the active FLC on each FLC EPS switch.
The factory default is 18-70-1-3.
...................................................................................................................................................................................................
In the field FLC-A IP Address modify the IP address of the left FLC.
The factory default is 18-70-1-1. This address is always configured on the (front
view) leftmost FLC card (Slot 73 in PSS-64 system, Slot 23 in PSS-36 system)
...................................................................................................................................................................................................
In the field FLC-B IP Address modify the IP address of the right FLC.
The factory default is 18-70-1-2. Once changed, this parameter cannot be reset to the
factory default. This address is always configured on the rightmost FLC card (Slot 75
in PSS-64 system Slot 40 in PSS-36 system)
...................................................................................................................................................................................................
In the field Subnet Mask enter the subnet mask of the network the NE is connected to on
the Customer LAN.
Additional information: {128-255} - {0-255} - {0-255} - {0-248}
Alternative the mask can be entered in CIDR notation: {1-29}

The mask, in binary representation, must contain a contiguous string of 1s (the
network portion) followed by a contiguous string of 0s (the host portion). All IP
addresses specified have to be in the same subnet.
...................................................................................................................................................................................................
In the field LAN Gateway enter the internet Protocol address of the gateway router,
connected to the OAMP LAN
Additional information: {1-99,101-126,128-223} - {0-255} - {0-255} - {0-255}
Internet Protocol address of the gateway router, connected to the OAMP LAN. The
address must be part of the IP subnet configured on the OAMP LAN via the
ACTIVEFLCIP, FLCAIP, FLCBIP, MASK parameters. The address must not be
....................................................................................................................................................................................................................................
1830 PSS
3-32
Issue 1 June 2013

....................................................................................................................................................................................................................................
identical to any of the ACTIVEFLCIP, FLCAIP, FLCBIP addresses. Neither the

network nor the host portion of the address (with respect to the value of the MASK
parameter) when viewed in binary format may be all 0s or all 1s.
The factory default is 0-0-0-0, meaning that no default route is set via the OAMP
LAN. Changing the value back to 0-0-0-0 is equivalent to removing the default route.
Note: Do not provision a LAN Gateway address for a Remote NE, that is not
physically connected to an OAMP LAN
...................................................................................................................................................................................................
Click Apply.
Result: The IP change is sent to NE and the Alcatel-Lucent 1830 PSS ZIC shows the
updated address.
...................................................................................................................................................................................................
10
Exit to the IP Address window.

...................................................................................................................................................................................................
11
Reconnect to the Alcatel-Lucent 1830 PSS ZIC.

Change of the FLC IP Addresses causes the active user session to become closed.
Reconnect to the Alcatel-Lucent 1830 PSS ZIC page with the browser using the newly
provisioned IP address and refresh the presented page until the ZIC SERVER state is
ALIGNED. Then launch ZIC application again.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-33
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to set or modify the loopback IP address of the NE, which is shared as
interface address by all ECC network interfaces (NETIF), IP over IP tunnel interfaces
(IPIPT), and which is also used as OSPF router Id.
Note: This IP address can also be set using Procedure 20-1: Initialize the NE using
EZ setup tool (p. 20-27).
ED-IP-ADDR
RTRV-IP-ADDR
Before you begin

Have proper User Community Authorization Level to perform this task,

ensure that no OSPF interface is enable in the system
ensure that neither a NETIF interface nor an IPIPT tunnel is provisioned.
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System Networking.
Then select IP Addresess, either by selecting Action from the main menu bar or by using
...................................................................................................................................................................................................
Click Edit Loopback IP Address.
....................................................................................................................................................................................................................................
1830 PSS
3-34
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Edit Loopback IP Address window opens.

...................................................................................................................................................................................................
In the field Loopback IP Address enter the loopback address of the NE.
Note: This address is an alias to the SYSTEM IP address as set up with Procedure
3-6: Modify the TCP/IP stack parameters (p. 3-38).
Additional information: The address 0-0-0-0 is not allowed.
The NE loopback address is also used as OSPF Router Id. The address must not be
part of the IP subnet configured on the customer LAN via the ACTIVEFLCIP,
FLCAIP, FLCBIP, MASK parameters. The address must not be identical to the CPIP
address.
...................................................................................................................................................................................................
Click Apply.
...................................................................................................................................................................................................
Exit the IP Address window.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-35
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to set the control plane IP addresses of the NE, if not already done
using Procedure 20-1: Initialize the NE using EZ setup tool (p. 20-27).
ED-IP-ADDR
RTRV-IP-ADDR
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System Networking.
Then select IP Addresess, either by selecting Action from the main menu bar or by using
...................................................................................................................................................................................................
Select the list entry you want to modify.

...................................................................................................................................................................................................
Click Edit Control Plane IP Address.

Result: The Edit Control Plane IP Address window opens.
...................................................................................................................................................................................................
In the field Control Plane IP Address enter the control plane node IP address of the NE.
....................................................................................................................................................................................................................................
1830 PSS
3-36
Issue 1 June 2013

....................................................................................................................................................................................................................................
Additional information: The address 0-0-0-0 is not allowed.
The address must not be part of the IP subnet configured on the customer LAN via the
identical to the LOOPBACKIP address.
Note: This address is an alias to the control plane IP address as set up with
Procedure 3-6: Modify the TCP/IP stack parameters (p. 3-38).
Note: After the GMRE processes have been activated by setting the GMRE
Administrative State to UP the Control Plane IP address cannot be modified
anymore.
...................................................................................................................................................................................................
Click Apply.
...................................................................................................................................................................................................
Exit the IP Address window.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-37
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
This procedure can also be used to configure TCP/IP parameters for some of the
interfaces:
LAN-OAMP (management LAN interface),

SYSTEM (Router ID),
CPN (Control Plane Node).
The configured IP address on System AID is the NE's loopback IP address, which is
shared as interface address by all unnumbered network interfaces.
The configured IP address on System AID will be also used as OSPF Router ID.
The configured IP address on control plane node AID is used as TDM control plane node
address. This address has to be provisioned, before the TDM control plane is started on
the NE. This address is used by the control plane for communicating with direct
neighbors.
ED-IP-IF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System Networking IP
Addresses IP Interfaces.
....................................................................................................................................................................................................................................
1830 PSS
3-38
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Manage IP Interfaces window opens.
...................................................................................................................................................................................................
Select the interface for which you want to configure:
SYSTEM
Loopback Address
CPN
Local Control Plane Node

( the CPN address cannot be set before the SYSTEM address is set)
CPNOTIFY (only displayed, can not be edited)
Local Control Plane Notify Interface
LAN-OAMP
Customer LAN
...................................................................................................................................................................................................
Click Modify.
Result: The Alcatel-Lucent 1830 PSS ZIC Manage IP Interfaces window opens.
...................................................................................................................................................................................................
Enter the Internet Protocol address of the NE on the addressed interfacein the IP Address
field.
For the IP address the following restrictions exist:
Possible values are {1-99, 101-126, 128-223} - {0-255} - {0- 255} - {0-255}
0-0-0-0 is not allowed

Neither the network nor the host portion of the address when viewed in binary format
may be all 0s or all 1s.
...................................................................................................................................................................................................
Enter the subnet mask fore NE in the Subnet Mask field.

For the IP address the following restrictions exist:
the Mask Parameter only applies to the LAN interface
Possible values are {128-255} - {0-255} - {0- 255} - {0-248}

network portion) followed by a contiguous string of 0s (the host portion)..
...................................................................................................................................................................................................
Enable the Internet Protocol on the addressed LAN interface.

Select Yes in the respective drop-down list box.
....................................................................................................................................................................................................................................
1830 PSS
3-39
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply to confirm.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-40
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to add a new access control rule to the NE firewall.
ENT-IPACLIST
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
with the right mouse button, select Add Rule.
Result: The Create access control rule window opens.
Reference: See Internet Protocol Access Control Lists (p. 3-45).
...................................................................................................................................................................................................
Enter the needed parameters as described.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-41
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify an existing access control rule of the NE firewall.
ED-IPACLIST
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Select an access control rule in the list displayed in the right part of the Alcatel-Lucent
1830 PSS ZIC main menu and click on Modify.
...................................................................................................................................................................................................
Modify the parameters as described.

...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-42
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete an internet protocol access rule.

DLT-IPACLIST
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Result: The Access Control Lists are displayed in the display pane of the

...................................................................................................................................................................................................
Select the access control rule and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-43
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve the internet protocol access rules.

RTRV-IPACLIST
Before you begin
Required equipment
Instructions
...................................................................................................................................................................................................
Result: The Access Control Lists are displayed in the display pane of the

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-44
Issue 1 June 2013

....................................................................................................................................................................................................................................

Access Control Lists for IP addresses and ports
The device supports the configuration of access control lists (ACL) or filters to limit the
access to the administration and other management protocols only from certain ranges of
authorized source IP addresses and ports. It is also possible to configure multiple disjoint
ranges specified through IP network and mask.
Access control lists are configurable on NEs to filter traffic which is destined for the NE
itself and forwarded by the NE. E.g.:
Completely block an NE service, which is not used in the operator context.

Restrict access to a service to a limited range of IP addresses.
Filter rules
Packet filter rules for IP forwarding can be defined by specifying ID as FORWARD.
There is one global filter chain for IP forwarding.
Packet filter rules for traffic destined to the NE can be defined by specifying ID as a
specific service value.
There is one filter chain for each service of the NE, specified via the ID parameter.
Each filter chain is an ordered list of rules. When matching a packet against rules of a
chain, the rules of the chain are applied one-by-one according to the given order. If one
rule matches, the TARGET action, specified by that rule is executed on the packet.
No further rules in the chain are applied to that packet, after one rule matched.
This matching mechanism allows to define and make use of conflicting rules.
As a typical example, a rule for accepting a set (A) of packets can be followed by a rule
for dropping a superset (B, including A) of packets. In sum, this has the effect of dropping
all packets in set B except for those, which are also in set A.
As a factory default, each chain contains a single rule, which unconditionally accepts
every packet. To define a more restrictive rule set, the following procedure can be
applied:
First append rules to the chain, which accept all desired specific traffic types.
Append one final rule, which drops or rejects everything.

Finally delete the 'accept all' factory default rule, which is still at the beginning of the
chain.
Creating a new rule
The default behavior is to append the new rule to the chain.
....................................................................................................................................................................................................................................
1830 PSS
3-45
Issue 1 June 2013

....................................................................................................................................................................................................................................
When specifying Index, the new rule is inserted before the existing rule indicated by the
value of Index. When inserting a rule into a chain, Index values of all existing rules (of
the same chain) with the same or a higher Index value are incremented by one.
....................................................................................................................................................................................................................................
1830 PSS
3-46
Issue 1 June 2013

....................................................................................................................................................................................................................................

Field/parameter ...
Meaning...
ID
Identifies the id of the chain, to which the rule belongs:
FORWARD
IP forwarding chain
TL1RAWUNSEC
Input chain for the raw encoded TL1 service on TCP port 3082
TL1RAW
Input chain for the raw encoded TL1 over SSH port 6084
TL1TELNET
Input chain for the telnet encoded TL1 over SSH port 6085
ZIC
Input chain for all SSL/TLS ports used by communication to

ZIC-GUI
DBG
Input chain for debug shell SSH port 22
CPMGT
Input chain for control plane management via CORBA over

TCP port 34567
CPCLI
Input chain for the control plane CLI over SSH port 6087
CPRSVP
Input chain for the control plane signaling protocol RSVP
CPOSPFTE
Input chain for the control plane OSPF-TE protocol (data plane
routing)
CPLMP
Input chain for the control plane LMP protocol on UDP port 701
NTP
Input chain for the NTP protocol on UDP port 123
OSPF
Input chain for the OSPFv2 routing protocol
ICMP
Input chain for ICMP messages
MON
Input chain for NE monitoring on TCP port 8649
ALL
ALL AID
....................................................................................................................................................................................................................................
1830 PSS
3-47
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Index
The index of the rule in the chain addressed by AID.

{1-4000}
When creating a new rule, this specifies in front of which existing
rule to insert the new rule. Index values are incremented for all rules
behind the inserted new rule.
Interface Input
Defines the interface(s) on which matching packets may have

entered the NE
LAN-{OAMP, CIT}
Customer LAN
only packets coming in on the specific interface can match the
rule
NETIF-{1-512}
Network Interface on an ECC protection group

rule
NETIF-ALL
packets coming in on any NETIF can match the rule
IPIPT-{1-64}
Internet Protocol in Internet Protocol Tunnel

rule
IPIPT-ALL
packets coming in on any IPIPT can match the rule
ALL
packets coming in on any interface can match the rule
....................................................................................................................................................................................................................................
1830 PSS
3-48
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Interface Output
Defines the interface(s) on which matching packets leave the NE.

This parameter is only supported for the forwarding chain, i.e. if
AID is reported as FORWARD.
LAN-{OAMP, CIT}
Customer LAN
rule
NETIF-{1-512}

rule
NETIF-ALL
packets coming in on any NETIF can match the rule
IPIPT-{1-64}
Internet Protocol in Internet Protocol Tunnel

rule
IPIPT-ALL
packets coming in on any IPIPT can match the rule
ALL
packets coming in on any interface can match the rule
....................................................................................................................................................................................................................................
1830 PSS
3-49
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
IP Protocol
Defines the IP protocol of matching packets.
{0-255}
Numeric protocol value from the IP header
ICMP
Equivalent to protocol number = 1
IGMP
TCP
Equivalent to protocol number == 6
UDP
RSVP
OSPFTE
OSPF
ALL
Equivalent to protocol number = 0, matches any protocol

number
When retrieving the internet protocol access rules this parameter is
only reported for the forwarding chain, i.e. if ID is reported as
FORWARD.
Note: This parameter is only allowed to be specified, if
adding/changing rules of the forwarding chain.
ICMP Type
Defines the ICMP header type field value of matching packets

For the forwarding chain, this parameter is only accepted, if ICMP is
specified via IP Protocol. For a service specific chain, this
parameter is only accepted, if the addressed service is ICMP.
Values:
{0-255}
ALL
Equivalent to numerical value 255, matches any value.

The ICMP type is not considered for matching.
....................................................................................................................................................................................................................................
1830 PSS
3-50
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
ICMP Code
Defines the ICMP header code field value of matching packets.

For the forwarding chain, this parameter is only accepted, if ICMP is
specified via IP Protocol. For a service specific chain, this
parameter is only accepted, if the addressed service is ICMP.
Values:
{0-255}
ALL
The code type is not considered for matching.
....................................................................................................................................................................................................................................
1830 PSS
3-51
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Source Port.
Defines the TCP or UDP source port of matching packets.

Values:
{0-65535}
TL1RAWUNSEC
Equivalent to TCP port 3082
TL1RAW
TL1TELNET
HTTPS
SSH
CPMGT
CPCLI
NTP
Equivalent to UDP port 123
MON
ALL
The source port is not considered for matching.

For the forwarding chain, this parameter is only accepted, if UDP or
TCP is specified via the IPPROTOCOL= parameter. For a service
specific chain, this parameter is only accepted, if the addressed
service is based on UDP or TCP.
A symbolic port name is only allowed, if it matches to the protocol
(TCP or UDP) specified via IPPROTOCOL=.
A set of ports can be specified via && ranging and & grouping.
Up to 15 ports can be given, where a && range specification counts
as 2 ports.
Only numeric values are allowed in a && ranging term.
....................................................................................................................................................................................................................................
1830 PSS
3-52
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Source Addr
Defines the source IP address of matching packets.

Values:
{0-255}-{0-255}-{0-255}-{0-255}
Together with the Source Mask parameter, an address range can be

specified. The wildcard value 0-0-0-0 with Source Mask=0 means,
source IP address is not considered for matching. Any address
different from 0-0-0-0 with Source Mask=32 means, a single
address is considered for matching
Source Mask
Defines the Source Mask of matching packets.

Values:
{0-255}-{0-255}-{0-255}-{0-255}
{0-32}
Defines the range of matching packets together with the source IP

address.
The mask can be given in CIDR notation or in dotted decimal
notation (e.g. 24 standing for CIDR notation /24 being synonym to
255-255-255-0, standing for dotted decimal notation
255.255.255.0).
Destination Addr
Defines the destination IP address of matching packets.

Values:
{0-255}-{0-255}-{0-255}-{0-255}
Together with the Destination Mask parameter, an address range can

be specified. The wildcard value 0-0-0-0 with Destination Mask=0
means, source IP address is not considered for matching. Any
address different from 0-0-0-0 with Destination Mask=32 means, a
single address is considered for matching
Destination Mask
Defines the Destination Mask of matching packets.

Values:
{0-255}-{0-255}-{0-255}-{0-255}
{0-32}
Defines the range of matching packets together with the Destination

address.
The mask can be given in CIDR notation or in dotted decimal
notation (e.g. 24 standing for CIDR notation /24 being synonym to
255-255-255-0, standing for dotted decimal notation
255.255.255.0).
....................................................................................................................................................................................................................................
1830 PSS
3-53
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Destination Port
Defines the TCP or UDP destination port of matching packets.

Values:
{0-65535}
TL1RAWUNSEC
TL1RAW
TL1TELNET
HTTPS
SSH
CPMGT
CPCLI
NTP
Equivalent to UDP port 123
MON
ALL
The source port is not considered for matching.

For the forwarding chain, this parameter is only accepted, if UDP or
TCP is specified via the IPPROTOCOL= parameter. For a service
specific chain, this parameter is not supported.
A symbolic port name is only allowed, if it matches to the protocol
(TCP or UDP) specified via IPPROTOCOL=.
A set of ports can be specified via && ranging and & grouping.
Up to 15 ports can be given, where a && range specification counts
as 2 ports.
Only numeric values are allowed in a && ranging term.
....................................................................................................................................................................................................................................
1830 PSS
3-54
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
State
This defines the connection tracking state of matching packets.

Values:
INVALID
The packet is associated with no known connection.
NEW
The packet has started a new connection, or is otherwise

associated with a connection which has not seen packets in both
directions.
ESTABLISHED
The packet is associated with a connection which has seen

packets in both directions.
RELATED
The packet is starting a new connection, but is associated with

an existing connection, such as an FTP data transfer, or an
ICMP error.
ALL
The connection state is not considered for matching.

Via & grouping, a list of states can be specified. The rule matches,
if one of the listed states applies.
This parameter is only supported for the forwarding chain,
Fragmentation.
Specifies, whether and how to match packets based on being

fragmented.
match packets which are a second or later packet
match packets which are not fragmented, or are a first fragment
ALL
don't care about fragmentation

Note: This parameter is only supported tor the forwarding chain.
Retrieving internet protocol access rules:
When retrieving internet protocol access rules this parameter is only
reported, if fragmentation is actually considered for matching. ALL
is never reported).
....................................................................................................................................................................................................................................
1830 PSS
3-55
Issue 1 June 2013

....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Treatment
Specifies how packets are treated, which match this rule
ACCEPT
matching packets are accepted
DROP
matching packets are silently discarded
REJECT
matching packets are discarded, an ICMP error message is sent

back
....................................................................................................................................................................................................................................
1830 PSS
3-56
Issue 1 June 2013

Procedure 3-11: Modify the ASAP of the Customer LAN

interface
....................................................................................................................................................................................................................................

interface
When to use
Use this procedure to modify the ASAP of the Customer LAN interface.
This applies to the following ports:
OAMP:
The OAMP faceplate LAN connector on the main shelf FLC cards. This is intended
for connecting the NE to the DCN for central management
Related TL1 command
The following TL1 command is related to this procedure:
ED-LAN.
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectSystem Networking

Customer LAN .
...................................................................................................................................................................................................
Select the LAN-OAMP entry in the list.

...................................................................................................................................................................................................
Then select Properties Alarm Severity - Set either by selecting Action from the main
menu bar or by using the context menu opened with the right mouse button.
Result: The Edit Alarm Profile Pointer window opens.
...................................................................................................................................................................................................
In the field Alarm Profile select the Alarm Severity Assignment Profile to be used.
....................................................................................................................................................................................................................................
1830 PSS
3-57
Issue 1 June 2013


interface
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-58
Issue 1 June 2013

Procedure 3-12: Configure LAN interfaces to form a

multi-shelf compound
....................................................................................................................................................................................................................................

When to use
Use this procedures to configure shelf interconnection LAN Ports on MTX cards for
setting up a multi-shelf compound.
For compound concept information refer to Alcatel-Lucent 1830 PSS Product Information
and Planning Guide.
Interconnection in a single multi-shelf compound
When extension shelves are used the main shelf and the extension shelves must be
interconnected by LAN cables in the following way to form a single compound:
The external LAN interfaces (ES1, ES2) of the left matrix card must be connected to
the external LAN interfaces (ES1, ES2) of the left matrix card of the neighbor
shelves.
The external LAN interfaces (ES1, ES2) of the right matrix card must be connected to
the external LAN interfaces (ES1, ES2) of the right matrix card of the neighbor
shelves
The ES1 interfaces of a shelf are always connected to the ES2 interfaces of its
neighbor shelf.
This must be done from one shelf to the next shelf until a ring closure is achieved.
Refer to the following figure for clarification:
A single compound can be configured as OCS or as WDM compound and both can be
interconnected as well. Compound interconnnect is done via OAMP LAN.
....................................................................................................................................................................................................................................
1830 PSS
3-59
Issue 1 June 2013


....................................................................................................................................................................................................................................
For additional configuration details on interconnecting compounds (for example, to

configure the interconnection of OCS compound to WDM compound) see Chapter 4 of
the 1830 PSS User Provisioning Guide.
Related TL1 command
ED-LAN.
Before you begin

Required equipment
Enable LAN interfaces

...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System Networking
Internal LAN.
...................................................................................................................................................................................................
Select a LAN entry in the list.

On the Alcatel-Lucent 1830 PSS-64:
LANPORT-1-1-71-ES1
LANPORT-1-1-71-ES2
LANPORT-1-1-72-ES1
LANPORT-1-1-72-ES2
LANPORT-1-<shelf>-11-ES1
....................................................................................................................................................................................................................................
1830 PSS
3-60
Issue 1 June 2013


....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Then select Properties General either by selecting Action from the main menu bar or
by using the context menu opened with the right mouse button.
...................................................................................................................................................................................................
Enable the addressed LAN interface, if not already enabled by default

Select Enabled in the respective drop-down list box.
...................................................................................................................................................................................................
Click Apply to close the window.

E...................................................................................................................................................................................................
N D O F S T E P S
Set the ASAP of an internal LAN interface

...................................................................................................................................................................................................
Internal LAN.
...................................................................................................................................................................................................
Select a LAN entry in the list.

LANPORT-1-1-71-ES1
LANPORT-1-1-71-ES2
LANPORT-1-1-72-ES1
LANPORT-1-1-72-ES2
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
3-61
Issue 1 June 2013


....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Additional information: Select LBL-ASAPLAN-SYSDFLT, if not already selected.
For further information on alarm profiles refer to the Product Information and
Planning Guide, table System-defined ASAP instances.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-62
Issue 1 June 2013

Procedure 3-13: Create a network interface on the

embedded communication channels (ECCs)
....................................................................................................................................................................................................................................
Procedure 3-13: Create a network interface on the embedded

communication channels (ECCs)
When to use
Use this procedure to create a network interface on the ECC for data communication
purposes.
This procedure creates an ECC protection group with the ECC channel specified as its
single member and automatically enables IP on the network interface.
ECC termination is done on IO cards. ECC bytes are transported between IO cards and
the central ECC routing component on FLC cards via dedicated bidirectional backplane
links.
You can add or remove ECC channels to/from the ECC protection group (see Procedure
3-15: Add a GCC leg to an ECC protection group (p. 3-67)).
The ECC channel can be the GCC0 of the specific OTU facility. The GCC0 is identified
by means of the OTU AID and the (optional) DCCCHNL parameter.
The ECC channel can be the GCC1 of the specific ODU facility. The GCC1 is identified
by means of the ODU AID and the (optional) DCCCHNL parameter.
ECC backplane capacity restrictions
The following ECC backplane capacity restrictions apply per I/O card:
a 2XANY40G card provides 297 bytes ECC backplane capacity towards the FLC
dedicated to ECCs from port 1, and 297 bytes ECC backplane capacity towards the
FLC dedicated to ECCs from port 2.
a 43SCUP card provides 297 bytes ECC backplane capacity towards the FLC.
an ODU2 GCC uses 22 ECC backplane bytes
an OTU2 GCC uses 22 ECC backplane bytes
an ODU2e GCC uses 23 ECC backplane bytes

an OTU2e GCC uses 23 ECC backplane bytes
an ODU3 GCC uses 84 ECC backplane bytes.
an OTU3 GCC uses 84 ECC backplane bytes.
an ODU3E2 GCC uses 87 ECC backplane bytes
an OTU3E2 GCC uses 87 ECC backplane bytes

An ODU4 GCC uses 216 ECC backplane bytes
An OTU4 GCC uses 216 ECC backplane bytes
....................................................................................................................................................................................................................................
1830 PSS
3-63
Issue 1 June 2013


....................................................................................................................................................................................................................................
ENT-NETIF
Before you begin

Loopback IP is configured.
Required equipment
Instructions
...................................................................................................................................................................................................

Network Interfaces.
Then select Create Interface, either by selecting Action from the main menu bar or by
using the context menu opened with the right mouse button.
Result: The Alcatel-Lucent 1830 PSS ZIC Network Interfaces Provisioning Dialog
window opens.
...................................................................................................................................................................................................
In the field Add facilty select the ODU facilty which should be used.
...................................................................................................................................................................................................
In the field ECC Channel specify the type of the referred ECC channel.
GCC0
the referred ECC is a GCC0 of an OTU facility
GCC1
the referred ECC is a GCC1 of an ODU facility

...................................................................................................................................................................................................
If needed you can reference Alarm Severity Assignment Profile (ASAPNETIF) instance
by selecing the respective Alarm Profile User Label.
....................................................................................................................................................................................................................................
1830 PSS
3-64
Issue 1 June 2013


....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Using the Status field you can specify the administrative status of the network interface:
ENABLED
DISABLED
Once enabled the network interface is taken into service, and IP is automatically
enabled on the network interface. Once disabled the network interface is taken out of
service.
Important! While the PPP and IP protocols are automatically enabled on a newly
created network interface, OSPF has to be enabled manually. Make sure to enable
OSPF on each newly created network interface.
...................................................................................................................................................................................................
Make sure that the settings in the Network Interfaces Provisioning Dialog window are
correct.
...................................................................................................................................................................................................
Click Apply.
Result: The command is sent.
E...................................................................................................................................................................................................
N D O F S T E P S
Adding or removing channels to/from the ECC protection group
To add or remove ECC channels to/from the ECC protection group see Procedure 3-15:
Add a GCC leg to an ECC protection group (p. 3-67).
....................................................................................................................................................................................................................................
1830 PSS
3-65
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify the ASAP of a network interface.

Related TL1 command
ED-NETIF
RTRV-NETIF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Network Interfaces .
...................................................................................................................................................................................................
Select a NETIF entry in the list.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-66
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to add a GCC leg to an ECC protection group.

ECC protection restrictions
The following ECC protection restrictions apply:
ECC protection group can contain both GGC0 and GCC1, but not of the same port
ECC protection group can only contain GCC from within same shelf
ECC backplane capacity restrictions
The following ECC backplane capacity restrictions apply per I/O card:
dedicated to ECCs from port 1, and 297 bytes ECC backplane capacity towards the
FLC dedicated to ECCs from port 2.
a 43SCUP card provides 297 bytes ECC backplane capacity towards the FLC.
an ODU2 GCC uses 22 ECC backplane bytes

an OTU2 GCC uses 22 ECC backplane bytes
an ODU2e GCC uses 23 ECC backplane bytes
an OTU2e GCC uses 23 ECC backplane bytes
an ODU3 GCC uses 84 ECC backplane bytes.

an OTU3 GCC uses 84 ECC backplane bytes.
an ODU3E2 GCC uses 87 ECC backplane bytes

an OTU3E2 GCC uses 87 ECC backplane bytes
An ODU4 GCC uses 216 ECC backplane bytes

An OTU4 GCC uses 216 ECC backplane bytes
ED-NETIF
Before you begin

....................................................................................................................................................................................................................................
1830 PSS
3-67
Issue 1 June 2013

....................................................................................................................................................................................................................................

Loopback IP is configured.
Required equipment
Instructions
...................................................................................................................................................................................................

Network Interfaces.
...................................................................................................................................................................................................
Select the NETIF to which you want to add a GCC leg.

...................................................................................................................................................................................................
Then select ECC Facilities Add, either by selecting Action from the main menu bar or
Result: The Alcatel-Lucent 1830 PSS ZIC Network Interfaces Add DCC Facilities
Dialog opens.
...................................................................................................................................................................................................
In the field Add facilty select the ODU facilty which should be used.
...................................................................................................................................................................................................
In the field DCC Channel specify the type of the referred ECC channel.
GCC0
the referred ECC is a GCC0 of an OTU facility
GCC1
the referred ECC is a GCC1 of an ODU facility

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-68
Issue 1 June 2013

Procedure 3-16: Remove GCC legs from the ECC protection

group
....................................................................................................................................................................................................................................

group
When to use
Use this procedure to remove GCC legs from a ECC protection group.
ED-NETIF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Network Interfaces.
...................................................................................................................................................................................................
Select the NETIF from which you want to remove a GCC leg.
...................................................................................................................................................................................................
Then select ECC Facilities Manage, either by selecting Action from the main menu bar
or by using the context menu opened with the right mouse button.
Result: The Alcatel-Lucent 1830 PSS ZIC Network Interfaces Add DCC Facilities
Dialog opens.
...................................................................................................................................................................................................
Select the GCC leg you want to remove.

...................................................................................................................................................................................................
Click Delete.
....................................................................................................................................................................................................................................
1830 PSS
3-69
Issue 1 June 2013


group
....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Network Interfaces Remove DCC Facility
Dialog opens.
...................................................................................................................................................................................................
Click Apply.
Result: The GCC leg is removed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-70
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to enable or disable a network interface.

ED-NETIF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Network Interfaces.
...................................................................................................................................................................................................
Select the NETIF you want to enable or disable.

...................................................................................................................................................................................................
Then select Properties General, either by selecting Action from the main menu bar or
Result: The Alcatel-Lucent 1830 PSS ZIC Properties Gereal window opens.
...................................................................................................................................................................................................
Using the field Status you can specify the administrative status of the network interface:
ENABLED
DISABLED
....................................................................................................................................................................................................................................
1830 PSS
3-71
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click on Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-72
Issue 1 June 2013

Procedure 3-18: Delete a network interface and an ECC

protection group
....................................................................................................................................................................................................................................

protection group
When to use
Use this procedure to delete a network interface and an ECC protection group. This puts
all member channels of the ECC protection group to the non-terminated state, disables
data communication on those channels, and frees all ECC resources previously held by
those channels.
DLT-NETIF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Network Interfaces.
...................................................................................................................................................................................................
Select the NETIF you want to delete.

...................................................................................................................................................................................................
Then select Delete, either by selecting Action from the main menu bar or by using the
Result: The Delete Network Interface window opens.
...................................................................................................................................................................................................
Click on Yes.
....................................................................................................................................................................................................................................
1830 PSS
3-73
Issue 1 June 2013


protection group
....................................................................................................................................................................................................................................
Result: The Network Interface with all protection members is deleted.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-74
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to establish IP-in-IP Tunnels (IPIPT) between NEs and towards
Network Management System. The IP tunnels are basically uni-directional and have to be
created from each side to get a bi-directional tunnel.
IP-in-IP tunnel
This function allows NEs to build Out-of-band protection links for In-Band (ECC) links
used by the control plane, or to tunnel management traffic through parts of the External
DCN topology, which are under different administrative control. The NE supports GRE
encapsulation according to RFC2784 and IP-in-IP encapsulation according to RFC2003.
The encapsulation method used on a tunnel can be defined and retrieved respectively
using this procedure.
The remote endpoint of the IP-in-IP tunnel can be specified and retrieved as the IP
address of the remote NE respectively via the ENT-NE-IPIPT and RTRV-NE-IPIPT
commands.
The local and remote endpoint addresses are the addresses used as source and destination
IP addresses in the outer delivery IP header of the encapsulated packet.
Local interface address
The local interface address is the address, which is used as source IP address in the
inner/payload IP header of locally originated packets, which are sent via the tunnel.
For this purpose either the IP address is used to which the service is bound that is using
the tunnel or in all other cases the NE loopback address is used that was specified in
Procedure 3-3: Set the FLC IP Addresses of the NE (p. 3-31).
The loopback IP address is the local IP address for all unnumbered interfaces and must be
configured first, before any tunnel can be configured.
IP routing
The IP routing for IP-in-IP tunnels is:
Static, by specifying a static route

Dynamic, by using OSPF.
When OSPF is used, it shall be possible to assign the tunnel interface to any of the OSPF
areas configured on the NE. If no additional area is configured then the backbone area
(0.0.0.0) is used by default. The IP-in-IP tunnel can be configured to be bound to a
....................................................................................................................................................................................................................................
1830 PSS
3-75
Issue 1 June 2013

....................................................................................................................................................................................................................................
customer LAN interface. If an IP-in-IP tunnel is bound to a LAN interface, it is to be

ensured, that packets, which are sent via the tunnel, will leave the NE only via the
specific LAN interface.
ENT-NE-IPIPT
RTRV-NE-IPIPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

IP-in-IP Tunnel.
Then select Create Interface either by selecting Action from the main menu bar or by
Result: The Alcatel-Lucent 1830 PSS ZIC Create IP-in-IP Tunnel window opens.
...................................................................................................................................................................................................
Using the AID text box, the identifier of the specific IP-in-IP tunnel can be modified.
Note: The AID value will be pre-populated with the next available AID. Can be
changed, but usually not necessary
...................................................................................................................................................................................................
Place the cursor in the Local Tunnel Endpoint IP Address text box, then type in the IP
Address of the Local Tunnel Endpoint.
....................................................................................................................................................................................................................................
1830 PSS
3-76
Issue 1 June 2013

....................................................................................................................................................................................................................................
Additional info The local tunnel endpoint address has to be identical to the local NE
address. Use the active FLC IP address.

...................................................................................................................................................................................................
Place the cursor in the Remote Tunnel Endpoint IP Address text box, then type in the IP
Address of the Remote Tunnel Endpoint.
...................................................................................................................................................................................................
In the field Encapsulation Type specify the way of encapsulating IP packets in IP

packets.
GRE
Generic Routing Encapsulation according to RFC2784.
IPINIP
IP-in-IP encapsulation. Encapsulation is according to RFC2003.

...................................................................................................................................................................................................
Using the field Bound 2 LAN, select LAN to which the tunnel is bound.
The only possible value is LAN-OAMP.
...................................................................................................................................................................................................
Using the field Alarm Profile you can reference to an existing IPIPT related Alarm
Severity Assignment Profile instance.
...................................................................................................................................................................................................
Make sure that the settings in the Create IP-in-IP Tunnel window are correct and
corresponds to the settings of the remote tunnel endpoint.
...................................................................................................................................................................................................
Click Apply.
Result: The IP-in-IP tunnel is created.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-77
Issue 1 June 2013

Procedure 3-20: Set the alarm severity profile of an IP-in-IP

tunnel
....................................................................................................................................................................................................................................

tunnel
When to use
Use this procedure to set the alarm severity profile of an IP-in-IP tunnel.
ED-NE-IPIPT
RTRV-NE-IPIPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

IP-in-IP Tunnel.
...................................................................................................................................................................................................
Select the respective IP-in-IP tunnel.

Result: The Alcatel-Lucent 1830 PSS ZIC Edit Alarm Profile Pointer window opens.
...................................................................................................................................................................................................
Using the field Alarm Profile you can reference to an existing IPIPT related Alarm
Severity Assignment Profile instance.
...................................................................................................................................................................................................
Make sure that the settings in the Edit Alarm Profile Pointer window are correct.
....................................................................................................................................................................................................................................
1830 PSS
3-78
Issue 1 June 2013


tunnel
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-79
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete an IP-in-IP Tunnels (IPIPT) between NEs.

DLT-NE-IPIPT
RTRV-NE-IPIPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
IP-in-IP Tunnel.
...................................................................................................................................................................................................
Select the IP-in-IP Tunnel you want to delete.

...................................................................................................................................................................................................
Then select Delete, either by selecting Action from the main menu bar or by using the
Result: The Delete IP-in-IP Tunnel window opens.
...................................................................................................................................................................................................
Click on Yes.
Result: The IP-in-IP Tunnel is deleted.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-80
Issue 1 June 2013

Procedure 3-22: Enter (add) a new static IP route in the IP

routing table
....................................................................................................................................................................................................................................

routing table
When to use
Use this procedure to enter (add) a new static IP route in the IP routing table
ENT-NE-IPRT
IP routing parameters
The NE allows to create multiple static routes to the same (DESTADDR, MASK) via
different interfaces. The METRIC parameter shall be used to decide which of the routes
shall be used for forwarding decisions. The route with the lowest METRIC value shall
take precedence.
Table 3-3
Parameter Name
Meaning
Range
AID
Addresses the interface whose Static

routing entry is being entered.
NETIF
LAN
IPIPT
Destination IP Address
IP address of the destination host or

network (in the format nnn-nnn-nnn-nnn).
The address 0-0-0-0 is used to specify a
default route. If NETMASK is not all '1'
(i.e., a network route is specified), the host
portion of the DESTADDR must be all '0'.
{0-99,101-126, 128- 223} {0-255} - {0- 255} - {0-255}
Route Network Mask
IP subnet Mask of the route.
{0-255} - {0-255} - {0- 255} {0-255}
....................................................................................................................................................................................................................................
1830 PSS
3-81
Issue 1 June 2013


routing table
....................................................................................................................................................................................................................................
Table 3-3
(continued)
Parameter Name
Meaning
Range
Next Hop Router IP Address
Next hop address. It is the IP address of

the next interface in the route (in the
format nnn-nnn-nnn-nnn). The target NE
shall be directly connected to this interface
via the Customer LAN. The address
0-0-0-0 is not allowed. Neither the
network nor the host portion of the address
when viewed in binary format may be all
zeros or all ones.
{1-99,101-126, 128- 223} {0-255} - {0- 255} - {0-255}
The next-hop address can only be given if

the AID references a LAN interface.
Router Metric
Cost Metric of the route. The given value

is used to define precedence between
different provisioned static routes to the
same destination (DESTADDR,MASK)
via different next hop interfaces (AID).
Lower values indicate higher precedence.
Static routes are always taking precedence
over routes, which are dynamically
discovered via routing protocols. If
ADVERTISE is set to Yes, this parameter
is not displayed.
065535
Advertise
Specifies whether the IP route is leaked

into routing protocols.
Y,
N
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
3-82
Issue 1 June 2013


routing table
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectSystem Networking .

Then select IP Routes Create either by selecting Action from the main menu bar or by
Result: The Alcatel-Lucent 1830 PSS ZIC Create IP Routes window opens.
...................................................................................................................................................................................................
In the AID field select the identifier of the local interface to be used for the IP route.
The AID specifies the network interface instance, via which the static route is directing
outgoing traffic:
NETIF-x: a network interface over an ECC / ECC protection group

IPIPT-x: an IP in IP tunnel interface
LAN-OAMP: the OAMP LAN on the active main shelf FLC card.
...................................................................................................................................................................................................
Place the cursor in the Destination IP Address text box, then type in the IP Address of the
destination host or network.
...................................................................................................................................................................................................
Place the cursor in the Route Network Mask text box, then type in the IP subnet Mask of
the route.
...................................................................................................................................................................................................
Place the cursor in the Next Hop Router IP Address text box, then type in the IP address
of the next interface in the route.
Note: Only required if AID is addressing a LAN.
...................................................................................................................................................................................................
In the field Advertise specify whether the IP route is leaked into routing protocols.
Yes
To be set if the NE is configured as ASBR (Autonomous System Border Router).
No (default)
...................................................................................................................................................................................................
Using the field Router Metric you can specify the cost metric of the route
...................................................................................................................................................................................................
Make sure that the settings in the Create IP Route window are correct.
....................................................................................................................................................................................................................................
1830 PSS
3-83
Issue 1 June 2013


routing table
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
Result: The new static route is created.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-84
Issue 1 June 2013

Procedure 3-23: Delete a static IP route from the IP routing

table
....................................................................................................................................................................................................................................

table
When to use
Use this procedure to delete a static IP route from the IP routing table
RTRV-NE-IPRT
DLT-NE-IPRT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System Networking .
Then select IP Routes Manage either by selecting Action from the main menu bar or
Result: The Alcatel-Lucent 1830 PSS ZIC Manage IP Routes window opens.
...................................................................................................................................................................................................
Select the static IP route you want to delete.

...................................................................................................................................................................................................
Click Delete.
Result: The Delete IP Route window opens.
...................................................................................................................................................................................................
Click Apply.
....................................................................................................................................................................................................................................
1830 PSS
3-85
Issue 1 June 2013


table
....................................................................................................................................................................................................................................
Result: The IP route is deleted.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-86
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create the IP address of a trusted Network Time Protocol (NTP)
server.
NTP servers
NTP servers are used for time of day synchronization when the NTP protocol is enabled .
You can enter up to 10 NTP trusted servers.
Note: It is expected that all external time servers are running on the same time-base,
i.e. that all of them are synchronized from a reliable master clock.
Related TL1 command
ENT-NTP-ADDR.
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System.

Then select NTP Create NTP Address either by selecting Action from the main menu
Result: The Alcatel-Lucent 1830 PSS ZIC Create NTP Address window opens.
...................................................................................................................................................................................................
In the field IP address enter the network address of the NTP server.
Note: To separate the fields use a hyphen instead of a dot.
....................................................................................................................................................................................................................................
1830 PSS
3-87
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-88
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to view and delete the IP address of the Network Time Protocol (NTP)
server.
NTP servers
You can enter up to 10 NTP trusted servers.
RTRV-NTP-ADDR
DLT-NTP-ADDR
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select NTP Manage NTP Address either by selecting Action from the main menu
Result: The Alcatel-Lucent 1830 PSS ZIC View NTP Address window opens.
...................................................................................................................................................................................................
Select the network address of the NTP server to be deleted

...................................................................................................................................................................................................
Click Delete.
....................................................................................................................................................................................................................................
1830 PSS
3-89
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Delete NTP Address window opens.
...................................................................................................................................................................................................
Click Apply.
Result: The IP address of the Network Time Protocol (NTP) server is deleted
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-90
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this retrieve parameters and current operating mode. of the Network Time Protocol
(NTP) server.
NTP servers
RTRV-NTP
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select NTP Operating Mode either by selecting Action from the main menu bar
Result: The Alcatel-Lucent 1830 PSS ZIC Operatin Mode window opens.
Possible values are:

FREE-RUNNING
NTP is not enabled, or the NE is not synchronized to an NTP server and is instead
using its own internal clock as a source.
HOLDOVER
NTP is enabled but the NE has lost NTP server connectivity, and is using the last
known clock update to synchronize its clock
NTPSYNC
....................................................................................................................................................................................................................................
1830 PSS
3-91
Issue 1 June 2013

....................................................................................................................................................................................................................................
An NTP server is selected and the NE is using the NTP protocol to synchronize its
clock.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-92
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to specify the global OSPF parameters.

RTRV-OSPF
ED-OSPF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Manage OSPF Parameters either by selecting Action from the main
Result: The Alcatel-Lucent 1830 PSS ZIC Manage OSPF Parameters window opens.
...................................................................................................................................................................................................
Select the OSPF entity.

...................................................................................................................................................................................................
Click Modify.
Result: The Alcatel-Lucent 1830 PSS ZIC Edit OSPF window opens.
...................................................................................................................................................................................................
Using the field Autonomous System Boundary Router State specify if importing of
external routes into OSPF should be enabled or disabled on the NE.
....................................................................................................................................................................................................................................
1830 PSS
3-93
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Using the field Static Route External Metric specify the cost metric value to be set in all
AS-External LSAs (Type 5 LSAs).
This parameter only takes effect, if Autonomous System Boundary Router State was set
to Y.
...................................................................................................................................................................................................
Using the field Static Route External Metric Type specify the metric type to be set in all
AS-External LSAs (Type 5 LSAs).
The metric value is assumed comparable to intra-AS metric values.
INT
Internal metric type (metric type 1).
EXT
External metric type (metric type 2). The metric value is assumed higher than the path
cost of any intra-AS path.
to Y.
...................................................................................................................................................................................................
Using the field Default Route External Metric specify the cost metric value to be set in
all AS-External LSAs (Type 5 LSAs), which result from Advertised default routes (see
Procedure 3-22: Enter (add) a new static IP route in the IP routing table (p. 3-81)).
to Y.
...................................................................................................................................................................................................
Using the field Default Route External Metric Type specify the metric type to be set in
all AS-External LSAs (Type 5 LSAs), which result from ADVERTISED default routes.
INT
Internal metric type (metric type 1). The metric value is assumed comparable to
intra-AS metric values.
EXT
External metric type (metric type 2). The metric value is assumed higher than the path
cost of any intra-AS path.
to Y.
...................................................................................................................................................................................................
Click Apply.
....................................................................................................................................................................................................................................
1830 PSS
3-94
Issue 1 June 2013

....................................................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-95
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create an OSPF area.

The NETIF, LAN, and IPIPT interfaces can then assigned to the OSPF area thus created.
The NE can be connected to up to 4 OSPF areas. One of these 4 areas is the backbone
area, which is always present and cannot be deleted. Only 3 non-backbone areas can be
created.
ENT-OSPF-AREA
Before you begin

Before configuring an OSPF area the OSPF Router ID of the NE must be configured
(see Procedure 3-3: Set the FLC IP Addresses of the NE (p. 3-31)).The loopback IP
address of the NE is also used as OSPF router Id.
Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Create OSPF Area either by selecting Action from the main menu
Result: The Alcatel-Lucent 1830 PSS ZIC Create OSPF Area window opens.
...................................................................................................................................................................................................
In the field AID select an OSPF area identifier for the area you want to create.
...................................................................................................................................................................................................
In the field Area Type specify the type of the OSPF area.
NORM
....................................................................................................................................................................................................................................
1830 PSS
3-96
Issue 1 June 2013

....................................................................................................................................................................................................................................
This OSPF area is a Normal Area
STUB
This OSPF area is a STUB area

...................................................................................................................................................................................................
Using Stub Default Metric spinner select the value to be used or type the value directly in
the field.
Only relevant for stub areas
...................................................................................................................................................................................................
Using the field Import Type 3 LSAs you can specify if the Type 3 LSAs (Summary LSAs)
are imported into a stub area or a default route will be advertised. Set this parameter to
No makes the area to a totally-stubby area.
...................................................................................................................................................................................................
Click Apply.
Result: The OSPF area is created.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-97
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify an OSPF area.

ED-OSPF-AREA
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Manage OSPF Area either by selecting Action from the main menu
Result: The Alcatel-Lucent 1830 PSS ZIC Manage OSPF Area window opens.
...................................................................................................................................................................................................
Select the OSPF area you want to modify and click Modify.
Result: The Alcatel-Lucent 1830 PSS ZIC Edit OSPF Area window opens.
...................................................................................................................................................................................................
In the field Area Type specify the type of the OSPF area.
NORM
This OSPF area is a Normal Area
STUB
....................................................................................................................................................................................................................................
1830 PSS
3-98
Issue 1 June 2013

....................................................................................................................................................................................................................................
This OSPF area is a STUB area

...................................................................................................................................................................................................
Using Stub Default Metric spinner select the value to be used or type the value directly in
the field.
...................................................................................................................................................................................................
Using the field Import Type 3 LSAs you can specify if the Type 3 LSAs (Summary LSAs)
are imported into a stub area or a default route will be advertised.
Note: Settings this parameter to No makes the area to a totally-stubby area.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-99
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete an OSPF area.

DLT-OSPF-AREA
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Manage OSPF Area either by selecting Action from the main menu
Result: The Alcatel-Lucent 1830 PSS ZIC Manage OSPF Area window opens.
...................................................................................................................................................................................................
Select the OSPF area you want to delete and click Delete.
Result: The Alcatel-Lucent 1830 PSS ZIC Delete OSPF Area window opens.
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-100
Issue 1 June 2013

....................................................................................................................................................................................................................................


Field/parameter ...
Values
Meaning...
AID
Specifies an access Identifier of the

OSPF area
OSPF Area Id
Area ID of the OSPF Area. This ID has

the format of an IP Address. The ID 00-0-0 is not allowed since the backbone
area always exists and is automatically
enabled/disabled.
Area Type
NORM
OSPF Area Type.
This OSPF area is a

Normal Area
STUB
This OSPF area is a

STUB area
Stub Default Metric (1
... 65535)
Default: 1
Range:
[1..65535]
Import Type 3 LSAs
Type 3 LSAs are

imported
Determines if the Type 3 LSAs

(Summary LSAs) are imported into a
stub area or not.
Type 3 LSAs are NOT

imported generally.
Instead, only one Type 3
LSA, which contains a
default route, is
imported. This makes the
area a totally stubby
area.
....................................................................................................................................................................................................................................
1830 PSS
3-101
Issue 1 June 2013

Procedure 3-31: Configure the IP address range for the

OSPF area
....................................................................................................................................................................................................................................
Procedure 3-31: Configure the IP address range for the OSPF

area
When to use
Use this procedure to configure IP address ranges for OSPF areas on an OSPF Area
Border Router (ABR).
The OSPF IP RANGE is used to summarize and filter out routes between OSPF Areas. If
an OSPF IP Range is not specified, then all routes are sent out of the area as is. Up to
three (3) OSPF IP address ranges can be configured per OSPF area.
ENT-OSPF-IPRANGE
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Create IP Range either by selecting Action from the main menu bar
Result: The Alcatel-Lucent 1830 PSS ZIC Create OSPF IP Range window opens.
...................................................................................................................................................................................................
In the field AID select the respective OSPF area.

...................................................................................................................................................................................................
Place the cursor in the Area ID text box, then type in the identifier for the OSPF area.
....................................................................................................................................................................................................................................
1830 PSS
3-102
Issue 1 June 2013

Procedure 3-31: Configure the IP address range for the

OSPF area
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the field Advertise Address specify if the summary address is advertised outside the
area or not.
Yes
used to summarize routes
No
used to filter out routes

...................................................................................................................................................................................................
Place the cursor in the Ip Address text box, then type in the IP address prefix of this
address range.
Together with RANGEMASK, this specifies the address range. The network portion
of the address when viewed in binary format may not be all zeros or all ones, the host
portion must be all zeros.
...................................................................................................................................................................................................
Place the cursor in the Range Mask text box, then type in the range mask.
Together with IP address prefix, this specifies the address range. The network portion
of the address when viewed in binary format may not be all zeros or all ones, the host
portion must be all zeros.
...................................................................................................................................................................................................
Click Apply.
Result: The IP address range for the OSPF area is configured.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-103
Issue 1 June 2013

Procedure 3-32: Delete the IP address range of an OSPF

area
....................................................................................................................................................................................................................................

When to use
Use this procedure to delete an OSPF IP address range at an OSPF Area Border Router
(ABR).
The OSPF IP RANGE is used to summarize and filter out routes between OSPF Areas. If
an OSPF IP Range is not specified, then all routes are sent out of the area as is. Up to
three (3) OSPF IP address ranges can be configured per OSPF area.
DLT-OSPF-IPRANGE
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Manage IP Range either by selecting Action from the main menu bar
Result: The Alcatel-Lucent 1830 PSS ZIC Manage OSPF IP Range window opens.
...................................................................................................................................................................................................
Select the OSPF IP range to be deleted.

...................................................................................................................................................................................................
Click Delete.
....................................................................................................................................................................................................................................
1830 PSS
3-104
Issue 1 June 2013

Procedure 3-32: Delete the IP address range of an OSPF

area
....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Network Interfaces Remove OSPF IP
Range Dialog opens.
...................................................................................................................................................................................................
Click Apply.
Result: The OSPF IP range is removed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-105
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to specify the OSPF interface parameters.

The NE can be part of up to 4 OSPF areas, out of which one is the backbone area.
Note: External IP routes (configured via ENT-NE-IPRT command with
ADVERTISE=Y) are only advertised into the OSPF routing domain, if the NE is
configured as ASBR via the ED-OSPF command, and the NE is not in a stub area. If
this command moves the last OSPF interface from a non-stub area to a stub area (via
the AREA parameter), previously advertised external routes will no longer be
advertised.
RTRV-OSPF-IF
ED-OSPF-IF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Manage OSPF Interface Parameters either by selecting Action
from the main menu bar or by using the context menu opened with the right mouse
button.
Result: The Alcatel-Lucent 1830 PSS ZIC Manage OSPF Interface Parameters
window opens.
...................................................................................................................................................................................................
Select the OSPF enabled entity, whose OSPF interface parameters are to be edited.
....................................................................................................................................................................................................................................
1830 PSS
3-106
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OSPF enabled entities can be selected:
IPIPT-{1-64}
Internet Protocol in Internet Protocol Tunnel)
LAN-OAMP
Customer LAN
NETIF-{1-512}

...................................................................................................................................................................................................
Click on Modify.
Result: The Alcatel-Lucent 1830 PSS ZIC Edit OSPF Interface window opens.
...................................................................................................................................................................................................
Using the field Status specify whether the OSPF protocol is enabled or disabled on the
addressed network interface.
...................................................................................................................................................................................................
In the field Area select the OSPF area the interface should belong to.
...................................................................................................................................................................................................
Using the field Hello Interval Timer specify the OSPF Hello interval timer in seconds.
Factory default: 10 seconds
Note: This value should not be modified. It must be equal in all routers in order to
enable OSPF adjacencies between them.
...................................................................................................................................................................................................
Using the field Dead Timer specify the OSPF Router Dead timer in seconds. Factory
default: 40 seconds
Note: This value should not be modified. It must be equal in all routers in order to
enable OSPF adjacencies between them.
...................................................................................................................................................................................................
Using the field Cost Metric specify the cost metric of the route.
Additional information Factory default values:
1 for LAN,
7 for ODU4/OTU4 GCC

18 for ODU3E2/OTU3E2 GCC
19 for ODU3/OTU3 GCC
74 for ODU2e/OTU2e GCC
....................................................................................................................................................................................................................................
1830 PSS
3-107
Issue 1 June 2013

....................................................................................................................................................................................................................................
76 for ODU2/OTU2 GCC

200 for IPIPT,
...................................................................................................................................................................................................
Using the field Router Priority specify the OSPF Router Priority.
Note: Router Priority is only relevant for Designated Router selection on broadcast
networks (LAN-OAMP).
...................................................................................................................................................................................................
10
Using the field Passive Mode specify the OPSF passive mode.
Additional information Factory Default:
Yes on LAN,
N on NETIF, and IPIPT
Possible values:
Yes
Passive Mode is enabled, i.e. no OSPF packets are sent via the interface, but the
interface is advertised as stub network in Router LSAs.
No
Passive Mode is disabled, i.e. OSPF packets are sent via the interface.
...................................................................................................................................................................................................
11
Click Apply.
Result: The specifications are sent.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-108
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify the OSPF authentication settings.

The settings are:
Authentication enabling/disabling
Authentication algorithm (for future extensions)
Authentication key and key identifier
ED-OSPFIF-SECU
RTRV-OSPFIF-SECU
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Then select OSPF Manage OSPF Authentication either by selecting Action from the
main menu bar or by using the context menu opened with the right mouse button.
Result: The Alcatel-Lucent 1830 PSS ZIC OSPF Authentication Settings window
opens.
...................................................................................................................................................................................................
Select the OSPF interface, for which you want to modify the OSPF authentication setting.
The following OPSF enabled entities can be selected:
IPIPT-{1-64}
....................................................................................................................................................................................................................................
1830 PSS
3-109
Issue 1 June 2013

....................................................................................................................................................................................................................................
Internet Protocol in Internet Protocol Tunnel)
LAN-OAMP
Customer LAN
NETIF-{1-512}

...................................................................................................................................................................................................
Click on Modify.
Result: The Alcatel-Lucent 1830 PSS ZIC Modify Authentication Settings window
opens.
...................................................................................................................................................................................................
Using the field Authentication specify the authentication algorithm. This parameter can
only be set away from NONE if a valid KEY and ID are set. If it is changed from MD5 to
NONE the formerly provisioned values for KEY and KEYID will be kept.
NONE (default)
disables the OSPF authentication
MD5
MD5 is used for the OSPF authentication

...................................................................................................................................................................................................
In the field KEY enter the OSPF Authentication Key used for MD5 128bit hash value
calculation.
Note: The OSPF Authentication Key is handled like a password, i.e. it is suppressed
in any response and cannot retrieved.
The string can be 1 to 16 characters.
...................................................................................................................................................................................................
Using the field ID specify the OSPF Authentication Key ID to be used for MD5 1hash
value key calculation.
Range: 1- 255
...................................................................................................................................................................................................
Click Apply.
Result: The specifications are sent.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-110
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section describes procedures which have to be performed for data communication
setup in a WDM application.
Contents
Procedure 3-35: View network (NE name, NE IP, software release) map
information
3-113
Network Map
3-114
3-115
3-116
3-117
3-118
3-119
IP Routes
3-120
3-121
3-122
Create OSPF Area
3-123
3-127
OSPF Areas
3-128
3-132
OSPF Area Details
3-133
3-137
3-138
3-140
Create NTP Server
3-142
3-143
NTP Properties
3-145
3-146
....................................................................................................................................................................................................................................
1830 PSS
3-111
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
Create NTP Key
3-147
3-148
3-149
....................................................................................................................................................................................................................................
1830 PSS
3-112
Issue 1 June 2013

Procedure 3-35: View network (NE name, NE IP, software

release) map information
....................................................................................................................................................................................................................................
Procedure 3-35: View network (NE name, NE IP, software

release) map information
When to use
Use the following procedure to view network (NE name, NE IP, software release) map
information.
Before you begin
The following procedures are available via the WebUI after the user initially connects to
Instructions
...................................................................................................................................................................................................
In the WebUI, select Reports > Network Map.

Result: The Network Map information is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-113
Issue 1 June 2013

Network Map
....................................................................................................................................................................................................................................
Network Map
Attribute
Value/Format
Network Element Name
Network Element IP
Software Release
Additional Info
Name of network element
found on the network via
OSC and GCC interfaces.
<IP address>
IP address of the network

element.
Software release of the
network element.
....................................................................................................................................................................................................................................
1830 PSS
3-114
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view / modify IP route metric settings.

Before you begin
Instructions
Note: The WebUI allows the user to view and/or modify the system-wide IP route
parameters for metric settings.
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP Route Redistribute Metrics.
Result: The IP Route Redistribute Metric Settings screen is displayed with current
values.
...................................................................................................................................................................................................
To modify the metric settings, enter attribute values and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-115
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Static Route Metric Type
{1,2}
A metric type of 1 adds

internal OSPF cost when a
static route is redistributed. A
metric type of 2 does NOT
add internal OSPF cost when
a static route is redistributed.
Static Route Metric Value
{0-16777214}
The cost of the static route at

every node distributed to.
Default Route Metric Type
{1,2}
A metric type of 1 adds

internal OSPF cost when the
default route is redistributed.
A metric type of 2 does NOT
add internal OSPF cost when
the default route is
redistributed.
Default Route Metric Value
{0-16777214}
The cost of the default route

at every node distributed to.
....................................................................................................................................................................................................................................
1830 PSS
3-116
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create IP static route.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP Routes.

Result: The IP Routes screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create Static IP Route screen is displayed.
...................................................................................................................................................................................................
To create the default route, select Default Route.

...................................................................................................................................................................................................
Enter attribute values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-117
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Default Route
(checkbox)
Indicates whether the route is

the default route. If yes,
Destination Address and
Mask are set to 0.0.0.0. Only
one default route may be
specified on the NE.
Destination IP
<IP address>
IP address of the destination

host or network.
Mask
<IP address>
IP subnet mask of the route.
Next Hop
<IP address>
IP address of the next

interface in the route, also
known as the gateway
address.
Distance
{1-255} (default = 1)
Used to calculate the most

efficient routes through the
network by summing all of
the distances to a destination
and using the route with the
lowest distance.
If the Redistribute field is set

to No, the default value of
Distance is 1.
Redistribute
Yes
No
Specifies whether the IP route

is leaked into the OSPF
routing protocols.
No indicates that the route
is only known on the local
NE.
Yes indicates that the route
is leaked into OSPF and
distributed over the network.
....................................................................................................................................................................................................................................
1830 PSS
3-118
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view all IP routes.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP Routes.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-119
Issue 1 June 2013

IP Routes
....................................................................................................................................................................................................................................
IP Routes
Attribute
Values/Format
Additional Info
Destination IP
<IP address>
IP address of the destination

host or network.
Mask
<IP address>
IP subnet mask of the route.
Next Hop
<IP address>
IP address of the next

interface in the route, also
known as the gateway
address.
Distance
{1-255} (default = 1)
Used to calculate the most

efficient routes through the
network by summing all of
the distances to a destination
and using the route with the
lowest distance.
If the Redistribute field is set

to No, the default value of
Distance is 1.
Redistribute
Yes
No
Specifies whether the IP route

is leaked into the OSPF
routing protocols.
No indicates that the route
is only known on the local
NE.
Yes indicates that the route
is leaked into OSPF and
distributed over the network.
Create

entering data to add a new
static route.
Delete
Delete a selected static route.

Only a static route previously
created by the user may be
deleted.
NOTE: If an IP Route is
deleted, loss of
communication may occur.
....................................................................................................................................................................................................................................
1830 PSS
3-120
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to delete IP static route.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > IP routes.

...................................................................................................................................................................................................
Select the IP Route and click Delete.

Note: For delete, a warning message is displayed to the user indicating that a loss of
communication may occur. The user can continue with the delete request or cancel.
Upon continuing with the request, the delete request will be sent to the NE for
execution.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-121
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create OSPF area.

Before you begin
Instructions
Note: The WebUI supports displaying all OSPF Areas configured on the NE. To help
in modifying OSPF Area ID on the USRPNL ports, the WebUI displays a picklist of
Area IDs configured. Up to 4 OSPF areas (including the default) may be configured
on the NE.
...................................................................................................................................................................................................
In the WebUI, select Administration > Networking > OSPF Areas.

Result: The OSPF Areas screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create OSPF Areas screen is displayed.
...................................................................................................................................................................................................
Enter attribute values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-122
Issue 1 June 2013

Create OSPF Area
....................................................................................................................................................................................................................................
Create OSPF Area

Attribute
Values/Format
Additional Info
Area Index
{0-3}

OSPF area. The value 0 is
reserved for the default Area
ID (0.0.0.0).
Area ID
<IP address>
IP address that uniquely

identifies the OSPF area.
Area Type
Normal
Specifies the OSPF area type.
Stub
Normal areas are defined as

areas that can accept
intra-area, inter-area and
external routes.
Totally Stub
NSSA
NSSA Totally Stub
Stub areas do not accept
routes belonging to external

autonomous systems (AS).
However, these areas have
inter-area and intra-area
routes. This reduces the size
of the routing databases for
the area's internal routers.
Routers in the stub area also
contain a default route which
is advertised to the area by the
Area Border Router (ABR).
Totally Stub areas do not
allow routes other than

intra-area and the default
route to be propagated within
the area. This further reduces
the size of the routing
databases for the area's
internal routers. The ABR
advertises a default route into
the area and all the routers
belonging to this area use the
default route to send any
traffic outside the area.
....................................................................................................................................................................................................................................
1830 PSS
3-123
Issue 1 June 2013

Create OSPF Area
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Area Type
NSSA (Not So Stub Areas) can
(continued)
import AS external routes

from within the area and send
them to other areas, but
cannot receive AS external
routes from other areas.
Inter-area and intra-area
routes are allowed along with
a default route which is
advertised to the area by the
ABR.
NSSA Totally Stub areas are
similar to nssa with the added

restriction that inter-area
routes are not allowed.
For the default area (0.0.0.0),
this field is read-only.
DNS Opaque LSAs
Distributed
Yes
WaveKey Opaque LSAs

Distributed
Yes
No
No
Specifies whether opaque

LSAs for the DNS application
are distributed into this OSPF
area and received from this
area. DNS opaque LSAs can
only be enabled in one OSPF
area.
LSAs for the Wave Key
application are distributed
into this OSPF area and
received from this area. Wave
Key opaque LSAs can only
be enabled in one OSPF area.
....................................................................................................................................................................................................................................
1830 PSS
3-124
Issue 1 June 2013

Create OSPF Area
....................................................................................................................................................................................................................................
Attribute
NSSA Router Translation
Values/Format
Candidate
Always
Never
Not Applicable
Additional Info
Determines behavior of
NSSA ABR router translation
of internal area type 7 LSAs
to type 5 LSAs, which get
propagated into other areas.
Candidate: OSPF selects one
of candidate routers to be a
translator for this area.
Always: The router will
always be used as translator
for this area.
Never: The router will never
be used as translator for this
area.
Not Applicable: Value with
Area Type is Normal, Stub or
Totally Stub.
This field is only applicable if
the Area Type field is set to
NSSA or NSSA Totally Stub.
ABR Default Route Cost
{0-16777215}
Not Applicable
Specifies the cost for the

default route originated by
Stub, Totally Stub, NSSA or
NSSA Totally Stub area ABR.
This field is not applicable if
Normal.
....................................................................................................................................................................................................................................
1830 PSS
3-125
Issue 1 June 2013

Create OSPF Area
....................................................................................................................................................................................................................................
Attribute
Virtual Link IP
Values/Format
<IP address>
Not applicable
Additional Info
Allows for the creation of a
virtual link for this area.
OSPF requires that all areas
attach directly to area 0.0.0.0,
but the attachment need not
be physical. One can take any
physical arrangement of areas
and attach them logically
through OSPF virtual links.
NOTE: Specify the Loopback
interface IP address of the NE
to terminate the virtual link.
This NE should have an
interface that is connected to
Area 0.0.0.0 and a non 0.0.0.0
Area.
NOTE: A virtual link must be
configured on both NEs.
Virtual links can not be
established through Area
0.0.0.0.
Normal.
....................................................................................................................................................................................................................................
1830 PSS
3-126
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view OSPF areas.

Before you begin
Instructions
...................................................................................................................................................................................................

Result: The OSPF Areas are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-127
Issue 1 June 2013

OSPF Areas
....................................................................................................................................................................................................................................
OSPF Areas
Attribute
Values/Format
Additional Info
Area Index
{0-3}

ID (0.0.0.0).
Area ID
<IP address>

Area Type
Normal
Stub

external routes.
Totally Stub
NSSA
NSSA Totally Stub


....................................................................................................................................................................................................................................
1830 PSS
3-128
Issue 1 June 2013

OSPF Areas
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Area Type
(continued)

ABR.

DNS Opaque LSAs
Distributed
Yes
WaveKey Opaque LSAs

Distributed
Yes
No
No

area.
....................................................................................................................................................................................................................................
1830 PSS
3-129
Issue 1 June 2013

OSPF Areas
....................................................................................................................................................................................................................................
Attribute
Values/Format
Candidate
Always
Never
Not Applicable
Additional Info
for this area.
area.
Totally Stub.
{0-16777215}
Not Applicable

Normal.
....................................................................................................................................................................................................................................
1830 PSS
3-130
Issue 1 June 2013

OSPF Areas
....................................................................................................................................................................................................................................
Attribute
Virtual Link IP
Values/Format
<IP address>
Not applicable
Additional Info
Area 0.0.0.0 and a non 0.0.0.0
Area.
0.0.0.0.
Normal.
Create

entering data to add a new
OSPF Area. A maximum of 3
OSPF areas may be created,
in addition to the default
backbone area (0.0.0.0)
Details

modifying data for a selected
OSPF Area.
Delete
Delete a selected OSPF Area.

The system-configured
default area (0.0.0.0) cannot
be deleted.
....................................................................................................................................................................................................................................
1830 PSS
3-131
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view/modify OSPF details.

Before you begin
Instructions
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the OSPF area and click Details.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-132
Issue 1 June 2013

OSPF Area Details
....................................................................................................................................................................................................................................
OSPF Area Details

Attribute
Values/Format
Additional Info
Area Index
{0-3}

ID (0.0.0.0).
Area ID
<IP address>

Area Type
Normal
Stub

external routes.
Totally Stub
NSSA
NSSA Totally Stub


....................................................................................................................................................................................................................................
1830 PSS
3-133
Issue 1 June 2013

OSPF Area Details
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Area Type
(continued)

ABR.

DNS Opaque LSAs
Distributed
Yes
WaveKey Opaque LSAs

Distributed
Yes
No
No

area.
....................................................................................................................................................................................................................................
1830 PSS
3-134
Issue 1 June 2013

OSPF Area Details
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Candidate
Always
Never
Not Applicable

for this area.
area.
Totally Stub.
{0-16777215}
Not Applicable

Normal.
....................................................................................................................................................................................................................................
1830 PSS
3-135
Issue 1 June 2013

OSPF Area Details
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Virtual Link IP
<IP address>

Not applicable

Area 0.0.0.0 and a non 0.0.0.0
Area.
0.0.0.0.
Normal.
....................................................................................................................................................................................................................................
1830 PSS
3-136
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to delete OSPF area.

Before you begin
Instructions
Note: The WebUI will not allow deletion of Area ID = 0.0.0.0.

...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the OSPF Area and click Delete.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-137
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to configure orderwire function.

Before you begin
Instructions
Engineering Order Wire (EOW) function is a traditional SONET/SDH function which

utilizes E1/2 channels to provide voice communication between sites. 1830 PSS offers
EOW function emulation via the VOIP port. The implementation provides a dedicated
LAN port and IP routing in enabling VOIP communication. The only setup needed is IP
configuration on the port and properly configure the IP phone used. The following
procedure details the VOIP configuration setup between two NEs.
...................................................................................................................................................................................................
In the WebUI expand the equipment tree to select System > PSS-32 or PSS-16 Shelf >
USRPNL > VOIP
Note: On PSS-36 shelf, this is on the MT0C card: System > PSS-36 Shelf > MT0C >
VOIP
Result: In the Port Details tab, the Port Interface Settings screen is displayed.
...................................................................................................................................................................................................
Configure the first NE IP Address (e.g., 160.1.1.2) and VOIP phone IP (e.g., 160.1.1.3)
...................................................................................................................................................................................................
Configure the second NE IP Address (e.g., 170.1.1.2) and VOIP phone IP (eg: 170.1.1.3)
...................................................................................................................................................................................................
For both NEs and VOIP phones, configure the Mask as 255.255.240.0
...................................................................................................................................................................................................
For both NEs, click on the OSPF details tab and set OSPF routing to ENABLED or
REDISTRIBUTE.
...................................................................................................................................................................................................
For both VOIP phones, configure Default Gateway as the VOIP port IP of the
corresponding NEs.
....................................................................................................................................................................................................................................
1830 PSS
3-138
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click on the Port Details tab and select Port Enabled for both NEs.
E...................................................................................................................................................................................................
N D O F S T E P S
To check if EOW setup is correct
Check to ensure that the following values are configured for the VOIP port for both NEs:
Present Link Speed: 100Mbps

Present Duplex Mode: Full
Link Integrity: Up
When dialed from one VOIP phone to the other (e.g., dialing 160.1.1.3 from 170.1.1.3 or
vice versa), voice communication should be heard at both ends. The communication is
point-to-point (one caller and one callee at a time) as long as the OSC is connected
between the NEs. If five NEs are connected in different directions through OSC, then
each NE can communicate to the other four NEs (one at a time). There is no broadcast
capability.
....................................................................................................................................................................................................................................
1830 PSS
3-139
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create / view the NTP server.

Supported features
The NE supports the following features:
Providing time of day setting (including both time and date) by user command.
Ability to provide time stamping accurate to within +/- 500 msec. per day.
Synchronize the NE clock from an NTP server.
Support customer provisionable time offset from UTC for all system time displays
and event time stamps.
Network Time Protocol (NTP) synchronization
The NE is capable of synchronizing its time of day via Network Time Protocol (NTP). It
is possible to provision up to three (3) NTP servers and it is also possible to delete an
NTP server. The user can retrieve the attributes and service state of all designated NTP
servers via user command. The following applies:
It is possible to enable or disable NTP synchronization. When NTP protocol is

enabled, the NE internal time of day clock uses the calculated UTC time from the
selected NTP server, as modified by the user-provisioned offset. All messages, event
reports, logs, and events that carry time stamps will use this time of day (NTP UTC
time + provisioned offset).
When NTP protocol is disabled after having been synchronized to an NTP server, the
NE internal clock adopts the last value of the NTP server time as its set time and
continues to calculate time stamps using the provisioned offset.
The NE supports the following time-of-day synchronization modes:

non-synchronized, free-running mode: NTP is not enabled, and the NE is not
synchronized to an NTP server and is instead using its own internal clock as a
source.
synchronized mode: the NE is using the NTP protocol to synchronize to an NTP
server. The NE is polling the NTP server and periodically making corrections to
its internal clock so as to maintain the same clock time as the NTP server.
The current time-of-day synchronization mode is retrievable via user command

NTP server addresses and NTP enable/disable status is able to survive a database
backup and restore.
....................................................................................................................................................................................................................................
1830 PSS
3-140
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: When configuring NTP servers on an NE network the provisioned NTP server
IP addresses should be that of external NTP servers and not the IP of GNE(s).
Appropriate DCN provisioning must be done such that the external NTP servers are
reachable from all NEs within the network.
Before you begin
Instructions
Note: Up to 3 NTP servers are supported on the NE.

...................................................................................................................................................................................................
In the WebUI, select Administration > NTP > Servers.

Result: The NTP Servers screen is displayed.
...................................................................................................................................................................................................
To create an NTP server click Create.

Result: The Create NTP Server screen is displayed.
...................................................................................................................................................................................................
Enter NTP server values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-141
Issue 1 June 2013

Create NTP Server
....................................................................................................................................................................................................................................
Create NTP Server

Attribute
Values/Format
Additional Info
Index
{1-3}
Unique index of the NTP

server. Up to 3 servers can be
added to the NE.
Server IP
<IP address>
IP address of the NTP server.
....................................................................................................................................................................................................................................
1830 PSS
3-142
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view the NTP properties.

Network Time Protocol (NTP) synchronization
The NE is capable of synchronizing its time of day via Network Time Protocol (NTP). It
is possible to provision up to three (3) NTP servers and it is also possible to delete an
NTP server. The user can retrieve the attributes and service state of all designated NTP
servers via user command. The following applies:
It is possible to enable or disable NTP synchronization. When NTP protocol is

enabled, the NE internal time of day clock uses the calculated UTC time from the
selected NTP server, as modified by the user-provisioned offset. All messages, event
reports, logs, and events that carry time stamps will use this time of day (NTP UTC
time + provisioned offset).
When NTP protocol is disabled after having been synchronized to an NTP server, the
NE internal clock adopts the last value of the NTP server time as its set time and
continues to calculate time stamps using the provisioned offset.
The NE supports the following time-of-day synchronization modes:

non-synchronized, free-running mode: NTP is not enabled, and the NE is not
synchronized to an NTP server and is instead using its own internal clock as a
source.
synchronized mode: the NE is using the NTP protocol to synchronize to an NTP
server. The NE is polling the NTP server and periodically making corrections to
its internal clock so as to maintain the same clock time as the NTP server.
The current time-of-day synchronization mode is retrievable via user command

NTP server addresses and NTP enable/disable status is able to survive a database
backup and restore.
Note: When configuring NTP servers on an NE network the provisioned NTP server
IP addresses should be that of external NTP servers and not the IP of GNE(s).
Appropriate DCN provisioning must be done such that the external NTP servers are
reachable from all NEs within the network.
Before you begin
....................................................................................................................................................................................................................................
1830 PSS
3-143
Issue 1 June 2013

....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
Select Administration > NTP > Properties

Result: The Network Time Protocol Properties screen is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-144
Issue 1 June 2013

NTP Properties
....................................................................................................................................................................................................................................
NTP Properties
Attribute
Values/Format
NTP Enabled
(checkbox)
Clock Mode
Free Running
Additional Info
Holdover
The current operating mode

of the NTP service:
NTP Sync
Free RunningNTP is
not enabled, or the NE is
not synchronized to an
NTP server and is instead
using its own internal
clock as a source.
HoldoverNTP is
enabled but the NE has
lost NTP server
connectivity, and is using
the last known clock
update to synchronize its
clock.
NTP SyncNTP is
enabled, and the NE is
using the NTP protocol to
synchronize to an NTP
server.
NTP Sync, Redundant

(Network Time Protocol
Synchronized
Redundant)NTP is
enabled and synchronized
to a reference server, and
a backup reference is also
available to become the
primary reference.
NTP Sync, Redundant
Current NTP Server
<IP address>
IPv4 network address of an

NTP server.
Estimated Drift
(microseconds/seconds)
x.xxxxxx
Estimated drift rate of the

current NTP server.
Estimated Time Offset

(seconds)
x.xxxxxx
The type of time being

returned.
....................................................................................................................................................................................................................................
1830 PSS
3-145
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create/view NTP keys.

Before you begin
Instructions
Note: The WebUI displays a table with all the NTP keys configured on the NE. The
following attributes are displayed: Index, Type, Key. The WebUI supports create,
modify, view and delete of an NTP key.
...................................................................................................................................................................................................
In the WebUI, select Administration > NTP > Keys.

Result: The NTP Keys screen is displayed.
...................................................................................................................................................................................................
To create an NTP key click Create.

Result: The Create NTP Key screen is displayed.
...................................................................................................................................................................................................
Enter NTP Key values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-146
Issue 1 June 2013

Create NTP Key
....................................................................................................................................................................................................................................
Create NTP Key

Attribute
Values/Format
Index
{1-65535}
Type
MD5
Additional Info
Unique index of the NTP
server.
SHA1
Key
<0-40 chars>
NTP Server jitter

milliseconds.
....................................................................................................................................................................................................................................
1830 PSS
3-147
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to set date and time manually.

Manual time of day synchronization
The following apply for manual (non-NTP) Time of Day synchronization.
The NE date and time are capable of being modified via user interface command
If NTP synchronization is enabled, attempts to modify date and time are denied.
The system ensures the date/time is set and reported within the valid range supported
by the user commands. The valid date range is from 1-Jan-2005 to 31-Dec-2059.
The NE preserves the correct time and date through a restart/reboot of the processors
where there is no loss of power, and also when a module or device (hard disk) has
been replaced.
The NE internal time of day clock uses the calculated UTC time from the selected
NTP server, when enabled, as modified by the user-provisioned offset. All messages,
event reports, logs, and events that carry time stamps use this time of day.
Note: Time/date changes may cause partial or incomplete PM data, depending on the
magnitude of the time change. Time/date changes will not affect the application of
security measures such as password aging.
Before you begin
Instructions
Note: The valid range for year is 2008 to 2020. Date and time cannot be modified if
NTP synchronization is enabled.
...................................................................................................................................................................................................
In the WebUI, select Administration > Date and Time.

Result: The Date and Time Administration screen is displayed.
...................................................................................................................................................................................................
Enter date and time values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
3-148
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Date
<day:month:year>
Time
<hour:minute:second>
Specifies the date and time on

the NE. The date/time cannot
be set if the NE is using NTP.
Time Zone Name
<0-35 chars>
This specifies the time zone to

show when displaying the
time. It is also used to adjust
the time displayed according
to the offset associated with
the selected time zone.
Standard time zone names
and codes are supported.
In addition, offsets from the
Universal Time Code (UTC)
may be specified.For
example, UTC+7 or
UTC-3.The offset hours may
range from -14 through
+12.Minutes may also be
specified in 15 minute
increments.For example,
UTC+7:30 or UTC-3:15.
....................................................................................................................................................................................................................................
1830 PSS
3-149
Issue 1 June 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
3-150
Issue 1 June 2013
4 onverged node set up

C
procedures
Overview
Purpose
This chapter describes the procedures which have to be performed for setting up the
converged node of OCS and WDM application.
Related information
For background information see Alcatel-Lucent 1830 PSS Product Information and
Planning Guide (PIPG),
chapter 1 Introduction, section Alcatel-Lucent 1830 Photonic Service Switch

(PSS) profile,
Contents
Procedure 4-1: Connect OCS application to WDM application
4-2
...................................................................................................................................................................................................................................
1830 PSS
4-1
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to connect OCS application to WDM application.

Coupling OSC and WDM compound
The Alcatel-Lucent 1830 PSS system supports WDM functionality and OCS switching
functionality within one node. Both functionalities are separated into two different
compounds:
The photonic compound supporting WDM functionality

The switching compound supporting mainly OCS switching functionality
Each compound consists of one main shelf and zero or more extension shelves. Each
main shelf has an own IP address and is attached to management communication via
OAM port.
Interconnection via IP enables to function as a converged node, supporting WDM and
OCS.
One of the main shelves can be the host for GMRE.
....................................................................................................................................................................................................................................
1830 PSS
4-2
Issue 1 June 2013
....................................................................................................................................................................................................................................
Figure 4-1 Converged node view (card level)
Uplink cards
Uplink cards can be used within a PSS-36 or PSS-64 shelf of a OCS application. The
uplink cards are auto-provisioned.
Autoprovisioning means assigning default configuration parameters to an equipment
component at the time when it is physical plugged in first. The default configuration
parameters are read from the NE database.
....................................................................................................................................................................................................................................
1830 PSS
4-3
Issue 1 June 2013
....................................................................................................................................................................................................................................
Before you begin
have a valid user login and password,

be connected to the subject NE,
have proper User Community Authorization Level to perform this task.,
assure that the rotary switches on the Bus Termination Cards (BT36, BTC3T8) on the
master shelf and extension shelf are correctly set (see Alcatel-Lucent 1830 PSS
Installation and System Turn-Up Guide (ITG))
assure both compound masters have IP connectivity
must have entered the IP address of photonic partner NE using EZ setup tool, refer to
Procedure 20-1: Initialize the NE using EZ setup tool (p. 20-27).
Required equipment
Alcatel-Lucent 1830 PSS WebUI
Instructions
...................................................................................................................................................................................................
In the WebUI, select System.

Result: The System Properties window is opened.
...................................................................................................................................................................................................
In the field OCS IP enter the OCS Partner IP address.
....................................................................................................................................................................................................................................
1830 PSS
4-4
Issue 1 June 2013
....................................................................................................................................................................................................................................
Example:
...................................................................................................................................................................................................
Click Submit.
...................................................................................................................................................................................................
Create Physical Topology on PSS32 (between PSS32 SFD/CWR port and OCS).
Additional information SFD ports which support OCS-type OCONNs are the
single-channel ports of SFD5x, SFD8x, SFD44, SFD44B, SFD40, SFD40B.

CWR ports which support OCS-type OCONNs are the CLS ports of CWR8,
CWR8-88.
...................................................................................................................................................................................................
For SFD40/40B/44/44B, click on the Create Shelf tab.

In the field Provisioned Type select the respective SFD shelf.
Click Submit.
For SFD5x, SFD8x or CWR, select the slot where the card will be equipped. In the field
Provisioned Type select the respective SFD/CWR card. Click Submit.
....................................................................................................................................................................................................................................
1830 PSS
4-5
Issue 1 June 2013
....................................................................................................................................................................................................................................
Example:
...................................................................................................................................................................................................
Select Connections Physical Topology from WebUI Menu Bar.
....................................................................................................................................................................................................................................
1830 PSS
4-6
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: The Physical Topology window is displayd.

Example:
...................................................................................................................................................................................................
Select the respective SFD/CWR port.

Click Inter Compound.
Enter the AID of the OCS Uplink card (e.g. PORT-1-1-35-1)
Click OK.
...................................................................................................................................................................................................
Using the Physical Topology window additional create a loopback connection for the
LD's DCM port and one between LD SIG and SFD OMD.
...................................................................................................................................................................................................
Create OCH connection between SFD/CWR port and LD Line port. (The OCS port can
not be used .)
Select Connections OCH Cross Connections from WebUI Menu Bar.
....................................................................................................................................................................................................................................
1830 PSS
4-7
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: The Create OCH Cross Connects window is displayed.

Example:
...................................................................................................................................................................................................
10
Enter A-End Port and Z-End Port.

...................................................................................................................................................................................................
11
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
4-8
Issue 1 June 2013
5quipment provisioning
E
procedures
Overview
Purpose
This chapter describes the procedures to be carried out for the provisioning of the
hardware components of an Alcatel-Lucent 1830 PSS network element (NE) by using the
Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) or WebUI.
Note:
The terms board, card, circuit pack or unit are used interchangeably throughout this
document.
Contents
5-5
5-6
Summary of important configuration rules
5-15
5-18
WDM equipment management specifics
5-19
5-43
Procedure 5-1: Define general properties of the system
5-44
5-46
Procedure 5-3: Remove an extension shelf
5-50
5-53
5-57
5-61
Procedure 5-7: Deprovision equipment
5-64
5-66
...................................................................................................................................................................................................................................
1830 PSS
5-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 5-9: Configure an optical interface port
5-70
Procedure 5-10: Configure Optical Channel parameters
5-72
5-74
5-76
Procedure 5-13: Configure an ODU path termination
5-84
5-89
5-92
Procedure 5-16: Deprovision an ODUk path termination function
5-95
5-97
5-99
5-101
Procedure 5-20: Remove a facility
5-107
5-109
5-111
Procedure 5-23: Inhibit equipment protection switching
5-113
Procedure 5-24: Initiate an equipment protection switch manually
5-115
Procedure 5-25: Initiate a circuit pack reset
5-117
5-123
Procedure 5-26: View or modify NE parameters
5-125
System Properties
5-126
Procedure 5-27: Reboot NE
5-129
Reboot Options
5-130
5-131
Firmware
5-134
5-135
Firmware
5-136
Shelf provisioning
5-137
Procedure 5-30: Create (pre-provision) a shelf
5-142
Create Shelf
5-143
5-146
Shelf Properties
5-147
Procedure 5-32: Delete a shelf
5-151
5-152
....................................................................................................................................................................................................................................
1830 PSS
5-2
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Shelf LEDs
5-153
5-154
Procedure 5-34: Create a card
5-175
Provision Card
5-176
Procedure 5-35: View / modify card properties
5-177
Procedure 5-36: View card inventory
5-178
Card Inventory
5-179
Procedure 5-37: View pluggable module inventory
5-180
5-181
5-182
Controller Protection Switch Settings
5-184
Procedure 5-39: Upgrade EC (in-service upgrade from simplex to duplex)
5-185
5-186
Reboot Options [Card]
5-187
Procedure 5-41: Delete a card
5-188
Delete Card
5-189
5-190
Procedure 5-42: Port provisioning procedures
5-402
5-446
Procedure 5-43: Retrieve general properties of the system
5-447
Procedure 5-44: Retrieve current conditions for a system component
5-448
View Current Conditions
5-449
5-451
5-453
5-456
Procedure 5-47: Retrieve information related to equipment protection groups
5-457
Procedure 5-48: Retrieve and edit optical channel parameters
5-459
5-460
Procedure 5-50: Perform LED test
5-462
5-463
5-465

General properties of the system as a whole
5-469
5-470
....................................................................................................................................................................................................................................
1830 PSS
5-3
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
General properties of a shelf
5-480
General properties of a TRU
5-482
General properties of an I/O card
5-483
General properties of an optical SDH/SONET port
5-484
5-489
5-497
General properties of a GBE / GBE10 port
5-501
General properties of an ODU path termination facilty
5-509
5-520
5-531
Parameters of equipment protection groups
5-539
Primary and secondary states of system components
5-541
5-548
TL1 parameters
5-579
....................................................................................................................................................................................................................................
1830 PSS
5-4
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section describes equipment provisioning principles for the OCS application of the
Alcatel-Lucent 1830 PSS network element (NE)
Contents
5-6
5-15
....................................................................................................................................................................................................................................
1830 PSS
5-5
Issue 1 June 2013

....................................................................................................................................................................................................................................

What does equipment provisioning mean?
Equipment provisioning means assigning configuration parameters to network element

components.
Equipment provisioning can take place for the first time after the installation of the
equipment (initial provisioning) or when a re-configuration of an Alcatel-Lucent
1830 PSS system in an existing network is necessary.
Equipment provisioning can be carried out using a management system, such as the
Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) or a network
management system (NMS) for example. The configuration data is stored in the
non-volatile memory (NVM) of the NE, the NE database. The NVM of the
Alcatel-Lucent 1830 PSS is realized by means of a mass storage device on the FLC.
Mandatory and non-mandatory equipment components
Alcatel-Lucent 1830 PSS equipment components can be classified as mandatory or

non-mandatory.
Mandatory equipment components
The following equipment components are automatically created (autoprovisioned) upon

the creation of the main shelf within an Alcatel-Lucent 1830 PSS system, whether the
equipment components are present or not:
Agnostic Matrix cards:

Matrix card A in slot 11 of the PSS-36 subrack, or slot 71 of the PSS-64 subrack
Matrix card B in slot 15 of the PSS-36 subrack, or slot 72 of the PSS-64 subrack
The following types of matrix cards exist:
MT960C or MT1T9C (Agnostic Matrix Card for the PSS-36 subrack, with a
switching capacity of up to 960 Gb/s or 1.9 Tb/s )
MT1T9 or MT3T8 (Agnostic Matrix Card for the PSS-64 subrack, with a
switching capacity of up to 1.9 Tb/s or 3.8 Tb/s)
First-level Controllers:
FLC_A (protected or protecting card) in slot 23 of the PSS-36 subrack, or slot 73
of the PSS-64 subrack
FLC_B (protected or protecting card) in slot 40 of the PSS-36 subrack, or slot 75

of the PSS-64 subrack
The following types of FLC cards exist:
ECHC (FLC) - FLC card for the PSS-64 subrack

FLC36EA - FLC card for the PSS-36 subrack
....................................................................................................................................................................................................................................
1830 PSS
5-6
Issue 1 June 2013

....................................................................................................................................................................................................................................
Bus Termination Cards:

BT3T8,
BTC3T8,
BT36
Power Supply Filter (PSF) units:
PSF unit (PSF3T8) in the slots 91 and 94 of the PSS-64 subrack
PSF unit (PFC) in the slots 44 and 45 of the PSS-36 subrack

Fan Unit (FAN3T8_A) in slot 92 and 93 of the PSS-64 subrack, or slot 41 of the
PSS-36 subrack
Equipment protection group for the First-level Controllers
Equipment protection group for the matrix cards.
Important! Mandatory equipment components cannot be deleted (deprovisioned).

Non-mandatory equipment components
The following equipment components are not mandatory:
I/O cards
Optical modules (SFP, XFP).
Non-mandatory equipment components support the following provisioning modes:
Autoprovisioning
Manual provisioning
Preprovisioning
Deprovisioning.
System-wide equipment provisioning mode
For non-mandatory equipment components, the equipment provisioning mode can be

configured on system level.
The following equipment provisioning modes are defined:
AUTOEQ
Equipment autoprovisioning is supported. Preprovisioning is also possible.
MANEQ
Equipment can only be manually provisioned. Preprovisioning is also

possible.
Note: The related facilities are always auto-created.
....................................................................................................................................................................................................................................
1830 PSS
5-7
Issue 1 June 2013

....................................................................................................................................................................................................................................
Types of equipment provisioning
These types of equipment provisioning can be distinguished:
Autoprovisioning
Provisioning
Preprovisioning
Deprovisioning
Reprovisioning.
These types of equipment provisioning will subsequently be described in more detail.

Autoprovisioning
Autoprovisioning means assigning default configuration parameters to an equipment

component at the time when it is physical plugged in first. The default configuration
parameters are read from the NE database.
Auto-provisioning is only performed, if the NE detects a configuration change by the
following triggers:
Plug-in of a card
Power on after a power-interruption.
Autoprovisioning enables to set up a network element with minimal user intervention.

A modification of the auto-provisioned parameters is possible by means of manual
provisioning (when the corresponding equipment is already physically present in the
system) or pre-provisioning (when the equipment is not yet physically present in the
system).
Provisioning
Provisioning, also referred to as manual provisioning, means setting configuration

parameters of network element components which are already physically present in the
system.
Preprovisioning
Preprovisioning means setting configuration parameters in advance, before the

corresponding equipment component is physically present in the system. The
preprovisioned configuration settings are stored in the NE database, and take effect as
soon as the respective equipment component is installed.
Note: Preprovisioning is also possible for extension shelfs.
Preprovisioning is possible for I/O card slots and optical module sockets (OM sockets).
Preprovisioning of an I/O card slot may include selecting a desired type of I/O card for
that slot from a list of permissible I/O cards. Preprovisioning of an OM socket may
include selecting a desired type of optical module for that OM socket from a list of
permissible optical module types.
....................................................................................................................................................................................................................................
1830 PSS
5-8
Issue 1 June 2013

....................................................................................................................................................................................................................................
Deprovisioning
Deprovisioning a slot or OM socket means cleaning up the NE database after a card or

optical module has been physically removed. It is not sufficient to only remove the card
or optical module because the provisioning information (configuration parameters stored
in the NE database) is not reset automatically (to the default settings).
Deprovisioning doesnt require physically removement.
Deprovisioning requires user interaction, and is possible for I/O card slots and optical
module sockets (OM sockets).
Deprovisioning of equipment components is only possible if previously its depending
entities, e.g. connections, protections or CP uses of the affected equipment have been
deprovisioned.
Reprovisioning (Exchangeability)
Reprovisioning is often also referred to as exchangeability. That means replacing an

already provisioned system component (referred to as the old system component in the
following) by another variant of the same or a different but compatible type (referred to as
the new system component in the following) without first having to deprovision the old
system component.
Important! Reprovisioning is only possible for pluggable optical modules
(SFPs/XFPs).
The principle proceeding to exchange different variants of optical modules, for example
SFPs/XFPs with different optical performance, is as follows:
Manually take the old optical module out of service by means of a management
command (ED-EQPT).
Remove the old optical module.
Insert a different (but compatible) SFP/XFP into the same OM socket.
Manually take the new optical module into service by means of a management
command (ED-EQPT).
Port groups and port group modes
The ports on the I/O cards are subdivided into so-called port groups which share a
common port group mode. This port group mode, in combination with the available types
of optical interface modules (SFPs/XFPs), determines the provisioning opportunities for
the ports. Ports in the same port group must be consistently provisioned.
For example, it is not possible to provision a port for a Gigabit Ethernet client signal
while a port in the same port group is already provisioned for an SDH or SONET client
signal.
The following port groups are defined:
....................................................................................................................................................................................................................................
1830 PSS
5-9
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-1
Port groups
I/O card
Number of port groups
Port groups
4XANY10G
Ports 1/2
Ports 3/4
10XANY10G
Ports 1/2
Ports 3/4
Ports 5/6
Ports 7/8
Ports 9/10
10XSTH10G
Ports 1/2
Ports 3/4
Ports 5/6
Ports 7/8
Ports 9/10
10XETH10G
Ports 1/2
Ports 3/4
Ports 5/6
Ports 7/8
Ports 9/10
10XOTH10G
Ports 1/2
Ports 3/4
Ports 5/6
Ports 7/8
Ports 9/10
24XANYMR
Ports 1-8
Ports 9-16
Ports 17-24
24XSTHMR
Ports 1-8
Ports 9-16
Ports 17-24
8XETH1G
Ports 1-8
24XETH1G
Ports 1-8
Ports 9-16
Ports 17-24
....................................................................................................................................................................................................................................
1830 PSS
5-10
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-1
Port groups
(continued)
I/O card
Number of port groups
Port groups
2XANY40G
Port 1
Port 2
43SCUP
Port 1
130SCUP
Port 1
The following port group modes and associated client selection modes are supported per
I/O card:
Table 5-2
Port group modes and client selection modes
I/O card
Port group mode
Client selectors
4XANY10G
OTH_OTH
OTU2 (OTU2 terminated)

OTU2E (OTU2e terminated)
ETHSTH_OTH
GBE10ODU2 (10 GbE mapped into ODU2)

GBE10ODU2E (10 GbE mapped into ODU2e)
In SDH mode: STM64T (STM-64 transparently
mapped into ODU2)
In SONET mode: OC192T (OC-192 transparently
mapped into ODU2)
10XSTH10G
PWRSV
Power-save mode: changing to any client selection

mode is possible.
STH_STH
STM64 (STM64 terminated)

OC192 (OC192 terminated)
10XANY10G
PWRSV

mode is possible.
OTH_OTH

ETHSTH_OTH

mapped into ODU2)
mapped into ODU2)
PWRSV

mode is possible.
....................................................................................................................................................................................................................................
1830 PSS
5-11
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-2
(continued)
I/O card
Port group mode
Client selectors
10XETH10G
ETHSTH_OTH

10XOTH10G
PWRSV

mode is possible.
OTH_OTH

ETHSTH_OTH

mapped into ODU2)
mapped into ODU2)
24XANYMR
PWRSV

mode is possible.
ETHSTH_OTH
GBEODU0 (1 GbE mapped into ODU0)
STH_OTHSTH
In SDH mode: STM-16T (STM-16 transparently

mapped into ODU1)
In SONET mode: OC-48T (OC-48 transparently
mapped into ODU1)
24XANYMRB
PWRSV

mode is possible.
ETHSTH_OTH
STH_OTHSTH
In SDH mode: STM-16T (STM-16 transparently

mapped into ODU1)
In SONET mode: OC-48T (OC-48 transparently
mapped into ODU1)
24XSTHMR
PWRSV

mode is possible.
STH_STH
STM16 (STM16 terminated)

OC48 (OC48 terminated)
8XETH1G
8XETH1GB
PWRSV

mode is possible.
ETHSTH_OTH
PWRSV

mode is possible.
ETHSTH_OTH
PWRSV

mode is possible.
....................................................................................................................................................................................................................................
1830 PSS
5-12
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-2
(continued)
I/O card
Port group mode
Client selectors
24XETH1G
ETHSTH_OTH
PWRSV

mode is possible.
ETHSTH_OTH
PWRSV

mode is possible.
OTH_OTH
PWRSV

mode is possible.
OTH_OTH
OTU3E2 (OTU3E2 terminated)
PWRSV

mode is possible.
OTH_OTH
PWRSV

mode is possible.
24XETH1GB
2XANY40G
43SCUP
130SCUP
The following optical interface modules (SFPs/XFPs) are supported, depending on the
respective client selection mode:
Table 5-3
Client selection mode
Compatible interface modules
GBEODU0
IR12G7AU, 1000BSXU, 1000BLXU, 1000BZXU, USER
GBE10ODU2
SR111G1AU, IR211G1AU, LR211G1AU, USER
GBE10ODU2E
STM1T
SR10G155TU, SL10G155TU, SL20G155TU , USER
STM4T
SR10G622TU, SL10G622TU, SL20G622TU, USER
STM16T
SR12G7TU, IR12G7TU, LR12G7TU, LR22G7TU, IR12G7AU, USER
STM64T
STM16
IR12G7AU, SR12G7TU, IR12G7TU, LR12G7TU, LR22G7TU, USER
STM64
OC48
IR12G7AU, SR12G7TU, IR12G7TU, LR12G7TU, LR22G7TU, USER
OC192
OC3T
OC12T
OC48T
....................................................................................................................................................................................................................................
1830 PSS
5-13
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-3

(continued)
Client selection mode
Compatible interface modules
OC192T
OTU2
SR111G1AU, IR211G1AU, LR211G1AU, LRT11G1TU, LRZCT11G1TUC,

SR<xx> W11G1TUC, SR<xx>W11G1TUI, LR< xx>W11G1TUC,
LR<xx>W11G1TUI, LR<xx>DW11G1TUI,USER
OTU2E
SR111G1AU, IR211G1AU, LR211G1AU, LRT11G1TU, LRZCT11G1TUC,

SR<xx> W11G1TUC, SR<xx>W11G1TUI, LR< xx>W11G1TUC,
LRxx>W11G1TUI, LRxx>DW11G1TUI, USER
Notes:
1.
The 2 40G ANY Port Unit (2XANY40G), , 43SCUP and 130SCUp do not support optical interface
modules (SFPs/XFPs) but have fixed ports.
2.
<xx>: the two middle digits are placeholders for the actual wavelength, e.g. <xx>=53 for a
wavelength=1531nm
....................................................................................................................................................................................................................................
1830 PSS
5-14
Issue 1 June 2013

....................................................................................................................................................................................................................................

Configuration rules and guidelines
Note: Take all the rules and guidelines in the following list into consideration as the
ordering in the list does not necessarily reflect the order of importance.
Observe the following general rules and guidelines with regard to the subrack
configuration:
1. Never operate an Alcatel-Lucent 1830 PSS system without a fan unit for more
than two (2) minutes to avoid overheating of the system.
Leaving the fan unit out of operation for more than two minutes may cause the
respective network element to fail.
2. Cover unequipped I/O card slots and OM sockets with blank front plates or OM
socket covers to guarantee proper cooling, airflow and EMC behavior. Do not
leave unequipped slots uncovered for more than five (5) minutes to avoid
overheating of the system. Disregarding this warning could cause the system to
fail and voids warranty. Blank front plates are available as orderable items (see
Alcatel-Lucent 1830 PSS Product Information and Planning Guide). Parent
boards for optical modules are shipped with the OM sockets covered.
The cooling of the Alcatel-Lucent 1830 PSS system relies on sufficient airflow.
Uncovered slots or OM sockets prevent an adequate cooling because
Alcatel-Lucent 1830 PSS systems make use of the stack effect.
3. Before plugging the first pluggable optic into a slot configure the port group.
Otherwise when plugging an SFP/XFP a default port group would be
automatically configured to indicate that a SFP/XFP has been plugged. (see Port
groups and port group modes (p. 5-9))
4. In principle provisioning of the 43SCUP IO-Card is restricted to the lower full I/O
slots in the PSS-64 shelf by temperature restrictions for these IO-Cards. But as up
to 15 43SCUPs are allowed under special circumstances provisioning of 43SCUPs
in the upper rows is allowed.
The inlet temperature to the shelf is not allowed to exceed 40 C. To control which
ambient temperature range is allowed for the PSS-64 shelf you have to explicitly
commit the environmental condition. This is done by a system-wide configuration
parameter.
Environmental Conditions Restricted (ENVCONDRSTR)
Y YES
normal temperature range; relevant for PSS64 shelves within the system;
certain equipment allowed in the upper row
N NO
....................................................................................................................................................................................................................................
1830 PSS
5-15
Issue 1 June 2013

....................................................................................................................................................................................................................................
exceptional temperature range; relevant for PSS64 shelves within the system;
certain equipment not allowed in the upper row
5. In principle provisioning of the 130SCUP IO-Cards is restricted to the lower full
I/O slots in the PSS-64 shelf by temperature restrictions for these IO-Cards. Under
special circumstances provisioning of 130SCUPs in the upper rows is allowed.
parameter.
Y YES
N NO
6. In principle provisioning of the 11QCUPC IO-Cards is restricted to the lower full

I/O slots in the PSS-64 shelf by temperature restrictions for these IO-Cards. Under
special circumstances provisioning of 11QCUPC in the upper rows is allowed.
parameter.
Y YES
N NO
7. Due to temperature restrictions the follwowing XFPs are restricted on the lower
Full I/O slots of the PSS-64 Shelf:
tunable XFPs for WDM (LRT11G1TU)
CWDM XFP SR<xx>W11G1TUC
(<xx>={47,49,51,53,55,57,59,61} ; maps to RI MNEMONIC:
X11MC<xx>SC)
CWDM XFP LR<xx>W11G1TUC
....................................................................................................................................................................................................................................
1830 PSS
5-16
Issue 1 June 2013

....................................................................................................................................................................................................................................
(<xx>={47,49,51,53,55,57,59,61} ; maps to RI MNEMONIC:

X11MC<xx>LC)
8. Colored, fixed XFPs are autoprovisioned, too.
....................................................................................................................................................................................................................................
1830 PSS
5-17
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section describes equipment provisioning principles for the WDM application of the
Alcatel-Lucent 1830 PSS network element (NE)
Contents
5-19
....................................................................................................................................................................................................................................
1830 PSS
5-18
Issue 1 June 2013

....................................................................................................................................................................................................................................

Equipment discovery
Detection of physical insertion and removal (via backplane equipage leads) is supported
for the following circuit packs which reside in 1830 PSS-32/PSS-16/PSS-32S shelf slots.
EC
MTC1T9
USRPNL
PF
FAN
HKPCNTL
A2325A/A2P2125/AHPHG/AHPLG/ALPHG/AM2125A/AM2125B/AM2318A
CWR8 & CWR8-88

OT
OPSA
OPSB
OSCT
PTPCTL
PTPIO
SFC
SFD
SVAC
MESH4
MVAC
RA2P
WR2-88
WR8-88A
WR8-88AF
WTOCM
WTOCMA
pluggable SFP/XFP modules
I/O cards
Uplink cards
....................................................................................................................................................................................................................................
1830 PSS
5-19
Issue 1 June 2013

....................................................................................................................................................................................................................................
Indirect detection of presence/absence (inferred by readability of electronic inventory

link) is supported for the following modules (when they are provisioned as managed).
These do not reside in PSS shelf slots.
DCM
ITLB
ITLU
SFD40
SFD40B
SFD44
SFD44B
Note: To allow a customer to use these modules beyond the range of the electronic
inventory link, these modules can be also provisioned as unmanaged, indicating that
they are to be treated by the system as present without reading the electronic
inventory link.
Insertion or extraction of a module does not cause equipment faults to occur on other
equipment entities, except extraction of the FAN module may eventually cause equipment
temperature faults. However, extraction of a module may cause facility signal faults on
other modules.
Note: For PSS-32, once the fan is extracted, two minutes is the maximum
recommended time interval for fan replacement (one minute for PSS-16). Replacing
the fan unit may necessitate a database restore.
Cascaded OTs
1830 PSS supports cascaded OTs. For this configuration, a signal is added at an OT client
port and multiplexed onto the higher bandwidth line port. The signal is then added at a
second higher-rate OT, and multiplexed to its line port. The reverse path is taken when the
signal is dropped.
Note: There may be multiple "OT B"s connected to "OT A", and each "OT B" need
not be the same card type.
The following cards support symmetric configurations, where the OTs are cascaded on
both the A-end and Z-end of a service:
11STMM10 OTU1 client port (OT A) connected to a 4DPA4 line port (OT B). Up to
four 4DPA4 OTs may be connected to one 11STMM10.
11DPM12 OTU1 client port (OT A) connected to a 4DPA4 line port (OT B). Up to
four 4DPA4 OTs may be connected to one 11DPM12.
11QPEN4 OTU2 client port (OT A) connected to an 11DPE12 line port (OT B). Up to
four 11DPE12 OTs may be connected to one 11QPEN4. This configuration provides
encrypted transmission for GbE services.
....................................................................................................................................................................................................................................
1830 PSS
5-20
Issue 1 June 2013

....................................................................................................................................................................................................................................
11QPEN4 OTU2 client port (OT A) connected to an 11DPE12A line port (OT B). Up
to four 11DPE12A OTs may be connected to one 11QPEN4. This configuration
provides encrypted transmission for GbE services.
11QPEN4 OTU2 client port (OT A) connected to an 11DPE12E line port (OT B). Up
to four 11DPE12E OTs may be connected to one 11QPEN4. This configuration
provides encrypted transmission for GbE services.
11QPEN4 OTU2 client port (OT A) connected to an 11DPM12 line port (OT B). Up
to four 11DPM12 OTs may be connected to one 11QPEN4. This configuration
provides encrypted transmission for GbE and FC100/FC200/FC400 services.
43SCX4 OTU2 client port (OT A) connected to an 11DPM12 line port (OT B). Up to
four 11DPM12 OTs may be connected to one 43SCX4.
43SCX4E OTU2 client port (OT A) connected to an 11DPM12 line port (OT B). Up
to four 11DPM12 OTs may be connected to one 43SCX4E.
43STX4P OTU2 client port (OT A) connected to an 11DPM12 line port (OT B). Up
to four 11DPM12 OTs may be connected to one 43STX4P.
112SCX10 OTU2 client port (OT A) connected to an 11DPM12 line port (OT B). Up
to ten 11DPM12 OTs may be connected to one 112SCX10.
112SNX10 OTU2 client port (OT A) connected to an 11DPM12 line port (OT B). Up
to ten 11DPM12 OTs may be connected to one 112SNX10.
112SNX10 OTU2 client port (OT A) connected to an 11QPEN4 line port (OT B). Up
to 10 11QPEN4 cards may be connected to one 112SNX10. Not supported with
11QPEN4 FC1200 client.
130SCX10 OTU2 client port (OT A) connected to an 11DPM12 line port (OT B). Up
to ten 11DPM12 OTs may be connected to one 130SCX10.
130SCX10 OTU2 client port (OT A) connected to an 11QPEN4 line port (OT B). Up
to 10 11QPEN4 cards may be connected to one 130SCX10. Not supported with
11QPEN4 FC1200 client.
The cascaded OT configuration is supported as follows:
An internal topological link is provisioned between the OT A client port and the OT B
line port.
The cross-connect terminates on the OT A line port. OT B is not included in a

cross-connect.
There is no wave key encoding on OT B so the eVOA port is not used.
There is no alarm correlation between OT A and OT B.
....................................................................................................................................................................................................................................
1830 PSS
5-21
Issue 1 June 2013

....................................................................................................................................................................................................................................
Manual restarts (reboot)
It is possible to reset a specified equipment entity or the entire NE. Different possible
levels of restart are:
Warm restart (a.k.a. soft reset and software reboot): Previous hardware state is
retained, and transmission is not affected.
Cold restart (a.k.a. hard reset, power cycle, and power-up): Hardware state is
completely reinitialized from scratch without reference to the previous state.
Transmission may be affected.
Note: Cold restart of a transmission-carrying pack kills traffic, and thus cold restart is
not allowed on an in-service pack. The pack must either be in maintenance state or
out-of-service as described below:
1. Put the pack (and ports) into maintenance state before performing the cold restart.
In maintenance state the cross connects can remain in place, and transmission is
still carried.
2. Perform a cold restart of the entire NE, instead of pack-by-pack. The TL1
command "INIT-SYS" allows this without individually changing all pack/port
admin states in the system -- if the user specifies the "forced" option. The CLI
command "config admin resetne" offers an equivalent to this "forced" option.
Note: After a cold restart of an 11QPEN4 in ESNCP configuration, Encryption
Current Key Mismatch may occur. The user must then provision new keys on both
nodes and switch to them, or use the Key Management Tool (KMT) to do the same
action. Once the switch occurs, communication is restored.
Manual restart can be applied individually to any of the following circuit pack types: EC,
LD, OSCT, CWR, OT, OPS, SVAC, MVAC, WR, MESH, WTOCM (see Instructions
(p. 5-186)). Manual restart of the entire NE performs restart of all of these circuit pack
types (see Instructions (p. 5-129)).
Note: The following recommended procedures will avoid causing the wavelength
power directed towards the Line Out direction (egress of the node) from spiking when
the SVAC/MVAC is unpowered or cold reset.
The physical fiber patch cord to the C1 input of the SVAC/MVAC should be
disconnected prior to issuing a cold reset of the pack, and prior to removal of the
pack from the shelf.
The physical fiber patch cord to the C1 input of ALL the SVAC/MVAC packs
should be disconnected in a shelf that is to be cold reset.
should be disconnected prior to powering off the shelf containing the packs for an
extended period of time.
should be disconnected prior to power cycling or powering on the shelf containing
the packs.
....................................................................................................................................................................................................................................
1830 PSS
5-22
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: USRPNL, FAN, PF, SFC, SFD, ITLB, ITLU, and DCM have no processors and
cannot be restarted.
Mandatory equipment
Each shelf contains mandatory modules with which it must be equipped. Some of the
shelves can also be equipped with optional modules.
1830 PSS-32 and 1830 PSS-16
Mandatory equipment must be automatically provisioned whether present or not. Each

shelf includes the following mandatory equipment.
One shelf controller (EC) in either slot 1 or slot 18 (for PSS-32) or slot 2 or 12 (for
PSS-16)
Two power modules (PF)
A fan module (FAN)
User interface panel (USRPNL) mandatory on the main shelf only, and not allowed
on other shelves
Mandatory equipment is provisioned without AINS state (AINS = Automatic In Service,

which allows newly provisioned entities to be inserted at the later time without generating
alarms). See Automatic in-service (AINS) (p. 5-42). Therefore, if mandatory equipment
is not present it will be alarmed (assuming its absence is detected).
Note: Automatic provisioning of mandatory equipment differs from the
"auto-provisioning" defined for non-mandatory equipment. Mandatory equipment is
provisioned regardless of module presence detection. Non-mandatory equipment is
auto-provisioned only upon equipment detection and validation.
1830 PSS-32S
Mandatory equipment must be automatically provisioned whether present or not. Each

shelf includes the following mandatory equipment.
Two matrix/control cards (MTC1T9)

Two power modules (PF)
A fan module (FAN)

Two bus termination modules (BTC)
A housekeeping control card (HKPCNTL)
Equipment Controller (EC)
EC types are defined as follows:
Active EC - This EC is responsible for all run time EC operations in the system.
Standby EC - This EC is responsible for monitoring the operation of the Active EC,
access to all shared resources and for updating its own persistent storage.
....................................................................................................................................................................................................................................
1830 PSS
5-23
Issue 1 June 2013

....................................................................................................................................................................................................................................
Master EC - Any EC that is in a shelf with a shelf ID of one (see Shelf provisioning
(p. 5-137)). This shelf is defined as the Master shelf for the system.
Subtending EC - Any EC that is in a shelf with a shelf ID greater than one (see Shelf
provisioning (p. 5-137)). A shelf with a shelf ID greater than one is defined as a
subtending shelf.
Each shelf contains one Active EC. A standby EC is present if the shelf is redundant. If
the shelf ID is one, that shelf is designated as the Master shelf. The Active and Standby
ECs in the Master shelf are designated as Master ECs. There is always one and only one
Master shelf per node. This shelf will always contain an Active Master EC and
connectivity to the USRPNL. If the node has only one shelf, the Active Master EC
performs the functionality of both the Master and the Subtending EC. If the node consists
of multiple shelves, the Master shelf contains the Master EC and all subsequent shelves
contain Subtending ECs.
Note: The circuit pack hardware is identical for both the Master and Subtending EC.
Only the behavior of the pack changes based on the slot position and the shelf ID.
Note: For 1830 multi-shelf configuration, if one shelf is redundant, all shelves should
be redundant.
Note: Admin State for Ethernet ports cannot be independent. If a switch over from
active with Ethernet port Admin state enabled to standbywith Ethernet port Admin
state disabled, a loss of communication will occur. The admin state of Ethernet ports
must match.
Important! One and only one shelf in each NE can have the role of Main Shelf. This
is designated by a backplane rotary dial setting of 0x81 (Shelf Role = Main Shelf,
Shelf ID = 1). When a new Universal shelf boots up and finds that its rotary dial is set
to 0x81, it automatically provisions itself with AID = SHELF-1. It automatically
provisions its shelf type according to its actual hardware: TL1 TYPEID =
UNV_SHELF_16 (if PSS-16), or UNV_SHELF (if PSS-32). It then begins to perform
the role of the main shelf. For details on how to change the rotary dial, see Rotary
dial backplane setting (p. 5-137).
The Master EC performs the following functions:
An EC behaves as a Master EC (either standby or active) if it detects that the shelf ID

is one.
The Active Master EC provides the external LAN interface for management of all
shelves in a multi-shelf node.
The Active Master EC terminates and or generates all communications with the
management system. This includes communications intended for the Subtending
shelves. It forwards information intended for a Subtending shelf to the proper EC.
The Active Master EC is responsible for maintenance of its persistent database and
configures all shelves and packs in the node using data in the persistent database.
....................................................................................................................................................................................................................................
1830 PSS
5-24
Issue 1 June 2013

....................................................................................................................................................................................................................................
The Active Master EC is responsible for maintaining the power state of all cards in
the same shelf and is responsible for monitoring voltage from the power filters in the
same shelf.
The Active Master EC monitors the health of all packs in the same shelf and monitors
the health of all shelves in the node.
The Standby Master EC is responsible for monitoring the operation of the Active EC,
access to all shared resources and for updating its own persistent storage.
Note: To replace the Active Master EC, it is necessary to switch the Active so it
becomes the Standby EC, and therefore can be replaced without disrupting the
system.
The Subtending EC is responsible for the following functions:
Any EC behaves as a Subtending EC (either standby or active) if it detects that the

shelf ID is any number greater than 1.
The Active Subtending EC is responsible for maintaining the power state of all cards
in the same shelf and is responsible for monitoring the voltage output from the power
filters in the same shelf.
The Active Subtending EC monitors the health of all packs in the same shelf and
forwards fault, and performance information to the Active Master EC
The Active Subtending EC monitors all services performed by a shelf and forwards
fault, and performance information to the Active Master EC
The Active Subtending EC coordinates all communication within a shelf and
communication to the Master shelf.
The Active Subtending EC stores card application images in its local mass storage and
provides the application images from its mass storage unit to the cards in the same
shelf at boot time, if a card is reset or on request from the Master EC.
The Standby Subtending EC is responsible for monitoring the operation of the Active
EC, access to all shared resources, and for updating its own persistent storage.
Matrix/Controller card (MTC1T9)
The Matrix/Controller card (MTC1T9) is designed for use with Alcatel-Lucent 1830
PSS-32S shelves. It combines the control functions of first-level and second-level
controller cards used in Alcatel-Lucent 1830 PSS-36 and Alcatel-Lucent 1830 PSS-64
shelves. It also has a 1.9 Tb/s agnostic switch matrix switch, capable of switching 1.92
Tb/s of ODU traffic. Packet traffic is transparently mapped into ODU along with
SDH/SONET. Two Matrix/Controller cards are required on each Alcatel-Lucent 1830
PSS-32S shelf.
On the Matrix/Controller card, five groups of functionalities are implemented:
First-level controller (FLC)

Second-level controller (SLC)
Clock reference unit (CRU)
....................................................................................................................................................................................................................................
1830 PSS
5-25
Issue 1 June 2013

....................................................................................................................................................................................................................................
Switch fabric matrix

LAN switch
The function of the First-level controller (FLC) is to provide:
Hardware resources and software functions required for communication between the
NE and the managing system. This functionality encompasses the implementation of
external LAN interfaces and ECC interfaces as well as the implementation of the
communication stacks needed to communicate with different Alcatel-Lucent 1830
PSS neighbor NEs.
Debug LAN access for service personnel, can be enabled or disabled by the operator
Management interfaces for management communication networks (MCN) and
signaling communication networks (SCN), for example TL1.
Management agents including event reporting and logging, equipment database
management, SW downloading and management, performance monitoring
management, alarm management, security management.
USB interface for software installation
Management of the network element database, resident on a mass storage (for
example, SSD).
The function of the Second-level controller (SLC) is control and management of the part
concerning SDH/SONET, OTN, and packet functionality. The control infrastructure is
managed by a controller module. Extension shelves can be controlled from the SLC
through the LAN switch.
The Clock reference unit (CRU) provides reference to clock and timing frame
synchronization used in all SDH/SONET units and for external timing.
The Switch fabric matrix accomplishes ODU and packet switching functions (central
scheduler). The alarm and performance monitoring overhead processing and protection
management functionality as well as packet functionality (central scheduler) is managed
by dedicated devices. SNC protection for ODU is also supported by the switch fabric
matrix.
The LAN switch performs the management of the internal and external local area network
(LAN) to be used for communication among microprocessor and/or for propagation of
control packets extracted from the data path. Extension shelves can be connected to the
matrix card unit through LAN cable
MTC1T9 cards have to be installed redundantly for transmission and control reliability
reasons. One MTC1T9 card will be active. The inactive MTC1T9 card enters a standby
state which implies that it can take over the active role once the former active card has
given up its role. Both cards operate in a hot-standby relationship (they operate the same
code due to same triggers), and data is synchronized
....................................................................................................................................................................................................................................
1830 PSS
5-26
Issue 1 June 2013

....................................................................................................................................................................................................................................
Power Filter (PF) modules
Each Power Filter module is capable of sustaining the entire load of the system so that its
partner can be replaced upon failure without disrupting transmission. Each shelf has its
own power connections and is powered independently from the other shelves in the NE.
The shelf power and ground connectors are located at the front of the shelf coming into
the PF cards at the lower left and lower right of the shelf.
FAN modules
The shelf is cooled by four variable-speed fans. The fans are housed in a replaceable FAN
tray. The FAN tray contains the variable-speed fans and a controller, which communicates
with the active control card to control the FAN speed.
1830 PSS-32/PSS-16/PSS-32S supports the ability to control fan speed via the WebUI.
When the Fan module is selected in the WebUI equipment tree, the fan speed can be set to
the following values:
normal - automatic speed control
maximum - constant full speed (100% RPMs)
Non-mandatory equipment
For non-mandatory equipment, the following provisioning modes are defined:
Auto-provisioning, also referred to as Plug & Play, where the EC provisions a card
upon discovering it.
Pre-provisioning, where the slot is provisioned in advance of a card being inserted.
Alcatel-Lucent 1830 PSS-32 universal slot(s) provisioning and validation
The supported packs and slot locations for a Alcatel-Lucent 1830 PSS-32 shelf are shown
in Table 5-4, Alcatel-Lucent 1830 PSS-32 Circuit Pack Slot Allocation (p. 5-27)
Table 5-4
Card
Alcatel-Lucent 1830 PSS-32 Circuit Pack Slot Allocation

Description
Slot Location
Height / Number
of Slots
112PDM11
112G DCI High

Capacity Mux
Transponder (10
clients)
2-17
Full/1
112SCA1
112G Single Port

Tunable Coherent
AnyRate Transponder
(1 client)
2-15
Full/3
....................................................................................................................................................................................................................................
1830 PSS
5-27
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-4
Card

Description
Slot Location
(continued)
Height / Number
of Slots
112SCX10
112G Single Port

Tunable Coherent
Mux Transponder (10
clients)
2-15
Full/3
112SNA1
112G Single Port

Tunable Coherent
AnyRate
Transponder,
w/Enhanced OSNR (1
client)
2-15
Full/3
112SNX10
112G Single Port

Tunable Coherent
Mux Transponder,
w/Enhanced OSNR
(10 clients)
2-15
Full/3
11DPE12
11G Dual Port

Pluggable GBE MUX
Transponder (12
clients)
2-17
Full/1
11DPE12A
11G Dual Port

Pluggable GBE Mux
Transponder, cost
enhanced (12 clients)
2-17
Full/1
11DPE12E
11G Dual Port

Pluggable GBE Mux
Transponder,
Enhanced (12 clients)
2-17
Full/1
11DPM12
11G Dual Port

Pluggable Multirate
ADM Transponder
(12 clients)
2-17
Full/1
11QPA4
11G Quad Port

Pluggable AnyRate
Transponder (4
clients)
2-17
Full/1
....................................................................................................................................................................................................................................
1830 PSS
5-28
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-4
Card

Description
Slot Location
(continued)
Height / Number
of Slots
11QPE24
11G Quad Port

Pluggable GBE Mux
Transponder (24
clients)
2-16
Full/2
11QPEN4
11G Quad Port

Pluggable AnyRate
Transponder with
encryption (4 clients)
2-17
Full/1
11STAR1
11G Single Port

Tunable AnyRate
Transponder (1 client)
2-17, 20-35
Half/1
11STAR1A
11G Single Port

Tunable AnyRate
Transponder, cost
enhanced (1 client)
2-17, 20-35
Half/1
11STGE12
11G Single Port

Tunable GBE MUX
Transponder (12
clients)
2-17
Full/1
11STMM10
11G Single Port

Tunable Multi-rate
MUX Transponder
(10 universal clients)
2-17
Full/1
130SCX10
130G Single Port

Tunable Coherent
Mux Transponder
with SDFEC (10
clients)
2-16
Full/2
43SCA1
43G Single Port

Tunable Coherent
AnyRate Transponder
(1 client)
2-15
Full/3
43SCGE1
43G Single Port

Tunable Coherent
GBE Transponder (1
client)
2-15
Full/3
....................................................................................................................................................................................................................................
1830 PSS
5-29
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-4
Card

Description
Slot Location
(continued)
Height / Number
of Slots
43SCX4
43G Single Port

Tunable Coherent
Mux Transponder (4
clients)
2-15
Full/3
43SCX4E
43G Single Port

Tunable Coherent
Mux Transponder,
cost enhanced (4
clients)
2-16
Full/2
43STA1P
43G Single Port

Tunable AnyRate (1
client)
2-15
Full/3
43STX4
43G Single Port

Tunable MUX (4
clients)
2-15
Full/3
43STX4P
43G Single Port

Tunable MUX with
P-DPSK (4 clients)
2-15
Full/3
4DPA2
4G Dual Port
Pluggable AnyRate
Transponder (2
clients)
2-17, 20-35
Half/1
4DPA4
4G Dual Port
Pluggable AnyRate
Transponder (4
clients)
2-17, 20-35
Half/1
A2325A
+23 dBm output

power, 25 dB gain
optical amplifier with
mid-stage access
2-17
Full/1
A2P2125
+21 dBm output

power, 25 dB gain
hybrid Raman +
EDFA amplifier
2-16
Full/2
....................................................................................................................................................................................................................................
1830 PSS
5-30
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-4
Card
Description
Slot Location
(continued)
Height / Number
of Slots
AHPHG/AHPLG
AHPHG (High Power

High Gain Line
Driver) or AHPLG
(High Power Low
Gain Line Driver)
2-17
Full/1
ALPHG
Low power (+17

dBm), high gain
mid-stage access
2-17
Full/1
AM2125A
+21 dBm output

power, 25 dB gain
mid-stage access
2-17
Full/1
AM2125B
+21 dBm output

power, 25 dB gain
no mid-stage access
2-17
Full/1
AM2318A
+23 dBm output

power, 18 dB gain
no mid-stage access
2-17
Full/1
CWR8
Colorless Wavelength
Router 44-channel
2-16
Full/2
CWR8-88
Colorless Wavelength
Router 88-channel
2-16
Full/2
EC
Equipment Controller
1,18
Half/1
FAN
FAN
37
Full/1
MESH4
1x4 Splitter card with

optical amplifier
2-17
Full/1
MVAC
Multiple port Variable

Attenuator Card
2-17, 20-35
Half/1
MVAC8B
Bidirectional Multiple
port Variable
Attenuator Card
2-17
Full/1
OPSA
Optical Protection
Switch card
2-17, 20-35
Half/1
....................................................................................................................................................................................................................................
1830 PSS
5-31
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-4
Card

Description
Slot Location
(continued)
Height / Number
of Slots
OPSB
Optical Protection
Switch card with
non-latching switch
2-17, 20-35
Half/1
OSCT
OSC card with Total

power monitoring
2-17, 20-35
Half/1
PF
Power Filter
19,36
Half/1
PTPCTL
PTP Controller Card
2-17, 20-35
Half/1
PTPIO
PTP I/O Card
2-17, 20-35
Half/1
RA2P
Raman Amplifier, 2
pumps
2-17
Full/1
SFC2
2 channel static
CWDM filter
2-17, 20-35
Half/1
SFC4
4 channel static
CWDM filter
2-17, 20-35
Half/1
SFC8
8 channel static
CWDM filter
2-17
Full/1
SFD5
5 channel static
DWDM filter
2-17, 20-35
Half/1
SFD8
8 channel static
DWDM filter
2-17
Full/1
SVAC
Single port VOA card
2-17, 20-35
Half/1
USRPNL
User Interface Panel
40 (main shelf only)
Full/1
WR2-88
1x2 Optimized
Wavelength Router,
88 channel
2-16, 20-34
Half/2
WR8-88A
Wavelength Router
88-channel
2-16
Full/2
WR8-88AF
Wavelength Router,
88 channel with
FlexGrid
2-16
Full/2
WTOCM
Wavelength Tracker
Optical Channel
Monitoring card
2-17, 20-35
Half/1
....................................................................................................................................................................................................................................
1830 PSS
5-32
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-4
Card
WTOCMA

Description
Wavelength Tracker
Optical Channel
Monitoring card
enhanced
Slot Location
2-17, 20-35
(continued)
Height / Number
of Slots
Half/1
Alcatel-Lucent 1830 PSS-32S universal slot(s) provisioning and validation
The supported packs and slot locations for a Alcatel-Lucent 1830 PSS-32S shelf are
shown in Table 5-5, Alcatel-Lucent 1830 PSS-32S Circuit Pack Slot Allocation
(p. 5-33)
Table 5-5
Card
Alcatel-Lucent 1830 PSS-32S Circuit Pack Slot Allocation

Description
Slot Location
Height / Number
of Slots
10AN10G
10G AnyRate OTN

Client/Line card (10
ports)
2-9, 12-19
Full/1
11QCUPC
11G Quad Port

Pluggable Coherent
Uplink card
2-9, 12-19
Full/1
130SCUP
130G Single Port

Tunable Coherent
Uplink card
2-8, 12-18
Full/2
24ANM
AnyRate OTN Client

card (24 ports)
2-9, 12-19
Full/1
24ET1GB
1G Ethernet OTN
Client card (24 ports)
2-9, 12-19
Full/1
BTC
Bus Termination Card
42, 43
Half/1
HKPCNTL
Housekeeping/
Control card
45
Half/1
FAN
FAN
40
Full/1
MTC1T9
PSS-32S Matrix and

Controller card
10, 11
Full/2
PF
Power Filter
37, 39
Half/1
....................................................................................................................................................................................................................................
1830 PSS
5-33
Issue 1 June 2013

....................................................................................................................................................................................................................................
Alcatel-Lucent 1830 PSS-16 universal slot(s) provisioning and validation
The supported packs and slot locations for a Alcatel-Lucent 1830 PSS-16 shelf are shown
in Table 5-6, Alcatel-Lucent 1830 PSS-16 Circuit Pack Slot Allocation (p. 5-34)
Table 5-6
Card

Description
Slot Location
Height / Number
of Slots
112PDM11
112G DCI High

Capacity Mux
Transponder (10
clients)
7-9 (main and

non-main)
Full/1
11DPE12
11G Dual Port

Pluggable GBE MUX
Transponder (12
clients)
3-9 (main) 3-10

(non-main)
Full/1
11DPE12A
11G Dual Port

Pluggable GBE Mux
Transponder, cost
enhanced (12 clients)
3-9 (main) 3-10

(non-main)
Full/1
11DPE12E
11G Dual Port

Pluggable GBE Mux
Transponder,
Enhanced (12 clients)
3-9 (main) 3-10

(non-main)
Full/1
11DPM12
11G Dual Port

Pluggable Multirate
ADM Transponder
(12 clients)
3-9 (main) 3-10

(non-main)
Full/1
11QPA4
11G Quad Port

Pluggable AnyRate
Transponder (4
clients)
3-9 (main) 3-10

(non-main)
Full/1
11QPE24
11G Quad Port

Pluggable GBE Mux
Transponder (24
clients)
3-8 (main) 3-9

(non-main)
Full/2
11QPEN4
11G Quad Port

Pluggable AnyRate
Transponder with
encryption (4 clients)
7-9 (main) 7-9

(non-main)
Full/1
....................................................................................................................................................................................................................................
1830 PSS
5-34
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-6
Card
Description
Slot Location
(continued)
Height / Number
of Slots
11STAR1
11G Single Port

Tunable AnyRate
Transponder (1 client)
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
11STAR1A
11G Single Port

Tunable AnyRate
Transponder, cost
enhanced (1 client)
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
11STGE12
11G Single Port

Tunable GBE MUX
Transponder (12
clients)
3-9 (main) 3-10

(non-main)
Full/1
11STMM10
11G Single Port

Tunable Multi-rate
MUX Transponder
(10 universal clients)
3-9 (main) 3-10

(non-main)
Full/1
4DPA2
4G Dual Port
Pluggable AnyRate
Transponder (2
clients)
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
4DPA4
4G Dual Port
Pluggable AnyRate
Transponder (4
clients)
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
A2325A
+23 dBm output

power, 25 dB gain
mid-stage access
3-9 (main) 3-10

(non-main)
Full/1
A2P2125
+21 dBm output

power, 25 dB gain
hybrid Raman +
EDFA amplifier
6-8 (main) 6-8

(non-main)
Full/2
AHPHG/AHPLG
AHPHG (High Power

High Gain Line
Driver) or AHPLG
(High Power Low
Gain Line Driver)
3-9 (main) 3-10

(non-main)
Full/1
....................................................................................................................................................................................................................................
1830 PSS
5-35
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-6
Card

Description
Slot Location
(continued)
Height / Number
of Slots
ALPHG
Low power (+17

dBm), high gain
mid-stage access
3-9 (main) 3-10

(non-main)
Full/1
AM2125A
+21 dBm output

power, 25 dB gain
mid-stage access
3-9 (main) 3-10

(non-main)
Full/1
AM2125B
+21 dBm output

power, 25 dB gain
no mid-stage access
3-9 (main) 3-10

(non-main)
Full/1
AM2318A
+23 dBm output

power, 18 dB gain
no mid-stage access
3-9 (main) 3-10

(non-main)
Full/1
EC
2,12
Half/1
FAN
FAN
21
Full/1
MESH4
1x4 Splitter card with

optical amplifier
3-9 (main) 3-10

(non-main)
Full/1
MVAC
Multiple port Variable

Attenuator Card
3-9, 13-19 [main]

3-10, 13-20
[non-main]
Half/1
MVAC8B
Bidirectional Multiple
port Variable
Attenuator Card
3-9 (main) 3-10

(non-main)
Full/1
OPSA
Optical Protection
Switch card
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
OPSB
Optical Protection
Switch card with
non-latching switch
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
OSCT
OSC card with Total

power monitoring
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
PF
Power Filter
1,11
Half/1
....................................................................................................................................................................................................................................
1830 PSS
5-36
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-6
Card

Description
Slot Location
(continued)
Height / Number
of Slots
PTPCTL
PTP Controller Card
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
PTPIO
PTP I/O Card
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
RA2P
Raman Amplifier, 2
pumps
7-9 (main) 7-9

(non-main)
Full/1
SFC2
2 channel static
CWDM filter
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
SFC4
4 channel static
CWDM filter
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
SFC8
8 channel static
CWDM filter
3-9 (main) 3-10

(non-main)
Full/1
SFD5
5 channel static
DWDM filter
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
SFD8
8 channel static
DWDM filter
3-9 (main) 3-10

(non-main)
Full/1
SVAC
Single port VOA card
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
USRPNL
User Interface Panel
10 (main shelf only)
Full/1
WR2-88
1x2 Optimized
Wavelength Router,
88 channel
3-8, 13-18 (main)

3-9, 13-19
(non-main)
Half/2
WR8-88A
Wavelength Router
88-channel
3-8 (main) 3-9

(non-main)
Full/2
WR8-88AF
Wavelength Router,
88 channel with
FlexGrid
3-8 (main) 3-9

(non-main)
Full/2
WTOCM
Wavelength Tracker
Optical Channel
Monitoring card
3-9, 13-19 (main)

3-10, 13-20
(non-main)
Half/1
....................................................................................................................................................................................................................................
1830 PSS
5-37
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-6
Card
WTOCMA

Description
Wavelength Tracker
Optical Channel
Monitoring card
enhanced
Slot Location
3-9, 13-19 (main)
3-10, 13-20
(non-main)
(continued)
Height / Number
of Slots
Half/1
For a PSS-32 shelf slots 2-17 and 20-35 are considered universal slots (i.e., installation of
any Alcatel-Lucent 1830 PSS DWDM circuit pack is permitted) and any inserted circuit
pack is auto-provisioned. For PSS-32S shelf, the universal slots are 2-9, 12-19, 21-36. For
a PSS-16 shelf the universal slots are 3-9, 13-19.
If a single-slot card is inserted in a slot provisioned for a different type of single-slot card,
a mismatch is declared, causing a state transition against the provisioned card. Likewise
for a multi-slot card inserted into the same slots already provisioned for a different type of
multi-slot card of the same height and width.
If a single-slot card is inserted in one of the slots provisioned for a multi-slot card, the
following changes occur:
If the single-slot card is inserted in the slot acting as reference for the multi-slot card,
a mismatch is declared, causing a state transition against the provisioned card.
If the single-slot card is inserted in the slot different from the one acting as reference
for the multi-slot card, a mismatch is declared, causing a state transition against the
slot entity for the slot of the inserted card
If more than one card is inserted in slots provisioned for the multi-slot card, the net
result in terms of state changes is the pure sum of the results for each card inserted.
If a multi-slot card is inserted into the NE and one of the slots is already provisioned for
another single-slot or multi-slot card, the following changes occur.
If the slot acting as reference for the plugged multi-slot card is also acting as reference
for a provisioned card, a mismatch is declared, causing a state transition against the
provisioned card.
If the slot acting as reference for the plugged multi-slot card is not also acting as
reference for a provisioned card, a mismatch is declared, causing a state transition
against the slot entity for the reference slot of the inserted card.
Note: For a selected slot, if a card is present (i.e. not empty) but not provisioned, the
WebUI will pre-populate the Provisioned Type attribute with the present card type.
The user can select a different card type from the pick list.
....................................................................................................................................................................................................................................
1830 PSS
5-38
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisioning hierarchy
Objects must be provisioned in order from higher level to lower level according to the
following hierarchy:
Shelf
Circuit pack
Port/facility, including SFP/XFP if applicable
Optical fiber connection

Photonic cross connection
Equipment states
The NE supports equipment Primary State (PST) values as described below:
IS (IS-NR or IS-ANR) to indicate that the provisioned equipment entity is in

in-service state. IS-NR is normal. IS-ANR is abnormal, but with no
autonomous/management events.
OOS-AU to indicate that the provisioned equipment entity is in out-of-service state
caused solely by an autonomous event.
OOS-MA to indicate that the equipment entity is in out-of-service state caused solely
by a management event.
OOS-AUMA to indicate that the equipment entity is in out-of-service state caused by
both an autonomous event and a management event.
OOS-[AU]MA, MT to indicate that the equipment entity is in maintenance state.
The NE supports equipment Secondary State (SST) values as described below to indicate
the cause for being in a particular PST:
FLT to indicate that a failure is detected pertaining to the equipment entity.

UEQ to indicate that the equipment entity is not present in the system.
MEA to indicate that the equipment entity physically present in the system is invalid
(the inserted module is inconsistent with slot provisioning data or the inserted module
is of incompatible revision).
UAS to indicate that the equipment entity is not provisioned.
AINS to indicate that the equipment is waiting for the correction of the off-normal
condition (UEQ). Alarms will not be generated for the entity if AINS is present.
MT to indicate maintenance state.
The NE supports SST values as described below to provide additional state information.
ACT to indicate the active EC in equipment protection.

NBK to indicate no backup for EC in equipment protection.
STBY to indicate the standby EC in equipment protection.
WKG to indicate the working EC in equipment protection.
....................................................................................................................................................................................................................................
1830 PSS
5-39
Issue 1 June 2013

....................................................................................................................................................................................................................................
Equipment state transitions
States can be nested if they share common behavior with minor differences. Transitions
can originate and terminate from either a parent state or a child state. Transitions
originating from a parent state apply to all of its child states. The following defines four
major administrative parent states:
Unassigned State: An entity is unassigned when provisioning for it does not exist,
either because it was never provisioned, or because it was deleted.
Admin Out-of-Service State: A provisioned entity can be configured out-of-service.
In this state a card does not provide service, but does perform fault monitoring (results
of which can be retrieved). It does not generate alarms or conditions. A card cannot be
put in this state if any of its ports are admin in-service.
Admin In-Service State: A provisioned entity can be configured in-service. In this
state a card provides service, performs fault monitoring, and generates alarms and
conditions.
Admin Maintenance State: A provisioned entity can be configured in maintenance
to perform a temporary maintenance activity on it. In this state a card continues to
provide service and performs fault monitoring (results of which can be retrieved). But
it does not generate alarms or conditions. A card cannot be put in this state if any of its
ports are admin in-service.
State transitions are determined by user operations and autonomous system processing
(e.g. fault detection). A user can perform the following operations on equipment entities:
Enter/Delete provisioning.
Edit provisioned parameter values.
Modify administrative state (logically remove or logically restore the entity).

Physically insert or physically remove the entity.
The same equipment state machine covers all modules. But for mandatory modules, some
states and transitions do not apply, due to the following rules:
Mandatory modules are automatically provisioned upon shelf creation, whether

present or not.
Mandatory modules are automatically configured to IS (in-service) upon insertion.
Mandatory modules cannot be configured to OOS (out-of-service).

Mandatory modules cannot be deleted.
....................................................................................................................................................................................................................................
1830 PSS
5-40
Issue 1 June 2013

....................................................................................................................................................................................................................................
Service affecting (SA) / Non-service affecting (NSA) conditions
When an equipment condition is defined as having the possibility to be either

service-affecting (SA) or non-service affecting (NSA), the following requirements apply:
An equipment condition is SA if the equipment has supported facilities below it, and
for any of its supported facilities a LOS would be service affecting.
An equipment condition is NSA if the equipment has no supported facilities below it,
and for any of its supported facilities a LOS would not be service affecting.
When an equipment condition on protected or redundant equipment is defined as having

the possibility to be either SA or NSA, the following requirements apply:
An equipment condition is SA if the protecting/redundant equipment is not IS.
An equipment condition is NSA if the protecting/redundant equipment is IS.
Equipment provisioning changes
The system supports the ability to modify the provisioned data associated with an
equipment entity. The modifications take effect immediately. This capability allows the
Primary State (PST) and Secondary State (SST) parameters to be modified for all
equipment entities except shelves and mandatory equipment. The user is able to perform
the following equipment state changes:
To administrative maintenance state

To administrative out-of-service state
To administrative in-service state
The following system-level equipment parameters can be modified:
System SONET/SDH operation mode. This affects system-wide naming of cards and
ports. It affects the content of alarm and event text. When the mode is changed, PM is
restarted with cleared counters, new PM names, and new TCA defaults. Byte filtering
changes to conform to the specified standard. The NE clears its database and clears all
services.
Note: When switching between SDH or SONET mode, the user needs to hard reboot
(cold reset) the LC packs.
System default AINS timer value. This applies to all ports that do not have an
individual port-level AINS timer provisioned.
Deprovisioning
The following applies to deprovisioning equipment:
A Delete Equipment command is supported to delete provisioned equipment.

Deletion of an equipment entity is not allowed if that entity is not logically removed.
Deletion of mandatory equipment in a PSS shelf is not allowed: (i.e., PF, FAN,
USRPNL, active EC).
....................................................................................................................................................................................................................................
1830 PSS
5-41
Issue 1 June 2013

....................................................................................................................................................................................................................................
Deletion of a PSS shelf is not allowed if it contains any provisioned modules (except
mandatory equipment).
Deprovisioning procedures on an entity do not cause equipment faults on other
equipment entities.
Pre-provisioning
A user can pre-provision any empty slot in a PSS shelf which supports non-mandatory
modules for a specific equipment type. The pre-provisioning must take into account
module height and width, and will fail if an already-assigned or invalid slot is used.
Pre-provisioning requires that the network element be equipped with a control card only.
All of the other components, including additional shelves, are assigned slots or locations
to create a virtual configuration that can be implemented at a later time. You can use all of
the provisioning commands to pre-provision a network element, including those used for
service provisioning.
Modules inserted in a pre-provisioned slot have their state determined by module fault
status, module mismatch status (comparison of actual type and pre-provisioned type), and
operator-provisioned PST value.
Note: It is possible to pre-provision equipment by downloading and activating a
previously stored database.
Automatic in-service (AINS)
The pre-provisioning command includes specification of an AINS state value to

determine whether a card missing alarm should be generated immediately for the empty
slot, or whether no alarm should be generated until after a card is plugged into the slot for
the first time. If AINS is enabled, all alarms are suppressed for the entity while it is not
present. When the card is inserted in the shelf, the card and ports on the card that are
configured AINS are automatically set up.
For cards, AINS is automatically removed when the pre-configured card type is inserted
in the shelf. For ports, AINS remains in effect while there are alarms on the port, and for a
configurable period of time after the port is alarm free.
Auto-provisioning
Auto-provisioning, also referred to as Plug & Play, means that new non-mandatory
equipment is detected and configured automatically upon card insertion (or controller
restart), if allowed in that location, and if there is no conflict (mismatch) with other
provisioning. Auto-provisioned modules have their initial state determined by module
fault status.
Note: If a card is deleted when it is still physically present, it will not be
rediscovered and auto-provisioned until it is physically removed and reinserted, or
until the system reboots (whichever comes first).
....................................................................................................................................................................................................................................
1830 PSS
5-42
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
Contents
5-44
5-46
5-50
5-53
5-57
5-61
5-64
5-66
5-70
5-72
5-74
5-76
5-84
5-89
5-92
Procedure 5-16: Deprovision an ODUk path termination function
5-95
5-97
5-99
5-101
5-107
5-109
5-111
5-113
Procedure 5-24: Initiate an equipment protection switch manually
5-115
5-117
....................................................................................................................................................................................................................................
1830 PSS
5-43
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to set the equipment provisioning mode.

The equipment provisioning mode defines if equipment has to be manually provisioned,
also the possibility to pre-provision or if the equipment is auto-provisioned.
Note: The related Facilities are always-created.
SET-PRMTR-NE
RTRV-PRMTR-NE
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the navigation pane of the Alcatel-Lucent 1830 PSS ZIC window, select System.
Result: System is highlighted in the navigation pane. The display pane provides
categories of system level configuration information under Contents of 'System'.
...................................................................................................................................................................................................
Choose one of the following options to open a relevant dialog box:
In the Action menu, select Properties General.
Right-click on System in the navigation pane, and select Properties General from
the context menu that opens.
....................................................................................................................................................................................................................................
1830 PSS
5-44
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Properties - General window opens.
The Properties - General window contains a table with the common system
parameters. The parameters USERLABEL , PROVMODE, ALTITUDE, AINSSTDFLT,
OTUDFLTASAP, ODUNDFLTASAP, ODUPTFDFLTASAP, AUNDFLTASAP, STSNDFTASAP,
ENVCONDRSTR, and Third Party Modules are configurable.
Reference: General properties of the system as a whole (p. 5-470)
...................................................................................................................................................................................................
Double-click inside a table cell to modify the respective parameter setting.

...................................................................................................................................................................................................
Verify your settings and correct if necessary.

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-45
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create an extension shelf.

Important! An extension shelf has to be entered first using this procedure before it
can be interconnected to the other shelves (see Alcatel-Lucent 1830 PSS Installation
and System Turn-Up Guide (ITG).
Multi-shelf configuration
In multi-shelf configurations the main shelf and the extension shelves must be
interconnected by LAN cables in the following way:
The external LAN interfaces (ES1,ES2) of the left matrix card must be connected to
the external LAN interfaces (ES1,ES2) of the left matrix card of the neighbor shelves
The external LAN interfaces (ES1,ES2) of the right matrix card must be connected to
the external LAN interfaces (ES1,ES2) of the right matrix card of the neighbor
shelves
The external LAN interfaces ES1 are always connected to the external LAN interfaces
ES2 of the neighbor shelf
This must be done from one shelf to the next shelf so that a ring closure is
accomplished
....................................................................................................................................................................................................................................
1830 PSS
5-46
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following figure shows the LAN connections in a configuration with three shelves.
Figure 5-1 Shelf interconnection
Shelf # w
Left
ES1
Right
ES1
Left
ES2
Right
ES2
Shelf # x
Left
ES1
Right
ES1
Left
ES2
Right
ES2
Shelf # y
Left
ES1
Right
ES1
Left
ES2
Right
ES2
ENT-EQPT
Before you begin

assure that the rotary switches on the Bus Termination Cards (BT36, BTC3T8) on the
master shelf and extension shelf are correctly set (see Alcatel-Lucent 1830 PSS
Installation and System Turn-Up Guide (ITG))
....................................................................................................................................................................................................................................
1830 PSS
5-47
Issue 1 June 2013

....................................................................................................................................................................................................................................
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the part of equipment you want
to create via Equipment Rack 1.
...................................................................................................................................................................................................
Then select Create Shelf , either by selecting Action from the main menu bar or by using
Result: The Enter Shelf dialogue box is displayed.
...................................................................................................................................................................................................
Under Shelf enter the extension shelf number. A maximum 7 extension shelves is
allowed.
...................................................................................................................................................................................................
Under Application Mode select OCS.

Additional information Application mode for the PSS36 shelf. Extension shelves can
only be of type OCS.

...................................................................................................................................................................................................
Under Matrix Size define the planned bandwidth switching capacity (Gb/s) of the Shelf.
960
1920
3840
Matrix Size mismatch If the provisioned Matrix Size is higher than the used MTX a
wrong Secondary State (SST) for one matrix in the new created extension shelf is
indicated.
If a new extension shelf is provisioned with a higher Matrix Size than the MTX used
in the shelf one MTX shows MEA (Mismatch of Equipment Attributes). The second
matrix will not boot, but no MEA is reported.
Follow the given indication to change MTXs or MTXSIZE. For the second MTX
MEA will be reported as soon as the first MTX matches with the MTXSIZE.
Remark: It is always allowed to provision a higher Matrix Size than the MTX used.
....................................................................................................................................................................................................................................
1830 PSS
5-48
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Under Air Flow define the Air Flow Application mode .

Additional information Air Flow Application mode for PSS-36 Shelf to consider the
airflow restriction of the different rack types and the position of the shelf in the rack.
HP36
High Power Application for PSS36 Shelf (default)
HP36LOWSUBR
High Power Application for PSS36 Shelf and subrack is mounted as the lower
subrack in a ETSI rack.
...................................................................................................................................................................................................
Under Alarm Profile define the alarm Severity Assignment Profile (ASAP) .
Additional information A reference to an existing (equipment related) Alarm Severity
Assignment Profile (ASAP) instance by using the string of the USERLABEL

parameter of that ASAP instance.
...................................................................................................................................................................................................
Verify your settings, and correct if necessary.

Then click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-49
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to remove an extension shelf.

Important! An extension shelf has to be removed first using this procedure before it
can be disconnected from the other shelves (see Alcatel-Lucent 1830 PSS Installation
and System Turn-Up Guide (ITG)).
Multi-shelf configuration
In multi-shelf configurations the main shelf and the extension shelves must be
interconnected by LAN cables in the following way:
The external LAN interfaces (ES1,ES2) of the left matrix card must be connected to
the external LAN interfaces (ES1,ES2) of the left matrix card of the neighbor shelves
The external LAN interfaces (ES1,ES2) of the right matrix card must be connected to
the external LAN interfaces (ES1,ES2) of the right matrix card of the neighbor
shelves
The external LAN interfaces ES1 are always connected to the external LAN interfaces
ES2 of the neighbor shelf
This must be done from one shelf to the next shelf so that a ring closure is
accomplished
....................................................................................................................................................................................................................................
1830 PSS
5-50
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following figure shows the LAN connections in a configuration with three shelves.
Figure 5-2 Shelf interconnection
Shelf # w
Left
ES1
Right
ES1
Left
ES2
Right
ES2
Shelf # x
Left
ES1
Right
ES1
Left
ES2
Right
ES2
Shelf # y
Left
ES1
Right
ES1
Left
ES2
Right
ES2
RMV-EQPT
Before you begin

assure that all equipment on the shelf has been removed before, see Procedure 5-6:
Set a board/module out of service (p. 5-61).
Required equipment
Alcatel-Lucent 1830 PSS WebUI
....................................................................................................................................................................................................................................
1830 PSS
5-51
Issue 1 June 2013

....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the shelf you want to remove via
Equipment Rack 1 Shelf (2..31)
...................................................................................................................................................................................................
Then select Service State Unassign, either by selecting Action from the main menu
Result: The Unassign dialogue box is displayed.
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-52
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to provision a equipment entity regardless of whether the equipment is
plugged in the slot or not.
The procedure can be used to provision one of the following equipment:
PSS-36 Shelf
PSS-64 Shelf
2XANY40G (2x 40G ANY Card)

10XOTH10G (10x 10G OTH Card)
10XETH10G (10x 10G GBE Card)

24XANYMR (24x Multirate ANY Card)
8XETH1G (8x 1 GBE Card)

24XANYMRB (24x Multirate ANY Card Version B)
24XETH1GB (24x 1 GBE Card Version B)
11QCUP (4 x 11G Switchponder - 8dB raw attenuation range)

11QCUPC (4x 11G Switchponder)
43SCUP (1 43G Switchponder Card)
130SCUP (1x 130G Switchponder Card)
112CFPTB (1x 100G Test Board)

SFC8 (Static Filter CWDM Card for eight CWDM channels)
10XSTH10G (10x 10G Synchronous Transport Hierarchy Card)

24XSTHMR (24x Multirate Synchronous Transport Hierarchy Card)
Port on 2XANY40G cards
XFP on 10XANY10G cards

SFP on 24XANYMR cards
ED-EQPT for provisioning
ENT-EQPT for pre-provisioning
....................................................................................................................................................................................................................................
1830 PSS
5-53
Issue 1 June 2013

....................................................................................................................................................................................................................................
Related information
A card or interface module that has not been provisioned, is reflected by the PST and SST
parameters (only if the SHELF has been provisioned ): :
If equipped:
PST=OOS-MA
SST=UAS
If unequipped:
PST=OOS-AUMA
SST=UAS & UEQ
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To provision a specific part of equipment in the Alcatel-Lucent 1830 PSS ZIC selection
tree select a free and for this part of equipment allowed slot via Equipment Rack 1
Shelf 1
Related information See Alcatel-Lucent 1830 PSS Product Information and Planning
Guide (PIPG), chapter 4 Product description for the allowed location of the IO
cards.
...................................................................................................................................................................................................
Then select Assign <part of equipment>, either by selecting Action from the main
Result: A window opens, for configuring the part of equipment.
...................................................................................................................................................................................................
In the field Provisioned Type select the type of the equipment to be provisioned
....................................................................................................................................................................................................................................
1830 PSS
5-54
Issue 1 June 2013

....................................................................................................................................................................................................................................
Allowed Interface Modules: The Provisioned Type parameters for SFP/XFP
modules are restricted per card type:
10XANY10G, 4XANY10G:
{SR111G1AU, IR211G1AU, LR211G1AU, LRT11G1TU, SR<xx>W11G1TUC,
SR<xx>W11G1TUI, LR<xx>W11G1TUC, LR<xx>W11G1TUI,
LR<xx>DW11G1TUC, USER}
10XETH10G:
{SR111G1AU, IR211G1AU, LR211G1AU, USER}
10XOTH10G:
{SR111G1AU, IR211G1AU, LR211G1AU, LRT11G1TU,SR<xx>W11G1TUC,
24XANYMR:
{SR10G155TU, SL10G155TU, SL20G155TU, SR10G622TU, SL10G622TU,
SL20G622TU, SR12G7TU, IR12G7TU, LR12G7TU, LR22G7TU, IR12G7AU,
1000BSXU, 1000BLXU, 1000BZXU, USER}
24XETH1G, 8XETH1G:
{IR12G7AU, 1000BSXU, 1000BLXU, 1000BZXU, USER}
24XANYMRB:
24XETH1GB, 8XETH1GB:
10XSTH10G:
24XSTHMR:
{SR12G7TU, IR12G7TU, LR12G7TU, LR22G7TU, IR12G7AU, USER}
Note: The following modules have no SFPs/XFPs and the values FIXED PORT is set
automatically::
2XANY40G
11QCUP
11QCUPC has SFPs/XFPs, but handled as NO SFPs/XFPs
43SCUP
130SCUP
....................................................................................................................................................................................................................................
1830 PSS
5-55
Issue 1 June 2013

....................................................................................................................................................................................................................................
The 112CFPTB has one CFP, but is handled as NO SFPs/XFPs

SFC8
...................................................................................................................................................................................................
In the field Automatic In-Service select the Automatic in service mode to which the
equipment is to be set:
AINS
If the addressed equipment is currently being plugged out, then standing conditions
are suppressed for this equipment. If the address equipment is currently being plugged
in, then standing conditions are raised (they get only be cleared and suppressed if the
equipment gets plugged out later). Note: There is no autonomous transition by a timer
threshold as applicable by transmission facilities.
NOWAIT
Standing conditions are always raised independent if the addressed equipment is

currently being plugged in or out. Plugging-out of this equipment later does not
suppress standing conditions.
...................................................................................................................................................................................................
In the field Primary State select either IS or OOS.

...................................................................................................................................................................................................
In the field SS-Bit you can configures the SS-Bit SONET/SDH overhead transmit value.
The value of the parameter is usable only on SDH/SONET terminated signals (not on
SDH/SONET transparent signals):
SS00
if the REGION parameter is ANSI.
SS10
if the REGION parameter is ETSI.

...................................................................................................................................................................................................
In the field Alarm Profile you can assign an Alarm Severity Assignment Profile (ASAP)
to the selected entity.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-56
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to provision a equipment entity regardless of whether the equipment is
plugged in the slot or not.
ED-EQPT for provisioning

ENT-EQPT for pre-provisioning
Related information
A card or interface module that has not been provisioned, is reflected by the PST and SST
parameters (only if the SHELF has been provisioned ): :
If equipped:
PST=OOS-MA
SST=UAS
If unequipped:
PST=OOS-AUMA
SST=UAS & UEQ
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To provision a specific part of equipment in the Alcatel-Lucent 1830 PSS ZIC selection
tree select a free and for this part of equipment allowed slot via Equipment Rack 1
Shelf 1 <Slot with usable card type>
....................................................................................................................................................................................................................................
1830 PSS
5-57
Issue 1 June 2013

....................................................................................................................................................................................................................................
Allowed interface modules: The SFP/XFP modules are restricted per card type:
10XANY10G, 4XANY10G:
{SR111G1AU, IR211G1AU, LR211G1AU, LRT11G1TU, SR<xx>W11G1TUC,
10XETH10G:
10XOTH10G:
{SR111G1AU, IR211G1AU, LR211G1AU, LRT11G1TU,SR<xx>W11G1TUC,
24XANYMR:
24XETH1G, 8XETH1G:
24XANYMRB:
24XETH1GB, 8XETH1GB:
10XSTH10G:
24XSTHMR:
{SR12G7TU, IR12G7TU, LR12G7TU, LR22G7TU, IR12G7AU, USER}
Note: The following modules have no SFPs/XFPs and the values FIXED PORT is set
automatically::
2XANY40G
11QCUP
11QCUPC has SFPs/XFPs, but handled as NO SFPs/XFPs
43SCUP
130SCUP
....................................................................................................................................................................................................................................
1830 PSS
5-58
Issue 1 June 2013

....................................................................................................................................................................................................................................
The 112CFPTB has one CFP, but is handled as NO SFPs/XFPs

SFC8
Related information See Alcatel-Lucent 1830 PSS Product Information and Planning
Guide (PIPG), chapter 4 Product description for the allowed location of the IO
cards.
...................................................................................................................................................................................................
Then select Assign <XFP or SFP>, either by selecting Action from the main menu bar
Result: A window opens, for configuring the part of equipment.
...................................................................................................................................................................................................
In the field Provisioned Type select the type of the equipment to be provisioned.
Reference: Refer to list in Step 1.
...................................................................................................................................................................................................
In the field Client Select select the client selection mode for the equipment to be
provisioned
Additional info: See Table 5-2, Port group modes and client selection modes
(p. 5-11).
Note: The payload type ODU3E2 is not supported by the ports of the 2xANY40G
IO-Card . But the Alcatel-Lucent 1830 PSS ZIC shows ODU3E2 for the
2XANY40G ports as available value.
Do not select ODU3E2 for 2XANY40G ports.
...................................................................................................................................................................................................
In the field Automatic In-Service select the Automatic in service mode to which the
equipment is to be set:
AINS
If the addressed equipment is currently being plugged out, then standing conditions
are suppressed for this equipment. If the address equipment is currently being plugged
in, then standing conditions are raised (they get only be cleared and suppressed if the
equipment gets plugged out later). Note: There is no autonomous transition by a timer
threshold as applicable by transmission facilities.
NOWAIT
Standing conditions are always raised independent if the addressed equipment is

currently being plugged in or out. Plugging-out of this equipment later does not
suppress standing conditions.
....................................................................................................................................................................................................................................
1830 PSS
5-59
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the field Primary State select either IS or OOS.

...................................................................................................................................................................................................
In the field Alarm Profile you can assign an Alarm Severity Assignment Profile (ASAP)
to the selected entity.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-60
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to set a board/module out of service

The procedure can be used for the following equipment:
FLC36EA (First Level Controller card for enhanced performance application for
PSS-36
ECHC (First Level Controller card in PSS-64)
Matrix Circuit Packs / MTX (Matrix card with various switching capacity)
MT960C (Matrix card with 960G switching capacity)
MT1T9 (Matrix card with 1.92T switching capacity)

MT1T9C (Matrix card with 1.92T switching capacity)
MT3T8 (Matrix card with 3.8T switching capacity)
PSF (Power Supply Filter)

FAN3T8 (Fan unit in PSS-64 shelf S3T8)
HPCFAP (High-Power Connection, Fuse and Alarm Panel)
IOCs (IO cards)





....................................................................................................................................................................................................................................
1830 PSS
5-61
Issue 1 June 2013

....................................................................................................................................................................................................................................

SFP on 24XANYMR and 24XETH1G card
XFP on 10XANY10G,10XOTH10G and 10XETH10G card
RMV-EQPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
to remove via Equipment Rack 1 Shelf (1..31)
...................................................................................................................................................................................................
Then select Service State Remove, either by selecting Action from the main menu
Result: The Remove dialogue box is displayed.
...................................................................................................................................................................................................
Under Command Mode you can choose between NORM and FORCED.
Required Forced Mode Settings for IOC/SFP/XFP/Port: If the command is executed
for addressed equipment entities that have its SST parameter being set to SDEE, then
the MODE parameter must be specified with the value FRCD to succeed.
This applies to:
IOC
SFP/XFP
Port
....................................................................................................................................................................................................................................
1830 PSS
5-62
Issue 1 June 2013

....................................................................................................................................................................................................................................
Required Forced Mode Settings for Equipment Group If the command is executed
for equipment that is part of a protection group which is currently active (having the
SST parameter being set to the value WKG),, the action is refused with the text:
The active FLC/MTX cannot be taken OOS!. This applies to:
FLC (First Level Controller )
MTX (Matrix card )
Required Forced Mode Settings for OOS of Mate Equipment: If the addressed
equipment entities shall be set to OOS (with the accompanied PST parameter value
OOS) and the equipment that has mate equipment and the mate equipment is not in
state IS, then the CMDMDE parameter must be specified with the value FRCD to
succeed. This applies to:
FAN3T8 (Fan)
PSF3T8 (Power supply)
PSFC (Power Supply Filter for PSS-36 shelf)
Required Forced Mode Settings for OOS of specific Equipment: If the addressed
equipment entities shall be set to OOS (with the accompanied PST parameter value
OOS), then the CMDMDE parameter must be specified with the value FRCD to
succeed.
This applies to:
HPCFAP
FAN in PSS-36
...................................................................................................................................................................................................

Then click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-63
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to deprovision an equipment object entity at the physical location
identified by its Access Identifier (AID) and deprovisions the specified equipment,
regardless of whether the equipment is installed in the system.
The procedure can be used for the following equipment:
PSS-36 Shelf
PSS-64 Shelf






XFP on 10XANY10G cards
SFP on 24XANYMR cards
DLT-EQPT
....................................................................................................................................................................................................................................
1830 PSS
5-64
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
Note: The equipment must be in state OOS-MA.

...................................................................................................................................................................................................
to de-provision via Equipment Rack 1 Shelf (1..31) <Slot>
...................................................................................................................................................................................................
Then select Unassign, either by selecting Action from the main menu bar or by using the
Result: A confirmation window opens, stating that the selected part of equipment will
be unassigned.
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-65
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to perform a matrix card upgrade.

Important! Traffic may be switched via inactive MTX card, pulling the inactive
MTX may destroy traffic.
At first trouble-shoote an INT-ERR alarm . If necessary, perform a forced switch to
the MTX card that has not such an alarm. It is strongly recommended that INT-ERR
alarms must be repaired before doing MTX exchanges (STM to LSI) or MTX upgrade
(capacity increasings).
Supported exchanges
Supported exchanges specific for upgrade scenario:
PSS-64: 2 x MT1T9 (STM/LSI) <-> MT1T9 (STM/LSI) / MT3T8 (LSI) <-> 2 x

MT3T8 (LSI)
PSS-36: 2 x MT960C (STM/LSI) <-> MT960C (STM/LSI) / MT1T9C (LSI) <->2 x
MT1T9C (LSI)
Mixed Operation
The following states are called Mixed Operation:
The two MTXs have same capacity but are produced from different vendors
(STM/LSI)
Note: STM und LSI MTXs with same capacity can be not differentiated by the
Mnemonic only the APN in the RIM is different.
one MTX has higher capacity as the other MTX .
Mixed Operation is only supported temporarily for MTX exchange or upgrade. If a mixed
operation is detected by the system, a condition MIXOPERAT is raised.
ALW-SWDX-EQPT
INH-SWDX-EQPT
RTRV-DX-EQPT
SW-DX-EQPT
....................................................................................................................................................................................................................................
1830 PSS
5-66
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Perform a database backup, see OCS backup and restore procedures (p. 17-16).
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the standby agnostic matrix card
via Equipment Rack 1 Shelf 0x:PSSxx.
...................................................................................................................................................................................................
Then select Switching State Inhibit Switch, either by selecting Action from the main
Result: The Inhibit Switch to Duplex dialogue box is displayed.
...................................................................................................................................................................................................
Click Yes.
...................................................................................................................................................................................................
Pull out the standby agnostic matrix card.

Reference: Refer to Procedure 19-3: Common card mounting rules (p. 19-10).
...................................................................................................................................................................................................
Insert the new agnostic matrix card.

...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the newly inserted agnostic
matrix card for which you want to enable autonomous or manual equipment protection
switching via Equipment Rack 1 Shelf 0x:PSSxx
...................................................................................................................................................................................................
Then select Switching Allow Switch, either by selecting Action from the main menu
....................................................................................................................................................................................................................................
1830 PSS
5-67
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Allow Switching dialogue box is displayed.

...................................................................................................................................................................................................
Click Yes.
...................................................................................................................................................................................................
Make the newly inserted agnostic matrix card the active one.
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the part of equipment for which
you want to perform the switch via Equipment Rack 1 Shelf (1 ... 31)
...................................................................................................................................................................................................
10
Then select Switching Switch, either by selecting Action from the main menu bar or
Result: The Switch Duplex dialogue box is displayed.
...................................................................................................................................................................................................
11
Under Command Mode you can choose between NORM and FORCED. For MTX upgrade
NORM (and not FORCED) should be used.
...................................................................................................................................................................................................
12
Click Switch.
...................................................................................................................................................................................................
13
Click Yes.
Result: Now an equipment protection switch from the currently active unit to the
standby unit takes place. As a result, the formerly standby unit becomes active, and
the formerly active unit becomes standby.
...................................................................................................................................................................................................
14
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the standby agnostic matrix card
via Equipment Rack 1 Shelf 0x:PSSxx.
...................................................................................................................................................................................................
15
...................................................................................................................................................................................................
16
Click Yes.
...................................................................................................................................................................................................
17
Pull out the standby agnostic matrix card.
....................................................................................................................................................................................................................................
1830 PSS
5-68
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
18
Insert the new agnostic matrix card.

...................................................................................................................................................................................................
19
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the newly inserted agnostic
matrix card for which you want to enable autonomous or manual equipment protection
switching via Equipment Rack 1 Shelf 0x:PSSxx
...................................................................................................................................................................................................
20
...................................................................................................................................................................................................
21
Wait until the ?UPGSWITCH alarm is displayed.

...................................................................................................................................................................................................
22
Change the matrix size to the actual value.

In the navigation pane of the Alcatel-Lucent 1830 PSS ZIC window, select System.
Result: System is highlighted in the navigation pane. The display pane provides
categories of system level configuration information under Contents of 'System'.
...................................................................................................................................................................................................
23
Right-click on System in the navigation pane, and select Properties General from
Result: The Properties - General window opens.
Reference: General properties of the system as a whole (p. 5-470)
...................................................................................................................................................................................................
24
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-69
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to configure an optical interface port. Modifies the specified facility
parameter values previously autoprovisioned when it's underlying equipment module was
provisioned.
ED-ODU0
ED-ODU1
ED-ODU2
ED-ODU2E
ED-ODU3
ED-ODU3E2
ED-ODU4
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the navigation pane of the Alcatel-Lucent 1830 PSS ZIC window, expand the
navigation tree under Facilities, and select the desired Optical Channel Group.
...................................................................................................................................................................................................
In the navigation pane, right-click on the optical interface port , and select Properties
General from the context menu that opens.
In the navigation pane, click on or select the optical interface port, and select Action
Properties General from the main menu bar.
....................................................................................................................................................................................................................................
1830 PSS
5-70
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result:
Result: The Properties - General window opens which contains a table with the
configuration parameters of the selected optical interface port.

Reference: See General properties of an OTU port facility (p. 5-489).
...................................................................................................................................................................................................

Additional information: The single parameters are sorted according to so-called
column groups. To modify a specific parameter of a column group you have to select
the respective column group radio button before.
Reference: See General properties of an OTU port facility (p. 5-489).
...................................................................................................................................................................................................
Additional information: Two different values shall be supported depending on the
NE REGION
This applies to:
FRCD for ETSI
NORM for ANSI
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-71
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to configure Optical Channel parameters.

ED-OCH
RTRV-OCH
RMV-OCH
RST-OCH
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
In the navigation pane, right-click on the Optical Channel, and select Properties
In the navigation pane, click on the Optical Channel, and select Action Properties
General from the main menu bar.
Result:
....................................................................................................................................................................................................................................
1830 PSS
5-72
Issue 1 June 2013

....................................................................................................................................................................................................................................
configuration parameters of the selected Optical Channel.

Reference: See General properties of an optical (p. 5-531).
...................................................................................................................................................................................................

Additional information: The single parameters are sorted according to so-called
column groups. To modify a specific parameter of a column group you have to select
the respective column group radio button before.
...................................................................................................................................................................................................
Additional information: Two different values shall be supported depending on the
NE REGION
This applies to:
FRCD for ETSI
NORM for ANSI
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-73
Issue 1 June 2013

Procedure 5-11: Perform remote laser shutdown on OTH

network ports
....................................................................................................................................................................................................................................

network ports
When to use
Use this procedure to perform remote laser shutdown on OTH network ports.
ED-OCH
RTRV-OCH
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
In the navigation pane, right-click on the Optical Channel, and select Properties
In the navigation pane, click on the Optical Channel, and select Action Properties
General from the main menu bar.
Result:
....................................................................................................................................................................................................................................
1830 PSS
5-74
Issue 1 June 2013


network ports
....................................................................................................................................................................................................................................
configuration parameters of the selected Optical Channel.

...................................................................................................................................................................................................
Select Misc. in the Column Groups box.

...................................................................................................................................................................................................
Double-click inside the Actual Laser State table cell and select Off.
Note: OCH facility must be Out Of Service to switch laser off.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-75
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create an ODUn path termination with a default substructure.
The following two principle ways to create an ODUn path termination can be
distinguished:
Implicit creation of an ODUn path termination
Explicit (manual) creation of an ODUn path termination
For both ways, corresponding procedures are provided in the following.

Implicit creation of ODUn facilities and ODUn path terminations
When I/O cards are inserted into an Alcatel-Lucent 1830 PSS shelf, then facilities are
automatically created, namely:
for a 1 100G Switchponder (130SCUP), an OTU4 with an unterminated higher

order ODU4 (higher order ODU4 NIM, not substructured) is auto-created.
for a 4 11G Switchponder (11QCUPC), an OTU2 with an unterminated higher order
ODU2 (higher order ODU2 NIM, not substructured) is auto-created.
for a 1 43G Switchponder, an OTU3E2 with an unterminated higher order ODU3E2
(higher order ODU3E2 NIM, not substructured) is auto-created.
for a 2 40G ANY Port Unit, an OTU3 with an unterminated higher order ODU3
(higher order ODU3 NIM, not substructured) is auto-created.
Then, you can create an ODUn (n = 2, 3, 3E2 or 4) path termination with a default
substructure by making a cross-connection between the unterminated ODUn and a virtual
ODUn path terminated entity from an ODUn pool.
The procedure Implicitly create an ODU path termination (p. 5-78) describes how to
make such a cross-connection.
Explicit (manual) creation of an ODUn path termination
A higher order ODUn path termination can be created manually by explicitly selecting an
ODUPTF (terminated ODU) facility from a pool of ODUPTF entities.
The following higher order ODUPTF entities are supported:
Terminated ODU2 entity identified as an ODU2 with a virtual slot number
....................................................................................................................................................................................................................................
1830 PSS
5-76
Issue 1 June 2013

....................................................................................................................................................................................................................................
Terminated ODU3E2 entity identified as an ODU3E2 with a virtual slot number

The virtual slot number that identifies a terminated ODUn entity is 71.
When a higher order ODU2, ODU3, ODU3E2 or ODU4 path termination is created
manually, it is created with a default payload type ODUMPT21 (ODUk multiplex
structure with 1.25G Tributary Slots) and a default payload structure with:
8 x ODU0 for an ODU2 path termination and the default payload type ODUMPT21
or
4 x ODU1 for an ODU2 path termination and payload type ODUM or

or
16 x ODU1 for an ODU3 path termination and payload type ODUM or
32 x ODU0 for an ODU3E2 path termination and the default payload type
ODUMPT21 or
The default payload type is ODUMPT21 (ODUk multiplex structure with 1.25G
Tributary Slots). For manual creation of ODUn path termination via ZIC the selection of
payload type is mandatory (valid payload type: ODUMPT21).
For ODU3 and ODU2 path termination two payload types are possible ODUMPT21
(default payload type) or ODUM.
For payload type ODUMPT21 the default payload structure is N x ODU0 where N=8
for ODU2 path termination and N=32 for ODU3 path termination.
For payload type ODUM the default payload structure is N xODU1 where N=4 for
ODU2 path termination and N=16 for ODU3 path termination.
When a higher order ODU4 path termination (payloadtype ODUMPT21) is created

manually, it is created with a default payload structure of 10 x ODU2 (ODUMPT21).
ENT-ODUPTF
ENT-CRS-ODU2
ENT-CRS-ODU3
ENT-CRS-ODU3E2
ENT-CRS-ODU4
ENT-CRSPROT-ODU2
ENT-CRSPROT-ODU3
....................................................................................................................................................................................................................................
1830 PSS
5-77
Issue 1 June 2013

....................................................................................................................................................................................................................................
ENT-CRSPROT-ODU3E2
ENT-CRSPROT-ODU4
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
If
then
you want to implicitly create an

ODU path termination,
refer to Implicitly create an ODU path termination

(p. 5-78).
you want to manually create an

ODU path termination,
refer to Manually create an ODU path termination

(p. 5-82).
E...................................................................................................................................................................................................
N D O F S T E P S
Implicitly create an ODU path termination

...................................................................................................................................................................................................
In the navigation pane of the Alcatel-Lucent 1830 PSS ZIC window, select the desired
OTU2, OTU3, OTU3E2 or OTU4 port in the navigation tree under Facilities.
....................................................................................................................................................................................................................................
1830 PSS
5-78
Issue 1 June 2013

....................................................................................................................................................................................................................................
As a result, the unterminated ODU2 (ODU2 NIM), unterminated ODU3 (ODU3

NIM), unterminated ODU3E2 (ODU3E2 NIM) or unterminated ODU4 (ODU4 NIM)
is displayed in the display pane. The following figure illustrates this using an ODU3
NIM as an example.
Figure 5-3 Example for the representation of an ODU3 NIM
ODU3 NIM
g-upg-0060
...................................................................................................................................................................................................
Select the ODU NIM by clicking on it in the display pane.

Result: The ODU NIM is highlighted.
...................................................................................................................................................................................................
Right-click on the selected ODU NIM, and select Connect To ODUPOOL

Protected or Connect To ODUPOOL Unprotected from the context menu that
opens.
Select Connect To ODUPOOL Unprotected if you want to make an
unprotected cross-connection between the selected ODU NIM and the ODU pool.
Select Connect To ODUPOOL Protected if you want to make a protected
cross-connection between the selected ODU NIM and the ODU pool.
In the Action menu, select Connect To ODUPOOL Protected or Connect To
ODUPOOL Unprotected.
Select Connect To ODUPOOL Unprotected if you want to make an
unprotected cross-connection between the selected ODU NIM and the ODU pool.
Select Connect To ODUPOOL Protected if you want to make a protected
cross-connection between the selected ODU NIM and the ODU pool.
Result: The Connection to ODUPOOL Dialog window opens.
...................................................................................................................................................................................................
If
then
you selected Connect To

ODUPOOL Protected for an
ODU2, ODU3, ODU3E2 or
ODU4.
continue with the next step.
....................................................................................................................................................................................................................................
1830 PSS
5-79
Issue 1 June 2013

....................................................................................................................................................................................................................................
If
then
you selected Connect To

ODUPOOL Unprotected for an
ODU2, ODU3, ODU3E2 or
ODU4.
continue with Step 13.
...................................................................................................................................................................................................
Enter the protecting facility into the Alternate field, or use the button to open the
Alternate window, and select the protecting facility from the facilities available in the
Alternate window.
...................................................................................................................................................................................................
Under XC Type, select the desired type of cross-connection.

2WAYSNCP- Two-way SNCP cross-connection (bidirectional path-protected
cross-connection)
...................................................................................................................................................................................................
Under Revertive, nothing is to be specified. Revertive mode is not implemented in the

current release.
...................................................................................................................................................................................................
If the SNCP operates in revertive mode, then set the wait to revert timer under Revert
Delay Time.
Possible values are 0 to 15 minutes in steps of 1 minute. The default setting is 0.
The Revert Delay Time can be ignored if the SNCP operates in non-revertive mode.
...................................................................................................................................................................................................
Under Hold Off Time, set the hold-off timer for automatic protection switching.
0 to 80 ms in steps of 20 ms
100 to 10000 ms in steps of 100 ms
...................................................................................................................................................................................................
10
Under SubNetwork Protection Type, set the protection type of the SNCP.
The protection type of an ODU SNCP is:
SNC/N - SNCP with non-intrusive monitoring
SNC/I - Sub Network Connection protection with Inherent monitoring
....................................................................................................................................................................................................................................
1830 PSS
5-80
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
11
As an option, you can assign an identification to the cross-connection by entering a text

string of up to 45 ASCII characters into theCircuit ID field.
The following rules apply:
0 to 45 ASCII characters
The following characters are not allowed for the text string itself:
* (asterisk)
\ (backslash)
(double quote)
> (greater-than)
< (less-than)
; (semicolon)
Empty string is possible; this is also the default setting.
...................................................................................................................................................................................................
12
Continue with Step 15.

...................................................................................................................................................................................................
13
Under XC Type, select the desired type of cross-connection.

2WAY - Two-way cross-connection (bidirectional cross-connection)
...................................................................................................................................................................................................
14
As an option, you can assign an identification to the cross-connection by entering a text

string of up to 45 ASCII characters into the Circuit ID field.
The following rules apply:
0 to 45 ASCII characters
The following characters are not allowed for the text string itself:
* (asterisk)
\ (backslash)
(double quote)
> (greater-than)
< (less-than)
; (semicolon)
Empty string is possible; this is also the default setting.
...................................................................................................................................................................................................
15
....................................................................................................................................................................................................................................
1830 PSS
5-81
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
16

Result: A cross-connection is made between the selected ODU NIM and the ODU
pool, and automatically the ODU path termination is created.

E...................................................................................................................................................................................................
N D O F S T E P S
Manually create an ODU path termination

...................................................................................................................................................................................................
navigation tree underFacilities, and ODUPOOL.
As a result, the facility types ODU2T (terminated ODU2), ODU3T (terminated ODU3),
ODU3E2T (terminated ODU3E2), and ODU4T (terminated ODU4) become visible in
the navigation tree under ODUPOOL.
...................................................................................................................................................................................................
Select the desired facility type by clicking on it:

To create an ODU2 termination,
select ODU2T.
select ODU3T.
To create an ODU3E2 termination,
select ODU3E2T.
select ODU4T.
...................................................................................................................................................................................................
Right-click on the selected facility type (ODU2T, ODU3T, ODU3E2T, or ODU4T) in

the navigation pane, and select Assign ODUn from the context menu that opens.
In case of an ODU2T, select Assign ODU2.
In case of an ODU3E2T, select Assign ODU3E2.

Select the desired facility type (ODU2T, ODU3T, or ODU3E2T) in the navigation
pane, then select Assign ODUn from the Action menu.
In case of an ODU3E2T, select Assign ODU3E2.
....................................................................................................................................................................................................................................
1830 PSS
5-82
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: Depending on the selected facility type, a corresponding provisioning
window opens:
In case of an ODU2T, the Provision ODU2T Dialog window opens.
In case of an ODU3E2T, the Provision ODU3E2T Dialog window opens.
...................................................................................................................................................................................................
In the provisioning window, select the desired Payload Type.

Payload Type: This parameter indicates the type of payload being carried by the
ODUk. It is used to compare the incoming payload type with the expected type in
order to detect a Payload Mismatch condition. Furthermore, it is used to set the

payload indication (PT byte) in the transmit direction.
Depending on the setting of the Payload Type parameter, the embedded tributaries are
automatically created as follows:
ODUM (only applicable for ODU2 and ODU3):
ODUk multiplexed structure with 2.5G Tributary Slots for OTU2 and above rates.
ODUMPT21 (default payload type) :
ODUk multiplex structure with 1.25G Tributary Slots

Note: When multiplexing 4 ODU1 into ODU2 between OCS and WDM OT
11DPM12 use payload type ODUMPT21.
...................................................................................................................................................................................................

...................................................................................................................................................................................................

Result: The ODU path termination is created accordingly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-83
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to configure parameters of an ODU path termination.

Note: The parameters of an ODU path termination can be configured at the time when
the ODU path termination is created (see Procedure 5-12: Create an ODUn path
termination (p. 5-76)), or later on as a separate configuration action. The present
procedure describes the latter case, that is the configuration of an already existing
ODU path termination.
ED-ODUPTF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Choose one of the following options to find the desired ODU path termination:
1. Selection of ODU path termination from ODUPOOL:
As a result, the existing ODU path terminations become visible in the navigation tree
under ODUPOOL.
The existing ODU path terminations (ODU2T-, ODU3T-, ODU3E2T-,
ODU4T-) are grouped into ODU facility groups:
ODU2TLP- (ODU2T facility group), and
ODU3TLP- (ODU3T facility group).
....................................................................................................................................................................................................................................
1830 PSS
5-84
Issue 1 June 2013

....................................................................................................................................................................................................................................
ODU3E2TLP- (ODU3E2T facility group).

Select the ODU facility group that contains the ODU path termination you want to
configure. As a result, the ODU path terminations contained in the selected ODU
facility group are listed in the display pane.
2. Selection of an ODU path termination for transparently mapped client signals:
navigation tree underFacilities, and select the desired client signal rate.
Possible selections are:
GBE
GBE10
OC3
OC12
OC48
OC192
STM-1
STM-4
STM-16
STM-64
ODU path terminations for transparently mapped client signals can be identified by
means of their associated Name which becomes visible in the display pane when
expanding the selection tree underFacilities in the navigation pane.
The following ODU path terminations can be distinguished:
GBEODU0T - Gigabit Ethernet transparently mapped into ODU0.
GBE10ODU2T - 10 Gigabit Ethernet transparently mapped into ODU2.
OC3ODU0T - OC-3 Transparently mapped into ODU0.
OC12ODU0T - OC-12 Transparently mapped into ODU0.
OC48ODU1T - OC-48 transparently mapped into ODU1.
OC192ODU2T - OC-192 transparently mapped into ODU2.
STM1ODU0T - STM-1 Transparently mapped into ODU0.
STM4ODU0T - STM-4 Transparently mapped into ODU0.
STM64ODU2T - STM-64 transparently mapped into ODU2.
STM16ODU1T - STM-16 transparently mapped into ODU1.
....................................................................................................................................................................................................................................
1830 PSS
5-85
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the display pane of the Alcatel-Lucent 1830 PSS ZIC window, select the ODU path
termination (, ODU2T-, ODU3T-, ODU3E2T-, ODU4T-, GBEODU0T,
GBE10ODU2T, OC3ODU0T, OC12ODU0T, OC48ODU1T, OC192ODU2T,
STM1ODU0T, STM4ODU0T, STM16ODU1T, STM64ODU2T) you want to configure
by clicking on it.
Then choose one of the following options to open a relevant dialog box:
Right-click on the selected ODU path termination, and select Properties General
from the context menu that opens.
Result: The Properties - General window related to the selected ODU path
termination opens.
...................................................................................................................................................................................................
In the Properties - General window, you can change the type of payload by clicking in
the Payload Type field, and selecting the desired value.
Payload Type: This parameter indicates the type of payload being carried by the
ODUk. It is used to compare the incoming payload type with the expected type in
order to detect a Payload Mismatch condition. Furthermore, it is used to set the

payload indication (PT byte) in the transmit direction.
Depending on the setting of the Payload Type parameter, the embedded tributaries are
automatically created as follows:
ASCBR:
Asynchronous CBR mapping 10G WAN PHY/OC192/STM64/STM16
10.709Gb/s
Asynchronous CBR mapping in a ODU0
BSCBR:
Bit synchronous CBR mapping 10G WAN PHY/OC192/STM64/STM16

10.709Gb/s Transparent transport of GBE10 in a ODU2E
1000BASEX
Transparent GBE into ODU0 mapping
STM1OC3
STM-1/OC-3 mapping into ODU0
STM4OC12
STM-4/OC-12 mapping into ODU0
ODUM (not appicable for ODU1):
....................................................................................................................................................................................................................................
1830 PSS
5-86
Issue 1 June 2013

....................................................................................................................................................................................................................................
ODUMPT21
AMCC
AMCC mapping used for transparent GBE10 as defined in G.709
CAMCC
AMCC mapping used for transparent GBE10 for interworking with Cienna
equipment.
OLDAMCC
AMCC mapping used for GBE10 as defined in G.sup43; for backward

compatibility.
GFP
GFP mapping used for transparent transport of GBE10

Note: When multiplexing 4 ODU1 into ODU2 between OCS and WDM OT
11DPM12 use payload type ODUMPT21.
...................................................................................................................................................................................................
For GBE10ODU2 facilities, you can define the Type of client signal fail format and the
propagation of Client Signal Fail indicatinon in the Properties - General window
Reference: See General properties of an ODU path termination facilty (p. 5-509).
...................................................................................................................................................................................................
In the Trail Trace Identifier (TTI) column group of the Properties - General window,
you can provision trail trace identifier parameters.
To modify a parameter, click in the respective field, and either enter the desired value
directly, or select the desired value from a list of possible values.
...................................................................................................................................................................................................
In the Degraded Supervision column group of the Properties - General window, you
can provision error monitoring parameters.
To modify a parameter, click in the respective field, and either enter the desired value
directly, or select the desired value from a list of possible values.
The following error monitoring parameters are configurable:
Burst Interval
Burst Threshold
....................................................................................................................................................................................................................................
1830 PSS
5-87
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

Result: The ODU path termination is configured accordingly.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-88
Issue 1 June 2013

Procedure 5-14: Changing the payload type of an ODU path

termination
....................................................................................................................................................................................................................................

termination
When to use
Use this procedure to change the payload type of an ODU path termination.
ED-ODUPTF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
under ODUPOOL.
configure. As a result, the ODU path terminations contained in the selected ODU facility
group are listed in the display pane.
....................................................................................................................................................................................................................................
1830 PSS
5-89
Issue 1 June 2013


termination
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the display pane of the Alcatel-Lucent 1830 PSS ZIC window, select the ODU path
termination (ODU2T-, ODU3T-, ODU3E2T-) you want to modify by clicking on
it.
Right-click on the selected ODU path termination, and select Properties Convert
to PT20/PT21 from the context menu that opens.
In the Action menu, select Properties Convert to PT20/PT21.
Result: The Convert to PT20/PT21 Facilty window related to the selected ODU path
termination opens.
Additional info: termination substructure
PT20 (ODUM)
PT21 (ODUMPT21)

ODU payload structure of the ODUPTF entity Depending on the selected payload
type, the payload structure is build up as follows:
PLDTYPE=ODUM (PT20)
[T#PN-ts[-ts-ts-ts][&T#PN-ts[-ts-ts-ts]]]
PLDTYPE=ODUMPT21 (PT21)
T#PN-ts[-ts[-ts-ts-ts-ts-ts-ts]][&T#PN-ts[-ts[-ts-ts-ts-ts-ts-ts]]]]
where
PN is Port Number of the constituent
T is the constituent type with the following general allowed values: ODU0,
ODU1, ODU2, ODU2E, ODU3
"ts" is the Multi Stucture Identifier (MSI) slot number
The overall bandwidth of the specified constituents must exactly match the rate of the
port..
T=ODU1with one ts value (range 1..4) for ODU2 entity and PLDTYPE=ODUM
T=ODU0 with one ts value (range 1..8) for ODU2 entity and
PLDTYPE=ODUMPT21
T=ODU1with two ts values (range 1..8) for ODU2 entity and
PLDTYPE=ODUMPT21
T=ODU1 with one ts value (range 1..16) for ODU3 entity and PLDTYPE=ODUM
T=ODU2 with four ts values (range 1..16) for ODU3 entity and
PLDTYPE=ODUM
....................................................................................................................................................................................................................................
1830 PSS
5-90
Issue 1 June 2013


termination
....................................................................................................................................................................................................................................
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
T=ODU2 with eight ts values (range 1..32) for ODU3 entity and
PLDTYPE=ODUMPT21
T=ODU2E with nine ts values (range 1..32) for ODU3 entity and
PLDTYPE=ODUMPT21
T=ODU0 with one ts value (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU1with two ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU2 with eight ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU2E with eight ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU3 with thirty two ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
T=ODU1 with two ts values (range 1..80) for ODU4 entity and
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
T=ODU2E with eight ts values (range 1..80) for ODU4 entity and
PLDTYPE=ODUMPT21
T=ODU3 with thirty one ts values (range 1..80) for ODU4 entity and
PLDTYPE=ODUMPT21
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-91
Issue 1 June 2013

Procedure 5-15: Changing the sub-structure of an ODU path

termination
....................................................................................................................................................................................................................................

termination
When to use
Use this procedure to change the path termination substructure of an ODU path
termination.
ED-ODUPTF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
navigation tree under Facilities, and ODUPOOL.
As a result, the existing ODU facility types become visible in the navigation tree under
ODUPOOL.
Expand the ODU facility type that contains the ODU facility group you want to
configure.
Expand the ODU facility group that contains the ODU path termination you want to
configure.
....................................................................................................................................................................................................................................
1830 PSS
5-92
Issue 1 June 2013


termination
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the navigation pane of the Alcatel-Lucent 1830 PSS ZIC window select the desired
ODU path termination. As a result, the lower order ODUs contained in the selected ODU
path termination are listed in the display pane.
...................................................................................................................................................................................................
In the display pane of the Alcatel-Lucent 1830 PSS ZIC window, select the lower order
ODU you want to modify by clicking on it.
Right-click on the selected ODU path termination, and select Assign ODU<y> from
In the Action menu, select Assign ODU<y>.
Result: The Provision ODU<x> Dialog related to the selected ODU path termination
opens.
...................................................................................................................................................................................................
Using the field Payload Type select the Payload Type to be used.
ODU payload structure of the ODUPTF entity Depending on the selected payload
type, the payload structure is can be build up as follows:
PLDTYPE=ODUM (PT20)
[T#PN-ts[-ts-ts-ts][&T#PN-ts[-ts-ts-ts]]]
PLDTYPE=ODUMPT21 (PT21)
T#PN-ts[-ts[-ts-ts-ts-ts-ts-ts]][&T#PN-ts[-ts[-ts-ts-ts-ts-ts-ts]]]]
where
PN is Port Number of the constituent
T is the constituent type with the following general allowed values: ODU0,
ODU1, ODU2, ODU2E, ODU3
"ts" is the Multi Stucture Identifier (MSI) slot number
The overall bandwidth of the specified constituents must exactly match the rate of the
port..
T=ODU1with one ts value (range 1..4) for ODU2 entity and PLDTYPE=ODUM
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
T=ODU1 with one ts value (range 1..16) for ODU3 entity and PLDTYPE=ODUM
T=ODU2 with four ts values (range 1..16) for ODU3 entity and
PLDTYPE=ODUM
....................................................................................................................................................................................................................................
1830 PSS
5-93
Issue 1 June 2013


termination
....................................................................................................................................................................................................................................
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
T=ODU2E with nine ts values (range 1..32) for ODU3 entity and
PLDTYPE=ODUMPT21
T=ODU0 with one ts value (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU1with two ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU2 with eight ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU2E with eight ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
T=ODU3 with thirty two ts values (range 1..32) for ODU3E2 entity and
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
T=ODU1 with two ts values (range 1..80) for ODU4 entity and
PLDTYPE=ODUMPT21
PLDTYPE=ODUMPT21
T=ODU2E with eight ts values (range 1..80) for ODU4 entity and
PLDTYPE=ODUMPT21
T=ODU3 with thirty one ts values (range 1..80) for ODU4 entity and
PLDTYPE=ODUMPT21
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-94
Issue 1 June 2013

Procedure 5-16: Deprovision an ODUk path termination

function
....................................................................................................................................................................................................................................

function
When to use
Use this procedure to deprovision (delete) an ODUk path termination.

Note: The present procedure is valid for ODUk path terminations which previously
had been created manually, and - as a consequence - have a secondary state (SST) of
MDLT; see also Manually create an ODU path termination (p. 5-82).
DLT-ODUPTF
RMV-ODUPTF
Before you begin

Important! Be sure that no cross-connections exist for the ODU path termination to
be deleted.
Required equipment
Instructions
...................................................................................................................................................................................................
under ODUPOOL.
....................................................................................................................................................................................................................................
1830 PSS
5-95
Issue 1 June 2013


function
....................................................................................................................................................................................................................................

delete. As a result, the ODU path terminations contained in the selected ODU facility
group are listed in the display pane.
...................................................................................................................................................................................................
Choose one of the following options:
Right-click on the selected ODU path termination, and select Unassign from the
context menu that opens.
In the Action menu, select Unassign.
Result: A confirmation window opens with the message:
The selected Facility (ies) will be unassigned. Do you wish
to continue? Yes/No
...................................................................................................................................................................................................
Click Yes to delete the ODU path termination.

Result: The ODU path termination will be deleted.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-96
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to configure parameters of an optical SDH/SONET port.

Note: The parameters of an optical SDH/SONET port can be configured at the time
when the port is created, or later on as a separate configuration action.
Currently only autoprovisioning is used, facilities are always autoprovisioned with
default parameters when the underlying equipment is entered.
The present procedure describes the latter case, that is the configuration of an already
existing optical SDH/SONET port.
ED-STM1
ED-STM4
ED-STM16
ED-STM64
ED-OC3
ED-OC12
ED-OC48
ED-OC192
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
navigation tree underFacilities, and select the desired optical SDH/SONET port.
....................................................................................................................................................................................................................................
1830 PSS
5-97
Issue 1 June 2013

....................................................................................................................................................................................................................................
The navigation tree under Facilities is hierarchically structured according to the

facility type, the facility groups, and the associated ports. The following figure
illustrates this structure using an OC-192 facility as an example.
Figure 5-4 Example for the representation of facilities
Facility type
Facility group
Port
...................................................................................................................................................................................................
In the navigation pane, right-click on the optical SDH/SONET port, and select
Properties General from the context menu that opens.
In the navigation pane, click on the optical SDH/SONET port, and select Action
Result:
configuration parameters of the selected optical SDH/SONET port.

Reference: See General properties of an optical SDH/SONET port (p. 5-484).
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-98
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to configure parameters of an optical GBE/GBE10 port.

Note: The parameters of an optical GBE/GBE10 port can be configured at the time
when the port is created, or later on as a separate configuration action. The present
procedure describes the latter case, that is the configuration of an already existing
optical GBE/GBE10 port.
ED-GBE
ED-/GBE10
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
navigation tree under Facilities, and select the desired optical GBE/GBE10 port.
....................................................................................................................................................................................................................................
1830 PSS
5-99
Issue 1 June 2013

....................................................................................................................................................................................................................................

illustrates this structure using an OC-192 facility as an example.
Facility type
Facility group
Port
...................................................................................................................................................................................................
In the navigation pane, right-click on the optical GBE/GBE10 port, and select
Properties General from the context menu that opens.
In the navigation pane, click on the optical GBE/GBE10 port, and select Action
Result:
configuration parameters of the selected GBE/GBE10 port.

Reference: See General properties of a GBE / GBE10 port (p. 5-501).
...................................................................................................................................................................................................

...................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-100
Issue 1 June 2013

Procedure 5-19: Provision a Tandem Connection Monitoring

(TCM) entity
....................................................................................................................................................................................................................................

(TCM) entity
When to use
Use this procedure to provision a Tandem Connection Monitoring (TCM) entity.

Tandem Connection Monitoring (TCM)
Alcatel-Lucent 1830 PSS, Release 6.0.0, supports TCM for the following signal rates:
ODU0
ODU1
ODU2
ODU2e
ODU3
ODU3e2
ODU4
The system supports provisioning 3 levels of TCM freely to one of the 6 levels defined by
G.709.
The following figures show examples of the TCM monitor points.
Figure 5-6 Examples (1 of 4)
HO ODU TCM HO ODU TCM
(position A)
(position B)
ODU path
NIM - ingress
HO ODU TCM
(position A)
Matrix
OTU
ODU path
NIM - egress
....................................................................................................................................................................................................................................
1830 PSS
5-101
Issue 1 June 2013


(TCM) entity
....................................................................................................................................................................................................................................

HO ODU TCM HO ODU TCM
(position A)
(position B)
ODU path HO ODU TCM

NIM - ingress (position X)
HO ODU
PTF
Matrix
OTU

LO ODU TCM LO ODU TCM
(position A)
(position B)
ODU path
NIM - ingress
LO ODU TCM
(position A)
Matrix
HO ODU
PTF
ODU path
NIM - egress

OTU
PFT
ODU TCM
(position A)
Matrix
Transparent
Payload;
STMn, OCn,
GBE[10]
The first example shows the possible monitoring points for an un-terminated ODUk, with
two monitoring points directed towards the interface and one monitoring point directed
towards the matrix. In addition, it also shows ODUk Path NIM monitoring, monitoring
both Ingress and Egress direction and OTU termination The second example shows the
possible monitoring points for a terminated ODUk with all three directed towards the
interface. The third example shows the TCM monitoring points for the LO ODU NIM,
and the fourth example shows the TCM monitoring points for transparent non-OTN
clients.
Note: The TCM monitoring points can either be unused (not provisioned) or can be
provisioned as a non-intrusive monitoring (NIM) point or as a TCM termination.
....................................................................................................................................................................................................................................
1830 PSS
5-102
Issue 1 June 2013


(TCM) entity
....................................................................................................................................................................................................................................
The following sub-characteristics of the TCM monitoring method are selectable based on
ODUk TCM non-intrusive monitoring:
the TCM sublayer (1,...,6)

Note that, 1830 PSS-64/36 provides access to 3 out of 6 levels of TCM, freely
selectable. This applies to all HO ODUk and all LO ODUk. Alcatel-Lucent 1830 PSS
is hardware ready to support all levels of TCM.
the position of the TCM non-intrusive monitoring (NIM) point. Note that only
position A or B can be selected; see also the examples above.
1+1 ODUk SNC/N based on TCM NIM
A 1+1 ODUk SNC/N based on TCM NIM protects against defects in the server layer of
the ODUk and against continuity, connectivity, and error degradation defects in the
selected ODUk TCM sublayer itself. Protection switching is triggered by a non-intrusive
monitoring of the ODUk TCM sub-layers at the tail end of the protected domain.
These are the characteristics of a 1+1 ODUk SNC/N based on TCM NIM:
One out of the six available TCM sublayers can be selected for the non-intrusive
monitoring
Unidirectional switching without APS protocol

Non-revertive switching
Revertive switching
Unidirectional and bidirectional transmission (connections)
ENT-TCM
ED-TCM
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
5-103
Issue 1 June 2013


(TCM) entity
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
OTU2, OTU3, OTU3E2 or OTU4 port in the navigation tree under Facilities.
As a result, the unterminated ODU2 (ODU2 NIM), unterminated ODU3 (ODU3
NIM), unterminated ODU3E2 (ODU3E2 NIM) or unterminated ODU4 (ODU4 NIM)
is displayed in the display pane. The following figure illustrates this using an ODU3
NIM as an example.
Figure 5-7 Example for the representation of an ODU3 NIM
ODU3 NIM
g-upg-0060
...................................................................................................................................................................................................
Select the facility by clicking on it in the display pane.

Result: The facility is highlighted.
...................................................................................................................................................................................................
In the navigation pane, right-click on the facility, and select Assign TCM from the
In the navigation pane, click on the faciltity, and select Action Assign TCM from
the main menu bar.
Result: The Provision TCM Dialog window opens.
...................................................................................................................................................................................................
Under Level, set the TCM level of the newly created entity.
Possible values are
....................................................................................................................................................................................................................................
1830 PSS
5-104
Issue 1 June 2013


(TCM) entity
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Under Position, define the position of the TCM monitor

Possible values are
AM
After Matrix
BM
Before Matrix
...................................................................................................................................................................................................
Under Role, define the expected TCM termination type.

Possible values are
TCT
for TCM termination.
TCN
for TCM NIM

...................................................................................................................................................................................................
Under Relative Position, define the relative position of the TCM monitor point.
The lower the position sequence, the closer the TCM monitor point to the client/matirix.
This means that the consequent action of the lower numbered position sequence TCM
monitor point affects the higher numbered position sequence TCM monitor point
Possible values are
...................................................................................................................................................................................................
Under Overhead Add, define if the provisioned TCM Overhead is to inserted or not.
Possible values are
Yes
No
...................................................................................................................................................................................................
Under Overhead Remove, define if the received TCM Overhead is discarded or not
Possible values are
Yes
No
....................................................................................................................................................................................................................................
1830 PSS
5-105
Issue 1 June 2013


(TCM) entity
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10
Click Apply.
Result: The Properties - General - TCM window opens.
Reference: See Properties of a Tandem Connection Monitoring (TCM) entity
(p. 5-520).
...................................................................................................................................................................................................
11
Define the respective parameter settings.

...................................................................................................................................................................................................
12

...................................................................................................................................................................................................
13
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-106
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to take a facility out of service for maintenance purposes.
RMV-GBE
RMV-GBE10
RMV-OC3
RMV-OC12
RMV-OC48
RMV-OC192
RMV-ODU0
RMV-ODU1
RMV-ODU2
RMV-ODU2E
RMV-ODU3
RMV-ODU3E2
RMV-ODU4
RMV-ODUPTF
RMV-OTU
RMV-TCM
RMV-STM1
RMV-STM4
RMV-STM16
RMV-STM64
Before you begin

Required privileges
....................................................................................................................................................................................................................................
1830 PSS
5-107
Issue 1 June 2013

....................................................................................................................................................................................................................................
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC navigation pane, expand the selection tree under
Facilities to select the desired facility.
Note: Some facilities are only available via display pane.
...................................................................................................................................................................................................
Then select Service State Remove, either by selecting Action from the main menu
Result: The Remove dialogue box is displayed.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-108
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to bring a facility back into service.

RST-GBE
RST-GBE10
RST-OC3
RST-OC12
RST-OC48
RST-OC192
RST-ODU0
RST-ODU1
RST-ODU2
RST-ODU2E
RST-ODU3
RST-ODU3E2
RST-ODU4
RST-ODUPTF
RST-OTU
RST-TCM
RST-STM1
RST-STM4
RST-STM16
RST-STM64
Before you begin

Required privileges
....................................................................................................................................................................................................................................
1830 PSS
5-109
Issue 1 June 2013

....................................................................................................................................................................................................................................
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC navigation pane, expand the selection tree
underFacilities to select the desired facility.
Note: Some facilities are only available via display pane.
...................................................................................................................................................................................................
Then select Service State Restore, either by selecting Action from the main menu bar
Result: The Restore dialogue box is displayed.
...................................................................................................................................................................................................
Click Apply.
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-110
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to enable autonomous or manual equipment protection switching for
agnostic matrix cards.
At first trouble-shoot an INT-ERR alarm. If necessary, perform a forced switch to the
MTX card that has not such an alarm. It is strongly recommended that INT-ERR alarms
must be repaired before removing or rebooting MTXes.
Note: The procedure applies to the following card types:
MT3T8 (Matrix cards in MTX slots in PSS-64 shelves)

MT1T9C (Matrix cards in MTX slots in PSS-36 shelves)
MT960C (Matrix cards in MTX slots in PSS-36 shelves)
ALW-SWDX-EQPT
INH-SWDX-EQPT
RTRV-DX-EQPT
SW-DX-EQPT
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
5-111
Issue 1 June 2013

....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the agnostic matrix card for
which you want to enable autonomous or manual equipment protection switching via
Equipment Rack 1 Shelf 0x:PSSxx
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-112
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to inhibit autonomous or manual equipment protection switching for
agnostic matrix cards.
MTX card that has not such an alarm. It is strongly recommended that INT-ERR
alarms must be repaired before removing or rebooting MTXes.
Note: The procedure applies to the following card types:

ALW-SWDX-EQPT
INH-SWDX-EQPT
RTRV-DX-EQPT
SW-DX-EQPT
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
5-113
Issue 1 June 2013

....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the agnostic matrix card for
which you want to inhibit autonomous or manual equipment protection switching via
Equipment Rack 1 Shelf 0x:PSSxx.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Yes.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-114
Issue 1 June 2013

Procedure 5-24: Initiate an equipment protection switch

manually
....................................................................................................................................................................................................................................

manually
When to use
Use this procedure to initiate an equipment protection switch manually.

You can perform this for the following 1:1 protected modules:
ECHC (Controller cards in FLC slots of PSS-64 shelves)

FLC36EA (Controller cards in FLC slots in PSS-36 shelves)

MTX card that has not such an alarm. It is strongly recommended that INT-ERR
alarms must be repaired before removing or rebooting MTXes.
ALW-SWDX-EQPT
INH-SWDX-EQPT
RTRV-DX-EQPT
SW-DX-EQPT
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
5-115
Issue 1 June 2013


manually
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the part of equipment for which
you want to perform the switch via Equipment Rack 1 Shelf (1 ... 31)
...................................................................................................................................................................................................
Then select Switching Switch, either by selecting Action from the main menu bar or
Result: The Switch Duplex dialogue box is displayed.
...................................................................................................................................................................................................
Under Command Mode you can choose between NORM and FORCED (not applicable to
the FLC equipment protection group.)).
...................................................................................................................................................................................................
Click Switch.
...................................................................................................................................................................................................
Click Yes.
Result: Now an equipment protection switch from the currently active unit to the
standby unit takes place. As a result, the formerly standby unit becomes active, and
the formerly active unit becomes standby.
Important! If you perform a manual equipment protection switch for FLCs, the
Alcatel-Lucent 1830 PSS ZIC will exit, and you will have to re-launch it once the
equipment protection switch is complete.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-116
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to initiate a circuit pack reset.

MTX card that has not such an alarm. It is strongly recommended that INT-ERR alarms
must be repaired before removing or rebooting MTXes.
INIT-SYS
Before you begin

Attention: Never reset the active FLC or active matrix card. First perform a manual
switch and then reset the FLC or matrix card that has the standby role after the manual
switch. See Procedure 5-24: Initiate an equipment protection switch manually
(p. 5-115).
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select Equipment Rack 1 Shelf
(1 ... 31). Then select the board or circuit pack, for which you want to initiate a circuit
pack reset .
Then select Initialize Board, either by selecting Action from the main menu bar or by
....................................................................................................................................................................................................................................
1830 PSS
5-117
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Initialize Board window opens.
A circuit pack reset can be applied to the following circuit packs:
First Level Controllers:

ECHC (FLC) - First Level Controller for PSS-64
FLC36EA - First Level Controller for PSS-36
Matrix cards:
MT3T8 - Matrix card for PSS-64, with a switching capacity of 3.84 Tb/s
MT1T9 - Matrix card for PSS-64, with a switching capacity of 1.92 Tb/s
MT1T9C - Matrix card for PSS-36, with a switching capacity of 1.92 Tb/s
MT960C - Matrix card for PSS-36, with a switching capacity of 960 Gb/s
I/O cards:
2 40G ANY Port Unit (2XANY40G)
4 10G ANY Card (4XANY10G)
10 10G ANY Port Unit (10XANY10G)

10 10 GbE / XFP Port Unit (10XETH10G)
10 OTU2 / XFP Port Unit (10XOTH10G)
24 Multirate ANY Port Unit (24XANYMR)

8 1 GbE Card (8XETH1G)
24 1 GbE / SFP Port Unit (24XETH1G)
1 43G Switchponder card (43SCUP)
10x 10G Synchronous Transport Hierarchy Card (10XSTH10G)

24x Multirate Synchronous Transport Hierarchy Card (24XSTHMR)
24x Multirate ANY Card Version B (24XANYMRB)
24x 1 GBE Card Version B (24XETH1GB)
8x 1 GBE Card Version B (8XETH1GB)

4 11G Switchponder card (11QCUP)
4 x 11G Switchponder (11QCUPC)

1 x 43G Switchponder (43SCUP)
1x 130G Switchponder Card (130SCUP)
1x 100G Test Board (112CFPTB)
...................................................................................................................................................................................................
Under Phase specify the type of restart.
....................................................................................................................................................................................................................................
1830 PSS
5-118
Issue 1 June 2013

....................................................................................................................................................................................................................................
Types of restart The following types of restart are defined:
APPL (application restart)
The card restarts its application processes.
The operating system keeps running.

No equipment protection switch is performed.
WARM (soft reset, software reboot)
The card restarts its application processes.
The card restarts its operating system.

The card restarts its CPU and devices that are important for inter-processor
communication.
If applied to active cards that are involved in an equipment protection, an implicit
equipment protection switch will happen.
COLD (hardware reset, power cycle)
The Card gets power cycled. All FPGAs of the card are pumped again. For the
First-level Controller (FLC), this implies a file system repair action. If applied to
active cards that are involved in an equipment protection, then an implicit
equipment protection switch will happen.
Table 5-7
Applicability of restart types to circuit packs
Circuit pack
Type of restart
Matrix card
APPL, WARM, COLD
First-level Controller
(FLC)
APPL, WARM, COLD

Exception:
Application reset commands to the active FLC cause an unexpected

switch to the standby FLC .
The standby FLC gets active. If the formerly active FLC shall get
active again, a manual equipment protection switch has to be
performed
I/O cards
COLD
Exception:
All uplink cards (11QCUPC, 43SCUP, 130SCUP) also supports a

WARM restart!
...................................................................................................................................................................................................
Define the Command Execution Mode using the respective radio button:
Forced
Normal
....................................................................................................................................................................................................................................
1830 PSS
5-119
Issue 1 June 2013

....................................................................................................................................................................................................................................
Additional info For the active matrix card or the active FLC, and if the Phase
parameter is set to any value other than APPL, the Command Execution Mode must
be set to Forced.
...................................................................................................................................................................................................
Click Apply.
...................................................................................................................................................................................................
Click OK in the confirmation window.

E...................................................................................................................................................................................................
N D O F S T E P S
Monitor the status of an equipment protection group
After an equipment protection switch or a reset of a card that is involved in an equipment

protection group, you should wait until the alignment process between both cards of the
equipment protection group has been completed. For that purpose, you should monitor the
status of the equipment protection group during the alignment process.
To monitor the status of an equipment protection group, you can chose one of the
following options:
1. Use the TL1 interface:
Apply the RTRV-DX-EQPT TL1 command to one of the cards involved in the
equipment protection group.
In the command response, the status of the equipment protection group is
indicated by means of the GROUPSTATE parameter.
Also refer to the Alcatel-Lucent 1830 PSS TL1 Command Guide.
2. Use the graphical user interface of the Alcatel-Lucent 1830 PSS ZIC:
From the Alcatel-Lucent 1830 PSS ZIC selection tree, select the shelf, then select
one of the cards involved in the equipment protection group in the Contents tab or
Graphical View tab.
Right-click on the selected card, and select Switching View from the context
menu that opens. The View Duplex Switching Equipments window opens.
In the View Duplex Switching Equipments window, read the status of the
equipment protection group from the Group State column.
....................................................................................................................................................................................................................................
1830 PSS
5-120
Issue 1 June 2013

....................................................................................................................................................................................................................................
The alignment process typically takes approximately 10 minutes, and the sequence of
status indications is as follows:
During the alignment process, the group state is ALIGNING, that is the protection
group prepares the inactive module for the standby role.
After the alignment process has finished, the group state can take on one of the
following values:
NOREQ - No switch request active on the protection group.
DEGRADED - Protection group in degraded state.
FAILURE - Protection group in failure state.
NORED - The redundant equipment module is not available.
Important! If the alignment between the FLCs of an FLC equipment protection

group is unsuccessful for any reasons, then this unsuccessful alignment is not
alarmed. Instead, the alignment process does not finish, and the second FLC card
remains in the group state ALIGNING. If the group state is in the ALIGNING state for
more than one hour, we recommend that you apply a reset to the inactive FLC in order
to restart the alignment process.
Visual indication of group states other than No Request (NOREQ)
When the group state of an equipment protection group has any value other than No
Request (NOREQ), then the cards pertaining to that equipment protection group are
highlighted with a light red background in the display pane of the Alcatel-Lucent
1830 PSS ZIC under Contents. This is illustrated in the following figure using the matrix
cards and FLCs in a PSS-36 shelf as an example.
The exact group state can then be retrieved as described above.
....................................................................................................................................................................................................................................
1830 PSS
5-121
Issue 1 June 2013

....................................................................................................................................................................................................................................
Figure 5-8 Example for highlighted cards in the display pane of the Alcatel-Lucent
1830 PSS ZIC
....................................................................................................................................................................................................................................
1830 PSS
5-122
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
Provisioning is the process of assigning values to parameters that determine the operating
characteristics of the system. The values of the provisioned parameters determine how
you interface with an NE and how the NE functions with various installed entities. Each
provisionable parameter has a factory-supplied original value when software is first
loaded onto an NE. These values become the current value upon launching the software
and are the values used by the system. All provisioned parameters and values are
preserved in the systems non-volatile memory and are protected and can be retrieved on
demand or restored upon recovering from power failure. Copies of these parameter
settings can also be used by other identical NEs.
User access to Equipment Management functions is available via all supported user
interfaces. Therefore, all externally user provisionable parameters can be set using the
WebUI, TL1, CLI, or EMS (1354 RM-PhM). Autonomous notifications are generated for
the following equipment-related events:
physical removal/insertion
failure/recovery
warm/cold restart
primary/secondary state changes
logical removal/restoration
provisioning creation/deletion/changes
Contents
5-125
System Properties
5-126
5-129
Reboot Options
5-130
5-131
Firmware
5-134
5-135
Firmware
5-136
Shelf provisioning
5-137
....................................................................................................................................................................................................................................
1830 PSS
5-123
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
5-142
Create Shelf
5-143
5-146
Shelf Properties
5-147
5-151
5-152
Shelf LEDs
5-153
5-154
5-175
Provision Card
5-176
5-177
5-178
Card Inventory
5-179
5-180
5-181
5-182
5-184
Procedure 5-39: Upgrade EC (in-service upgrade from simplex to duplex)
5-185
5-186
5-187
5-188
Delete Card
5-189
5-190
5-402
....................................................................................................................................................................................................................................
1830 PSS
5-124
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view or modify NE parameters

Before you begin
Instructions
...................................................................................................................................................................................................
Login to the NE and using the WebUI, select System from the equipment tree. Select the
Provision/Info function.
Result: System properties are displayed under the Details tab.
...................................................................................................................................................................................................
View or modify the System Properties fields as necessary.

Note: If the Loopback IP Address is changed, a warning message is displayed
indicating that a reboot will occur. The user can continue or cancel the request.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-125
Issue 1 June 2013

System Properties
....................................................................................................................................................................................................................................
System Properties
Attribute
Value/Format
Additional Info
<1-20 chars>
User-specified name of the

network element.
Network Element Type
Type of 1830 network

element.
Description
<0-255 chars>
User-specified description of
the network element.
Software Release
<0-20 chars>
Network element software

release number.
Loopback IP
<IP address>
IP address for the network

element.
Loopback Subnet Mask
<IP address>
IP address mask for the

network element.
For nodes that are in the same
subnetwork, each node must
have Loopback Subnet Mask
set to 255.255.255.255.
OCS IP
<IP address>
OSPF Area Index (GCC/OSC

Interfaces)
{0-3}
OSPF area index for all GCC

and OSC ports on the network
element.
OSPF Area ID (GCC/OSC

Interfaces)
<IP address>
OSPF area for all GCC and

OSC ports on the network
element.
....................................................................................................................................................................................................................................
1830 PSS
5-126
Issue 1 June 2013

System Properties
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
SNMP Source
Any IP interface
The source of SNMP traps

and reply messages.
Loopback IP only
Any IP interfaceindicates that
SNMP requests can be made

using any of the NEs
interface IP addresses or
Loopback IP address. The
source IP address in SNMP
trap/reply messages shall be
the interface IP address on
which the packet leaves the
NE. It is the SNMP clients
responsibility to be able to
associate an NE with multiple
IP addresses.
Loopback IP Only indicates
that SNMP requests can be

made using ONLY the NEs
Loopback IP address. The
source IP address in SNMP
trap/reply messages shall be
fixed as the Loopback IP.
SNMP clients need only have
a single association to the
NEs Loopback IP address.
ETR Validation Enabled
(checkbox)
Specifies if the network

element should validate that
all hardware is temperature
hardened. 1830 PSS-4 only.
UI Mode
Normal (default)
Indicates the security setting

for the network element.
Encrypted
NOTE: UI Mode cannot be

changed at the same time as
Loopback IP, Loopback
Subnet Mask and/or SNMP
Source fields.
....................................................................................................................................................................................................................................
1830 PSS
5-127
Issue 1 June 2013

System Properties
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
TL1 Autonomous Messages

Enabled
(checkbox)
Enables and disables TL1

autonomous messages. When
disabled (unchecked), only
request/response commands
are supported on the TL1
interface.
AINS Timer
<Hours-Minutes,
Default timer value used on

all ports that support
automatic in-service mode
(AINS). Specifies the amount
of time that a valid signal
must be detected on a port
before that port becomes
automatically in service.
max value = 96-00>
Temperature Units
Celsius
Fahrenheit
EC Programmed Capacity
Unknown
4G
16G
SONET/SDH Mode
Specifies the units when

displaying temperatures.
The expected capacity (in
Gigabytes) of the
flash-memory associated with
a controller card.
SONET
SDH
....................................................................................................................................................................................................................................
1830 PSS
5-128
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to reboot the NE.

The user can request a manual reboot of the entire NE which reboots all applicable circuit
packs. Both warm and cold restarts are supported. For a cold restart, the WebUI displays a
warning indicating that service may be affected. The user is allowed to continue with the
request or cancel. (USRPNL, FAN, PF, SFC, SFD, ITLB, ITLU, and DCM have no
processors and cannot be restarted.)
Before you begin
Instructions
...................................................................................................................................................................................................
Select System from the equipment tree and select the Reboot tab.
Result: The Reboot Options screen is displayed.
...................................................................................................................................................................................................
Select either Warm Reboot or Cold Reboot and click Submit.

Note: Cold restart of a transmission-carrying pack kills traffic, and thus cold restart is
not allowed on an in-service pack. The pack must either be in maintenance state or
out-of-service as described below:
1. Put the pack (and ports) into maintenance state before performing the cold restart.
In maintenance state the cross connects can remain in place, and transmission is
still carried.
2. Perform a cold restart of the entire NE, instead of pack-by-pack. The TL1
command "INIT-SYS" allows this without individually changing all pack/port
admin states in the system -- if the user specifies the "forced" option. The CLI
command "config admin resetne" offers an equivalent to this "forced" option.
Note: When a pack warm reboots or is cold rebooted the PM data is not available.
Similarly, pack related alarms cannot be retrieved.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-129
Issue 1 June 2013

Reboot Options
....................................................................................................................................................................................................................................
Reboot Options
Attribute
Additional Info
Warm Reboot
A warm reboot reinitializes the network

element software only and is not service
affecting.
Cold Reboot
A cold reboot reinitializes the network element

hardware and software and is service affecting.
....................................................................................................................................................................................................................................
1830 PSS
5-130
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to configure the firmware.

Before you begin
Instructions
...................................................................................................................................................................................................
Select the card from the equipment tree and click the Firmware tab.
...................................................................................................................................................................................................
Select desired Provisioned Release from the picklist.

Additional information: To support modification of the provisioned release, the
WebUI displays a picklist of valid values for the card type. For each card type, there is
a default firmware version.
The WebUI supports configuring firmware for the following card types:
4DPA2,
4DPA4,
11DPE12,
11DPE12A,
11DPE12E,
11DPM12,
11QPA4,
11QPE24,
11QPEN4,
11STAR1,
11STAR1A,
11STGE12,
11STMM10,
130SCX10,
43SCGE1,
43SCA1,
43SCX4,
43SCX4E,
....................................................................................................................................................................................................................................
1830 PSS
5-131
Issue 1 June 2013

....................................................................................................................................................................................................................................
43STA1P,
43STX4,
43STX4P,
112PDM11
112SCA1,
112SCX10,
112SNA1,
112SNX10,
A2325A,
A2P2125,
AHPHG,
AHPLG,
ALPHG,
AM2125A,
AM2125B,
AM2318A
CWR8,
CWR8-88,
MESH4,
MVAC,
MVAC8B,
OPSA,
OPSB,
OSCT,
PTPCTL
PTPIO
RA2P,
SVAC,
WR2-88,
WR8-88A,
WR8-88AF
WTOCM,
WTOCMA.
....................................................................................................................................................................................................................................
1830 PSS
5-132
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-133
Issue 1 June 2013

Firmware
....................................................................................................................................................................................................................................
Firmware
Attribute
Value/Format
Additional Info
Provisioned Release
<32 chars>
User-selected firmware
release.
--default--" indicates the
default firmware release for
the current software release.
NOTE: The firmware
upgrade will take effect after
the card is cold rebooted.
Provisioned On
<date/time>
Date/time when the

Provisioned firmware release
was configured.
Active Release
<64 chars>
Currently active firmware

release.
Activated On
<date/time>
Date/time when active

firmware release was loaded.
Load State
None
Status of the firmware load.

The Init states indicate that
the load is in progress.
Loaded
Failed
Timeout
Init[1-10]
Elapsed Time
<MM:SS>
Time since firmware load was

initiated. Only applicable
when the LoadState is Init
[1-10], that is, the load is in
progress.
....................................................................................................................................................................................................................................
1830 PSS
5-134
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view the firmware.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Reports > Firmware.

Result: The Firmware report window is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-135
Issue 1 June 2013

Firmware
....................................................................................................................................................................................................................................
Firmware
Attribute
Value/Format
Additional Info
Location
<shelf/slot>
Shelf and slot of the card.
Card Type
<Type of card present in the

specified location>
Provisioned Release
<32 chars>
User-selected firmware
release.
--default--" indicates the
default firmware release for
the current software release.
Provisioned On
<date/time>
Date/time when the

Provisioned firmware release
was configured.
Active Release
<64 chars>
Currently active firmware

release.
Activated On
<date/time>
Date/time when active

firmware release was loaded.
LoadState
None
Status of the firmware load.

The Init states indicate that
the load is in progress.
Loaded
Failed
Timeout
Init[1-10]
Elapsed Time
<MM:SS>
Time since firmware load was

initiated. Only applicable
when the LoadState is Init
[1-10], that is the load is in
progress.
....................................................................................................................................................................................................................................
1830 PSS
5-136
Issue 1 June 2013

Shelf provisioning
....................................................................................................................................................................................................................................
Shelf provisioning
Overview
The 1830 PSS supports the following shelf types: PSS-32 universal shelf, PSS-16
universal shelf, DCM shelf, SFD40 shelf, SFD40B shelf, SFD44 shelf, SFD44B shelf,
ITLB shelf and ITLU shelf. The DCM, SFD44, SFD44B, ITLB and ITLU shelves are all
passive module shelves.
Table 5-8, 1830 PSS Shelf Combinations (p. 5-137) lists the combinations of PSS-32,
PSS-32S, and PSS-16 shelves that are supported in a single NE.
Table 5-8
1830 PSS Shelf Combinations
Main Shelf Type
PSS-16
Subtending
Universal Shelf
Type
Number of
Subtending
Universal Shelves
Non-Universal
Shelf Types
PSS-16
0 to 7 PSS-16 shelves
DCM
PSS-32
0 to 23 PSS-32
shelves
ITLB, ITLU
Maximum 23
combined
PSS-32
SFD40, SFD40B,
SFD44, SFD44B
PSS-16
0 to 8 PSS-16 shelves
DCM
PSS-32
0 to 23 PSS-32
shelves
ITLB, ITLU
PSS-32S
0 to 1 PSS-32S
shelves
SFD40, SFD40B,
SFD44, SFD44B
Maximum 23
combined
Important! Alcatel-Lucent 1830 PSS requires that filler blanks be used in all un-used
slots in a shelf to ensure proper airflow and cooling.
PSS shelf
Rotary dial backplane setting
On each PSS shelf, a shelf ID number and a shelf role can be set via a physical
mechanism (rotary dial) on the backplane. Up to 8 bits of information can be set. The
rotary dial for each shelf must be set to a valid value, and the value must be unique within
the same NE.
The values of the rotary dial are interpreted as follows:
Bits 4-3-2-1-0 code the shelf ID number, an integer in the range 1-24.
....................................................................................................................................................................................................................................
1830 PSS
5-137
Issue 1 June 2013

Shelf provisioning
....................................................................................................................................................................................................................................
Bit 7 (the most significant bit), codes the shelf role according to the following rule:
Bit 7 = zero: Shelf Role = Not-Main Shelf
Bit 7 = one: Shelf Role = Main Shelf
Note: Bits 6-5 of the register must be set to 0 (zero).
If any new shelf begins to boot with an invalid or non-unique rotary dial setting, it is
prevented from completing initialization, and it is not assigned an AID. A system
PRCDRERR alarm is raised (if the main shelf is operational). The new shelf begins
blinking all its LEDs and continues until the situation is resolved.
Note: The rotary dial must not be changed after the shelf has been discovered by the
system.
Important! A unique shelf ID is required for each shelf.
Main shelf
One and only one shelf in each NE can have the role of Main shelf. This is designated by
a backplane rotary dial setting of 0x81 (Shelf Role = Main Shelf, Shelf ID = 1). When a
new PSS-32 shelf boots up and finds that its rotary dial is set to 0x81, it automatically
provisions itself with AID = SHELF-1 and TYPEID = UNV. It then begins to perform the
role of the main shelf.
Note: Two main shelves (i.e. two NEs) cannot be connected by internal LAN cable as
if they belonged to a single NE (i.e., as if one was subordinate to the other).
Not-Main shelf
A Not-Main shelf is pre-provisioned by user command specifying a unique Shelf AID and
specifying TYPEID = UNV. The shelf number of the Shelf AID should be set equal to the
expected rotary dial setting. For example, if the pre-provisioned AID is SHELF-3, the
shelf is expected to have a rotary dial setting of 0x03.
A shelf AINS mode parameter can be set to prevent immediate loss of communication
alarming against a newly pre-provisioned shelf.
When a new Not-Main shelf (with valid and unique rotary dial setting) is detected by the
system (by internal LAN discovery), it is checked against current pre-provisioned shelf
definitions. If a match is found, the new shelf is assigned the pre-provisioned shelf AID.
Match is defined as follows.
The shelf number of the pre-provisioned shelf AID must be equal to the actual value
read from the rotary dial, and the pre-provisioned shelf TYPEID value must be UNV.
When a newly detected not-main shelf (with valid and unique rotary dial setting) does not
match any pre-provisioned definition, it is auto-provisioned. The shelf number of the
shelf AID is automatically assigned the actual value read from the rotary dial. The
TYPEID is automatically set to UNV.
....................................................................................................................................................................................................................................
1830 PSS
5-138
Issue 1 June 2013

Shelf provisioning
....................................................................................................................................................................................................................................
Note: Main shelves cannot be auto-provisioned, but Not-Main shelves can be

pre-provisioned and can be auto-provisioned.
SFD40, SFD40B, SFD44, SFD44B, ITLB, ITLU, and DCM shelf
SFDs multiplex and de-multiplex optical channel signals.The SFD40 100GHz Channel
Spacing Optical Multiplexer/Demultiplexer and the SFD40B with 50GHz frequency shift
are used to multiplex and to demultiplex forty optical channels in the C-Band. The SFD44
and SFD44B are passive standalone rack-mounted devices that are not slot-resident. The
SFD has an optical line-level interface to an ITLB, ITLU, or CWR circuit pack (or an LD,
in the case of an end terminal node). The SFD44 is modeled by the system as a shelf of
type SFD44, with one fixed slot containing a card of type SFD44. The SFD44B is
modeled by the system as a shelf of type SFD44B, with one fixed slot containing a
card of type SFD44B.
The ITLB/ITLU is designed to be used in combination with the SFD44 and SFD44B. The
ITLB/ITLU combines and de-muxes the odd and even sets of signals into a single group
of 88-channel group of signals with 50GHz spacing. The ITLB/ITLU is modeled by the
system as a shelf of type ITLB/ITLU, with one fixed slot containing a card of type
ITLB/ITLU.
DCM is a passive rack-mounted device that is not slot-resident. The DCM is modeled as a
shelf of type DCM, with one fixed slot containing a card of type DCM. There are 3
different sizes of DCM. Up to 16 DCMs (depending on size) can reside together in a
shelf-like housing with no backplane. DCMs provide optical line-level dispersion
compensation to LD or OSCT circuit packs. There are SMF, LEAF, and TWRS fiber
types for the DCM modules. The NE supports a fibertype attribute for DCMs to allow the
user to provision or have the NE auto provision the type (if inventoried).
Any provisioning of a new SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf
automatically provisions the contained
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM card. Deprovisioning an
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf automatically de-provisions
(deletes) the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM card, and this is the
only way to delete an SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM card.
SFD40/SFD40B/SFD44/SFD44B/ITLB/DCM shelves have no rotary dial mechanism.
Instead, each SFD40/SFD40B/SFD44/SFD44B/ITLB/DCM shelf is identified by a
unique serial number which is stored on the RI EEPROM, and is also externally visible
on the equipment label.
Transmission association
The transmission association between an

SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM and the optical line equipment it
supports is defined solely by a topology fiber assignment between
....................................................................................................................................................................................................................................
1830 PSS
5-139
Issue 1 June 2013

Shelf provisioning
....................................................................................................................................................................................................................................
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM and CWR (or LD or OSCT, in an

end terminal node). The transmission association and the management association must
agree; they must have the same modules as endpoints.
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM remote inventory data is retrieved
electronically by a CWR, LD, or OSCT pack; this is the only management access to the
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM. The first reading of
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM electronic inventory is treated as
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM detection, and this defines an
internal management association between an
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM and a CWR, LD, or OSCT. The
system must internally map the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM AID
to the CWR, LD, or OSCT via which the
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM was first detected. This allows
subsequent data retrieval against an SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM
AID to be directed internally to the correct CWR, LD, or OSCT.
SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelves can be pre-provisioned and
can be auto-provisioned. An SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf is
pre-provisioned by user command specifying a unique Shelf AID, specifying
TYPEID=SFD44/DCM, and (optionally) specifying a unique PROVSERNUM value
equal to the expected SFD/DCM serial number. This allows checking for connection of
the correct SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM.
Matching pre-provisioned values
When a new SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf is detected by the

system (by electrical inventory discovery), it is checked against current pre-provisioned
shelf definitions. If a match is found, the new shelf is assigned the pre-provisioned AID.
If there is more than one match, the one with the lowest pre-provisioned AID is used.
Match is defined as follows.
If Serial Number was pre-provisioned with a non-default value: The actual

SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM serial number must be equal to
the Serial Number value. The actual shelf type must equal the pre-provisioned
TYPEID value.
If Serial Number was pre-provisioned with the default value (i.e. has not yet been
specified): The actual shelf type must equal the pre-provisioned TYPEID value. In
this case, Serial Number is now automatically assigned the actual serial number read
from the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM.
When a newly detected SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM shelf does

not match any pre-provisioned definition, it is auto-provisioned. It is automatically
assigned the lowest available shelf AID. The serial number is automatically assigned the
actual serial number read from the SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM.
The TYPEID is automatically assigned the actual shelf type.
....................................................................................................................................................................................................................................
1830 PSS
5-140
Issue 1 June 2013

Shelf provisioning
....................................................................................................................................................................................................................................
Note: The Serial Number value can be modified by the user whenever needed. For
example, when an SFD40/SFD40B/SFD44/SFD44B/ITLB/ITLU/DCM is physically
replaced without deletion of its provisioning, Serial Number must be changed from
the old serial number to the new one.
....................................................................................................................................................................................................................................
1830 PSS
5-141
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to create (pre-provision) a shelf (see Shelf provisioning
(p. 5-137)).
Note: The WebUI supports creation (pre-provisioning) for all shelves, except the main
shelf (see Shelf provisioning (p. 5-137)).
Before you begin
Instructions
...................................................................................................................................................................................................
From the WebUI, select System > Create Shelf.

Result: The Create Shelf screen is displayed.
...................................................................................................................................................................................................
Enter shelf parameters and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-142
Issue 1 June 2013

Create Shelf
....................................................................................................................................................................................................................................
Create Shelf
Attribute
Provisioned Type
Value/Format
Empty
Additional Info
Type of shelf.
External DCM
ITLB
ITLU
PSS-4 Universal
PSS-16 Universal
PSS-32 Universal
PSS-32S Universal
SFD40
SFD40B
SFD44
SFD44B
Shelf ID
{2-8} for PSS-4 Universal

{2-24} for PSS-16 Universal,
PSS-32 Universal, and
PSS-32S Universal
Unique identifier for the shelf.

Shelf ID 1 is reserved for
the Master shelf.
{25-64} for External DCM,

ITLB, ITLU SFD (all)
Shelf Name
<0-31 chars>

shelf.
Description
<0-255 chars>
the shelf.
AINS Enabled
(checkbox)
When enabled, shelf

communication alarms and
card alarms for this shelf are
suppressed until the shelf is
physically present and
detected by the NE.
This field is not applicable to
the Main Shelf.
Serial Number
<0-16 chars>
Serial number of the shelf.

Not applicable to PSS-4,
PSS-16, PSS-32, and
PSS-32S Universal shelves.
....................................................................................................................................................................................................................................
1830 PSS
5-143
Issue 1 June 2013

Create Shelf
....................................................................................................................................................................................................................................
Attribute
Is Managed
Value/Format
(checkbox)
Additional Info
Indicates whether the shelf is
expected to be managed via
the serial electrical inventory
wire. When enabled,
inventory readability indicates
presence or absence. When
disabled, the shelf is treated
as always present, even
though there is no
communication.
PSS-32, and PSS-32S
Universal shelves.
Expected PF (Amps)
PSS-4: {Auto, 3.7, 4.1, 8.5,

20.6}
The expected amperage of the

shelf power supply module.
PSS-16: {Auto, 20, 35}
Applicable to PSS-4, PSS-16,

PSS-32, and PSS-32S
Universal shelves only.
PSS-32: {Auto, 20, 30, 50,

60, 70}
PSS-32S: {Auto, 3x50}
PF A Expected Amps
PSS-4: {3.7, 4.1, 8.5, 20.6}

Applicable to PSS-4 only.
PF B Expected Amps
PSS-4: {3.7, 4.1, 8.5, 20.6}

Expected Volts
48 (default) V dc
60 V dc
Specifies the nominal voltage

for the shelf and sets the
voltage alarms to the ends of
the standard operating range
for the specified input supply
voltage.
48: The input supply
voltage is nominally -48

V dc

V dc
....................................................................................................................................................................................................................................
1830 PSS
5-144
Issue 1 June 2013

Create Shelf
....................................................................................................................................................................................................................................
Attribute
High Voltage Threshold
(Volts)
Low Voltage Threshold

(Volts)
Value/Format
35.0 - 85.0
Default:
57 V dc (when Expected
Volts is 48 V dc)
Volts is 60 V dc)
35.0 - 85.0
Default:
40.5 V dc (when
Expected Volts is 48 V
dc)
Volts is 60 V dc)
Voltage Threshold Tolerance

(Volts)
2 (default)
Wavelength Tracker Enabled
(checkbox)
1-5
Additional Info
Specifies the high voltage
threshold for the power filter
input voltage. The default
value is the high voltage
specified in the operating
range.
Specifies the low voltage
value is the low voltage
range.
Specifies the response lag for

the threshold voltage to
prevent switching the alarm
on and off near the threshold.
Indicates if cards on the shelf
are capable of providing WT
encoder or decoder
functionality. When enabled,
a PFDCA power filter may
not be equipped in this shelf.
When disabled, only unkeyed
optical channels may be
provisioned on cards in this
shelf.
Applicable to PSS-32
Universal shelf only.
....................................................................................................................................................................................................................................
1830 PSS
5-145
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view/modify shelf properties (see Shelf provisioning
(p. 5-137)).
Before you begin
Instructions
Note: There are restrictions on which shelves and parameters can be modified.
...................................................................................................................................................................................................
Select the shelf from the equipment tree and select the Provision/Info function.
Result: The Shelf Properties screen is displayed.
...................................................................................................................................................................................................
Modify applicable parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-146
Issue 1 June 2013

Shelf Properties
....................................................................................................................................................................................................................................
Shelf Properties
Attribute
Value/Format
Additional Info
Present Shelf Type
Empty
Value of shelf type detected

by the network element.
External DCM
ITLB
ITLU
PSS-4 Universal
PSS-16 Universal
PSS-32 Universal
PSS-32S Universal
SFD40
SFD40B
SFD44
SFD44B
Provisioned Shelf Type
External DCM
ITLB
Value of shelf type

pre-provisioned by the user.
ITLU
PSS-4 Universal
PSS-16 Universal
PSS-32 Universal
PSS-32S Universal
SFD40
SFD40B
SFD44
SFD44B
Shelf Name
<0-31 chars>

shelf.
Description
<0-255 chars>
the shelf.
....................................................................................................................................................................................................................................
1830 PSS
5-147
Issue 1 June 2013

Shelf Properties
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
AINS Enabled
(checkbox)
When enabled, shelf

communication alarms and
card alarms for this shelf are
suppressed until the shelf is
physically present and
detected by the NE.
Not applicable to the main
shelf.
Status LED Color
{Off, Red, Green, Orange}

{Solid, Wink, Blink}
The LED behavior is based

on the EC state and the
highest shelf/system alarm
level.
Expected PF (Amps)
PSS-4: {3.7, 4.1, 8.5, 20.6,

Mixed}
PSS-16: {Auto, 20, 35}
The expected current rating of

the shelf power supply
module.
PSS-32: {Auto, 20, 30, 50,

60, 70}
Expected Volts
48 (default) V dc
60 V dc
Specifies the nominal voltage

for the shelf and sets the
voltage alarms to the ends of
the standard operating range
for the specified input supply
voltage.

V dc

V dc
High Voltage Threshold
(Volts)
35-80
Default:
Volts is 48 V dc)
Volts is 60 V dc)
Specifies the high voltage

value is the high voltage
range.
....................................................................................................................................................................................................................................
1830 PSS
5-148
Issue 1 June 2013

Shelf Properties
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Low Voltage Threshold

(Volts)
35-80
Specifies the low voltage

value is the low voltage
range.
Default:
40.5 V dc (when
Expected Volts is 48 V
dc)
Volts is 60 V dc)
Voltage Threshold Tolerance

(Volts)
2 (default)
Wavelength Tracker Enabled
(checkbox)
1-5
Specifies the response lag for

the threshold voltage to
prevent switching the alarm
on and off near the threshold.
Indicates if cards on the shelf
are capable of providing WT
encoder or decoder
functionality. When enabled,
a PFDCA power filter may
not be equipped in this shelf.
When disabled, only unkeyed
optical channels may be
provisioned on cards in this
shelf.
Applicable to PSS-32
Is Managed
(checkbox)
Indicates whether the shelf is

expected to be managed via
the serial electrical inventory
wire. When enabled,
inventory readability indicates
presence or absence. When
disabled, the shelf is treated
as always present, even
though there is no
communication.
PSS-16 and PSS-32 Universal
shelves.
Company ID
<0-4 chars>
The shelf manufacturer.

Applicable to PSS-4
....................................................................................................................................................................................................................................
1830 PSS
5-149
Issue 1 June 2013

Shelf Properties
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Mnemonic
<0-8 chars>
The Alcatel-Lucent
mnemonic for the shelf.
Applicable to PSS-4
CLEI
<0-10 chars>
The Common Location

Equipment Identifier for the
shelf.
Applicable to PSS-4
Unit Part Number
<0-14 chars>
The Alcatel-Lucent part

number for the shelf.
Applicable to PSS-4
Software Part Number
<0-14 chars>

number for the software
running on the shelf.
Applicable to PSS-4
Factory ID
<0-4 chars>
Identifier of the factory where

the shelf is manufactured.
Applicable to PSS-4
Serial Number
<0-16 chars>
The serial number of the

shelf.
Applicable to PSS-4
Date
<0-6 chars>
The date the EEPROM was

written.
Applicable to PSS-4
Extra Data
<46 bytes>
Additional inventory data,

populated based on the shelf
type.
Applicable to PSS-4
....................................................................................................................................................................................................................................
1830 PSS
5-150
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to delete a shelf.

Before you begin
Instructions
Note: The main shelf cannot be deleted.

...................................................................................................................................................................................................
Select the shelf from the equipment tree and click Delete.
Note: For an Alcatel-Lucent 1830 PSS-32 and Alcatel-Lucent 1830 PSS-16 shelf, all
cards except the active EC, FAN, USRPNL, and PF must be manually deleted before
a shelf can be deleted.
For an 1830 PSS-32S shelf, all cards except the BTC, HKPCNTL, FAN, MTC1T9
and PF must be manually deleted before a shelf can be deleted.
For SFD40, SFD40B, SFD44, SFD44B, ITLB, and ITLU shelves, the card is
automatically deleted by the NE when the shelf is deleted. The card must be in a valid
state for deletion before the shelf can be deleted.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-151
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to test LEDs.

Before you begin
Instructions
...................................................................................................................................................................................................
Select the PSS shelf from the equipment tree and select the Test/Analysis function.
Result: The Shelf LEDs screen is displayed.
...................................................................................................................................................................................................
Select Test LEDs and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-152
Issue 1 June 2013

Shelf LEDs
....................................................................................................................................................................................................................................
Shelf LEDs
Attribute
Additional Info
Test LEDs
Lights all the LEDs on the shelf, allowing

identification of faulty LEDs.
....................................................................................................................................................................................................................................
1830 PSS
5-153
Issue 1 June 2013

....................................................................................................................................................................................................................................
4DPA2 OT
The 4DPA2 is a half-height, single-wide dual transponder that has two client ports with
SFP optics directly associated with two line ports. It also supports a single E-SNCP
protection group, which uses both line ports to protect one of the two client ports. With
E-SNCP only one client port is supported. The 4DPA2 is an optimized version of the
4DPA4 for application in the Alcatel-Lucent 1830 PSS-16.
The following client signals are supported:
OC48/STM16
1GbE
4DPA4 OT
The 4DPA4 OT, sometimes referred to as the MSC (Multi-Service Card), is a half-height,
single-wide card that accepts up to four client signals via SFP optics, and performs
non-blocking multiplexing into one or both line ports. It has dual pluggable OTU1 line
ports that support B&W, CWDM, or DWDM line signals, and supports a variety of
sub-ODU1 client signals with extremely flexible transponder mappings.
There are four pluggable client interfaces: two at the top, and two at the bottom. The
middle of the faceplate has sockets for the dual line interfaces: two eVOA SFPs and two
line port SFPs. Line transmit fibers are externally connected through the eVOA ports for
Wavetracker functionality. There is a pack status LED in the upper right corner of the
faceplate. Each port has a dedicated port status LED, and each port also has a second
LED. The second LED is used on client ports is used to indicate dynamic Ethernet
activity, and is not used on line ports and eVOA ports.
Two card mode values are supported for 4DPA4: DualTran and FlexMux. The "Card
Mode" parameter determines the feature type of the 4DPA4 main firmware image. It
affects many fundamental aspects of card and port behavior, including:
Which client signal types are supported.
Which client ports can be used.

Which user interface commands apply.
Whether line ports are created manually or automatically.
How client ports are mapped to line ports.

Whether or not timeslots exist on the line ports.
How the near-end node reads LosProp data sent by the far-end node.
Whether or not E-SNCP protection is supported.
....................................................................................................................................................................................................................................
1830 PSS
5-154
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisioning the cardmode parameter is allowed only when there are no connections and
all ports are unassigned. Otherwise it is denied. As with other parameters, cardmode can
be provisioned on a card that is physically present, physically absent, or pre-provisioned.
Note: Changing the cardmode automatically clears any non-default provisioning of
firmware release (package identifier), and automatically triggers a cold restart of the
card to download the default version of the firmware line corresponding to the new
cardmode.
DualTran card mode
When cardmode=DualTran, FC400 is the only client signal type supported. Client ports
C1 and C3 can be used, but C2 and C4 cannot be used. Provisioning of C2 and C4 are
denied. FC400 commands apply to 4DPA4 only in this card mode. TL1 and CLI
commands specific to other client signal types are denied. Line ports are created
automatically. ODU1 commands are denied. Timeslots do not exist, and E-SNCP
protection is not supported.
When cardmode=DualTran, client port parameters and line port parameters behave or
apply as appropriate for the Dual Transponder FC400 feature. Examples: OPRMODE,
OTURATE, and FCMODE parameters have different values in FC400 image.
OPRMODE is read-only. TS, NETSMAP, FETSMAP, PLDTYPE, and ODU0INTERWK
parameters do not apply. Parameters specific to SONET, SDH, or 1GBE do not apply.
FlexMux card mode
When cardmode=FlexMux, all client signal types are supported except FC400. All four
client ports can be used. TL1 and CLI command specific to FC400 are denied. Line ports
are created manually. ODU1 commands apply. Timeslots exist to flexibly assign line port
bandwidth for sub-ODU1 clients. E-SNCP protection is available. When
cardmode=FlexMux, client port parameters and line port parameters behave or apply as
appropriate for the Flexible Mux feature.
11DPE12(A/E) OT
The 11DPE12, 11DPE12E (enhanced), and 11DPE12A (2nd generation 11EPE12E) are
12xGbE MUX OT single slot, full height cards, providing an Ethernet multiplexing
platform that aggregates up to twelve full-rate GbE client services onto two 10G paths,
supported by B&W/CWDM/DWDM line-side PTM optics. By providing unrestricted
throughput and MAC PDU transparency for up to ten GBE clients, this pack offers
Ethernet Virtual Private Line (EVPL) service transport with Q_in_Q tagging mechanism,
as defined in MEF and ITU-T documents.
The 11DPE12, 11DPE12E, and 11DPE12A support 88 channels when configured with a
tunable XFP. When configured with a fixed channel XFP, only 44 even channels are
supported. Fixed odd channel XFPs are not supported. The fixed channel XFPs supported
on these line ports are not wavelength locked, therefore traffic from these XFPs may only
traverse 100 GHz systems.
....................................................................................................................................................................................................................................
1830 PSS
5-155
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: The 11DPE12E and 11DPE12A contain a more sophisticated switch which
enables the development of advanced features in future releases. The 11DPE12A
supports the IEEE 1588v2 Precision Timing Protocol (PTP).
The 11DPE12(A/E) card supports the following features:
Multiplex of 12 Ethernet interfaces and two 10G line interfaces
Statistical L2 multiplexing
Supports FullRate, SubRate, QinQ operational mode
Full 88 channel C-band DWDM support
Terminal loopback and facility loopback
Supports E-SNCP protection in QinQ mode
11DPE12A/E supports synchronization timing references (only applicable if the card

has Synchronous Ethernet Enabled).
Note: For 11DPE12(A/E) QinQ mode, packet loss occurs when traffic load is 100%.
Therefore, keep the client ingress bandwidth less than 95%.
If the 11DPE12(A/E) card has an E-SNCP protection group provisioned, modifying the
Operational Mode from FullRate to SubRate or QinQ is not allowed.
11DPE12A enhancements
The 11DPE12A is a 12xGbE MUX OT variant that supports the IEEE 1588v2 Precision
Timing Protocol (PTP). The following features and enhancements are provided on the
11DPE12A:
IEEE 1588v2
Beginning in Release 6.0 PTPIO and PTPCTL cards can be used in conjunction with
11DPE12A to support IEEE 1588v2 PTP.
Y-cable and ESNCP across mate packs

Y-cable (for 1GbE client ports) and ESNCP across cards are supported on 11DPE12A
beginning in Release 6.0 in the same way as 11DPE12E in previous releases. Note
that LAG is only available on a single card and cannot be used in conjunction with
ENSCP across cards.
ITU-T Y.1731 PM (LM, SLM, 2-way & 1-way DM - on-demand only)

11DPE12A implements the ITU-T Y.1731 PM functions Loss Measurement
(Eth-LM), Synthetic Loss Measurement (ETH-SLM) and Delay Measurement
(ETH-DM, both 1-way and 2-way). In this release, they are only configured as
on-demand OAM tools.
CRU for EEC/SEC
Two external 1pps+ToD and BITS interfaces (CLK1 and CLK2)

Hardware acceleration allowing independent timing reference for line ports
....................................................................................................................................................................................................................................
1830 PSS
5-156
Issue 1 June 2013

....................................................................................................................................................................................................................................
Architectural changes
New L2 switch
Large Look-aside FPGA for IEEE 1588v2 and Y.1731
Enhanced controller and RAM
Support for 10/100/1000BASE-T SFP with embedded WT encoder
Enhanced Data features
Existing 11DPE12E features (QinQ for EVPL, CIR/PIR, E-SCNP, etc), except
Y-cable and ESNCP across mate packs
1588V2 PTP OC master/slave, BC over OTN HWready (CMCC CI version)
Ethernet OAM enhancements (IEEE 802.1ag CFM [CC, LB], ITU-T Y.1731 FM
[RDI, CSF], LPT, G.8021-compliant FM processes)
OAM and LPT on 10GbE client ports
Service OAM (CFM and Y.1731) and Link-Pass-Through (LPT) is available also
on 10GbE client ports (configured with special UNI port role)
SyncE support
Ethernet PM enhancements
11DPE12A supports the following additional optical pluggable modules in R6.0:
Bidirectional 1GbE SFP 20km and 40km, uplink and downlink
(1000BASE-BX20-U, 1000BASE-BX20-D, 1000BASE-BX40-U,
1000BASE-BX20-D)
Multi-rate 10/100/1000BASE-T electrical SFP, which can be used globally. This is

a replacement of the existing electrical SFP which is restricted to ETSI region due
to a supplier patent issue for deployments in NAR. The same part number is used.
10G DWDM fixed wavelength XFP, with the following characteristics: operating
bit rate: 9.95 Gbit/s to 11.3 Gbit/s (for w/ FEC application only), 50GHz channel
spacing in C band, 80km, 88 channels)
IEEE 1588v2 PTP feature support
The following features are supported on the 11DPE12A variant of the 12xGbE MUX OT
by PTPCTL and PTLIO cards:
Clock scope: Standalone PTP clock (single)
Clock mode: OC-master/slave, BC

Clock type: One-step
Delay measurement scheme: End-to-end
PTP transport over Ethernet ports:

Encapsulation: Ethernet
Addressing: Unicast/multicast/hybrid
....................................................................................................................................................................................................................................
1830 PSS
5-157
Issue 1 June 2013

....................................................................................................................................................................................................................................
PTP transport over OTU2e ports:

Encapsulation: Ethernet
Addressing: Unicast/multicast/hybrid
Transport PTP packets together with the Ethernet traffic

Supported PTP messages: Announce, Sync, Delay_Req, Delay_Resp
External ToD interfaces: 2 configurable input/output with CMCC format
Link asymmetric correction: Manual

Cable correction
Interworking with syncE: independent; 1588 over syncE
Ethernet OAM
Note: This applies to the 11DPE12A/E card only.

The WebUI supports the following:
Maintenance Domain - The WebUI supports create, modify and view of 1

maintenance domain on the 11DPE12A/E card. The WebUI supports deletion of a
maintenance domain when there are no maintenance associations for the maintenance
domain.
Maintenance Association - For each Maintenance Domain, the WebUI displays a table
listing all the configured maintenance associations. For each Maintenance Domain,
the WebUI supports create, modify and view of up to 400 maintenance associations.
The WebUI supports adding and deleting a Remote MEP ID to a maintenance
association. A Remote MEP ID can only be added if a maintenance end point exists.
The WebUI supports deletion of a maintenance association if there are no
maintenance end points associated with it.
Maintenance End Point - For each Maintenance Association, the WebUI displays a
table listing all the configured maintenance end points. For each Maintenance
Association, the WebUI supports create, modify and view of up to 100 maintenance
end points. For each Maintenance End Point, the WebUI displays a table of the MEP
CCM database. The MEP CCM database can only be retrieved if a remote MEP ID
has been provisioned on the MA. The WebUI supports deletion of a maintenance end
point only if the Remote MEP ID on the MA has been deleted.
For the 11DPE12A/E card, the WebUI displays an object with the label MEP under
the card. This object represents all MEPs (Maintenance End Points) for the port.
TheWebUI displays a list of all active alarms for all MEPs on the selected card. The
user can select a MEP and then display a list of condition types that are applicable to
the selected MEP. A refresh button is provided so that the user can refresh the alarm
list.
CFM Stack - For the 11DPE12A/E card, the WebUI displays a table of MEP data
representing the CFM stack.
....................................................................................................................................................................................................................................
1830 PSS
5-158
Issue 1 June 2013

....................................................................................................................................................................................................................................
Precision Time Protocol (PTP)
Note: This applies to the 11DPE12A card only.

PTP is a message protocol similar to NTP, that operates closer to the physical layer. PTP
can be used to distribute time of day, a common Epoch or Frequency. It maintains
synchronization between master and slave clocks, but unlike standard NTP in the server,
PTP distributes the time to slaves using multicast rather by responding to requests from
the slaves as with NTP. (For details see 1830 PSS Product Information and Planning
Guide.)
The WebUI supports provisioning functions for the following PTP entities:
PTP ToD
The WebUI supports modify and view of the PTP ToD (Time of Day) interface
attributes for each of the ToD interfaces on the card.
ToD interfaces are created and deleted with the card
ToD interface attributes are only modifiable if PTP is enabled on the

PTP Clock
Note: Only one PTP clock is supported per card.
A PTP Clock is automatically created when the Clock Mode is changed from
PTP Disabled to another mode.
A PTP Clock is automatically deleted when the Clock Mode is changed to PTP
Disabled.
Domain can only be modified if Clock Enabled = No.
PTP Port
The WebUI displays a table with all PTP ports provisioned on a PTP Clock
The WebUI supports creating up to 14 PTP ports per PTP clock. (If Clock Mode =
Ordinary Clock Master or Ordinary Clock Slave, only one PTP Port may
be created per PTP Clock. If Clock Mode = Boundary Clock, multiple PTP ports
may be created.)
The WebUI supports deletion of a PTP port. (The port cannot be deleted when
Port Enabled = Yes.)
....................................................................................................................................................................................................................................
1830 PSS
5-159
Issue 1 June 2013

....................................................................................................................................................................................................................................
The WebUI supports the following Fault functions on a per-PTP object basis:
PTP Clock/PTP Port
The WebUI displays a list of all active alarms on the selected PTP object. A
refresh button is provided, so that the user may refresh the alarm list. The WebUI
will not automatically update the screen for new alarms and clears. Note: there are
no severity filters for this alarm list.
The WebUI displays a list of condition types that are applicable to the selected
object.
PTP ToD
A user may modify the facility alarm severity for a selected condition type.
A user may revert to the default severity for all condition types of a specified
category.
11DPE12A enhancements
The 11DPE12A is a 12xGbE MUX OT variant that supports the IEEE 1588v2 Precision
Timing Protocol (PTP). The following features and enhancements are provided on the
11DPE12A:
IEEE 1588v2
11DPM12 OT
The 11DPM12 transponder is a single slot wide, full height card supporting dual
pluggable line ports with flexible any-rate client signal aggregation and add/drop. With
two line ports and flexible traffic configuration, the 11DPM12 OT can provide ADM on a
blade and E-SNCP functionalities. All client signals can be transported in a bit-transparent
or character-transparent manner over OTN.
The 11DPM12 card supports the following features:
Twelve client interfaces with B&W or CWDM pluggable optics (SFPs)

Support for the following client interfaces: OC3/STM1, OC12/STM4, OTU-1
(G.709), 1Gb Ethernet, FC100/FICON, FC-200/FICON_Express,
FC400/FICON_Express4, Optical HD-SDI, Optical 3G-SDI, SD-SDI
Any service on any client port
Independent service level switching between two line ports for all types of supported
signals
Independent port level add/drop switching between any line port and any client port
Full-rate non-blocking muxing capacity into line ports: 9xGbE, 10xFC100, 5x FC200,
2x FC400, 12x OC3/STM1, 12x OC12/ STM4, 3x 3G-SDI, 6x HD-SDI 6x SD-SDI,
12xFE, 4xOTU1, 4xOC48
....................................................................................................................................................................................................................................
1830 PSS
5-160
Issue 1 June 2013

....................................................................................................................................................................................................................................
Two OTU2 line ports (10.709Gbps, provisionable) with EFEC (G.975.1 I.4) and RS
FEC (G.709), supported by CWDM or DWDM pluggable optics (XFPs) and tunable
DWDM XFP. DWDM XFPs DTV control function is supported at both line ports
Wavelength Tracker encoding on line-side transmit, by separate pluggable modules on

the faceplate. (Each line has a dedicated SFP VOA that supports slow eVOA for
attenuation and fast eVOA as Wavelength Tracker.)
11QPA4/11QPEN4 OT
The 11QPA4/11QPEN4 is a 10G, Quad port, any rate module with four client interfaces.
This module supports four independent multi-rate 10G channels. The 11QPA4A is the
temperature hardened version of this module.
The 11QPA4/11QPEN4 has four pluggable client interfaces (C1, C2, C3, and C4), four
pluggable line interfaces (L1, L2, L3 and L4) and four VOA sockets (VA1, VA2, VA3 and
VA4). The pack has a status LED, but does not support status LEDs for the optical ports
and VOA ports due to physical limitations on the faceplate, but the WEBUI does support
LED status for all ports.
The 11QPEN4 offers provisionable encryption attributes for the optical data center
connect feature.
The 10G pluggable line port supports 88 channels when configured with a tunable XFP.
When configured with a fixed channel XFP, only 44 even channels are supported. Fixed
odd channel XFPs are not supported. The fixed channel XFPs supported on these line
ports are not wavelength locked, therefore traffic from these XFPs may only traverse 100
GHz systems.
The 11QPA4/11QPEN4 transponder supports four independent Multi-rate 10G channels
and an 8G Fibre channel. The following client signals are supported.
OTU2
STM-64, OC-192 (11QPA4)
10GbE WAN PHY (11QPA4)
10GbE LAN PHY
FC800
FC1200
The following operational modes are supported:
ADD_DROP (11QPA4 and 11QPEN4)
....................................................................................................................................................................................................................................
1830 PSS
5-161
Issue 1 June 2013

....................................................................................................................................................................................................................................
In this mode, the circuit pack is processing signal in both transmission directions
(ingress, from client port towards the line side, from line side to client port). The
board supports C1 to L1 ADD_DROP. The board supports C2 to L2 ADD_DROP.
The board supports C3 to L3 ADD_DROP. The board supports C4 to L4
ADD_DROP.
CrossRegen (11QPA4)
In this mode, the Line port input signal is looped towards another line port output
through 8x8 matrix. The client XFP is not necessarily provisioned or equipped, and no
alarm or performance monitoring is associated with those client ports. The circuit
pack supports CrossRegen between any two line ports.
AddOnly (11QPA4)
In this mode, each Line port involved in the multicast connection is provisioned for
ADD_ONLY mode with the source client port specified.
DropContinue (11QPA4)
In this mode, the card is processing the signal in the egress direction and looping the
signal from the line side input towards the line side output. The alarms in the unused
direction are masked.
11QPE24
The 11QPE24 is a double-width full height pack providing Ethernet aggregation and
switching capabilities for its 10/100/1000 client ports and four OTN-mapped (OTU2) or
native 10GE line ports. The card is equipped with 24 Client ports, currently client ports
1-22 can be provisioned for service. All optics on the 11QPE24 are provided by pluggable
transmission modules (PTMs).
11QPE24 supports the pluggable optics shown below for the following ports:
24 SFP slots for Client ports. Both optical and electrical SFPs are supported.
4 XFP slots for the 10G Line ports
4 SFP VOA slots
The 10G pluggable line port of the 11QPE24 supports 88 channels when configured with
a tunable XFP. When configured with a fixed channel XFP, only 44 even channels are
supported. Fixed odd channel XFPs are not supported. The fixed channel XFPs supported
on these line ports are not wavelength locked, therefore traffic from these XFPs may only
traverse 100 GHz systems.
The 11QPE24 supports the following features:
24 SFP slots for Client ports. Both optical and electrical SFPs are supported.
4 XFP slots for the 10G Line ports

4 SFP VOA slots (SFP)
....................................................................................................................................................................................................................................
1830 PSS
5-162
Issue 1 June 2013

....................................................................................................................................................................................................................................
OTN FM/PM is the same as 11DPE12(E/A)

State-of-the-art carrier-grade L2 Switch
Carrier Ethernet Services
L2 Switching Support for E-LAN services
Layer 2 Access control List (ACL)

IGMPv2 snooping for L2 multicast
Port Mirroring
VLAN Push/Pop (E-LAN ) configurable per port
L2 Switching Support for E-LAN services
DiffServ QoS (8 CoS)

ERP acc. G.8032(v2) w/o multi-ring support
Ethernet OAM (ITU-T Y.1731/IEEE 802.1ag FM)
Ethernet OAM Enhancements (ITU-T Y.1731)

Ethernet Link OAM (IEEE 802.3ah)
SyncE
Port and Service PM counters (w/o binning)
The following interfaces are supported on the ports of the 11QPE24 with the appropriate
PTM:
Line interface
OTU2
Client interface
1GbE
10GbE
Fast Ethernet (FE)
11STAR1/11STAR1A OT
The 11STAR1/11STAR1A Optical Transponder (OT) is a multi-service card that supports

one client interface (C1) and an 11G tunable line side interface (L1). It is called a
multi-service card because it supports different client signal types, configurable through a
user interface. On the client interface, the 11STAR1/11STAR1A OT uses an XFP
pluggable module, to allow support for different optical link applications. The user can
configure the 11STAR1/11STAR1A OT to support transmission of a variety of optical
signal protocols (i.e., OC-192, STM-64, 10GbE LAN PHY, 10GbE WAN PHY, 8Gb Fibre
Channel (11STAR1A only) 10Gb Fibre Channel, and OTU2 with G.709 FEC).
....................................................................................................................................................................................................................................
1830 PSS
5-163
Issue 1 June 2013

....................................................................................................................................................................................................................................
On the line side interface (L1), standard ITU-T G.709 digital structures are used. Line
side Forward Error Correction is provisionable for standard G.709 FEC (Reed-Solomon
(255, 239)) or enhanced FEC (EFEC) for higher coding gain. The L1 transmitter can be
tuned to any of the 88 channels supported by the system.
Attention: If the 11STAR1A is provisioned with FECTYPE set to EFEC2, there is a
small chance that under certain situations, traffic would be impacted. The two ends
would no longer be able to pass traffic correctly. Cold reboot of the 11STAR1A packs
on both ends must be executed to recover. Therefore, it is highly recommended to
always use FECTYPE = EFEC or RSFEC. The default setting for the 11STAR1A is
EFEC.
As with all supported OTs, the 11STAR1/11STAR1A can be configured for different
customer applications. The following user provisioning is supported on both the C1 and
L1 ports of the 11STAR1/11STAR1A OT:
Port state and Automatic In-service operation

Enable/Disable Loopback (facility and terminal)
Performance monitoring
The 11STAR1/11STAR1A supports lighting of its LEDs upon appropriate external

triggers to notify the operator of its current operation. However, the LEDs on the
11STAR1 behave slightly differently from other circuit packs. An in-service 11STAR1
with no pack-level alarm, but with a minor port-level alarm (and with no other port-level
alarm that is higher than minor severity) has the following LED behavior:
pack status LED solid green
affected port status LED solid yellow
This means that a minor port-level alarm will have no effect on the pack status LED. This
exception pertains only to the 11STAR1.
11STGE12 OT
11STGE12 Optical Transponder is a GbE multiplexing unit that allows the user to
aggregate up to 10 GbE services onto a 10G digital structure. The pack is designed in a
way that allows flexible port to service provisioning.
Note: Ports 1-10 are available for transporting GbE services while ports 11 and 12
should remain unassigned.
11STGE12 OT supports Ethernet Private Line bi-directional services for up to 10 client
ethernet signals with MAC layer transparency including transparency to client domain
VLAN tag(s). 10 GbE ports can be transported simultaneously with full throughput and
all frame sizes up to Jumbo size of 9216.
....................................................................................................................................................................................................................................
1830 PSS
5-164
Issue 1 June 2013

....................................................................................................................................................................................................................................
The user can enable/disable Auto-negotiation independently on all 10 client ports. Each of
the 10 client facing ports is implemented as an SFP module to allow flexible physical
layer configuration.
As with all supported OTs, the 11STGE12 can be configured for different customer
applications. The following user provisioning is supported on C1-10 and L1 ports of the
11STGE12 OT:

Enable/Disable Loopback (line/facility and terminal). Loopbacks on client ports can
be provisioned independently.
11STMM10 OT
11STMM10 Optical Transponder is a multi-protocol multiplexing unit that allows the

user to aggregate up to 10 client services onto a 10G G.709 compliant digital structure.
This pack is designed in a way that allows flexible port to service provisioning.
The following client signal types can be configured on client ports of 11STMM10 OT:
GbE -> Ethernet private line service using GFP-T encapsulation and code word
transparency for client signal.
OC3/OC12/OC48 -> Terminated SONET services (applicable for SONET system
mode).
STM1/STM4/STM16 -> Terminated SDH services (applicable for SDH system
mode).
Note: For 11STMM10, VC3 structures in SDH mode are not supported.
CBR2G5 -> Bit transparent transport of OC48/STM16 clients (compliant with G.709)
FC100/FC200/FC400 -> Fibre channel services (either FC or FICON mode)
OTU1 -> Terminated OTU1 trail functions
Note: When used in transparent mode, the local onboard oscillator is used. PJE's may
be generated over time. This may impact transparent STM-4 working.
Each of the 10 client facing ports is implemented as an SFP module to allow flexible
physical layer configuration.
Client bit streams characteristic information is adapted to a server carrying digital
structure and mapped into contiguous bandwidth slot on a DWDM line port digital
structure. Figure 5-9, 11STMM10 OT signal processing from client port to DWDM line
port (p. 5-166) shows logical signal processing from the client port to the DWDM line
port. Line port structure consists of 4 ODU1s multiplexed into an ODU2.
....................................................................................................................................................................................................................................
1830 PSS
5-165
Issue 1 June 2013

....................................................................................................................................................................................................................................
Figure 5-9 11STMM10 OT signal processing from client port to DWDM line port
For the purpose of bandwidth allocation and flexible Client transport configurations,
DWDM Line port defines 64 virtual time slots (4 sets of 16). Time slots are identified as
ODU1 # followed by time slot #. ODU1 # ={1,2,3 & 4} while time slot # ={1, 4, 7, 10,
13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}
Each client adapted information takes fixed amount of bandwidth expressed in virtual
time slots in the following way:
OC12/STM4 4 time slots

OC3/STM1 1 time slot
GbE 7 time slots
CBR2G5 16 time slots
FC-100 6 time slots
FC-200 12 time slots

FC-400 24 time slots
OC48/STM16 16 time slots
OTU1 16 time slots
At the time of client port type provisioning, the user enters the starting time slot of the
contiguous bandwidth area on the line port which will transport client adapted
information.
....................................................................................................................................................................................................................................
1830 PSS
5-166
Issue 1 June 2013

....................................................................................................................................................................................................................................
Overall bandwidth required to transport client adapted information does not exceed 64
time slots. In addition to that rule the following provisioning rules apply:
1. Any port can carry any supported signal type
2. Sum of individual OC3/STM1 and OC12/STM4 plus two times sum of OC48/STM16
needs to be less than or equal to 8.
3. OC48/STM16 or CBR2G5 can start on the ODU1 boundaries (time slots 1-1, 2-1, 3-1
or 4-1)
4. OC12/STM4 can start only on the 4 time slot boundary (1-1, 1-13, 1-25, 1-37, 2-1,
)
Each 11STMM10 encodes its port and time slot map and sends it in-band to the peer
11STMM10 pack to validate provisioning match. If port number, signal type, and time
slot provisioning on the two ends doesnt match, FEPORTMISMATCH alarm is declared.
If the user reconfigures client port allocation by deleting OC3/STM1 or OC12/STM4
services in order to configure OC48/STM16 service, there is a potential that internal
Pointer Processor resources will be fragmented (2 adjacent PP sections needed for
OC48/STM16 processing may not be available). 11STMM10 SW uses optimal algorithm
for assigning internal resources so that simple service provisioning (addition) never
causes this condition. However, deletion and reconfiguration of previously configured
services may in some cases exhibit this behavior. If internal PP resources are not available
for OC48/STM16 service, provisioning will be denied. To avoid this condition the user
can either retrieve available PP sections (show resource command) prior to re-configuring
the 11STMM10 to determine which OC3/STM1, OC12/STM4 ports need to be deleted
(to free up at least one pair of PP sections 1&2, 3&4, 5&6 or 7&8) or use transparent
OC48/STM16 option by provisioning CBR2G5 signal type (there is no PP section
allocation for CBR2G5 transport).
Note: For 11STMM10, a summary of resource allocation for Sonet/SDH or PCS can
be displayed in the WebUI by clicking on the Resources tab, selecting the Resource
Type, and clicking Retrieve.
As with all supported OTs, the 11STMM10 can be configured for different customer
applications. The following user provisioning is supported on C1-10 and L1 ports of the
11STMM10 OT:

Enable/Disable Loopback (line/facility and terminal). Loopbacks on client ports can
be provisioned independently.
Note: For 11STMM10 (10xAny ) card, SONET PM counters increment & LOF is
reported after enabling client Facility Loopback. (LOF/LOS by fault gets reported due
to loopback position. PM counters get incremented due to LOF/LOS reported by
fault.)
....................................................................................................................................................................................................................................
1830 PSS
5-167
Issue 1 June 2013

....................................................................................................................................................................................................................................
112PDM11 OT
The 112PDM11 is a high capacity Ethernet muxponder OT that supports Data Center
Interconnections. It can multiplex up to ten 10Gb/s Ethernet (10GE) client signals into an
OTU4 frame for transport to the network over an OTM-0.4v4 optical interface.
Although this transponder is generically called a 100G transponder, the OTU4 nominal
bit rate on the line interface is 111.809 Gb/s, with a bit rate tolerance of 20ppm. The
multiple client interfaces can all be provisioned to transport 10GE client signal types.
The 112PDM11 pack is implemented as a single slot wide pack, capable of operating at
any channel in the C-band 1830 PSS frequency grid. The pack can be equipped with up to
10 SFP+ pluggable modules on its client interfaces, and supports a 100G (4x28G) CFP on
the line side.
The 112PDM11 has one tunable transceiver CFP module in line side which has four
sub-port interfaces L1, L2, L3 and L4. An OTU4 facility is carried over four OTLC
physical ports, the first physical port in the OTLC group (L1) is designated to be the
index forfacility management of OTU4 and ODU4.
The first 10 client interfaces of the 112PDM11 (C1-C10) can be equipped with SFP+
pluggable modules and the last client interface can be equipped with an QSFP+ pluggable
module.
Bit synchronous mapping of a constant bit rate client signal into and from an OTU4
signal is supported
The 112PDM11 operates in ADD_DROP or REGEN modes.
ADD_DROP mode permits transport of client signals to the line side output.
REGEN mode puts the pack in regeneration mode, where the OTU4 line receive
signal is terminated, regenerated, and sent out the line transmit port. When used in
REGEN mode, the client interfaces are not used, and the SFP+ modules do not need
to be present.
Note: Due to thermal requirement, the PSS-32 shelf must be equipped with the
high-power fan (FAN32H) when an 112DPM11 card is installed in the shelf.
112SCA1/112SNA1 OT
The 112SCA1/112SNA1 OT is a three-slot-wide full-height pack, which supports one

100GBE Hot pluggable module on the client interface. The 112SCA1/112SNA1 OT also
supports one OTU4 line interface (non-pluggable), that can be tuned to any of the 99
wavelengths over the extended C-band (Freq: 191.150 THz to 196.050 THz).
The 112SCA1/112SNA1 operates in the optical C band with other Alcatel-Lucent 1830
PSS-32/PSS-36 OTs. The 112SNA1 OT is identical to the 112SCA1 OT, except that the
112SNA1 OT has enhanced OSNR performance.
....................................................................................................................................................................................................................................
1830 PSS
5-168
Issue 1 June 2013

....................................................................................................................................................................................................................................
The 112SCA1/112SNA1 OT supports the following functional features:
Facility and Terminal Loopbacks, Optical Performance Monitoring (OPR, OPT),

Digital Performance Monitoring (RMON, SONET/SDH, OTN - Client Side,
OTUk/ODUk Monitoring Line Side)
Hardware ready to support full ITU-T G.709 functionality, including GCC0 and TCM
Line side features:
PDM NRZ QPSK pulse format (Polarization Division Multiplexing NRZ
Quadrature Phase Shift Keying)
Line side coherent receiver, combined with a DSP to compensate for impared
linear and non-linear transmission (CD, PMD, SPM and non-linear phase noise).
Line side optics can be tuned to any of the 88 wavelengths for 112SCA1 over the
extended C-band (Freq: 191.150 THz to 196.050 THz)
Supports Alcatel-Lucent Enhanced FEC (~9.2 dB coding gain at 1E-15 for ~7-%
overhead)
Wave tracker supports optical power auto-management. User configurable option
to disable the WT for the interoperability application with other systems without
WT
Client side features:

Standard FEC (RS-FEC)
Supports 100 Gbe and OTU4 client interfaces
Note: In TOADM applications the 112SCA1/112SNA1 may not be connected to a
CWR8 or CWR8-88 CLS port.
Note: DWDM-DWDM single channel OEO regeneration is supported on the 100G
112SCA1/112SNA1 with line port operational mode configured for REGEN. For this
configuration, the channel can be different on each SFD (i.e. channel shifting is
supported). Since the regen configuration on the 100G OTs requires unidirectional
connections from the line port to different SFDs and recoloring is supported, receive
frequency (Rx) is an attribute on the line port (in addition to Tx frequency).
112SCX10/112SNX10/130SCX10 OT
Three versions of the 100G Mux OT are supported: 112SCX10, 112SNX10, and
130SCX10. The 112SCX10/112SNX10 OT is a three-slot-wide (130SCX10 is two-slot
wide) full-height pack, that supports multiplexing of up to ten 10G client signals into one
OTU4 line interface. The 112SCX10/112SNX10/130SCX10 OT supports one line
interface (non-pluggable) and ten client interfaces with XFP modules (B&W, CWDM).
The line side optics of the 112SCX10/112SNX10/130SCX10 OT can be tuned to 99
channels in the C-band. Each port has a dedicated port status LED.
....................................................................................................................................................................................................................................
1830 PSS
5-169
Issue 1 June 2013

....................................................................................................................................................................................................................................
The 112SCX10, 112SNX10, and 130SCX10 operate in the optical C band with other
Alcatel-Lucent 1830 PSS-32/PSS-36 OTs.
The 112SCX10 OTs use Polarization Division Multiplexing NRZ Quadrature Phase Shift
Keying (PDM NRZ QPSK) pulse format on the line interface. A line side coherent
receiver, combined with a digital signal processor (DSP), provides compensation of linear
transmission impairments (chromatic dispersion, PMD) and reduction of intra-channel
non-linear transmission impairments (Self Phase Modulation (SPM) and non-linear phase
noise). The 112SNX10 OT is identical to the 112SCX10 OT, except that the 112SNX10
OT has enhanced OSNR performance.
For the 130SCX10, FEC type = SDFEC is supported
The 112SCX10, 112SNX10, and 130SCX10 OT supports the following functional
features:
Facility and Terminal Loopbacks, Optical Performance Monitoring (OPR, OPT),

Digital Performance Monitoring (RMON, SONET/SDH, OTN - Client Side,
OTUk/ODUk Monitoring Line Side)
The 112SCX10/112SNX10/130SCX10 OTs support Y-cable protection
Line side supports the following features:
PDM NRZ QPSK pulse format (Polarization Division Multiplexing NRZ
Quadrature Phase Shift Keying)
Line side coherent receiver, combined with a DSP to compensate for linear
transmission impairments (CD & PMD) and mitigate non-linear impairments
(SPM and non-linear phase noise)
The line side optics can be tuned to any of the 88 wavelengths for 112SCX10 over
the extended C-band (Freq: 191.150 THz to 196.050 THz)
Support Alcatel-Lucent Enhanced FEC (~9.2 dB coding gain at 1E-15 for ~7-%
overhead)
Wave tracker supporting optical power auto-management. User configurable
option to disable the WT for the interoperability application with other systems
without WT
Client side supports the following features:
Standard FEC (RS-FEC)

Supports OC-192/STM-64, 10 GbE, FC800, and OTU2 client interfaces
The mother board supports four key functions: client access, client signal processing,
control architecture, and power supply. Client access is through the ten XFP modules (B
& W and CWDM). Short, long, and extended reach XFP modules are supported. Client
signal processing includes: Status, Alarms, PM, FEC, and pre-mapping of the client signal
into p-ODTU24.
....................................................................................................................................................................................................................................
1830 PSS
5-170
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: In TOADM applications the 112SCX10/112SNX10/130SCX10 may not be

connected to a CWR8 or CWR8-88 CLS port.
Note: DWDM-DWDM single channel OEO regeneration is supported on the 100G
112SCX10/112SNX10/130SCX10 with line port operational mode configured for
REGEN. For this configuration, the channel can be different on each SFD (i.e.
channel shifting is supported). Since the regen configuration on the 100G OTs
requires unidirectional connections from the line port to different SFDs and
recoloring is supported, receive frequency (Rx) is an attribute on the line port (in
addition to Tx frequency).
Note: For interoperability configuration LOS prop = laser off is not supported.
43SCA1 OT
The 43SCA1 OT supports one client port and one, single OTU3 line interface. This pack
is referred to as a 40G Add/Drop or more simply 40G A/D OT. Like the 43SCX4 OT
(see below), the 43SCA1 OT uses a pulse format with Polarization Division Multiplexing
NRZ Binary Phase Shift Keying (PDM NRZ BPSK) on the line interface. It has a line
side coherent receiver, combined with a digital signal processor (DSP), that provide
compensation for linear transmission impairments (chromatic dispersion, PMD) and
reduction of intra-channel non-linear transmission impairments (Self Phase Modulation
(SPM) and non-linear phase noise). The line side optics of the 43SCA1 OT can be tuned
to any of the 99 wavelengths in the extended C-band.
The following client signal types are supported:
OC-768/STM-256
OTU3
43SCX4/43SCX4E OT
The 43SCX4/43SCX4E is a 4x10G MUX OT with a single 43 Gb/s (OTU-3e2 =

44.583355576 Gb/s 20ppm) tunable line port and 4 client ports. It supports
multiplexing of up to four 10G client signals into the single OTU-3e2 line interface.
The 43SCX4/43SCX4E OT uses a Polarization Division Multiplexing NRZ Binary Phase
Shift Keying (PDM NRZ BPSK) pulse format on the line interface. A line side coherent
receiver, combined with a digital signal processor (DSP), provides compensation of linear
transmission impairments (chromatic dispersion, PMD) and reduction of intra-channel
non-linear transmission impairments (Self Phase Modulation [SPM] and non-linear phase
noise). The line side optics of the 43SCX4/43SCX4E OT can be tuned to any of the 99
wavelengths in the extended C-band.
Wavetracker is supported on the line interface for optical power auto-management in
1830 PSS. For the interoperability application with LambdaXtreme, Wavetracker is
turned off.
....................................................................................................................................................................................................................................
1830 PSS
5-171
Issue 1 June 2013

....................................................................................................................................................................................................................................
The client interfaces support XFP pluggable modules (B&W and CWDM). The following
client signal types are supported:
OC-192/STM64
10GBE (GFP-F, GFP-P, CBR11096, CBR11049)
OTU2 (10.709, 11.049, 11.096)
FC800
43SCGE1 OT
The 43SCGE1 is a 43G Single Port Tunable Coherent GBE Transponder (1 client).
The following client signal type is supported:
40GbE LAN
43STA1P OT
The 43STA1P is a 3-slot wide, full height 43G Single Port Tunable Anyrate Add/Drop
Transponder. It contains transmit and receive optics as well as multiplexer, driver,
clock/data recovery, demultiplexer, and control functionality.
The 43STA1P accepts a single OC-768/STM-256 client signal and an OTU3 Line
interface with full-band tunable optics. The line interface can be used to select any one of
88 channels (50 GHz spacing). Channel frequency can be provisioned automatically or
manually.
The following signals are supported on the line side:
OTU3
The following signals are supported on the client side:
OTU3
OC-768/STM-256
43STX4 OT
The 43STX4 OT is a three slot wide, full height OT that accepts up to four bi-directional
sub-43G client signals and multiplexes them into the 43G DWDM line signal. The
module has XFP pluggable modules on the client interface ports, and uses LC type optical
connectors on all interfaces.
OC192/STM64
OTU2
10GbE
....................................................................................................................................................................................................................................
1830 PSS
5-172
Issue 1 June 2013

....................................................................................................................................................................................................................................
Up to 4 independent client signals can be multiplexed and sent out on the line side. Any
combination of client signals is supported. On the line side, the 43STX4 OT supports
full-band tunable optics, capable of supporting all 44 even channels (100GHz spacing).
The frequency of the channel can be provisioned manually or automatically.
43STX4P OT
The 43STX4P transponder accepts up to four bi-directional sub-43G client signals and
multiplexes them into the 43G DWDM line signal. The module has XFP pluggable
modules on the client interface ports, and uses LC type optical connectors on all
interfaces.
OC192/STM64
OTU2
10GbE
Up to four independent client signals can be multiplexed and sent out on the line side.
Any combination of client signals is supported.
On the line side, the 43STX4P OT supports full band tunable line side optics, capable of
supporting 44 even channels (at 100GHz spacing). The frequency of the channel can be
provisioned manually or automatically. It also supports eVOA management and WT
encoding functions.
MVAC/MVAC8B
The Multiple Variable Attenuator Card (MVAC/MVAC8B) contains an array of eight fast
optical VOA and WaveTracker encoders to condition alien wavelengths to pass through
the TOADM system.
The MVAC supports unidirectional (single-strand) connections to and from its ports. The
MVAC8B supports bidirectional connections to and from its ports.The alien wavelength
passes through the MVAC/MVAC8B when added to the network for Wavelength Tracker
encoding and monitoring. When the wavelength is dropped from the network, it does not
go through the MVAC.
The MVAC is a half-height module and the MVAC8B is a full-height module. These can
be configured in any of the universal slots in the 1830 PSS-32/PSS-16/PSS-32S shelves.
MVAC ports do not support bidirectional connections. MVAC8B do support bidirectional
connections.
SVAC
The single port variable attenuation card is used as a bridge by the compatible wavelength
transponders into Alcatel-Lucent 1830 PSS-36/PSS-32/PSS-16 DWDM domain.
....................................................................................................................................................................................................................................
1830 PSS
5-173
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following are the basic functions provided by SVAC as demarcation and adaptation
for so-called alien (foreign wavelength) channel:
Encodes theWavelength Tracker wave keys onto the optical channel

Automatically adjusts a variable optical attenuator (VOA) on each channel to set the
channel output optical power to the target level determined by NE SW
Monitors incoming alien wavelength optical power level and appropriate alarming.
SVAC is implemented as a half-height module that can be configured in any of the
universal slots in the universal shelves.
Channel spacing rules for 10G channels adjacent to 40G channels
Channels +/- 50GHz from a 40G signal may not be used unless the 40G signal has passed
through an ITLB or a 50GhZ WSS (drop <or thru> direction of a CWR8-88). The
restrictions include the following:
1. If the 40G demand enters through a colorless port (CLS) on the CWR8-88, then the
NE will block 10G channels from being allowed on the adjacent (50GHz away)
channels for the same optical line as the 40G channel. This restriction applies to add,
mesh, and thru channels at this node only. The restriction is limited to the node at
which the 40G channel is added colorlessly. The remainder of the path is not restricted
until it possibly passes through a regeneration location. If the 40G channel is added
colorlessly at both ends, then the restriction occurs for the optical lines at each end of
the demand.
2. For 40G demands - there are no restrictions on neighbor channels 100GHz away.
3. If the 40G demand enters through a SFD44/ITLB/CWR8-88, then there is no
restriction on neighbor (50GHz away) channels.
4. If the 40G demand enters through a SFD44/CWR8 or through a colorless port (CLS)
on the CWR8, then the NE will block channels from being allowed on the adjacent
(50GHz away) channels for the length of the demand route in the network until after it
passes thru the 50GHz WSS on the CWR8-88, or passes thru an ITLB.
If the 40G demand makes a mesh connection from a CWR8 towards a CWR8-88 (it is
a mesh add channel at the CWR8-88), then the NE will block 10G channels from
being allowed on the adjacent (50GHz away) channels for the same CWR8-88 optical
line as the 40G channel. This restriction applies to add, mesh, and thru channels at this
node. There would be no restrictions further down the route until the next
regeneration location.
Note: The CWR8-88 end terminals must be co-located. The loss budgets are designed
for fiber jumper loss only between the NEs and not for intervening spans.
....................................................................................................................................................................................................................................
1830 PSS
5-174
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision a card.

The WebUI supports View, Modify, Create, and Delete card-level functions and the
pre-provisioning of a card in an empty slot.
Related information
See OT slot/card provisioning (p. 5-154).

Before you begin
Instructions
Note: For provisioning 2-slot height cards and 2-slot width cards, adjacent slots must
be empty.
...................................................................................................................................................................................................
Select an empty slot from the equipment tree for pre-provisioning of a card and select the
Provision/Info function.
Result: The Provision Card screen is displayed.
...................................................................................................................................................................................................
Enter card parameters in the respective fields and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-175
Issue 1 June 2013

Provision Card
....................................................................................................................................................................................................................................
Provision Card
Attribute
Value/Format
Additional Info
Provisioned Type

specified shelf and slot>
Type of card
Primary State
In Service
Specifies the service state of

the card.
In Service, AINS
Out of Service
....................................................................................................................................................................................................................................
1830 PSS
5-176
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view / modify card properties.

The WebUI supports View, Modify, Create, and Delete card-level functions and the
pre-provisioning of a card in an empty slot.
Related information

Before you begin
Instructions
...................................................................................................................................................................................................
Select the card from the equipment tree.

Result: Slot Settings and Circuit Pack Information are displayed under the Details
tab.
Note: The Primary State (PST) setting of specific cards can be provisioned from
this screen. A card cannot be placed Out of Service (OOS) if any ports on the card
are in service.
...................................................................................................................................................................................................
To modify card properties, select the Provision/Info function.

Result: Provisionable card properties are displayed.
Note: The units displayed are dependent on the value of the system setting. If set
to Celsius, the attribute values are displayed in Celsius. If set to Fahrenheit, the
attribute values are displayed in Fahrenheit.
...................................................................................................................................................................................................
Enter appropriate values in the respective fields and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-177
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view card inventorys.

Related information

Before you begin
Instructions
The WebUI supports retrieving and displaying all provisioned and equipped cards in the
NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Inventory > Card.

Result: Card Inventory is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-178
Issue 1 June 2013

Card Inventory
....................................................................................................................................................................................................................................
Card Inventory
Attribute
Value/Format
Additional Info
Shelf
The shelf where the card is

located in the NE.
Slot
The slot where the card is

located in the specified shelf.
Status
Equipped
Provisioned
Indicates whether the card is

in a pre-provisioned state or is
present in the slot.
Card Type

Value of card type

pre-provisioned by the user or
present in the slot.
Software Load
<0-20 chars>
The software release that is

currently running on the card.
Company ID
<0-4 chars>
The card manufacturer
Mnemonic
<0-8 chars>
The Alcatel-Lucent
mnemonic for the card.
CLEI
<0-10 chars>
The Common Location

card.
Unit Part Number
<0-14 chars>

number for the card.
<0-14 chars>

number for the software
running on the card.
Factory ID
<0-4 chars>
The identifier for the factory

where the card is
manufactured.
Serial Number
<0-16 chars>
The serial number of the card.
Date
<0-6 chars>
The date the card was

manufactured.
Extra Data
<0-46 chars>

populated based on the card
type.
....................................................................................................................................................................................................................................
1830 PSS
5-179
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view pluggable module inventory.

Note: The following ports have pluggable modules (XFP/SFP/CFP):
OT client and VA ports

112PDM11, 11DPM12, 11QPA4, 11QPEN4, 11QPE24, 11DPE12(A/E), 4DPA4,
4DPA2 line ports
10AN10G, 11QCUPC, 130SCUP, 24ANM, 24ET1GB ports
A2325A/AHPHG/AHPLG/ALPHG/AM2325A, OSC ports
A2P2125, AM2125A, AM2125B, AM2318A and OSCT OSCSFP ports

MVAC G ports
Related information

Before you begin
Instructions
The WebUI retrieves and displays pluggable module inventory for all applicable cards in
the NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Inventory > Pluggable Module.

Result: The Pluggable Module Inventory is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-180
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Port
<shelf/slot/port>
Identifies the port where the

pluggable module is located.
Vendor
<0-16 chars>
Indicates the manufacturer of

the pluggable module.
Module Type
<0-8 chars>
Indicates the pluggable

module type used in
providing physical layer
function on the port.
CLEI
<0-10 chars>
The Common Location

pluggable module.
Unit Part Number
<0-14 chars>
Unit part number of the

pluggable module.
<0-14 chars>
Software part number of the

pluggable module.
Factory ID
<0-4 chars>
The identifier for the factory

where the pluggable module
is manufactured.
Serial Number
<0-18 chars>
The serial number of the

pluggable module.
Date
<0-6 chars>
The date the pluggable

module was manufactured.
Frequency
{9170~9605} for DWDM
The frequency of the

pluggable module.
{1471~1611} for CWDM

{850, 1310, 1490, 1530,
1550} for B&W
Max Case Temp
<0-4 chars>
The maximum case

temperature of the pluggable
module.
Interchangeability Marking
<0-6 chars>
Applicable for CFPs only.
Acronym Code
<0-12 chars>
Applicable for CFPs only.
Extra Data
<0-46 chars>

populated based on the
pluggable module type.
....................................................................................................................................................................................................................................
1830 PSS
5-181
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to switch protection (EC/MTC1T9).

Note: The controller supports duplex mode (i.e., redundancy). If the standby
controller is equipped, the WebUI will allow the user to initiate a switch between the
inactive and the active controller.
The active controller will deny any and all requests from CLI, WebUI and PhM
when a switchover is taking place.
The active controller will deny manual requests for a switchover when a backup
or restore is taking place.
The system will abort any backup or restore that is taking place if an automatic
switchover takes place.
Before you begin
Instructions
...................................................................................................................................................................................................
Select the controller from the equipment tree and select the Protection Switch tab.
Result: The Controller Protection Switch Settings screen is displayed.
...................................................................................................................................................................................................
To manually switch to the inactive controller select the Force Protection Switch option
and click Submit.
Note: A switch is not allowed if:
Protection Setting of the selected card = Unequipped
For PSS-16 shelf:
The selected card is in slot 2 and slot 12 is unequipped.

For PSS-32 shelf:
The selected card is in slot 1 and slot 18 is unequipped

....................................................................................................................................................................................................................................
1830 PSS
5-182
Issue 1 June 2013

....................................................................................................................................................................................................................................
For PSS-32S shelf:
Result: The WebUI displays a warning to the user indicating that the active and
standby controller will be rebooted and all users will be logged off. The user will be
allowed to continue with the request or cancel. Upon continuing with the request, the
WebUI will logout the user.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-183
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Protection Setting
Active
Activity state of the controller

card.
Inactive
Unequipped
Unknown
Standby Controller Ready to
Protect
Yes
Force Protection Switch
(checkbox)
No
Indicates whether a standby

controller is available and
ready for a protection switch.
Initiates the protection switch
to the standby controller (in
redundant configurations).
....................................................................................................................................................................................................................................
1830 PSS
5-184
Issue 1 June 2013

Procedure 5-39: Upgrade EC (in-service upgrade from

simplex to duplex)
....................................................................................................................................................................................................................................
Procedure 5-39: Upgrade EC (in-service upgrade from simplex

to duplex)
When to use
Use the following procedure to upgrade EC (in-service upgrade from simplex to duplex).
Before you begin
Instructions
...................................................................................................................................................................................................
Remove any EC pack from slot 18.

...................................................................................................................................................................................................
Insert the EC pack into slot 1.

...................................................................................................................................................................................................
Download, install, and activate software.

...................................................................................................................................................................................................
Remove and re-seat the EC in slot 1. Allow to boot completely.

Result: In service upgrade to EC pack is complete.
Note: If another pack needs to be upgraded, place it in slot 1 and perform the
procedure again.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-185
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to reboot card.

Note: The user can request a manual reboot of a specific card (on cards that support
this feature). Both warm and cold restarts are supported. For a cold restart, the WebUI
displays a warning indicating that service may be affected. The user is allowed to
continue with the request or cancel. The WebUI will not allow a reboot request if the
card is not equipped (i.e., the card is pre-provisioned but is not present in the shelf
(see Manual restarts (reboot) (p. 5-22)).
Before you begin
Instructions
...................................................................................................................................................................................................
Select the card from the equipment tree and select the Reboot tab.
Result: The Reboot Options screen is displayed.
...................................................................................................................................................................................................
Select either Warm Reboot or Cold Reboot and click Submit.

Note: After a cold reboot, it is necessary to perform Clear bin in order to have a
clean PM collection period.
Note: On warm rebooting the OPSA/OPSB pack, "Automatic switch to working" /
"Automatic switch to protection" message is raised, although no actual switching
takes place.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-186
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Additional Info
Warm Reboot
A warm reboot reinitializes the card software

only and is not service affecting.
Cold Reboot
A cold reboot reinitializes the card hardware

and software and is service affecting.
....................................................................................................................................................................................................................................
1830 PSS
5-187
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to delete a card.

Note: The card must support deletion and the card must be in a valid state for
deletion.
Before you begin
Instructions
...................................................................................................................................................................................................
Select the card from the equipment tree and select the Delete tab.
Result: The Delete Card screen is displayed.
...................................................................................................................................................................................................
Select option to Delete this Card and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-188
Issue 1 June 2013

Delete Card
....................................................................................................................................................................................................................................
Delete Card
Attribute
Value/Format
Additional Info
Provisioned Type

Value of card type.
Primary State
In Service - Normal
Indicates the current service

state of the card.
In Service - Abnormal
Out of Service - Autonomous
Out of Service - Management
Out of Service - Auto and
Management
Secondary State
Additional information about

the status of the card.
Multiple values may apply.
Delete this Card
Select to delete the card.
....................................................................................................................................................................................................................................
1830 PSS
5-189
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port/facility states
Primary states applicable to port entities are:
IS, IS-NR to indicate In_Service, Normal state. The entity is capable and allowed to
provide its provisioned functions. (IS and IS-NR are used interchangeably.)
IS-ANR to indicate In_Service_Abnormal state. The entity is capable of most
functions, is allowed to provide its provisioned functions, but is operating in a
degraded or abnormal state (e.g., non-alarmed BER Signal Degrade threshold
crossing on an OCn or STS).
OOS-AU to indicate Out_Of_Service-Autonomous state. The entity is not available
for providing its provisioned functions but the entity is not intentionally suspended by
external management command (from an OS or craft interface) from performing these
functions. In general, the cause of the incapability is due to an unsolicited autonomous
event detected in the system or in the associated network (e.g., LOS detected).
OOS-AUMA to indicate Out_Of_Service-Autonomous_and_Management state. The
entity is not available for providing its provisioned functions because an OOS-AU
state transition has occurred and the entity is intentionally suspended by external
management command (from an OS or craft interface) from performing its
provisioned functions.
OOS-MA to indicate Out_Of_Service-Management state. The entity is intentionally
suspended by external management command (from an OS or craft interface) from
performing its provisioned functions, but the entity may still be operationally capable
of performing its provisioned functions.
Secondary states applicable to port entities are:
AINS to indicate Automatic In-Service state. The facility is in a delay transition (to
IS) state. The transition to IS is pending on the correction of off-normal conditions on
the facility (such as FAF for termination point). Alarms will not be generated if AINS
is present. Once the off-normal conditions are cleared, the facility will transition to IS
according to the autonomous rules of the OOS-AU state. When using the ENT
command to provision an entity, if the requested state in the command is IS and the
required resource is not present (such as circuit pack is not present for the equipment
or valid signal is not present for the termination point), then the entity will enter the
OOS-AU state and alarms will be generated. However, if the AINS value is also
present in the SST field in the ENT command, then no alarms will be generated.
FAF to indicate Facility Failure state. The associated facility entity has failed, (e.g.,
LOS, LOF condition).
FLT applies to ports with pluggable modules and indicates pluggable module failure,
mismatch or module missing condition.
MT to indicate when a port is in maintenance. It generates traffic and monitors for
faults, but it only generates non-reported conditions.
....................................................................................................................................................................................................................................
1830 PSS
5-190
Issue 1 June 2013

....................................................................................................................................................................................................................................
SGEO to indicate Supporting Entity Outage. The associated supporting entity has
failed or is out-of-service due to management action (OOS-MA or OOS-AUMA).
UAS to indicate Unassigned. The entity has not been assigned with the necessary
provisioning data. No service activity or maintenance activity (including monitoring,
testing, or service recovery) is permitted in this state since the necessary data has not
been assigned.
Port/facility provisioning behavior
The following applies to port/facility provisioning:
The NE allows the client port object entity to be created and provisioned. Attribute
values identified as default are set initially unless they are explicitly defined in the
provisioning command.
The NE allows a modification of the provisioned parameters of a port object entity.
The NE allows deprovisioning of a provisioned port entity.
The NE allows retrieving the provisioned parameters and the state of a port object
entity.
11STAR1/11STAR1A OT port state provisioning
The states of the C1 and L1 ports are provisioned independently. The following port states
are supported:
Up - Provisioning the state to Up enables the port.

Down - Provisioning the state to Down disables the port
mt - Provision the state to mt to set the admin state to maintenance
ains - Provision the state to ains to set the admin state to Automatic In-Service. When
in this state, the port is allowed to transition to the in-service (Up) state if it is
operationally capable. That is, when all alarms on that port have cleared and the
ainstimer has expired. When in this state, the user can choose from the following:
configure the properties of the ainstimer to use either the system value, or to enter
the number of hours and minutes (1 minute to 96 hours). The default value of the
ainstimer is system.
Set ains to enabled
Set ains to disabled
11STAR1/11STAR1A client port provisioning
The user can provision the 11STAR1 OT for the following client signal types:
10GbE LAN
8G Fibre Channel (FC800) - 11STAR1A only
10G Fibre Channel (FC1200)

OTM-0.2 (OTU2)
....................................................................................................................................................................................................................................
1830 PSS
5-191
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC-192
STM-64
10GbE LAN client port provisioning
The following attributes are provisionable on the 11STAR1 C1 interface when the signal
type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
Attribute Definition
Specifies the channel frequency for the client port.
Enter this keyword to display the current setting. To change the
setting, enter this keyword followed by one of the following values:
encmode
errfrmdrop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Encapsulation mode. This attribute is used to provision the

encapsulation mode used to map the 10GbE LAN signal. Select from
one of the following:
GFP-F - (Standard, frame-based GFP encapsulation mode)
GFP-P - (Proprietary GFP encapsulation mode, semi-transparent)
cbrlan11.049 - (Transparent mode, no GFP)
Errored Frame Drop Mode. This attribute, when enabled, will discard
all received errored frames. Select either:
Enabled - Discard all ingress errored frames.
Disabled (default) - Do not discard all ingress errored frames.
....................................................................................................................................................................................................................................
1830 PSS
5-192
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
Pluggable module type. This attribute specifies the pluggable module
type expected in the socket identified by the port AID. Enter one of
the acceptable Client port moduletype values:
10GB-ZR
10GB-SR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C
Auto If this value is configured, then the network element will

accept a pluggable module from the list of modules supported by
Alcatel-Lucent.
User - If the user wants to use a pluggable module that is not on

the Alcatel-Lucent qualified list of pluggable modules, without
generating an alarm, set this attribute to user.
Attribute that controls the status of the client-side transmitter during

signal failures on the line port, or when a far-end failure signal is
received on the line side. Enter one of the following:
laserOn (default) transmitter stays on
laserOff turn off the transmitter
8G fibre channel (FC800) client port provisioning (11STAR1A only)
The following attributes are provisionable on the 11STAR1A C1 interface when the signal
type is provisioned to FC800:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-193
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
X8FCLC-L
X8FCSN-I

Alcatel-Lucent.

Default: Auto
encmode
Specifies the encapsulation mode used to transport the 8G- FC client

signal. Enter this keyword followed by the value of gfp-t.
Default: gfp-t
losprop

10G fibre channel (FC1200) client port provisioning
The following attributes are provisionable on the 11STAR1 C1 interface when the signal
type is provisioned to FC1200:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-194
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
10GB-SR
XI-64.1
XL-64.2C
XS-64.2C

Alcatel-Lucent.


OC-192 or STM-64 or 10GbE WAN PHY client port provisioning
The following attributes are provisionable on the 11STAR1 C1 interface when the
provisioned signal type is either OC-192, STM-64, or 10GbE WAN PHY:
Provisionable
Attribute
channel
J0_ex
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Expected J0. Configure expected J0. Enter a value that depends on the
J0 format selected (1-byte or 16-byte):
15-character string if the format is 16-byte
byte in Hex format if the value of j0_fmt is 1_byte
....................................................................................................................................................................................................................................
1830 PSS
5-195
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
J0_fmt
trccmp
moduletype
losprop
sdth
J0 format Configure the J0 format. Select from one of the following:
1 - Configure J0 format to 1-byte mode.
J0 trace comparison. Choose from one of the following:
Enable - Enable J0 comparison.
Disable - Disable J0 comparison.

10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


Attribute that specifies the BER threshold to declare a Signal Degrade

condition. Enter a value from the following range for the bit error rate,
expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6
Attribute that specifies the BER threshold to declare a Signal Fault

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
....................................................................................................................................................................................................................................
1830 PSS
5-196
Issue 1 June 2013

....................................................................................................................................................................................................................................
OTU2 client port provisioning
provisioned client signal type is OTU2:
Provisionable
Attribute
channelrx
Specifies the receive channel frequency. Not settable for internal
topology connections.
channeltx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the transmit channel frequency.

fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Forward Error Correction Type. Enter one of the following values:
NOFEC - No forward error connection (i.e., FEC is disabled)
RSFEC - Configure Reed-Solomon FEC
Note: Changing fectype while admin status is 'up' can cause loss of
traffic/data link (GCC). Changing fectype should only be made in
'down' state.
gccstat
gcctype
GCC0 Status. Enter one of the following values:
Set to enabled to enable GCC1/GCC2/GCC3 processing
Set to disabled to disable GCC0/GCC2/GCC3 processing (default)
Specifies which GCC communication channel type will be selected.

Values: GCC0; GCC1; GCC2
Default: GCC0
....................................................................................................................................................................................................................................
1830 PSS
5-197
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
ospf helloint
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


HELLO INTERVAL of the OSPF interface. By default, the interface is

set to 10 seconds. This is the time elapsed before the next HELLO
PDU is sent.
Range: 1-65535
ospf deadint
DEAD INTERVAL of the OSPF interface. By default, the Interface is

set to four times the value of the HELLOINT, so the default is 40
seconds. The dead interval is a timer used to timeout inactive
adjacencies. The dead interval value must always be greater than the
hello interval value.
ospf metric
METRIC or Cost of the OSPF interface. By default, the interface is set

to 30.
Range: 1-65535
ospf md5key
Key is used for MD5 128bit hash value key calculation. This
parameter is mandatory if md5keyid is entered. The value is 1 to 16
ASCII characters. The string can be 1 to 16 uppercase or lowercase
alphanumeric characters; the first character can not be a numeric
value. This parameter is mandatory if md5_status is enable.
Default: NUL ()
....................................................................................................................................................................................................................................
1830 PSS
5-198
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5keyid
md5keyid is used for MD5 128bit hash value key calculation. This
parameter is mandatory if md5staus is enable.
Range: 1- 255
Default: 1
ospf md5status
Set to enable - the MD5 authentication is activated on the OSPF

area.
Set to disable - the MD5 authentication is not required on the

OSPF area.
This parameter can be set to enable only if a md5key and md5keyid

have been set.
Default: disable
packettype
The packet type describes if it is standard packet or not. If it is

standard the mtu size can be configured. If the packettype is
non-standard the mtu size is default.
Default: nonstd
mtu
Maximum transmission unit. The default is 1473 Bytes.

Range: 576 - 1500
oturate
OTU rate Specifies the client OTM0.2 rate. Enter one of the following
values:
10.709 (Gb/s) (default)
11.049 (Gb/s)
11.096 (Gb/s)
....................................................................................................................................................................................................................................
1830 PSS
5-199
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti
Configure Trail Trace Indentifier attributes:
exp_sapi Specifies the expected incoming Source Access Point

Identifier. Enter this keyword followed by 15 ASCII characters,
enclosed in quotation marks. Default: Null character (15 bytes
each with hex value 00)
tx_sapi Specifies the transmitted Source Access Point Identifier.

Enter this keyword followed by 15 ASCII characters, enclosed in
quotation marks. Default: Null character (15 bytes each with hex
value 00).
timmresp Optical channel Path Trace Identifier Mismatch

Response. Enter either of the following:
Set to enable to enable TIMM defect detection.
Set to disable to disable TIMM defect detection. (default)
trccmp Optical channel Trace compare. This keyword enables

and disables the comparison between the incoming sapi value and
the provisioned (i.e., exp_sapi) value.
Set to Enable to enable comparison
Set to Disable to disable comparison (default)
ODU2 Client Port Provisioning
Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
1830 PSS
5-200
Issue 1 June 2013

....................................................................................................................................................................................................................................
11STAR1/11STAR1A line port provisioning
The line interface on the 11STAR1/11STAR1A OT supports provisionable parameters at

the OTU2 and ODU2 transport layers, as defined in the following tables.
OTU2 line port provisioning
The following OTU2 attributes are provisionable on the 11STAR1/11STAR1A L1

interface:
Provisionable
Attribute
channel
Attribute that configures the frequency of the tunable transponder.
Enter one of the following: {9605, 9600, 9595, 9590, 9585, 9580,
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9215, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
fectype
Forward error correction mode. Specifies the type of forward error

correction on the interface port. Enter one of the following values:
EFEC - Enhanced FEC (default)
RSFEC - Reed-Solomon FEC
EFEC2 ALU Enhanced FEC (only applicable to 11star1a card)
'down' state.
RegenResp
Configure OTU2 Regeneration Response for OPS configuration
Set to LaserOn Line port laser is turned on if there is no client

OTU2 LOS/LOF alarm
Set to LaserOff Line port laser is shut down if client OTU2

LOS/LOF alarm is detected
Default: LaserOn
gccstat
gcctype
Set to disabled to disable GCC0/GCC2/GCC3 processing (default)

Default: GCC0
....................................................................................................................................................................................................................................
1830 PSS
5-201
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf helloint
PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 30.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
1830 PSS
5-202
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




Enter a string of 15 ASCII characters, enclosed in quotation
marks. Default: Null character (15 bytes each with hex value 00)
ODU2 line port provisioning
The following ODU2 attributes are provisionable on the 11STAR1 L1 interface:

Provisionable
Attribute
ptmmresp
ODU2 Payload Type Mismatch Response. Specifies whether the OT
will take a consequent action or pass the received signal. Enter one of
the following:
enabled enable the consequent action
disabled disable (turn off) the consequent action (default)
....................................................................................................................................................................................................................................
1830 PSS
5-203
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




11STMM10 OT port state provisioning
The states of the C1-10 and L1 ports are provisioned independently. The following port
states are supported:

Set ains to enabled
11STMM10 client port provisioning
The user can provision the 11STMM10 OT for the following client signal types:
OTU1
GbE
....................................................................................................................................................................................................................................
1830 PSS
5-204
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC3
STM1
OC12
STM4
OC48
STM16
CBR2G5
FC100
FC200
FC400
For each of the above client signal types, the user can provision different attributes as
described in the following subsections.
GbE client port provisioning
The following attributes are provisionable on the 11STMM10 C1-10 interfaces when the
signal type is provisioned to GbE :
Port Attribute
channel
Description
Specifies the wavelength of the pluggable module.
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the encapsulation mode used to transport the 10GbE LAN

signal. Enter this keyword followed by one of the following values:
gfp-f specifies the use of the Generic Framing protocol (ITU-T

G.7041)
gfp-p Generic Framing Protocol, Proprietary, where the client

Ethernet frame preamble is preserved.
Default: previously existing value

errfrmdrop
Specifies whether inbound error frames are discarded or passed. This

attribute is only meaningful for GFP transport modes. Enter this
keyword followed by either of the following values:
....................................................................................................................................................................................................................................
1830 PSS
5-205
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
timeslot
[line | vts]
Description
Specifies how the near end client facing transmitter port reacts to a
Loss of Signal (LOS), Loss of Frame (LOF) or other defect from the
far-end client-facing receiver. Enter this keyword to display the
current setting. To change the setting, enter this keyword followed by
laserOn transmitter stays on (default)
Specifies the pluggable module type to be used on the specified

interface port. Enter this keyword to display the current setting. To
change the setting, enter this keyword followed by one of the
following:
Enter one of the acceptable Client port moduletype values:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A
SS-16.2C

Alcatel-Lucent.

generating an alarm, this attribute should be set to user.
Specifies the time slot on the line port and on the ODU1. Enter this
keyword followed by the following:
Enter the keyword line to specify the ODU1 on the line port,
followed by a value from the following range:
{0-4}
Enter the keyword vts to specify the time slot of the ODU1,
Range: {0 or 1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46}
Value 0 in both cases indicates no time slot assignment
....................................................................................................................................................................................................................................
1830 PSS
5-206
Issue 1 June 2013

....................................................................................................................................................................................................................................
CBR2G5 client port provisioning
signal type is provisioned to CBR2G5 :
Port Attribute
channel
Description
Specifies the wavelength of a pluggable module.
sdth
sfth
jo
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the received BER threshold required to raise a signal defect

condition. Enter this keyword followed by a value for the bit error
rate, expressed as 10-n.
Range: {10-5, 10-6, 10-7, 10-8, 10-9}
Default: 10-6
Specifies the received BER threshold for Excessive BER defect

declaration. Enter this keyword followed by a value for the bit error
Range: {10-3, 10-4, 10-5}
Default: 10-3
Configure J0 attributes:
j0_ex Expected J0. Enter this keyword followed by either one of

the following:
1-byte in Hex format if the value of j0_fmt is 1_byte
j0_fmt J0 format. Enter this keyword followed by a value for the

J0 format.
<value>=1: configure J0 format to 1-byte mode
<value>=16: configure J0 format to 16-byte mode (default)
trccmp J0 trace compare. This keyword enables and disables the

comparison between the incoming J0 value and the provisioned
(i.e., expected) value.
Set to enable to enable comparison
Set to disable to disable comparison (default)
....................................................................................................................................................................................................................................
1830 PSS
5-207
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
losprop
mappingmode
moduletype
timeslot
[odu1 | vts]
Description
Specifies the type of mapping of the CBR2g5 signal into the ODU1
structure
bitsync (default)
async

following:

Sl-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A
SS-16.2C

Alcatel-Lucent.

Specifies the time slot on the line port. Both odu1 and vts must be
entered at the same time. Enter this keyword followed by the
following:
Enter the keyword odu1 to specify the ODU1 tributary within the
line port, followed by a value from the following range: {0-4}
Enter the keyword vts to specify the STS3c time slot within the
ODU1, followed by a value from the following range: {0 or 1, 4,
7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}
Value 0 indicates no time slot assignment
....................................................................................................................................................................................................................................
1830 PSS
5-208
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC3/OC12/OC48 and STM1/STM4/STM16 client port provisioning
signal type is provisioned to OC3/OC12/OC48 and STM1/STM4/STM16 :
Port Attribute
channel
Description
sdth
sfth
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the received BER threshold required to raise a signal defect

condition. Enter this keyword followed by a value for the bit error
Range: {10-5, 10-6, 10-7, 10-8, 10-9}
Default: 10-6
Specifies the received BER threshold for Excessive BER defect

declaration. Enter this keyword followed by a value for the bit error
Range: {10-3, 10-4, 10-5}
Default: 10-3
....................................................................................................................................................................................................................................
1830 PSS
5-209
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
jo
losprop
Description

the following:

J0 format.
j0_tx Transmitted J0. Enter this keyword followed by either one

of the following:

- timmresp Optical channel Path Trace Identifier Mismatch

Response. Enter this keyword followed by either of the following:
Set to enabled to enable TIMM defect detection.
Set to disabled to disable TIMM defect detection. (default).

Note: When the head-end OT has client LOS, it sends CMF
downstream. For Sonet/SDH signal rates, the LOS recovery time
may cause a slight delay in traffic restoration.
....................................................................................................................................................................................................................................
1830 PSS
5-210
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
moduletype
timeslot
[line | vts]
Description
following:

For OC3/STM1:
SL-1.1
SL-16.2C
SS-16.1A
SS-16.2C
For OC12/STM4:
SL-4.1
SL-16.2C
SS-4.1
SS-16.1A
SS-16.2C
For OC48/STM16:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A
SS-16.2C

Alcatel-Lucent (default).

Specifies the time slot on the line port and on the ODU1. Enter this
keyword followed by the following:
Enter the keyword line to specify the time slot on the line port,
{0-4}
Enter the keyword vts to specify the time slot of the ODU1,
For OC-3 or STM1clients:
Range: {0 or 1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46}
For OC-12 or STM4 clients:
Range: {0,1,13,25,37}
For OC-48 or STM16 client:
Range: {0 or 1}
Value 0 indicates no time slot assignment

....................................................................................................................................................................................................................................
1830 PSS
5-211
Issue 1 June 2013

....................................................................................................................................................................................................................................
FC100/FC200/FC400 client port provisioning
Note: The 11STMM10 muxponder uses GFP-T encoding to transfer all traffic
generated by the FC equipment to the remote end of the circuit. GFP-T encoding
requires valid FC fill words in the FC signal used. (See paragraph at the end related to
FC test sets). The 11STMM10 does not provide buffer credit management and expects
the attached FC switches to be provisioned to handle all buffer credits over the
extended distance. For Brocade, best practice is to use the long distance LS mode.
11STMM10 1G/2G/4G FC doesnt support long distance LD mode.
Use of the 1830 11STMM10 is to extend an inter-switch link (ISL) over the DWDM
network. The expectation is the attached ports in the FC switch are provisioned to
G-port in Brocade systems and E-ports in Cisco Systems and have their speeds locked
to the rate to be used: i.e., the default auto-negotiation (AN) for speeds should not be
used- hard set to 4G, 2G or 1G should be used instead. Brocade licensing for distance
extension and calculation and provisioning of buffering should be coordinated with
local Brocade network engineering.
signal type is provisioned to 1, 2 or 4 Gb/s Fiber channel:
Port Attribute
channel
Description
fcmode
losprop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the FC interface type (Fibre Channel compliant with INCITS

x.320 or FICON). Enter this keyword followed by:
fc (default)
ficon
....................................................................................................................................................................................................................................
1830 PSS
5-212
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
moduletype
timeslot
[odu1 | vts]
Description
following:

For FC100 and FC200:
2FCLC-L
2FCSN-1
4FCLC-L
4FCSN-1
SS-16.1A
For FC400:
4FCLC-L
4FCSN-1


following:
7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}
Value 0 in both cases indicates no time slot assignment
Note: Port channel is either not set or typically set to 850. Assure that the right
multimode jumpers are used if 850nm is used and single mode fibers are used for
CWDM and 1310 and 1550 lasers.
Losprop shall be laserOff for interoperability with Brocade and Cisco FC Switches.
Other options shall be left to default. Brocade and Cisco FC switches need to be
provisioned port to specific line rate (4G, 2g or 1G) instead of using the
auto-negotiation speed option. Make sure FC switches are properly configured to use
the 1830 link as an ISL. Typically, an E-port and fabric switch provisioning and FC
buffer credit provisioning necessary for using 1830 in a FC transport application
across a distance.
Most common moduletype used is the 4FCSN-I for FC400.
....................................................................................................................................................................................................................................
1830 PSS
5-213
Issue 1 June 2013

....................................................................................................................................................................................................................................
Make sure the receiver powers are between the optical overload and the minimum
receiver sensitivity.
Timeslot needs to be set for 24 separate vts for FC400, and 12 separate vts for FC200
and 6 separate vts for FC100.
If Timeslot is set to numbers less than required, errored behavior or dropped frames
will occur- potentially without being reported.
The 11STMM10 is designed to transport valid FC fill word ordered sets (such as
IDLEs and ARBs) and valid FC frames as defined in INCITS T11 FC-FS-2. Many FC
test sets have several modes that do not comply with the fill word requirement. The
11STMM10 is NOT designed to transport FC signals that do not contain some fill
words because the 11STMM10 rate adapts to the different clocks at the FC switches
at both ends and will add or remove fill words as necessary to compensate for the
differences in clocks at both ends. Without opportunities for rate adaptation, internal
buffering will underflow or overflow and cause errors.
Provisioning the 11STMM10 to 4GFC transports can also be used to transport 4G
FICON. (also true at 2G and 1G rates).
FICON and FC are only differentiated at layer 4 and above of the protocol stack. The
11STMM10 pack only gets involved in layer 2 and below and therefore support
FICON and FC equally well when provisioned for FC.
Provisionable
Attribute
channelrx
channeltx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-214
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
RSFEC - Configure Reed-Solomon FEC (default)
'down' state.
Note: When interconnecting MSC and 11STMM10, the only
configuration supported is NOFEC. GCC termination on 10xANY
when FEC is enabled is not supported.
gccstat
ospf helloint
Enabled - Configure GCC0 status to enabled.
Disabled - Configure GCC0 status to disabled (default).

PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 40.
Range: 1-65535
ospf md5key
value. This parameter is mandatory if md5_status is enable
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
....................................................................................................................................................................................................................................
1830 PSS
5-215
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
mtu

Range: 576 - 1500
moduletype
losprop

following:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A
SS-16.2C
Auto (default) If this value is configured, then the network

element will accept a pluggable module from the list of modules
supported by Alcatel-Lucent.

far-end client-facing receiver.
setting, enter this keyword followed by one of the following:
....................................................................................................................................................................................................................................
1830 PSS
5-216
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf area
Specifies the area ID for the GCC0 channel. A valid area identifier
consists of four integer values separated by periods, for example
0.0.0.5. The specified area must have been previously configured on
the NE at the system-level.
Default: 0.0.0.0
timeslot [odu1
odu1_trib vts vts]
tti
following:
7, 10, 13, 16, 19, 22, 25, 28, 31, 34, 37, 40, 43, 46}


value 00).


....................................................................................................................................................................................................................................
1830 PSS
5-217
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


11STMM10 line port provisioning
The line interface on the 11STMM10 OT supports provisionable parameters at the OTU2
and ODU2 transport layers, as defined in the following tables.
The following OTU2 attributes are provisionable on the 11STMM10 L1 interface:

Provisionable
Attribute
channel
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
....................................................................................................................................................................................................................................
1830 PSS
5-218
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
efec- Enhanced FEC (default)
rsfec - Reed-Solomon FEC
'down' state.
tti




Note: The enhanced FEC allows the greatest span distances without regeneration, but
it does add the most delay to the transport of the signal. For the 11STM10 pack, an
end to end circuit using a total delay of 243, 235, and 231 microseconds for FC-100,
FC-200 and FC-400, respectively. Each 5 us of delay is equivalent to the delay in 1
km of fiber. These delays must be accounted for in the Fibre Channel switch buffer
credit calculation.
The EFEC with protection scheme is not allowed for deployments where the use of
RFEC is mandatory (I.e. EMC Distance Extension Solution).
The RSFEC allows for significant span distances without regeneration, and it has
greatly reduced delay to the transport of the signal. For the 11STM10 pack an end to
end circuit using a total delay of 101, 93, 89 microseconds for FC-100, FC-200 and
FC-400, respectively.
....................................................................................................................................................................................................................................
1830 PSS
5-219
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following ODU2 attributes are provisionable on the 11STMM10 L1 interface:

Provisionable
Attribute
ptmmresp
tti
the following:




11STGE12 OT port state provisioning
The states of the C1-C12 and L1 ports are provisioned independently. The following port

....................................................................................................................................................................................................................................
1830 PSS
5-220
Issue 1 June 2013

....................................................................................................................................................................................................................................
Set ains to enabled
11STGE12 client port provisioning
The following attributes are provisionable on the 11STGE12 C1-12 interfaces:

Port Attribute
channel
Description
autoneg
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Attribute that controls the status of auto-negotiation. Enter this

enabled
disabled (default)
Note: Auto-negotiation can be provisioned (enabled or disabled) only

when the port state is OOS (admin state=Down). When the admin
state is Up or Maintenance, provision of the auto-negotiation attribute
is not allowed.
Note: Performance times may be adversely affected on 11STGE12
ports which have autoneg=enabled. If so, set autoneg=disabled (for
both ports on both ends).
losprop
....................................................................................................................................................................................................................................
1830 PSS
5-221
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
moduletype
Description
following:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A


11STGE12 line port provisioning
The line interface on the 11STGE12 OT supports provisionable parameters at the OTU2
The following OTU2 attributes are provisionable on the 11STGE12 L1 interface:

Provisionable
Attribute
channel
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
....................................................................................................................................................................................................................................
1830 PSS
5-222
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
efec2- Enhanced FEC type 2 (default)
'down' state.
oturate
OTU rate. Specifies the line OTU2 rate. Enter one of the following
values:
Set to 11.049, for 11.049 Gb/s overclocked rate
Default: 11.096
tti




....................................................................................................................................................................................................................................
1830 PSS
5-223
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following ODU2 attributes are provisionable on the 11STGE12 L1 interface:

Provisionable
Attribute
pldtype
Specifies the value of the Payload Type field within the ODU2
payload overhead. pldtype has a default value and is based on the
encoded client signal.
ptmmresp
tti
Set to a value in the following range: {0-255}

the following:




11DPE12(A/E) OT port state provisioning
The states of the C1-C12, L1, L2, VA1, and VA2 ports are provisioned independently. The
following port states are supported:

....................................................................................................................................................................................................................................
1830 PSS
5-224
Issue 1 June 2013

....................................................................................................................................................................................................................................
Set ains to enabled
Note: For 11DPE12(E), the line-side laser is shut down if the port state is provisioned
to "down". The line-side laser is turned on if the port state is set to "up" or
"maintenance".
11DPE12(A/E) client port provisioning
The following attributes are provisionable on the 11DPE12(A/E) C1-12 interfaces:

Port Attribute
channel
Description
autoneg
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Attribute that controls the status of auto-negotiation. Enter this

enabled
disabled (default)
Note: Auto-negotiation can be provisioned (enabled or disabled) only

when the port state is OOS (admin state=Down). When the admin
state is Up or Maintenance, provision of the auto-negotiation attribute
is not allowed.
Note: Performance times may be adversely affected on 11DPE12(E)
ports which have autoneg=enabled. If so, set autoneg=disabled (for
both ports on both ends).
Note: When using electric 1GbE SFP (1000BASE-T), 11DPE12E
traffic cannot be up if Auto-Negotiation is enabled against the client
port. Auto-Negotiation should be disabled against the client port
(electric SFP) for the 1GbE traffic to work normally.
....................................................................................................................................................................................................................................
1830 PSS
5-225
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
ethmtu
Description
Specify the max transport unites on the specified port.
Enter this keyword to display the current setting. The range of the
value is 1518-9600 bytes.
Default: 9600
losprop
Note : this parameter can be provisioned only when the FlowCM is

APS/PCC or CCM
lptca
Specifies how the near end client facing transmitter port reacts to Link
pass through function (pass the Loss of Signal (LOS), Loss of SYNC
(LSS) or other defect from the far-end client-facing receiver).
disable disable the LPT consequent action
shutdownany turn off the transmitter when the client port any
flow has failure
shutdownall turn off the transmitter when the client port all
flows have failure
Default: disable
Note : this parameter can be provisioned only when the FlowCM is
CSF
....................................................................................................................................................................................................................................
1830 PSS
5-226
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
moduletype
ssmtrans
Description
following:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A
SS-16.2C

User If the user wants to use a pluggable module that is not on

Manually configure SSM/Quality Level Transmission in each port.

The value can be:
In SDH mode: ACT, PRC, SSU_A, SSU_B, SEC, DNU,NONE;
In SONET mode: ACT, PRS,STU, ST2, ST3E, ST3,DUS,NONE.
Default value is ACT.

Note: This parameter only takes effect only when config card
11DPE12A syncesupp is set to enable.
stpid
SVLAN Tag Protocol Identifier (STPID) it is used for CE-VLAN

tagged packets in QinQ mode.
Stpid1 The client stpid is provisioned with global

stpid1.(default)
Stpid2 The client stpid is provisioned with global stpid2.
Note: It is applicable only when the pack is in QinQ mode.

SYNCEOPRMODE
Configure port Synchronous Ethernet Operation Mode. When the port

is in SYNC mode, recovered clock of its input signal can be selected
as a reference clock to the system clock. When the port is in
NON-SYNC mode, the recovered clock of its input signal cannot be a
candidate to system timing references
The value can be sync or non-sync.
Default value is sync.
....................................................................................................................................................................................................................................
1830 PSS
5-227
Issue 1 June 2013

....................................................................................................................................................................................................................................
FE client port provisioning

Port Attribute
channel
Description
losprop
moduletype
stpid
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

following:

1000BLX10



stpid1.(default)
....................................................................................................................................................................................................................................
1830 PSS
5-228
Issue 1 June 2013

....................................................................................................................................................................................................................................
VTS client port provisioning
Note: Configure the C{1-12} client ports with the CE-VLAN ID map attributes on the
11DPE12(A/E) card. This command is only applicable when the card mode is set to
Subrate or QinQ mode.
Port Attribute
vts{1-10}
Description
Specifies the virtual time slot within the port.
The valid values are: vts1, vts2, vts3, vts4, vts5, vts6, vts7, vts8, vts9,
vts10.
....................................................................................................................................................................................................................................
1830 PSS
5-229
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
cmode
Description
Classification mode, it is used to differ classification mode in Q in Q
mode. The value of the cmode can be: SVLANID, CEVLANID, and
PORT.
CEVLANID: The CEVLANID is used for CVLAN traffic.
SVLANID: SVLANID is used for SVLAN tagged traffic. .
PORT: PORT is used for the fullrate service (fullrate service is

different fullrate mode), all the port packets which includes
CE-VLAN tagged, SVLAN tagged and un-tagged packets are
mapped into the line VTS. When the PORT is provisioned, the
port parameter PVID should only be NULL..
Untagged : When the cmode is configured as untagged mode, a

CEVLAN ID is provisioned for untagged mode. then the
incoming untagged and priority tagged packet and CVLAN
tagged which the VLAN ID is same as the provision CEVLANID
will be treated as a flow , and a SVLAN will be added , when the
flow is out from a client port ,the svlan will be popped . The
cevlan id for untagged mode can only be a signal value .The
default value is NULL.
The valid value for each cmode are following:
Value of CEVLANID: ID number or ID ranges separated by

comma:
ID Range: [1-4095], null
Default: null
Note: null string (zero-length) is used to indicate that no traffic
flow is mapped into the client VTS.
Value of SVLANID unique ID number.

ID Range: [2- 4094], null
Default: null
Value of untagged:unique ID number

ID Range : [1-4094], NULL.
Default: null
Value of PORT: All, NULL.

Default: null
In Q in Q, the client VTS/cmode mapping is unidirectional. Users

must specify the map direction. The valid directions are :
Egress the mapping direction is out from the port.
Ingress the mapping direction is into the port.
....................................................................................................................................................................................................................................
1830 PSS
5-230
Issue 1 June 2013

....................................................................................................................................................................................................................................
11DPE12(A/E) line port provisioning
The line interface on the 11DPE12(A/E) OT supports provisionable parameters at the

OTU2, ODU2, and 10GbE transport layers, as defined in the following tables.
The following OTU2 attributes are provisionable on the 11DPE12(A/E) L1,2 interface:
Provisionable
Attribute
channelrx
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None

channeltx
Specifies the transmit channel frequency. Not settable for internal

CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-231
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ethmtu
Specify the Ethernet max transport unites on the specified port. Enter
this keyword to display the current setting. The range of the value is
1518-9600 bytes.
Default: 9600
fectype

efec2- Enhanced FEC type 2 (default)
'down' state.
gccstat
gcctype
Specifies the status of GCC0 signal processing.
Set to enabled to enable GCC0 processing (default)
Set to disabled to disable GCC0 processing

Default: GCC0
Note: When GCCSTAT is enabled, the change of gcctype is denied.
ospf helloint

PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 30.
Range: 1-65535
....................................................................................................................................................................................................................................
1830 PSS
5-232
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5key
Default: NULL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status
If set to enable - The MD5 authentication is activated on the OSPF

area.
If set to disable - The MD5 authentication is not required on the OSPF
area
have been set
Default: disable
packettype

Default: nonstd
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
1830 PSS
5-233
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
interface port.
oturate
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C
Auto If this value is configured, then the network element

accepts the pluggable module. (Default)

OTU rate. Specifies the line OTU2 rate. Enter one of the following
values:
Default: 11.096
stpid


stpid1.(default)
....................................................................................................................................................................................................................................
1830 PSS
5-234
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti
Holdofftimer




Specifies whether this port will use a hold-off timer to delay taking a
consequent action for line failure.
Set to disabled Disabled holdoff timer
Set to enabled Enabled holdoff timer
Default: Disabled
compatibilityMode
Configure the compatibility mode. Available values:
defaultMode the port operates in the default mode which cannot

support interworking with 11dpe12.
11dpe12Mode the port operates in the 11dpe12 compatable

mode which supports interworking with 11dpe12.
Default: defaultMode.
The following ODU2 attributes are provisionable on the 11DPE12(A/E) L1,2 interface:
Provisionable
Attribute
pldtype
Specifies the value of the Payload Type field within the ODU2
payload overhead. pldtype has a default value and is based on the
encoded client signal.
....................................................................................................................................................................................................................................
1830 PSS
5-235
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ptmmresp
tti
the following:




....................................................................................................................................................................................................................................
1830 PSS
5-236
Issue 1 June 2013

....................................................................................................................................................................................................................................
10Gbe line port provisioning
The following 10Gbe attributes are provisionable on the 11DPE12(A/E) L1,2 interface:
Provisionable
Attribute
channelrx
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None

channeltx

CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W {850, 1310, 1550}
Not set: None

ethmtu
Specify the Ethernet max transport unites on the specified port. Enter
this keyword to display the current setting. The range of the value is
1518-9600 bytes.
Default: 9600
....................................................................................................................................................................................................................................
1830 PSS
5-237
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
interface port.
stpid
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C




stpid1.(default)
Default: stpid1.
portRole
Configure the port role. Available values are:
UNI
NNI
Default: NNI
pvid
Port VLAN ID The PVID is the CEVLAN ID for Untagged and

PriorityTagged Packets in QinQ mode. Enter this keyword followed
by an ID number.
Value range: 1 4094
Default: 1
....................................................................................................................................................................................................................................
1830 PSS
5-238
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
laserOn transmitter stays on
Default: laserOn
Note: this attribute can be provisioned is applicable only when the
portRole is UNI and FlowCM is APS/PCC or CCM.
lptca
Specifies how the near end client facing transmitter port reacts to Link
pass through function (pass the Loss of Signal (LOS), Loss of SYNC
(LSS) or other defect from the far-end client-facing receiver ). Enter
this keyword to display the current setting. To change the setting, enter
this keyword followed by one of the following:
disable disable the LPT consequent action
shutdownany-turn off the transmitter when the client port any

flow has failure
shutdownall-turn off the transmitter when the client port all flows
have failure
Default: disable
Note : this parameter can be provisioned only when the portRole is
UNI and the FlowCM is CSF.
Holdofftimer
Specifies whether this port will use a hold-off timer to delay taking a
consequent action for line failure.
Default: Disabled
VTS line port provisioning
Note: Configure the L{1-2} line ports with the classification mode map attributes in
Q in Q mode on the 11DPE12(A/E) card. This command is only applicable when the
card mode is set to QinQ mode.
Port Attribute
vts{1-100}
Description
Specifies the virtual time slot within the port.
The valid values are: vts{1-100}.
....................................................................................................................................................................................................................................
1830 PSS
5-239
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
cmode
Description
Classification mode, it is used to differ classification mode in Q in Q
mode. User must enter the keyword followed by specific cmode,
cmode_value and cmode_direction.
CEVLANID: The CEVLANID is used for CVLAN traffic.
SVLANID: SVLANID is used for SVLAN tagged traffic. .
Untagged : When the cmode is configured as untagged mode, a

CEVLAN ID is provisioned for untagged mode. then the
incoming untagged and priority tagged packet and CVLAN
tagged which the VLAN ID is same as the provision CEVLANID
will be treated as a flow , and a SVLAN will be added , when the
flow is out from a client port ,the svlan will be popped . The
cevlan id for untagged mode can only be a signal value .The
default value is NULL.
The valid value for each cmode are following:
Value of CEVLANID: ID number or ID ranges separated by

comma:
ID Range: [1-4095], null
Default: null
Note: null string (zero-length) is used to indicate that no traffic
flow is mapped into the client VTS.
Value of SVLANID unique ID number.

ID Range: [2- 4094], null
Default: null
Value of untagged:unique ID number

ID Range : [1-4094], NULL.
Default: null
Note: In 11DPE12E, when we use the CCM mode for FlowCM (flow
continuity monitoring), the line port ingress VTS SVLAN ID and line
port egress VTS SVLAN ID should be same. So when the pack
FlowCM is set to CCM and the line ingress VTS#i entity COMDE
and line egress VTS#i entity COMDE are set as SVLAN tagged , the
line ingress VTS#i and line egress VTS#i entity SVLAN ID should be
same .
11DPE12(A/E) VA port provisioning
Note:
11DPE12(A/E)/VA[1-2] cannot connect to any SFDxx Channel Out
11DPE12(A/E)/VA[1-2] Out cannot connect to 11DPE12(A/E)/VA[1-2] In
The VA port on the 11DPE12(A/E) OT supports the OCH attributes for the eVOA ports
(VA{1-2}) on the 11DPE12(A/E) card as defined in the following table.
....................................................................................................................................................................................................................................
1830 PSS
5-240
Issue 1 June 2013

....................................................................................................................................................................................................................................
VA port provisioning
The following OCH attributes are provisionable on the 11DPE12(A/E) VA interface:

Provisionable
Attribute
moduletype
change the setting, enter this keyword followed by the following:
sVOA slow VOA (Default)
fVOA fast VOA
auto If this value is configured, then the network element will

accept and provision any qualified Alcatel-Lucent pluggable
module.
LAG port provisioning (11DPE12A only)
The following attributes are provisionable on the 11DPE12A LAG interface:

Provisionable
Attribute
detail
Display the provisioned LAG information
....................................................................................................................................................................................................................................
1830 PSS
5-241
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
create
Create a LAG on the pack. Follow this keyword with the following:
Actadmkey: Specify the LAG actor "admin Key"

Range: 1 to 123
actsyspriority: Specify the LAG actor system Priority

Range: 1-65535 (default value is 32768)
Admin: specify the Administration status.

The values are up or down. (default value is down)
lacp: Specify the LACP status, the value can be enable or disable.
When the LACP is enable, it means that the LACP function is
supported. When the LACP is disable , it means that the LACP is
not supported and the manual LAG configuration is supported .
(Default value is enable)
Losprop: Specify the lospropagation behavior. The value can be

laseron or laseroff. (Default value is laseron).
Lptconaction: Specify the LPT consequent action behaviour. The

value can be disable, shutdownforall, and shutdownforany. When
the value is disable, then there is no consequent action when
detecting a client port failure in peer port. When the value is
shutdownforall, it means that the laser will be shutdown only
when all the flows in the client port detect failure. When the value
is shutdownforany, it means that the laser will be shutdown when
any flow in the client port detects failure. (Default value is
disable)
maxport: Specify the max ports that the LAG can support.
Value range: 1 to 4. (Default value is 4).
Mtu: Specify the max transport unite for the LAG ports.
Name: Specify the name of the lag.

Value range is 1-160 size charstring
Tpid: Specify the TPID for the LAG.

Value range: STPID1, STPID2, STPID3, STPID4 (Default value
is STPID1).
....................................................................................................................................................................................................................................
1830 PSS
5-242
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
Modify
Delete
Modify LAG parameter on the pack. Follow this keyword with the
following:
actsyspriority: Specify the LAG actor system Priority.

The range: 1-65535 (Default value is 32768)
Admin: specify the Administration status.

The values are up or down. (default value is down)
Losprop: Specify the lospropagation behavior. The value can be

laseron or laseroff. (Default value is laseron).
Lptconaction: Specify the LPT consequent action behaviour. The

value can be disable, shutdownforall, and shutdownforany. When
the value is disable, then there is no consequent action when
detecting a client port failure in peer port. When the value is
shutdownforall, it means that the laser will be shutdown only
when all the flows in the client port detect failure. When the value
is shutdownforany, it means that the laser will be shutdown when
any flow in the client port detects failure. (Default value is
disable)
maxport: Specify the max ports that the LAG can support.
Mtu: Specify the max transport unite for the LAG ports.
Name: Specify the name of the lag.

Value range is 1-160 size charstring
Tpid: Specify the TPID for the LAG.

Value range: STPID1, STPID2, STPID3, STPID4 (Default value
is STPID1).
Delete the LAG entity
....................................................................................................................................................................................................................................
1830 PSS
5-243
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
add attachedport
<interface>
modify attachedport
<interface>
delete attachedport
<interface>
Attach physical ports to the LAG and set the lag port parameters ,
Follow this keyword with the following:
attachedport: specify the LAG attached port interface number.

Value range is C{1-12}.
actadmstate: Specify the lag port actor admin state . Enter this
Lacpactivity: the value can be active or passive (Active LACP
is encoded as a 1; Passive LACP is encoded as a 0). Default
value is active
Lacptimeout: the value can be short or long (Short Timeout is
encoded as a 1; Long Timeout is encoded as a 0). Default
value is short
Aggregation: the value can be only true (TRUE (encoded as a
1) indicates that the System considers this link to be
Aggregateable; i.e., a potential candidate for aggregation).
actporpriority: Specify the lag actor port priority. The value

Range: 0-65536 .
Default value is 128C.
Modify the lag port parameters. Follow this keyword with the
following:
Attachedport: specify the LAG attached port interface number.

Value range is C{1-12}.
actadmstate: Specify the lag port actor admin state . Enter this
Lacpactivity: the value can be active or passive (Active LACP
is encoded as a 1; Passive LACP is encoded as a 0). Default
value is active
Lacptimeout: the value can be short or long (Short Timeout is
encoded as a 1; Long Timeout is encoded as a 0). Default
value is short
Aggregation: the value can be only true (TRUE (encoded as a
1) indicates that the System considers this link to be
Aggregateable; i.e., a potential candidate for aggregation).
actporpriority: Specify the lag actor port priority. The value

Range: 0-65536 .
Default value is 128C.
Detach the port from the LAG.
....................................................................................................................................................................................................................................
1830 PSS
5-244
Issue 1 June 2013

....................................................................................................................................................................................................................................
11DPM12 OT port state provisioning
The states of the C[1-12], L[1-2], and VA[1-2] ports are provisioned independently. The

Set ains to enabled
11DPM12 client port provisioning
The user can provision the 11DPM12 OT for the following client signal types:
OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16

OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16 LOODUK
1GbE
1GbE LOODUK
HDSDI
HDSDI LOODUK
OTU1
ODU1
Note: Once an OPTSG cross-connection between the client port and ODU1PTF is
created, the ODU1PTF timeslot will be visible.
Note: To regenerate the STM-1 within the 1830 network, it is recommended to
regenerate the STM-1 interface via the OTU1 Client Port-Client Port connection, or
via Line-Line Port Pass-thru ODU0/ODU1 connections to optimize jitter and
transmission performance.
If the STM-1 Client-Client configuration is needed, the total OPTSG cascading
number should be less than 30 and the number of STM-1 regenerations
(client-to-client connections) should be less than 11.
....................................................................................................................................................................................................................................
1830 PSS
5-245
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16 client port provisioning
The following attributes are provisionable on the 11DPM12 C1-12 interfaces when the
provisioned signal type is either OC-3, OC-12, OC-48 or STM-1, STM-4, STM-16:
Provisionable
Attribute
channel
container
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Select the container that will be used for client signal to ODU2
multiplexing structure.
Set to optsg proprietary mapping into sub-ODU1 time slots. The

ODU1 will be mapped into ODU2 with AMP per G.709.
Set to odu0 - mapping into ODU0 with GMP per G.709.
Set to odu1 - mapping into ODU1 with GMP per G.709
Default: NULL
Note:
J0
looduk
Allowable containers for OC3 are optsg and odu0.
16 - Configure J0 format to 16-byte mode.(default)
Configure the client LO ODUk attributes for ODU2 multiplexing

structure.
Note: This entry is applicable only when user selects non-optsg
container for the client port.
mappingmode
Specify the mapping mode for constant bit rate client signals OC48
into OPUk .
Set to async asynchronous mapping CBR into ODUk

information structure by the ODUkP/CBRx adaptation function.
Set to bitsync synchronous mapping CBR into ODUk

information structure by the ODUkP adaptation function. (default)
Note: This entry is applicable to OC48 only.
....................................................................................................................................................................................................................................
1830 PSS
5-246
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
For OC-3:
SS-1.1
SL-1.1
SL-1.2
SL-16.2C
SS-16.1A
SS-16.2C
For OC-12
SS-4.1
SL-4.1
SL-4.2
SL-16.2C
SS-16.1A
SS-16.2C
For OC-48
losprop
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1A (includes SS-16.1)
SS-16.2C

Alcatel-Lucent. (default)


....................................................................................................................................................................................................................................
1830 PSS
5-247
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC-3, OC-12, OC-48 / STM-1, STM-4, STM-16 LOODUK client port provisioning
provisioned signal type is either OC-3, OC-12, OC-48 or STM-1, STM-4, STM-16
LOODUK. It is applicable only when the client container is ODU0/ODU1/ODUflex.
Provisionable
Attribute
ptmmresp
LO ODUk Payload Type Mismatch Response. Specifies whether the
OT will take a consequent action or pass the received signal.
state
tti
Set to enabled to enable the consequent action.
Set to disabled to disable (turn off) the consequent action.

(default)
Set the LO ODUK admin state.
up turn up the LO ODUk alarm reporting if cross-connect exists

and there is an alarm present.
down suppressing the LO ODUk alarm reporting. (default)


value 00).


....................................................................................................................................................................................................................................
1830 PSS
5-248
Issue 1 June 2013

....................................................................................................................................................................................................................................
HDSDI client port provisioning
provisioned signal type is HDSDI:
Provisionable
Attribute
channel
container
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Select the container that will be used for client HD-SDI to ODU2

ODU1 will be mapped into ODU2 with AMP per G.709..
Default: NULL
looduk
Configure client HD-SDI ports LO ODUk attributes for ODU2

Note: This entry is applicable only when user select ODU1 container
for the HD-SDI port..
moduletype

the acceptable Client port moduletype values::
SS-16.1A
SS-16.2C
SL-16.2C


....................................................................................................................................................................................................................................
1830 PSS
5-249
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
Applies to both optical and electrical interfaces.

HDSDI LOODUK client port provisioning
provisioned signal type is HDSDI LOODUK. It is applicable only when the client
container is ODU0/ODU1/ODUflex.
Provisionable
Attribute
ptmmresp
state

(default)

....................................................................................................................................................................................................................................
1830 PSS
5-250
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


1GbE client port provisioning
provisioned signal type is 1GbE:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
For electrical SFPs, the value none should be used.

container

ODU1 will be mapped into ODU2 with AMP per G.709..
Set to odu0 mapping into ODU0 with GMP per G.709.
Default: NULL
....................................................................................................................................................................................................................................
1830 PSS
5-251
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
looduk
Configure client 1GbE ports LO ODUk attributes for ODU2
Note: This entry is applicable only when user select ODU0 container
for the 1GbE port.
moduletype
losprop

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SS-16.1A
SS-16.2C
SL-16.2C
GE-BX20U
GE-BX20D
GE-BX40U
GE-BX40D



....................................................................................................................................................................................................................................
1830 PSS
5-252
Issue 1 June 2013

....................................................................................................................................................................................................................................
1GbE LOODUK client port provisioning
provisioned signal type is 1GbE LOODUK:
Provisionable
Attribute
ptmmresp
state
tti

(default)



value 00).


....................................................................................................................................................................................................................................
1830 PSS
5-253
Issue 1 June 2013

....................................................................................................................................................................................................................................
3GSDI client port provisioning
provisioned signal type is 3GSDI:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

container
Set to none no mapping method.
- Set to oduflex - mapping with BMP into ODUflex which will be

mapped into ODU2 with GMP per G.709
Default: none
looduk
Configure client 3G-SDI ports LO ODUk attributes for ODU2

Note: This entry is applicable only when user select ODUflex
container for the 3G-SDI port.
moduletype

3GSDI-SH
3GSDI-MH


....................................................................................................................................................................................................................................
1830 PSS
5-254
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop

3GSDI LOODUK client port provisioning
provisioned signal type is 3GSDI LOODUK:
Provisionable
Attribute
ptmmresp
state

(default)

....................................................................................................................................................................................................................................
1830 PSS
5-255
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


FC100, FC200, FC400 client port provisioning
provisioned signal type is FC100, FC200, FC400:
Note: The 11DPM12 does not provide buffer credit management and expects the
attached FC switches to be provisioned to handle all buffer credits over the extended
distance. For Brocade, best practice is to use the long distance LS mode. 11DPM12
1G/2G/4G FC doesnt support long distance LD mode.
Use of the 1830 11DPM12 is to extend an inter-switch link (ISL) over the DWDM
used- hard set to 4G, 2G or 1G should be used instead. Brocade licensing for distance
extension and calculation and provisioning of buffering should be coordinated with
local Brocade network engineering.
....................................................................................................................................................................................................................................
1830 PSS
5-256
Issue 1 June 2013

....................................................................................................................................................................................................................................
Use of the 11DPM12 with Brocade frame trunking is supported.

Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

container
Select the container that will be used for client signal to ODU2
Set to none no mapping method.
Set to odu0 - mapping into ODU0 with GMP per G.709.
Set to oduflex - mapping with BMP into ODUflex which will be

mapped into ODU2 with GMP per G.709
Default: none
Note:
Allowable containers for FC100 are odu0.
Allowable containers for FC200 are odu1.
Allowable containers for FC400 are oduflex.
fcmode

x.320, or FICON, or ISC3 Peer Mode). Enter this keyword followed
by:
fc
ficon
isc3peer (applies to FC200 only)
Default: fc
looduk
Configure the client LO ODUk attributes for ODU2 multiplexing

structure.
Note: This entry is applicable only when user select non-optsg
container for the client port.
....................................................................................................................................................................................................................................
1830 PSS
5-257
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
acceptable Client port moduletype values.
For FC-100:
2FCLC-L
2FCSN-I
4FCLC-L
4FCSN-I
SS-16.1A
For FC-200:
2FCLC-L
2FCSN-I
4FCLC-L
4FCSN-I
SS-16.1A
For FC-400:
losprop
4FCLC-L
4FCSN-I



Note: Port channel is either not set or typically set to 850. Assure that the right
multimode jumpers are used if 850nm is used and single mode fibers are used for
CWDM and 1310 and 1550 lasers.
....................................................................................................................................................................................................................................
1830 PSS
5-258
Issue 1 June 2013

....................................................................................................................................................................................................................................
Losprop shall be laserOff for interoperability with Brocade and Cisco FC Switches.
Other options shall be left to default. Brocade and Cisco FC switches need to be
provisioned port to specific line rate (4G, 2g or 1G) instead of using the
across a distance.
Most common moduletype used is the 4FCSN-I for FC400.
Provisioning the 11DPM12 to 4GFC transports can also be used to transport 4G
FICON. (also true at 2G and 1G rates).
11DPM12 pack only gets involved in layer 2 and below and therefore support FICON
and FC equally well when provisioned for FC.
FC100, FC200, FC400 LOODUK client port provisioning
provisioned signal type is FC100, FC200, FC400 LOODUK:
Provisionable
Attribute
ptmmresp
state

(default)

....................................................................................................................................................................................................................................
1830 PSS
5-259
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


Provisionable
Attribute
channelrx
channeltx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-260
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
'down' state.
gccstat
moduletype
mtu
Specifies the status of GCC0 signal processing. Enter one of the

following values:

following:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.2C
SS-16.1A



Range: 576 1500
ospf helloint

PDU is sent.
Range: 1-65535
....................................................................................................................................................................................................................................
1830 PSS
5-261
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf deadint
Range: 1-65535
ospf metric

to 40.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
parameter is mandatory if md5status is enable.
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
....................................................................................................................................................................................................................................
1830 PSS
5-262
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


Provisionable
Attribute
tti



....................................................................................................................................................................................................................................
1830 PSS
5-263
Issue 1 June 2013

....................................................................................................................................................................................................................................
11DPM12 line port provisioning
The line interface on the 11DPM12 OT supports provisionable parameters at the OTU2,
ODU2, and ODU2 LOODUK {1-8} transport layers, as defined in the following tables.
The following OTU2 attributes are provisionable on the 11DPM12 L1,2 interface:
Provisionable
Attribute
channelrx
DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W {850, 1310, 1550}
Not set: None

channeltx

DWDM: { 9600, 9590, 9580, 9570, 9560, 9540, 9530, 9520,

9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420,
9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220,
9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575, 9565,
9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475, 9465,
9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375, 9365,
9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-264
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
efec AMCC Enhanced FEC
efec2- ALU Enhanced FEC type 2 (default)
nofec AMCC Enhanced FEC
'down' state.
Note:
gccstat
ospf helloint
Set to enabled to enable GCC0 processing (default)
Set to disabled to disable GCC0 processing

PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 40.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
....................................................................................................................................................................................................................................
1830 PSS
5-265
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
postfecber
Display the 1-second post-fec BER.
prefecber
Display the 1-second pre-fec BER.
mtu

Range: 576 - 1500
holdofftimer
Specifies whether 11DPM12 will use a hold-off timer to delay taking

a consequent action for line failure.
Default: Disabled
It is recommended to set holdoff timer parameter to enable.
....................................................................................................................................................................................................................................
1830 PSS
5-266
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
interface port.
tti
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C






Note: The enhanced FEC2 (EFEC2) allows the greatest span distances without
regeneration, but it does add the most delay to the transport of the signal. For the
11DPM12 pack, an end to end circuit using a total delay of 157, 154, and 153
....................................................................................................................................................................................................................................
1830 PSS
5-267
Issue 1 June 2013

....................................................................................................................................................................................................................................
microseconds for FC-100, FC-200 and FC-400, respectively. Each 5 us of delay is

equivalent to the delay in 1 km of fiber. These delays must be accounted for in the
Fibre Channel switch buffer credit calculation.
The EFEC/EFEC2 with protection scheme is not allowed for deployments where the
use of RSFEC is mandatory (I.e. EMC Distance Extension Solution).
greatly reduced delay to the transport of the signal. For the 11DPM12 pack an end to
end circuit using a total delay of 15, 12, 11 microseconds for FC-100, FC-200 and
FC-400, respectively.
The following ODU2 attributes are provisionable on the 11DPM12 L1,2 interface:
Provisionable
Attribute
exp_looduk
Modify the exptected LO ODUk structures of HO ODU2 attributes:
To modify LO ODUk of HO ODU2, users must enter a string
containing odukType#oduid-tsMap.
When multiple looduk is needed, users must use & to separate them.
When no string is provided, system will display all expected LO
ODUk of HO ODU2 attributes.
odukType Specifies the ODUk type. Following values are the valid
ODUkTypes.
ODU0 set to ODU0 type.
oduid Specifies the unique ID assigned to the LO ODUk. It is a

single number between 1 to 8. Note: The oduid should be equal to the
smallest Number of its occupied Time slot number.
tsMap Specifies the numbers of Time Slots assigned to the LO
ODUk. It can be a single TS number or TS ranges separated by
comma. Range of TS: [1-8]
Note:
1. If ODUkType is ODU0, ODU0 occupies 1 TS.
2. If ODUkType is ODU1, ODU1 occupies 2 TSs.
Default: the default LO ODUk string for HO ODU2 is
ODU0#1-1&ODU0#2-2&ODU0#3-3&ODU0#4-4&ODU0#55&ODU0#6-6&ODU0#7-7&ODU0#8-8
looduk{1-8}
Configure attributes for a specific LO ODUK in the line ports. See

ODU2 LOODUK{1-8}below.
....................................................................................................................................................................................................................................
1830 PSS
5-268
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
pldtype
ODU2 Payload Type
setting, enter this keyword followed by a 2-digit hexadecimal value.
Must be the same on both ends.
0x21 indicate a GMP capable multiplexed ODUk structure

supporting ODTUk.ts and ODTUjk (k=2).
0x20 indicate interworking with legacy 4xODU1 to ODU2

equipment
Default: 0x21
Multiplexing between OCS and WDM
When multiplexing 4*ODU1 into ODU2 between OCS and WDM OT

11DPM12 use payload type 0x21.
ptmmresp
tti

the following:




....................................................................................................................................................................................................................................
1830 PSS
5-269
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tx_looduk
Modify the exptected LO ODUk structures of HO ODU2 attributes:
To modify LO ODUk of HO ODU2, users must enter a string
containing odukType#oduid-tsMap.
When multiple looduk is needed, users must use & to separate them.
When no string is provided, system will display all expected LO
ODUk of HO ODU2 attributes.
odukType Specifies the ODUk type. Following values are the valid
ODUkTypes.
oduid Specifies the unique ID assigned to the LO ODUk. It is a

single number between 1 to 8. Note: The oduid should be equal to the
smallest Number of its occupied Time slot number.
tsMap Specifies the numbers of Time Slots assigned to the LO
ODUk. It can be a single TS number or TS ranges separated by
comma. Range of TS: [1-8]
Note:
1. If ODUkType is ODU0, ODU0 occupies 1 TS.
2. If ODUkType is ODU1, ODU1 occupies 2 TSs.
Default: the default LO ODUk string for HO ODU2 is
ODU0#1-1&ODU0#2-2&ODU0#3-3&ODU0#4-4&ODU0#55&ODU0#6-6&ODU0#7-7&ODU0#8-8
Note: The tx_looduk structure can be changed only when the
adminState of the related LO ODUk is down, and No XC present.
ODU2 LOODUK {1-8} client port provisioning
The following attributes are provisionable on the 11DPM12 L1,2 interface: when the
provisioned signal type is ODU2 LOODUK {1-8}:
Provisionable
Attribute
state
up turn up the LO ODUk alarm reporting if there is an alarm

regardless the present of cross-connect..
....................................................................................................................................................................................................................................
1830 PSS
5-270
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti



11DPM12 VA port provisioning
The VA port on the 11DPM12 OT supports the OCH attributes for the eVOA ports
(VA{1-2}) on the 11DPM12 card as defined in the following table.
The following OCH attributes are provisionable on the 11DPM12 VA interface:

Provisionable
Attribute
moduletype
sVOA slow VOA
fVOA fast VOA

module.
Default: auto
....................................................................................................................................................................................................................................
1830 PSS
5-271
Issue 1 June 2013

....................................................................................................................................................................................................................................
11QPA4/11QPEN4 OT port state provisioning
The states of the C[1-4], L[1-4], and VA[1-4] ports are provisioned independently. The

Set ains to enabled
Note: For 11QPA4/11QPEN4 the line-side laser is shut down if the port state is
provisioned to "down". The line-side laser is turned on if the port state is set to "up" or
"maintenance".
11QPA4/11QPEN4 client port provisioning
The user can provision the 11QPA4/11QPEN4 OT for the following client signal types:
OC-192 (11QPA4 only)

STM-64 (11QPA4 only)
10GbE
OTU2
FC-10G
FC-8G
....................................................................................................................................................................................................................................
1830 PSS
5-272
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC-192 or STM-64 client port provisioning
The following attributes are provisionable on the 11QPA4 C1-4 interfaces when the
provisioned signal type is either OC-192 or STM-64:
Provisionable
Attribute
channel
J0
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Configure J0 attributes.
j0_ex - Expected J0. Enter this keyword followed by either one of the
following:
j0_fmt - J0 format. Enter this keyword followed by a value for the J0

format:
<value> = 1: configure J0 format to 1-byte mode
<value> = 16:configure J0 format to 16-byte mode
Default: 16
trccmp - J0 trace compare. This keyword enables and disables the
comparison between the incoming J0 value and the provisioned (i.e.,
expected) value.
Set to enabled to enable comparison
Set to disabled to disable comparison
Default: disabled
....................................................................................................................................................................................................................................
1830 PSS
5-273
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
sdth
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.



expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
....................................................................................................................................................................................................................................
1830 PSS
5-274
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 11QPA4/11QPEN4 C1-4 interfaces

when the signal type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

cbrlan11.049
cbrlan11.096
gfp-f (11QPA4 only) specifies the use of the Generic Framing

protocol (ITU-T G.7041)
gfp-p (11QPA4 only) Generic Framing Protocol, Proprietary,

where the client Ethernet frame preamble is preserved.

errfrmdrop

....................................................................................................................................................................................................................................
1830 PSS
5-275
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
10GB-ZR
10GB-SR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.



when the provisioned client signal type is OTU2:
Provisionable
Attribute
channelrx
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-276
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channeltx
fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
'down' state.
gccstat
moduletype
losprop

following:
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C


....................................................................................................................................................................................................................................
1830 PSS
5-277
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf helloint
PDU is sent.
Range: 1-65535
ospf deadint

ospf metric

to 30.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
postfecber
prefecber
....................................................................................................................................................................................................................................
1830 PSS
5-278
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
mtu
Range: 576 - 1500
oturate
tti
Specifies the client OTU2 rate.
Set to 10.709 for standard OTU2 rate (default)
Set to 11.049 for 11.049 Gb/s overclocked rate
Set to 11.096 for 11.096 Gb/s overclocked rate


value 00).


....................................................................................................................................................................................................................................
1830 PSS
5-279
Issue 1 June 2013

....................................................................................................................................................................................................................................

when the provisioned client signal type is OTU2:
Provisionable
Attribute
tti


Note: The 11QPA4 and 11QPEN4 transponder for 10GFC (FC-1200) uses constant
bit rate encoding to transfer all ordered set generated by the FC equipment to the
remote end of the circuit. The 11QPA4 does not provide buffer credit management
and expects the attached FC switches to be provisioned to handle all buffer credits
over the extended distanceBrocade licensing for distance extension and calculation
and provisioning of buffering should be coordinated with local Brocade network
engineering. For Brocade, best practice is to use the long distance LS mode. 11QPA4
and 11QPEN4 8G/10G FC do not support long distance LD mode.
Use of the 1830 11QPA4/11QPEN4 is to extend an inter-switch link (ISL) over the
DWDM network. The expectation is the attached ports in the FC switch are
provisioned to G-port in Brocade systems and E-ports in Cisco Systems and have
their speeds locked to the rate to be used: i.e., the default auto-negotiation (AN) for
speeds should not be used- hard set to 8G or 10G should be used instead.
Recommendation is to turn off Brocade Forward Error Correction (FEC) for ports that
support it.
....................................................................................................................................................................................................................................
1830 PSS
5-280
Issue 1 June 2013

....................................................................................................................................................................................................................................

when the provisioned client signal type is FC10G:
Provisionable
Attribute
channel
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

signal. Enter this keyword followed by one of the following four
values:
cbrlan11.049
cbrlan11.096

G.7041)

Default: gfp-f
errfrmdrop

enabled
disabled
Default: disabled
....................................................................................................................................................................................................................................
1830 PSS
5-281
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
XI-64.1
10GB-SR
10GB-ZR
XS-64.2B
XS-64.2C
XL-64.2C

Alcatel-Lucent.



when the provisioned client signal type is FC800:
Note: The 11QPA4 and 11QPEN4 transponder for 8GFC (FC-800) uses GFP-T
encoding to transfer all ordered set generated by the FC equipment to the remote end
of the circuit. The 11QPA4 does not provide buffer credit management and expects
the attached FC switches to be provisioned to handle all buffer credits over the
extended distanceBrocade licensing for distance extension and calculation and
provisioning of buffering should be coordinated with local Brocade network
engineering. For Brocade, best practice is to use the long distance LS mode. 11QPA4
and 11QPEN4 8G/10G FC do not support long distance LD mode.
Use of the 1830 11QPA4/11QPEN4 is to extend an inter-switch link (ISL) over the
DWDM network. The expectation is the attached ports in the FC switch are
provisioned to G-port in Brocade systems and E-ports in Cisco Systems and have
their speeds locked to the rate to be used: i.e., the default auto-negotiation (AN) for
....................................................................................................................................................................................................................................
1830 PSS
5-282
Issue 1 June 2013

....................................................................................................................................................................................................................................
speeds should not be used- hard set to 8G or 10G should be used instead.
Recommendation is to turn off Brocade Forward Error Correction (FEC) for ports that
support it.
Provisionable
Attribute
channel
moduletype
encmode
B&W: {1310}
Not set: None

X8FCLC-L
X8FCSN-I

Alcatel-Lucent.

Specifies the encapsulation mode used to transport the 8G- FC client

signal. Enter this keyword followed by the value of gfp-t.
Default: gfp-t
losprop

Note: The following apply for using 1830 PSS 11QPA4 and 11QPEN4 with 8G
(FC-800) Fibre Channel Switches:
Port channel is either not set or typically set to 1310. Assure that the right single mode
jumpers are used.
....................................................................................................................................................................................................................................
1830 PSS
5-283
Issue 1 June 2013

....................................................................................................................................................................................................................................
Losprop will be laserOff for interoperability with 1,2,4,8G Brocade and 1,2,4,8,10G
Cisco FC Switches. Losprop will be laserOn for interoperability with 10G Brocade
FC Switches. Other options will be left to default. Brocade and Cisco FC switches
need to be provisioned port to specific line rate (8G) instead of using the
across a distance.
The 11QPA4/11QPEN4 at 8GFC is designed to transport valid FC fill word ordered
sets (such as IDLEs and ARBs) and valid FC frames as defined in INCITS T11
FC-FS-2. Many FC test sets have several modes that do not comply with the fill word
requirement. The 11QPA4/11QPEN4 at 8GFC is NOT designed to transport FC
signals that do not contain some fill words because the 11QPA4/11QPEN4 rate
adapts to the different clocks at the FC switches at both ends and will add or remove
fill words as necessary to compensate for the differences in clocks at both ends.
Without opportunities for rate adaptation, internal buffering will underflow or
overflow and cause errors.
Provisioning the 11QPA4/11QPEN4 to 8GFC/10GFC transports can also be used to
transport 8G/10G FICON.
11QPA4 /11QPEN4 pack only gets involved in layer 2 and below and therefore
support FICON and FC equally well when provisioned for FC.
11QPA4/11QPEN4 line port provisioning
The line interface on the 11QPA4/11QPEN4 OT supports provisionable parameters at the

OTU2 and ODU2 transport layers, as defined in the following tables. The 11QPEN4, in
addition, offers provisionable encryption attributes for the optical data center connect
feature.
Note: If one line port is assigned while the other line port is unassigned, the assigned
line port is set to CrossRegen firstly, the other unassigned line port will copy the
attribute of the assigned line port including oprmode value and OTU2 rate.
....................................................................................................................................................................................................................................
1830 PSS
5-284
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OTU2 attributes are provisionable on the 11QPA4/11QPEN4 L1-4

interface:
Provisionable
Attribute
channelrx
Specifies the expected receive channel frequency or wavelength of the
pluggable module. Not settable for internal topology connections.
DWDM frequencies: {9605, 9600, 9595, 9590, 9585, 9580, 9575,
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170}
channeltx
CWDM wavelengths: {1471, 1491, 1511, 1531, 1551, 1571, 1591,

1611}
Not set: None
Specifies the expected transmit channel frequency or wavelength of

the pluggable module. Not settable for internal topology connections.
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170}
gccstat

1611}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-285
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
oprmode
following:
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2C
X8FCLC-L


Operational mode of the 11QPA4/11QPEN4. This parameter applies to

all line ports.
Set to ADDDROP In this mode pack is processing signal in both

transmission directions (ingress, from client port towards the line
side; egress, from line side to client port)
Set to CROSSREGEN In this mode the Line port input signal is

looped towards another line port output via 8x8 matrix.
Corresponding client ports cannot be used.
1) Value : L{1-4}
2) value must be different than its own port
Set to ADDONLY in this mode, pack is processing signal in

ingress direction (form client port towards the line side)
Value: C{1-4}
Set to DROPCONTINUE In this mode, pack is processing the

signal in egress direction and looping the signal from the line side
input towards the line side output.
Default: ADDDROP
ospf helloint

PDU is sent.
Range: 1-65535
....................................................................................................................................................................................................................................
1830 PSS
5-286
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf deadint

ospf metric

to 30.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
postfecber
prefecber
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
1830 PSS
5-287
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
correction on the interface port:
Set to efec AMCC Enhanced FEC (Default)
Set to rsfec Reed-Solomon FEC
Set to efec2 ALU Enhanced FEC

Note: When the 11QPA4 is provisioned for 10GbE traffic and the
FEC type is EFEC2, the FEC-EC and FEC-UBC counters will be
increasing when a Line Facility Loopback is enabled at the far end
NE.
'down' state.
oturate
values:
11.049 (Gb/s)
11.096 (Gb/s)
Note: this parameter is provisionable only when the line side oprmode
is CROSSREGEN.
tti
CrossRegPartner




Displays the CrossRegPartner port when oprmode is crossRegen

Note: When oprMode is not crossRegen, this field displays as NONE.
....................................................................................................................................................................................................................................
1830 PSS
5-288
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
multicastfrom
Display the multicastfrom information when oprmode is addonly.
Value: C{1-4}, None
Note: when oprmode is not addonly, this field displays as none.
Note: The following apply for using 1830 PSS 11QPA4 and 11QPEN4 with 8G
(FC-800) Fibre Channel Switches:
The EFEC2 allows the greatest span distances without regeneration, but it does add
the most delay to the transport of the signal. For the 11QPA4/11QPEN4 pack, an end
to end circuit uses a total delay of approximately 157 microseconds for FC-800. Each
5 us of delay is equivalent to the delay in 1 km of fiber. This delay is in addition to the
delay on the fiber between the DWDM systems and must be accounted for in the
Fibre Channel switch buffer credit calculation. EFEC provides long span distances but
will lower latency than EFEC2. For the 11QPA4/11QPEN4 pack, an end to end
circuit, EFEC uses a total delay of approximately 59 microseconds for FC-800.
greatly reduced delay to the transport of the signal as compared to EFEC2 or EFEC.
For the 11QPA4/11QPEN4 pack, an end to end circuit, RSFEC uses a total delay of
approximately 15.5 microseconds for FC-800. Only RSFEC is qualified for use with
IBM IB DDR applications.
Note: For IBM IB DDR port channel is either not set or typically set to 1310. Use
XFP X8FCLC-L. Assure that the right single mode jumpers are used.
Losprop should be laserOff for interoperability with IBM IB DDR. Other options
should be left to default.
The supported PSIFB DDR configuration with IBM does not use any 1830 protection
schemes.
....................................................................................................................................................................................................................................
1830 PSS
5-289
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following ODU2 attributes are provisionable on the 11QPA4/11QPEN4 L1-4

interface:
Provisionable
Attribute
mappingmode
pldtype
ODUkp to CBRx mapping mode. This attribute specifies the mappng
mode that wil be used when the client port signal is provisioned to
OC-192, STM-64 or 10GbE WAN.
Set to bitsync bit synchronous CBR mapping
Set to async asynchronous CBR mapping
Specifies the value of the Payload Type field of a Payload Structure

Identifier in the OTUk frame. pldtype has a default value and is based
on the encoded client signal. This attribute only applies when the
client signal is not an OTM0.2 signal.
ptmmresp
tti

the following:




....................................................................................................................................................................................................................................
1830 PSS
5-290
Issue 1 June 2013

....................................................................................................................................................................................................................................
Encryption line port provisioning (11QPEN4 only)
The following encryption attributes are provisionable only on the 11QPEN4 L1-4
interface:
Provisionable
Attribute
display
Displays the current encryption settings for the port.
next Key
Specifies a next encryption key for the interface port. Enter this
keyword followed by string of 64 Hexadecimal digits, or enter this
keyword without any parameters to display the date/time of when the
nextkey was set.
wkat
Specifies a well-known-answer-test for the interface port. Enter this

keyword followed by string of 16 characters, or enter this keyword
without any parameters to display the current description for the
interface: The WKAT string used to authenticate the far end and
validate the keys are correct.
encryptstate
Enable or disable encryption for the port.
switchkey
Commands the port to switch to the next key for encryption.
11QPA4/11QPEN4 VA port provisioning
Note:
11QPA4/11QPEN4 VA[1-4]] cannot connect to any SFDxx Channel Out

11QPA4/11QPEN4 VA[1-4] Out cannot connect to 11QPA4/11QPEN4 VA[1-4] In
The VA port on the 11QPA4/11QPEN4 OT supports the OCH attributes for the eVOA
ports (VA{1-4}) on the 11QPA4/11QPEN4 card as defined in the following table.
....................................................................................................................................................................................................................................
1830 PSS
5-291
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OCH attributes are provisionable on the 11QPA4/11QPEN4 VA interface:

Provisionable
Attribute
moduletype
sVOA slow VOA
fVOA fast VOA

module.
Default: auto
11QPE24 OT port state provisioning
The states of the C[1-22], X[1-4], and VA[1-4] ports are provisioned independently. The

Set ains to enabled
The user can provision the 11QPE24 OT for the following client signal types:
1GbE
FE
10GbE
....................................................................................................................................................................................................................................
1830 PSS
5-292
Issue 1 June 2013

....................................................................................................................................................................................................................................
11QPE24 client port provisioning
The user can provision the 11QPE24 OT for the following client signal types:
1GbE
FE
10GbE
The following attributes are provisionable on the 11QPE24 C1-22 interfaces when the
provisioned signal type is 1GbE:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

moduletype

interface port.
1000B-LX
1000B-SX
1000B-T
1000B-T2
1000B-ZX
SL-16.2C
SS-16.1A
SS-16.2C


....................................................................................................................................................................................................................................
1830 PSS
5-293
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ssmtrans
The value can be:
In SDH mode: ACT, DNU;
In SONET mode: ACT, DUS.

11qpe24 syncesupp is set to enable.
synceoppmode
Configure interface Synchronous Ethernet Operation Mode. When the

interface is in SYNC mode, SSM are transmitted on the interface.
When the interface is in NON-SYNC mode, the SSM are not
transmitted.
FE client port provisioning
The following attributes are provisionable on the 11QPE24 C1-22 interfaces when the
provisioned signal type is FE:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

moduletype

interface port.
100BLX10
1000B-T2

....................................................................................................................................................................................................................................
1830 PSS
5-294
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ssmtrans
The value can be:

synceoppmode

transmitted.
TENGIGE client port provisioning
The following attributes are provisionable on the 11QPE24 X(1-4) interfaces when the
provisioned client signal type is TENGIGE:
Provisionable
Attribute
channelrx
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9550, 9540, 9530,

9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430,
9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330,
9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230,
9220, 9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575,
9565, 9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475,
9465, 9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375,
9365, 9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275,
9265, 9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-295
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channeltx
moduletype
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9550, 9540, 9530,

9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430,
9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330,
9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230,
9220, 9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575,
9565, 9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475,
9465, 9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375,
9365, 9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275,
9265, 9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W: {850, 1310, 1550}
Not set: None

following:
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C
10GB-SR

Alcatel-Lucent.

Default: auto
....................................................................................................................................................................................................................................
1830 PSS
5-296
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ssmtrans
The value can be:

synceoppmode

transmitted.
11QPE24 line port provisioning
The line interface on the 11QPE24 OT supports provisionable parameters at the OTU2
provisioned signal type is ODU2:
Provisionable
Attribute
pldtype [value]
Configure the value of Payload Type Field within the ODU2 payload
overhead. pldtype has a default value and is based on the signal rate:
0x85 for oturate 11.096, 0x84 for oturate 11.049
Range: 0-255
ptmmresp

will take a consequent action or pass the received signal.
disabled disable (turn off) the consequent action
Default: disabled
....................................................................................................................................................................................................................................
1830 PSS
5-297
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti

- timmresp Optical channel Path Trace Identifier Mismatch

Response.. Enter this keyword followed by either of the
following:
Set to enabled to enable TIMM defect detection.
Set to disabled to disable TIMM defect detection.
Default: disabled

Set to enabled to enable comparison
Set to disabled to disable comparson
Default: disabled
tx_sapi Specifies the transmitted Source Access Point
Identifier. Enter this keyword followed by 15 ASCII
characters, enclosed in quotation marks. Default: Null
character (15 bytes each with hex value 00)
....................................................................................................................................................................................................................................
1830 PSS
5-298
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channelrx
channeltx
CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9550, 9540, 9530,

9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430,
9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330,
9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230,
9220, 9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575,
9565, 9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475,
9465, 9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375,
9365, 9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275,
9265, 9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W: {850, 1310, 1550}
Not set: None

CWDM: {1611, 1591, 1571, 1551, 1531, 1511, 1491, 1471}
DWDM: { 9600, 9590, 9580, 9570, 9560, 9550, 9540, 9530,

9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430,
9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330,
9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230,
9220, 9210, 9200, 9190, 9180, 9170, 9605, 9595, 9585, 9575,
9565, 9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485, 9475,
9465, 9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375,
9365, 9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275,
9265, 9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-299
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
correction on the interface port:
Set to efec2, for Enhanced FEC type 2
Set to efec, for Enhanced FEC type 1
Set to rsfec, for Reed-Solomon FEC Set to rsfec, for

Reed-Solomon FEC
Default: efec2
'down' state.
gccstat
Set to disabled to disable GCC0/GCC1/GCC2 processing
Default: disabled
gcctype
Specifies GCC communication channel type.

Default: GCC0
Note: When gccstat is enabled, the change of gcctype is denied.
moduletype

following:
10GB-ZR
XI-64.1
XL-64.2C
XL-64.2D
XL-64TU
XS-64.2b
XS-64.2C

Alcatel-Lucent.

Default: auto
....................................................................................................................................................................................................................................
1830 PSS
5-300
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf helloint
PDU is sent.
Range: 1-65535
ospf deadint

Range: 1-65535
ospf metric

to 30.
Range: 1-65535
ospf md5key
The key used for MD5 128bit hash value key calculation. This
ASCII characters. The string can be uppercase or lowercase
value. This parameter is mandatory if md5status is enable.
Default: NULL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
mtu

Range: 576 - 1500
oturate
OTU2 rate. Specifies the line OTU2 rate
Default: 11.096
....................................................................................................................................................................................................................................
1830 PSS
5-301
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ssmtrans
The value can be:

synceoppmode

transmitted.
tti




value 00)
....................................................................................................................................................................................................................................
1830 PSS
5-302
Issue 1 June 2013

....................................................................................................................................................................................................................................
11QPE24 VA port provisioning
The following OCH attributes are provisionable on the 11QPE24 VA interface:

Provisionable
Attribute
moduletype
sVOA slow VOA
fVOA fast VOA

module.
Default: auto
112PDM11 OT port state provisioning
The states of the C(1-10) and L1 ports are provisioned independently. The following port

Set ains to enabled

112PDM11 client port provisioning
The user can provision the 112PDM11 OT for the following client signal types:
tengige
....................................................................................................................................................................................................................................
1830 PSS
5-303
Issue 1 June 2013

....................................................................................................................................................................................................................................
tengige LAN client port provisioning
The following attributes are provisionable on the 112PDM11 C(1-10) interface when the
signal type is provisioned to tengige:
Provisionable
Attribute
channel
Specifies the expected wavelength of the pluggable module. Enter this
keyword to display the current setting. To change the setting, enter this
keyword followed by one of the following values:
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
moduletype
losprop
Specifies the CFP pluggable module type to be used on the specified

following:
S10GB-LR
S10GB-SR

Alcatel-Lucent.

far-end client-facing receiver. Enter one of the following:
112PDM11 line port provisioning
The line interface on the 112PDM11 OT supports otl4.4 provisionable parameters, as

defined in the following tables.
....................................................................................................................................................................................................................................
1830 PSS
5-304
Issue 1 June 2013

....................................................................................................................................................................................................................................
otl4.4 line port provisioning
The following otl4.4 attributes are provisionable on the 112PDM11 L1 interface:

Provisionable
Attribute
Channelrx
setting, enter this keyword followed by one of the following values::
9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420, 9410, 9400,
9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320, 9310, 9300, 9290,
9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200, 9190, 9180,
9170, 9575, 9565, 9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485,
9475, 9465, 9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375,
9365, 9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
Channeltx
Not set: None

the pluggable module.
setting, enter this keyword followed by one of the following values::
9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430, 9420, 9410, 9400,
9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320, 9310, 9300, 9290,
9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210, 9200, 9190, 9180,
9170, 9575, 9565, 9555, 9545, 9535, 9525, 9515, 9505, 9495, 9485,
9475, 9465, 9455, 9445, 9435, 9425, 9415, 9405, 9395, 9385, 9375,
9365, 9355, 9345, 9335, 9325, 9315, 9305, 9295, 9285, 9275, 9265,
9255, 9245, 9235, 9225, 9215, 9205, 9195, 9185, 9175}
dtvcontrol
Not set: None
Specifies DTV control status.

Set to disabled stop DTV loop. The values of DTV amplitude and
phase will be reset to default hardware value.
Set to enabled run DTV loop.
Default: enabled
Note: It is applicable to 112PDM11 L1 only.
....................................................................................................................................................................................................................................
1830 PSS
5-305
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
gccstat
- Set to enabled to enable GCC0 processing.
- Set to disabled to disable GCC0 processing.
Default: disabled
holdofftimer
Specifies whether 112PDM11 will use a hold-off timer to delay taking

a consequent action for line failure.
Default: Disabled
Note: It is applicable 112PDM11 L1 only.
Mtu

Range: 576 1500
ospf helloint
HELLO INTERVAL of the OSPF Interface. By default, the interface

shall be set to 10 seconds. This is the time elapsed before the next
HELLO PDU is sent.
Range: 1-65535
ospf deadint
DEAD INTERVAL of the OSPF Interface. By default, the Interface

shall be set to four times the value of the HELLOINT, so the default is
40 seconds. The dead interval is a timer used to timeout inactive
Range: 1-65535
ospf metric
METRIC or Cost of the OSPF Interface. By default, the interface shall

be set to 40.
ospf metric METRIC or Cost of the OSPF Interface. By default, the
interface shall be set to 40. Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
....................................................................................................................................................................................................................................
1830 PSS
5-306
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf md5status
Set to enable - The MD5 authentication is activated on the OSPF area.
Set to disable - The MD5 authentication is not required on the OSPF
area
have been set.
Default: disable
112SCA1 OT port state provisioning
are supported:


Set ains to enabled
112SCA1 client port provisioning
The user can provision the 112SCA1 OT for the following client signal types:
100GbE
OTU4
ODU4
....................................................................................................................................................................................................................................
1830 PSS
5-307
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 112SCA1 C1 interface when the signal
Provisionable
Attribute
errfrmdrop
moduletype
losprop

C113G4C
C113G10C

Alcatel-Lucent.

....................................................................................................................................................................................................................................
1830 PSS
5-308
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 112SCA1 C1 interface when the
provisioned client signal type is ODU4:
Provisionable
Attribute
tti


The following attributes are provisionable on the 112SCA1 C1 interface when the
Provisionable
Attribute
fectype
'down' state.
moduletype

following:
C113G4C
C113G10C


....................................................................................................................................................................................................................................
1830 PSS
5-309
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
Note: When the client losprop is set to laserOff and the ODU4 AIS is
detected at line RX port, the client laser will be shut off.
tti


value 00).


112SCA1 line port provisioning
The line interface on the 112SCA1 OT supports provisionable parameters at the OTU4
....................................................................................................................................................................................................................................
1830 PSS
5-310
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OTU4 attributes are provisionable on the 112SCA1 L1 interface:

Provisionable
Attribute
channel
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
fectype
Not set: None

correction on the interface port.
AFEC (Alcatel-Lucent FEC)
Note: In 100G packs, the corrected counts can increase incrementally

due to preFec errors. This is normal behavior for 100G packs.
'down' state.
oprmode
Operation Mode. Specifies the mode of the pack. Enter this keyword
followed by one of the following values:
add_drop
regen
Note: When oprmode is changed from Regen to Add/Drop the OT

requires a cold reboot to recover transmission.
Note: The 100G OTs in REGEN mode are unidirectional where Line
Input port is connected to one Line while the Line Output port is
connected to a different line.
....................................................................................................................................................................................................................................
1830 PSS
5-311
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU4 attributes are provisionable on the 112SCA1 L1 interface:

Provisionable
Attribute
pldtype
Default: 20
ptmmresp

the following:
....................................................................................................................................................................................................................................
1830 PSS
5-312
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




112SNA1 client port provisioning
The user can provision the 112SNA1 OT for the following client signal types:
100GbE
OTU4
ODU4
The following attributes are provisionable on the 112SNA1 C1 interface when the signal
Provisionable
Attribute
errfrmdrop
....................................................................................................................................................................................................................................
1830 PSS
5-313
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
C113G4C (100GbE only)
C113G4D (dual rate 100GbE/OTU4)
C113G10C (10x10G)

Alcatel-Lucent.

The following attributes are provisionable on the 112SNA1 C1 interface when the
provisioned client signal type is ODU4:
Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
1830 PSS
5-314
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 112SNA1 C1 interface when the
Provisionable
Attribute
fectype
'down' state.
moduletype
losprop

following:
C113G4C
C113G10C


Note: When the client losprop is set to laserOff and the ODU4 AIS is
detected at line RX port, the client laser will be shut off.
....................................................................................................................................................................................................................................
1830 PSS
5-315
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


112SNA1 line port provisioning
The line interface on the 112SNA1 OT supports provisionable parameters at the OTU4
....................................................................................................................................................................................................................................
1830 PSS
5-316
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OTU4 attributes are provisionable on the 112SNA1 L1 interface:

Provisionable
Attribute
channeltx
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
channelrx
Not set: None

9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-317
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype

'down' state.
tti




The following ODU4 attributes are provisionable on the 112SNA1 L1 interface:

Provisionable
Attribute
pldtype
Default: 20
....................................................................................................................................................................................................................................
1830 PSS
5-318
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ptmmresp
tti
the following:




112SCX10 OT port state provisioning

....................................................................................................................................................................................................................................
1830 PSS
5-319
Issue 1 June 2013

....................................................................................................................................................................................................................................
Set ains to enabled
112SCX10 client port provisioning
The user can provision the 112SCX10 OT for the following client signal types:
10GbE LAN
OTU2
ODU2
OC-192
STM-64
FC800
The following attributes are provisionable on the 112SCX10 C1-10 interfaces when the
signal type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-320
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
encmode
errfrmdrop
moduletype
losprop

Note: Maximum packet size that can be transmitted is 10236.


10GB-ZR
10GB-SR
L-64.2
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


....................................................................................................................................................................................................................................
1830 PSS
5-321
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channel
J0_ex
J0_fmt
trccmp
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

10GB-ZR
10GB-SR
L-64.2
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.

....................................................................................................................................................................................................................................
1830 PSS
5-322
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
mappingmode
Specifies the mapping mode used for the SONET/SDH signal.
Set to bitsync for bit synchronous CBR mapping
Set to async for asynchronous CBR mapping
Default = previously existing value

sdth

expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-323
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
RSFEC - Configure Reed-Solomon FEC
Note: The 100G MUX OTs support the following FECTYPES on the
client interfaces: RSFEC, NOFEC, EFEC, and EFEC2.
'down' state.
moduletype
losprop
oturate

10GB-ZR
10GB-SR
L-64.2
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


values:
11.049 (Gb/s)
11.096 (Gb/s)
....................................................................................................................................................................................................................................
1830 PSS
5-324
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
1830 PSS
5-325
Issue 1 June 2013

....................................................................................................................................................................................................................................
FC800 client port provisioning
signal type is provisioned to FC800:
Provisionable
Attribute
channel
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

X8FCLC-L
X8FCSN-I

Alcatel-Lucent.

Default: Auto
losprop

112SCX10 line port provisioning
The line interface on the 112SCX10 OT supports provisionable parameters at the OTU4
....................................................................................................................................................................................................................................
1830 PSS
5-326
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OTU4 attributes are provisionable on the 112SCX10 L1 interface:

Provisionable
Attribute
channelrx
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
Not set: None
channeltx
Display the transmit channel frequency of the tunable transponder.
fectype

'down' state.
oprmode
add_drop
regen
....................................................................................................................................................................................................................................
1830 PSS
5-327
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
regenresp
Regeneration Response. Specifies the consequent action of the line
TX laser when the OT is configured for regeneration mode
(oprmode=regen) . Enter this keyword followed by one of the
following values:
laseron
laseroff
Default: laseron
postfecber
prefecber
tti




The following ODU4 attributes are provisionable on the 112SCX10 L1 interface:

Provisionable
Attribute
pldtype
Default: 20
....................................................................................................................................................................................................................................
1830 PSS
5-328
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ptmmresp
tti
the following:




112SNX10 OT port state provisioning

....................................................................................................................................................................................................................................
1830 PSS
5-329
Issue 1 June 2013

....................................................................................................................................................................................................................................
Set ains to enabled
112SNX10 client port provisioning
The user can provision the 112SNX10 OT for the following client signal types:
10GbE LAN
OTU2
ODU2
OC-192
STM-64
FC800
The following attributes are provisionable on the 112SNX10 C1-10 interfaces when the
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-330
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
encmode
errfrmdrop
moduletype
losprop



10GB-ZR
10GB-SR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


....................................................................................................................................................................................................................................
1830 PSS
5-331
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channel
J0_ex
J0_fmt
trccmp
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.

....................................................................................................................................................................................................................................
1830 PSS
5-332
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
mappingmode

sdth

expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-333
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
EFEC Enhanced FEC
EFEC2 ALU FEC
'down' state.
moduletype
losprop
oturate

10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


values:
11.049 (Gb/s)
11.096 (Gb/s)
....................................................................................................................................................................................................................................
1830 PSS
5-334
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
1830 PSS
5-335
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channel
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

X8FCLC-L
X8FCSN-I

Alcatel-Lucent.

Default: Auto
losprop

112SNX10 line port provisioning
The line interface on the 112SNX10 OT supports provisionable parameters at the OTU4
....................................................................................................................................................................................................................................
1830 PSS
5-336
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OTU4 attributes are provisionable on the 112SNX10 L1 interface:

Provisionable
Attribute
channelrx
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
channeltx
Not set: None

9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-337
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
fectype
'down' state.
oprmode
add_drop
regen
regenresp

following values:
laseron
laseroff
Default: laseron
....................................................................................................................................................................................................................................
1830 PSS
5-338
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU4 attributes are provisionable on the 112SNX10 L1 interface:

Provisionable
Attribute
pldtype
Default: 20
ptmmresp

the following:
....................................................................................................................................................................................................................................
1830 PSS
5-339
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




130SCX10 OT port state provisioning

Set ains to enabled
....................................................................................................................................................................................................................................
1830 PSS
5-340
Issue 1 June 2013

....................................................................................................................................................................................................................................
130SCX10 client port provisioning
The user can provision the 130SCX10 OT for the following client signal types:
10GbE LAN
OTU2
ODU2
OC-192
STM-64
FC800
Provisionable
Attribute
channel
encmode
errfrmdrop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None



....................................................................................................................................................................................................................................
1830 PSS
5-341
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
10GB-ZR
10GB-SR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-342
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
J0_ex
J0_fmt
moduletype
losprop
mappingmode

10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.



sdth

expressed as 10-n.
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6
....................................................................................................................................................................................................................................
1830 PSS
5-343
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
sfth
expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
Provisionable
Attribute
channel
fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
EFEC Enhanced FEC
EFEC2 ALU FEC
'down' state.
....................................................................................................................................................................................................................................
1830 PSS
5-344
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
oturate
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C

Alcatel-Lucent.


values:
11.049 (Gb/s)
11.096 (Gb/s)
....................................................................................................................................................................................................................................
1830 PSS
5-345
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti


value 00).


Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
1830 PSS
5-346
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channel
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

X8FCLC-L
X8FCSN-I

Alcatel-Lucent.

Default: Auto
losprop

130SCX10 line port provisioning
The line interface on the 130SCX10 OT supports provisionable parameters at the OTU4
....................................................................................................................................................................................................................................
1830 PSS
5-347
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OTU4 attributes are provisionable on the 130SCX10 L1 interface:

Provisionable
Attribute
channelrx
9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
channeltx
Not set: None

9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520,
9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410,
9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355,
9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300,
9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245,
9240, 9235, 9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190,
9185, 9180, 9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135,
9130, 9125, 9120, 9115}
fectype
Not set: None
Attribute that configures the Forward Error Correction (FEC) type. Set
to one of the following values:
sdfec (Soft Decision FEC)
afec (ALU FEC)
Default: sdfec
Note: Set line port Admin State down before changing FEC type.
....................................................................................................................................................................................................................................
1830 PSS
5-348
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
oprmode
add_drop
regen
regenresp

following values:
laseron
laseroff
Default: laseron
tti




....................................................................................................................................................................................................................................
1830 PSS
5-349
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following ODU4 attributes are provisionable on the 130SCX10 L1 interface:

Provisionable
Attribute
pldtype
Default: 20
ptmmresp
tti

the following:




4DPA4 OT port state provisioning
The states of the C1-4 and L1-2 ports are provisioned independently. The following port

....................................................................................................................................................................................................................................
1830 PSS
5-350
Issue 1 June 2013

....................................................................................................................................................................................................................................

Set ains to enabled
4DPA4 client port provisioning
The user can provision the 4DPA4 OT for the following client signal types:
GbE
OC3
STM1
OC12
STM4
OC48
STM16
FC100, FC200, FC400
DVBASI, FE, HDSDI, SDSDI
Note: For 4DPA4, available bandwidth validation is done only when timeslots are
assigned; not when the client port is created. (This is different from 11STMM10 OT
behavior.)
The following attributes are provisionable on the 4DPA4 C1-4 interfaces when the signal
type is provisioned to GbE :
Port Attribute
channel
Description
Specifies the expected wavelength of the pluggable module.
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-351
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
losprop
moduletype
Description

following:

1000B-LX
1000B-SX
1000B-T
1000B-ZX
SL-16.2C
SS-16.1A
SS-16.2C
GE-BX20U
GE-BX20D
GE-BX40U
GE-BX40D

Alcatel-Lucent.

....................................................................................................................................................................................................................................
1830 PSS
5-352
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description
Specifies the line port and the timeslot on the line port, that the client
port will be mapped to. Both line and vts parameters must be included.
Both must be zero, or both must be non-zero. Enter the keyword
timeslot followed by:
The keyword line and a linenum value as follows. Range: {0-2}

Enter 0 to unassign the client port from any line port.
Enter 1 to assign the client port to L1.
The keyword vts and a vtslist value as follows. Range: {0-2}

The value 0 unassigns the client port from any timeslots.
The value 1 assigns the client port to the timeslots of ODU0
#1: 1,3,5,7,9,11,13,15.
The value 2 assigns the client port to the timeslots of ODU0
#2: 2,4,6,8,10,12,14,16.
OC3/OC12/OC48 and STM1/STM4/STM16 client port provisioning
type is provisioned to OC3/OC12/OC48 and STM1/STM4/STM16 :
Port Attribute
channel
Description
losprop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-353
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
moduletype
Description
following:

For OC3/STM1:
SL-1.1
SL-1.2
SL-16.2C
SS-1.1
SS-16.1A
SS-16.2C
FE-BX40U
FE-BX40D
For OC12/STM4:
SS-4.1
SL-4.1
SL-4.2
SL-16.2C
SS-16.1A
SS-16.2C
GE-BX20U
GE-BX20D
GE-BX40U
GE-BX40D
For OC48/STM16:
SI-16.1
SL-16.1
SL-16.2
SL-16.2C
SS-16.1
SS-16.1A
SS-16.2C


....................................................................................................................................................................................................................................
1830 PSS
5-354
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description
Specifies the line port, and the timeslot on the line port, that the client

The keyword vts and a vtslist value as follows. Range: {0-16,

vtslist}
For STM-1 clients: Enter 0, or any single timeslot from 1 to
16.
For STM-4 clients: Enter 0, or a vtslist representing four
timeslots from 1 to 16. The vtslist can include a list of
individual timeslots and/or a list of timeslot ranges. If only
one timeslot is specified, the request is for a contiguous range
of timeslots starting at that value.
For STM-16 clients: Enter 0, or 1. Timeslot 1 represents the
entire OTU1 line capacity (all 16 timeslots).
FC100, FC200, FC400 client port provisioning
Note: The 4DPA4 does not provide buffer credit management and expects the
attached FC switches to be provisioned to handle all buffer credits over the extended
distance Brocade licensing for distance extension and calculation and provisioning of
buffering should be coordinated with local Brocade network engineering. For
Brocade, best practice is to use the long distance LS mode. 4DPA4 1/2/4GFC does not
support long distance LD mode.
4DPA4 DualTran and FlexMux is only designed for unprotected non-trunked links.
Use of the 1830 4DPA4 is to extend an inter-switch link (ISL) over the DWDM
used - hard set to 1G or 2G or 4G should be used instead.
type is provisioned to FC100, FC200, FC400:
....................................................................................................................................................................................................................................
1830 PSS
5-355
Issue 1 June 2013

....................................................................................................................................................................................................................................
FC100 and FC200 apply only in FlexMux card mode. FC400 applies only in DualTran
card mode.
Port Attribute
channel
fcmode
losprop
moduletype
Description
Specifies the expected wavelength of the pluggable module. Enter this
keyword to display the current setting. To change the setting, enter this
keyword followed by one of the following values:
B&W: {850, 1310, 1550}
Not set: None

x.320, or FICON, or ISC3 Peer Mode). Enter this keyword followed
by:
fc (default)
ficon
isc3peer (applies to FC200 only)

following:

FC100, FC200, FC400:
4FCLC-L
4FCSN-1
FC100 and FC200:
SS-16.1A


....................................................................................................................................................................................................................................
1830 PSS
5-356
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
timeslot
[line | vts]
Description


vtslist}
For FC100 clients: Enter 0, or a vtslist representing seven
For FC200 clients: Enter 0, or a vtslist representing fourteen
Note: Port channel is either not set or typically set to 1310nm for single mode or
850nm for multi mode. Assure that the right jumpers are used.
Losprop shall be set to laserOff for interoperability with 1,2,4G Brocade.
Other options shall be left to default. Brocade switches need to be provisioned port to
specific line rate (1,2,4G) instead of using the auto-negotiation speed option. Make
sure FC switches are properly configured to use the 1830 link as an ISL. Typically, an
E-port and fabric switch provisioning and FC buffer credit provisioning necessary for
using 1830 in a FC transport application across a distance.
....................................................................................................................................................................................................................................
1830 PSS
5-357
Issue 1 June 2013

....................................................................................................................................................................................................................................
DVBASI, FE, HDSDI, SDSDI client port provisioning
type is provisioned to FE:
Port Attribute
channel
Description
hdsdirate
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Specifies the HD-SDI signal rate. Applies only when port type =
hdsdi.
1.485 standard rate, 1.485 Gb/s
1.485/1.001 rate compatible with existing NTSC systems
Default = 1.485/1.001
losprop
....................................................................................................................................................................................................................................
1830 PSS
5-358
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
moduletype
timeslot
[line | vts]
Description
following:

For FE:
100BLX10
FE-BX40D
FE-BX40U
For DVB ASI, HD-SDI, and SD-SDI:
SS-16.1A
SS-16.2C
SL-16.2C




vtslist}
For FE clients: Enter 0, or any single timeslot from 1 to 16.
For DVB ASI and SD-SDI clients: Enter 0, or a vtslist
representing two timeslots from 1 to 16. The vtslist can
include a list of individual timeslots and/or a list of timeslot
ranges. If only one timeslot is specified, the request is for a
contiguous range of timeslots starting at that value.
For HD-SDI clients: Enter 0, or a vtslist representing ten
....................................................................................................................................................................................................................................
1830 PSS
5-359
Issue 1 June 2013

....................................................................................................................................................................................................................................
4DPA4 line port provisioning
Note: 4DPA4/L[1-2] cannot connect to any CWR8 CLS In.

Note: The 4DPA4 pack is used in Pt-Pt configurations to provide transport of
multiplexed FC-100/200 signals over an OTU1 structure. In egress direction, physical
layer impairments are monitored at OTU1/ODU1 layers (including FEC error counts).
Any errors that cant be corrected are counted on the line port and correspond to PCS
layer errors in Tx direction of client FC-100/200 bit stream (i.e., any error observed
on the client egress bit stream resulting from DWDM/CWDM line impairment is
detected and counted as a PM event on the associated ODU1/OTU1 line port input).
The line interface on the 4DPA4 OT supports provisionable parameters at the OTU1 and
ODU1 transport layers, as defined in the following tables.
The following OTU1 attributes are provisionable on the 4DPA4 L1 and L2 interface:
Provisionable
Attribute
channelrx
pluggable module. Enter this keyword to display the current setting.
To change the setting, enter this keyword followed by one of the
following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}

1611}
B&W wavelengths: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-360
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channeltx
fectype
the pluggable module. Enter this keyword to display the current
setting. To change the setting, enter this keyword followed by one of
the following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}

1611}
B&W wavelengths: {850, 1310, 1550}
Not set: None

rsfec - Reed-Solomon FEC (default)
nofec No forward error correction.
'down' state.
gccstat
enabled to enable GCC0 processing.
disabled to disable GCC0 processing (default).
....................................................................................................................................................................................................................................
1830 PSS
5-361
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
Specifies the pluggable module type to be used on the specified line
port. Enter this keyword to display the current setting. To change the
FlexMux:
SL-16.1
SL-16.2C
SL-16.2D
SS-16.1A
SS-16.2C
DualTran:
oprmode
ospf helloint
4FC-OC
4FC-OD


Operational mode of the 4DPA4. This parameter applies to both line

ports, but it can be set only on port L1. The L2 value is read-only, and
is always equal to the L1 value.
Set to ADDDROP Add/Drop Mode. Client port signals can be

added and dropped to/from the line ports. There is no regen
function. (Default)
Set to CROSSREGEN Cross Regeneration Mode. Line-to-line

regen function is activated. Client ports cannot be used.

PDU is sent.
Range: 1-65535
ospf deadint

....................................................................................................................................................................................................................................
1830 PSS
5-362
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
ospf metric
to 40.
Range: 1-65535
ospf md5key
Default: NUL ()
ospf md5keyid
Range: 1- 255
Default: 1
ospf md5status

area.

OSPF area.

have been set.
Default: disable
packettype

Default: nonstd
mtu

Range: 576 - 1500
....................................................................................................................................................................................................................................
1830 PSS
5-363
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti
Configure the OTU1 Trail Trace Indentifier attributes:




Note: The RSFEC allows for significant span distances without regeneration, and it
has greatly reduced delay to the transport of the signal. For the 4DPA4 pack, in case
of end to end circuit, RSFEC uses a total delay of approximately 31 microseconds for
FC-100, 28 microsecond for FC-200 and 36 microsecond for FC-400.
....................................................................................................................................................................................................................................
1830 PSS
5-364
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following ODU1 attributes are provisionable on the 4DPA4 L1 and L2 interface:
Provisionable
Attribute
odu0interwk
Standard ODU0 Interworking. When disabled, ODU1 Payload Type
should be set to 0x80 and there is proprietary encoding of OPTS OH
in PSI bytes and LosProp in APS/PCC bytes. The 4DPA4 can then
interwork at 2xODU0 only with another 4DPA4 at the far end. When
enabled, ODU1 Payload Type should be set to 0x20 (ODU multiplex
structure) and there is no proprietary use of PSI or APS/PCC bytes.
The 4DPA4 can then interwork with standard 2xODU0 equipment at
the far end. Enter this keyword to display the current setting. To
following:
enabled to enable standard ODU0 interworking.
disabled to disable (turn off) standard ODU0 interworking

(default).
Important: When client signals are not GbE, the odu0interwk

parameter must be set to DISABLE. ODU0 interworking is only valid
for GbE traffic.
Note: ODU0INTERWK and PLDTYPE attributes must be
provisioned consistently (synchronized).
pldtype
ODU1 Payload Type. Enter this keyword to display the current

setting. To change the setting, enter this keyword followed by a 2-digit
hexadecimal value. Must be the same on both ends.
0x80 indicates a proprietary mixture of sub-ODU1 signals

(default).
0x20 indicates standard 2xODU0 interworking.
Note: ODU0INTERWK and PLDTYPE attributes must be

provisioned consistently (synchronized).
ptmmresp

the following:
....................................................................................................................................................................................................................................
1830 PSS
5-365
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




4DPA4 VA port provisioning
Note:
4DPA4/VA[1-2] cannot connect to any CWR8 CLS Out

4DPA4/VA[1-2] cannot connect to any SFDxx Channel Out
4DPA4/VA[1-2] Out cannot connect to 4DPA4/L[1-2] In
The VA port on the 4DPA4 OT supports the OCH attributes for the eVOA ports
(VA{1-2}) on the 4DPA4 card as defined in the following table.
....................................................................................................................................................................................................................................
1830 PSS
5-366
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OCH attributes are provisionable on the 4DPA4 VA interface:

Provisionable
Attribute
moduletype
following:
fVOA


4DPA2 OT port state provisioning
The states of the C1,2 and L1,2 ports are provisioned independently. The following port


Set ains to enabled
4DPA2 client port provisioning
The user can provision the 4DPA2 OT for the following client signal type:
STM16
OC48
1GbE
....................................................................................................................................................................................................................................
1830 PSS
5-367
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC48 or STM16 client port provisioning
The following attributes are provisionable on the 4DPA2 C1,2 interfaces when the signal
type is provisioned to OC48 or STM16:
Port Attribute
channel
Description
moduletype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

following:

For OC48/STM16:
SL-16.1
SL-16.2C
SS-16.1A
SS-16.2C


....................................................................................................................................................................................................................................
1830 PSS
5-368
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 4DPA2 C1,2 interfaces when the signal
type is provisioned to 1GbE:
Port Attribute
channel
Description
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

moduletype

following:

For 1GbE:
1000B-LX
1000B-SX
1000B-T
SL-16.2C
SS-16.1A
SS-16.2C


4DPA2 line port provisioning
For 4DPA2, the line port is automatically created when the client port is created and the
line port is deleted when the client port is deleted. The L1 and L2 interface on the 4DPA2
OT supports provisionable parameters as defined in the following tables.
....................................................................................................................................................................................................................................
1830 PSS
5-369
Issue 1 June 2013

....................................................................................................................................................................................................................................
OC48 or STM16 line port provisioning
The following OC48 or STM16 attributes are provisionable on the 4DPA2 L1 and L2
interface:
Provisionable
Attribute
channel
moduletype
Specifies the expected channel frequency or wavelength of the
following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}
Not set: None

Enter one of the acceptable line port moduletype values:

SL-16.2D


....................................................................................................................................................................................................................................
1830 PSS
5-370
Issue 1 June 2013

....................................................................................................................................................................................................................................
1GbE line port provisioning
The following 1GbE attributes are provisionable on the 4DPA2 L1 and L2 interface:
Provisionable
Attribute
channel
moduletype
Specifies the expected channel frequency or wavelength of the
following values:

9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440,
9430, 9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340,
9330, 9320, 9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240,
9230, 9220, 9210, 9200, 9190, 9180, 9170}
Not set: None

Enter one of the acceptable line port moduletype values:

SL-16.2D


43SCA1 OT port state provisioning
are supported:

....................................................................................................................................................................................................................................
1830 PSS
5-371
Issue 1 June 2013

....................................................................................................................................................................................................................................
cnfigure the properties of the ainstimer to use either the system value, or to enter
Set ains to enabled
43SCA1 client port provisioning
The user can provision the 43SCA1 OT for the following client signal types:
OC-768
STM-256
ODU3
OTU3
type is provisioned to OC-768 or STM-256:
Port Attribute
jo
Description

the following:

J0 format.

....................................................................................................................................................................................................................................
1830 PSS
5-372
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
losprop
sdth
Description

expressed as 10-n.
sfth
Range: {10-5, 10-6, 10-7, 10-8, 10-9}

Default: 10-6

expressed as 10-n.
Range: {10-3, 10-4, 10-5}

Default: 10-3
Note: When real Payload Type Mismatch and far-end OC-768/STM256 LOF are
detected simultaneously, the real Payload Type Mismatch defect will not be raised.
type is provisioned to OTU3:
Port Attribute
losprop
fectype
Description

correction on the interface port
Set to nofec FEC correction disabled
Set to rsfec Reed-Solomon FEC
....................................................................................................................................................................................................................................
1830 PSS
5-373
Issue 1 June 2013

....................................................................................................................................................................................................................................
Port Attribute
tti
Description
Configure OTU3 Trail Trace Indentifier attributes:




Note: For 43SCA1 pack, the regeneration mode or transparent mode refers only to the
line transmit direction.
The following ODU3 attributes are provisionable on the 43SCA1 C1 interface:

Provisionable
Attribute
tti


....................................................................................................................................................................................................................................
1830 PSS
5-374
Issue 1 June 2013

....................................................................................................................................................................................................................................
43SCA1 line port provisioning
The line interface on the 43SCA1 OT supports provisionable parameters at the OTU3 and
ODU3 transport layers, as defined in the following tables.
The following OTU3 attributes are provisionable on the 43SCA1 L1 interface:

Provisionable
Attribute
channelrx
Attribute that configures the receive frequency.
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515, 9510,
9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465, 9460, 9455,
9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410, 9405, 9400,
9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355, 9350, 9345,
9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300, 9295, 9290,
9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245, 9240, 9235,
9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190, 9185, 9180,
9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125,
9120, 9115}
Not set: None
channeltx
Attribute that configures the transmit frequency.

Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515, 9510,
9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465, 9460, 9455,
9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410, 9405, 9400,
9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355, 9350, 9345,
9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300, 9295, 9290,
9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245, 9240, 9235,
9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190, 9185, 9180,
9175, 9170, 9165, 9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125,
9120, 9115}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-375
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU3 attributes are provisionable on the 43SCA1 L1 interface:

Provisionable
Attribute
mappingmode
OC-768 or STM-256.

ptmmresp

the following:
....................................................................................................................................................................................................................................
1830 PSS
5-376
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




43SCGE1 OT port state provisioning
are supported:

Set ains to enabled
43SCGE1 client port provisioning
The user can provision the 43SCGE1 OT for the following client signal types:
40GbE LAN
....................................................................................................................................................................................................................................
1830 PSS
5-377
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 43SCGE1 C1 interface when the signal
Provisionable
Attribute
errfrmdrop
moduletype
losprop

following:
C43g4c (40GbE)



43SCGE1 line port provisioning
The line interface on the 43SCGE1 supports provisionable parameters at the OTU4 and
ODU4 transport layers as defined in the following tables.
....................................................................................................................................................................................................................................
1830 PSS
5-378
Issue 1 June 2013

....................................................................................................................................................................................................................................
43SCGE1 OTU4 line port provisioning
The following OTU4 attributes are provisionable on the 43SCGE1 L1 interface:

Provisionable
Attribute
channelrx
channeltx
fectype
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515,
9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365,
9360, 9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315,
9310, 9305, 9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265,
9260, 9255, 9250, 9245, 9240, 9235, 9230, 9225, 9220, 9215,
9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175, 9170, 9165,
9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125, 9120, 9115}
Not set: None
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515,
9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365,
9360, 9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315,
9310, 9305, 9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265,
9260, 9255, 9250, 9245, 9240, 9235, 9230, 9225, 9220, 9215,
9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175, 9170, 9165,
9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125, 9120, 9115}
Not set: None

correction on the interface port
Enter this keyword followed by one of the following values:
afec (Alcatel-Lucent FEC)
....................................................................................................................................................................................................................................
1830 PSS
5-379
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU4 attributes are provisionable on the 43SCGE1 L1 interface:

Provisionable
Attribute
pldtype
on the encoded client signal.
Default: 20
ptmmresp

the following:
....................................................................................................................................................................................................................................
1830 PSS
5-380
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




43SCX4 / 43SCX4E / 43STX4(P) OT port state provisioning

Set ains to enabled
....................................................................................................................................................................................................................................
1830 PSS
5-381
Issue 1 June 2013

....................................................................................................................................................................................................................................
43SCX4 / 43SCX4E / 43STX4(P) client port provisioning
The user can provision the 43SCX4 / 43SCX4E / 43STX4(P) OT for the following client
signal types:
FC800
10GbE LAN
OC-192
STM-64
OTU2

Provisionable
Attribute
channel
moduletype
losprop
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None

following:
X8FCLC-L
X8FCSN-I



....................................................................................................................................................................................................................................
1830 PSS
5-382
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 43SCX4 / 43SCX4E / 43STX4(P) C1-4
interface when the signal type is provisioned to 10GbE LAN:
Provisionable
Attribute
channel
encmode
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None


G.7041)

Note: On 43STX4(P) boards GFP-F and GFP-P encapsulations are

available. Both modes will add delay in LFI/RFI alarm generation or
transport. When interworking with MPLS routers it is recommended
to implement link monitoring protocols on router side.
errfrmdrop

....................................................................................................................................................................................................................................
1830 PSS
5-383
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
moduletype
losprop
following:
10GB-SR
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C



interface when the provisioned signal type is either OC-192 or STM-64:
Provisionable
Attribute
channel
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-384
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
J0_ex
J0_fmt
trccmp
moduletype
losprop
mappingmode
Disable - Disable J0 comparison (default).

following:
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C



Mapping Mode. Specifies the mapping mode used for the

SONET/SDH signal.
async for asynchronous mapping
bitsync for bit-synchronous mapping
....................................................................................................................................................................................................................................
1830 PSS
5-385
Issue 1 June 2013

....................................................................................................................................................................................................................................
interface when the provisioned client signal type is OTU2:
Provisionable
Attribute
channel
fectype
CWDM: {1471, 1491, 1511, 1531, 1551, 1571, 1591, 1611}
B&W: {850, 1310, 1550}
Not set: None
Set to efec Enhanced FEC
Set to efec2 ALU FEC
'down' state.
moduletype

following:
10GB-ZR
XI-64.1
XL-64.2C
XS-64.2b
XS-64.2C


....................................................................................................................................................................................................................................
1830 PSS
5-386
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
losprop
tti


value 00).


....................................................................................................................................................................................................................................
1830 PSS
5-387
Issue 1 June 2013

....................................................................................................................................................................................................................................
ODU2 client port provisioning
interface when the provisioned client signal type is OTU2:
Provisionable
Attribute
tti


43SCX4 / 43SCX4E / 43STX4(P) line port provisioning
The line interface on the 43SCX4 / 43STX4(P)/ 43SCX4 / 43SCX4E / 43STX4(P)

supports provisionable parameters at the OTU3 and ODU3 transport layers, as defined in
the following tables.
Note: Provisioning max power on 43SCX4 OT is limited and cannot be provisioned
to 4dB on the line port of the OT.
43SCX4/43SCX4E OTU3 line port provisioning
The following OTU3 attributes are provisionable on the 43SCX4/43SCX4E L1 interface:

Provisionable
Attribute
channelrx
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515,
9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365,
9360, 9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315,
9310, 9305, 9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265,
9260, 9255, 9250, 9245, 9240, 9235, 9230, 9225, 9220, 9215,
9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175, 9170, 9165,
9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125, 9120, 9115}
Not set: None
....................................................................................................................................................................................................................................
1830 PSS
5-388
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channeltx
oprmode
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515,
9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465,
9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365,
9360, 9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315,
9310, 9305, 9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265,
9260, 9255, 9250, 9245, 9240, 9235, 9230, 9225, 9220, 9215,
9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175, 9170, 9165,
9160, 9155, 9150, 9145, 9140, 9135, 9130, 9125, 9120, 9115}
Not set: None
Operation mode. Specifies the type of operation mode supported on

the interface
Set to:
ADDDROP Add/Drop mode
REGEN Regeneration mode
postfecber
prefecber
tti




....................................................................................................................................................................................................................................
1830 PSS
5-389
Issue 1 June 2013

....................................................................................................................................................................................................................................
43STX4(P) OTU3 line port provisioning
The following OTU3 attributes are provisionable on the 43STX4(P) L1 interface:

Provisionable
Attribute
channel
The following applies to 43STX4:
Enter one of the following: {0, 9600, 9590, 9580, 9570, 9560, 9540,
9530, 9520, 9510, 9500, 9490, 9480, 9470, 9460, 9450, 9440, 9430,
9420, 9410, 9400, 9390, 9380, 9370, 9360, 9350, 9340, 9330, 9320,
9310, 9300, 9290, 9280, 9270, 9260, 9250, 9240, 9230, 9220, 9210,
9200, 9190, 9180, 9170}
The following applies to 43STX4P:
9575, 9570, 9565, 9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525,
9520, 9515, 9510, 9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470,
9465, 9460, 9455, 9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415,
9410, 9405, 9400, 9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360,
9355, 9350, 9345, 9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305,
9300, 9295, 9290, 9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250,
9245, 9240, 9235, 9230, 9225, 9220, 9215, 9210, 9215, 9200, 9195,
9190, 9185, 9180, 9175, 9170}
fectype

afec ALU FEC (default)
'down' state.
....................................................................................................................................................................................................................................
1830 PSS
5-390
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




The following ODU3 attributes are provisionable on the 43SCX4 / 43SCX4E /

43STX4(P) L1 interface:
Provisionable
Attribute
pldtype
on the encoded client signal.
Default: 20
ptmmresp

the following:
....................................................................................................................................................................................................................................
1830 PSS
5-391
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
tti




43STA1P OT port state provisioning
The states of the C1-C12 and L1 ports are provisioned independently. The following port

cnfigure the properties of the ainstimer to use either the system value, or to enter
Set ains to enabled
....................................................................................................................................................................................................................................
1830 PSS
5-392
Issue 1 June 2013

....................................................................................................................................................................................................................................
43STA1P client port provisioning
The user can provision the 43STA1P OT for the following client signal types:
OC-768
STM-256
OTU3
The following attributes are provisionable on the 43STA1P C1 interface when the signal
type is provisioned to OC-768 or STM-256:
Port Attribute
jo
Description
losprop

the following:

J0 format.

Note: When real Payload Type Mismatch and far-end OC-768/STM256 LOF are
detected simultaneously, the real Payload Type Mismatch defect will not be raised.
....................................................................................................................................................................................................................................
1830 PSS
5-393
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following attributes are provisionable on the 43STA1P C1 interface when the signal
type is provisioned to OTU3:
Port Attribute
losprop
Description
Note: OTU3 client port provisioning is intended for OTU3 regeneration configuration
between a pair of 43STA1P OTs. OTU3 port provisioning may not be used as NNI
port connected to third party OTN network due to lack of FEC field
termination/processing, ODU3P layer monitoring (ODU3 defects or path BIP-8
monitoring at ODUkP/T layer isnt supported) or GCC[n] channel processing. OTUk
monitoring functions, including section BIP-8 is supported.
Note: For 43STA1P pack, the regeneration mode or transparent mode refers only to
the line transmit direction.
43STA1P line port provisioning
The line interface on the 43STA1P OT supports provisionable parameters at the OTU3
....................................................................................................................................................................................................................................
1830 PSS
5-394
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following OTU3 attributes are provisionable on the 43STA1P L1 interface:

Provisionable
Attribute
channel
Set to {9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565, 9560,
9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515, 9510, 9505,
9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465, 9460, 9455, 9450,
9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410, 9405, 9400, 9395,
9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355, 9350, 9345, 9340,
9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300, 9295, 9290, 9285,
9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245, 9240, 9235, 9230,
9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190, 9185, 9180, 9175,
9170}
Not set: None
fectype

ufec ultra FEC (default)
'down' state.
postfecber
prefecber
tti




....................................................................................................................................................................................................................................
1830 PSS
5-395
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following ODU3 attributes are provisionable on the 43STA1P L1 interface:

Provisionable
Attribute
mappingmode
OC-768 or STM-256.

ptmmresp
tti

the following:




MVAC OT port state provisioning
The states of the G{1-8} ports are provisioned independently. The following port states
are supported:

....................................................................................................................................................................................................................................
1830 PSS
5-396
Issue 1 June 2013

....................................................................................................................................................................................................................................

Set ains to enabled
MVAC VA port provisioning
The G port on the MVAC OT supports the OCH attributes for the eVOA ports (G{1-8})
on the MVAC card as defined in the following table.
The following OCH attributes are provisionable on the MVAC G interface:

Provisionable
Attribute
moduletype
following:
fVOA fast VOA
sVOA slow VOA

MVAC8B OT port state provisioning
The states of the C{1-8} ports are provisioned independently. The following port states
are supported:

....................................................................................................................................................................................................................................
1830 PSS
5-397
Issue 1 June 2013

....................................................................................................................................................................................................................................
Set ains to enabled
MVAC8B client port provisioning
The following attributes are provisionable on the MVAC8B C{1-8} port:

Provisionable
Attribute
description
Specifies a description for the interface port. Enter this keyword

followed by string that describes the interface, or enter this keyword
interface.
detail
Display the current settings for the selected port.
PM
Set the Performance Monitoring attributes.
state
Sets the port state.
type
Specifies the port type:
set to och to set the port to OCH.
MVAC8B line port provisioning
The following attributes are provisionable on the MVAC8B L{1-8} port:
....................................................................................................................................................................................................................................
1830 PSS
5-398
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channel
Attribute that configures the frequency of the channel at the L{1-8}
port output of the MVAC8B:
Set to {0, 9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515, 9510,
9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465, 9460, 9455,
9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410, 9405, 9400,
9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355, 9350, 9345,
9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300, 9295, 9290,
9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245, 9240, 9235,
9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190, 9185, 9180,
9175, 9170}
The configured channel value is only used for manual power
management.
description

interface.
detail
PM
power
Specifies the expected optical output power level of the L{1-8} port.
Choose a value from between the range -20 dBm to +4 dBm.
The provisioned power value is only used for manual power
management.
state
type
SVAC OT port state provisioning
The states of the C1 port are provisioned independently. The following port states are
supported:

....................................................................................................................................................................................................................................
1830 PSS
5-399
Issue 1 June 2013

....................................................................................................................................................................................................................................
Set ains to enabled
SVAC client port provisioning
The following attributes are provisionable on the SVAC C1 port:

Provisionable
Attribute
description

interface.
detail
PM
state
type
SVAC line port provisioning
The following attributes are provisionable on the SVAC L1 port:
....................................................................................................................................................................................................................................
1830 PSS
5-400
Issue 1 June 2013

....................................................................................................................................................................................................................................
Provisionable
Attribute
channel
Attribute that configures the frequency of the channel at the L1 port
output of the SVAC.
Set to {0, 9605, 9600, 9595, 9590, 9585, 9580, 9575, 9570, 9565,
9560, 9555, 9550, 9545, 9540, 9535, 9530, 9525, 9520, 9515, 9510,
9505, 9500, 9495, 9490, 9485, 9480, 9475, 9470, 9465, 9460, 9455,
9450, 9445, 9440, 9435, 9430, 9425, 9420, 9415, 9410, 9405, 9400,
9395, 9390, 9385, 9380, 9375, 9370, 9365, 9360, 9355, 9350, 9345,
9340, 9335, 9330, 9325, 9320, 9315, 9310, 9305, 9300, 9295, 9290,
9285, 9280, 9275, 9270, 9265, 9260, 9255, 9250, 9245, 9240, 9235,
9230, 9225, 9220, 9215, 9210, 9205, 9200, 9195, 9190, 9185, 9180,
9175, 9170}
The configured channel value is only used for manual power
management.
description

interface.
detail
PM
power
Specifies the expected optical output power level of the L1 port.

Choose a value from between the range -20 dBm to +4 dBm.
The provisioned power value is only used for manual power
management.
state
type
....................................................................................................................................................................................................................................
1830 PSS
5-401
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to provision ports.

The port types that can be created and deleted are:
A2325A/AHPHG/AHPLG/ALPHG OSC port

A2P2125, AM2125A, AM2125B, AM2318A, OSCSFP port
OSCT card OSCSFP port
All OT Client ports
4DPA4: L{1,2}, only when Card Mode = FlexMux

4DPA4 : VA{1,2}
10AN10G: {1-10}
24ANM: {1-24}
24ET1GB: {1-24}
11DPE12(A/E) : L{1,2}, VA{1,2}
11DPM12 : L{1,2}, VA{1,2}
11QCUPC : L{1-4}, VA{1-4}

11QPA4/11QPEN4 : L{1-4}, VA{1-4}
11QPE24 : X{1-4}, VA{1-4}
CWR8 and CWR8-88 CLS {1-8}

PF: TRUMON
PTPCTL: P{1-6}
Related information
See Port/facility provisioning (p. 5-190).

Before you begin
11STAR1/11STAR1A line port (L1)
Note: The line port is automatically created and deleted with the
11STAR1/11STAR1A card.
The following procedure describes how to view or modify the 11STAR1/11STAR1A line
port settings.
....................................................................................................................................................................................................................................
1830 PSS
5-402
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the 11STAR1/11STAR1A OT in the equipment tree to show ports. Select L1 line
port.
Result: OTU2 attributes are displayed under the OTU2 Details tab. For ODU2
attributes, select the ODU2 Details tab.
...................................................................................................................................................................................................
To modify line port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
11STAR1/11STAR1A client port (C1)
The following procedure describes how to create, view, or modify an

11STAR1/11STAR1A client port.
...................................................................................................................................................................................................
Expand the 11STAR1/11STAR1A OT in the equipment tree to show ports. Select C1

client port.
Result: For an unprovisioned client port, the Unprovisioned Client Port screen is
displayed.
Note: For a client port that is already provisioned, the Client Details screen is
displayed and attributes can be viewed or modified.
...................................................................................................................................................................................................
To create the client port, specify the primary state and signal rate of the port and click
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11STMM10 line port (L1)
Note: The line port is automatically created and deleted with the 11STMM10 card.
The following procedure describes how to view or modify the 11STMM10 line port
settings.
...................................................................................................................................................................................................
Expand the 11STMM10 OT in the equipment tree to show ports. Select L1 line port.
....................................................................................................................................................................................................................................
1830 PSS
5-403
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
11STMM10 client port (C1-C10)
The following procedure describes how to create, view, or modify an 11STMM10 client
port.
...................................................................................................................................................................................................
Expand the 11STMM10 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11STGE12 line port (L1)
Note: The line port is automatically created and deleted with the 11STGE12 card.
The following procedure describes how to view or modify the 11STGE12 line port
settings.
...................................................................................................................................................................................................
Expand the 11STGE12 OT in the equipment tree to show ports. Select L1 line port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-404
Issue 1 June 2013

....................................................................................................................................................................................................................................
11STGE12 client port (C1-C12)
Note: Only ports 1-10 are provisionable. Ports 11 and 12 are not supported.
The following procedure describes how to create, view, or modify an 11STGE12 client
port.
...................................................................................................................................................................................................
Expand the 11STGE12 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11DPE12(A/E) line port (L1, L2)
The following procedure describes how to create, view, or modify the 11DPE12(A/E) line
port settings.
...................................................................................................................................................................................................
Expand the 11DPE12(A/E) OT in the equipment tree to show ports. Select L1 or L2 line
port.
Result: For an unprovisioned line port, the Unprovisioned Line Port screen is
displayed.
Note: For a line port that is already provisioned, the Line Details screen is
...................................................................................................................................................................................................

...................................................................................................................................................................................................
For OTU2 attributes, select the OTU2 Details tab. For ODU2 attributes, select the ODU2
Details tab.
....................................................................................................................................................................................................................................
1830 PSS
5-405
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To modify OTU2 or ODU2 line port settings, enter parameters and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11DPE12(A/E) VA port (VA1, VA2)
The following procedure describes how to create, view, or modify the 11DPE12(A/E) VA
port settings.
...................................................................................................................................................................................................
Expand the 11DPE12(A/E) OT in the equipment tree to show ports. Select VA1 or VA2
port.
Result: For an unprovisioned VA port, the Unprovisioned VA Port screen is displayed.
Note: For a VA port that is already provisioned, the VA Details screen is displayed
and attributes can be viewed or modified.
...................................................................................................................................................................................................
To modify VA port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
11DPE12(A/E) client port (C1-C12)
The following procedure describes how to create, view, or modify an 11DPE12(A/E)

client port.
...................................................................................................................................................................................................
Expand the 11DPE12(A/E) OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-406
Issue 1 June 2013

....................................................................................................................................................................................................................................
11DPM12 line port (L1, L2)
The following procedure describes how to create, view, or modify the 11DPM12 line port
settings.
...................................................................................................................................................................................................
Expand the 11DPM12 OT in the equipment tree to show ports. Select L1 or L2 line port.
displayed.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
11DPM12 VA port (VA1, VA2)
The following procedure describes how to create, view, or modify the 11DPM12 VA port
settings.
...................................................................................................................................................................................................
Expand the 11DPM12 OT in the equipment tree to show ports. Select VA1 or VA2 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-407
Issue 1 June 2013

....................................................................................................................................................................................................................................
11DPM12 client port (C1-C12)
The following procedure describes how to create, view, or modify an 11DPM12 client
port.
...................................................................................................................................................................................................
Expand the 11DPM12 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11QPA4/11QPEN4 line port (L1-L4)
The following procedure describes how to create, view, or modify the 11QPA4/11QPEN4
line port settings.
...................................................................................................................................................................................................
Expand the 11QPA4/11QPEN4 OT in the equipment tree to show ports. Select the line
port.
displayed.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Attention: The following steps are provided for 11QPEN4 encryption provisioning.
....................................................................................................................................................................................................................................
1830 PSS
5-408
Issue 1 June 2013

....................................................................................................................................................................................................................................
Modify the line port settings.

...................................................................................................................................................................................................
Go to the Encryption attributes screen.

Note: Enabling encryption requires coordinated provisioning at both ends of an
encrypted service.
...................................................................................................................................................................................................
Provision WKAT and nextkey and click Submit .

Note: The key must be exactly 64 hex symbols long (0-9, A-F - valid input)
...................................................................................................................................................................................................
Repeat provisioning of same WKAT and nextkey at the 11QPEN4 port at the other end of
the encrypted service and click Submit.
...................................................................................................................................................................................................
Click the checkbox for encryption enabled and click Submit.

...................................................................................................................................................................................................
10
Click the checkbox for encryption enabled at the other end of the encrypted service and
click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11QPA4/11QPEN4 VA port (VA1-VA4)
The following procedure describes how to create, view, or modify the 11QPA4/11QPEN4
VA port settings.
...................................................................................................................................................................................................
Expand the 11QPA4/11QPEN4 OT in the equipment tree to show ports. Select the VA
port..
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-409
Issue 1 June 2013

....................................................................................................................................................................................................................................
11QPA4/11QPEN4 client port (C1-C4)
The following procedure describes how to create, view, or modify an 11QPA4/11QPEN4

client port.
...................................................................................................................................................................................................
Expand the 11QPA4/11QPEN4 OT in the equipment tree to show ports. Select the client
port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11QPE24 line port (X1-X4)
The following procedure describes how to create, view, or modify the 11QPE24 line port
settings.
...................................................................................................................................................................................................
Expand the 11QPE24 OT in the equipment tree to show ports. Select line port.
displayed.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-410
Issue 1 June 2013

....................................................................................................................................................................................................................................
11QPE24 VA port (VA1-VA4)
The following procedure describes how to create, view, or modify the 11QPE24 VA port
settings.
...................................................................................................................................................................................................
Expand the 11QPE24 OT in the equipment tree to show ports. Select the VA port..
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
11QPE24 client port (C1-C22)
The following procedure describes how to create, view, or modify an 11QPE24 client
port.
...................................................................................................................................................................................................
Expand the 11QPE24 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
11QCUPC line port {L1-L4}
Note: The WebUI supports creation of 11QCUPC line ports. The supported signal
rates are dependent on the port group mode.
The WebUI supports modify and view of 11QCUPC line ports. The user must first
specify the port role when creating the port.
....................................................................................................................................................................................................................................
1830 PSS
5-411
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following procedure describes how to create, view, or modify the 11QCUPC line port
settings.
...................................................................................................................................................................................................
Click on the 11QCUPC OT in the equipment tree.

Result: Card Properties screen is displayed. To modify, enter desired properties and
click Submit.
...................................................................................................................................................................................................
To assign a Port Group, select the Port Groups tab.

Specify the Port Group mode and click Submit.
...................................................................................................................................................................................................
To create a port, select desired line portL1-L4 from the equipment tree.
Result: For an unprovisioned port, the Unprovisioned Port screen is displayed.
Note: For a port that is already provisioned, the Card Properties screen is
...................................................................................................................................................................................................
Enter Signal Rate and Primary State and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
11QCUPC VA port {VA1-VA4}
Note: The WebUI supports creation of 11QCUPC VA ports.

The WebUI supports modify and view of 11QCUPC VA ports.
The following procedure describes how to create, view, or modify the 11QCUPC VA port
settings.
...................................................................................................................................................................................................
Click on the 11QCUPC OT in the equipment tree.

click Submit.
...................................................................................................................................................................................................
To create a port, select desired portVA1-VA4 from the equipment tree.

....................................................................................................................................................................................................................................
1830 PSS
5-412
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
10AN10G port {1-10}
Note: The WebUI supports creation of 10AN10G ports. The supported signal rates are
dependent on the port group mode.
The WebUI supports modify and view of 10AN10G ports. The user must first specify
the port role when creating the port.
The following procedure describes how to create, view, or modify the 10AN10G port
settings.
...................................................................................................................................................................................................
Click on the 10AN10G OT in the equipment tree.

click Submit.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
To create a port, select desired Port 1-10 from the equipment tree.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
24ANM Port {1-24}
Note: The WebUI supports creation of 24ANM ports. The supported signal rates are
The WebUI supports modify and view of 24ANM ports. The user must first specify
....................................................................................................................................................................................................................................
1830 PSS
5-413
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following procedure describes how to create, view, or modify the 24ANM port
settings.
...................................................................................................................................................................................................
Click on the 24ANM OT in the equipment tree.

click Submit.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
24ET1GB Port {1-24}
Note: The WebUI supports creation of 24ET1GB ports. The supported signal rates are
The WebUI supports modify and view of 24ET1GB ports. The user must first specify
The following procedure describes how to create, view, or modify the 24ET1GB port
settings.
...................................................................................................................................................................................................
Click on the 24ET1GBOT in the equipment tree.

click Submit.
...................................................................................................................................................................................................

....................................................................................................................................................................................................................................
1830 PSS
5-414
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
112PDM11 line port (L1)
Note: The line port is automatically created and deleted with the 112PDM11 card.
The following procedure describes how to view or modify the 112PDM11 line port
settings.
...................................................................................................................................................................................................
Expand the 112PDM11 OT in the equipment tree to show ports. Select L1 line port.
Result: OTL4.4 attributes are displayed under the OTL4.4 Details tab.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
112PDM11 line port (L2-L4)
Note: The line port is automatically created and deleted with the 112PDM11 card.
Provisioning for ports {L2-L4} is different than L1 The WebUI supports view-only of
the 112PDM11 line ports (L2-L4) attributes
The following procedure describes how to view the 112PDM11 line port settings.
...................................................................................................................................................................................................
Expand the 112PDM11 OT in the equipment tree to show ports. Select L2-L4 line port.
Result: OTL4.4 attributes are displayed under the OTL4.4 Details tab.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-415
Issue 1 June 2013

....................................................................................................................................................................................................................................
112PDM11 client port (C1-C10)
The following procedure describes how to create, view, or modify an 112PDM11 client
port.
...................................................................................................................................................................................................
Expand the 112PDM11 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
112SCA1 / 112SNA1 line port (L1)
Note: The line port is automatically created and deleted with the 112SCA1/112SNA1
card.
The following procedure describes how to view or modify the 112SCA1/112SNA1 line
port settings.
...................................................................................................................................................................................................
Expand the 112SCA1/112SNA1 OT in the equipment tree to show ports. Select L1 line
port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
112SCA1 / 112SNA1 client port (C1)
The following procedure describes how to create, view, or modify an 112SCA1/112SNA1

client port.
....................................................................................................................................................................................................................................
1830 PSS
5-416
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the 112SCA1/112SNA1 OT in the equipment tree to show ports. Select C1 client
port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
112SCX10 / 112SNX10 / 130SCX10 line port (L1)
Note: The line port is automatically created and deleted with the
112SCX10/112SNX10/130SCX10 card.
The following procedure describes how to view or modify the
112SCX10/112SNX10/130SCX10 line port settings.
...................................................................................................................................................................................................
Expand the 112SCX10/112SNX10/130SCX10 OT in the equipment tree to show ports.

Select L1 line port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
112SCX10 / 112SNX10 / 130SCX10 client port (C1-C10)
The following procedure describes how to create, view, or modify an

112SCX10/112SNX10/130SCX10 client port.
...................................................................................................................................................................................................
Expand the 112SCX10/112SNX10/130SCX10 OT in the equipment tree to show ports.

Select the client port.
....................................................................................................................................................................................................................................
1830 PSS
5-417
Issue 1 June 2013

....................................................................................................................................................................................................................................
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
130SCUP line port (L1)
Note: The line port is automatically created and deleted with the 130SCUP card.
The following procedure describes how to view or modify the 130SCUP line port
settings.
...................................................................................................................................................................................................
Expand the 130SCUP OT in the equipment tree to show ports. Select L1 line port.
Result: Attributes are displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
4DPA4 line port (L1, L2)
The following procedure describes how to create, view, or modify the 4DPA4 line port
settings.
...................................................................................................................................................................................................
Expand the 4DPA4 OT in the equipment tree to show ports. Select L1 or L2 line port.
displayed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
5-418
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
4DPA4 VA port (VA1, VA2)
The following procedure describes how to create, view, or modify the 4DPA4 VA port
settings.
...................................................................................................................................................................................................
Expand the 4DPA4 OT in the equipment tree to show ports. Select VA1 or VA2 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
4DPA4 client port (C1-C4)
The following procedure describes how to create, view, or modify a 4DPA4 client port.
...................................................................................................................................................................................................
Expand the 4DPA4 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-419
Issue 1 June 2013

....................................................................................................................................................................................................................................
4DPA2 line port (L1, L2)
Note: The line port is automatically created when the client port is created.
The following procedure describes how to view or modify the 4DPA2 line port settings.
...................................................................................................................................................................................................
Expand the 4DPA2 OT in the equipment tree to show ports. Select L1 or L2 line port.
Result: Attributes are displayed under the Details tab.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
4DPA2 client port (C1-C2)
The following procedure describes how to create, view, or modify a 4DPA2 client port.
...................................................................................................................................................................................................
Expand the 4DPA2 OT in the equipment tree to show ports. Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
43SCA1 line port (L1)
Note: The line port is automatically created and deleted with the 43SCA1 card.
The following procedure describes how to view or modify the 43SCA1 line port settings.
...................................................................................................................................................................................................
Expand the 43SCA1 OT in the equipment tree to show ports. Select L1 line port.
Result: 43SCA1 line port attributes are displayed under the Port Details tab.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
5-420
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Details tab.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
43SCA1 client port (C1)
The following procedure describes how to create, view, or modify a 443SCA1 client port.
...................................................................................................................................................................................................
Expand the 43SCA1 OT in the equipment tree to show ports. Select C1 client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
43SCGE1 line port (L1)
Note: The line port is automatically created and deleted with the 43SCGE1 card.
The following procedure describes how to view or modify the 43SCGE1 line port
settings.
...................................................................................................................................................................................................
Expand the 43SCGE1 OT in the equipment tree to show ports. Select L1 line port.
Result: 43SCGE1 line port attributes are displayed under the Port Details tab.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
....................................................................................................................................................................................................................................
1830 PSS
5-421
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
43SCGE1 client port (C1)
The following procedure describes how to create, view, or modify a 43SCGE1 client port.
...................................................................................................................................................................................................
Expand the 43SCGE1 OT in the equipment tree to show ports. Select C1 client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
43SCX4 / 43SCX4E / 43STX4(P) line port (L1)
Note: The line port is automatically created and deleted with the 43SCX4 / 43SCX4E
/ 43STX4(P) card.
The following procedure describes how to view or modify the 43SCX4 / 43SCX4E /
43STX4(P) line port settings.
...................................................................................................................................................................................................
Expand the 43SCX4 / 43SCX4E / 43STX4(P) OT in the equipment tree to show ports.
Select L1 line port.
Result: 43SCX4 / 43SCX4E / 43STX4(P) line port attributes are displayed under the
Port Details tab.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
....................................................................................................................................................................................................................................
1830 PSS
5-422
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
43SCX4 / 43SCX4E / 43STX4(P) client port (C1-C4)
The following procedure describes how to create, view, or modify a 43SCX4 / 43SCX4E
/ 43STX4(P) client port.
...................................................................................................................................................................................................
Expand the 43SCX4 / 43SCX4E / 43STX4(P) OT in the equipment tree to show ports.
Select the client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
43STA1P line port (L1)
Note: The line port is automatically created and deleted with the 43STA1P card.
The following procedure describes how to view or modify the 43STA1P line port settings.
...................................................................................................................................................................................................
Expand the 43STA1P OT in the equipment tree to show ports. Select L1 line port.
Result: 43STA1P line port attributes are displayed under the Port Details tab.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Details tab.
....................................................................................................................................................................................................................................
1830 PSS
5-423
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
43STA1P client port (C1)
The following procedure describes how to create, view, or modify a 43STA1P client port.
...................................................................................................................................................................................................
Expand the 43STA1P OT in the equipment tree to show ports. Select C1 client port.
displayed.
...................................................................................................................................................................................................
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
A2325A/AHPHG/AHPLG/ALPHG LINE port
Note: The LINE port is automatically created and deleted with the
A2325A/AHPHG/AHPLG/ALPHG card.
A2325A/AHPHG/AHPLG/ALPHG LINE port settings.
...................................................................................................................................................................................................
Expand the A2325A/AHPHG/AHPLG/ALPHG in the equipment tree to show ports.

Select LINE port.
Result: Provisionable settings are displayed under the Port Details tab.
...................................................................................................................................................................................................
To modify port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-424
Issue 1 June 2013

....................................................................................................................................................................................................................................
A2325A/AHPHG/AHPLG/ALPHG SIG port
Note: The SIG port is automatically created and deleted with the
A2325A/AHPHG/AHPLG/ALPHG card.
A2325A/AHPHG/AHPLG/ALPHG SIG port settings.
...................................................................................................................................................................................................

Select SIG port.
Result: Provisionable settings are displayed under the Port Details tab. To display
SIG port attributes, select the SIG Details tab.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
A2325A/AHPHG/AHPLG/ALPHG/ OSC port
The following procedure describes how to create, view, or modify the

A2325A/AHPHG/AHPLG/ALPHG/OSC port settings.
...................................................................................................................................................................................................

Select OSC port.
Result: For an unprovisioned OSC port, the WebUI supports creation of the OSC port
and will set the value = OTS in the create request.

Note: For an OSC port that is already provisioned, the provisionable settings can
be viewed or modified.
...................................................................................................................................................................................................
To create the OSC port, enter pluggable module type and primary state and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
A2325A/AHPHG/AHPLG/ALPHG/AM2125A DCM port
Note: A2325A/AHPHG/AHPLG/ALPHG/AM2125A
A2325A/AHPHG/AHPLG/ALPHG/AM2125A DCM port settings.
....................................................................................................................................................................................................................................
1830 PSS
5-425
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the A2325A/AHPHG/AHPLG/ALPHG/AM2125A in the equipment tree to show

ports. Select DCM port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
OSCT LINE port
Note: The LINE port is automatically created and deleted with the OSCT card.
The following procedure describes how to view or modify the OSCT LINE port settings.
...................................................................................................................................................................................................
Expand the OSCT in the equipment tree to show ports. Select LINE port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
OSCT SIG port
Note: The SIG port is automatically created and deleted with the OSCT card.
The following procedure describes how to view or modify the OSCT SIG port settings.
...................................................................................................................................................................................................
Expand the OSCT in the equipment tree to show ports. Select SIG port.
Result: Provisionable settings are displayed under the Port Details tab. To display
SIG port attributes, select the SIG Details tab.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-426
Issue 1 June 2013

....................................................................................................................................................................................................................................
A2P2125/AM2125A/AM2125B/AM2318A/OSCT OSC port

A2P2125/AM2125A/AM2125B/AM2318A/OSCT OSC port settings.
...................................................................................................................................................................................................
Expand the A2P2125/AM2125A/AM2125B/AM2318A/OSCT in the equipment tree to

show ports. Select OSC port.
Result: For an unprovisioned OSC port, the WebUI supports creation of the OSC port
and will set the value = OTS in the create request.

Note: For an OSC port that is already provisioned, the provisionable settings can
be viewed or modified.
...................................................................................................................................................................................................
To create the OSC port, enter pluggable module type and primary state and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
A2P2125/AM2125A/AM2125B/AM2318A/OSCT OSCSFP port

A2P2125/AM2125A/AM2125B/AM2318A/OSCT OSCSFP port settings.
...................................................................................................................................................................................................
Expand the A2P2125/AM2125A/AM2125B/AM2318A/OSCT in the equipment tree to

show ports. Select OSCSFP port.
Result: For an unprovisioned OSCSFP port, the WebUI supports creation of the
OSCSFP port.
Note: For an OSCSFP port that is already provisioned, the provisionable settings
can be viewed or modified.
...................................................................................................................................................................................................
To create the OSCSFP port, enter pluggable module type and primary state and click
Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
A2P2125/AM2125A/AM2125B/AM2318A LINEIN port
Note: The LINEIN port is automatically created and deleted with the
A2P2125/AM2125A/AM2125B/AM2318A card.
....................................................................................................................................................................................................................................
1830 PSS
5-427
Issue 1 June 2013

....................................................................................................................................................................................................................................

A2P2125/AM2125A/AM2125B/AM2318A LINEIN port settings.
...................................................................................................................................................................................................
Expand the A2P2125/AM2125A/AM2125B/AM2318A in the equipment tree to show

ports. Select LINEIN port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
A2P2125/AM2125A/AM2125B/AM2318A LINEOUT port
Note: The LINEOUT port is automatically created and deleted with the
A2P2125/AM2125A/AM2125B/AM2318A card.
Note: When the cover is removed from the output port of
A2P2125/AM2125A/AM2125B/AM2318A equipped with a protective cover switch,
the optical amplifier will shut down. The shut down occurs within 150 ms of the time
that the cover is removed. An APR-Active Port Switch condition is raised against the :
A2P2125/AM2125A/AM2125B/AM2318A - LINE OUT port.
A2P2125/AM2125A/AM2125B/AM2318A LINEOUT port settings.
...................................................................................................................................................................................................
Expand the AM2125A/AM2125B/AM2318A in the equipment tree to show ports. Select

LINEOUT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
CWR8/CWR8-88 SIG port
Note: The SIG port is automatically created and deleted with the CWR8/CWR8-88
card.
The following procedure describes how to view or modify the CWR8/CWR8-88 SIG port
settings.
....................................................................................................................................................................................................................................
1830 PSS
5-428
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select SIG port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
CWR8/CWR8-88 OMD port
Note: The OMD port is automatically created and deleted with the CWR8/CWR8-88
card.
The following procedure describes how to view or modify the CWR8/CWR8-88 OMD
port settings.
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select OMD port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
CWR8/CWR8-88 THRU port
Note: The THRU port is automatically created and deleted with the
CCWR8/CWR8-88 card.
The following procedure describes how to view or modify the CWR8/CWR8-88 THRU
port settings.
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select THRU port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-429
Issue 1 June 2013

....................................................................................................................................................................................................................................
CWR8/CWR8-88 CLS [1-8] ports
The following procedure describes how to create, view, or modify the CWR8/CWR8-88
CLS [1-8] port settings.
...................................................................................................................................................................................................
Expand the CWR8/CWR8-88 in the equipment tree to show ports. Select the CLS port..
Result: For an unprovisioned CLS port, the Unprovisioned CLS Port screen is
displayed.
Note: For a CLS port that is already provisioned, the CLS Details screen is
...................................................................................................................................................................................................
To modify CLS port settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
DCM port
Note: The DCM port is automatically created and deleted with the DCM card.
The following procedure describes how to view or modify the DCM DCM port settings.
...................................................................................................................................................................................................
Expand the DCM in the equipment tree to show ports. Select DCM port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
EC CIT port
Note: The CIT port is automatically created and deleted with the EC card.
The following procedure describes how to view or modify the EC CIT port settings.
...................................................................................................................................................................................................
Expand the EC in the equipment tree to show ports. Select CIT port.
....................................................................................................................................................................................................................................
1830 PSS
5-430
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
EC ES1 and ES2 ports
Note: The ES1 and ES2 ports are automatically created and deleted with the EC card.
The following procedure describes how to view or modify the EC ES1 and ES2 port
settings.
...................................................................................................................................................................................................
Expand the EC in the equipment tree to show ports. Select ES1 or ES2 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MTC1T9 CIT port
Note: The CIT port is automatically created and deleted with the MTC1T9 card.
The following procedure describes how to view or modify the MTC1T9 CIT port settings.
...................................................................................................................................................................................................
Expand the MTC1T9 in the equipment tree to show ports. Select CIT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MTC1T9 E1/E2 and ES1/ES2 ports
Note: The E1/E2 and ES1/ES2 ports are automatically created and deleted with the
MTC1T9 card.
....................................................................................................................................................................................................................................
1830 PSS
5-431
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following procedure describes how to view or modify the MTC1T9 E1/E2 and
ES1/ES2 port settings.
...................................................................................................................................................................................................
Expand the MTC1T9 in the equipment tree to show ports. Select E1/E2 or ES1/ES2 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MTC1T9 OAMP port
Note: The OAMP port is automatically created and deleted with the MTC1T9 card.
The following procedure describes how to view or modify the MTC1T9 OAMP port
settings.
...................................................................................................................................................................................................
Expand the MTC1T9 in the equipment tree to show ports. Select OAMP port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MESH4 SIGIN and SIGOUT [1-4] ports
Note: The SIGIN and SIGOUT [1-4] ports are automatically created and deleted with
the MESH4 card.
The following procedure describes how to view or modify the MESH4 SIGIN and
SIGOUT [1-4] port settings.
...................................................................................................................................................................................................
Expand the MESH4 in the equipment tree to show ports. Select SIGIN or SIGOUT [1-4]
port.
....................................................................................................................................................................................................................................
1830 PSS
5-432
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
OPSA/OPSB A and B ports
Note: The A and B ports are automatically created and deleted with the OPSA/OPSB
card.
The following procedure describes how to view or modify the OPSA/OPSB A and B port
settings.
...................................................................................................................................................................................................
Expand the OPSA/OPSB in the equipment tree to show ports. Select A or B port.
Note: The settings are view-only for users with Observer and Provisioner
privileges.
...................................................................................................................................................................................................

Note: Switching Threshold and Switching Threshold Tolerance can only be modified
if Switching Threshold Calculation Mode = Manual and the user has Admin or
Service level privileges. These attributes are viewable by all user types.
E...................................................................................................................................................................................................
N D O F S T E P S
OPSA/OPSB SIG port
Note: The SIG port is automatically created and deleted with the OPSA/OPSB card.
The following procedure describes how to view or modify the OPSA/OPSB SIG port
settings.
...................................................................................................................................................................................................
Expand the OPSA/OPSB in the equipment tree to show ports. Select SIG port.
....................................................................................................................................................................................................................................
1830 PSS
5-433
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
PF TRUMON port
Note: The PF TRUMON port is supported on the PF for the PSS-32S shelf only.
The following procedure describes how to create, view, or modify the PF TRUMON port
settings. . For creation, the user will specify the signal rate of the port.
...................................................................................................................................................................................................
Expand the PF OT in the equipment tree to show ports. Select desired port.
Note: For a PF port that is already provisioned, the Details screen is displayed and
attributes can be viewed or modified.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
PTPCTL P port (1-6)
The following procedure describes how to create, view, or modify the PTPCTL P port
settings.
...................................................................................................................................................................................................
Expand the PTPCTL OT in the equipment tree to show ports. Select desired port.
Note: For a P port that is already provisioned, the Details screen is displayed and
attributes can be viewed or modified.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-434
Issue 1 June 2013

....................................................................................................................................................................................................................................
PTPCTL BITS port (1-2), TOD port (1-2)
Note: The ports are automatically created and deleted with the PTPCTL card.
The following procedure describes how to view or modify the PTPCTL port settings.
...................................................................................................................................................................................................
Expand the PTPCTL OT in the equipment tree to show ports. Select desired port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
PTPIO line port (1-2), SIG port (1-2), TP port (1-2), ITP port (1-2)
Note: The port are automatically created and deleted with the PTPIO card.
The following procedure describes how to view or modify the PTPIO port settings.
...................................................................................................................................................................................................
Expand the PTPIO OT in the equipment tree to show ports. Select desired port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
RA2P LINEIN port
Note: The LINEIN port is automatically created and deleted with the RA2P card.
The following procedure describes how to view or modify the RA2P LINEIN port
settings.
...................................................................................................................................................................................................
Expand the RA2P in the equipment tree to show ports. Select LINEIN port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-435
Issue 1 June 2013

....................................................................................................................................................................................................................................
RA2P LINEOUT port
Note: The LINEOUT port is automatically created and deleted with the RA2P card.
The following procedure describes how to view or modify the RA2P LINEOUT port
settings.
...................................................................................................................................................................................................
Expand the RA2P in the equipment tree to show ports. Select LINEOUT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
SFC/SFD OMD port, EXP port, and Channel ports
Note: The OMD port, EXP port, and Channel ports are automatically created and
deleted with the SFC/SFD card. The EXP port is not applicable to the SFD40,
SFD40B, SFD44, SFD44B, and SFC8.
Important! The default state for SFD channel and expansion ports is down and users
need to manually turn them up to In Service after provisioning these.
The following procedure describes how to view or modify the SFC/SFD OMD port, EXP
port, and Channel ports settings.
...................................................................................................................................................................................................
Expand the SFC/SFD in the equipment tree to show ports. Select OMD port, EXP port, or
Channel ports.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
ITLB SIG, E and O ports
Note: The SIG, E and O ports are automatically created and deleted with the
ITLB/ITLU card.
The following procedure describes how to view or modify the ITLB SIG, E and O port
settings.
....................................................................................................................................................................................................................................
1830 PSS
5-436
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the ITLB in the equipment tree to show ports. Select SIG, E or O port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
ITLU SIGIN, EOUT and OOUT ports
Note: The SIGIN, EOUT and OOUT ports are automatically created and deleted with
the ITLB/ITLU card.
The following procedure describes how to view or modify the ITLU SIGIN, EOUT and
OOUTport settings.
...................................................................................................................................................................................................
Expand the ITLU in the equipment tree to show ports. Select SIGIN, EOUT or OOUT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
SVAC L1 port
Note: The L1 port is automatically created and deleted with the SVAC card.
The following procedure describes how to view or modify the SVAC L1 port settings.
...................................................................................................................................................................................................
Expand the SVAC in the equipment tree to show ports. Select L1 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-437
Issue 1 June 2013

....................................................................................................................................................................................................................................
SVAC C1 port
Note: The C1 port is automatically created and deleted with the SVAC card.
The following procedure describes how to view or modify the SVAC C1 port settings.
...................................................................................................................................................................................................
Expand the SVAC in the equipment tree to show ports. Select C1 port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MVAC G [1-8] ports
Note: The G ports are automatically created and deleted with the MVAC card.
The following procedure describes how to view or modify the MVAC G [1-8] port
settings.
...................................................................................................................................................................................................
Expand the MVAC in the equipment tree to show ports. Select G [1-8] port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MVAC8B L [1-8] port
Note: The L [1-8] ports are automatically created and deleted with the MVAC8B card.
The following procedure describes how to view or modify the MVAC8B line port
settings.
...................................................................................................................................................................................................
Expand the MVAC8B in the equipment tree to show ports. Select L [1-8] port.
....................................................................................................................................................................................................................................
1830 PSS
5-438
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
MVAC8B C [1-8] port
Note: The C [1-8] ports are automatically created and deleted with the MVAC8B
card.
The following procedure describes how to view or modify the MVAC8B C [1-8] port
settings.
...................................................................................................................................................................................................
Expand the MVAC8B in the equipment tree to show ports. Select C [1-8].
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
USRPNL OAMP and VOIP ports
Note: The OAMP and VOIP ports are automatically created and deleted with the
USRPNL card.
The following procedure describes how to view or modify the USRPNL OAMP and
VOIP port settings.
...................................................................................................................................................................................................
Expand the USRPNL in the equipment tree to show ports. Select OAMP or VOIP port.
Result: Port Interface settings are displayed under the Port Details tab.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
To view or modify OSPF parameters for the OAMP and VOIP ports, select the OSPF
Details tab.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-439
Issue 1 June 2013

....................................................................................................................................................................................................................................
USRPNL E1 and E2 ports
Note: This procedure describes scenarios/configurations and procedures for setting up

the 1830 PSS DCN to manage external Raman/EDFA boxes connected to the 1830
User Panel E1/E2 ports.
The two external LAN ports, E1 and E2, connect to externally managed devices, like
RAMAN power booster amplifiers. To manage the third party Raman amplifiers, the
preferred way is to hook up the ethernet port of these to the E1/E2 ports of the
adjacent NE.
The following configuration scenarios are considered for the procedure:
1. Connecting Raman/EDFA to E1 and/or E2 of GNE/RNE.
2. Connecting Raman/EDFA to E1 and/or E2 of GNE/RNE with multiple GNEs in
the network.
3. Connecting Raman/EDFA to E1 and/or E2 via L2 Switch.
The following steps describe the DCN procedure for connecting Raman/EDFA boxes to
E1/E2 port:
...................................................................................................................................................................................................
In the WebUI expand the equipment tree to select System > PSS-32 Shelf > USRPNL > E1
or E2
Result: In the Port Details tab, the Port Interface Settings screen is displayed.
...................................................................................................................................................................................................
Assign an IP address and subnet mask to the E1/E2 port. Each E1/E2 port should be on a
unique subnet within the DCN. For example: Our GNE OAMP IP address was
192.168.5.57/20 so we configured the E1 IP to be 182.168.11.1/24 and the E2 to be
182.168.12.1/24. Ensure that the configured subnet does not overlap with any other
subnet in the DCN.
...................................................................................................................................................................................................
Click on the OSPF details tab and provision the E1/E2 port routestate to redistribute.
...................................................................................................................................................................................................
Click on the Port Details tab and provision the E1/E2 port admin state to up..
...................................................................................................................................................................................................
On the Raman/EDFA box, set the IP address in the same subnet as the E1/E2 port IP
address: for example, for the Raman connected to E1 set the Raman IP address and subnet
mask to be 182.168.11.170/24. Set the Raman/EDFA box default gateway IP address as
the IP address of the E1 port (in our case 182.168.11.1).
....................................................................................................................................................................................................................................
1830 PSS
5-440
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Connect the E1/E2 port of the PSS-32 to the Raman/EDFA Ethernet port. If more than
two Raman/EDFA boxes are necessary then a L2 switch may be placed between the
E1/E2 port and the Raman/EDFA boxes.
...................................................................................................................................................................................................
If using static routes to connect to the 1830 network from the customer DCN, than add
static routes for the E1/E2 subnets on all necessary customer routers. On every 1830 GNE
add a default route using the subtending router interface IP address and set the redistribute
option in the default route. If the OSPF routing protocol is used on the customer DCN
instead of static routes, then enable OSPF on all GNE OAMP ports (using cli set OAMP
port routestate to enable.
...................................................................................................................................................................................................
On all PhM servers or client PCs, it is necessary to modify the Ethernet NIC MTU size
from the default 1500 to 1491.
Note: This procedure needs to be followed for each Raman/EDFA box that is
connected to an E1/E2 port.
E...................................................................................................................................................................................................
N D O F S T E P S
WR2-88 SIG port
Note: The SIG port is automatically created and deleted with the WR2-88 card.
The following procedure describes how to view or modify the WR2-88 SIG port settings.
...................................................................................................................................................................................................
Expand the WR2-88 in the equipment tree to show ports. Select SIG port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR2-88 THRU port
Note: The THRU port is automatically created and deleted with the WR2-88 card.
The following procedure describes how to view or modify the WWR2-88 THRU port
settings.
....................................................................................................................................................................................................................................
1830 PSS
5-441
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the WR2-88 in the equipment tree to show ports. Select THRU port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR2-88 ADDIN [1-8] ports
Note: The ADDIN [1-8] port is automatically created and deleted with the WR2-88
card.
The following procedure describes how to view or modify the WR2-88 ADDIN [1-8] port
settings.
...................................................................................................................................................................................................
Expand the WR2-88 in the equipment tree to show ports. Select ADDIN [1-8] port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR2-88 DROPOUT port
Note: The DROPOUT port is automatically created and deleted with the WR2-88
card.
The following procedure describes how to view or modify the WR2-88 DROPOUT port
settings.
...................................................................................................................................................................................................
Expand the WR2-88 in the equipment tree to show ports. Select DROPOUT port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-442
Issue 1 June 2013

....................................................................................................................................................................................................................................
WR8-88A/WR8-88AF SIG port
Note: The SIG port is automatically created and deleted with the WR8-88A/WR888AF card.
The following procedure describes how to view or modify the WR8-88A/WR8-88AF SIG
port settings.
...................................................................................................................................................................................................
Expand the WR8-88A/WR8-88AF in the equipment tree to show ports. Select SIG port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A/WR8-88AF THRU port
Note: The THRU port is automatically created and deleted with the
WR8-88A/WR8-88AF card.
The following procedure describes how to view or modify the WR8-88A/WR8-88AF
THRU port settings.
...................................................................................................................................................................................................
Expand the WR8-88A/WR8-88AF in the equipment tree to show ports. Select THRU
port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A/WR8-88AFADDIN [1-8] ports
Note: The ADDIN [1-8] port is automatically created and deleted with the
ADDIN [1-8] port settings.
....................................................................................................................................................................................................................................
1830 PSS
5-443
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Expand the WR8-88A/WR8-88AF in the equipment tree to show ports. Select ADDIN
[1-8] port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A/WR8-88AF DROPOUT port
Note: The DROPOUT port is automatically created and deleted with the
DROPOUT port settings.
...................................................................................................................................................................................................
Expand the WR8-88A/WR8-88AF in the equipment tree to show ports. Select DROPOUT
port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WR8-88A/WR8-88AF MESHOUT [1-3] ports
Note: The MESHOUT [1-3] port is automatically created and deleted with the
WR8-88A card.
MESHOUT [1-3] port settings.
...................................................................................................................................................................................................
Expand the WR8-88A/WR8-88AF in the equipment tree to show ports. Select MESHOUT
[1-3] port.
....................................................................................................................................................................................................................................
1830 PSS
5-444
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
WTOCM/WTOCMA IN port (1-4)
Note: The WTOCM/WTOCMA IN ports are automatically created when the

WTOCM/WTOCMA pack is provisioned.
The following procedure describes how to view or modify the WTOCM/WTOCMA IN
port settings. An association between the WTOCM/WTOCMA IN port and the line side
port that it monitors must be provisioned.
...................................................................................................................................................................................................
Expand the WTOCM/WTOCMA in the equipment tree to show ports. Select IN port.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-445
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
Contents
5-447
Procedure 5-44: Retrieve current conditions for a system component
5-448
5-449
5-451
5-453
5-456
Procedure 5-47: Retrieve information related to equipment protection groups
5-457
5-459
5-460
5-462
5-463
5-465
....................................................................................................................................................................................................................................
1830 PSS
5-446
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve general properties of the system.

RTRV-PRMTR-NE
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Right-click on System in the selection tree, and select Properties General from the
Result: The Properties - General window opens, displaying the general properties of
the system.
Reference: See General properties of the system as a whole (p. 5-470).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-447
Issue 1 June 2013

Procedure 5-44: Retrieve current conditions for a system

component
....................................................................................................................................................................................................................................
Procedure 5-44: Retrieve current conditions for a system

component
When to use
Use this procedure to display the events and conditions that are currently present for a
system component.
RTRV-COND-EQPT
RTRV-COND-ALL
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Choose one of the following methods to invoke the View Current Conditions window for
the desired system component:
In the selection tree, right-click on System, and select View Current Conditions from
Expand the selection tree down to shelf level, then right-click on Shelf, and select
View Current Conditions from the context menu that opens.
Expand the selection tree down to board or facility level, then right-click the
respective board or facility in the main window, and select View Current Conditions
Result: The View Current Conditions window opens, displaying the events and
conditions that are currently present for the selected system component.
Reference: See View Current Conditions (p. 5-449).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-448
Issue 1 June 2013

....................................................................................................................................................................................................................................

Purpose
The View Current Conditions window serves to retrieve the current status of any
reported, alarmed, not alarmed or not reported conditions (also referred to as events in
the following) for a particular system component.
Parameters
Parameter
Value
Description
Name
Alphanumeric string of up to 20
characters.
The user-friendly name of the

system component.
Note that letters are always displayed

in uppercase.
AID Type
Please see Overview of access

identifiers (p. 5-548).
The access identifier of the

system component.
Notification Code
CR - Critical
The type of alarm generated by

the system upon occurrence of
the event.
MJ - Major
MN - Minor
WR - Warning
NA - Not Alarmed
NR - Not Reported
Condition Type
Please see Condition types (p. 5-450).
Service Affecting
NSA - Non service-affecting

SA - Service-affecting
Date Occured
Month and day in the form 'mm-dd'
Time Occured
Hour, minute and second in the form

'hh-mm-ss'
Location
NEND (Near end)

FEND (Far end)
Direction
RCV - Receive direction

TRMT - Transmit direction
The effect on service caused by

the event.
Date and time when the event
occurred.
The location where the

condition type is monitored.
Please also see Condition
types (p. 5-450).
The direction to which the
condition type relates to. Please
also see Condition types
(p. 5-450).
....................................................................................................................................................................................................................................
1830 PSS
5-449
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Value
Description
Monitored Value
{0 - 4294967295} (for digital values)
(for TCAs only)
51.0 - 51.0 (for analogue values)
The measured value of the

monitored parameter (at the
time when the TCA was raised).
Threshold Level
(for TCAs only)
Time Period
1-day
(for TCAs only)
15-minutes
The threshold level for the

The accumulation period for
performance monitoring
information (1-day or
15-minutes count).
Condition types
The condition types are described in the Alcatel-Lucent 1830 PSS Maintenance and
Trouble-Clearing Guide, chapter Alarm and condition details.
....................................................................................................................................................................................................................................
1830 PSS
5-450
Issue 1 June 2013

Procedure 5-45: Retrieve remote inventory for a system

component
....................................................................................................................................................................................................................................

component
When to use
Use this procedure to display remote inventory for any entity in the system, which is
physically present in the system and
is provisioned or
is the first un-provisioned entity in the equipment module hierarchy (e.g.: If an IOC is
un-provisioned, Remote-information is not retrievable from plugged in SFP/XFPs.)
RTRV-RI
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Right-click on the system in the selection tree, and select Properties Remote
Inventory from the context menu that opens.
Note: If no SLC is installed no Remote Inventory information of either the FLC nor
other system components can be retrieved. The SLC collects all Remote Inventory
information of the system also the Remote Inventory information info of the FLC.
The SLC then gives this info to the FLC, which makes it accessible using the ZIC.
If there are no Remote Inventory information for the FLC displayed, please at first
perform a refresh of the FLC by right-click on the FLC in the selection tree, and select
Refresh from the context menu that opens.
....................................................................................................................................................................................................................................
1830 PSS
5-451
Issue 1 June 2013


component
....................................................................................................................................................................................................................................
Result: The Remote Inventory window opens, displaying the remote inventory
information for the selected system component.

Reference: See Retrieve remote inventory (p. 5-453).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-452
Issue 1 June 2013

....................................................................................................................................................................................................................................

Purpose
The Remote Inventory window serves to retrieve the current status of any reported,
alarmed, not alarmed or not reported conditions (also referred to as events in the
following) for a particular system component.
The Remote Inventory window serves to retrieve remote inventory information for any
entity in the system, which is physically present in the system and
is provisioned
is the first un-provisioned entity in the equipment module hierarchy (e.g.: If an IOC is
un-provisioned, Remote-information is not retrievable from plugged in SFP/XFPs.)
Parameters
Parameter
Value

system component.
AID Type
COMPANY
Description
up to 14 bytes
Identifier of the board

manufacturer.
THIRDPARTYMOD indicates
that this SFP/XFP interface
module is a third party interface
module.
MNEMONIC
up to 12 Bytes>
The Alcatel-Lucent mnemonic

for the given equipment.
CLEI
up to 10 Bytes >
The CLEI code for the given

equipment.
PARTNUM
up to 14 Bytes
The Alcatel-Lucent part number

for the given equipment.
FACTORY
up to 4 Bytes / FACTORY
IDENTIFIER)
Identifier of the factory

manufacturer.
SERIAL
up to 18 Bytes (SERIAL NUMBER)
serial number
DATE
{{00-99}-{01-12}-{01-31}
The date the EPROM was

written. If only year and month
info are available, then the day
info shall be set to "01".
....................................................................................................................................................................................................................................
1830 PSS
5-453
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Value
Description
EXTRADATA
String collecting the remaining

characters, excluding checksum bytes,
with dash '-' characters replacing
non-printable ones; up to 46 Bytes
ASCII dump of the rest of the

bytes in the RI.
VENDORNAME
16 characters; (Text String)
Vendor Name of the third party

interface module (SFP/XFP)
The parameter is a ASCII
representation. Non-printable
ASCII characters are replaced
by a dot ('.') in the output.
VENDORCOMPANY
X{{0-9,A-F}{0-9,A-F}}[3] (hex
string)
Vendor Company code of the

third party interface module
(SFP/XFP)
VENDORPARTNUM
16 characters> (Text String)
Vendor Part Number of the third

party interface module
(SFP/XFP) The parameter is a
ASCII representation.
Non-printable ASCII characters
are replaced by a dot ('.') in the
output.
VENDORREVLVL
<2 characters> (Text String)
Vendor Revision Level of the

output.
VENDORSERIAL
<16 characters> (Text String)
Vendor Serial number of the

output.
VENDORDATE
{{00-99}-{01-12}-{01-31}
Vendor manufacturing Date of

the third party interface module
(SFP/XFP)
VENDORWAVELENGTH
{0 - 65535
Vendor Wavelength in
nanometer [nm] of the third
(SFP/XFP)
....................................................................................................................................................................................................................................
1830 PSS
5-454
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Value
Description
VENDORTRANSCODES
{BASE-PX, BASE-BX10,
100BASE-FX, 100BASE-LX-LX10,
1000BASE-T, 1000BASE-CX,
1000BASE-LX, 1000BASE-SX,
10GBASE-SR, 10GBASE-LR,
10GBASE-ER, 10GBASE-LRM,
10GBASE-SW, 10GBASE-LW,
10GBASE-EW, 1xFC-MMF,
1xFC-SMF, 2xFC-MMF, 2xFC-SMF,
1xFC-SX, 1xFC-LX,
1xFC-Copper-Active,
1xFC-Copper-Passive,
10GFC-1200-MX-SN-I,
10GFC-1200-SM-LL-L,
10GFC-ER-1550nm,
10GFC-IR-1300nm-FP,
ESCON-MMF, ESCON-SMF, I-64.1r,
I-64.1, I-64.2r, I-64.2, I-64.3, I-64.5,
S-64.1, S-64.2a, S-64.2b, S-64.3a,
S-64.3b, S-64.5a, S-64.5b, L-64.1,
L-64.2a, L-64.2b, L-64.2c, L-64.3,
P1L1-2D2, V-64.2a, V-64.2b, V-64.3,
OC192-SR, SONET-reach-specifierbit1, SONET-reach-specifier-bit2,
OC48-LR, OC48-IR, OC48-SR,
OC12-LR, OC12-IR, OC12-SR,
OC3-LR, OC3-IR, OC3-SR
Vendor Tranxceiver Codes of

the third party interface module
(SFP/XFP)
MMF (Multi Mode Fibre)
Vendor Fibre Type of the third

(SFP/XFP)
VENDORFIBERTYPE
SMF (Single Mode Fibre)

VENDORUSERDATA
up to 120 characters (Text String)
If more than one code is

supported by the SFP/XFP, the
different codes will be separated
by '&'.
Vendor User Data of the third

(SFP/XFP). An SFP interface
module returns 120 characters
of data. An XFP interface
module returns 32 characters of
data. Non-printable ASCII
characters are replaced by a dot
('.') in the output.
....................................................................................................................................................................................................................................
1830 PSS
5-455
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve TL1 parameters regarding TL1 encoding over TCP/IP.
RTRV-NE-TL1
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Right-click on System in the selection tree, and select TL1 Parameters from the context
menu that opens.
Result: The TL1 Parameters window opens, displaying parameters regarding TL1
encoding over TCP/IP.

Reference: See TL1 parameters (p. 5-579).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-456
Issue 1 June 2013

Procedure 5-47: Retrieve information related to equipment

protection groups
....................................................................................................................................................................................................................................

protection groups
When to use
Use this procedure to retrieve the relevant parameters related to the equipment protection
groups of FLCs and agnostic matrix cards.
ALW-SWDX-EQPT
INH-SWDX-EQPT
RTRV-DX-EQPT
SW-DX-EQPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the navigation pane of the Alcatel-Lucent 1830 PSS ZIC window, select Equipment in
the navigation tree.
...................................................................................................................................................................................................
Right-click on Equipment, and select Switching View from the context menu that
opens.
In the Action menu, select Switching View.
....................................................................................................................................................................................................................................
1830 PSS
5-457
Issue 1 June 2013


protection groups
....................................................................................................................................................................................................................................
Result: The View Duplex Switching Equipments window opens, displaying the
relevant parameters related to the equipment protection groups of FLCs and agnostic
matrix cards.
Reference: See Parameters of equipment protection groups (p. 5-539).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-458
Issue 1 June 2013

Procedure 5-48: Retrieve and edit optical channel

parameters
....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve all parameters related to an optical channel.

RTRV-OCH
ED-OCH
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the navigation pane of the Alcatel-Lucent 1830 PSS ZIC window,, select the desired
OCH port in the navigation tree underFacilities.
As a result, the OCH channels are displayed in the display pane.
...................................................................................................................................................................................................
Right-click on an OCH channel, and select Properties General from the context
menu that opens.
Result: The Properties General window opens, displaying the relevant parameters
related to the OCH .

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-459
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to perform diagnostic tests on the NE.

DGN-EQPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select Equipment Rack1 Shelf.
...................................................................................................................................................................................................
Right-click on Shelf in the selection tree, and select Diagnostics from the context menu
that opens.
Result: The Diagnose Equipment window opens, displaying the general properties of
the system.
...................................................................................................................................................................................................
Click on Send.
....................................................................................................................................................................................................................................
1830 PSS
5-460
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The on-demand diagnostic tests, provides the following information,
displayed as a table:
Parameter
Details
AID
Access identifier of equipment entity.

MTX-{1}-{1-31}-{71,72} (PSS-64 shelf)
MTX-{1}-{1-31}-{11,15} (PSS-36 shelf)
Matrix and Timing Card

LNKTOMTX
LNKFROMMTX
String, consisting of:
PSS64 subrack
Three heading letters for a quadrant coding "xyQ"
(x={L,R} for left or right quadrant and y={T,B} for the top
or bottom quadrant;
For PSS36 subrack.
-
16 digits for link set failure coding (one per I/O slot from
left upper to the right lower corner, first left to right then
top down) indicating the number of failed links out of the
number of used links from the I/O slots to the specified
matrix slot. The value range per digit is "0-9", "A", "-":
where the value 0 indicates no failure, the values 1-9
indicate partial link failures, the value A indicates that all
links are failed (at maximum 10), and the value - indicates
that the I/O slot is not equipped.
String, consisting of:
PSS64 subrack
Three heading letters for a quadrant coding "xyQ"
(x={L,R} for left or right quadrant and y={T,B} for the top
or bottom quadrant;
For PSS36 subrack.
-
16 digit positions for link set failure coding (one per I/O
slot from left upper to the right lower corner, first left to
right then top down) indicating the number of failed links
out of the number of used links from the specified matrix
slot to the I/O slots. The value range per digit is "0-9", "A",
"-": where the value 0 indicates no failure, the values 1-9
indicate partial link failures, the value A indicates that all
links are failed (at maximum 10), and the value - indicates
that the I/O slot is not equipped.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-461
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure turns on each LED in all shelves of the compound for 30 seconds
(color: amber). Then all LEDs return to their true states.
DGN-EQPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Right-click on the Shelf in the selection tree, and select LED Test from the context menu
that opens.
Result: The LED Test window opens, displaying the general properties of the system.
...................................................................................................................................................................................................
Click on Yes.
Result: All LED in all shelves of the compound are turned on for 30 seconds (color:
amber), with the following exceptions:
the status LED on the SFC8 lits green

the LOS LED on the SFC8 lits red
the critical alarm LED (LED3) on an FLC lits red

the major alarm LED (LED4) on an FLC lits red.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-462
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to check shelf cabling.

DGN-EQPT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Internal LAN
Then select VLAN Discovery, either by selecting Action from the main menu bar or by
Result: The VLAN Discovery window opens, displaying the general properties of the
system.
...................................................................................................................................................................................................
Click on Send.
Result: The on-demand diagnostic tests, provides the following information,
displayed as a table:
Parameter
Details
SHELFAID
AID representing the detected shelf. Note that an MDL AID is

used, as it is possible that a shelf is detected, which is not
provisioned, i.e. which has no "real SHELF AID".
MDL-1-<shelf>
....................................................................................................................................................................................................................................
1830 PSS
5-463
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
ES1L
Two character string indicating the neighboring shelf found on

the left side ES1 interface of the shelf identified by
SHELFAID.
If a neighboring shelf is detected, then its shelf id is given in
two digit decimal notation (using a leading 0 if required). The
shelf id of the main shelf is given as 01. If no neighboring shelf
is detected, then two dashes (--) are given.
ES1R

the right side ES1 interface of the shelf identified by
SHELFAID.
ES2L

the left side ES2 interface of the shelf identified by
SHELFAID.
ES2R

the right side ES2 interface of the shelf identified by
SHELFAID.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-464
Issue 1 June 2013

Procedure 5-52: Retrieval analog optical parameters from

optical modules
....................................................................................................................................................................................................................................

optical modules
When to use
Use this procedure to retrieve the following set of analog parameters from any optical
module in the system (pluggable as well as fixed mounted):
Optical input power

Optical output power
Laser bias current
Optical module current temperature
RTRV-DDM
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select an optical module via
Equipment Rack Shelf Slot Port
Then select Digital Diagnostic Monitoring, either by selecting Action from the main
Result: The Digital Diagnostic Monitoring window opens.
The on-demand diagnostic tests, provides the following information, displayed as a

table:
Parameter
Details
AID
Access identifier of equipment entity.
....................................................................................................................................................................................................................................
1830 PSS
5-465
Issue 1 June 2013


optical modules
....................................................................................................................................................................................................................................
Parameter
Details
PROVISIONEDTYPE
Provisioned interface module type.

SR12G7TU (maps to RI MNEMONIC: S2G7D2I)
IR12G7TU (maps to RI MNEMONIC: S2G7D15E)
LR12G7TU (maps to RI MNEMONIC: S2G7D40E)
LR22G7TU (maps to RI MNEMONIC: S2G7D80E )
IR12G7AU (maps to RI MNEMONIC: S2G7M15I )
1000BSXU (maps to RI MNEMONIC: S1GE05I )
1000BLXU (maps to RI MNEMONIC: S1GE10I )
1000BZXU (maps to RI MNEMONIC: S1GE80I )
SR111G1AU (maps to RI MNEMONIC: X11M10I )
IR211G1AU (maps to RI MNEMONIC: X11M40I )
LR211G1AU (maps to RI MNEMONIC: X11M80E )
LRT11G1TU (maps to RI MNEMONIC: X11MDTNC )
SR<xx>W11G1TUC (<xx>={47,49,51,53,55,57,59,61} ; maps
to RI MNEMONIC:X11MC<xx>SC)
SR<xx>W11G1TUI (<xx>={47,49,51,53,55} ; maps to RI
MNEMONIC: X11MC<xx>SI)
LR<xx>W11G1TUC (<xx>={47,49,51,53,55,57,59,61} ; maps
to RI MNEMONIC:X11MC<xx>LC)
Note: <xx> are the two middle digits for the actual wavelength,
e.g. <xx>=53 for a wavelength= 1531nm
SR10G155TU (maps to RI MNEMONIC: S155S15I)
SL10G155TU (maps to RI MNEMONIC: S155S40I)
FIXED (Optical module cannot be changed e.g. 2x 40G ANY
Card)
NOTAPPL (Not Applicable, for unprovisioned modules)
....................................................................................................................................................................................................................................
1830 PSS
5-466
Issue 1 June 2013


optical modules
....................................................................................................................................................................................................................................
Parameter
Details
Actual type
Physically equipped module type.

SR12G7TU (maps to RI MNEMONIC: S2G7D2I)
IR12G7TU (maps to RI MNEMONIC: S2G7D15E)
IR12G7AU (maps to RI MNEMONIC: S2G7M15I)
1000BSXU (maps to RI MNEMONIC: S1GE05I)
1000BLXU (maps to RI MNEMONIC: S1GE10I)
1000BZXU (maps to RI MNEMONIC: S1GE80I)
SR111G1AU (maps to RI MNEMONIC: X11M10I)
IR211G1AU (maps to RI MNEMONIC: X11M40I)
LR211G1AU (maps to RI MNEMONIC: X11M80E)
LRT11G1TU (maps to RI MNEMONIC: X11MDTNC)
SR<xx>W11G1TUC (<xx>={47,49,51,53,55,57,59,61} ; maps
to RI MNEMONIC:X11MC<xx>SC)
SR<xx>W11G1TUI (<xx>={47,49,51,53,55} ; maps to RI
MNEMONIC: X11MC<xx>SI)
LR<xx>W11G1TUC (<xx>={47,49,51,53,55,57,59,61} ; maps
to RI MNEMONIC:X11MC<xx>LC)
e.g. <xx>=53 for a wavelength= 1531nm
FIXED (Optical module cannot be changed e.g. 2x 40G ANY
Card)
UNKNOWN Unknown Type, the system cannot be determined
the type e.g. the RIM is corrupted or the card does not belong
to the 1830 system.
UNPLUGGED Unplugged , the module slot is empty.
Temperature
Measured Device Temperature. NA indicates that for specified

monitored type baselined value hasn't been established.
....................................................................................................................................................................................................................................
1830 PSS
5-467
Issue 1 June 2013


optical modules
....................................................................................................................................................................................................................................
Parameter
Details
TXBIASCURR
Measured Transmitter Laser BIAS Current. NA indicates that

for specified monitored type baselined value hasn't been
established.
TXPWR
Measured Output Power. NA indicates that for specified

RXPWR
Measured Input Power. NA indicates that for specified

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
5-468
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
Contents
5-470
5-480
5-482
5-483
5-484
5-489
5-497
5-501
5-509
5-520
5-531
5-539
5-541
5-548
TL1 parameters
5-579
....................................................................................................................................................................................................................................
1830 PSS
5-469
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The Properties - General window, invoked for the system, provides the following
information:
Parameter
Values
Details
AID
ACTSW
Identifies the entity for which the output data

are retrieved
(The active software

generic on the NE)
STBYSW (The standby
software generic on the
NE)
System Type
1830 PSS
Indicates the system type, 1830 PSS.
....................................................................................................................................................................................................................................
1830 PSS
5-470
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
Release
Identification
{E, F, P,
R}{00-99}.{00-99}.{0099}
Indicates the release ID of the system

software, that is the identifier of the actual
product release (R041.00.001 for example).
Explanation:
Release Date
E
Engineering Load. When software has
progressed to the point where
components and functions are brought
together in a single testable load (Internal
load only).
F
First Office Application, the software
load is intended for FOA evaluation and
testing and is qualified to carry traffic
under specified conditions or constraints
(Load given to customer during
development that could be changed to an
R load pending customer acceptance).
P
Preliminary, the software load is only
intended for evaluation and testing under
controlled, nontraffic-bearing conditions
development, not meant for deployment
or real traffic).
R
Released, the software load is fully
qualified to carry traffic per applicable
ALU specifications.
The first pair of digits indicates the

major release.
The second pair of digits indicates the

minor release.
The third and last pair of digits indicates

the maintenance release.
Release Date, identifies the date of the

system software release in the format of
YY-MM-DD.
....................................................................................................................................................................................................................................
1830 PSS
5-471
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
Matrix Size
0, 960, 1920, 3840,

UNKNOWN
Indicates the actual supported bandwidth

switching capacity (Gb/s) of the system,
which is autonomously determined by the
switching capacity of the smallest Matrix
Card of the system.
NODETYPE
PSS
Node type, identifies the role of the NE.
USERLABEL
Up to 15 characters
enclosed in double quotes.
Allowed values are
alphanumeric characters
and dashes ("-").
An operator-defined user label. The string is

enclosed in double quotes to support also an
empty string (no character between quotes).
REGION
ANSI, ETSI
The type of NE application:
PROVMODE
AUTOEQ, MANEQ
ANSI the NE operates in SONET

mode.
ETSI the NE operates in SDH mode.

Only editable in EZ setup tool.
The equipment provisioning mode supported

by the NE:
AUTOEQ - Equipment auto-creation

enabled
MANEQ - Equipment auto-creation

disabled
See also System-wide equipment

provisioning mode (p. 5-7).
ALTITUDE
0, 1, 2, 3, 4, 5, 6, 7, 8
The altitude of the NE above sea level. The

values refer to entire kilometers (for
example: 800 m above sea level relates to the
value 0, 1400 m above sea level relates to the
value 1). Locations below sea level are
reflected by the value 0.
....................................................................................................................................................................................................................................
1830 PSS
5-472
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
AINSSTDFLT
AINS
(related to
facilities only)
After auto-creation, the

listed facilities enters the
state OOS,AINS
Automatic IN-Service STate DeFauLT is the

system wide initial value of the AINS state
for auto-created facilities.
Affected facilities are:
NOWAIT
OTU
After auto-creation, the

listed facilities enters the
state IS or depending of
standing conditions the
state OOS.
ODUn
ODUPTF
AUn
STSn
....................................................................................................................................................................................................................................
1830 PSS
5-473
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
OTUDFLTASAP
ASAPDFLT
OTU DeFauLT ASAP is the system wide

initial assigned ASAP profile for
auto-created OTU facilities.
Initial ASAP is determined

based on DFLT parameter
as defined for the ASAPs
of the OTU facilites.
None
Initial ASAP for OTU

facility is determined by
the user label of one of the
five system-defined
ASAPs of type OTU.
SYSDFLT

five system-defined
ASAPs of type OTU.
NotPrimary

five system-defined
ASAPs of type OTU.
FerfAis

five system-defined
ASAPs of type OTU.
All

five system-defined
ASAPs of type OTU.
....................................................................................................................................................................................................................................
1830 PSS
5-474
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
ODUPTFDFLTASA
P
ASAPDFLT
ODUPTF DeFauLT ASAP is the system wide

auto-created ODUPTF facilities.
initial ASAP is determined

of the ODUPTF facilites.
None
Initial ASAP for ODUPTF

five system-defined
ASAPs of type ODUn
(there are no ASAP types
for ODUPTF defined).
SYSDFLT

five system-defined
ASAPs of type ODUn
NotPrimary

five system-defined
ASAPs of type ODUn
FerfAis

five system-defined
ASAPs of type ODUn
All

....................................................................................................................................................................................................................................
five system-defined
1830 PSS
5-475
ASAPs of type ODUn
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
ODUNDFLTASAP
ASAPDFLT
ODUN DeFauLT ASAP is the system wide

auto-created ODUn facilities.

of the ODUn facilites.
None
Initial ASAP for ODUn

five system-defined
ASAPs of type ODUn
SYSDFLT

five system-defined
ASAPs of type ODUn
NotPrimary

five system-defined
ASAPs of type ODUn
FerfAis

five system-defined
ASAPs of type ODUn
All

five system-defined
ASAPs of type ODUn
....................................................................................................................................................................................................................................
1830 PSS
5-476
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
AUNDFLTASAP
ASAPDFLT
AUN DeFauLT ASAP is the system wide

auto-created AUn facilities.

of the AUn facilites.
None
initial ASAP for ODUn

five system-defined
ASAPs of type AUn.
SYSDFLT

five system-defined
ASAPs of type AUn.
NotPrimary

five system-defined
ASAPs of type AUn.
FerfAis

five system-defined
ASAPs of type AUn.
All

five system-defined
ASAPs of type AUn.
....................................................................................................................................................................................................................................
1830 PSS
5-477
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
STSNDFLTASAP
ASAPDFLT
STSN DeFauLT ASAP is the system wide

auto-created STSn facilities.

of the STSn facilites.
None

five system-defined
ASAPs of type STSn.
SYSDFLT

five system-defined
ASAPs of type STSn.
NotPrimary

five system-defined
ASAPs of type STSn.
FerfAis

five system-defined
ASAPs of type STSn.
All

five system-defined
ASAPs of type STSn.
....................................................................................................................................................................................................................................
1830 PSS
5-478
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
AINSTHDFLT
Time in hours and minutes

(HH:MM format)
Indicates the default setting for the automatic

in-service threshold.
(related to
facilities only)
The automatic in-service threshold

determines the time how long a valid signal
must be present on the respective facility
without a failure condition before the system
puts the facility in service.
The threshold is given in the HHH-MM
(hours-minutes) format, where HHH
ranges from 0 to 168, and MM ranges from
0 to 59. The possible overall value range is
from 0 to 168 hours.
Note:
The value 0 must not be used if the AINS
feature is to be applied.
PARTNERNE
{1-99,102-126,128-223} {0-255} - {0-255} {0-255}
The IP Address of the WDM Partner NE. It

defines to which WDM Partner NE the OCS
node belongs to.
Only editable in EZ setup tool.
STATUS
COMPLETE,
IN-PROGRESS
Identifies the status of any system restart

process. It is strictly aligned to the INIT
alarm condition, which means the STATUS
goes to COMPLETE, when the INIT
condition is cleared.
Third Party
Modules
Yes, No
The parameter Third Party Modules) enables

the acceptance of colored, fixed XFPs within
the system which cannot be
auto-provisioned.
If the parameter is set to Yes, the Provisioned
Type of a I/O card can be configured to
USER.
....................................................................................................................................................................................................................................
1830 PSS
5-479
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The Properties - General window, invoked for a shelf, provides the following
information:
Parameter
Values
Description
The primary state of the optical module.
Secondary State
see Primary and

secondary states of system
components (p. 5-541)
Provisioned Type
PSS64
PSS64 Universal shelf
PSS36
PSS64 Universal shelf
Actual Type
PSS64, PSS36
Shelf with a switching capacity of 3.8 Tb/s

(PSS64) or 1.9 Tb/s (PSS36).
Matrix Size
960
Indicates the switching capacity of the shelf

(in Gb/s).
Name
Primary State
1920
The secondary state of the optical module.
3840
Switching
Capacity 1
Describes the Switching Capacity of the

first/upper shelf row in the unit of GBit/s.
The parameter contains three values, which
are ampersand-separated:
Switching
Capacity 2
The 1st integer value represents the Total

Switching Capacity of the Pool.
The 2nd integer value represents the

Used Switching Capacity of the Pool.
The 3rd integer value represents the Free

Describes the Switching Capacity of the

second shelf row (if available) in the unit of
GBit/s



....................................................................................................................................................................................................................................
1830 PSS
5-480
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Description
Describes the SDH/SONET Switching
Capacity of the shelf in the unit of GBit/s
Switching
Capacity STH

Connected TRU



NONE
Indicates the connected
HPCFAP-1-<shelf>-1
HPCFAP High-Power Connection, Fuse

and Alarm Panel in TRU shelf
....................................................................................................................................................................................................................................
1830 PSS
5-481
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The Properties - General window, invoked for a shelf, provides the following
information:
Parameter
Values
Description
Name
TRU-1-128
Primary State
see Primary and

secondary states of system
components (p. 5-541)
The primary service state of an equipment

part.
Provisioned Type
TRU
Top Rack Unit
....................................................................................................................................................................................................................................
1830 PSS
5-482
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The Properties - General window, invoked for an I/O card, provides the following
information:
Parameter
Details
Name
Indicates the access identifier of the I/O card; see Overview of

access identifiers (p. 5-548).
Primary State
Indicates the primary state of the I/O card; see Primary and
secondary states of system components (p. 5-541).
Secondary State
Indicates the secondary state of the I/O card; see Primary and
Provisioned Type
Indicates the type of I/O card which is provisioned for the slot.
Actual Type
Indicates the type of I/O card which is currently present in the slot.
Automatic-In-Service
specifies the automatic in service (AINS) mode of the I/O card.

AINS: Standing conditions are cleared and suppressed as long as

the I/O card is unplugged. Note that there is no autonomous
transition by a timer threshold as applicable for transmission
facilities.
NOWAIT: Standing conditions are raised (and not supressed)

even if the I/O card is unplugged.
Note that the AINS mode cannot be changed anymore once the I/O
card is plugged.
Autoprovisioning
Indicates if autoprovisioning is allowed for the I/O card or not.

ON - autoprovisioning is allowed
OFF - autoprovisioning is not allowed
This read-only parameter serves to prevent the autoprovisioning of an

I/O card (after a restart) in a slot in which it has previously been
logically deleted (deprovisioned).
....................................................................................................................................................................................................................................
1830 PSS
5-483
Issue 1 June 2013

....................................................................................................................................................................................................................................

Types of optical SDH/SONET port facilities
The following types of optical SDH/SONET port facilities can be distinguished:
SDH/SONET synchronous optical interface ports:

STM-16
STM-64
OC-48
OC-192
SDH/SONET facility transparently mapped into an ODU path facility:

STM-1 embedded in ODU0
STM-4 embedded in ODU0
STM-16 transparently mapped into ODU1

OC-3 embedded in ODU0
OC-12 embedded in ODU0

OC-48 transparently mapped into ODU1
General
The following general parameters are available for optical SDH/SONET ports:
Table 5-9
Parameter
General parameters of an optical SDH/SONET port
Details
....................................................................................................................................................................................................................................
1830 PSS
5-484
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-9
(continued)
Parameter
Details
Name
Indicates the access identifier (AID) of the optical SDH/SONET port; see Overview
of access identifiers (p. 5-548).
Examples of possible AIDs for Alcatel-Lucent 1830 PSS-64 are:
STM16-{1-7}-{1-9}-{1-16,33-48}-{1-24}
STM-16 port on a 24 Multirate ANY client port card
STM64-{1-7}-{1-9}-{1-16,33-48}-{1-10}
STM-64 port on a 10 10G ANY client port card
STM16-{1-7}-{1-9}-{2-9,12,13,16-21}-{1-24}
STM-16 port on a 24 Multirate ANY client port card
STM64-{1-7}-{1-9}-{2-9,12,13,16-21}-{1-10}
STM-64 port on a 10 10G ANY client port card
Primary State
Indicates the primary state of the I/O card; see Primary and secondary states of system
components (p. 5-541).
Secondary State
Indicates the secondary state of the I/O card; see Primary and secondary states of
system components (p. 5-541).
Port Type
Indicates the type of port facility, see Types of optical SDH/SONET port facilities
(p. 5-484).
NORMALSO - Normal synchronous optical interface port:
In SDH mode: STM-16, STM-64

In SONET mode: OC-48, OC-192
TRANSTDMOT - SDH/SONET facility transparently mapped into an ODUn (n = 1,
2).
In SDH mode:
In SONET mode:
....................................................................................................................................................................................................................................
1830 PSS
5-485
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-9
Parameter
Details
Manager Access
Control
Indicates which manager controls the port.
(continued)
Possible settings are:
CP - Port is under the control of the control plane (GMRE).
MNGPLN - Port is under the control of the management plane, that is under the
control of a management system.
CP&MNGPLN - Port control is shared between the control plane and the
management plane.
[not specified] - Port control is not yet assigned, that is the port is neither
controlled by CP nor MNGPLN.
Automatic In-Service (AINS) parameters
The following AINS parameters are available for optical SDH/SONET ports:
Table 5-10
Parameter
Details
Automatic
In-Service
Threshold
Specifies how long an input signal must be present on the facility without a failure
condition before the system automatically transitions the facility into the In-Service
state.
The threshold is given in the HHH-MM (hours-minutes) format, where HHH
ranges from 0 to 168, and MM ranges from 0 to 59. The overall value range is from
0 to 168 hours. The default value is determined by the AINSTHDFLT; see General
properties of the system as a whole (p. 5-470).
Automatic
In-Service Timer
Specifies how much time is currently remaining on the AINS timer before the facility
is placed into the In-Service state. The timer value, given in the HH-MM
(hours-minutes) format, is truncated to the next highest minute - for example, a timer
value of 1 minute and 5 seconds is displayed as 00-02.
Note that the current value of the AINS timer is not persistent through an FLC switch
or cold restart. All running AINS timers will be reset and restarted following these
events.
....................................................................................................................................................................................................................................
1830 PSS
5-486
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-10
(continued)
Parameter
Details
Automatic
In-Service Criteria
Determines which fault criteria must be present to trigger the state transition to the
In-Service state.
(valid for SDH

facilities only!)
Port Mode (valid for
SDH facilities only!)
NOLOS - the clear event of a loss of signal (LOS) condition triggers the state
transition.
NOSF - the clear event of the last present signal fail (SF) condition triggers the state
transition.
Port monitoring mode, determines whether the port is monitored for defects or not, and
whether detected alarm conditions are reported or not.
AUTO (Automatic) - Port monitoring is disabled. However, when an event as

defined by the Automatic In-Service Criteria parameter is detected, and when the
AINS timer has expired, then the port monitoring mode is automatically switched
to Monitored (MON).
NMON (Not monitored) - The incoming port signal is monitored for defects but the
conditions defined by the Primary State Correlation parameter are not reported.
MON (Monitored) - The incoming port signal is monitored for defects, and
conditions are reported according to the ASAP associated to the port.

Determines the set of conditions which are correlated with the port monitoring mode.
Primary State
Correlation (valid
for SDH facilities

only!)
LOS - Loss of signal (LOS) conditions are not reported when the port monitoring
mode is NMON (Not monitored).
ALL - When the port monitoring mode is NMON (Not monitored) then no alarm
conditions are reported.
Trail Trace Messaging
The following trace messaging parameters are available for optical SDH/SONET ports:
Table 5-11
Parameter
Trace Messaging parameters of an optical SDH/SONET port
Details
....................................................................................................................................................................................................................................
1830 PSS
5-487
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-11
Trace Messaging parameters of an optical SDH/SONET port

(continued)
Parameter
Details
Expected
Section Trace
Msg. Format
Determines the format of the expected section trace identifier (J0 byte).
Expected
Section Trace
Message
Trace
Monitoring On
The following formats are supported:
1 specific repeating byte - (Format: X{0-9,A-F}[2])
16 byte specific string - Hex (Format: X{{0-7}{0-9,A-F}[15])
16 byte specific string - Text (Format:15 ASCII characters)
Indicates the value of the expected section trace message.

For the 1 specific repeating byte format:

X{0-9,A-F}[2]
A single byte in hexadecimal notation (range from 0x00 to 0xFF).
Overview of SDH performance parameters (p. 16-13)
For the 16 byte specific string format:

X{{0-7}{0-9,A-F}}[15]
Hex string: The string consists of 31 ASCII characters (X followed by 30
hexadecimal characters), which encode the 15 byte trail trace identifier (TTI) into
30 half-byte characters in hexadecimal format. The string starts with the first byte
after the CRC header byte (the CRC header byte is generated by the NE). The 30
half-byte characters need to be entered as 15 pairs in the value range from 0x00 to
0x7F.
15 ASCII characters
Quoted text string: This consists of up to 15 ASCII characters enclosed with double
quotes. The string will be padded with ASCII NULL characters if the length is less
than 15 characters. The CRC header byte is generated by the NE.
Indicates whether the receive signal is monitored for the detection of a trace identifier
mismatch (TIM).
Trace Mismatch
Consequent
Action
Yes - TIM detection is enabled.
No - TIM detection is disabled.
Determines if consequent actions (insertion of an all-ones signal, and SSF signaling towards
the client layer) are to be performed if a trace identifier mismatch (TIM) is detected.
The only possible value for this parameter is Yes, that is consequent actions are enabled by
default. However, the setting of this parameter is only relevant if TIM detection is enabled
(Trace Monitoring On).
....................................................................................................................................................................................................................................
1830 PSS
5-488
Issue 1 June 2013

....................................................................................................................................................................................................................................

Types of OTU port facilities
The following types of OTU port facilities can be distinguished:
OTU2
OTU2E
OTU3
OTU3E2
OTU4
General
The following general parameters are available for OTU port facilities:
Table 5-12
Parameter
Details
....................................................................................................................................................................................................................................
1830 PSS
5-489
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-12
(continued)
Parameter
Details
Name
Indicates the access identifier (AID) of the OTU port facility; see Overview of access
OTU-{1}-{1-31}-{1-16,33-48}-{1,2}
OTU3 on a 2 40G ANY client port card
OTU-{1}-{1-31}-{33-39,41-47}-{1}
OTU3E2 on a 1 43G Switchponder 43SCUP
OTU-{1}-{1-9}-{1-16,33-48}-{1-10}
OTU2E on a 10 10G ANY client port card
OTU-{1}-{1-31}-{33-48}-{1-4}
OTU2E on a 4 11G Switchponder 11QCUP
OTU-{1}-{1-31}-{1-16,33-48}-{1-10}
OTU-{1}-{1-31}-{33-48}-{1-4}
OTU2 on a 4 11G Switchponder 11QCUP
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1,2}
OTU-{1}-{1-31}-{2-8,12,16-20}-{1}
OTU3E2 on a 1 43G Switchponder 43SCUP
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
OTU2E on a 10 10G ANY client port card
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1}
OTU4 on a 130SCUP)
Primary State
Indicates the primary state of the OTU port facility; see Primary and secondary states
of system components (p. 5-541).
Secondary State
Indicates the secondary state of the OTU port facility; see Primary and secondary
states of system components (p. 5-541).
....................................................................................................................................................................................................................................
1830 PSS
5-490
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-12
Parameter
Details
Manager Access
Control
Indicates which manager controls the OTU port facility.
(continued)
CP - Port is under the control of the control plane (GMRE).
MNGPLN - Port is under the control of the management plane, that is under the
control of a management system.
CP&MNGPLN - Port control is shared between the control plane and the
management plane.
[not specified] - Port control is not yet assigned, that is the port is neither
controlled by control plane nor management plane.
Automatic In-Service (AINS) parameters
The following AINS parameters are available for OTU port facilities:
Table 5-13
AINS parameters of an OTU port facility
Parameter
Details
Automatic
In-Service
Threshold
condition before the system automatically transitions the facility into the In-Service
state.
The threshold is given in the HHH-MM (hours-minutes) format, where HHH
ranges from 0 to 168, and MM ranges from 0 to 59. The overall value range is from
0 to 168 hours. The default value is determined by the AINSTHDFLT; see General
properties of the system as a whole (p. 5-470).
Automatic
In-Service Timer
Specifies how much time is currently remaining on the AINS timer before the facility
is placed into the In-Service state. The timer value, given in the HH-MM
(hours-minutes) format, is truncated to the next highest minute - for example, a timer
value of 1 minute and 5 seconds is displayed as 00-02.
Note that the current value of the AINS timer is not persistent through an FLC switch
or cold restart. All running AINS timers will be reset and restarted following these
events.
....................................................................................................................................................................................................................................
1830 PSS
5-491
Issue 1 June 2013

....................................................................................................................................................................................................................................
Trace Messaging
The following trace messaging parameters are available for OTU port facilities:
Table 5-14
Parameter
Details
Expected Incoming
Destination Access
Point Identifier
The expected Destination Access Point Identifier (DAPI) part of the Trail Trace
Identifier (TTI) on the OTUk layer.
Expected Incoming
Source Access Point
Identifier
Hexadecimal format
TTI values are displayed as a sequence of hexadecimal values. The TTI consists of
an X followed by 15 hexadecimal values, each represented by 2 ASCII
characters.
Text format
TTI values are displayed as a text string consisting of 15 ASCII characters. ASCII
NULL characters (00 hex) are represented by . character. If the TTI consists of
ASCII NULL characters only, then 15 . characters will be displayed. If the TTI
contains unsupported characters, then a question mark (? character) will be
displayed for those characters.
The expected Source Access Point Identifier (SAPI) part of the Trail Trace Identifier
(TTI) on the OTUk layer.
Hexadecimal format
characters.
Text format
....................................................................................................................................................................................................................................
1830 PSS
5-492
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-14
(continued)
Parameter
Details
Transmit
Destination Access
Point Identifier
The transmitted Destination Access Point Identifier (DAPI) part of the Trail Trace
Identifier (TTI) on the OTUk layer.
Transmit Operator
Specific Field
hexadecimal format
characters.
Text format
The Transmit Operator Specific Identifier part of the Trail Trace Identifier (TTI) on the
OTUk layer.
Transmit Source
Access Point
Identifier
hexadecimal format
characters.
Text format
The transmitted Source Access Point Identifier (SAPI) part of the Trail Trace Identifier
(TTI) on the OTUk layer.
hexadecimal format
characters.
Text format
....................................................................................................................................................................................................................................
1830 PSS
5-493
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-14
(continued)
Parameter
Details
Trail Trace
Identifier
Monitoring
Indicates whether the receive signal is monitored for the detection of a trace identifier
mismatch (TIM). If monitoing is enabled, then this parameter further determines if
only DAPI, only SAPI, or both SAPI and DAPI are monitored for the comparison
between the incoming and the expected TTI.
N - TIM detection is disabled.
DAPI - TIM detection is enabled and only DAPI is used for that purpose.
SAPI - TIM detection is enabled and only SAPI is used for that purpose.
SAPIDAPI - TIM detection is enabled, and both DAPI and SAPI are used for that
purpose.
Trace Mismatch
Consequent Action
Determines if consequent actions are to be performed or not if a trace identifier

mismatch (TIM) is detected.
ENABLE - consequent actions are enabled. AIS will be inserted downstream if a
trace identifier mismatch (TIM) is detected.
DISABLE - consequent actions are disabled. No consequent actions will be triggered

if a trace identifier mismatch (TIM) is detected but the received signal will be
passed.
Ingress Error Monitoring
The following ingress error monitoring parameters are available for OTU port facilities:
Table 5-15
Parameter
Details
Burst Interval
Specifies the number of consecutive degraded seconds (see Burst Threshold) to be

detected before declaring a signal degrade defect.
2 to 10 (seconds), default setting: 7
....................................................................................................................................................................................................................................
1830 PSS
5-494
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-15

(continued)
Parameter
Details
Burst Threshold
Indicates the number of errored blocks that must be exceeded before a second is
declared a degraded second.
Forward Error
Correction Enable
Mode
For OTU2 port facilities: 1 .. 82026 in steps of 1, default setting: 4000
For OTU2E port facilities: 1 .. 82300 in steps of 1, default setting: 4000
For OTU3E2 port facilities: 1 .. 341478 in steps of 1, default setting: 16000
Indicates if Forward Error Correction (FEC) is used or not, and the directionality of the
FEC, if used.
NO FEC
Enable FEC Insertion only
Enable FEC Evaluation only
Enable both FEC Evaluation and Insertion
....................................................................................................................................................................................................................................
1830 PSS
5-495
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-15

(continued)
Parameter
Details
Forward Error
Correction Type
Indicates the type of Forward Error Correction (FEC) used.

EFEC Enhanced FEC (proprietary) for 10G interfaces (= AMCCs enhanced FEC)
RSFEC Reed-Solomon FEC as defined in G.709
SDFEC Soft Decision FEC
AFEC Alcatel-Lucent enhanced FEC Compliant with G.975.1 for 40G interfaces (=
ALUs enhanced FEC for 40G and higher)
EFEC2 Enhanced FEC Compliant with G.975.1 for 10G interfaces (enhanced FEC
for 10G)
Note:
Prior to R5.0 the following definition was used:
EFEC Enhanced FEC Compliant with G.975.1 (= ALU's enhanced FEC for 10G)
which in case of a In-Service-Upgrade (ISU) to R5.0 was migrated to the new R5.0
EFEC2 definition.
Values valid for:
OTU4: AFEC, SDFEC
OTU3E2: AFEC
OTU3: RSFEC
OTU2E: EFEC, EFEC2, RSFEC

Exception: Use RSFEC or EFEC instead of EFEC2 for OTU2E on a 11QCUP or a
10XANY10G.
OTU2: EFEC, EFEC2, RSFEC

Exception: Use RSFEC or EFEC instead of EFEC2 for OTU2 on a 11QCUP or a
10XANY10G.
....................................................................................................................................................................................................................................
1830 PSS
5-496
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The Properties - General window, invoked for an optical module, provides the following
information:
Note: Fixed ports are handled as "SFP/XFP modules" which are already plugged in,
when the card is plugged in the system.
Fixed Ports are available on the following IO-Cards:
2XANY40G: 2 x 40G ANY IO-Card
11QCUP: 4 x 11G Switchponder

11QCUPC: 4 x 11G has SFPs/XFPs, but handled as NO SFPs/XFPs
43SCUP: 1 x 43G Switchponder
130SCUP 1 x 100G Coherent Switchponder/Uplink card

112CFPTB 1x100G Switchponder Test Board with CFP, but handled as NO
SFPs/XFPs
SFC8 CWDM filter module
Parameter
Details
Name
Indicates the access identifier of the optical module; see Overview

of access identifiers (p. 5-548).
Primary State
Indicates the primary state of the optical module; see Primary and
Secondary State
Indicates the secondary state of the optical module; see Primary and
....................................................................................................................................................................................................................................
1830 PSS
5-497
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Provisioned Type
Indicates the type of optical module which is provisioned for the

OM socket.
The following types of SFP/XFP modules are supported:
SR12G7TU (S2G7D2I )
IR12G7TU (S2G7D15E )
LR12G7TU (S2G7D40E )
LR22G7TU (S2G7D80E )
IR12G7AU (S2G7M15I )
1000BSXU (S1GE05I )
1000BLXU (S1GE10I )
1000BZXU (S1GE80I )
SR111G1AU (X11M10I )
IR211G1AU (X11M40I )
LR211G1AU (X11M80E )
LRT11G1TU (X11MDTNC )
SR<xx>W11G1TUC (<xx>={47,49,51,53,55,57,59,61};
X11MC<xx>SC)
SR<xx>W11G1TUI (<xx>={47,49,51,53,55}; X11MC<xx>SI)
LR<xx>W11G1TUC (<xx>={47,49,51,53,55,57,59,61};
X11MC<xx>LC)
LR<xx>W11G1TUI (<xx>={47,49,51,53,55,57,59,61};
X11MC<xx>LI;)
LR<xx>DW11G1TUC; (<xx>={17,18,...,60} X11MD<xx>LC;)

e.g. <xx>=53 for a wavelength=1531nm
SR10G155TU (S155S15I)
SL10G155TU (S155S40I)
SL20G155TU (S155S80I)
SR10G622TU (S622S15I)
SL10G622TU (S622S40I)
SL20G622TU (S622S80I)
USER (third party interface module type SFP/XFP
....................................................................................................................................................................................................................................
1830 PSS
5-498
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Actual Type
Indicates the type of optical module which is actually present in the

OM socket.
Automatic-In-Service
Any type of SFP/XFP module as listed under Provisioned Type.
Unknown - the type of optical module cannot be determined
Unplugged - the type of optical module cannot be determined
specifies the automatic in service (AINS) mode of the optical

module.
AINS: Standing conditions are cleared and suppressed as long as

the optical module is unplugged. Note that there is no
autonomous transition by a timer threshold as applicable for
transmission facilities.
NOWAIT: Standing conditions are raised (and not supressed)

even if the optical module is unplugged.
Note that the AINS mode cannot be changed anymore once the
optical module is plugged.
Autoprovisioning
Indicates if autoprovisioning is allowed for the optical module or

not.
ON - autoprovisioning is allowed
OFF - autoprovisioning is not allowed
This read-only parameter serves to prevent the autoprovisioning of

an optical module (after a restart) in an OM socket in which it has
previously been logically deleted (deprovisioned).
....................................................................................................................................................................................................................................
1830 PSS
5-499
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Client-Select
Indicates the facility type supported by the optical module.

Possible values are (see also Port groups and port group modes
(p. 5-9)):
STM64T
STM64 over OTN transparent (STM64 mapped transparently to
ODU2 terminated)
OC192T
OC192 over OTN transparent (OC192 mapped transparently to
ODU2 terminated)
STM16T
ODU1 terminated)
OC48T
ODU1 terminated)
STM4T
ODU0 terminated)
OC12T
ODU0 terminated)
STM1T
ODU0 terminated)
OC3T
ODU0 terminated)
STM64
STM64 terminated
OC192
OC192 terminated
STM16
STM16 terminated
OC48
OC48 terminated
OTU2
OTU2 terminated
OTU2E
OTU2E terminated
OTU3
OTU3 terminated
OTU3E2
....................................................................................................................................................................................................................................
OTU3E2 terminated
5-500
1830 PSS
Issue 1 June 2013
OTU4
OTU4 terminated
GBEODU0
GBE over OTN (GBE mapped to ODU0 terminated)

....................................................................................................................................................................................................................................

Overview
The Properties - General window, invoked for a GBE/GBE10 port, is used to display
parameters of the GBE/GBE10 port.
Property windows typically use mutable tables, which contain editable or non-editable
text fields, spinners, or combo boxes.
Description
The Properties - General window, invoked for a GBE/GBE10 port, provides the
following information:
Parameter
Values
Details
Command Mode
Forced
Command Execution Mode
Normal
Name
Alcatel-Lucent
1830 PSS-64:
GBE port on a 24XANYMR module

(GBE10 port on a 10XANY10G module)
GBE-{1-7}-{1-9}-{1-16,
33-48}-{1-24}
GBE10-{1-7}-{1-9}-{1-16,
33-48}-{1-10}
Alcatel-Lucent
1830 PSS-36:
GBE-{1-7}-{1-9}-{2-9,12,
13,16-21}-{1-24}
GBE10-{1-7}-{1-9}-{2-9,
12,13,16-21}-{1-10}
Primary State
Indicates the primary state of the GBE/GBE10 port; see Primary and
Secondary State
Indicates the secondary state of the GBE/GBE10 port ; see Primary and
....................................................................................................................................................................................................................................
1830 PSS
5-501
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
CSF Laser
C(onsequent)
A(ction)
This parameter defines the Consequent

Action in case of CSF for port-port
applications
No Action
No action is to be
performed on the
facility in case of CSF
Laser Shutdown
Laser-shutdown is to
be performed on the
facility in case of CSF
Unidirectional
connections
For unidirectional
connections the following
has to be set:
GBE10 port1 (source):

No Action
GBE10 port2 (sink):

Laser Shutdown
SSF Laser
C(onsequent)
A(ction)
No Action
No action is to be
performed on the
facility in case of SSF
This parameter defines the Consequent

Action in case of SSF for port-port
applications
Laser Shutdown
Laser-shutdown is to
be performed on the
facility in case of SSF
Unidirectional
connections
For unidirectional
connections the following
has to be set:
GBE10 port1 (source):

No Action
GBE10 port2 (sink):

No Action
....................................................................................................................................................................................................................................
1830 PSS
5-502
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
Flow Control
Mode
Flow control mode selection
NO-PAUSE
Pause frames will not

be transmitted nor
processed. (Flow
control disabled). This
value is only
applicable for the
following PORTTYPE
value: GFPFODU
ASYMMETRIC-PAUSE
Asymmetric pause
toward link partner.
The transmitter can
transmit pause frames
but will not process
received pause frames
(Factory Default)This
value is only
applicable for the
following PORTTYPE
value: GFPFODU
ASYMMETRIC-PAUSEOPENLOOP
Asymmetric pause
toward link partner
with buffer. In this
function, pause frames
are transmitted at
regular intervals, as
against sending pause
frames when its
receiver buffer reaches
certain level as is done
in Asymmetrical Pause
Function. This value is
only applicable for the
following PORTTYPE
value: GFPFODU
TRANSP
Pause frames are

passed through
transparently. This
value is only
applicable for the
following PORTTYPE
value: CBRODU
PPOSODU
....................................................................................................................................................................................................................................
1830 PSS
Issue 1 June 2013
5-503

....................................................................................................................................................................................................................................
Parameter
Values
Details
Port Type
CBRODU
Ethernet port client layer of a NE local

Ethernet Port;
Ethernet is mapped as
CBR into ODUn (i.e.
PLDTYPE of
corresponding ODUPTF is
equal to value
'1000BASEX' in case of
GBE or 'BSCBR'in case of
GBE10)
Ethernet port server layer used as for the

transport. The following values are
supported: ')
GFPFODU
Ethernet is mapped via

GFP-F into ODUn (i.e.
PLDTYPE of
equal to value 'GFP')
PPOSODU
Ethernet is mapped via

PPOS (i.e. extended
payload) into ODUn (i.e.
PLDTYPE of
equal to value AMCC,
CAMCC or 'OLDAMCC
Capabilities
The following values are

supported:
CBR
Mapping of GBEn as
CBR
Specifies a list of capabilities supported by

GBEn port facility If more than one
capability is supported, the different
capabilities will be separated by '&'.
GFPF
Mapping of GBEn via

GFP-F
PPOS
Mapping of GBEn as
extended payload
(AMCC mapping)
PPOSC
Mapping of GBEn as
extended payload
(CAMCC mapping)
....................................................................................................................................................................................................................................
1830 PSS
5-504
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
Associated TID
Alcatel-Lucent
1830 PSS-64:
Access identifier of GBE facility.
GBE-{1-7}-{1-9}-{1-16,
33-48}-{1-24}
GBE10-{1-7}-{1-9}-{1-16,
33-48}-{1-10}
Alcatel-Lucent
1830 PSS-36:
GBE-{1-7}-{1-9}-{2-9,12,
13,16-21}-{1-24}
GBE10-{1-7}-{1-9}-{2-9,
12,13,16-21}-{1-10}
Associated AID
Alcatel-Lucent
1830 PSS-64
GBE-{1-7}-{1-9}-{1-16,
33-48}-{1-24}
GBE10-{1-7}-{1-9}-{1-16,
33-48}-{1-10}
Alcatel-Lucent
1830 PSS-36:
GBE-{1-7}-{1-9}-{2-9,12,
13,16-21}-{1-24}
GBE10-{1-7}-{1-9}-{2-9,
12,13,16-21}-{1-10}
NE Native AID
Alcatel-Lucent
1830 PSS-64
GBE-{1-7}-{1-9}-{1-16,
33-48}-{1-24}
GBE10-{1-7}-{1-9}-{1-16,
33-48}-{1-10}
Alcatel-Lucent
1830 PSS-36:
GBE-{1-7}-{1-9}-{2-9,12,
13,16-21}-{1-24}
GBE10-{1-7}-{1-9}-{2-9,
12,13,16-21}-{1-10}
....................................................................................................................................................................................................................................
1830 PSS
5-505
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
ALMPROF (visible
via Properties
Alarm Severity View)
1-40 alphanumeric
characters (plus '-')
assigned as the userlabel
for the desired profile.
The Alarm Severity Assignment profile

(ASAP) name to use with this facility. On
facility creation, the currently assigned
default profile for this rate is used as default.
1-40 alphanumeric characters (plus '-')
assigned as the userlabel for the desired
profile
Factory Default is
userlabel for ASAP#1 for
this entity type
TCAPROF
(visible via the

Performance
Monitoring
View Thresholds
menu)
<user-label>1-40
alphanumeric characters
(plus '-') assigned as the
userlabel for the desired
profile.
The PM Threshold Crossing Alert (TCA)

profile name to use with this facility. On
facility creation, the currently assigned
default profile for this rate is used as default.
Factory Default is
userlabel for THP#1 for
this entity type
Parameter visible when selecting AINS in the Column Groups box.

Automatic
In-Service
Threshold
[{0-167}-{0-59}], [168-0]
Automatic In-Service Threshold, specifies

how long an input signalmust be present on
the facility without a failure condition before
the system transitions the facility into the
In-Service state. Time, specifies the duration
of an alarm-free signal, in HHH-MM format,
where value HHH indicates the time duration
in hours and value MM indicates the time
duration in minutes. Note that the current
value of the AINSTIMER is not persistent
through an FLC switch or cold restart. All in
process AINSTIMERs will be reset and
counts restarted following these events.
Automatic
In-Service Timer
Time, in HHH-MM format
Automatic In-Service Timer value, specifies

how much time is currently remaining on the
AINS timer before the facility is placed in
service. The timer value is truncated to the
next highest minute - for example, a timer
value of 1 minute 5 seconds is displayed as
00-02. Note that the current value of the
AINSTIMER is not persistent through an
FLC switch or cold restart. All in process
AINSTIMERs will be reset and counts
restarted following these events.
Velues:
[{0-167}-{0-59}],
[168-0] (
....................................................................................................................................................................................................................................
1830 PSS
5-506
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
Automatic
In-Service
Criteria
NOLOS
the clear event for LOS
triggers the state
transition
Determines the fault criteria to leave the

PMODE/SST state value AUTO/AINS.
NOSF
the clear event for last
present SF condition
triggers the state
transition
Port Mode
Primary State
Correlation
AUTO, NMON, MON
LOS, ALL
Port Mode, determines if the conditions for

the facility are reported or not. The criteria
for leaving the AUTO state autonomously
depends on the current value of the
parameter AINSCRIT. In addition the set of
conditions which are considered for the
alarm correlation with PMODE depends on
the current value of the parameter
PSTCORR.
AUTO
the conditions as defined by PSTCORR
are not reported and transition to.
MON
if condition as defined by AINSCRIT is
cleared and AINSTIMER has expired.
NMON
the conditions as defined by PSTCORR
are not reported.
Determines the set of conditions which are

correlated with PMODE/PST state. LOS
only LOS condition is correlated with
PMODE/PST state w.r.t. reporting ALL all
non off-normal conditions reported by the
port facility are correlated with PMODE/PST
state w.r.t. reporting.
Parameter visible when selecting Misc. in the Column Groups box.
....................................................................................................................................................................................................................................
1830 PSS
5-507
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Values
Details
Manager Access
Control
Access Control Parameter, list of managers

currently in control of this resource.
<null>
The entity identified

by AID is free.
CP
Tthe entity identified

by AID is owned by
CP.
MNGPLN,
The entity identified

by AID is owned by
MNGPLN.
Negotiation Type
The following values are

supported with
applicability restriction for
the different GBEn port
type
Negotiation mode with link partner.
TRANSP
Auto-negotiation
frames are passed
through transparently.
This value is only
applicable for the
following PORTTYPE
value: CBRODU
Restriction:
The parameter is
applicable for the
following GBE
command modifier
values: GBE
....................................................................................................................................................................................................................................
1830 PSS
5-508
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The Properties - General window, invoked for a ODU path termination facilty,is used to
display and modify parameter of the ODU path termination facilty.
Property windows typically use mutable tables, which contain editable or non-editable
text fields, spinners, or combo boxes.
Description
The Properties - General window, invoked for a ODU path termination facilty, provides
the following information:
Parameter
Details
Command Mode

NE Native AID
Forced
Normal
The access Identifier of the ODU PTF.

ODU4-{1-7}-{shelf}-{slot}-{ID}
ODU4 Termination on virtual and preset plane
ODU3E2-{1-7}-{shelf}-{slot}-{ID}
ODU3E2 Termination on virtual and preset plane
ODU3-{1-7}-{shelf}-{slot}-{ID}
ODU2E-{1-7}-{shelf}-{slot}-{1-10}
Transparent mapping ODU2E Termination on a 10xANY10G
ODU2-{1-7}-{1-9}-72-{101-4802}
ODU2-{1-7}-{1-9}-{1-16,33-48}-{1-10}
Transparent mapping ODU2 / Termination on a 10xANY10G
ODU1-{1-7}-{1-9}-{1-16,33-48}-{1-24}
Transparent mapping ODU1 / Termination on a 24XANYMR
ODU0-{1-7}-{1-9}-{1-16,33-48}-{1-24}
Transparent mapping ODU0 / Termination on a 24XANYMR
....................................................................................................................................................................................................................................
1830 PSS
5-509
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Primary State
Specifies the primary state of the addressed ODU PTF.

IS-NR
In Service - Normal
IS-ANR
In Service - Abnormal
OOS-AU
Out Of Service - AUtonomous
OOS-AUMA
Out Of Service - AUtonomous and MAnagement
OOS-MA
Out Of Service - MAnagement
....................................................................................................................................................................................................................................
1830 PSS
5-510
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Secondary State
Secondary state, specifies the secondary state of the addressed ODU PTF.
AINS
Automatic In-Service
BUSY
Busy
CP
Control Plane
CPMP
Control Plane and Management Plane
CPMPE
Control Plane and Management Plane Enhanced
DSBLD
Disabled.
FAF
Facility Failure
MDLT
Manual Delete
MP
Management Plane
NOIMP
Not Implemented in Hardware
PMD
Performance Monitoring Disabled
PSI
Protection Switching Inhibited
SDEE
Supported Entity Exists
STBYH
Standby-Hot, when a standby entity has no switch request
STBYS
Standby-Switched - When a standby entity is has a switch request or

has switched
TRM
Supported facilities are connected
WRK
Working
UAS
Unassigned
....................................................................................................................................................................................................................................
1830 PSS
5-511
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Payload Type
Indicates the client signal being carried by the ODUPTF.

The mapping between the parameter value to the Hex value that is used in
the PT byte is as follows:
1000BASEX
GBE into ODU0 mapping (timing transparent transcoding (TTT))
ASCBR
Asynchronous CBR mapping, 10G WAN PHY/OC192/STM64

10.709Gb/s
BSCBR
Bit synchronous CBR mapping

10G WAN PHY/OC192/STM64 10.709Gb/s; 10GBE Mapped into
ODU2E
ODUM (not appicable for ODU1):
ODUk multiplexed structure with 2.5G Tributary Slots for OTU2 and
above rates.
ODUMPT21
AMCC
AMCC mapping used for transparent GBE10 as defined in G.709
CAMCC
AMCC mapping used for transparent GBE10 for interworking with

Cienna equipment.
OLDAMCC
AMCC mapping used for GBE10 as defined in G.sup43; for backward

compatibility.
GFP
GFP mapping used for transparent transport of GBE10

Type of client
signal fail format
Indicates the kind of format of signal carrying client signal fail indication.
The signal is generated by the addressed ODU to the far end.
(valid for
GBE10ODU2
facilities only!)
LCS
Loss of Client signal. GFP frame reporting CSF indication has UPI
equal to 1, that means Loss of Client signal, this value is not
recommended by Standard ITU-T G.7041.
LCCS
Loss of client character Synchronization. GFP frame reporting CSF

indication has UPI equal to 2, that means Loss of client character
Synchronization, this value is recommended by Standard ITU-T
G.7041.
....................................................................................................................................................................................................................................
1830 PSS
5-512
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Client Signal Fail

indication
Propagation of Client Signal Fail indication. Defines modalities of the

propagation of Client Signal Fail indication, if it has to be propagated
forward, backward, both or neither of the previous ones. The signal is
generated by the addressed ODU to the far end.
NONE
No CSF Propagation. For the GFP-F mapped signal, neither Failure on

the interface at client side nor GFP Server Signal Fail alarm detected by
the addressed ODU causes GFP CSF Propagation.
This value is valid for the following signals:
GBE10 transparently transported via GFP-F by ODU2
FWD
Forward CSF Propagation. Failure on the interface at client side has to

be propagated forward by the addressed ODU as Client Signal Fail
indication to the far end.
This value is valid for the following signals with indication of the type
of CSF sent out:
GBE10 transparently transported via AMCC, OLDAMCC and
CAMCC payload mapping by ODU2 - GFP CSF
GBE10 transparently transported via GFP-F by ODU2 - GFP CSF
GBE10 transparently transported by ODU2E - ODU CSF
GBE transparently transported by ODU0 - ODU CSF
OCn/STMn transparently transported by ODU - ODU CSF
FWDBWD
Forward and Backward CSF Propagation. Failure on the interface at

client side has to be propagated forward by the addressed ODU as
Client Signal Fail indication to the far end. GFP Server Signal Fail
alarm detected by the addressed ODU has to be propagated in the
backward direction as the Client Signal Fail to the far end
This value is valid for the following signals:
GBE10 transparently transported via GFP-F by ODU2
Unidirectional connections
For unidirectional connections the following has to be set:
GBE10 port1 (source): FWD
GBE10 port2 (sink): NONE
AINS parameters visible when selecting AINS in the Column Groups box.
Automatic
In-Service
Threshold
Specifies how long an input signal must be present on the facility without a
failure condition before the system transitions the facility into the
In-Service state. [{0-167}-{0-59}], [168-0] Time, specifies the duration of
an alarm free signal, in HH-MM format, where value HH indicates the time
duration in hours and value MM indicates the time duration in minutes.
....................................................................................................................................................................................................................................
1830 PSS
5-513
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Automatic
In-Service Timer
Specifies how much time is currently remaining on the AINS timer before
the facility is placed in service.
Trace parameters visible when selecting Trail Trace Identifier (TTI) in the Column Groups box.
Expected
incoming Source
Access point
Identifier
Expected incoming Source Access Point Identifier. Displayed either as

HEX text or Quoted ASCII string depending on the value of the TTIFMT.
Hex textI
The string consists of 31 ASCII characters ("X" followed by 30

hexadecimal characters), which encode the 15 byte TTI into 30 half-byte
characters in hexadecimal format. The string starts after the CRC header
byte (the header byte is generated by the NE and not returned in the
response).
Quoted ASCII
This consists of 15 ASCII characters. If the trace to be displayed is all

ASCII NULLs (00 Hex), then 15 "." characters will be displayed. If the it
contains ASCII characters other than those listed here, then the "?"
character will be displayed for those characters. The string starts with the
first character after the CRC byte.
Expected
incoming
Destination
Access point
Identifier
Expected incoming Destination Access Point Identifier. Displayed either as

HEX text or Quoted ASCII string depending on the value of the TTIFMT.
Hex textI

response).
Quoted ASCII

....................................................................................................................................................................................................................................
1830 PSS
5-514
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Trail Trace
Identiifer
Monitoring
Determines if the incoming/received signal is monitored for the detection

of Trail Trace Identifier Mismatch defect. If monitoring is enabled, further
determines if only DAPI, only SAPI or both SAPI/DAPI are monitored for
TIM defect generation.
TIM detection monitoring is disabled.
DAPI
TIM detection is enabled and only DAPI is used for the purpose.
SAPI
TIM detection is enabled and only SAPI is used for the purpose.
SAPIDAPI
TIM detection is enabled and both DAPI and SAPI are used for the
purpose.
Trace Mismatch
Consequent
Action
This parameter determines whether an ODUPTF will take a Consequent

Action by sending AIS downstream or pass the received signal upon
detection of a Trail Trace Mismatch at its input.
DISABLE
disable TIMM defect detection
ENABLE
enable TIMM defect detection

Transmit
Destination
Access point
Identifier
Displayed either as HEX text or Quoted ASCII string depending on the

value of the TTIFMT.
Hex textI

response).
Quoted ASCII

....................................................................................................................................................................................................................................
1830 PSS
5-515
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Transmit
Operator
Specific Field

Hex textI

response).
Quoted ASCII

Transmit Source
Access point
Identifier

Hex textI

response).
Quoted ASCII

Parameters visible when selecting Degraded Supervision in the Column Groups box.
Burst Interval
Specifies the number of consecutive bad seconds (see parameter Burst

Threshold) to be detected before declaring a signal degrade defect
(SDBER) on the OTU layer. The defect is cleared if Burst Interval
consecutive good seconds (see parameter Burst Threshold) are detected.
2 10
....................................................................................................................................................................................................................................
1830 PSS
5-516
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Burst Threshold
Specifies a number of errored blocks on the multiplex section layer. A

second is declared as good if the number of detected errored blocks within
one second is less than BRSTTH; otherwise the second is declared as bad
second.
1 329492
Parameter visible when selecting Misc. in the Column Groups box.
....................................................................................................................................................................................................................................
1830 PSS
5-517
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Associated TCMs
List of the AIDs of the Tandem Connection Monitoring facilities associated

with the addressed ODUPTF.
ODU4TCN-1-<shelf>-<slot>-<ID>-{1- 6}-AM
TCM NIM at ODU4 Termination on virtual or preset plane
ODU4TCT-1-<shelf>-<slot>-<ID>-{1- 6}-AM
TCM Termination at ODU4 Termination on virtual or preset plane
ODU3E2TCN-1-<shelf>-<slot>-<ID>-{1- 6}-AM
TCM NIM at ODU3E2 Termination on virtual or preset plane
ODU3E2TCT-1-<shelf>-<slot>-<ID>-{1- 6}-AM
TCM Termination at ODU3E2 Termination on virtual or preset plane
ODU3TCN-1-<shelf>-<slot>-<ID>-{1-6}- AM
ODU3TCT-1-<shelf>-<slot>-<ID>-{1-6}- AM
ODU2TCN-1-<shelf>-<slot>-<ID>-{1-6}- AM
ODU2TCT-1-<shelf>-<slot>-<ID>-{1-6}- AM
ODU2ETCN-1-<shelf>-<slot>-{1-10}-{1- 6}-AM
TCM NIM at transparent mapping ODU2E Termination on
10XANY10G
ODU2ETCT-1-<shelf>-<slot>-{1-10}-{1- 6}-AM
TCM Termination at transparent mapping ODU2E Termination on
10XANY10G
ODU2TCN-1-<shelf>-<slot>-{1-10}-{1-6 }-AM
TCM NIM at transparent mapping ODU2 Termination on
10XANY10G
ODU2TCT-1-<shelf>-<slot>-{1-10}-{1-6} -AM
TCM Termination at transparent mapping ODU2 Termination on
10XANY10G
24XANYMR
24XANYMR
24XANYMR
24XANYMR
....................................................................................................................................................................................................................................
1830 PSS
5-518
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Payload
Structure
Specifies the ODU payload Structure of the ODUPTF entity (i.e. the
embedded tributaries in terms of ODU1, ODU2). The string must match the
pattern [T#PN-ts[-ts-tsts][& T#PN-ts[-ts-ts-ts]]]* where PN is Port Number
of the constituent and T is the constituent Type with the following general
allowed values: ODU1, ODU2 and "ts" is the Multi Stucture Identier (MSI)
slot number . The overall bandwidth of the specified constituents must
exactly match the rate of the port. This parameter isonly valid when the
PLDTYPE=ODUM and when the ODUPTF is not ODU1
Manager Access
Control
Determines how the facility is managed (i.e. to which manager assigned).
<null>
Port is not managed by any specific manager.
CP
Port managed by TDM Control Plane.
MNGPLN,
Port managed by Management Plane.

ODU Subtype
Indicates the sub-type of the ODUPTF.

TERM
Terminated ODUPTF supporting either ODUs and/or STMn/OCn

entities
TRANSP
Transparent ODUPTF entity used to transparently carry

STMn/OCn/GBE10 entities.
....................................................................................................................................................................................................................................
1830 PSS
5-519
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The Properties - General - TCM window, invoked for a TCM facilty, is used to display
and modify parameter of a Tandem Connection Monitoring (TCM) entity.
Description
The Properties - General - TCM window, provides the following information:

Parameter
Details
General parameters visible in the area General.

Primary State
Specifies the primary state of the addressed ODU PTF.

IS
In Service
OOS
Out Of Service
This parameter is valid for both TCM NIM and TCM termination.
Secondary State
Secondary state, specifies the secondary state to which the facility is set.
AINS
AINS-DEA
Automatic In-Service Deactivate

....................................................................................................................................................................................................................................
1830 PSS
5-520
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
NE Native AID
Access Identifier, specifies an access Identifier of the ODU pool.

Possible values for TCM NIM facilities are:
OTUODU4TCN-1-{shelf}-{slot}-{1}-{1-6}-{AM,BM}
TCM NIM at higher order ODU4 NIM on 130SCUP/112CFPTB)
OTUODU3E2TCN-1-{shelf}-{slot}-{1}-{1-6}-{AM,BM}
(TCM NIM at higher order ODU3E2 NIM on 43SCUP)
OTUODU3TCN-1-{shelf}-{slot}-{1,2}-{1-6}-{AM,BM}
(TCM NIM at higher order ODU3 NIM on 2XANY40G)
OTUODU2ETCN-1-{shelf}-{slot}-{port}-{1-6}-{AM,BM}
(TCM NIM at higher order ODU2E NIM on a 10G ANY Multiport Card)
OTUODU2ETCN-1-{shelf}-{slot}-{1-4}-{1-6}-{AM,BM}
(TCM NIM at higher order ODU2E NIM on 11QCUP)
OTUODU2TCN-1-{shelf}-{slot}-{port}-{1-6}-{AM,BM}
(TCM NIM at higher order ODU2 NIM on a 10G ANY Multiport Card)
OTUODU2TCN-1-{shelf}-{slot}-{1-4}-{1-6}-{AM,BM}
(TCM NIM at higher order ODU2 NIM on 11QCUP)
ODU4ODU3TCN-1-{shelf}-{slot}-{ID}-{1-80}-{1-6}-{AM,BM}
(TCM NIM at lower order ODU3 NIM which is contained in ODU4 on virtual or
preset plane)
ODU3E2ODU3TCN-1-{shelf}-{slot}-{ID}-{1-32}-{1-6}-{AM,BM}
(TCM NIM at lower order ODU3 NIM which is contained in ODU3E2 on virtual
or preset plane)
ODU4ODU2ETCN-1-{shelf}-{slot}-{ID}-{1-80}-{1-6}-{AM,BM}
(TCM NIM at lower order ODU2E NIM which is contained in ODU4 on virtual or
preset plane)
ODU3E2ODU2ETCN-1-{shelf}-{slot}-{ID}-{1-32}-{1-6}-{AM,BM}
(TCM NIM at lower order ODU2E NIM which is contained in ODU3E2 on virtual
or preset plane)
ODU3ODU2ETCN-1-{shelf}-{slot}-{ID}-{1-32}-{1-6}-{AM,BM}
(TCM NIM at lower order ODU2E NIM which is contained in ODU3 on virtual or
preset plane)
preset plane)
or preset plane)
preset plane)
preset plane)
....................................................................................................................................................................................................................................
1830 PSS
Issue 1 June 2013
5-521

....................................................................................................................................................................................................................................
Parameter
Details
NE Native AID
Possible values for TCM NIM facilities are:
(continued)
or preset plane)
preset plane)
preset plane)
preset plane)
or preset plane)
preset plane)
preset plane)
ODU4TCN-1-{shelf}-{slot}-{ID}-{1-6}-AM
(TCM NIM at ODU4 Termination on virtual or preset plane)
ODU3E2TCN-1-{shelf}-{slot}-{ID}-{1-6}-AM
(TCM NIM at ODU3E2 Termination on virtual or preset plane)
ODU2ETCN-1-{shelf}-{slot}-{port}-{1-6}-AM
(TCM NIM at transparent mapping ODU2E Termination on a 10G ANY Multiport

Card)
ODU2TCN-1-{shelf}-{slot}-{port}-{1-6}-AM
(TCM NIM at transparent mapping ODU2 Termination on a 10G ANY Multiport

Card)
ODU1TCN-1-{shelf}-{slot}-{1-24}-{1-6}-AM
(TCM NIM at transparent mapping ODU1 Termination on 24XANYMR)
ODU0TCN-1-{shelf}-{slot}-{port}-{1-6}-AM
(TCM NIM at transparent mapping ODU0 Termination on a Multirate ANY Card)
....................................................................................................................................................................................................................................
1830 PSS
5-522
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
NE Native AID
Possible values for TCM termination facilities are:
(continued)
OTUODU4TCT-1-{shelf}-{slot}-{1}-{1-6}-{AM,BM}
(TCM Termination at higher order ODU4 NIM on 130SCUP/112CFPTB)
OTUODU3E2TCT-1-{shelf}-{slot}-{1}-{1-6}-{AM,BM}
(TCM Termination at higher order ODU3E2 NIM on 43SCUP)
OTUODU3TCT-1-{shelf}-{slot}-{1,2}-{1-6}-{AM,BM}
(TCM Termination at higher order ODU3 NIM on 2XANY40G)
OTUODU2ETCT-1-{shelf}-{slot}-{port}-{1-6}-{AM,BM}
(TCM Termination at higher order ODU2E NIM on a 10G ANY Multiport Card)
OTUODU2ETCT-1-{shelf}-{slot}-{1-4}-{1-6}-{AM,BM}
(TCM Termination at higher order ODU2E NIM on 11QCUP)
OTUODU2TCT-1-{shelf}-{slot}-{port}-{1-6}-{AM,BM}
(TCM Termination at higher order ODU2 NIM on a 10G ANY Multiport Card)
OTUODU2TCT-1-{shelf}-{slot}-{1-4}-{1-6}-{AM,BM}
(TCM Termination at higher order ODU2 NIM on 11QCUP)
ODU4ODU3TCT-1-{shelf}-{slot}-{ID}-{1-80}-{1-6}-{AM,BM}
(TCM Termination at lower order ODU3 NIM which is contained in ODU4 on

virtual or preset plane)
ODU3E2ODU3TCT-1-{shelf}-{slot}-{ID}-{1-32}-{1-6}-{AM,BM}
(TCM Termination at lower order ODU3 NIM which is contained in ODU3E2 on

ODU4ODU2ETCT-1-{shelf}-{slot}-{ID}-{1-80}-{1-6}-{AM,BM}
(TCM Termination at lower order ODU2E NIM which is contained in ODU4 on

ODU3E2ODU2ETCT-1-{shelf}-{slot}-{ID}-{1-32}-{1-6}-{AM,BM}
(TCM Termination at lower order ODU2E NIM which is contained in ODU3E2 on

ODU3ODU2ETCT-1-{shelf}-{slot}-{ID}-{1-32}-{1-6}-{AM,BM}
(TCM Termination at lower order ODU2E NIM which is contained in ODU3 on





....................................................................................................................................................................................................................................
1830 PSS
5-523
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
NE Native AID
Possible values for TCM termination facilities are:
(continued)







ODU4TCT-1-{shelf}-{slot}-{ID}-{1-6}-AM
(TCM Termination at ODU4 Termination on virtual or preset plane)
ODU3E2TCT-1-{shelf}-{slot}-{ID}-{1-6}-AM
(TCM Termination at ODU3E2 Termination on virtual or preset plane)
ODU2ETCT-1-{shelf}-{slot}-{port}-{1-6}-AM
(TCM Termination at transparent mapping ODU2E Termination on a 10G ANY

Multiport Card)
ODU2TCT-1-{shelf}-{slot}-{port}-{1-6}-AM
(TCM Termination at transparent mapping ODU2 Termination on a 10G ANY

Multiport Card)
ODU1TCT-1-{shelf}-{slot}-{1-24}-{1-6}-AM
(TCM Termination at transparent mapping ODU1 Termination on 24XANYMR)
ODU0TCT-1-{shelf}-{slot}-{port}-{1-6}-AM
(TCM Termination at transparent mapping ODU0 Termination on a Multirate ANY

Card)
....................................................................................................................................................................................................................................
1830 PSS
5-524
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Command Mode

Forced for ETSI
Normal for ANSI
AINS parameters
Automatic
In-Service
Threshold
condition before the system transitions the facility into the In-Service state.
[{0-167}-{0-59}], [168-0] Time, specifies the duration of an alarm free signal, in
HH-MM format, where value HH indicates the time duration in hours and value MM
indicates the time duration in minutes.
Trail Trace Identifier (TTI) parameters

AISONDEF
Determines if consequent action of sending AIS will be taken on the TCM defect.
ENABLE
Enable Consequent Action of TCM defect
DISABLE
Disable Consequent Action of TCM defect

This parameter is valid for TCM termination only.
For HO TCM, the TCM is in defect on LOS at the OCH layer, LOF, LOM, AIS-S or
TIM-S (if provisioned to do so) defects on OTUk input signals, or AIS-T, OCI-T,
LCK-T, LTC-T (if LTCRESP is ENABLE) or TIM-T (if TIMMRESP is ENABLE).
For LO TCM, the TCM is in defect on LOS at the OCH layer, LOF, LOM, AIS-S or
TIM-S (if TIMMRESP of OTU is ENABLE) defects on OTUk input signals, or AIS-P,
OCI, LCK, or TIM-P (if TIMMRESP on ODU is ENABLE), PLM-P defects on the HO
ODUk input signal or LOFLOM, MSIM, AIS-T, OCI-T, LCK-T, LTC-T (LTCRESP is
ENABLE) or TIM-T (if TIMMRESP is ENABLE) This parameter is valid for TCM
termination only.
....................................................................................................................................................................................................................................
1830 PSS
5-525
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Expected incoming
Destination Access
point Identifier
Expected incoming Destination Access Point Identifier (EXPDAPI). If the ASCII mode
is used then the double quotes are mandatory and the string can be less than 15
characters, while if the HEXA mode is used the prefix 'X' is mandatory and there shall
be exactly 30 characters.
Expected incoming Destination Access Point Identifier. Displayed either as HEX text
or Quoted ASCII string.
Hex textI
The string consists of 31 ASCII characters ("X" followed by 30 hexadecimal

characters), which encode the 15 byte TTI into 30 half-byte characters in hexadecimal
format. The string starts after the CRC header byte (the header byte is generated by the
NE and not returned in the response).
Quoted ASCII
This consists of 15 ASCII characters. If the trace to be displayed is all ASCII NULLs
(00 Hex), then 15 "." characters will be displayed. If the it contains ASCII characters
other than those listed here, then the "?" character will be displayed for those
characters. The string starts with the first character after the CRC byte.
Expected incoming
Source Access point
Identifier
Expected incoming Source Access Point Identifier (EXPDAPI). If the ASCII mode is
used then the double quotes are mandatory and the string can be less than 15
characters, while if the HEXA mode is used the prefix 'X' is mandatory and there shall
be exactly 30 characters.
Expected incoming Source Access Point Identifier. Displayed either as HEX text or
Quoted ASCII stringT.
Hex textI

Quoted ASCII
(00 Hex), then 15 "." characters will be displayed. If the it contains ASCII characters
other than those listed here, then the "?" character will be displayed for those
characters. The string starts with the first character after the CRC byte.
....................................................................................................................................................................................................................................
1830 PSS
5-526
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
LTC defect
Response
This parameter determines whether a Consequent Action of sending ODUk AIS on

detecting LTC defect will be taken or not.
ENABLE
Enable Consequent Action on LTC defect detection
DISABLE
Disable Consequent Action on LTC defect detection

This parameter is valid for both TCM NIM and TCM termination
Trail Trace
Identiifer
Monitoring
Determines if the incoming/received signal is monitored for the detection of Trail Trace
Identifier Mismatch defect. If monitoring is enabled, further determines if only DAPI,
only SAPI or both SAPI/DAPI are monitored for TIM defect generation.
TIM detection monitoring is disabled.
DAPI
TIM detection is enabled and only DAPI is used for the purpose.
SAPI
TIM detection is enabled and only SAPI is used for the purpose.
SAPIDAPI
TIM detection is enabled and both DAPI and SAPI are used for the purpose.
Trail Trace
Identifier Mismatch
Response
This parameter determines whether a Consequent Action will be taken such as sending
AIS for a TCM termination or use for switch criteria for SNCP for TCM NIM or pass
the received signal upon detection of a TCM layer trace Mismatch at its input.
DISABLE
Disable Consequent Action of TIM detection
ENABLE
Enable Consequent Action of TIM detection

....................................................................................................................................................................................................................................
1830 PSS
5-527
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Transmit
Destination Access
point Identifier
This parameter determines the Transmit TTI channel content of the Path Monitoring
overhead of an TCM information structure.
There are two options for entering this parameter: Hex String or Quoted String.
Hex textI

format. The string starts with the first byte after the header byte (i.e. the header byte is
generated by the NE). The 30 half-byte characters shall be entered as 15 pairs in the
value range from 0x00 to 0x7F.
Quoted ASCII
This consists of 0-15 ASCII valid input characters. The string will be padded with
ASCII NULL character if length is less than 15. The header byte is generated by the
NE
Transmit Operator
Specific Identifier
There are two options for entering this parameter: Hex String or Quoted String.
Hex textI

format. The string starts with the first byte after the header byte (i.e. the header byte is
generated by the NE). The 64 half-byte characters shall be entered as 32 pairs in the
value range from 0x00 to 0x7F.
Quoted ASCII
This consists of 0-32 ASCII valid input characters. The string will be padded with
ASCII NULL character if length is less than 32. The header byte is generated by the
NE
....................................................................................................................................................................................................................................
1830 PSS
5-528
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Transmit Source
Access point
Identifier
Displayed either as HEX text or Quoted ASCII string.
Hex textI

Quoted ASCII
(00 Hex), then 15 "." characters will be displayed.
Degraded Supervision parameters
Burst Interval
Specifies the number of consecutive bad seconds (see parameter Burst Threshold) to
be detected before declaring a signal degrade defect (SDBER) . The defect is cleared if
Burst Interval consecutive good seconds (see parameter Burst Threshold) are
detected.
Burst Threshold
2 10
Ingress Burst Threshold specifies a number of errored blocks on the TCM layer. A
second is declared as good if the number of detected errored blocks within one second
is less than BRSTTH; otherwise the second is declared as bad second.
for ODU0
{1-10210} for TCM carried by ODU0 (ODU0TCM)
for ODU1
for ODU2
for ODU2E
{1-82300} for TCM carried by ODU2E (ODU2ETCM)
for ODU3
for ODU3E2
{1-341478} for TCM carried by ODU3E2 (ODU3E2TCM)
for ODU4
TCM parameters
....................................................................................................................................................................................................................................
1830 PSS
5-529
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Level
The TCM level of the TCM entity

Possible values are
Position
The position of the TCM monitor

Possible values are
AM
After Matrix
BM
Before Matrix
Role
Defines the expected TCM termination type

Possible values are
TCT
for TCM termination.
TCN
for TCM NIM

Realtive Position
Defines the relative position of the TCM monitor point.

The lower the position sequence, the closer the TCM monitor point to the
client/matirix. This means that the consequent action of the lower numbered position
sequence TCM monitor point affects the higher numbered position sequence TCM
monitor point
Possible values are
Overhead Remove
Determines if, the provisioned TCM Overhead is inserted or not.

The TCM OH is passed through without modification
The received TCM OH is discarded and all zeros TCM overhead is inserted.
....................................................................................................................................................................................................................................
1830 PSS
5-530
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
Note: In the following table, OCh port represents the port to which the optical
pertains.
The Properties - General window, invoked for an optical , provides the following
information:
Parameter
Details
Name
Indicates the access identifier of the OCh port; see Overview of

access identifiers (p. 5-548).
Primary State
OCH-1-<shelf>-<slot>-<port> (OCH on a 10G ANY Multiport

Card)
OCH-1-<shelf>-<slot>-{1,2} (OCH on a 2XANY40G)
OCH-1-<shelf>-<slot>-{1-4} (OCH on a 11QCUP)
OCH-1-<shelf>-<slot>-{1} (OCH on a 43SCUP)
OCH-1-<shelf>-<slot>-{1} (OCH on a 130SCUP)
Indicates the secondary state of the OCh port; see for general
description.
IS In-Service
OOS Out Of Service
The parameter is applicable for the following OCH types:
Secondary State
BW
FIXED
TUNABLE
UPLINK
Indicates the secondary state of the OCh port; see for general
description.
AINS Automatic In-Service
AINS-DEA Automatic In-Service Deactivate
BW
FIXED
TUNABLE
UPLINK
....................................................................................................................................................................................................................................
1830 PSS
5-531
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Frequency in GHz
Indicates the frequency (in GHz) of the optical .

Possible values are in the range from 191100 GHz to 196150 GHz,
in steps of 50 GHz.
Valid for OCH Types FIXED, TUNABLE and UPLINK.
Min Frequency in GHz
Indicates the minimum frequency (in GHz) that is supported by the

optical .
The minimum frequency is 191100 GHz.
Valid for OCH Types TUNABLE and UPLINK.
Max Frequency in GHz
Indicates the maximum frequency (in GHz) that is supported by the

optical .
The maximum frequency is 196150 GHz.
Spacing between Min

and Max in GHz
Indicates the spacing, 50 GHz.
AINS -
Indicates how long an input signal must be present on the OCh port
without a failure condition before the system takes the OCh port into
the In-Service state.
Threshold
Time, specifies the duration of an alarm-free signal, in HH-MM

format, where value HH indicates the time duration in hours and
value MM indicates the time duration in minutes.
Restriction: The parameter is applicable for the following OCH
types:
AINS Automatic In Service

Timer
BW
FIXED
TUNABLE
UPLINK
Indicates how much time is currently remaining on the AINS timer

before the OCh port is taken into the In-Service state.
....................................................................................................................................................................................................................................
1830 PSS
5-532
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
AINS -
Indicates the criteria for taking the OCh port into the In-Service
state.
Criteria
Possible value is:
NOLOS - No loss of signal

The OCh port is taken into the In-Service state as soon as a
transition from no input signal present to input signal
applied is detected.

types:
BW
FIXED
TUNABLE
UPLINK
....................................................................................................................................................................................................................................
1830 PSS
5-533
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
AINS -
Determines if the conditions for the facility are reported or not. The
criteria for leaving the AUTO state autonomously depends on the
current value of the parameter Automatic In-Service Criteria. In
addition the set of conditions which are considered for the alarm
correlation with Port Mode depends on the current value of the
parameter Primary State Correlation.
Port Mode
The meaning of the different port modes is as follows:
AUTO - Port monitoring is disabled. The conditions as defined

by Primary State Correlation are not reported However, when a
transition from no input signal present to input signal
applied is detected (see Automatic In-Service Criteria), and
the AINS timer has expired (see Automatic In Service Timer),
then the port mode is autonomously switched to monitored.
Note that the transition from no input signal present to input
signal applied is mandatory in order that the port mode can
autonomously be switched to monitored. The port mode will
remain unchanged (Auto) as long as no transition from no input
signal present to input signal applied takes place.
MON (Monitored) - Port monitoring is enabled, conditions are

reported according the defined ASAP.
NMON (Not monitored) - Port monitoring is disabled, the

incoming port signal is not monitored for defects. Conditions as
defined by the Primary State Correlation are not reported.

types:
AINS Primary State

Correlation
BW
FIXED
TUNABLE
UPLINK
Determines the set of conditions which shall not be reported when

the Port Mode is NMON.
LOS
ALL
all non off-normal conditions reported by the OCH port

types:
BW
FIXED
TUNABLE
UPLINK
....................................................................................................................................................................................................................................
1830 PSS
5-534
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Misc. -
Indicates which manager is currently assigned to the OCh port.
Manager Access Control
CP - The OCh port is managed by the control plane.
MNGPLN - The OCh port is managed by the management plane

(NMS or TL1 manager).
CP&MNGPLN - The OCh port is jointly managed by the

control plane and the management plane.
[not specified]- The OCh port is not managed by any specific

manager.
Misc. -
Indicates the OTU rate carried by the OCH.
OTU Level
Misc. -Encoding
OTU2
OTU2E
OTU3
OTU3E2
OTU4
Determines the modulation/line code which is applied..

NRZ
Non-Return-to-Zero (for OTU2/OTU2E)
NRZ
Non-Return-to-Zero (for OTU3)
COHPMBPSK
Coherent Polarisation Multiplexing Binary Phase-Shift Keying
(for OTU3E2)
PDMQPSK (OTU4 / UPLINK )

Polarization Division Multiplexing and Quadrature Phase-Shift
Keying with coherent detection
PDMINRZQPSK UPLINK (OTU4 / UPLINK)

Polarization Division Multiplexing with Interleaved
Non-Return-to-Zero and Quadrature Phase-Shift Keying with
coherent detection

types:
BW
FIXED
TUNABLE
UPLINK
....................................................................................................................................................................................................................................
1830 PSS
5-535
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
Misc. -OCH Type
Determines the OCH sub-type with the following value:

BW
OCH is a black & white
FIXED
OCH is a coloured with fixed frequency determined by the

provisioned equipment module type
TUNABLE
OCH is a coloured with provisionable frequency
UPLINK
OCH is a coloured with provisionable frequency and is managed

by DWDM compound
Misc. -Actual Laser
State
Determines whether the laser is switched on or off.

If no frequency is provisioned (i.e. == F0 and parameter is
applicable for the OCH type) the laser will be off independent from
the TSTATE provisioning.
On
Off

types:
CHANWK1
BW
FIXED
TUNABLE
UPLINK
0 for an unprovisioned wavekey {1-4095} for provisioned wavekey

The parameter specifies the first provisioned WavelengthTracker key
for the OCH.
CHANWK2
UPLINK
0 for an unprovisioned wavekey {1-4095} for provisioned wavekey

The parameter specifies the second provisioned WavelengthTracker
key for the OCH.
UPLINK
....................................................................................................................................................................................................................................
1830 PSS
5-536
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
CMDMDE
Command Execution Mode. .

Two different values are supported depending on the NE region
FRCD for ETSI
NORM for ANSI
RMCONPORT
BW
FIXED
TUNABLE
UPLINK
NONE (1-40 VALID USERLABEL CHARACTERS)

The parameter specifies the remote connected port (RMCONPORT)
to the OCH as determined via cable provisioning as configured in
the DWDM compound. The value NONE is used if a cable
connection is not yet provisioned The userlabel string specifies shelf,
slot and port of the optical card in the DWDM compound cabled
with the uplink OCH facility.
TCAPROF
UPLINK
Definition of the active threshold crossing alarm profile (TCA) for

optical PM.
<userlabel>
TXDELTAPOWER
UPLINK
The parameter describes the acceptable power delta (unit: mBm)

from the target transmit power at the addressed WaveTracker
encoder (TXDELTAPOWER: Transmit Delta Power).
{-9999 - 9999}
TXTARGETPOWER
UPLINK
The parameter specifies the target transmit power (unit: mBm)at the
addressed WaveTracker (TXTARGETPOWER: Transmit Target
Power).
{-9999 - 9999}
UPLINK
....................................................................................................................................................................................................................................
1830 PSS
5-537
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
WTENABLE
The parameter specifies whether WaveTracker encoder is enabled or

not (WTENABLE: Wavetracker Enable).
{Y, N}
WTENABLEKEYS
UPLINK
The parameter specifies whether WaveTracker key use is enabled or

not (WTENABLEKEYS: Wavetracker Enable Keys).
{Y, N}
WTENABLEPWRCTL
UPLINK
The parameter specifies whether WaveTracker power control is

enabled or not (WTENABLEPWRCTL: Wavetracker Enable Power
Control).
{Y, N}
UPLINK
....................................................................................................................................................................................................................................
1830 PSS
5-538
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The View Duplex Switching Equipments window displays the parameters related to the
equipment protection groups in an Alcatel-Lucent 1830 PSS system; it provides the
following information:
Parameter
Details
Active
The AID of the active equipment in the duplex switching equipment

protection group.
Values are:
Standby
FLC-1-<shelfs>-{73,75} (Controller in FLC slot, PSS-64)
MTX-1-<shelfs>-{71,72} (Controller in MTX slot, PSS-64)
The AID of the inactive equipment in the duplex switching

equipment protection group.
Values are:
....................................................................................................................................................................................................................................
1830 PSS
5-539
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Details
GROUP STATE
Indicates the status of the equipment protection group for the

agnostic matrix card.
Values are:
NOREQ - No switch request or switch inhibition is active, no

failure is present, ready to switch.
DEGRADED - No switch request or switch inhibition is active,

at least one of the involved agnostic matrix cards has a minor
failure, no major failure present.
FAILURE - No switch request or switch inhibition is active, at

least one of the involved agnostic matrix cards has a major
failure.
FORCED - A forced switch or switch inhibition is active,

switching is not possible.
ALIGNING - No switch request or switch inhibition is active,

the inactive agnostic matrix card is not yet aligned (not in a
position to take on the standby role).
NORED - The redundant equipment module is not available.
RECOVERY - One or both agnostic matrix cards are in a

recovery; the equipment protection group is temporarily not
available.
UNAVAIL - The equipment protection group is permanently not

available.
....................................................................................................................................................................................................................................
1830 PSS
5-540
Issue 1 June 2013

....................................................................................................................................................................................................................................

Primary states
The following primary states are defined:
IS In service
The entity is capable and allowed to provide its provisioned functions. The IS primary
state usually relates to equipment entities.
IS-NR In service, Normal

The entity is capable and allowed to provide its provisioned functions. The IS-NR
primary state usually relates to facilities.
IS-ANR In service, Abnormal

The entity is capable to provide most of its functions, is allowed to provide its
provisioned functions, but is operating in a degraded or abnormal state.
OOS-AU Out of service, Autonomous

The entity is not available for providing its provisioned functions but the entity is not
intentionally suspended by an external management command (from an OS or craft
interface) from performing these functions. In general, the cause of the incapability is
due to an unsolicited autonomous event detected in the system or in the associated
network (for instance, OC-3 LOS detected).
OOS-MA Out of service, Management

The entity is intentionally suspended by external management command from
performing its provisioned functions, but the entity may still be operationally capable
of performing its provisioned functions.
OOS-AUMA Out of service, Autonomous and Management

The entity is not available for providing its provisioned functions because an
OOS-AU state transition has occurred and the entity is intentionally suspended by
external management command from performing its provisioned functions.
Secondary states
The following secondary states are defined:
ACT Active
The entity is currently in use and has spare operating capacity for further usage
demand. When applied to a facility entity, this value means that the entity is
cross-connected (the entity is a constituent leg of a cross-connection) and additional
cross-connection capacity is available, such that more one-way cross-connections can
be added.
....................................................................................................................................................................................................................................
1830 PSS
5-541
Issue 1 June 2013

....................................................................................................................................................................................................................................
The entity is allowed to transition to the in-service state if it is operationally capable.

For example, an OC-3 transitions from OOS-AU,AINS to IS when all OC-3 alarm
conditions have cleared.
BUSY Busy
The entity is currently in use and has no spare operating capacity for further usage
demand. For example, a head end bridge with 2 broadcast legs, or a connected test
access port are both BUSY.
CLKNA Clock Not Aligned

The clock of the standby matrix is not aligned to the clock of the active matrix.
CP Control Plane
The facility or connection is under management by the control plane for data services.
CPMP Control Plane

The facility or connection is shared between management plane and the control plane.
DSBLD Disabled
The facility entity is prohibited from carrying traffic, for example because the
required supporting equipment is not provisioned or provisioned for another service.
FAF Facility Failure

The associated facility entity has failed, for example a LOS, LOF or AIS condition is
present.
LPBK Loopback
A loopback activity is currently being performed on the entity.
MDLT Manual Delete

The ODU path-terminated facility has been manually provisioned, and can only be
deleted by manual command. The MDLT secondary state is valid for ODU
path-terminated facilities only.
MEA Mismatch of Equipment and Attributes

An incompatible system component is physically present in a provisioned slot.
MT Maintenance
The standby FLC is in a temporary maintenance state (for example during
Backup/Restore).
NOIMP Not Implemented in Hardware

The higher-order ODU path termination function (HO ODUPTF) and lower-order
ODU path termination function (LO ODUPTF; if any) entities are not connected
toward the NNI side.
PMD Performance monitoring inhibited and disabled
....................................................................................................................................................................................................................................
1830 PSS
5-542
Issue 1 June 2013

....................................................................................................................................................................................................................................
The performance monitoring counters (current and history counters) have been
removed from memory.
PSI Protection Switching Inhibited

The working entity is inhibited from automatic protection switching by means of an
operator command, that means, it is locked out from automatic protection switching.
SDEE Supported Entity Service Exists

The entity (equipment or facility) is currently supporting services such as
cross-connections or loopback, or is supporting other entities that are carrying such
services.
Attempts to delete an entity carrying an SDEE secondary state is denied.
When SDEE is set on an entity then the SDEE state is propagated to the entity's
parents and up the supporting hierarchy chain. This applies to the complete facility
and equipment hierarchy.
When SDEE is removed on an entity due to the deletion of a service, then the SDEE
state of the entity's parents is reevaluated. If this is the last service being supported by
the parent(s) then SDEE is removed from the parent(s) also. In this case, the
reevaluation shall continue up the supporting hierarchy chain.
For an OTUk port, SDEE is set if it:
HO ODUk has SDEE condition
is involved in a loopback
has a GCC0 channel enabled.
For an HO ODUk path facility, SDEE is set if it:
has a GCC1 channel enabled
is cross connected to HO ODUkTERM entity (Virtual)
is cross connected to another ODUk (Matrix)
a TCM is provisioned corresponding to this ODUk
For an HO ODUkTERM path facility, SDEE is set if it:
is cross connected to ODUk entity (i.e. as soon as it is created)
a TCM is provisioned corresponding to this ODUkTERM
For an LO ODUj path facility, SDEE is set if it:
is intact cross connected to another ODUj (Matrix)
a TCM is provisioned corresponding to this ODUk
....................................................................................................................................................................................................................................
1830 PSS
5-543
Issue 1 June 2013

....................................................................................................................................................................................................................................
For an equipment port of an IO card with matrix interface, SDEE is set if:
the associated OCn/STMn/GBE10 facility is in SDEE (port with non OTN client
port)
the associated OTU facility is in SDEE (port OTN port)

the remote connected port (TL1 parameter ,RMCONPORT) is set for the OCH
facility on uplink card (port OTN port)
For a tranparently transported STMn/OCn, SDEE is set if:
the ODUkTERM used to carry OCn/STMn is in SDEE
the OCn/STMn is in a loopback
For a tranparently transported GBE10, SDEE is set if:
the ODUkTERM used to carry GBE10 is in SDEE
the GBE10 is in a loopback
For a tranparently transported GBE, SDEE is set if:
the ODUkTERM used to carry GBE is in SDEE
the GBE is in a loopback
For an ODUkTERM used to transparently carry GBE10/OCn/STMn , SDEE is set if:
the GCC1 is enabled.
it is cross connected to ODUk (Matrix).
a TCM is provisioned corresponding to this ODUkTERM.
For an ODU0TERM used to transparently carry GBE, SDEE is set if:
the GCC1 is enabled.
it is cross connected to ODU0 (Matrix).
a TCM is provisioned corresponding to this ODUkTERM
For a TCM, SDEE is set if:
on all TCM entities, which are referenced by the protected method or protecting
method of a protection connection.
For a XFP/SFP, SDEEis set if
the OCn/STMn/GBE/GBE10 ports residing on the XFP/SFP is in SDEE
For an OCn/STMn port, SDEEis set if it:
is involved in a loopback
one of its embedded tributaries has SDEE condition
For a GBE and GBE10 port, SDEE is set if:
the ODUkTERM used to carry GBE/GBE10 is in SDEE
the GBE/GBE10 is in a loopback
For an STSn/VCn path facility, SDEE is set if it:
is used in cross-connection (SST has ACT or BUSY)
....................................................................................................................................................................................................................................
1830 PSS
5-544
Issue 1 June 2013

....................................................................................................................................................................................................................................
Card/Port/SFP/XFP Level SDEE SST setting rules:

A Card has the SDEE SST set if at least one Port/SFP/XFP provisioned on it has
the SDEE SST set
A Port/SFP/XFP has the SDEE SST set if at least one Facility supported by it has
the SDEE SST set
Just the presence of a facility does not constitute SDEE on the Port/SFP/XFP
SDEE is set by control plane, if:
The OTU is assigned to MP, associated TCM entity is assigned to CP. Note, that
this state is a transient state. It will be left automatically by CP removing the TCM
entity.
The detailed state of affected entities is the following: OCH/OTU/OTUODUn:
SST=MP,SDEE; MGRACD=MGNPLN
The OTU is assigned to MP, associated TCM is not assigned to any plane. Note,
that this state is outside the CP scope.
The OTU and associated TCM entity are assigned to MP. Note, that this state is
outside the CP scope.
The OTU and associated TCM entity are not assigned to any plane. Note, that this
state is outside the CP scope.
SST=SDEE; MGRACD=<>
The OTU is not assigned to any plane, associated TCM is assigned to MP. Note,
that this state is outside the CP scope.
SST=SDEE; MGRACD=<>
The OTU is not assigned to any plane, the associated TCM entity is assigned to
CP.
SST=SDEE; MGRACD=<>
The OTU is assigned as supporting facility to an INNI DB, no traffic is

established.
SST=CP,SDEE; MGRACD=CP
The OTU is assigned as supporting facility to an INNI DB with traffic being

established.
....................................................................................................................................................................................................................................
1830 PSS
5-545
Issue 1 June 2013

....................................................................................................................................................................................................................................

SST=CP,SDEE; MGRACD=CP
The OTU is assigned as supporting facility to an INNI DB, traffic is established,

no associated TCM entity exists. Note, that this state is a transient state. It will be
left automatically by CP creating a TCM entity.
SST=CP,SDEE; MGRACD=<>
The OTU is assigned as supporting facility to a DROP DB, traffic is established,

no associated TCM entity exists.
SST=CPMP,SDEE; MGRACD=CP&MGNPLN;
SGEO Supporting Entity Outage

The associated supporting entity has failed (OOS-AU) or is out-of-service due to a
management action (OOS-MA or OOS-AUMA), or set itself to state SGEO.
STBYC Standby Cold

The system component is the standby unit for another system component. A standby
unit with a cold standby status will not be immediately able to take over the role of
the active unit, and will require some initialization activity. An autonomous or manual
switch cannot be performed within 50 ms. Note that the STBYC state will be
maintained even when the standby unit is out of service. The STBYC state is mutually
exclusive with the WRK and STBYH states.
STBYH Standby Hot

In a facility protection scheme, this secondary state is declared on the standby facility
whenever a switch request or signal fail or signal degrade (SF/SD) condition is not
present. In the context of equipment protection this state is also declared for the
standby matrix card.
STBYS Standby Switched

In a facility protection scheme, this secondary state is declared on the standby facility
whenever any switch request (other than WTR, DNR, or NR) is present.
SWDL Software Download

A software download is in progress, the system component is out of service because it
is in the process of acquiring, loading, and/or initializing its software.
TRM Terminated
The facility entity has been given termination parameters, that means, the entity has
been connected and its path has been terminated (as a result of the connection) or the
parent entity has been terminated as a result of its subentities being connected. For
line entities, this state indicates that the entity is supporting cross-connections.
UAS Unassigned
....................................................................................................................................................................................................................................
1830 PSS
5-546
Issue 1 June 2013

....................................................................................................................................................................................................................................
The entity has not been assigned with the necessary provisioning data. No service
activity or maintenance activity (including monitoring, testing, or service recovery) is
permitted in this state since the necessary data has not been assigned.
UEQ Unequipped
There is no system component in the addressed position.
WRK Working
The entity is currently providing service as part of a protection group (for instance,
selector is selecting this entity in a path protection configuration).
....................................................................................................................................................................................................................................
1830 PSS
5-547
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
Access identifiers (AIDs) are used for addressing particular components within an
Alcatel-Lucent 1830 PSS system, like a shelf, circuit pack, slot or port, for example.
Types of access identifiers
The following types of AIDs can be distinguished:
Equipment AIDs
Facility AIDs - AIDs related to Input/Output (I/O) facilities of the system
Timing Reference AIDs
ASAP (Alarm Severity Assigned Profile) AIDs
THP (Threshold Profile) AIDs

Common AIDs
These types of AIDs will be described subsequently.

Conventions used
The following conventions are used for the description of access identifiers:
If certain values (or a value range) are possible for an entry, then these values are
given in curly braces, for example:
{1,17,33,49} represents a discrete set of possible values
{1-9} represents a value range
Optional AID components are enclosed in square brackets, for example [SFP/XFP#].
Equipment AIDs
The general equipment AID format is as follows:
equipment name - bay# - shelf# - slot# - [SFP/XFP/PORT#]
where:
equipment name represents the type of equipment
bay# represents the bay number
bay has always the fixed value 1
shelf# represents the shelf number within the sytem
slot# represents the slot number or position within the shelf in which the
equipment is present
SFP/XFP/PORT# represents the SFP, XFP, or port number within the slot
....................................................................................................................................................................................................................................
1830 PSS
5-548
Issue 1 June 2013

....................................................................................................................................................................................................................................
Shelf, slot and virtual ID ranges
The numeric shelf/slot/ID values depend on the shelf type (for example PSS-64, PSS-36).
The shelf/slot/ID ranges are defined in the following tables.
Table 5-16
Value ranges for the shelf field in the AID depending on the shelf
type
Shelf type
Shelf range
Description
PSS64
{1}
PSS-64 universal shelf (active

shelf)
PSS36
{1-31}
PSS-36 universal shelf (active

shelf)
TRU
{128-255}
Top Rack Unit shelf (passive

shelf)
Table 5-17
Relation of equipment name/equipment AID prefix to supported

PROVISIONEDTYPES
Equipment name / AID Prefix
Supported PROVISIONEDTYPES
SHELF
PSS36, PSS64
BTC
BT3T8, BTC3T8, BT36
PF
PSF3T8, PSFC
FAN
FAN3T8
FLC
ECHC, FLC36EA
MTX
MT960C, MT1T9, MT1T9C, MT3T8
24XANYMR
24XANYMR, 24XANYMRB, 24XETH1G,

24XETH1GB, 24XSTHMR
8XANYMR
8XETH1G, 8XETH1GB
10XANY10G
10XANY10G, 10XOTH10G, 10XETH10G,

10XSTH10G
4XANY10G
4XANY10G
2XANY40G
2XANY40G
130SCUP
130SCUP, 112CFPTB
43SCUP
43SCUP
11QCUP
11QCUP, 11QCUPC
SFC8
SFC8
....................................................................................................................................................................................................................................
1830 PSS
5-549
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-17
Relation of equipment name/equipment AID prefix to supported

PROVISIONEDTYPES (continued)
Equipment name / AID Prefix
Supported PROVISIONEDTYPES
SFP
SR10G155TU, SL10G155TU, SL20G155TU,

SR10G622TU, SL10G622TU, SL20G622TU,
SR12G7TU, IR12G7TU, LR12G7TU, LR22G7TU,
IR12G7AU, 1000BSXU, 1000BLXU, 1000BZXU
XFP
SR111G1AU, IR211G1AU, LR211G1AU,

LRT11G1TU, LRZCT11G1TUC.
The following CWDM/DWDM XFPs are
supported:
SR<xx>W11G1TUC,
SR<xx>W11G1TUI
LR<xx>W11G1TUC
LR<xx>DW11G1TUC
LR<xx>W11G1TUI
ONETRU
ONETRU
HPCFAP
HPCFAP
Important! A shelf of shelf type PSS64 will always be used as main shelf. So the
shelf value will always be {1} although in the following examples the theoretical
range of {1-31} is mentioned.
Table 5-18
Component

Access identifier for Alcatel-Lucent
1830 PSS-64
1830 PSS-36
Shelf
SHELF-{1}-{31}
SHELF-{1}-{1-31}
Main shelf
SHELF-1-1
SHELF-1-1
First-level Controller
FLC-{1}-{1-31}-{73,75}
FLC-{1}-{1-31}-{23,40}
First-level Controller, Primary

Working
FLC-{1}-{1-31}-73
FLC-{1}-{1-31}-23
First-level Controller, Secondary

Protection
FLC-{1}-{1-31}-75
FLC-{1}-{1-31}-40
Matrix and Timing Card
MTX-{1}-{1-31}-{71,72}
MTX-{1}-{1-31}-{11,15}
Matrix and Timing Card, Primary

Working
MTX-{1}-{1-31}-71
MTX-{1}-{1-31}-11
Matrix and Timing Card, Secondary

Protection
MTX-{1}-{1-31}-72
MTX-{1}-{1-31}-15
....................................................................................................................................................................................................................................
1830 PSS
5-550
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-18
Component
(continued)
1830 PSS-64
1830 PSS-36
Matrix and Timing Card, port
MTX-{1}-{1-31}-{71,72}-{SCNAUX,VOIP,
ES1, ES2, E1, E2}
MTX-{1}-{1-31}-{11,15}-{SCNAUX,VOIP,
ES1, ES2, E1, E2}
First-level Controller, customer LAN

port
LANPORT-{1}-{1-31}-{73,75}-{OAMP,
CIT}
FLC-{1}-{1-31}-{23,40}-{OAMP,CIT}
Matrix and Timing Card, shelf

interconnection LAN ports
LANPORT-{1}-{1-31}-{71,72}-{ES1, ES2}
LANPORT-{1}-{1-31}-{11,15}-{ES1, ES2}
Power Supply Filter
PF-{1}-{1-31}-{91,94}
PF-{1}-{1-31}-{44,45}
Top-Rack-Unit shelf
TRU-{1}-{1-31}
High-Power Connection Fuse and

Alarm Panel
HPCFAP-1-{128-255}-1
Fan unit
FAN-{1}-{1-31}-{92,93}
FAN-{1}-{1-31}-{41}
10 10G ANY client port card
10XANY10G-{1}-{1-31}-{1-16,33-48}
10XANY10G-{1}-{1-31}-{2-9,12,13,16-21}
4XANY10G-{1}-{1-31}-{1-16,33-48}
4XANY10G-{1}-{1-31}-{2-9,12,13,16-21}
Port groups on 10 10G ANY client

port cards
PORTGP-{1}-{1-31}-{1-16,33-48}-{1,3,5,7,
9}
PORTGP-{1}-{1-31}-{2-9,12,13,16-21}-{1,3,
5,7,9}

port cards
PORTGP-{1}-{1-31}-{1-16,33-48}-{1,3}
PORTGP-{1}-{1-31}-{2-9,12,13,16-21}-{1,
3}
2XANY40G-{1}-{1-31}-{1-16,33-48}
2XANY40G-{1}-{1-31}-{2-9,12,13,16-21}

port cards
PORTGP-{1}-{1-31}-{1-16,33-48}-{1,2}
PORTGP-{1}-{1-31}-{2-9,12,13,16-21}-{1,
2}
8 Multirate ANY client port card
8XANYMR-{1}-{1-31}-{1-16,33-48}
8XANYMR-{1}-{1-31}-{2-9,12,13,16-21}
24 Multirate ANY client port card
24XANYMR-{1}-{1-31}-{1-16,33-48}
24XANYMR-{1}-{1-31}-{2-9,12,13,16-21}
Port groups on 8 Multirate ANY

client port cards
PORTGP-{1}-{1-31}-{1-16,33-48}-{1}
PORTGP-{1}-{1-31}-{2-9,12,13,16-21}-{1}
Port groups on 24 Multirate ANY

client port cards
PORTGP-{1}-{1-31}-{1-16,33-48}-{1,9,17}
PORTGP-{1}-{1-31}-{2-9,12,13,16-21}-{1,9,
17}
XFP on 10 10G ANY client port

cards
XFP-{1}-{1-31}-{1-16,33-48}-{1-10}
XFP-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
XFP on 4 10G ANY client port

cards
XFP-{1}-{1-31}-{1-16,33-48}-{1-4}
XFP-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
SFP on 24 Multirate ANY client

port card
SFP-{1}-{1-31}-{1-16,33-48}-{1-24}
SFP-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
SFP on 8 Multirate ANY client

port card
SFP-{1}-{1-31}-{1-16,33-48}-{1-8}
SFP-{1}-{1-31}-{2-9,12,13,16-21}-{1-8}
Ports on 2 40G ANY client port

cards (fixed optical ports)
PORT-{1}-{1-31}-{1-16,33-48}-{1-2}
PORT-{1}-{1-31}-{2-9,12,13,16-21}-{1-2}
11G Switchponder 11QCUP
11QCUP-{1}-{1-31}-{2-16,33-48}
11QCUP-{1}-{1-31}-{2-9,12,13,16-21}
....................................................................................................................................................................................................................................
1830 PSS
5-551
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-18
Component
(continued)
1830 PSS-64
1830 PSS-36
Port groups on 4 11G

Switchponder 11QCUP
PORTGP-{1}-{1-31}-{2-16,33-48}-{1,3}
PORTGP-{1}-{1-31}-{2-9,12,13,16-21}-{1,
3}
Ports on 4 11G Switchponder

11QCUP
PORT-{1}-{1-31}-{2-16,33-48}-{1-4}
PORT-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
1 43G Switchponder 43SCUP
43SCUP-{1}-{1-31}-{2-7,9-15,33-39,41-47}
43SCUP-{1}-{1-31}-{2-8,12,16-20}
1 100G Switchponder 130SCUP
130SCUP-{1}-{1-31}-{2-7,9-15,33-39,4147}
130SCUP-{1}-{1-31}-{2-8,12,16-20}
1 112G Test Board 112CFPTB
130SCUP-{1}-{1-31}-{2-7,9-15,33-39,4147}
130SCUP-{1}-{1-31}-{2-8,12,16-20}
Port on a 1 100G Switchponder

130SCUP / 1x100G Switchponder
Test Board 112CFPTB
PORT-{1}-{1-31}-{2-7,9-15,33-39,41-47}{1}
PORT-{1}-{1-31}-{2-8,12,16-20}-{1}
Port group on a 1 100G

Switchponder 130SCUP / 1x100G
Switchponder Test Board 112CFPTB
PORTGP-{1}-{1-31}-{2-7,9-15,33-39,4147}-{1}
PORTGP-{1}-{1-31}-{2-8,12,16-20}-{1}
Port groups on 1 43G

Switchponder 43SCUP
PORTGP-{1}-{1-31}--{2-7,9-15,33-39,4147}-{1}
PORTGP-{1}-{1-31}-{2-8,12,16-20}-{1}
SFC8 static filter card (optical

mux/demux)
SFC8-{1}-{1-31}-{1-16,33-48}
SFC8-{1}-{1-31}-{2-9,12,13,16-21}
Ports on a SFC8 static filter card
PORT-{1}-{1-31}-{1-16,33-48}-{1471,
1491, 1511, 1531, 1551, 1571, 1591, 1611,
OMD}
PORT-{1}-{1-31}-{2-9,12,13,16-21}-{1471,
1491, 1511, 1531, 1551, 1571, 1591, 1611,
OMD}
SFC8 Mux/Demux Port
OTS-{1}-{1-31}-{1-16,33-48}{OMD}
OTS-{1}-{1-31}-{2-9,12,13,16-21}-{OMD}
SFC8 Optical Channel I/O ports
PORT-{1}-{1-31}-{1-16,33-48}-{1471,
1491, 1511, 1531, 1551, 1571, 1591, 1611}
PORT-{1}-{1-31}-{2-9,12,13,16-21}-{1471,
1491, 1511, 1531, 1551, 1571, 1591, 1611}
BT3T8-{1}-{1-31}-{81,82,85,86}
Bus Termination Card CMISS
BTC-{1}-{1-31}-{81,82,83,84,85,86}
BTC-{1}-{1-31}-{42,43}
Bus Termination Card CMISS (with

shelf remote inventory)
BTC-{1}-{1-31}-84
BTC-{1}-{1-31}-43
External Optical Connection
EXTERNAL
EXTERNAL
Facility AIDs
The general AID format of the Input/Output (I/O) facilities is as follows:
facility type - bay# - shelf# - slot# - facility#
where:
facility type represents the facility type (for example OC192, or ODU3)
bay# represents the number of the bay within the system.
....................................................................................................................................................................................................................................
1830 PSS
5-552
Issue 1 June 2013

....................................................................................................................................................................................................................................
shelf# represents the number of the shelf within the specified bay.
slot# represents the number of the slot or position within the shelf in which the
facility is present. For facilities on virtual ODU planes the slot number 71 is used.
For facilities on the Preset AID plane the slot number 72 is used.
facility# represents the facility number. This facility number depends on the
type of facility; see the corresponding facility AID formats which are described in
the following.
Alcatel-Lucent 1830 PSS facility AIDs are composed as follows:
SONET facility AIDs are of the form:

facility type - bay# - shelf# - slot# - OC# [- STSnC# [- STS1#]]
where:
the elements ranging from facility type to slot# correspond to the general
facility AID format as described above,
OC# is the OC facility number within the slot ,
SDH facility AIDs are of the form:
facility type - bay# - shelf# - slot# - STM# [ - AU4#]
where:
STM# STM facility (port) number within the slot.
OTN facility AIDs are of the form:
facility type - bay# - shelf# - slot# - facility# [ - ODU#]
where:
facility# is the facility (port) number within the slot or the facility number
within the ODU plane.
ODU# is the lower order ODU facility number.
WDM facility AIDs are of the form:
facility type - bay# - shelf# - slot# - facilityID# [ -tributaryID#]
where:
facility# is the facility (port) number within the slot or the facility number
within the ODU plane.
tributaryID# is the tributary identifier. The tributary identifier is either the
tributary number, the tributary mnemonic name, the optical wavelength or the
optical frequency.
....................................................................................................................................................................................................................................
1830 PSS
5-553
Issue 1 June 2013

....................................................................................................................................................................................................................................
OTH TCM facility AIDs are of the form:

prefix - bay# - shelf# - slot# - facility# [ - ODU#] - level# - position
where:
prefix
is the TCM facility name. The TCM facility name is the name of the OTN facility
containing the TCM facility followed by either TCN for a TCM NIM or TCT
for a TCM termination.
the elements ranging from bay# to slot# correspond to the general facility AID
format as described above,
facility#
is the facility number.

For facilities associated with physical ports, the facility number is the number of
the facility (port) within the slot. For facilities on the virtual ODU plane, the
facility number is an integer number assigned by the system during facility
creation.
For facilities on the Preset AID plane, the facility number is an integer number
calculated from the slot and port number as: facility# = slot# * 100 +
port#.
ODU#
is the lower order ODU facility number.
level#
is the TCM level.
position
is the position of the TCM facility, AM indicates after matrix, BMindicates

before matrix.
Gigabit Ethernet facility AIDs are of the form:

facility type - bay# - shelf# - slot# - facility#
where:
facility# is the facility (1/10 GbE port) number within the slot.
Important! A shelf of shelf type PSS64 will always be used as main shelf. So the
shelf value will always be {1} although in the following examples the theoretical
range of {1-31} is mentioned.
....................................................................................................................................................................................................................................
1830 PSS
5-554
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
Facility
Access identifier for Alcatel-Lucent 1830 PSS-64
OC-48 on a
24 Multirate ANY
client port card
OC48-{1}-{1-31}-{1-16,33-48}-{1-24}
OC48-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
STS-48 mapped into an

OC-48 on a
24 Multirate ANY
client port card
OC48STS48C-{1}-{1-31}-{1-16,33-48}-{1-24}-1
OC48STS48C-{1}-{1-31}-{2-9,12,13,16-21}-{124}-1
STS-12c mapped into an

OC-48 on a
24 Multirate ANY
client port card
OC48STS12C-{1}-{1-31}-{1-16,33-48}-{1-24}-{1,
5,9,13}
OC48STS12C-{1}-{1-31}-{2-9,12,13,16-21}-{124}-{1,5,9,13}

OC-48 on a
24 Multirate ANY
client port card
OC48STS3C-{1}-{1-31}-{1-16,33-48}-{1-24}{116}
OC48STS3C-{1}-{1-31}-{2-9,12,13,16-21}-{124}-{116}

OC-48 on a
24 Multirate ANY
client port card
OC48STS1-{1}-{1-31}-{1-16,33-48}-{1-24}-{116}-{1-3}
OC48STS1-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}{116}-{1-3}
OC-3 on a
24 Multirate ANY
client port card
OC3-{1}-{1-31}-{1-16,33-48}-{1-24}-1
OC3-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}-1
OC-12 on a
24 Multirate ANY
client port card
OC12-{1}-{1-31}-{1-16,33-48}-{1-24}
OC12-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
OC-192 on a 4 10G
ANY client port card
OC192-{1}-{1-31}-{1-16,33-48}-{1-4}
OC192-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
OC-192 on a 10 10G
OC192-{1}-{1-31}-{1-16,33-48}-{1-10}
OC192-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}

OC-192 on a 10 10G
OC192STS48C-{1}-{1-31}-{1-16,33-48}-{1-10}-{1, OC192STS48C-{1}-{1-31}-{2-9,12,13,16-21}-{117,33,49}
10}-{1,17,33,49}

OC-192 on a 10 10G
OC192STS12C-{1}-{1-31}-{1-16,33-48}-{1-10}-{1, OC192STS12C-{1}-{1-31}-{2-9,12,13,16-21}-{15,9,13,17,21,25,29,33,37,41,45,49,53,57,61}
10}-{1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,
61}

OC-192 on a 10 10G
OC192STS3C-{1}-{1-31}-{1-16,33-48}-{1-10}{1-64}
OC192STS3C-{1}-{1-31}-{2-9,12,13,16-21}-{110}-{1-64}

OC-192 on a 10 10G
OC192STS1-{1}-{1-31}-{1-16,33-48}-{1-10}-{164}-{1-3}
OC192STS1-{1}-{1-31}-{2-9,12,13,16-21}-{110}-{1-64}-{1-3}
OC and STm ports
....................................................................................................................................................................................................................................
1830 PSS
5-555
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
STM-1 port on a
24 Multirate ANY
client port card
STM1-{1}-{1-31}-{1-16,33-48}-{1-24}
STM1-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
STM-4 port on a
24 Multirate ANY
client port card
STM4-{1}-{1-31}-{1-16,33-48}-{1-24}
STM4-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
STM-16 port on a
24 Multirate ANY
client port card
STM16-{1}-{1-31}-{1-16,33-48}-{1-24}
STM16-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
AU4 mapped into an

STM-16 port on a
24 Multirate ANY
client port card
STM16AU4-{1}-{1-31}-{1-16,33-48}-{1-24}-{116}
STM16AU4-{1}-{1-31}-{2-9,12,13,16-21}-{124}-{1-16}
AU4-4C mapped into an

STM-16 port on a
24 Multirate ANY
client port card
STM16AU44C-{1}-{1-31}-{1-16,33-48}-{1-24}-{1, STM16AU44C-{1}-{1-31}-{2-9,12,13,16-21}-{1,5,
5,9,13}
9,13}-{1-16}
AU4-16C mapped into

an STM-16 port on a
24 Multirate ANY
client port card
STM16AU416C-{1}-{1-31}-{1-16,33-48}-{1-24}{1}
STM16AU416C-{1}-{1-31}-{2-9,12,13,16-21}-{124}-{1}
STM-64 port on a
10 10G ANY client
port card
STM64-{1}-{1-31}-{1-16,33-48}-{1-10}
STM64-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
AU4 mapped into an

STM-64 port on a
10 10G ANY client
port card
STM64AU4-{1}-{1-31}-{1-16,33-48}-{1-10}-{164}
STM64AU4-{1}-{1-31}-{2-9,12,13,16-21}-{110}-{1-64}
AU4-4C mapped into an

STM-64 port on a
10 10G ANY client
port card
STM64AU44C-{1}-{1-31}-{1-16,33-48}-{1-10}-{1, STM64AU44C-{1}-{1-31}-{2-9,12,13,16-21}-{15,9,13,17,21,25,29,33,37,41,45,49,53,57,61}
10}-{1,5,9,13,17,21,25,29,33,37,41,45,49,53,57,
61}
AU4-16C mapped into

an STM-64 port on a
10 10G ANY client
port card
STM64AU416C-{1}-{1-31}-{1-16,33-48}-{1-10}{1,17,33,49}
STM64AU416C-{1}-{1-31}-{2-9,12,13,16-21}-{110}-{1,17,33,49}
STM-64 port on a
4 10G ANY client port
card
STM64-{1}-{1-31}-{1-16,33-48}-{1-4}
STM64-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
OTU-{1}-{1-31}-{1-16,33-48}-{1,2}
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1,2}
OTN
OTU3 on a 2 40G
....................................................................................................................................................................................................................................
1830 PSS
5-556
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
OTU4 on a 1 100G
Switchponder 130SCUP
/ 1x100G Switchponder
Test Board 112CFPTB
OTU-{1}-{1-31}-{2-7,9-15,33-39,41-47}-{1}
OTU-{1}-{1-31}-{2-8,12,16-20}-{1}
OTU3E2 on a 1 43G
Switchponder 43SCUP
OTU-{1}-{1-31}-{2-7,9-15,33-39,41-47}-{1}
OTU-{1}-{1-31}-{2-8,12,16-20}-{1}
OTU2 on a 4 11G
Switchponder 11QCUP
OTU-{1}-{1-31}-{2-16,33-48}-{1-4}
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
OTU2 on a 4 10G
OTU-{1}-{1-31}-{1-16,33-48}-{1-4}
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
OTU2E on a 4 10G
OTU-{1}-{1-31}-{1-16,33-48}-{1-4}
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
OTU2 on a 10 10G
OTU-{1}-{1-31}-{1-16,33-48}-{1-10}
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
OTU2E on a 10 10G
OTU-{1}-{1-31}-{1-16,33-48}-{1-10}
OTU-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
Optical channel (OCh)

on a 2 40G ANY client
port card
OCH-{1}-{1-31}-{1-16,33-48}-{1,2}
OCH-{1}-{1-31}-{2-9,12,13,16-21}-{1,2}

on a 10 10G ANY
client port card
OCH-{1}-{1-31}-{1-16,33-48}-{1-10}
OCH-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}

port card
OCH-{1}-{1-31}-{1-16,33-48}-{1-4}
OCH-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}

on a 1 43G
Switchponder 43SCUP
OCH-{1}-{1-31}-{2-7,9-15,33-39,41-47}-{1}
OCH-{1}-{1-31}-{2-8,12,16-20}-{1}

on a 1 100G
Test Board 112CFPTB
OCH-{1}-{1-31}-{2-7,9-15,33-39,41-47}-{1}
OCH-{1}-{1-31}-{2-8,12,16-20}-{1}

on a 4 11G
Switchponder 11QCUP
OCH-{1}-{1-31}-{2-16,33-48}-{1-4}
OCH-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
Higher order ODU2

NIM on a 4 10G ANY
client port card
OTUODU2-{1}-{1-31}-{1-16,33-48}-{1-4}
OTUODU2-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
Higher order ODU2

NIM on a 10 10G
OTUODU2-{1}-{1-31}-{1-16,33-48}-{1-10}
OTUODU2-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
....................................................................................................................................................................................................................................
1830 PSS
5-557
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
Higher order ODU2E

NIM on a 4 10G ANY
client port card
OTUODU2E-{1}-{1-31}-{1-16,33-48}-{1-4}
OTUODU2E-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
Higher order ODU2E

NIM on a 10 10G
OTUODU2E-{1}-{1-31}-{1-16,33-48}-{1-10}
OTUODU2E-{1}-{1-31}-{2-9,12,13,16-21}-{110}
Higher order ODU3

NIM on a 2 40G ANY
client port card
OTUODU3-{1}-{1-31}-{1-16,33-48}-{1,2}
OTUODU3-{1}-{1-31}-{2-9,12,13,16-21}-{1,2}
Higher order ODU3E2

NIM on a 1 43G
Switchponder 43SCUP
OTUODU3E2-{1}-{1-31}-{2-7,9-15,33-39,41-47}{1}
OTUODU3E2-{1}-{1-31}-{2-8,12,16-20}-{1}
Higher order ODU4

NIM on a 1 100G
Test Board 112CFPTB
OTUODU4-{1}-{1-31}-{2-7,9-15,33-39,41-47}{1}
OTUODU4-{1}-{1-31}-{2-8,12,16-20}-{1}
Lower order ODU3

NIM embedded in
ODU4
ODU4ODU3-{1}-{1-31}-{33-39,41-47}-{1}-{180}
ODU4ODU3-{1}-{1-31}-{2-8,12,16-20}-{1}{180}
Lower order ODU3

NIM embedded in
ODU3E2
ODU3E2ODU3-{1}-{1-31}-71-{1-64}-{1-32}
ODU3E2ODU3-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU2E

NIM embedded in
ODU4
ODU4ODU2E-{1}-{1-31}-71-{1-32}-{1-80}
ODU3E2ODU2E-{1}-{1-31}-71-{1-16}-{1-80}
Lower order ODU2E

NIM embedded in
ODU3E2
ODU3E2ODU2E-{1}-{1-31}-71-{1-64}-{1-32}
ODU3E2ODU2E-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU0

NIM embedded in
ODU3E2
ODU3E2ODU0-{1}-{1-31}-71-{1-64}-{1-32}
ODU3ODU0-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU2E

NIM embedded in
ODU3
ODU3ODU2E-{1}-{1-31}-71-{1-64}-{1-32}
ODU3ODU2E-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU2

NIM embedded in
ODU4
ODU4ODU2-{1}-{1-31}-71-{1-32}-{1-80}
ODU4ODU2-{1}-{1-31}-71-{1-16}-{1-80}
Lower order ODU2

NIM embedded in
ODU3E2
ODU3E2ODU2-{1}-{1-31}-71-{1-64}-{1-32}
ODU3E2ODU2-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU2

NIM embedded in
ODU3
ODU3ODU2-{1}-{1-31}-71-{1-64}-{1-32}
ODU3ODU2-{1}-{1-31}-71-{1-32}-{1-32}
....................................................................................................................................................................................................................................
1830 PSS
5-558
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
Lower order ODU1

NIM embedded in
ODU4
ODU4ODU1-{1}-{1-31}-71-{1-32}-{1-80}
ODU4ODU1-{1}-{1-31}-71-{1-16}-{1-80}
Lower order ODU1

NIM embedded in
ODU3E2
ODU3E2ODU1-{1}-{1-31}-71-{1-64}-{1-32}
ODU3E2ODU1-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU1

NIM embedded in
ODU3
ODU3ODU1-{1}-{1-31}-71-{1-64}-{1-32}
ODU3ODU1-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU0

NIM embedded in
ODU4
ODU4ODU0-{1}-{1-31}-71-{1-32}-{1-80}
ODU4ODU0-{1}-{1-31}-71-{1-16}-{1-80}
Lower order ODU0

NIM embedded in
ODU3E2
ODU3E2ODU0-{1}-{1-31}-71-{1-64}-{1-32}
ODU3E2ODU0-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU0

NIM embedded in
ODU3
ODU3ODU0-{1}-{1-31}-71-{1-64}-{1-32}
ODU3ODU0-{1}-{1-31}-71-{1-32}-{1-32}
Lower order ODU1

NIM embedded in
ODU2
ODU2ODU1-{1}-{1-31}-71-{1-384}-{1-8}
ODU2ODU1-{1}-{1-31}-71-{1-192}-{1-8}
Lower order ODU0

NIM embedded in
ODU2
ODU2ODU0-{1}-{1-31}-71-{1-384}-{1-8}
ODU2ODU0-{1}-{1-31}-71-{1-192}-{1-8}
Lower order ODU2

NIM in ODU3 on Preset
AID plane
ODU3ODU2-{1}-{1-31}-72-{101-4802}-{1-4}
ODU3ODU2-{1}-{1-31}-72-{201-2102}-{1-4}
Lower order ODU1

AID plane
ODU3ODU1-{1}-{1-31}-72-{101-4802}-{1-16}
ODU3ODU1-{1}-{1-31}-72-{201-2102}-{1-16}
Lower order ODU0

AID plane
ODU3ODU0-{1}-{1-31}-72-{101-4802}-{1-32}
ODU3ODU0-{1}-{1-31}-72-{201-2102}-{1-32}
Lower order ODU1

AID plane
ODU2ODU1-{1}-{1-31}-72-{101-4810}-{1-4}
ODU2ODU1-{1}-{1-31}-72-{201-2110}-{1-4}
Lower order ODU0

AID plane
ODU2ODU0-{1}-{1-31}-72-{101-4810}-{1-8}
ODU2ODU0-{1}-{1-31}-72-{201-2110}-{1-8}
ODU4 termination
ODU4-{1}-{1-31}-71-{1-32}
ODU4-{1}-{1-31}-71-{1-16}
ODU4 termination on
Preset AID plane
ODU4-{1}-{1-31}-72-{33-39,41-47}{01}
ODU4-{1}-{1-31}-72-{2-8,12,16-20}{01}
ODU3E2 termination
ODU3E2-{1}-{1-31}-71-{1-64}
ODU3E2-{1}-{1-31}-71-{1-32}
....................................................................................................................................................................................................................................
1830 PSS
5-559
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
ODU3E2 termination on
Preset AID plane
ODU3E2-{1}-{1-31}-72-{2-7,9-15,33-39,41-47}
{01}
ODU3E2-{1}-{1-31}-72-{2-8,12,16-20}{01}
ODU3 termination
ODU3-{1}-{1-31}-71-{1-64}
ODU3-{1}-{1-31}-71-{1-32}
ODU2 termination
ODU2-{1}-{1-31}-71-{1-384}
ODU2-{1}-{1-31}-71-{1-192}
ODU3 termination on
Preset AID plane
ODU3-{1}-{1-31}-72-{101-4802}{01,02}
ODU3-{1}-{1-31}-72-{201-2102}{01,02}
ODU2 termination on
Preset AID plane
ODU2-{1}-{1-31}-72-{1-16,33-48}
{01,02,03,04,05,06,07,08,09,1 0}
ODU2-{1}-{1-31}-72-{2-9,12,13,16-21}
{01,02,03,04,05,06,07,08,09,1 0}
Transparent mapping
ODU2E on a 4 10G
ODU2E-{1}-{1-31}-{1-16,33-48}-{1-4}
ODU2E-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
Transparent mapping
ODU2E on a 10 10G
ODU2E-{1}-{1-31}-{1-16,33-48}-{1-10}
ODU2E-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
Transparent mapping
ODU2 on a 4 10G
ODU2-{1}-{1-31}-{1-16,33-48}-{1-4}
ODU2-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
Transparent mapping
ODU2 on a 10 10G
ODU2-{1}-{1-31}-{1-16,33-48}-{1-10}
ODU2-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
Transparent mapping
ODU1 on a
24 Multirate ANY
client port card
ODU1-{1}-{1-31}-{1-16,33-48}-{1-24}
ODU1-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
Transparent mapping
ODU0 on a
24 Multirate ANY
client port card
ODU0-{1}-{1-31}-{1-16,33-48}-{1-24}
ODU0-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
Transparent mapping
ODU0 on a
8 Multirate ANY
client port card
ODU0-{1}-{1-31}-{1-16,33-48}-{1-8}
ODU0-{1}-{1-31}-{2-9,12,13,16-21}-{1-8}
TCM NIM at higher

order ODU4 NIM on a1
100G Switchponder
130SCUP / 1x100G
Switchponder Test
Board 112CFPTB
OTUODU4TCN-{1}-{1-31}-{2-7,9-15,33-39,4147}-{1}-{1-6}-{AM,BM}
OTUODU3E2TCN-{1}-{1-31}-{2-8,12,16-20}{1}-{1-6}-{AM,BM}
TCM NIM at higher

order ODU3E2 NIM on
a 1 43G Switchponder
43SCUP card
OTUODU3E2TCN-{1}-{1-31}-{2-7,9-15,33-39,
41-47}-{1}-{1-6}-{AM,BM}
OTUODU3E2TCN-{1}-{1-31}-{2-9,12,13,16-21}{1}-{1-6}-{AM,BM}
....................................................................................................................................................................................................................................
1830 PSS
5-560
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM NIM at higher

order ODU3 NIM on a
card
OTUODU3TCN-{1}-{1-31}-{1-16,33-48}-{1,2}{1-6}-{AM,BM}
OTUODU3TCN-{1}-{1-31}-{2-9,12,13,16-21}-{1,
2}-{1-6}-{AM,BM}
TCM NIM at higher

order ODU2E NIM on a
card
OTUODU2ETCN-{1}-{1-31}-{1-16,33-48}-{1-4}{1-6}-{AM,BM}
OTUODU2ETCN-{1}-{1-31}-{2-9,12,13,16-21}{1-4}-{1-6}-{AM,BM}
TCM NIM at higher

order ODU2E NIM on a
10 10G ANY client
port card
OTUODU2ETCN-{1}-{1-31}-{1-16,33-48}-{110}-{1-6}-{AM,BM}
OTUODU2ETCN-{1}-{1-31}-{2-9,12,13,16-21}{1-10}-{1-6}-{AM,BM}
TCM NIM at higher

order ODU2 NIM on a
card
OTUODU2TCN-{1}-{1-31}-{1-16,33-48}-{1-4}{1-6}-{AM,BM}
OTUODU2TCN-{1}-{1-31}-{2-9,12,13,16-21}{1-4}-{1-6}-{AM,BM}
TCM NIM at higher

order ODU2 NIM on a
10 10G ANY client
port card
OTUODU2TCN-{1}-{1-31}-{1-16,33-48}-{1-10}{1-6}-{AM,BM}
OTUODU2TCN-{1}-{1-31}-{2-9,12,13,16-21}{1-10}-{1-6}-{AM,BM}
TCM NIM at lower

order ODU2E NIM
which is contained in
ODU3E2 on virtual
plane
ODU3E2ODU2ETCN-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
TCM NIM at lower

order ODU3 NIM which
is contained in ODU4 on
virtual plane
ODU4ODU3TCN-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU3TCN-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM NIM at lower

is contained in ODU3E2
on virtual plane
ODU3E2ODU3TCN-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU3TCN-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM NIM at lower

order ODU2E NIM
ODU4 on virtual plane
ODU4ODU2ETCN-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU2ETCN-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM NIM at lower

order ODU2E NIM
ODU3E2 on virtual
plane
TCM NIM at lower

on virtual plane
ODU3E2ODU2TCN-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU2TCN-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
....................................................................................................................................................................................................................................
1830 PSS
5-561
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM NIM at lower

order ODU2E NIM
ODU3ODU2ETCN-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU2TCN-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
TCM NIM at lower

virtual plane
ODU4ODU2TCN-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU2TCN-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM NIM at lower

on virtual plane
ODU3E2ODU2TCN-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU2TCN-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM NIM at lower

virtual plane
ODU3ODU2TCN-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU2TCN-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
TCM NIM at lower

virtual plane
ODU4ODU1TCN-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU1TCN-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM NIM at lower

virtual plane
ODU3ODU1TCN-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU1TCN-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
TCM NIM at lower

on virtual plane
ODU3E2ODU1TCN-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU1TCN-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM NIM at lower

virtual plane
ODU4ODU0TCN-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU0TCN-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM NIM at lower

on virtual plane
ODU3E2ODU0TCN-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU0TCN-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM NIM at lower

virtual plane
ODU3ODU0TCN-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU0TCN-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
(TCM NIM at lower

virtual plane
ODU2ODU1TCN-{1}-{1-31}-71-{1-384}-{1-8}{1-6}-{AM,BM}
ODU2ODU1TCN-{1}-{1-31}-71-{1-192}-{1-8}{1-6}-{AM,BM}
....................................................................................................................................................................................................................................
1830 PSS
5-562
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM NIM at lower

virtual plane
ODU2ODU0TCN-{1}-{1-31}-71-{1-384}-{1-8}{1-6}-{AM,BM}
ODU2ODU0TCN-{1}-{1-31}-71-{1-192}-{1-8}{1-6}-{AM,BM}
TCM NIM at ODU4

Termination on virtual
plane
ODU4TCN-{1}-{1-31}-71-{1-32}-{1-6}-AM
ODU4TCN-{1}-{1-31}-71-{1-16}-{1-6}-AM
TCM NIM at ODU3E2

plane
ODU3E2TCN-{1}-{1-31}-71-{1-64}-{1-6}-AM
ODU3E2TCN-{1}-{1-31}-71-{1-32}-{1-6}-AM
TCM NIM at ODU3

plane
ODU3TCN-{1}-{1-31}-71-{1-64}-{1-6}-AM
ODU3TCN-{1}-{1-31}-71-{1-32}-{1-6}-AM
TCM NIM at ODU2

plane
ODU2TCN-{1}-{1-31}-71-{1-384}-{1-6}-AM
ODU2TCN-{1}-{1-31}-71-{1-192}-{1-6}-AM
TCM Termination at
lower order ODU3 NIM
ODU4 on preset plane
ODU4ODU3TCN-{1}-{1-31}-72-{33-39,41-47}{1-80}-{1-6}-{AM,BM}
ODU4ODU3TCN-{1}-{1-31}-72-{2-8,12,16-20}{1-80}-{1-6}-{AM,BM}
TCM NIM at lower

on preset plane
ODU3E2ODU3TCN-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU3TCN-{1}-{1-31}-2-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM Termination at
lower order ODU2E
NIM which is contained
in ODU4 on preset plane
ODU4ODU2ETCN-{1}-{1-31}-72-{33-39,41-47}{1-80}-{1-6}-{AM,BM}
ODU4ODU2ETCN-{1}-{1-31}-72-{2-8,12,1620}-{1-80}-{1-6}-{AM,BM}
TCM NIM at lower

order ODU2E NIM
ODU3E2 on preset
plane
ODU3E2ODU2ETCN-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU2ETCN-{1}-{1-31}-2-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM NIM at lower

order ODU2E NIM
ODU3ODU2ETCN-{1}-{1-31}-72-{101-4802}-{132}-{1-6}-{AM,BM}
ODU3ODU2ETCN-{1}-{1-31}-2-{201-2102}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU4ODU2TCN-{1}-{1-31}-72-{33-39,41-47}{1-80}-{1-6}-{AM,BM}
ODU4ODU2TCN-{1}-{1-31}-72-{2-8,12,16-20}{1-80}-{1-6}-{AM,BM}
TCM NIM at lower

on preset plane
ODU3E2ODU2TCN-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU2TCN-{1}-{1-31}-2-{201-2102}{1-32}-{1-6}-{AM,BM}
....................................................................................................................................................................................................................................
1830 PSS
5-563
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM NIM at lower

preset plane
ODU3ODU2TCN-{1}-{1-31}-72-{101-4802}-{14}-{1-6}-{AM,BM}
ODU3ODU2TCN-{1}-{1-31}-72-{201-2102}-{14}-{1-6}-{AM,BM}
TCM NIM at lower

preset plane
ODU3ODU1TCN-{1}-{1-31}-72-{101-4802}-{116}-{1-6}-{AM,BM}
ODU3ODU1TCN-{1}-{1-31}-72-{201-2102}-{116}-{1-6}-{AM,BM}
TCM Termination at
ODU4ODU1TCN-{1}-{1-31}-72-{33-39,41-47}{1-80}-{1-6}-{AM,BM}
ODU4ODU1TCN-{1}-{1-31}-72-{2-8,12,16-20}{1-80}-{1-6}-{AM,BM}
TCM NIM at lower

on preset plane
ODU3E2ODU1TCN-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU1TCN-{1}-{1-31}-72-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM Termination at
ODU4ODU0TCN-{1}-{1-31}-72-{33-39,41-47}{1-80}-{1-6}-{AM,BM}
ODU4ODU0TCN-{1}-{1-31}-72-{2-8,12,16-20}{1-80}-{1-6}-{AM,BM}
TCM NIM at lower

on preset plane
ODU3E2ODU0TCN-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU0TCN-{1}-{1-31}-72-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM NIM at lower

preset plane
ODU3ODU0TCN-{1}-{1-31}-72-{101-4802}-{132}-{1-6}-{AM,BM}
ODU3ODU0TCN-{1}-{1-31}-72-{201-2102}-{132}-{1-6}-{AM,BM}
(TCM NIM at lower

preset plane
ODU2ODU1TCN-{1}-{1-31}-72-{101-4810}-{18}-{1-6}-{AM,BM}
ODU2ODU1TCN-{1}-{1-31}-72-{201-2110}-{184}-{1-6}-{AM,BM}
TCM NIM at lower

preset plane
ODU2ODU0TCN-{1}-{1-31}-72-{101-4810}-{18}-{1-6}-{AM,BM}
ODU2ODU0TCN-{1}-{1-31}-72-{201-2110}-{18}-{1-6}-{AM,BM}
TCM NIM at ODU3

Termination on preset
plane
ODU3TCN-{1}-{1-31}-72-{101-4802}-{1-6}-AM
ODU3TCN-{1}-{1-31}-72-{201-2102}-{1-6}-AM
TCM NIM at ODU2

Termination on preset
plane
ODU2TCN-{1}-{1-31}-72-{101-4810}-{1-6}-AM
ODU2TCN-{1}-{1-31}-72-{201-2110}-{1-6}-AM
....................................................................................................................................................................................................................................
1830 PSS
5-564
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM NIM at transparent

mapping ODU2E
Termination on a
10 10G ANY client
port card
ODU2ETCN-{1}-{1-31}-{1-16,33-48}-{1-10}-{16}-AM
ODU2ETCN-{1}-{1-31}-{2-9,12,13,16-21}-{110}-{1-6}-AM

mapping ODU2E
Termination on a
card
ODU2ETCN-{1}-{1-31}-{1-16,33-48}-{1-4}-{16}-AM
ODU2ETCN-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}{1-6}-AM

mapping ODU2
Termination on a
card
ODU2TCN-{1}-{1-31}-{1-16,33-48}-{1-4}-{16}-AM
ODU2TCN-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}{1-6}-AM

mapping ODU1
Termination on a
24 Multirate ANY
client port card
ODU1TCN-{1}-{1-31}-{1-16,33-48}-{1-24}-{16}-AM
ODU1TCN-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}{1-6}-AM

mapping ODU0
Termination on a
24 Multirate ANY
client port card
ODU0TCN-{1}-{1-31}-{1-16,33-48}-{1-24}-{16}-AM
ODU0TCN-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}{1-6}-AM

mapping ODU0
Termination on a
8 Multirate ANY
client port card
ODU0TCN-{1}-{1-31}-{1-16,33-48}-{1-24}-{16}-AM
ODU0TCN-{1}-{1-31}-{2-9,12,13,16-21}-{1-8}{1-6}-AM
TCM Termination at
higher order ODU3 NIM
port card
OTUODU3TCT-{1}-{1-31}-{1-16,33-48}-{1,2}{1-6}-{AM,BM}
OTUODU3TCT-{1}-{1-31}-{2-9,12,13,16-21}-{1,
2}-{1-6}-{AM,BM}
TCM Termination at
on a 1 100G
Test Board 112CFPTB
OTUODU4TCT-{1}-{1-31}-{2-7,9-15,33-39,4147}-{1}-{1-6}-{AM,BM}
OTUODU4TCT-{1}-{1-31}-{2-8,12,16-20}-{1}{1-6}-{AM,BM}
TCM Termination at
higher order ODU3E2
NIM on a 1 43G
Switchponder 43SCUP
card
OTUODU3E2TCT-{1}-{1-31}-{2-7,9-15,33-39,4147}-{1}-{1-6}-{AM,BM}
OTUODU3E2TCT-{1}-{1-31}-{2-9,12,13,16-21}{1}-{1-6}-{AM,BM}
....................................................................................................................................................................................................................................
1830 PSS
5-565
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM Termination at
higher order ODU2E
NIM on a 4 10G ANY
client port card
OTUODU2ETCT-{1}-{1-31}-{1-16,33-48}-{1-4}{1-6}-{AM,BM}
OTUODU2ETCT-{1}-{1-31}-{2-9,12,13,16-21}{1-4}-{1-6}-{AM,BM}
TCM Termination at
higher order ODU2E
NIM on a 10 10G
OTUODU2ETCT-{1}-{1-31}-{1-16,33-48}-{110}-{1-6}-{AM,BM}
OTUODU2ETCT-{1}-{1-31}-{2-9,12,13,16-21}{1-10}-{1-6}-{AM,BM}
TCM Termination at
port card
OTUODU2TCT-{1}-{1-31}-{1-16,33-48}-{1-4}{1-6}-{AM,BM}
OTUODU2TCT-{1}-{1-31}-{2-9,12,13,16-21}-{14}-{1-6}-{AM,BM}
TCM Termination at
on a 10 10G ANY
client port card
OTUODU2TCT-{1}-{1-31}-{1-16,33-48}-{1-10}{1-6}-{AM,BM}
OTUODU2TCT-{1}-{1-31}-{2-9,12,13,16-21}-{110}-{1-6}-{AM,BM}
TCM Termination at
ODU4ODU3TCT-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU3TCT-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM Termination at
ODU3E2 on virtual
plane
ODU3E2ODU3TCT-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU3TCT-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM Termination at
lower order ODU2E
in ODU4 on virtual
plane
ODU4ODU2ETCT-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU2ETCT-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM Termination at
lower order ODU2E
in ODU3E2 on virtual
plane
ODU3E2ODU2ETCT-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU2ETCT-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM Termination at
lower order ODU2E
in ODU3 on virtual
plane
ODU3ODU2ETCT-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU2ETCT-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
TCM Termination at
ODU4ODU2TCT-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU2TCT-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
....................................................................................................................................................................................................................................
1830 PSS
5-566
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM Termination at
ODU3E2 on virtual
plane
ODU3E2ODU2TCT-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU2TCT-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU3ODU2TCT-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU2TCT-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
TCM Termination at
ODU4ODU1TCT-{1}-{1-31}-71-{1-32}-{1-80}{1-6}-{AM,BM}
ODU4ODU1TCT-{1}-{1-31}-71-{1-16}-{1-80}{1-6}-{AM,BM}
TCM Termination at
ODU3E2 on virtual
plane
ODU3E2ODU1TCT-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU1TCT-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU3ODU1TCT-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU1TCT-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
TCM Termination at
ODU3E2 on virtual
plane
ODU3E2ODU0TCT-{1}-{1-31}-71-{1-64}-{132}-{1-6}-{AM,BM}
ODU3E2ODU0TCT-{1}-{1-31}-71-{1-32}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU3ODU0TCT-{1}-{1-31}-71-{1-64}-{1-32}{1-6}-{AM,BM}
ODU3ODU0TCT-{1}-{1-31}-71-{1-32}-{1-32}{1-6}-{AM,BM}
TCM Termination at
ODU2ODU1TCT-{1}-{1-31}-71-{1-384}-{1-4}{1-6}-{AM,BM}
ODU2ODU1TCT-{1}-{1-31}-71-{1-192}-{1-4}{1-6}-{AM,BM}
TCM Termination at
ODU2ODU0TCT-{1}-{1-31}-71-{1-384}-{1-8}{1-6}-{AM,BM}
ODU2ODU0TCT-{1}-{1-31}-71-{1-192}-{1-8}{1-6}-{AM,BM}
TCM Termination at
ODU4 Termination on
virtual plane
ODU4TCT-{1}-{1-31}-71-{1-64}-{1-6}-AM
ODU4TCT-{1}-{1-31}-71-{1-32}-{1-6}-AM
TCM Termination at
ODU3E2 Termination
on virtual plane
ODU3E2TCT-{1}-{1-31}-71-{1-64}-{1-6}-AM
ODU3E2TCT-{1}-{1-31}-71-{1-32}-{1-6}-AM
....................................................................................................................................................................................................................................
1830 PSS
5-567
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM Termination at
ODU3 Termination on
virtual plane
ODU3TCT-{1}-{1-31}-71-{1-64}-{1-6}-AM
ODU3TCT-{1}-{1-31}-71-{1-32}-{1-6}-AM
TCM Termination at
ODU2 Termination on
virtual plane
ODU2TCT-{1}-{1-31}-71-{1-64}-{1-6}-AM
ODU2TCT-{1}-{1-31}-71-{1-32}-{1-6}-AM
TCM Termination at
ODU3E2 on preset
plane
ODU3E2ODU3TCT-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU3TCT-{1}-{1-31}-72-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM Termination at
lower order ODU2E
in ODU3E2 on preset
plane
ODU3E2ODU2ETCT-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU2ETCT-{1}-{1-31}-72-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM Termination at
lower order ODU2E
in ODU3 on preset plane
ODU3ODU2ETCT-{1}-{1-31}-72-{101-4802}-{132}-{1-6}-{AM,BM}
ODU3ODU2ETCT-{1}-{1-31}-72-{201-2102}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU3E2 on preset
plane
ODU3E2ODU2TCT-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU2TCT-{1}-{1-31}-72-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM Termination at
ODU3ODU2TCT-{1}-{1-31}-72-{101-4802}-{132}-{1-6}-{AM,BM}
ODU3ODU2TCT-{1}-{1-31}-72-{201-2102}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU3E2 on preset
plane
ODU3E2ODU1TCT-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU1TCT-{1}-{1-31}-72-{201-2102}{1-32}-{1-6}-{AM,BM}
TCM Termination at
ODU3ODU1TCT-{1}-{1-31}-72-{101-4802}-{132}-{1-6}-{AM,BM}
ODU3ODU1TCT-{1}-{1-31}-72-{201-2102}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU4ODU0TCT-{1}-{1-31}-72-{33-39,41-47}{1-80}-{1-6}-{AM,BM}
ODU4ODU0TCT-{1}-{1-31}-72-{2-8,12,16-20}{1-80}-{1-6}-{AM,BM}
TCM Termination at
ODU3E2 on preset
plane
ODU3E2ODU0TCT-{1}-{1-31}-72-{101-4802}{1-32}-{1-6}-{AM,BM}
ODU3E2ODU0TCT-{1}-{1-31}-72-{201-2102}{1-32}-{1-6}-{AM,BM}
....................................................................................................................................................................................................................................
1830 PSS
5-568
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM Termination at
ODU3ODU0TCT-{1}-{1-31}-72-{101-4802}-{132}-{1-6}-{AM,BM}
ODU3ODU0TCT-{1}-{1-31}-72-{201-2102}-{132}-{1-6}-{AM,BM}
TCM Termination at
ODU2ODU1TCT-{1}-{1-31}-72-{101-4810}-{18}-{1-6}-{AM,BM}
ODU2ODU1TCT-{1}-{1-31}-72-{201-2110}-{18}-{1-6}-{AM,BM}
TCM Termination at
ODU2ODU0TCT-{1}-{1-31}-72-{101-4810}-{18}-{1-6}-{AM,BM}
ODU2ODU0TCT-{1}-{1-31}-72-{201-2110}-{18}-{1-6}-{AM,BM}
TCM Termination at
ODU4 Termination on
preset plane
ODU4TCT-{1}-{1-31}-72-{33-39,41-47}-{0-1}{1-6}-{AM}
ODU4TCT-{1}-{1-31}-72-{2-8,12,16-20}-{0-1}{1-6}-{AM}
TCM Termination at
ODU3E2 Termination
on preset plane
ODU3TCT-{1}-{1-31}-72-{101-4802}-{1-6}-AM
ODU3TCT-{1}-{1-31}-72-{201-2102}-{1-6}-AM
TCM Termination at
ODU3 Termination on
preset plane
ODU3TCT-{1}-{1-31}-72-{101-4802}-{1-6}-AM
ODU3TCT-{1}-{1-31}-72-{201-2102}-{1-6}-AM
TCM Termination at
ODU2 Termination on
preset plane
ODU2TCT-{1}-{1-31}-72-{101-4802}-{1-6}-AM
ODU2TCT-{1}-{1-31}-72-{201-2102}-{1-6}-AM
TCM Termination at
transparent mapping
ODU2E Termination on
a 10 10G ANY client
port card
ODU2ETCT-{1}-{1-31}-{1-16,33-48}-{1-10}-{16}-AM
ODU2ETCT-{1}-{1-31}-{2-9,12,13,16-21}-{110}-{1-6}-AM
TCM Termination at
transparent mapping
ODU2E Termination on
a 4 10G ANY client
port card
ODU2ETCT-{1}-{1-31}-{1-16,33-48}-{1-4}-{16}-AM
ODU2ETCT-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}{1-6}-AM
TCM Termination at
transparent mapping
ODU2 Termination on a
10 10G ANY client
port card
ODU2TCT-{1}-{1-31}-{1-16,33-48}-{1-10}-{16}-AM
ODU2TCT-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}{1-6}-AM
TCM Termination at
transparent mapping
card
ODU2TCT-{1}-{1-31}-{1-16,33-48}-{1-4}-{16}-AM
ODU2TCT-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}{1-6}-AM
....................................................................................................................................................................................................................................
1830 PSS
5-569
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-19
(continued)
Facility
TCM Termination at
transparent mapping
24 Multirate ANY
client port card
ODU1TCT-{1}-{1-31}-{1-16,33-48}-{1-24}-{16}-AM
ODU1TCT-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}{1-6}-AM
TCM Termination at
transparent mapping
24 Multirate ANY
client port card
ODU0TCT-{1}-{1-31}-{1-16,33-48}-{1-24}-{16}-AM
ODU0TCT-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}{1-6}-AM
TCM Termination at
transparent mapping
8 Multirate ANY
client port card
ODU0TCT-{1}-{1-31}-{1-16,33-48}-{1-8}-{16}-AM
ODU0TCT-{1}-{1-31}-{2-9,12,13,16-21}-{1-8}{1-6}-AM
ODU pool for all ODU

terminations on virtual
ODU planes within a
shelf
ODUPOOL-{1}-{1-31}-1
ODUPOOL-{1}-{1-31}-1
GbE port on a
24 Multirate ANY
client port card
GBE-{1}-{1-31}-{1-16,33-48}-{1-24}
GBE-{1}-{1-31}-{2-9,12,13,16-21}-{1-24}
GbE port on a
8 Multirate ANY
client port card
GBE-{1}-{1-31}-{1-16,33-48}-{1-8}
GBE-{1}-{1-31}-{2-9,12,13,16-21}-{1-8}
10 GbE port on a
card
GBE10-{1}-{1-31}-{1-16,33-48}-{1-4}
GBE10-{1}-{1-31}-{2-9,12,13,16-21}-{1-4}
10 GbE port on a
10 10G ANY client
port card
GBE10-{1}-{1-31}-{1-16,33-48}-{1-10}
GBE10-{1}-{1-31}-{2-9,12,13,16-21}-{1-10}
OTS at SFC8
Mux/Demux Port
OTS-1-{1}-{1-31}-OMD
OTS-1-{1}-{1-31}-OMD
OMSOCH at SFC8
Mux/Demux port
GBE10-{1}-{1-31}-{1-16,33-48}-{1-10}
OMSOCH-1-{1}-{1-31}-OMD-{1471, 1491, 1511,

1531, 1551, 1571, 1591, 1611}
OMSOCHIF at SFC8
Optical Channel I/O
ports
OMSOCHIF-1-{1}-{1-31}-{1471, 1491, 1511,

1531, 1551, 1571, 1591, 1611}
Gigabit Ethernet
Optical Linet
OMSOCH-1-{1}-{1-31}-OMD-{1471, 1491, 1511,

1531, 1551, 1571, 1591, 1611}
OMSOCHIF-1-{1}-{1-31}-{1471, 1491, 1511,

1531, 1551, 1571, 1591, 1611}
....................................................................................................................................................................................................................................
1830 PSS
5-570
Issue 1 June 2013

....................................................................................................................................................................................................................................
The following table provides an overview of timing reference AIDs:

Table 5-20
Component
Access identifier
Timing node within a shelf
SYNC-{1}-{1-31}-0
External timing input port of a shelf
BITS-{1}-{1-31}-{0,1}
ASAP (Alarm Severity Assigned Profile) AIDs
The general ASAP AID format is as follows:
ASAP name - ASAP index#
where:
ASAP name represents the name of the respective type of ASAP.
ASAP index# represents the number of the ASAP instance for that type of ASAP.
Note: The ASAP index values 0 and 1 or 0-4, depending on the ASAP type, are
related to the system-defined ASAPs (null and factory default ASAPs), while the
other index values correspond to user-defined ASAPs.
Table 5-21
Alarm severity assigned profile
Access identifier
System-defined EQPT ASAP
ASAPEQPT-{0-4}
User-defined EQPT ASAP
ASAPEQPT-{5-255}
System-defined BITS ASAP
ASAPBITS-{0-4}
User-defined BITS ASAP
ASAPBITS-{5-255}
System-defined TIMING ASAP
ASAPTIMING-{0-4}
User-defined TIMING ASAP
ASAPTIMING-{5-255}
System-defined OC3 ASAP
ASAPOC3-{0-4}
User-defined OC3 ASAP
ASAPOC3-{5-255}
ASAPOC12-{0-4}
ASAPOC12-{5-255}
ASAPOC48-{0-4}
ASAPOC48-{5-255}
ASAPOC192-{0-4}
ASAPOC192-{5-255}
....................................................................................................................................................................................................................................
1830 PSS
5-571
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-21
Access identifier
System-defined STS1 ASAP
ASAPSTS1-{0-4}
User-defined STS1 ASAP
ASAPSTS1-{5-255}
System-defined STS3C ASAP
ASAPSTS3C-{0-4}
User-defined STS3C ASAP
ASAPSTS3C-{5-255}
ASAPSTS12C-{0-4}
ASAPSTS12C-{5-255}
ASAPSTS48C-{0-4}
ASAPSTS48C-{5-255}
System-defined GBE ASAP
ASAPGBE-{0-4}
User-defined GBE ASAP
ASAPGBE-{5-255}
System-defined 10GBE ASAP
ASAPGBE10-{0-4}
User-defined 10GBE ASAP
ASAPGBE10-{5-255}
System-defined STM1 ASAP
ASAPSTM1-{0-4}
User-defined STM1 ASAP
ASAPSTM1-{5-255}
ASAPSTM4-{0-4}
ASAPSTM4-{5-255}
ASAPSTM16-{0-4}
ASAPSTM16-{5-255}
ASAPSTM64-{0-4}
ASAPSTM64-{5-255}
System-defined VC4 ASAP
ASAPVC4-{0-4}
User-defined VC4 ASAP
ASAPVC4-{5-255}
System-defined VC44C ASAP
ASAPVC44C-{0-4}
User-defined VC44C ASAP
ASAPVC44C-{5-255}
System-defined VC416C ASAP
ASAPVC416C-{0-4}
User-defined VC416C ASAP
ASAPVC416C-{5-255}
System-defined ODU4 ASAP
ASAPODU4-{0-4}
User defined ODU4 ASAP where 255 is a theoretic

limit)
ASAPODU4-{5-255}
System-defined ODU3E2 ASAP
ASAPODU3E2-{0-4}
User-defined ODU3E2 ASAP
ASAPODU3E2-{5-255}
(continued)
....................................................................................................................................................................................................................................
1830 PSS
5-572
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-21
Access identifier
ASAPODU3-{0-4}
User-defined ODU3 ASAP
ASAPODU3-{5-255}
System-defined ODU2E ASAP
ASAPODU2E-{0-4}
User-defined ODU2E ASAP
ASAPODU2E-{5-255}
ASAPODU2-{0-4}
ASAPODU2-{5-255}
ASAPODU1-{0-4}
ASAPODU1-{5-255}
ASAPODU0-{0-4}
ASAPODU0-{5-255}
System-defined TCM ASAP
ASAPTCM-{0-4}
User-defined TCM ASAP
ASAPTCM-{5-255}
System-defined OTU ASAP
ASAPOTU-{0-4}
User-defined OTU ASAP
ASAPOTU-{5-255}
System-defined OCH ASAP
ASAPOCH-{0-4}
User-defined OCH ASAP
ASAPOCH-{5-255}
System-defined OTS ASAP
ASAPOTS-{0-4}
User-defined OTS ASAP
ASAPOTS-{5-255}
System-defined OMS ASAP
ASAPOMS-{0-4}
User-defined OMS ASAP
ASAPOMS-{5-255}
System-defined SECU ASAP
ASAPSECU-{0-1}
System-defined NETIF ASAP
ASAPNETIF-{0-4}
User-defined NETIF ASAP
ASAPNETIF-{5-255}
System-defined IPIPT ASAP
ASAPIPIPT-{0-4}
User-defined IPIPT ASAP
ASAPIPIPT-{5-255}
System-defined LAN ASAP
ASAPLAN-{0-4}
User-defined LAN ASAP
ASAPLAN-{5-255}
(continued)
THP (Threshold Profile) AIDs
The general Threshold Profile AID format is as follows:
THP name - THP index#
....................................................................................................................................................................................................................................
1830 PSS
5-573
Issue 1 June 2013

....................................................................................................................................................................................................................................
where:
THP name represents the name of the respective type of THP.
THP index# represents the number of the THP instance for that type of THP.
Note: The THP index values 0 and 1 are related to the system-defined THPs (null and
factory default THPs), while the other index values correspond to user-defined THPs.
Table 5-22
Examples of THP (Threshold Profile) AIDs
Threshold profile
Access identifier
System-defined OC3 THP
THPOC3-{0-1}
User defined OC3 THP
THPOC3-{2-127}
THPOC12-{0-1}
THPOC12-{2-127}
THPOC48-{0-1}
THPOC48-{2-127}
THPOC192-{0-1}
User-defined OC192 THP
THPOC192-{2-127}
System-defined STM1 THP
THPSTM1-{0-1}
User-defined STM1 THP
THPSTM1-{2-127}
THPSTM4-{0-1}
THPSTM4-{2-127}
THPSTM16-{0-1}
THPSTM16-{2-127}
THPSTM64-{0-1}
THPSTM64-{2-127}
System-defined ODU4 THP
THPODU4-{0-1}
User-defined ODU4 THP
THPODU4-{2-127}
System-defined ODU3E2 THP
THPODU3E2-{0-1}
User-defined ODU3E2 THP
THPODU3E2-{2-127}
THPODU3-{0-1}
THPODU3-{2-127}
System-defined ODU2E THP
THPODU2E-{0-1}
User-defined ODU2E THP
THPODU2E-{2-127}
THPODU2-{0-1}
THPODU2-{2-127}
....................................................................................................................................................................................................................................
1830 PSS
5-574
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-22
Examples of THP (Threshold Profile) AIDs
(continued)
Threshold profile
Access identifier
THPODU1-{0-1}
THPODU1-{2-127}
THPODU0-{0-1}
THPODU0-{2-127}
System-defined ODU4 TCM THP
THPODU4TCM-{0-1}
User-defined ODU4 TCM THP
THPODU4TCM-{2-127}
System-defined ODU3E2 TCM THP
THPODU3E2TCM-{0-1}
User-defined ODU3E2 TCM THP
THPODU3E2TCM-{2-127}
THPODU3TCM-{0-1}
THPODU3TCM-{2-127}
System-defined ODU2E TCM THP
THPODU2ETCM-{0-1}
User-defined ODU2E TCM THP
THPODU2ETCM-{2-127}
THPODU2TCM-{0-1}
THPODU2TCM-{2-127}
THPODU1TCM-{0-1}
THPODU1TCM-{2-127}
THPODU0TCM-{0-1}
THPODU0TCM-{2-127}
System-defined OTU4 THP
THPOTU4-{0-1}
User-defined OTU4 THP
THPOTU4-{2-127}
System-defined OTU3E2 THP
THPOTU3E2-{0-1}
User-defined OTU3E2 THP
THPOTU3E2-{2-127}
THPOTU3-{0-1}
THPOTU3-{2-127}
System-defined OTU2E THP
THPOTU2E-{0-1}
User-defined OTU2E THP
THPOTU2E-{2-127}
THPOTU2-{0-1}
THPOTU2-{2-127}
Factory defined OCH THP
THPOCH-{0-1}
User defined OCH THP
THPOCH-{2-127}
....................................................................................................................................................................................................................................
1830 PSS
5-575
Issue 1 June 2013

....................................................................................................................................................................................................................................
Common AIDs
The following AIDs are common AIDs:

Table 5-23
Component
Access identifier for

Alcatel-Lucent 1830 PSS-64

The following AIDs are related to traffic bearing equipment that is not yet provisioned :
Generic Shelf AID
MDL-{1}-{1-31}
MDL-{1}-{1-31}
Generic I/O Slot AID
MDL-{1}-{1-31}-{1-64}
MDL-{1}-{1-31}-{1-32}
Generic Slot AID
MDL-{1}-{1-31}-{1-64,71-76,
81-86,91-94}
MDL-{1}-{1-31}-{1-45}
Generic SFP/XFP and

PORT AID
MDL-{1}-{1-31}-{1-16,33-48}{1-24}
MDL-{1}-{1-31}-{2-9,12,13,1621}-{1-24}
The following AID is related to the ECC network interface :

Network Interface on an
ECC protection group
NETIF-{1-512}
NETIF-{1-512}
The following AIDs are related to OSPF areas:

OSPF Area
OSPFAREA-{0-3}
OSPFAREA-{0-3}
Non Backbone OSPF

Area
OSPFAREA-{1-3}
OSPFAREA-{1-3}
The following AIDs are related to the Internet Protocol Tunnel:

Internet Protocol in
Internet Protocol
Tunnel
IPIPT-{1-64}
IPIPT-{1-64}
The following AIDs are related to the Management LAN entities:

Customer LAN
LAN-{OAMP, CIT}
LAN-{OAMP, CIT}
OAMP LAN
LAN-{OAMP}
LAN-{OAMP}
Customer LAN Port on

FLC card
LANPORT-1-<shelf>-<slot>{OAMP, CIT}
LANPORT-1-<shelf>-<slot>{OAMP, CIT}
Customer LAN Port on

main shelf FLC card)
LANPORT-1-1-<shelf>-<slot>{OAMP, CIT}
LANPORT-1-1-<shelf>-<slot>{OAMP, CIT}
MTX LAN Ports
LANPORT-1-<shelf>-<slot>-{ES1, LANPORT-1-<shelf>-<slot>-{ES1,
ES2}
ES2}
The following generic AID is used to address all entities in a particular command:
ALL AID
ALL
ALL
....................................................................................................................................................................................................................................
1830 PSS
5-576
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-23
Component
(continued)


The following generic AID is used to indicate that no entity is addressed or that no relation to
another entity exists:
None AID
NONE
NONE
Firewall filter chain AIDs
The following AIDs are related to firewall filter chain (IP ACL):
Table 5-24
Component
Meaning
FORWARD
IP forwarding chain
TL1RAWUNSEC
Input chain for the raw encoded TL1 service on TCP

port 3082
TL1RAW
Input chain for the raw encoded TL1 over SSH port
6084
TL1TELNET
Input chain for the telnet encoded TL1 over SSH port
6085
ZIC
Input chain for all SSL/TLS ports used by

communication to ZIC-GUI
DBG
Input chain for debug shell SSH port 22
CPMGT
Input chain for control plane management via CORBA

over SSL/TLS port 684
CPCLI
Input chain for the control plane CLI over SSH port
6087
CPRSVP
Input chain for the control plane signaling protocol

RSVP
CPOSPFTE
Input chain for the control plane OSPF-TE protocol

(data plane routing)
CPLMP
Input chain for the control plane LMP protocol on UDP

port 701
NTP
Input chain for the NTP protocol on UDP port 123
OSPF
Input chain for the OSPFv2 routing protocol
ICMP
Input chain for ICMP messages
MON
Input chain for NE monitoring on TCP port 8649
....................................................................................................................................................................................................................................
1830 PSS
5-577
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 5-24
(continued)
Component
Meaning
NETIF-ALL
Matches any NETIF
IPIPT-ALL
Matches any IPIPT
Database AIDs
The following AIDs are related to database backups:

Component
Access identifier
System's primary backup database.
ACTDSKDB
System's secondary backup database.
STBYDB
Database backup on a remote file

server.
RFSDB
PM Global file collection AIDs
The following AIDs represent the PM global file collection:

Component
Access identifier
Local NE PM Global file collection
LOCPMGLB
Remote file server PM Global file

collection
RFSPMGLB
Software AIDs
The following AIDs are related to software loads (generics):

Component
Access identifier
Standby software generic on the NE
STBYSW
Software generic on a remote file

server
RFSSW
Active software generic on the NE
ACTSW
....................................................................................................................................................................................................................................
1830 PSS
5-578
Issue 1 June 2013

TL1 parameters
....................................................................................................................................................................................................................................
TL1 parameters
Overview
The TL1 Parameters window displays the parameters related TL1 encoding over TCP/IP;
it provides the following information:
Parameter
Details
IP Raw encoding Port
Is the IP port used for raw TL1 encoding over SSH .

Values are:
IP Telnet encoding Port
6084
Is the IP port used for TL1 telnet encoding over SSH.

Values are:
Prompt
6085
The prompt string used for TL1 over telnet encoding. This prompt
string is a text string which can include (in addition to the TL1
character set) the following control characters:
Outputs carriage return character.
Outputs line feed character.
Outputs tabulator character
....................................................................................................................................................................................................................................
1830 PSS
5-579
Issue 1 June 2013
TL1 parameters
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
5-580
Issue 1 June 2013
11QPE24 L2 Features
6
Overview
Purpose
This chapter provides descriptions and CLI commands for the 11QPE24 L2 features. For
CLI command details and parameters, see the Alcatel-Lucent 1830 Photonic Service
Switch (PSS) Release 6.0 Command Line Interface Guide.
Contents
11QPE24 Quality of Service (QOS)
6-3
11QPE24 QOS CLI commands
6-5
11QPE24 Ethernet Ring Protection
6-9
11QPE24 ERP CLI commands
6-14
11QPE24 Ethernet OAM
6-15
11QPE24 Ethernet OAM CLI commands
6-27
6-29
6-32
11QPE24 Services
6-33
11QPE24 Services CLI commands
6-40
11QPE24 Link Aggregation Group (LAG)
6-44
6-47
11QPE24 MC-LAG CLI commands
6-48
6-49
11QPE24 Remote Managed Device CLI commands
6-51
6-53
11QPE24 Clear CLI commands
6-55
...................................................................................................................................................................................................................................
1830 PSS
6-1
Issue 1 June 2013
11QPE24 L2 Features
Overview
....................................................................................................................................................................................................................................
11QPE24 Tools CLI commands
6-56
11QPE24 General CLI commands
6-57
6-58
....................................................................................................................................................................................................................................
1830 PSS
6-2
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
The 11QEP24 is designed with Quality of Service (QoS) mechanisms on both ingress and
egress to support multiple services per physical port. It has extensive and flexible
capabilities to classify, police, shape, and mark traffic. The 11QEP24 supports eight
forwarding classes internally named: Network-Control, High-1, Expedited, High-2,
Low-1, Assured, Low-2 and Best-Effort. Support for 802.1ad 4P3D and other forwarding
classes is also provided.
The 11QEP24 uses QoS policies to control how QoS is handled at distinct points in the
service delivery model. There are different types of QoS policies for the different QoS
needs at each point. QoS policies are defined in a global context in the 11QEP24 and only
take effect when they are applied to a relevant entity. QoS policies are uniquely identified
with a policy ID number or name. Policy ID 1 or Policy ID default is reserved for the
default policy which is used if no policy is explicitly applied.
The QoS policies within the 11QEP24 can be divided into three main types:
QoS policies are used for classification, defining metering and queuing attributes and
marking.
Slope policies define WRED slope profiles for each forwarding class queue.
Port scheduler policies determine how queues are scheduled.
QOS policies
Common to all services are policies that are assigned to the service. Policies are defined
at a circuit pack level and then applied to a service. Policies are used to define service
enhancements. QoS policies are applied on service ingress, access port egress, and uplink
port ingress & egress.
The types of QoS policies that are supported on the 11QPE24 pack are:
SAP Ingress QoS policies which define different classes of traffic within a service at
SAP ingress.
Service ingress QoS policies are applied to the customer-facing Service Access Points
(SAPs). Traffic that enters through the SAP is classified to map it to a Forwarding
Class (FC). Each FC is assigned to a separate egress queue for scheduling.
Forwarding classes are associated with meters/policier on ingress. The mapping of
traffic to meters can be based on combinations of customer QoS marking (IEEE
802.1p bits) and MAC criteria, or DSCP. The definition includes the number of
....................................................................................................................................................................................................................................
1830 PSS
6-3
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
forwarding class meters for unicast traffic and the meter characteristics (like CIR,
PIR, etc.). Each of the forwarding classes can be associated with different unicast
parameters. A service ingress QoS policy also defines up to three meters per
forwarding class to be used for multipoint traffic. There can be up to 16 meters in total
per Service ingress QOS policies.
A QoS policy must be created before it can be applied to a SAP. Only a single SAP
ingress QoS policy can be associated with a SAP. If an ingress QoS policy is not
assigned to a SAP, a default ingress QoS policy is assigned by the system.
Access egress QoS policies

An access egress policy is applied to the physical port or LAG as opposed to the
logical service access point (SAP). An access egress QoS policy maps the FC traffic
egressing out on the customer facing ports into various queues and marks the traffic
accordingly. FC-to-queue mapping is static and is not configurable. The number of
queues is static and there are always 8 queues per port. An access egress policy also
defines how to remark the forwarding class to IEEE 802.1p bits in the customer
traffic.
Slope QoS Policies

Port Scheduler policies
Define the operating parameters (such as egress scheduling algorithm, weights per
priority). They are associated with physical ports and LAGs.
Network QoS policies

Network QoS policies apply to uplink ports. On ingress, the policy maps incoming
802.1p (Dot1p) values to forwarding class and profile state (color) for the traffic
received from the network. On egress, the policy maps forwarding class and profile
state to Dot1p values for traffic to be transmitted into the network.
Network Queue QoS policies

Network queue policies are applied on egress to network (uplink) ports. Similar to
access egress, these policies map uplink egress traffic into various queues according
to FC. The policies define the forwarding class queue BW profile characteristics for
these entities. FC-to-queue mapping is static and is not configurable. The number of
queues is static and there are always 8 queues at the port level.
Service ingress, access egress, and network QoS policies are defined with a scope of
either template or exclusive. Template policies can be applied to multiple entities (such as
SAPs and ports) whereas exclusive policies can only be applied to a single entity.
....................................................................................................................................................................................................................................
1830 PSS
6-4
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the Services CLI commands for 11QPE24. For command details and
parameters, see the Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 6.0
Command Line Interface Guide.
Configuration Commands
QOS
create
Sap Ingress QoS Policy Commands
sap-ingress
description
scope
num-qos-classifiers
Sap Meter QoS Policy Commands
meter
adaptation-rule
cbs
mbs
mode
rate
Forwarding Class (FC) Commands
default-fc
fc
broadcast-meter
meter
multicast-meter
unknown-meter
Sap Ingress MAC QoS Policy Match Commands
mac-criteria
entry
action
....................................................................................................................................................................................................................................
1830 PSS
6-5
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
match
dot1p
dst-mac
etype
src-mac
Sap Ingress IP DSCP QoS Policy Match Commands
ip-criteria
entry
action
match
dscp
Sap Ingress IPv6 DSCP QoS Policy Match Commands
ipv6-criteria
entry
action
match
dscp
Access Egress QoS Policy Commands
access-egress
description
scope
fc
dot1p-in-profile
dot1p-out-profile
queue
remarking
Access Egress Queue QoS Policy Commands
adaptation-rule
rate
....................................................................................................................................................................................................................................
1830 PSS
6-6
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Network QoS Policy Commands (for Uplink ports)
network
description
scope
Network Ingress QoS Policy Commands
ingress
default-action
dot1p
Network Ingress Meter Commands
meter
adaptation-rule
cbs
mbs
rate
Ingress Forwarding Class (FC) Commands
fc
meter
multicast-meter
Network Egress QoS Policy Commands
egress
fc
dot1p-in-profile
dot1p-out-profile
remarking
Network Queue QoS Policy Commands
network-queue
description
queue
adaptation-rule
rate
....................................................................................................................................................................................................................................
1830 PSS
6-7
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Port Scheduler Policy Commands
port-scheduler-policy
description
mode
queue
Slope Policy Commands
slope-policy
description
queue
high-slope
low-slope
non-tcp-slope
time-average-factor
RED Slope Commands
max-avg
max-prob
start-avg
shutdown
Show Commands
sap-ingress
access-egress
network
port-scheduler-policy
network-queue
....................................................................................................................................................................................................................................
1830 PSS
6-8
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Ethernet ring protection (ERP) switching offers ITU-T G.8032 specification compliance
to achieve resiliency for Carrier Ethernet networks. Because it is simple, robust, and
optimized for rings, it is faster and more reliable than, and therefore preferred over, IEEE
802.1 Spanning Tree Protocols in ring networks. Like STP networks, ERP normally keeps
one link in the ring blocked to user traffic, but also like MSTP, it is possible to run
multiple ring sessions on the same physical ring, with different blocked links in each.
This enables load balancing on the ring when traffic patterns allow.
Eth-rings can interwork with other rings with single or dual interconnections. In R5.1,
only stand-alone rings are supported, and only on uplink (NNI) ports, but multiple
non-interworking ring instances are supported.
In R5.1 only VPLS services can use ERP (epipes are emulated as two-node ERPs). All
VPLS services may be protected by one Eth-ring instance, or arbitrarily divided among
several.
ERP is instantiated on uplink (NNI) ports, and ERP switching is triggered by NNI port
failures, and also optionally by Eth-OAM CCM link faults detected by Down MEPs on
the ring ports, for a ring topology in which links are not directly connected. Although ring
switching can be held off to allow underlying protection to operate first, this in not usual:
the advantage of ERP is its native fast (~50 ms) protection switching.
Eth-rings use the G.8032 standard protocol for control, and participating nodes exchange
protocol messages using Y.1731-defined OAM frames called R-APS. R-APS frames are
sent by MEPs belonging to an MA not associated with a service, and positioned on ring
paths. R-APS frames are tagged and should be configured with a unique (not shared with
a service or other ring) VID when the ring port has dot1q encapsulation, and with a
unique outer VID when the ring port has qinq encapsulation (the inner VID doesnt
matter). In R5.1, Eth-rings are only on individual NNI ports (no LAGs), and NNI ports
only use qinq encapsulation.
Basic G.8032 ERP Operation
The following sections describes the Basic G.8032 ERP Operation.

G.8032 ERP Protocol Messages
R-APS messages that carry the G.8032 protocol are sent on dedicated protocol VLAN
called ERP VLAN (or Ring Control Instance). In the revertive case, and initially in the
non-revertive case, G.8032 Protocol ensures that the Ring Protection Link (RPL) owner
blocks the RPL link. R-APS messages are periodically multicast in both directions to
simultaneously inform other nodes in the Ring about the blocked port in the RPL owner
node. In non-revertive mode any link may be the blocked link; it is the last one to recover
....................................................................................................................................................................................................................................
1830 PSS
6-9
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
from a failure. (Revertive operation ensures a known configuration and is required when
multiple concurrent rings are used for load balancing. Non-revertive operation avoids the
extra traffic hit caused by reversion.) Y.1731 Ethernet OAM APS is the basis of the
R-APS messages.
Y.1731 CC messages are typically used by nodes in the ring to monitor the health of each
link in the ring in both directions. However CC messages are not mandatory. Other link
layer mechanisms are considered for example Ethernet LOS (Loss of Signal) when the
nodes are directly connected.
Ring Startup Convergence
Initially each Ring Node blocks one of its links and notifies other nodes in the ring about
the blocked link (RPL Owner blocks the RPL). Once a ring node in the ring other than the
RPL Owner learns that another link is blocked, the node unblocks its blocked link
possibly causing FDB flush in all links of the ring for the affected service VLANs. This
procedure results in unblocking all links but the RPL and the ring normal (or idle) state is
reached. In revertive mode the RPL link is always the link that is blocked when all links
are operable after the revert (WTR) time. In non-revertive mode the RPL link is no
different from other ring links (until a clear command is issued, which restores the RPL as
blocked). Each time there is a topology change that affects reachability, the nodes may
flush their FDB and MAC learning takes place for the affected service VLANs, allowing
forwarding of packets to continue, some on new paths. Flushing is triggered by the
G.8032 state machine and the 11QPE24 implementation allows flooding of traffic during
the flushing interval to expedite traffic recovery.
Figure 6-1 G.8032 Ring in the Initial State
....................................................................................................................................................................................................................................
1830 PSS
6-10
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Ring Fault Operation
When a ring failure occurs, the node or nodes detecting the failure (by local port fault or
by Y.1731 OAM CC monitoring) send R-APS message in both directions. This allows the
nodes at both ends of the failed link to block forwarding to the failed link preventing it
from being active. In revertive mode, the RPL Owner (or in non-revertive mode,
whichever node(s) are blocking) then unblocks the previously blocked RPL and triggers
FDB flush for all nodes for the affected service instances by R-APS. The ring is now in
the protecting state and full ring connectivity is restored. MAC learning takes place to
allow Layer 2 packet forwarding on a ring.
Figure 6-2 G.8032 Ring in the Protecting State
Ring Fault Recovery
Once the failed link recovers, the nodes that blocked the link again send the R-APS
messages indicating no failure this time. This in turn triggers the RPL Owner to block the
RPL link (following Wait-to-Restore timeout) and indicate the Blocked RPL link the ring
in R-APS message, which when received by the nodes at the recovered link cause them to
unblock that link and restore connectivity (again all nodes in the ring perform FDB Flush
and MAC learning takes place). In non-revertive mode the RPL ignores the messages
from the nodes with blocked links, and they remain blocked; no FDB flushing is needed.
The ring is back in the normal (or idle) state.
ERP Implementation
The following sections describe ERP implementation.

....................................................................................................................................................................................................................................
1830 PSS
6-11
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
VLPS Service for Ring Instance
In the 11QPE24 implementation, the Ethernet Ring control instance is built from a
dedicated dummy VPLS service on each node with VPLS SAPs that carries only R-APS
messages. It is not used for subscriber data.
Use of ETH-CFM MEPs
Within each path, Y.1731 Down MEPs are used to exchange R-APS specific information
(when control-mep is enabled). For this function they behave more like MIPs than
standard Down MEPs: they copy and forward received R-APS PDUs rather than
terminate them, terminating only if they originated locally. This allows faster propagation
of information than hop-by-hop signaling as is done by spanning tree protocols.
The MEPs can also optionally exchange fast CCM for node-to-node fault detection. This
is especially necessary when nodes are not directly connected by Ethernet links so that
not all faults are detected by the ports. CCM messages can be configured with intervals
between 3.3 msec and 100 msec, the former providing fault detection time of 10 msec.
Because the path Down MEP is monitoring the link, and not a service, it is typically
configured at a low MD level, although this is not required.The control tag (raps-tag)
defined under each eth-ring path is used by the MEP for encapsulating and forwarding the
CCMs and the G.8032 R-APS messages used for the protection function.
Fault Detection
For fault detection using CCMs, three CC messages must be missed for a fault to be
declared on the associated path. After it receives the fault indication, the protection
module declares the associated ring link down and the G.8032 state machine sends the
appropriate messages to open the blocked link and flush the learned addresses.
Service Allocation to Ring Instances
G.8032 supports multiple data channels (services) per ring control instance (R-APS tag).
G.8032 also supports multiple control instances such that each instance can have its RPL
on a different link providing for a load balancing capability. However once services have
been assigned to one instance, the same services on other nodes must be on the same ring
instance. When there is any one link failure or any one node failure in the ring, the
G.8032 protocol is capable of restoring traffic among all remaining nodes for these data
services.
Each NNI (uplink) port supports up to 10 ring instances which can coexist with
unprotected VPLS SAPs. In R5.1, Eth-Rings are not supported on LAGs.
Rings on Access Ports (Future)
In a future release, Ethernet R-APS can be configured on any port configured for access
mode using dot1q, q-in-q encapsulation enabling support for Ethernet R-APS protected
services on the service edge towards the customer site, or within the Ethernet backbone.
....................................................................................................................................................................................................................................
1830 PSS
6-12
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Service Independence from Ring
E-Line, E-LAN (and E-Tree in the future) services can be given Ethernet R-APS
protection and the services are configured independent of the Ring properties. The
intention of this is to cause minimum disruption to the service during Ethernet R-APS
failure detection and recovery. Note that E-Line services are provided using the VPLS
service construct because Epipes are not currently supported by ERP.
QoS Considerations
Ethernet ring CC and R-APS messages transmitted over the SAP queues using the default
egress QoS policy use NC (network class) as a forwarding class. If user traffic is assigned
to the NC forwarding class, it competes for the same bandwidth resources with the
Ethernet CCMs. As CCM loss could lead to unnecessary switching of the Ethernet ring,
congestion of the queues associated with the NC traffic should be avoided. The operator
must configure different QoS Policies to avoid congestion for the CCM forwarding class
by controlling the amount of traffic assigned into the corresponding queue. For the same
reason, the ccm-ltm-priority setting for the control MEPs should always be the highest
priority.
Operator Switch Commands
The user can control ring switching by commands in the tools>perform>eth-ring context.
The force command puts the target path into the blocked state, which remains regardless
of faults or other force commands in the ring. Unless otherwise constrained (fault or
force), the RPL owner removes its block at that time. The manual command is similar,
except that the block remains only while the ring is fault-free. The clear command, which
applies to the ring instance, removes either of the above local commands. In the revertive
mode it also clears an active WTR or WTB timer to cause immediate reversion; in the
non-revertive mode it causes reversion to the RPL owner.
Timers
The user can configure the guard and revert timers. The guard timer is used to prevent
stale R-APS messages, circulating after a local Signal Fail clears, from affecting the state
machine. It may need to be tuned to optimize for different size rings. The revert timer,
also known as Wait to Restore (WTR), is only effective in revertive mode, and enforces
delay to allow bouncing faults to settle before the RPL owner reverts to the normal
blocked state.
There is a non-configurable Wait to Block (WTB) timer used by the RPL owner to delay
reversion to the blocked state following the removal of an operator switch command, to
ensure there is no other forced switch on the ring.
....................................................................................................................................................................................................................................
1830 PSS
6-13
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the ERP CLI commands for 11QPE24. For command details and
CLI Configuration Commands
eth-ring
description
guard-time
revert-time
rpl-node
node-id
compatible-version
path
description
rpl-end
eth-cfm
mep
ccm-enable
ccm-ltm-priority
control-mep
low-priority-defect
mac-address
shutdown
Sub Ring Commands
sub-ring
interconnect
propagate-topology-change
Show Commands
eth-ring
....................................................................................................................................................................................................................................
1830 PSS
6-14
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
The IEEE and the ITU-T have loosely cooperated to define the protocols, procedures and
managed objects to support service based fault management. Both IEEE 802.1ag standard
and the ITU-T Y.1731 recommendations support a set of tools that allow operators to
deploy the necessary administrative constructs, management entities and functionality of
Ethernet Connectivity Fault Management (ETH-CFM). These include continuity and
connectivity checking, one-shot loopback, and MAC based link trace. The ITU-T has also
implemented advanced ETH-CFM for carrier service providers, including Eth-AIS, APS,
proactive loss and delay measurement for SLA monitoring, and on-demand versions for
troubleshooting.
ETH-CFM uses Ethernet frames which are distinguishable by Ethertype 0x8902. In
certain functions a reserved multicast address is used to identify the maintenance level at
the MAC layer. However, the multicast MAC addressing is not used for every function or
in every case. The Operational Code (OpCode) in the common CFM header is used to
identify the type of function carried in the CFM packet. ETH-CFM frames are only
processed by IEEE 802.1 bridges. With CFM, interoperability can be achieved among
different vendors equipment in the service provider network, and customer premises
bridges.
Target applications
Ethernet Link OAM (802.3ah, Ethernet in the First Mile (EFM)) runs between peer
MACs on a point-to-point link. It is typically used on UNIs, i.e. between provider
equipment and customer equipment. It may also be tunneled through the provider
equipment.
Ethernet Service OAM (ETH-CFM) is more general and can be used to monitor a link
similar to Link OAM (their capabilities overlap somewhat, not completely), but can also
monitor services through the network. For a provider, a service OAM instance begins and
ends at the UNI-Ns of the service. A customer can also run service OAM instances among
its UNI-Cs. These can interact to a limited degree. The providers network can also be
partitioned with each partition monitored separately between the E-NNIs.
Ethernet Service OAM can also be applied to monitor Ethernet Ring spans, providing an
APS channel and fault monitoring per span.
Service OAM Features
The following sections describe the service OAM features.
....................................................................................................................................................................................................................................
1830 PSS
6-15
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Maintenance Domain
A Maintenance Domain (MD)/Maintenance Entity (ME) is the administrative container

that defines the scope of CFM. It is typically the area of ownership and management
responsibility. The IEEE allows for various formats to name the domain, including
none, allowing up to 43 characters, depending on the format selected. ITU-T does not
support the concept of MD, leaving only the name format of none.
0 Undefined and reserved by the IEEE.
1 No domain name. It is the only format supported by Y.1731 as the ITU-T
specification does not use the domain name. This is supported in the IEEE 802.1ag
standard but is not currently implemented for 802.1ag-defined contexts in the 11QPE24.
2,3,4 Provides the ability to input various different textual formats, up to 43 characters.
The string format (2) is the default.
An MD has a level (0 7) to distinguish among the administrators that may be involved
in monitoring a service, e.g. customer, provider, and providers provider (operator), and
provides a hierarchy among them. The hierarchy is given by the nesting rule which
prohibits CFM traffic of lower levels from passing through higher levels, controlling the
width of the domains. The wider the domain, the farther the ETH-CFM packets can
travel. The widest domain is the customers (typically level 7) with maintenance
endpoints in the CE. Lower and inside are the Providers levels which contains operators
levels, if any. The lowest level (0) is usually reserved for link monitoring. All eight levels
are available for use.
Maintenance Association
A Maintenance Association (MA)/Maintenance Entity Group (MEG) is the construct

within an MD for all the maintenance entities of a service. The MA includes a set of
MEPs (Maintenance Endpoints, see below), each configured with the same MAID and
MD level used monitor a single service instance.
Each MA is uniquely identified in a network by its MAID. The MAID is composed of the
MD name and MA name of a particular format. The IEEE and the ITU-T use their own
specific formats. The MA short name formats (0-255) have been divided between the
IEEE (0-31, 64-255) and the ITU-T (32-63), with five currently defined (1-4, 32). Even
though the different standards bodies now recognize the others formats, a Y.1731
context can only be configured in R5.1 using the ITU-T format option 32. This is
important because the Y.1731 functions (AIS, DM, SLM) are only available in a Y.1731
context.
1 (Primary VID) Values 0 4094
2 (String) Raw ASCII, excluding 0-31 decimal/0-1F hex (which are control characters)
form the ASCII table
3 (2-octet integer) 0 65535
....................................................................................................................................................................................................................................
1830 PSS
6-16
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
4 (VPN ID) Hex value as described in RFC 2685, Virtual Private Networks Identifier
32 (icc-format) Exactly 13 characters from the ITU-T recommendation T.50
(essentially printable ASCII characters).
Note: When a VID is used as the short MA name, 802.1ag will not support VLAN
translation because the MAID must match all the MEPs. The default format for a short
MA name is an integer. Integer value 0 means the MA is not attached to a VID.
In the 11QPE24, the MA is not directly configured for a VLAN. For an MA used for
service monitoring, it picks up the appropriate VID by being attached to a service through
the bridge ID parameter, which is configured to be the service ID. In Fig. 1 each color
represents a different MA, but all are for the same service (VLAN). For an MA used for
ERP MEPs, no bridge ID is configured. The VLAN used is that of the raps-tag
parameter.
Maintenance Endpoints
Maintenance Endpoints (MEPs)/MEG Endpoints (MEPs) are the workhorses of

ETH-CFM. A MEP has a unique ID number within an MA (0-8191). Each MEP is
uniquely identified by the MAID, MEPID tuple. This management entity is responsible
for initiating, processing and terminating ETH-CFM functions, following the nesting
rules. MEPs form the boundaries which prevent the ETH-CFM packets from flowing
beyond the specific scope of responsibility. A MEP has direction, Up or Down. Each
indicates the directions packets are generated; Up toward the switch fabric, Down toward
the SAP away from the fabric. CFM packets arriving from the designated direction of the
MEP are compared to its MD level and passed, processed, or dropped if they are of a
higher, same, or lower level, respectively. CFM packets of higher level that enter the
back side of the MEP are passed transparently through the MEP, otherwise they are
blocked.
Each MEP contained within the same maintenance association and with the same level
(MAID) represents endpoints within a single service. MEP creation on a SAP is allowed
only for Ethernet ports with null, q-tag, or q-in-q encapsulations. The 11QPE24 supports
both Up MEPs and Down MEPs. Up MEPs are configured on client ports to monitor
services. They don't need a high rate and can be configured with an interval or 1 second
or longer. Down MEPs in Provider equipment typically monitor links and may need an
interval as short as 3.3 milliseconds. A Down-MEP must be configured on each path of an
Eth-Ring. It generates the Ring APS messages when the control-mep option is enabled.
It can also be configured to trigger ring protection switching based on CCM faults. This is
the usual case, to increase switching speed and to respond to intermediate faults not
detected by the local Ethernet port.
Maintenance Intermediate Points
Maintenance Intermediate Points (MIPs)/MEG Intermediate Points (MIPs) are

management entities between the terminating MEPs along the service path. These provide
insight into the service path connecting the MEPs. MIPs only respond to Loopback
....................................................................................................................................................................................................................................
1830 PSS
6-17
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Messages (LBM) and Linktrace Messages (LTM). All other CFM functions are
transparent to these entities. Only one MIP is allowed per SAP. The creation of the MIPs
can be done when the lower level domain is created (explicit). This is controlled by the
use of the mhf-creation mode within the association under the bridge-identifier. MIP
creation is supported on SAPs. By default, no MIPs are created. Only one MIP can exist
on a given port for a particular service, usually automatically configured at the configured
MD level just above the highest level MEP. This conserves resources. Only the Down
portion of MIPs are supported in R5.1.
CFM Configuration Location
There are two locations in the configuration where ETH-CFM is defined. The
infrastructure: domains, associations (including linkage to the service id), MIP creation
method, common ETH-CFM functions and remote MEPs, are defined under the top level
eth-cfm command. It is important to note, when Y.1731 functions are required the context
under which the MEPs are configured must follow the Y.1731 specific formats (domain
format of none, MA format icc-format). Once these parameters have been entered, a MEP
and possibly a MIP can be defined within the service under the SAP.
Loopback
A loopback message is generated by a MEP to a peer MEP or an intervening MIP. The

functions are similar to an IP ping to verify Ethernet connectivity between the nodes. The
following loopback-related functions are supported:
Loopback message functionality on an MEP or MIP can be enabled or disabled.
MEP Supports generating loopback messages and responding to loopback

messages with loopback reply messages.
MIP Supports responding to loopback messages with loopback reply messages
when loopback messages are targeted to it.
Displays the loopback test results on the originating MEP. There is a limit of ten
outstanding tests per node.
Loopback messages are unicast, multicast are not generated, but may be responded .
Linktrace
A linktrace message (LTM) is originated by a MEP and targeted to a peer MEP. Its
function is similar to IP traceroute, tracing a specific MAC address through the service.
The peer MEP responds with a linktrace reply (LTR) after successful inspection of the
LTM. The MIPs along the path also process the LTM and respond with LTRs to the
originating MEP if the received LTM has a TTL greater than 1 and forward the LTM if a
look up of the target MAC address in the Layer 2 FDB is successful. The originating
MEP expects to receive multiple LTRs and from processing the, can put together the route
to the target bridge. The target MEP (or any MEP) terminates the LTM.
....................................................................................................................................................................................................................................
1830 PSS
6-18
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
The target MAC address is carried in the payload of the LTM. Each MIP receiving the
LTM checks whether it knows the target MAC address (via the FDB). In order to use
linktrace the target MAC address must have been learned (or statically configured) by the
nodes in the network. If so, an LTR is sent back to the originating MEP. Also, a MIP
forwards the LTM out of the port where the target MAC address was learned.
The LTM uses a multicast destination address. On a broadcast LAN, it can be received by
multiple nodes connected to that LAN. But, at most, one node will send a reply, the one
with a path to the target.
The following linktrace related functions are supported:
Enable or disables linktrace functions on an MEP.

MEP Supports generating LTMs and responding with LTRs.
MIP Supports responding to LTMs with LTRs.

Displays linktrace test results on the originating MEP. There is a limit of ten
outstanding tests per node. Storage is provided for up to ten MEPs and for the last ten
responses. If more than ten responses are received older entries are overwritten.
Delay Measurement
ETH-DM, specified by Y.1731, uses time-stamped delay measurement messages (DMM)

and replies (DMR) to perform single-ended two-way delay measurement. Four
timestamps are collected: DMM sent by originator, DMM received from responder, DMR
sent by responder, and DMR received by originator. Close synchronization between ends
isnt necessary. The difference between the originators timestamps is the gross roundtrip
delay. The difference between the responders timestamps is the dwell time at the
responder. The difference between the differences is the sum of the link delays in each
direction, i.e. two-way delay.
The 11QPE24 supports two-way delay measurement, using the two-way-delay-test
command in the oam eth-cfm context. The result is viewed per MEP using the
two-way-delay-test qualifier in the show eth-cfm command. A delay variation result is
also shown as the difference in delay from a previous measurement.
Without TOD synchronization, one-way delay measurements arent useful and therefore
arent supported.
Synthetic Loss Measurement
Synthetic loss measurement implementation is a single-ended feature that allows the

operator to run on-demand tests to determine "in" loss, "out" loss and "unacknowledged"
packets, and proactive tests to monitor Frame Loss Ratio. It can be used between peer
MEPs in both point-to-point and multipoint services. Only remote MEP peers within the
maintenance association and matching the unicast destination address will respond to the
SLM packet. Responders arent configured; when a valid SLM frame is received by a
MEP initiating a test (new test-id), if there sufficient resources it will start the associated
Rx and Tx counters.
....................................................................................................................................................................................................................................
1830 PSS
6-19
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
The specification uses various sequence numbers in order to determine in which direction
the loss occurred. Alcatel-Lucent has implemented the required counters to determine loss
in each direction. In order to properly use the information that is gathered the following
terms are defined;
Count The number of probes that are sent when the last frame is not lost. When the
last frame(s) is or are lost, the count and unacknowledged equals the number of
probes sent.
Out-Loss (Far-end) Packets lost on the way to the remote node, from test initiator
to the test destination.
In-Loss (Near-end) Packet loss on the way back from the remote node to the test
initiator.
Unacknowledged Number of packets at the end of the test that were not responded
to.
The per-probe specific loss indicators are available when looking at the on-demand test
runs, or the individual probe information stored in the MIB.
On-Demand ETH-SLM
The on-demand function can be executed from CLI or SNMP. The on-demand tests are
meant to provide the carrier a way to perform spot testing. However, this approach is not
meant as a method for storing archived data for later processing. The probe count for
on-demand SLM has a range of one to 100 with configurable probe spacing between one
second and ten seconds. This means it is possible that a single test run can be up to 1000
seconds in length. Although possible, it is more likely the majority of on-demand cases
will use 100 probes or less at a one second interval. A card may only initiate and maintain
a single active on-demand SLM test at any given time. A maximum of one storage entry
per remote MEP is maintained in the results table. Subsequent runs to the same peer can
overwrite the results for that peer. This means, when using on-demand testing the test
should be run and the results checked prior to starting another test.
Proactive Test SLM/DM
Proactive Test is an extension of on-demand tests for SLM and DM. Proactive means they
run continuously once started, and measurement results are binned similar to other L2
binning with optional TCAs on maximum and average values measured during a bin
interval. Proactive tests are typically used to monitor a service demarked by Up-MEPs.
Proactive SLM and DM are configured similarly to the on-demand tests. One difference
is that forwarding class is specified instead of priority. Each proactive test has an
associated PMON policy which defines the TCAs and binning as for other L2 PMON.
The test begins when the policy is attached, after which parameters and policy-id cant be
changed. Identical on-demand and proactive tests may be run simultaneously. The number
of simultaneous proactive tests is 32 64 per type.
....................................................................................................................................................................................................................................
1830 PSS
6-20
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Proactive SLM is used to calculate Frame Loss Ratios. It is a single ended measurement
with counts of sent frames embedded. Average FLR is calculated over the entire bin
interval. Max and Min FLR are determined from FLR calculated over subintervals within
a bin. FLR measurement interval is configurable in policy
Note: There is no 15-min bin for FLR.
Proactive DM bins min, max, and average round-trip delay, and one-way delay
variation per direction.
Proactive Test PMON is similar to other L2 PMON. Eight policies per type are
configurable. TCAs are settable on max and average counters .
The principal use of Proactive Test use cases is for monitoring a service, e.g. SLA
verification
Between Up MEPs
Point to Point
Multipoint.
The user can create a new proactive test until system resources are exhausted.
Proactive tests are configured on MEPs.
Proactive tests make measurements at a particular CoS. A MEP can potentially
have tests configured at every CoS.
An on-demand test can be run with the same parameters as a proactive test.
A responder for a two-way test is not configured. When a valid SLM PDU is
received by a MEP, a responder with associated counters is automatically created
if sufficient resources are available. The responder replies with SLR PDUs based
on its counters. When a valid DMM PDU is received by a MEP, a DMR response
is sent if sufficient resources are available.
The user can show the proactive tests that exist on a card, including their type
(SLM or Delay).
The user can show the configuration parameters of a proactive test.

The user can show the PMON bin output for a proactive test .
The user can delete a proactive test, which removes all of its configuration and
PMON bins and cancels any associated TCA alarms.
ETH-SLM Test Details
The ETH-SLM packet format contains a test-id that is internally generated and not
configurable. The test-id is visible for the on-demand test in the display summary. It is
possible for a remote node processing the SLM frames to receive overlapping test-ids as a
result of multiple MEPs measuring loss between the same remote MEP. For this reason,
the uniqueness of the test is based on remote MEP-ID, test-id and Source MAC of the
packet
....................................................................................................................................................................................................................................
1830 PSS
6-21
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
ETH-SLM is applicable to Up and Down MEPs and is transparent to MIPs. There is no

coordination with various fault conditions that could impact loss measurement. This is
also true for conditions where MEPs are placed in shutdown state as a result of linkage to
a redundancy scheme like MC-LAG. Loss measurement is based on the ETH-SLM and
not coordinated across different functional aspects on the network element. ETH-SLM is
supported on service based MEPs.
It is possible that two MEPs may be configured with the same MAC on different remote
nodes. This causes various issues in the FDB for multipoint services and is considered a
misconfiguration for most services. It is possible to have a valid configuration where
multiple MEPs on the same remote node have the same MAC. In fact, this is likely to
happen. In this release, only the first responder is used to measure packet loss. The second
responder is dropped. Since the same MAC for multiple MEPs is only truly valid on the
same remote node this should be acceptable.
There is no way for the responding node to understand when a test is completed. For this
reason an inactivity-timer determines the length of time a test is valid. The timer will
maintain an active test as long as it is receiving packets for that specific test, defined by
the test-id, remote MEP Id and source MAC. When there is a gap between the packets
that exceeds the inactivity-timer the responding node responds with a sequence number of
one regardless of the sequence number that the instantiating node sent. This means the
remote MEP accepts that the previous test has expired and these probes are part of a new
test. The inactivity timer is fixed to 100 seconds.
The responding node is limited to a fixed number of SLM tests per card. Any test, that
attempts to involve a responder that is already actively processing at the system limit of
the SLM tests, shows up as out loss or unacknowledged packets on the node that
instantiated the test because the packets are silently discarded at the responder. It is
important for the operator to understand this is silent and no log entries or alarms are
raised. It is also important to keep in mind that these packets are ETH-CFM based and the
different nodes stated receive rate limit for ETH-CFM must not be exceeded.
Continuity Check
A Continuity Check Message (CCM) is a multicast frame that is generated by a MEP and
multicast to all other MEPs in the same MA. The CCM does not induce a reply message;
all MEPs generate CCM autonomously. To identify faults, the receiving MEP maintains
an internal list of remote MEPs it should be receiving CCM messages from. This list is
the remote-mepid configuration within the MA. When the local MEP does not receive a
CCM from one of the configured remote MEPs within a pre-configured period, the local
MEP raises an alarm.
....................................................................................................................................................................................................................................
1830 PSS
6-22
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
The following functions are supported:
Enable and disable CC for a MEP
Manually configure and delete remote MEP entries in the MEP monitoring database.
It is only required to provision remote MEPs. Local MEPs are automatically put into
the database when they are created.
CCM transmit interval: 3.3ms, 10ms, 100ms,1s,10s, 60s and 600s for Down-MEPs,
1s, 10s, 60s, 600s for Up-MEPs.
Default: 10s.
When configuring MEPs with sub-second CCM intervals, bandwidth consumption must
be taken into consideration. Each CCM PDU is 100 bytes (800 bits). Taken individually
this is a small value. However, the bandwidth consumption increases rapidly as multiple
MEPs are configured with subsecond CCMs. Sub-second enabled MEPs are supported on
the following:
Down MEPs configured on Ethernet SAPs.

Lowest MD-level, when multiple MEPs exist on same Ethernet SAP.
11QPE24 can have multiple MEPs with sub-second intervals on the same SAP.
CCM processing will declare a fault, when:
The MEP stops hearing from one of the remote MEPs for 3.5 times CC interval
Hears from a MEP with a LOWER MD level
Hears from a MEP that is not part of the local MEPs MA
Hears from a MEP that is in the same MA but not in the configured MEP list
Hears from a MEP in the same MA with the same MEP id as the receiving MEP
The CC interval of the remote MEP does not match the local configured CC interval
The remote MEP is declaring a fault (port down)
An alarm is raised and a trap is sent if the defect is greater than or equal to the configured
low-priority-defect value.
Remote Defect Indication (RDI) is supported but by default is not recognized as a defect
condition because the low-priority-defect setting default does not include RDI.
Alarm Indication Signal
Alarm Indication Signal (AIS) provides an Y.1731-capable MEP the ability to signal a
fault condition in the reverse direction of the MEP, out the back side. When a fault
condition is detected the MEP generates AIS packets at the configured client levels and at
the specified AIS interval until the condition is cleared. Currently a MEP configured to
generate AIS must do so at a level higher than its own. The MEP configured on the
service receiving the AIS packets is required to have the active side facing the receipt of
....................................................................................................................................................................................................................................
1830 PSS
6-23
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
the AIS packet and must be at the same level as the AIS. The absence of an AIS packet for
3.5 times the AIS interval set by the sending node clears the condition on the receiving
MEP.
AIS is intended for use in point-to point configurations, so care must be taken when used
in a VPLS service that it is configured as point-to-point.
CFM Connectivity Fault Conditions
CFM MEP declares a connectivity fault when its defect flag is equal to or higher than its
configured lowest defect priority. The defect can be any of the following depending on
configuration:
DefRDICCM
DefMACstatus
DefRemoteCCM
DefErrorCCM
DefXconCCM
The following additional fault condition applies to Y.1731 MEPs:
Reception of AIS for the local MEP level.
CFM Fault Propagation
Fault propagation (Link Loss Forwarding) is only intended for point-to-point

configurations. Care must be taken when used in a VPLS service that it is configured as
point-to-point. In R5.1 an Up MEP sending CCM with interface status TLV "down" is
used for Link Loss Forwarding signaling (port shutdown).
802.3ah EFM OAM fault interaction
802.3ah EFM OAM declares a link fault when any of the following occurs:
Loss of OAMPDU for a certain period of time

Receiving OAMPDU with link fault flags from the peer
When 802.3ah EFM OAM declares a fault, the port goes into operation state down. The
SMGR communicates the fault to CFM MEPs in the service. OAM fault propagation in
the opposite direction (SMGR to EFM OAM) is not supported.
ETH-CFM on ETH-Rings
ETH-CFM is used to monitor services carried over an ETH-Ring, and supports the
functioning of the ring itself. Only the ring MD/MA/MEPs are supported in R5.1. Down
MEPs are used to monitor the links between ring ports of adjacent nodes. The ring MD
level is typically at the lowest available, 0. In R5.1 it must have no MD name, so that the
ring MA implicitly becomes Y.1731 (its name format can only be set to icc-based).
The MA has an implicit VLAN which is the raps-tag of the ring paths where the
....................................................................................................................................................................................................................................
1830 PSS
6-24
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
MEPs are created. "The MEPs are configured as control-MEPs to exchange Ring APS
messages with their neighbors. By enabling 3.3 msec CCM they quickly detect faults to
trigger fast protection switching."
LINK OAM (EFM)
802.3ah Clause 57 (EFM OAM) defines the Operations, Administration, and Maintenance
(OAM) sub-layer, which provides mechanisms useful for monitoring link operation such
as remote fault indication and remote loopback control. In general, OAM provides
network operators the ability to monitor the health of the network and quickly determine
the location of failing links or fault conditions. EFM OAM described in this clause
provides data link layer mechanisms that complement applications that may reside in
higher layers.
OAM information is conveyed in slow protocol frames called OAM protocol data units
(OAMPDUs). OAMPDUs contain the appropriate control and status information used to
monitor, test and troubleshoot EFM OAM-enabled links. OAMPDUs traverse a single
link, being passed between peer OAM entities, and as such, are not forwarded by MAC
clients (like bridges or switches), unless configured to do so (see below).
The following EFM OAM functions are supported:
EFM OAM capability discovery.

Active and passive modes.
Remote failure indication Handling of critical link events (for example, link fault)
Loopback A mechanism is provided to support a data link layer frame-level

loopback mode. Both remote and local loopback modes are supported; the latter is
proprietary.
Dying gasp messages not supported.
EFM OAMPDU tunneling, mutually excusive with peering.
High resolution timer for EFM OAM in 500ms interval (minimum).
OAM Events
EFM OAM defines a set of events that may impact link operation. The following events
are supported:
Critical link events (defined in 802.3ah clause 57.2.10.1)

Link fault: the PHY has determined a fault has occurred in the receive direction of the
local DTE.
Critical event: an unspecified critical event has occurred.
These critical link events are signaled to the remote DTE by the flag field in OAM PDUs.
The 11QPE24 does not generate EFM OAM PDUs with these flags. However, it supports
processing of these flags in EFM OAM PDUs received from the peer.
....................................................................................................................................................................................................................................
1830 PSS
6-25
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Remote Loopback
EFM OAM provides a link-layer frame loopback mode that can be remotely controlled.
To initiate remote loopback, the local EFM OAM client sends a loopback control OAM
PDU by enabling the OAM remote-loopback command. After receiving the loopback
control OAM PDU, the remote OAM client puts the remote port into local loopback
mode.
To exit remote loopback, the local EFM OAM client sends a loopback control OAM PDU
by disabling the OAM remote-loopback command. After receiving the loopback control
OAM PDU, the remote OAM client puts the port back into normal forwarding mode.
Note that during remote loopback test operation, all frames except EFM OAM PDUs are
dropped at the local port for the receive direction, where remote loopback is enabled. If
local loopback is enabled, then all frames except EFM OAM PDUs are dropped at the
local port for both the receive and transmit directions. This behavior may result in many
protocols (such as STP or LAG) resetting their state machines.
EFM PDU Tunneling
Tunneling EFM OAM PDUs is only useful in a point-to-point service. Care must be taken
when used in a VPLS service that it is configured as point-to-point in the network. Ports
must be configured as null encapsulated SAPs.
When OAM PDU tunneling is enabled, 802.3ah OAM PDUs received at one end of are
forwarded. 802.3ah can run between devices that are located at each end of the service.
When OAM PDU tunneling is disabled (by default), OAM PDUs are dropped or
processed locally according to the efm-oam configuration (shutdown or no shutdown).
Note that enabling 802.3ah for a specific port and enabling OAM PDU tunneling for the
same port are mutually exclusive. Enforcement is performed on the CLI level.
....................................................................................................................................................................................................................................
1830 PSS
6-26
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the Ethernet OAM CLI commands for 11QPE24. For command
details and parameters, see the Alcatel-Lucent 1830 Photonic Service Switch (PSS)
Release 6.0 Command Line Interface Guide.
eth-cfm
mep
ais-enable
client-meg-level
interval
priority
ccm-enable
ccm-ltm-priority
control-mep
low-priority-defect
mac-address
shutdown
domain
association
bridge-identifier
mhf-creation
vlan
ccm-interval
remote-mepid
oam
linktrace
loopback
two-way-delay-test
two-way-slm-test
proactive-test
two-way-delay
two-way-slm
pmon-dm-policy
....................................................................................................................................................................................................................................
1830 PSS
6-27
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
pmon-slm-policy
efm
local-loopback
remote-loopback
MC-LAG Commands
redundancy
mc-lag
propagate-hold-time
standby-mep-shutdown
Show Commands
eth-cfm
association
cfm-stack-table
domain
mep
MC-LAG Show Commands
redundancy
mc-lag
....................................................................................................................................................................................................................................
1830 PSS
6-28
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
When troubleshooting complex operational problems, customer packets can be examined

as they traverse the pack. Port mirroring provides the capability to mirror customer
packets to allow for troubleshooting and offline analysis. The 11QPE24 supports local
mirroring: original packets are forwarded while a copy is sent out the mirroring
(destination) port; only a NULL SAP can be provisioned as a mirror destination. Either
ingress or egress traffic can be mirrored, or both.
Mirror Implementation
Alcatel-Lucents implementation of packet mirroring is based on the following:
Ingress and egress packets are mirrored as they appear on the wire. This is important
for troubleshooting encapsulation and protocol issues.
When mirroring at ingress, an exact copy of the original ingress packet is sent to
the mirror destination while normal forwarding proceeds on the original packet.
When mirroring is at egress, the system performs normal packet handling on the
egress packet, encapsulating it for the destination interface. A copy of the
forwarded packet (as seen on the wire) is forwarded to the mirror destination.
Mirroring at egress takes place before the packet is processed by egress QoS.
Hence, there exists a possibility that a packet is dropped by egress QoS
mechanisms (because of RED mechanisms and so on) and thus not forwarded, but
it is still mirrored.
Mirror Source and Destinations
Mirror sources and destinations have the following characteristics:
Mirroring source and destination can only be on the same card (local mirroring only,
no remote).
A mirror destination can terminate on only one port (Null SAP).
A mirror source can be a port, a port which is a member of a LAG, or a LAG (but not
both a LAG and its member).
Packets ingressing a port can have a mirror destination separate from packets
egressing another or the same port.
A total of four mirror destinations are supported (local only).
For port ingress mirroring, any number of source ports may be configured to one or
more mirror destinations but one ingress mirror source can be configured to only one
mirror destination.
....................................................................................................................................................................................................................................
1830 PSS
6-29
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
For port egress mirroring, only a maximum of 4 egress mirror sources are allowed and
one egress mirror source can be configured to only one mirror destination.
Multiple concurrent mirroring sessions are allowed so traffic from more than one
ingress mirror source can be mirrored to the same or different mirror destinations.
Mirroring Performance
Replication of mirrored packets can, typically, affect performance and should be used
carefully.
Mirroring Configuration
Configuring mirroring is similar to creating a uni-directional service. A Mirroring service

requires the configuration of:
Mirror source(s) The traffic on a specific port or ports to mirror.

Mirror destination The location to send the mirrored traffic, where the sniffer will
be located.
Configuration Notes
This section describes mirroring configuration caveats.
Multiple mirroring service IDs (mirror destinations) may be created within a single
system.
A mirrored source can only have one destination.

Physical layer problems such as collisions, jabbers, etc., are not mirrored. Typically,
only complete packets are mirrored.
Starting and shutting down mirroring:
Mirror destinations:
The default state for a mirror destination service ID is shutdown. You must issue a
no shutdown command to enable the feature.
When a mirror destination service ID is shutdown, mirrored packets associated
with the service ID are not accepted from its mirror source. The associated mirror
source is put into an operationally down mode. Mirrored packets are not
transmitted out the SAP. Each mirrored packet is silently discarded.
Mirror destination service IDs must be shut down first to delete a service ID, or
SAP association from the system. The SAP does not need to be removed before
deleting the mirror destination.
....................................................................................................................................................................................................................................
1830 PSS
6-30
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Mirror sources:
The default state for a mirror source for a given mirror-dest service ID is no
shutdown. Enter a shutdown command to deactivate (disable) mirroring from that
mirror-source.
Mirror sources do not need to be shutdown to stop their mirror. When a mirror
destination is shutdown, mirroring is terminated for all sources defined locally for
the mirror destination service ID.
Mirror sources do not need to be shutdown to delete or change the port and
mirrored flow directions
....................................................................................................................................................................................................................................
1830 PSS
6-31
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the Port Mirroring CLI commands for 11QPE24. For command
details and parameters, see the Alcatel-Lucent 1830 Photonic Service Switch (PSS)
Release 6.0 Command Line Interface Guide.
CLI Mirror Configuration Commands
mirror
shutdown
CLI Mirror Destination Configuration Commands
mirror-dest
sap
CLI Mirror Source Configuration Commands
mirror-source
port
Show Commands
mirror mirror-dest
mirror
....................................................................................................................................................................................................................................
1830 PSS
6-32
Issue 1 June 2013
11QPE24 L2 Features
11QPE24 Services
....................................................................................................................................................................................................................................
11QPE24 Services
Overview
A service is a construct for conveying a client's information through a provider's network,

creating a virtual private network (VPN). Each service is uniquely identified by a service
ID and an optional service name within a service area. The 11QPE24 service model uses
logical service entities to construct a service. In the service model, logical service entities
provide a uniform, service-centric configuration and management model for service
provisioning.
In the 11QPE24, services use Layer 2 bridging between a subscriber's service access point
(SAP: a logical service entity on a port where traffic enters and exits the service) one pack
and another subscriber SAP on another pack.
Service Types
The 11QEP24 offers the following types of subscriber services
Virtual Private LAN Service (VPLS) :

A Layer 2 multipoint-to-multipoint (E-LAN)
A Layer 2 point to point (E-Line)
Please note that both of these services use a VPLS based service model.
QoS Policies
Common to all services are policies that are assigned to the service. Policies are defined
at a circuit pack level and then applied to a service. Policies are used to define service
enhancements. The types of policies those are supported on the 11QPE24 pack are:
SAP Quality of Service (QoS) policies which allow for different classes of traffic
within a service at SAP ingress. QoS ingress policies determine the QoS
characteristics for a SAP. A QoS ingress policy applied to a SAP specifies the number
of meters, meter characteristics (such as forwarding class, committed and peak
information rates, etc.) and the mapping of traffic to a forwarding class. A QoS policy
must be created before it can be applied to a SAP. Only a single SAP ingress QoS
policy can be associated with a SAP. If an ingress QoS policy is not assigned to a
SAP, a default ingress QoS policy is assigned by the system.
Scheduler policies define the operating parameters (such as scheduling algorithm,
weights per priority). They are associated with physical ports.
Network QoS policies type port (uplink ingress and egress)
Network Queue QoS policies (egress Uplink port)
Access egress QoS policies
Slope QoS Policies
....................................................................................................................................................................................................................................
1830 PSS
6-33
Issue 1 June 2013
11QPE24 L2 Features
11QPE24 Services
....................................................................................................................................................................................................................................
Service Model
Services are provisioned on the 11QPE24 pack and transported across an

Ethernet/DWDM provider core network. The benefits of the service-centric model
include:
Many services can be bound to a single customer.
QoS policies, filter policies, and accounting policies are applied to each service
instead of correlating parameters and statistics from ports to customers to services.
Service provisioning uses logical entities to provision a service where additional

properties can be configured for bandwidth provisioning, QoS, security filtering to the
appropriate entity.
Service Entities
The basic logical entities in the service model used to construct a service are:
Customers
Service Access Points (SAPs)
Customers
The terms customers and subscribers are used synonymously. The most basic required
entity is the customer ID value which is assigned when the customer account is created.
To provision a service, a customer ID must be associated with the service at the time of
service creation.
Service Access Points (SAPs)
Each subscriber service type is configured with at least one service access point (SAP). A
SAP identifies the customer interface point for a service. The SAP configuration requires
that slot, and port information be specified. The slot and port parameters must be
configured prior to provisioning a service. A SAP is a local entity to the 11QPE24 and is
uniquely identified by:
The physical Ethernet port

The encapsulation identifier (ID) (encapsulation ID identifies the tags used on the
SAP).
Depending on the port encapsulation, a physical port can have more than one SAP
associated with it. SAPs are created on ports designated as access or uplink (network
side
SAP, Port Encapsulation Types, and Identifiers
The port encapsulation type is an access property of a service Ethernet port. The
appropriate encapsulation type for the port depends on the requirements to support
multiple services on a single port and the capabilities of the downstream equipment
connected to the port. For example, a port can be configured for IEEE 802.1Q (referred to
....................................................................................................................................................................................................................................
1830 PSS
6-34
Issue 1 June 2013
11QPE24 L2 Features
11QPE24 Services
....................................................................................................................................................................................................................................
as dot1q) encapsulation in which each individual VLAN tag can be identified with a
service. When a SAP is created, the VLAN tag(s) (or lack of) belonging to the service is
identified by the encapsulation ID. This becomes, after shelf/slot/port, part of the SAP ID.
Ethernet Port Encapsulations
The following lists port encapsulation service options on access Ethernet ports:
Null Supports a single service on the port. For example, a single customer with a
single service customer edge (CE) device is attached to the port. The encapsulation ID
is always 0 (zero).
Dot1q Supports multiple services for one customer or services for multiple
customers. The encapsulation ID used to distinguish an individual service is the
VLAN ID in the IEEE 802.1Q header. For example, the port is connected to an
Ethernet switch with multiple downstream customers.
QinQ The QinQ encapsulation type adds a IEEE 802.1ad or 802.1Q tag to the
802.1Q tagged packets entering the access port to expand the VLAN space, producing
a double tagged frame.
The following lists port encapsulation service options on uplink Network Ethernet
ports:
QinQ The QinQ encapsulation type adds a IEEE 802.1ad or 802.1Q tag to the
802.1Q tagged packets entering the network to expand the VLAN space, producing a
double tagged frame.
SAP types on an Access port

Default SAP on a Dot1q Port
On a dot1q- encapsulated port where a default SAP is configured, all packets with q-tags
not matching any explicitly defined SAPs will be assigned to this SAP. In this context, the
character * (encapsulation ID) indicates default which means allow through. The
default SAP also accepts untagged or priority tagged packets. A default SAP must be
configured explicitly. When a default SAP is not configured explicitly, packets not
matching any explicitly defined dot1q SAPs will be dropped.
Dot1Q Default SAP is represented as follows:
sap C1:*
Where C1 or X1 is the port, the * represents any CVLAN.

This type of SAP is mutually exclusive with a SAP defined by explicit null encapsulation
(for example, 1/1/1:0). This avoids conflict as to which SAP untagged frames should be
associated.
Explicit Null SAP on a Dot1q Port
On a dot1q-encapsulated port where an explicit Null SAP is configured, all untagged or

priority tagged packets will be assigned to this SAP.
....................................................................................................................................................................................................................................
1830 PSS
6-35
Issue 1 June 2013
11QPE24 L2 Features
11QPE24 Services
....................................................................................................................................................................................................................................
Dot1Q Explicit Null SAP is represented as follows:

Sap C1:0
Where C1 or X1 is the port, and the 0 represents untagged or priority packets.

This type of SAP is mutually exclusive with a dot1q Default SAP (for example, C1:*).
This avoids conflict as to which SAP untagged frames should be associated.
Dot1q SAP on a Dot1q Port
On a dot1q- encapsulated port where a SAP is configured, CVLAN- tagged packets

matching the SAP encapsulation ID are assigned to this SAP.
Dot1Q SAP is represented as follows:
Sap C1:10
Where C1 or X1 is the port and the example encapsulation ID 10 represents the CVLAN
of the packets.
Null SAP on a Null Port
On a null encapsulated port where a Null SAP is configured, all packets will be assigned
to this SAP.
One of the applications where this configuration can be applicable is Private Line, an
access connection of a subscriber who uses the whole port. The subscriber's VLAN tags
are transparent to the service provider.
The Null SAP is only supported on a null encapsulated port
Null SAP is represented as follows:
Sap C1
Where C1 or X1 is the port.

SAP types on Uplink port and Access port
QinQ SAPs
QinQ SAP is represented by the port identifier followed by the Q1.Q2 structure, Q1
represent the SVLAN and Q2 represent the CVLAN (the Ethertype configuration
determines whether Q1 is a standard SVLAN or a proprietary tag).
Q1.Q2 SAP: example (sap X1:1000.10) represents a SAP where the SVLAN is equal
to 1000 and the CVLAN is equal to 10. This is normally used when one CVLAN is
mapped to a SVLAN service. Note that the same SVLAN.CVLAN can be configured
on another uplink port SAP for resiliency.
Q.* SAP: example (sap X2:2000.*) represents a SAP where the SVLAN is equal to
2000 and the CVLAN is any value. This is normally used when Untagged or/and
unspecified CVLAN packets are mapped to a service.
....................................................................................................................................................................................................................................
1830 PSS
6-36
Issue 1 June 2013
11QPE24 L2 Features
11QPE24 Services
....................................................................................................................................................................................................................................
Default QinQ SAPs
Default QinQ SAPs (sap 1/1/20: *.*) are used to avoid the need to configure services on
all the intermediate nodes in the ring which are transiting the service. Default QinQ SAPs
matches all SVLAN tagged traffic which is not classified into any other SAP configured
on the same port.
Default QinQ SAP can co-exist with 0.* SAP on an uplink. A default QinQ SAP accepts
only tagged packets. Untagged packets or priority tagged packets are not accepted on
Default QinQ SAPs.
Default QinQ SAP is available for use only in a VPLS service created with svc-sap-type
parameter set to "null-star". Default QinQ SAP can be configured along with other SAPs
allowed in the same service (that is, service with svc-sap-type parameter set to
"null-star").
Note: Default QinQ SAPs in a VPLS service does not support any loop-avoidance
mechanisms such as G.8032. It is not recommended for use in a topology where
Layer-2 loop exists. It must be used carefully and is typically helpful to aggregate a
set of VLANs into a service towards an upstream node in a hub-spoke network
topology without Layer-2 loops.
Service SAP Type
Every service requires a service SAP type; it specifies the type of service and allowed
SAPs in the service:
null-star Specifies that the allowed SAP in the service that can be Null SAP, dot1q
Default SAP, Q.* SAP or Default QinQ SAP (aka *.* SAP).
dot1q Specifies that the allowed SAP in the service are Dot1q SAPs
dot1q-preserve Specifies that the allowed SAP in the service are Dot1q. The Dot1q
ID is not stripped after packets match the SAP.
any When svc-sap-type is set to any, for a explicit NULL SAP, the system
processes and forwards only packets with no VLAN tag (that is, untagged). All other
packets with one or more VLAN tags (even those with priority tag only) are not
processed and dropped. Users can use the service with svc- sap-type set to null-star, to
process and forward packets with one or more tags (including priority tag) on a null
SAP.
The Default svc-sap-type is null-star.

VPLS Service Overview
Virtual Private LAN Service (VPLS) is a class of virtual private network service that
allows the connection of multiple sites in a single bridged domain over a provider-bridge
QinQ network. The customer sites in a VPLS instance appear to be on the same LAN,
regardless of their location. VPLS uses an Ethernet interface on the customer-facing
....................................................................................................................................................................................................................................
1830 PSS
6-37
Issue 1 June 2013
11QPE24 L2 Features
11QPE24 Services
....................................................................................................................................................................................................................................
(access) side which simplifies the LAN/WAN boundary and allows for rapid and flexible
service provisioning. A VPLS service provides connectivity between two or more SAPs.
The connection appears to be a bridged domain to the customer sites so protocols,
including routing protocols, can traverse the VPLS service.
VPLS Features
Alcatel-Lucents VPLS implementation includes several enhancements beyond basic

connectivity. The following VPLS features can be configured individually for each VPLS
service instance:
Extensive MAC and IP filter support. Filters can be applied on a per SAP basis.
Forwarding Information Base (FIB) management features including

Configurable FIB size limit
FIB size alarms
MAC learning disable
Discard unknown
Separate aging timers for learned MAC addresses.
Ingress rate limiting for broadcast, multicast, and destination unknown flooding on a
per SAP basis.
IGMP snooping on a per-SAP basis.
VPLS MAC Learning and Packet
The 11QPE24 pack performs the packet replication required for broadcast, unknown
destination unicast, and multicast traffic across the bridged domain. MAC address
learning is performed by the 11QPE24 to reduce the amount of unknown destination
MAC address flooding. Each 11QPE24 maintains a Forwarding Information Base (FIB)
for each VPLS service instance and learned MAC addresses are populated in the FIB
table of the service. All traffic is switched based on MAC addresses and forwarded
between all participating nodes.
VPLS and Rate Limiting
Traffic that is normally flooded throughout the VPLS can be rate limited on SAP ingress
through the use of service ingress QoS policies. In a service ingress QoS policy,
individual meters can be defined per forwarding class to provide rate-limiting/policing of
broadcast traffic, MAC multicast traffic and unknown destination MAC traffic. For more
info refer to the 11QPE24 Quality of Service PRD document.
Note: On the 11QPE24 card, setting the aggregate meter rate below the sap ingress
meter rate will have no aggregate meter effect.
....................................................................................................................................................................................................................................
1830 PSS
6-38
Issue 1 June 2013
11QPE24 L2 Features
11QPE24 Services
....................................................................................................................................................................................................................................
SAP Encapsulations
VLPS services provide connectivity among SAPs compatible with and associated with
the service. The following SAP encapsulations are supported on the VPLS service:
null
Dot1q
Dot1q Default
Dot1q Explicit Null
The SAP encapsulation definition on Ethernet access ports defines which VLAN tags are
used to determine the service that the packet belongs:
1. Null encapsulation defined on ingress Any VLAN tags are ignored and the packet
goes to a port based service for the SAP.
2. Dot1q encapsulation defined on ingress Only first label is considered.
3. Dot1q Default encapsulation defined on ingress Tagged packets not matching any
of the configured VLAN encapsulations would be accepted. This is like a default SAP
for tagged packets.
4. Dot1q Explicit Null encapsulation defined on ingress Any untagged or priority
tagged packets are accepted.
....................................................................................................................................................................................................................................
1830 PSS
6-39
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the Services CLI commands for 11QPE24. For command details and
Customer Management Commands
customer
contact
phone
description
MAC Filter Commands
filter
mac-filter
default-action
description
scope
entry
action
match
dot1p
dst-mac
etype
src-mac
VPLS Service Commands
vpls
disable-aging
disable-learning
discard-unknown
fdb-table-size
local-age
mfib-table-size
service-name
mc-lag-binding
....................................................................................................................................................................................................................................
1830 PSS
6-40
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
VPLS igmp-snooping Commands
igmp-snooping
query-interval
report-src-ip
query-src-ip
robust-count
Generic Commands
shutdown
description
VPLS SAP Commands
sap
l2pt-termination
max-nbr-mac-addr
statistics
pmon-sap-policy
ingress
counter-mode
llf
static-mac
discard-unknown-source
VPLS SAP QoS Policy Commands and VPLS Filter
ingress
filter
aggregate-meter-rate
qos
VPLS SAP Multicast IGMP Commands
igmp-snooping
query-interval
robust-count
fast-leave
import
last-member-query-interval
max-num-groups
....................................................................................................................................................................................................................................
1830 PSS
6-41
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
max-num-sources
mrouter-port
query-response-interval
send-queries
static
group
source
starg
version
Global Service Show Commands
customer
fdb-info
fdb-mac
service-using
sap-using
VPLS Service Show Commands
id
base
all
fdb
sap
pmon
l2pt
mfib
IGMP Snooping VPLS Show Commands
igmp-snooping
base
mrouters
port-db
querier
static
statistics
all
....................................................................................................................................................................................................................................
1830 PSS
6-42
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Filter Show Commands
mac
....................................................................................................................................................................................................................................
1830 PSS
6-43
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Based on the IEEE 802.1AX standard (formerly 802.3ad), Link Aggregation Groups
(LAGs) are a form of inverse multiplexing of a logical interface to a group of physical
Ethernet links. In a Carrier context, they are used primarily for link protection, and
usually in an active/standby configuration: one link is in service and the other held in
standby in case of link failure. LAGs can also be used to increase the bandwidth available
between two devices, depending on the number of links installed (from 1 to 4), although
how much bandwidth is available depends on how well the traffic can be distributed
among the member links, with the constraint that a particular flow (conversation) must
always use the same link to avoid misordering. Flows are distributed among member
links using a hash function operating on packet parameters such as IP addresses or MAC
addresses.
LAGs can be statically configured or formed dynamically with Link Aggregation Control
Protocol (LACP). The optional marker protocol described in IEEE 802.3ax is not
implemented. LAGs can be configured on where all member ports have the same rate.
LAGs are used for link protection of Ethernet services on UNIs, especially on 10 GbE
handoffs. They can also be used as a form of linear protection for NNI ports. LAGs may
be also be used for ERP paths.
Basic LAG Operation
A LAG is a logical port which behaves the same, from an L2 perspective, as a stand-alone
physical port. Its member ports have no L2 attributes; the LAG has no L1 attributes. For
example, a member port can be mirrored, but not a LAG; a LAG has QoS policies
applied, but not member ports.
The LAG function (traffic collection and distribution among members) can be manually
created, or it can be managed by the Link Aggregation Control Protocol (LACP). Without
LACP, members are always active unless failed. LACP facilitates active/standby
operation, and provides additional capability such as removing any members which are
looped among themselves. Alternatively, the LAG function can operate in the CE at each
end of the network, by 11QPE24 ports which tunnel the LACP messages rather than
terminating them. Up to 20 LAGs may be configured on an 11QPE24, and a LAG may
have as many as four members ports.
....................................................................................................................................................................................................................................
1830 PSS
6-44
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Basic LAG Configuration
LAG configuration guidelines include:
A maximum of 20 LAGs, 4 ports in each, can be configured on the 11QPE24.

Ports can be added or removed from the LAG while the LAG and its ports (other than
the port being removed) remain operational. When ports to and/or from the LAG are
added or removed, the hashing algorithm is adjusted for the new port count. This may
cause a momentary misordering of a flow.
The show commands display physical port statistics on a port-by-port basis or the
entire LAG can be displayed.
LAG is supported on Ethernet ports.
Ports of a particular LAG can be of different types but they must be the same speed
and duplex. To guarantee the same port speed is used for all ports in a LAG,
autonegotiation must be disabled or in limited mode to ensure only a specific speed is
advertised.
Hashing
When a LAG has more than one active member, hashing is used to identify flows and
distribute the flow traffic among the members. For the 11QPE24, if the traffic is IP, then
hashing is based on IP SA and DA, and Source and Destination L4 ports. If it is not IP,
then hashing uses MAC SA and DA, Ethertype, and VLAN ID. In either case, if the
traffic is unlearned, Port ID is added to the hash.
Advanced LAG Operation
The following sections include advanced LAG operation functions.

Port Threshold
The LAG port threshold feature enables the following behavior. If the number of links
available (up) in a LAG is less than or equal to the configured threshold, then the LAG is
becomes operationally down. For example, assume a LAG consists of four physical links
and the threshold is set to two. If the number of operational links is equal to or drops
below two, the link is operationally down until the number of operational links is two or
more.
Active/Standby LAG
This is configured using subgroups. When using subgroups in a LAG, they should only be
configured on one peer of the LAG, not both. Only having one side perform the
active/standby selection guarantees a consistent selection and fast convergence (the
slave-to-partner flag can alternatively be used for this purpose). The active/standby
selection is signaled through LACP to the other side. The hold time should be configured
when using subgroups to prevent the LAG going down when switching between active
....................................................................................................................................................................................................................................
1830 PSS
6-45
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
and standby links in case no links are usable for a short time, especially in case a
subgroup consists of one member. LACP is used to make selection of active links
predictable and compatible with any vendor equipment
In summary, the 11QPE24 implementation of LACP supports the following
A given LAG member can be assigned to sub-groups. The selection algorithm then
assures that only members of a single sub-group are selected as active links.
The selection algorithm is effective only if LACP is enabled on a given LAG. At the
same time, it is assumed that connected system has also LACP enabled (active or
passive mode).
The algorithm will select active links based on following criteria:
Depending on the selection-criteria setting either the sub-group with the highest
number of eligible links or the sub-group with the highest aggregate weight (i.e. sum
of (65535 port priority)) of all eligible members is selected first.
If multiple groups satisfy the selection criteria, the sub-group being currently active
remains active. Initially, the sub-group containing the highest priority eligible link is
selected.
Only links pertaining to a single sub-group are active at any time.
An eligible member refers to a LAG member link which can potentially become
active. This means it is operationally up, and if the slave-to-partner flag is set, the
remote system did not disable its use (by signaling stand-by).
The selection algorithm works in a reverting mode. This means that every time the
configuration or status of any link in a LAG changes, the selection algorithm is re-run.
In case of a tie between two groups (one of them being currently active) the active
group remains active (no reverting).
LAG and QoS Policies
On the 11QPE24, an ingress QoS policy is applied to the aggregate traffic of the LAG.
For example, if an ingress policy is configured with a policer of PIR 100Mb, for a SAP
configured on a LAG with two member ports, then the policer limits the traffic entering
the system through the two ports to a maximum of 100Mb.
Egress QoS policy shaper parameters are applied to all the ports that are members of the
LAG (all ports get the full SLA). For example, if an egress policy is configured with a
policer of PIR 100Mb, each port would get a PIR of 100 Mb. The advantage of this
method over a scheme where the PIR is divided equally among all the member ports of
the LAG, is that a single flow can consume the entire SLA. The disadvantage is that the
overall SLA can be exceeded if the flows span multiple
....................................................................................................................................................................................................................................
1830 PSS
6-46
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the LAG CLI commands for 11QPE24. For command details and
lacp-system-priority
lag
description
encap-type
hold-time
lacp
lacp-xmit-interval
mac
mode
lacp-xmit-stdby
port
priority
subgroup
port-threshold
selection-criteria
shutdown
split-horizon-group
Show Commands
lag
....................................................................................................................................................................................................................................
1830 PSS
6-47
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the MC-LAG CLI commands for 11QPE24. For command details
and parameters, see the Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 6.0
CLI Multi-Chassis Redundancy Commands
redundancy
multi-chassis
source
peer
peer-name
description
shutdown
mc-lag
hold-on-neighbor-failure
keep-alive-interval
lag
flush-eth-ring-when-active
shutdown
sync
igmp-snooping
shutdown
MC-LAG
Sync
Show Commands
redundancy
multi-chassis
....................................................................................................................................................................................................................................
1830 PSS
6-48
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the PMON CLI commands for 11QPE24. For command details and
CLI Configure PMON policies
pmon
Configure SAP PMON policies
pmon-sap-policy
description
bin-15min
bin-1day
tca-15min
tca-1day
ingresspktsdropped
ingressoctetsdropped
CLI Configure Port PMON policies
pmon-port-policy
description
bin-15min
bin-1day
tca-15min
tca-1day
port
queue
ifinpackets
ifoutpackets
ifinoctect
ifoutoctets
ifindiscards
ifoutdiscards
ifinerrors
ifouterrors
....................................................................................................................................................................................................................................
1830 PSS
6-49
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
highcapacitypkts
highcapacityoctets
pktsdropped
octetsdropped
CLI Configure Proactive SLM PMON policies
pmon-slm-policy
description
bin-1day
flr-1day
tca-1day
anflr
xnflr
afflr
xfflr
CLI Configure Proactive DM PMON policies
pmon-dm-policy
description
bin-15min
bin-1day
tca-15min
tca-1day
abfd
xbfd
anfdv
xnfdv
affdv
xffdv
Show Commands
pmon
pmon-sap-policy
pmon-port-policy
pmon-slm-policy
pmon-dm-policy
....................................................................................................................................................................................................................................
1830 PSS
6-50
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the RMD CLI commands for 11QPE24. For command details and
RMD Discovery Commands
rmd-discovery
rmd-access-interface
oui
start
RMD Access Interface Commands
RMD Instance Commands
rmd
description
reset
port
autonegotiate
autonegotiate-fallback
duplex
speed
traffic
forwarding
eth-cfm
mep
ccm-enable
remote-mepid
shutdown
efm-oam
shutdown
....................................................................................................................................................................................................................................
1830 PSS
6-51
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
Show Commands
RMD Discovery
rmd-discovery
Access-Interface
Remote Managed Device
rmd
....................................................................................................................................................................................................................................
1830 PSS
6-52
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the Port CLI commands for 11QPE24. For command details and
Basic Port Commands
port
split-horizon-group
Ethernet Port Commands
ethernet
pmon-port-policy
access
egress
efm-oam
shutdown
accept-remote-loopback
mode
transmit-interval
tunneling
uplink
qos
queue-policy
egress-scheduler-policy
mode
mtu
autonegotiate
duplex
egress-rate
encap-type
lacp-tunnel
qinq-etype
speed
....................................................................................................................................................................................................................................
1830 PSS
6-53
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
pool
slope-policy
Show Commands
port
Port PMON statistics
pmon
....................................................................................................................................................................................................................................
1830 PSS
6-54
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the Clear CLI commands for 11QPE24. For command details and
VPLS Service Clear Commands
clear
service
id
fdb
igmp-snooping
port-db
querier
statistics
counters
sap
Filter Clear Commands
filter
mac
Lag Clear Commands
lag
Port Clear Commands
port
Remote Managed Device Clear Commands
rmd
Performace Monitoring PMON Clear Command
pmon
port
sap
proactive-test
....................................................................................................................................................................................................................................
1830 PSS
6-55
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the Tools CLI commands for 11QPE24. For command details and
tools
perform
eth-ring
clear
force
manual
lag
clear-force
force
MC-LAG Switching Command
force all-mc
clear-force all-mc
force peer-mc
clear-force peer-mc
....................................................................................................................................................................................................................................
1830 PSS
6-56
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

Overview
Following is a list of the General CLI commands for 11QPE24. For command details and
split-horizon-group
description
Show Commands
split-horizon-group
....................................................................................................................................................................................................................................
1830 PSS
6-57
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................

When to use
Use the following procedure to configure Ethernet-Ring (one node). An Ethernet Ring is
built on a topology of 11QPE24 cards which have 10G ports daisy-chained in a closed
ring. As many as 10 Eth-Ring logical instances may be configured on a single 10G
physical ring. For Eth-ring protection, services are assigned to a particular instance
through their uplink SAP configuration.
Before you begin
Prior to performing this task you must:

Have proper user privilege level to perform this task.
Note: Other nodes have complimentary configuration for service access. Most
parameters may be changed as needed, however consistency around the ring is
necessary for:
domain format and level

association ccm-interval
raps-tag
and between link-pairs for:
association name
MEP ID
Any 11QPE24 node in the physical topology which has no service add/drop for some
Eth-rings must have a pass-through service configured on the uplink ports for all
services associated with those Eth-rings, including the ring control services. This can
be done with a single service having default QinQ (*.*) SAPs on the uplink ports at
those nodes.
Customer VPLS services access the ring by having SAPs specifying the ring ID
option when they are created on the uplink ports. For example with CLI, in a vpls
context, the following command could be used to create a SAP on a ring port: sap
1/7/X1:1000.5 eth-ring 13 create.
Create ring instance
Note: CLI commands are:

config card 11qpe24 <1/7> eth-ring <13>
exit
....................................................................................................................................................................................................................................
1830 PSS
6-58
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
WebUI procedure:
...................................................................................................................................................................................................
On the equipment tree, select Ethernet Rings under the 11QPE24 card to display the
Ethernet Rings page.
...................................................................................................................................................................................................
Select the Create button to display the Create Ethernet Ring page.
...................................................................................................................................................................................................
Create an Ethernet Ring with:
Ethernet Ring ID = <13>
RPL Node = <Owner>
E...................................................................................................................................................................................................
N D O F S T E P S
Configure uplink ports for ring instance
Note: CLI commands are:

config card 11qpe24 <1/7/X1> X1 ethernet
mode access uplink
encap-type qinq
exit all
config card 11qpe24 <1/7/X2> ethernet
mode access uplink
encap-type qinq
exit all
WebUI procedure:
...................................................................................................................................................................................................
On the equipment tree, select X1 under the 11QPE24 card to display the Unprovisioned
Port page.
...................................................................................................................................................................................................
After the port is successfully provisioned, select the Ethernet Port tab.
Set Mode= Uplink. Encapsulation Type will automatically be set to QinQ when the
request is submitted.
....................................................................................................................................................................................................................................
1830 PSS
6-59
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Repeat Steps 1 and 2 for port X2.

E...................................................................................................................................................................................................
N D O F S T E P S
Configure Eth-CFM for ring control
Note: The downstream nodes will instantiate peer MEPs 3 and 4 on their paths.
CLI commands are:
config card 11qpe24 <shelf/slot> eth-cfm
domain <99> format none level <1>
association <1> format icc-based name <ring-13-east->
ccm-interval 3.3ms
remote-mepid 3
exit
association 2 format icc-based name <ring-13-west->
ccm-interval 3.3ms
remote-mepid <4>
exit all
WebUI procedure:
...................................................................................................................................................................................................
On the equipment tree, select MEPs under the 11QPE24 card to display the Maintenance
Domains page.
...................................................................................................................................................................................................
Select the Create button to display the Create Maintenance Domain page.
...................................................................................................................................................................................................
Create a Maintenance Domain with:
Index = 99
Format = None
Level = 1
...................................................................................................................................................................................................
Go back to the Maintenance Domains page and select the created Maintenance Domain
(Index=99) in the table.
....................................................................................................................................................................................................................................
1830 PSS
6-60
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the Maintenance Associations button to display the Maintenance Associations

page.
...................................................................................................................................................................................................
Select the Create button to display the Create Maintenance Association page.
...................................................................................................................................................................................................
Create a Maintenance Association with:
Index = 1
Format = ITU ICC
CCM Interval = 3.33 ms
Name = ring-13-{east}
...................................................................................................................................................................................................
Go back to the Maintenance Associations page and select the created Maintenance
Association in the table.
...................................................................................................................................................................................................
Select the Remote MEPs buton to display the Remote MEPs page.
...................................................................................................................................................................................................
10
Select the Create button to display the Create Remote MEP page.
...................................................................................................................................................................................................
11
Create Remote MEP ID= 3.

...................................................................................................................................................................................................
12
Repeat Steps 4-11 to create another Maintenance Association with:
Index = 2
Format = ITU ICC
Name = ring-13-west
CCM Interval = 3.33 ms
Remote MEP ID = 4
E...................................................................................................................................................................................................
N D O F S T E P S
Create VPLS and SAPs for ring control
Note: This is not used for customer service data.

CLI commands are:
....................................................................................................................................................................................................................................
1830 PSS
6-61
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
config card 11qpe24 <shelf/slot> vpls <99> customer <2> svc-saptype any create
sap <1/7/X1:4093.4094> eth-ring <13> create
exit
sap <1/7/X2:4093.4094> eth-ring <13> create
exit all
WebUI procedure:
...................................................................................................................................................................................................
On the equipment tree, select Services under the 11QPE24 card to display the Services
page.
...................................................................................................................................................................................................
Select the VPLS tab to display the VPLS page.

...................................................................................................................................................................................................
Select the Create button to display the Create VPLS page.

...................................................................................................................................................................................................
Create a VPLS with:
Service ID = 99
Customer ID = 2
SAP Type = Any
...................................................................................................................................................................................................
Go back to the VPLS page and select the created VPLS (ID = 99) in the table.
...................................................................................................................................................................................................
Select the SAPs button to display the Service Access Points page.
...................................................................................................................................................................................................
Select the Create button to display the Create SAP page.

...................................................................................................................................................................................................
Create a SAP with:
Port ID = X1
SVLAN ID = 4093
CVLAN ID = 4094
Ethernet Ring ID = 13
....................................................................................................................................................................................................................................
1830 PSS
6-62
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Create another SAP with:
Port ID = X2
SVLAN ID = 4093
CVLAN ID = 4094
Ethernet Ring ID = 13
E...................................................................................................................................................................................................
N D O F S T E P S
Configure ring path details
Note: One node in the ring needs to be configured as rpl-node owner, and one path the
rpl-end, shown below. The node at the other end of the rpl-end path must be
configured as rpl-node nbr.
CLI commands are:
config card 11qpe24 <1/7> eth-ring <13>
rpl-node owner
path a <X1> raps-tag <4093.4094>
rpl-end
eth-cfm
mep <1> domain <99> association <1>
ccm-enable
control-mep
no shutdown
exit
exit
no shutdown
exit
path b <X2> raps-tag <4093.4094>
eth-cfm
mep <2> domain <99> association <2>
ccm-enable
control-mep
....................................................................................................................................................................................................................................
1830 PSS
6-63
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
no shutdown
exit
exit
no shutdown
exit
no shutdown
exit
WebUI:
...................................................................................................................................................................................................
For WebUI, follow the procedures below.

E...................................................................................................................................................................................................
N D O F S T E P S
WebUI procedure - Configure the Ring Paths

1. On the equipment tree, select Ethernet Rings under the 11QPE24 card.
2. Select the created Ethernet Ring (ID=<13>).
3. Select the Ethernet Ring Paths button.
4. Select the Create button to display the Create Ethernet Ring Path page.
5. Create Path A with:
Path ID = Path A
Port Name = X1
RAPS SVLAN ID = 4093
RAPS CVLAN ID = 4094
Path Type = RPL End
6. Create Path B with:

Path ID = Path B
Port Name = X2
RAPS SVLAN ID = 4093
RAPS CVLAN ID = 4094
Path Type = Normal
....................................................................................................................................................................................................................................
1830 PSS
6-64
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
WebUI procedure - Configure the MEPs

1. On the equipment tree, select MEPs under the 11QPE24 card to display the
Maintenance Domains page
2. Select the created Maintenance Domain in the table (Index = 99).
3. Select the Maintenance Associations button to display the Maintenance
Associations page.
4. Select the Maintenance Association with Index = 1 in the table.
5. Select the MEPs button to display the Maintenance End Points page.
6. Select the Create button to display the Create Maintenance End Point page.
7. Create a MEP ID with:
MEP ID = 1
Direction = Down
Interface Type = Ethernet Ring Path
Interface = Eth Ring 13: Path A X1:4093.4094
MEP Active = Checked
CCM Enabled = Checked
8. When the MEP is successfully created, select the created MEP from the Maintenance
End Points table and select the Details button
9. Modify the following on the MEP:
Control MEP Enabled = Checked.
10. Repeat Steps 4-9 to create another Maintenance End Point on Maintenance
Association (Index = 2) with:
MEP ID = 2
Direction = Down
Interface Type = Ethernet Ring Path
Interface = Eth Ring 13: Path B X2:4093.4094
MEP Active = Checked
Control MEP Enabled = Checked.
CCM Enabled = Checked
WebUI procedure - Put the Ring in service

1. On the equipment tree, select Ethernet Rings under the 11QPE24 card.
2. Select the created Ethernet Ring (ID=13) and select the Ethernet Ring Paths button.
3. Select Path A in the table and select the Details button to display the Ethernet Ring
Path Details page.
....................................................................................................................................................................................................................................
1830 PSS
6-65
Issue 1 June 2013
11QPE24 L2 Features
....................................................................................................................................................................................................................................
4. Set Admin State = Up.

5. Repeat steps 3 and 4 for Path B.
6. On the Ethernet Rings page, select the created Ethernet Ring (ID=13).
7. Select the Details button to display the Ethernet Ring Details page.
8. Set Admin State = Up.
....................................................................................................................................................................................................................................
1830 PSS
6-66
Issue 1 June 2013
7 larm management
A
procedures
Overview
Purpose
The present chapter describes the procedures which have to be performed for the alarm
management of the Alcatel-Lucent 1830 PSS network elements
Alarm management in a combined OCS/WDM system
In a combined system, the Alcatel-Lucent 1830 PSS ZIC has one alarm list that contains
both OCS and WDM alarms.
Contents
7-3
Procedure 7-1: View NE alarms
7-3
7-5
Procedure 7-2: Create an Alarm Severity Assignment Profile (ASAP)
7-7
Procedure 7-3: Display Alarm Assignment Profiles
7-10
Procedure 7-4: Display Alarm Assignment Profiles assigned to specific entities
7-11
7-12
Procedure 7-6: Manage ASAP profile assigned to a specific entity
7-14
7-16
7-18
7-19
Introduction
7-19
Procedure 7-9: Display active alarm list
7-23
Alarm List
7-24
7-25
...................................................................................................................................................................................................................................
1830 PSS
7-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 7-11: Display active alarms or alarm level on a shelf or slot/card
7-26
7-27
Alarms Log
7-28
Procedure 7-13: View events history log
7-29
General Events Log
7-30
7-31
Alarmable Conditions
7-32
Procedure 7-15: Provision environmental (housekeeping) alarms
7-35
Environmental Alarms
7-36
....................................................................................................................................................................................................................................
1830 PSS
7-2
Issue 1 June 2013

View NE alarms
....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve detailed information about the current alarm status of a
Alcatel-Lucent 1830 PSS NE.
RTRV-ALM-ALL
Before you begin

Required privileges
You must have at least a User Community Authorization Level of 1 to perform this task.
Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select the bell symbol on the tool bar
or select Navigation Show Alarms from the main menu bar.
Result: The Alcatel-Lucent 1830 PSS ZIC View Current Alarms and Conditions
window opens.
Any reported alarm in the system is displayed.
....................................................................................................................................................................................................................................
1830 PSS
7-3
Issue 1 June 2013

....................................................................................................................................................................................................................................
Reference: See View Current Alarms And Conditions (p. 7-5).

...................................................................................................................................................................................................
To filter the displayed alarms and conditions you can select from the following options
using the Show spin box below the table:
All
Any reported alarm and condition in the system is displayed.
Active Alarms
All active alarms (CR, MJ, MN, WR) are displayed.
Standing Conditions
All not alarmed, not reportdet conditions are displayed.
Suppressed Alarms
All alarms which are suppressed by AINS are displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-4
Issue 1 June 2013

....................................................................................................................................................................................................................................

Purpose
The View Current Alarms And Conditions window serves to retrieve the current status of
any reported, alarmed, not alarmed or not reported conditions (also referred to as events
in the following) for a particular system component.
Parameters
Parameter
Value
Description
Name
Alphanumeric string of up to 20
characters.
The user-friendly name of the

system component.
Note that letters are always displayed

in uppercase.
Compound
Possible values:
OCS
WDM
Depicts the compound from

which the condition is reported.
AID Type
Please see Overview of access


system component.
Notification Code
CR - Critical
The type of alarm generated by

the system upon occurrence of
the event.
MJ - Major
MN - Minor
WR - Warning
NA - Not Alarmed
NR - Not Reported
Condition Type
Please see Condition types (p. 5-450).
Description
1-10 lines of up to 64 valid output

characters per line
An optional, non- parsable text

description of the condition or
problem being reported.
Service Affecting
NSA - Non service-affecting
The effect on service caused by

the event.
SA - Service-affecting
Date Occured
Month and day in the form 'mm-dd'
Time Occured
Hour, minute and second in the form

'hh-mm-ss'
Date and time when the event

occurred.
....................................................................................................................................................................................................................................
1830 PSS
7-5
Issue 1 June 2013

....................................................................................................................................................................................................................................
Parameter
Value
Description
Location
NEND (Near end)
The location where the

condition type is monitored.
Please also see Condition
types (p. 5-450).
FEND (Far end)
Direction

Monitored Value
(for TCAs only)
Threshold Level
(for TCAs only)
Time Period
1-day
(for TCAs only)
15-minutes
The direction to which the

condition type relates to. Please
also see Condition types
(p. 5-450).
The threshold level for the
The accumulation period for
performance monitoring
information (1-day or
15-minutes count).
....................................................................................................................................................................................................................................
1830 PSS
7-6
Issue 1 June 2013

Procedure 7-2: Create an Alarm Severity Assignment Profile

(ASAP)
....................................................................................................................................................................................................................................

(ASAP)
When to use
Use this procedure to create an Alarm Severity Assigned Profile (ASAP) instance for a
given profile type.
The ASAP is created as a clone of the factory default ASAP of the given type.
ENT-ASAP-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To create EQPT profiles, select the equipment node in the Alcatel-Lucent 1830 PSS ZIC
selection tree.
To create facility profiles, select the respective facility node in the Alcatel-Lucent
1830 PSS ZIC selection tree.
To create BITS, TIMING and NETIF profiles select System in the Alcatel-Lucent
1830 PSS ZIC selection tree
...................................................................................................................................................................................................
Then select Alarm Profiles Create, either by selecting Action from the main menu bar
....................................................................................................................................................................................................................................
1830 PSS
7-7
Issue 1 June 2013


(ASAP)
....................................................................................................................................................................................................................................
Result: The Alarm Assignment Profile Creation Dialog window is displayed.

...................................................................................................................................................................................................
Using the Profile Type drop down list box select the ASAP type for the ASAP that shall
be created.
Possible values are, when System was selected:
BITS
IPIPT
LAN
NETIF
TIMING
...................................................................................................................................................................................................
Using the drop down list box Set as Default specify if the created ASAP shall become the
default ASAP for the entered ASAP type or not.
Yes
No
Note: It isnt necessary to apply a value for Set as Default. If nothing is selected the
new profile is created with the default values.
Note: It isnt necessary to apply a value for Clone From. If nothing is selected the
...................................................................................................................................................................................................
In the field User Label enter as string to address the ASAP in place of the AID.
Note: It isnt necessary to apply a value for User Label. If nothing is selected the new
profile is created with the default values.
Allowed characters are alphanumerics and dashes (-).
...................................................................................................................................................................................................
Using the drop down list box Clone From specify the index of the system-defined ASAP
instance to be cloned.
All Disabled
All Enabled
FERF and AIS Disabled
Non-Primary Disabled
System Default
Note: It isnt necessary to apply a value for Clone From. If nothing is selected the
....................................................................................................................................................................................................................................
1830 PSS
7-8
Issue 1 June 2013


(ASAP)
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-9
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to display Alarm Assignment Profiles.

RTRV-ASAP-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To display EQPT profiles, select the equipment node in the Alcatel-Lucent 1830 PSS ZIC
selection tree.
To display facility profiles, select the respective facility node in the Alcatel-Lucent
To display BITS, TIMING and NETIF profiles select System in the Alcatel-Lucent
...................................................................................................................................................................................................
Then select Alarm Profiles View Assignments, either by selecting Action from the
Result: The View Assignment Profile window is displayed showing Alarm
Assignment Profiles.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-10
Issue 1 June 2013

Procedure 7-4: Display Alarm Assignment Profiles assigned

to specific entities
....................................................................................................................................................................................................................................
Procedure 7-4: Display Alarm Assignment Profiles assigned to

specific entities
When to use
Use this procedure to display Alarm Assignment Profiles assigned to specific entities.
RTRV-ASAP-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To display Alarm Assignment Profiles assigned to a specific entity, select the entity in the
Alcatel-Lucent 1830 PSS ZIC selection tree.
...................................................................................................................................................................................................
Then select Properties Alarm Severity View, either by selecting Action from the
Result: The Alarm Severity window is displayed showing the Alarm Assignment
Profile assigned to the specific entity.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-11
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to edit an ASAP profile.

ED-ASAP-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To manage EQPT profiles, select the equipment node in the Alcatel-Lucent

To manage facility profiles, select the respective facility node in the Alcatel-Lucent
To manage BITS, TIMING and NETIF profiles select System in the Alcatel-Lucent
...................................................................................................................................................................................................
Then select Alarm Profiles Manage, either by selecting Action from the main menu
Result: The Show All Alarm Assignment Profile window is displayed.
...................................................................................................................................................................................................
Select one of the Alarm Assignment Profiles.

You can now modify or delete the selected Alarm Assignment Profile.
...................................................................................................................................................................................................
Click Modify.
....................................................................................................................................................................................................................................
1830 PSS
7-12
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Edit Alarm Profile window is displayed.

...................................................................................................................................................................................................
Using the drop down list box Promote as Default specify if the created ASAP shall
become the default ASAP for the entered PFTYPE or not.
Yes
No
...................................................................................................................................................................................................
In the field User Label enter as string to address the ASAP in place of the AID.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-13
Issue 1 June 2013

Procedure 7-6: Manage ASAP profile assigned to a specific

entity
....................................................................................................................................................................................................................................

entity
When to use
Use this procedure to edit an ASAP profile assigned to a specific entity.

ED-ASAP-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To manage Alarm Assignment Profiles assigned to a specific entity, select the entity in the
Alcatel-Lucent 1830 PSS ZIC selection tree.
...................................................................................................................................................................................................
Then select Properties Alarm Severity Set, either by selecting Action from the main
Result: The Edit Alarm Profile Pointer window is displayed showing Alarm
Assignment Profile assigned to the specific entity.

...................................................................................................................................................................................................
Using the drop down list box Alarm Porfile select the ASAP to be assigned to the selected
entity.
...................................................................................................................................................................................................
Using the drop down list box Mode select the command execution mode.
Forced
Normal
....................................................................................................................................................................................................................................
1830 PSS
7-14
Issue 1 June 2013


entity
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-15
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to edit notification code.

ED-ASAP-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
To edit EQPT profiles, select the equipment node in the Alcatel-Lucent 1830 PSS ZIC
selection tree.
To edit facility profiles, select the respective facility node in the Alcatel-Lucent
To edit BITS, TIMING and NETIF profiles select System in the Alcatel-Lucent
...................................................................................................................................................................................................
Then select Alarm Profiles Edit, either by selecting Action from the main menu bar or
Result: The Edit Alarm Assignment Profile window is displayed.
...................................................................................................................................................................................................
Select an ASAP
...................................................................................................................................................................................................
Click Modify.
....................................................................................................................................................................................................................................
1830 PSS
7-16
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Edit Alarm Assignment Profile window is displayed.

...................................................................................................................................................................................................
Using the drop down list box Notification Codes specify the notification code
CR
Critical alarm
MJ
Major alarm
MN
Minor alarm
WR
Warning Alarm
NA
Not Alarmed
NR
Not Reported
DFLT
Factory Default Value

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-17
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete an Alarm Severity Assigned Profile (ASAP) instance for a
given profile type.
DLT-ASAP-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectSystem ,Facilities or Equipment
Then select Alarm Profiles Manage, either by selecting Action from the main menu
Result: The Show All Alarm Assignment Profiles window is displayed.
...................................................................................................................................................................................................
Select the Alarm Assignment Profile to be deleted.

...................................................................................................................................................................................................
Click Delete.
...................................................................................................................................................................................................
Click Yes to confirm your settings.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-18
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................

Introduction
Alarm operation
An alarm is a notification of a failure and also an external visible indication of a failure

by enabling the contact closure on the alarm grid. An autonomous message is generated to
report the alarm and the FAULT LED on the circuit pack or user panel may be turned on
or made to blink depending on the severity and type of alarm.
The main focus in alarm management is to present the user with the current alarms of
Alcatel-Lucent 1830 PSS in summaries and different views, so that the user gets a quick
overview of the state of the NE. These views also support the user in analyzing fault
conditions and quickly finding a solution for the problem. The following conditions apply
to alarm operation:
Trouble notifications are provided for and distinguish between equipment failures and
incoming signal failures.
Local notifications are consistent with the remote notifications for the same trouble.
Any single failure results in only one alarmed output message.
The system supports two modes for alarm reporting: SONET and SDH. The mode of
alarm reporting is defined by the system level MODE parameter.
The system supports autonomous reporting and logging of alarms and conditions for
equipment and facilities. All currently existing alarmed, not alarmed, and not reported
events are retrievable via all user interfaces.
When an entity is deleted, all of its associated alarms and conditions are cleared.
When an entity is not provisioned, no alarms or conditions are set against that entity.
If a condition error is associated with a non-provisioned entity, then it is set against
the SLOT entity with the same instance of the non-provisioned entity.
When an entity is logically removed (placed in OOS-[AU]MA state), clear messages
are sent for all the outstanding conditions on that entity that were autonomously
reported, except for the off-normal conditions. However, outstanding conditions on
that entity will still be retrievable.
Alarm severity management
You can change the default alarm severity for an alarm condition on a specific entity (for
example a port) or for all entities of the same type. While alarm severity is modifiable, the
service-affectedness of the condition cannot be modified.
....................................................................................................................................................................................................................................
1830 PSS
7-19
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
The NE allows default alarm severities to be modified via all supported user interfaces,
and all user interfaces provide a means of reverting to the default alarm severities. All
user interfaces provide a means of listing the severities in effect.
The NE supports the following condition severities (notification codes) which are
reported to maintenance and operations personnel responsible for the equipment:
Critical (CR)
Major (MJ)
Minor (MN)
Warning (WR)
Not-Alarmed (NA)
Alarm reporting
The system supports autonomous reporting and logging of all alarms and conditions and
management and retrieval of alarm logs is available. Each trouble requiring craftsperson
action results in an alarm condition and is reported by three concurrent methods:
Automatic output message

Visual indication at NE
Audible and visual indications under the control of the NE
A trouble not requiring craftsperson action is reported via an automatic output message.
Incoming signal failures generate alarmed trouble notifications. Transient events (e.g.,
threshold crossing alerts) generate not-alarmed notifications as the default.
Each automatic output message includes, as a minimum, the following information:
The time the event occurred.

The trouble type (e.g. loss of signal).
Identification of the failed NE or the NE in which the failed unit resides.
Identification of the NE's affected replaceable element.

Designation as service-affecting or non-service-affecting.
Designation as alarmed or non-alarmed.
For alarmed events, the severity of the trouble (i.e. critical, major or minor).
After an autonomously reported standing condition has been cleared, an automatic output
message is generated by the NE indicating that the alarmed condition has been cleared.
The automatic output message has the same priority as that reported in the original alarm.
....................................................................................................................................................................................................................................
1830 PSS
7-20
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
The colors red, amber, yellow, cyan, and green indicating the severity of the trouble are
used on an NE's physical control/status display panel to visually represent various alarm
levels and status conditions at the NE's equipment location. The alarm LEDs for an entity
on the NE are lit according to the alarm level(s) being asserted by the NE. The level
priorities are:
Critical
Major
Minor
Warning
None
Alarm hierarchy
For non-independent failures, only the highest trouble in the alarm hierarchy will be
reported. When a higher level alarm clears and lower level problems persist that were not
alarmed, the lower level problem will be alarmed. The timestamp of the alarm will be the
detection time of the problem not that of the higher level alarm clearing.
When a lower level alarm is cleared due to a logical removal of the entity, then it can be
retrieved by the related condition retrieval command. Its timestamp will be the time of the
command that logically removed the entity. If re-raised (logically inserted again) the
timestamp will be the time of original problem detection, not the time the logical insertion
occurred.
Equipment/ facility alarms
Equipment and facility failures are classified as either service-affecting (SA) or non
service-affecting (NSA), depending on whether they affect the service that the equipment
transports. Detectable faults on a module that affect the operation of that module results in
an alarm generated against the failed module. An error occurring between two pieces of
equipment results in an alarm on the receiving/detecting equipment.
Audible alarms
The NE provides audible alarm dry contacts and alarm cut-off capability. The alarm
cut-off function (in the alarm area of the WebUI toolbar) removes the signal from the dry
contacts, but does not affect the internal state of the NE, nor affect any of the visual
indicators.
Environmental (housekeeping) alarms
The NE provides eight input sensors and four output controls for status and management
of customer external equipment and environment. Upon successful provisioning of the
main shelf on an NE, all External Control Output Points (CPO) and all External Control
....................................................................................................................................................................................................................................
1830 PSS
7-21
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Input Points (CPI) are automatically created. Housekeeping (HKP) alarm provisioning is
persistent and stored in the database. If customer controls are active prior to a system
reset, they remain active through the reset and maintain their prior state following the
reset. On restoration of a backup database, customer controls are restored to their state at
the time of backup .
It is possible to configure user labels for each alarm input and control output for message
purposes on all user interfaces (via the local terminal and element manager). The labels
consist of ASCII text fields up to 30 characters. It is possible to modify each label at any
time.
Input sensors
The NE can receive and process eight separate customer-defined inputs for fault
conditions arising externally to the NE. These fault conditions are processed and reported
the same as for internally detected fault conditions. It is possible to disable the reporting
from any input if not used. The inputs are normally used for site specific alarms such as
open door, high temperature, high water level, etc. The system issues a database change
event when the HKP provisioning is updated.
Output controls
The NE drives four separate output station controls for customer defined site specific
facilities external to the NE, such as air conditioning, generators, etc. Operating an
external control means that a relay is activated to control some external device. Releasing
an external control means deactivating the relay. The polarity of an external output
control determines the relationship between the control state value and the physical signal
The states of the control relays are persistent through a restart or protection switch. That
is, at the completion of the restart or protection switch, the state of the outputs remain the
same as before the restart or protection switch. During the time that the NE restarts or
switch activity is in process, if the control relay states cannot be maintained, then they
default to the open contact state.
....................................................................................................................................................................................................................................
1830 PSS
7-22
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to display the active alarm list.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Reports > Alarm List > {Total, Critical, Major, Minor}
Note: Alarms can also be selected via the alarms display area on the WebUI toolbar.
Result: The selected alarms are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-23
Issue 1 June 2013

Alarm List
....................................................................................................................................................................................................................................
Alarm List
Attribute
Value/Format
Additional Info
Time
<date time>

the alarm was raised.
Source
<shelf/slot/port>

on which the alarm occurred.
Card

alarm occurred.
Category

component where the alarm
occurred.
Severity
Critical
Major
Indicates the severity of the

reported alarm.
Minor
Warning
Description
<0-255 chars>
Condition
SA
Identifies the type of alarm

being reported.
Yes
No
Data

reported alarm.
<0-255 chars>
Indicates if the alarm affects

service.
alarm.
....................................................................................................................................................................................................................................
1830 PSS
7-24
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view the condition list.

Before you begin
Instructions
The WebUI displays a list of all active conditions on the NE. The WebUI will allow the
user to filter the list based on Severity.
...................................................................................................................................................................................................
In the WebUI, select Reports > Condition List.

Result: The Condition List is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-25
Issue 1 June 2013

Procedure 7-11: Display active alarms or alarm level on a

shelf or slot/card
....................................................................................................................................................................................................................................
Procedure 7-11: Display active alarms or alarm level on a

shelf or slot/card
When to use
Use the following procedure to display active alarms or alarm level on a shelf or slot/card.
Before you begin
Instructions
Note: The WebUI will display a list of all active alarms on the selected shelf or
slot/card and all entities hierarchically below.
...................................................................................................................................................................................................
From the WebUI equipment tree, select the shelf or slot/card. Click the Fault function.
Result: The Alarm List/Alarm Level is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-26
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view alarms history log.

Before you begin
Instructions
The WebUI supports the following alarms history logs: All, Critical, Major, Minor, Not
Reported, Not Alarmed, Warning.
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Alarms > {All Alarms, Critical Alarms, Major
Alarms, Minor Alarms, Not Reported, Not Alarmed, Warnings}.
Result: The respective Alarms Log is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-27
Issue 1 June 2013

Alarms Log
....................................................................................................................................................................................................................................
Alarms Log
Attribute
Value/Format
Additional Info
Number
{1-2,147,483,647}

sequence when the
the NE.
Severity
Critical
Indicates the severity of the

reported alarm.
Major
Minor
Warning
Not Alarmed
Not Reported
Time
<date time>

the alarm was raised.
Source
<shelf/slot/port>

on which the alarm occurred.
Card

alarm occurred.
Category

occurred.
Description
<0-255 chars>
Condition
SA
Identifies the type of alarm

being reported.
Yes
No
Data

reported alarm.
<0-255 chars>
Indicates if the alarm affects

service.
alarm.
....................................................................................................................................................................................................................................
1830 PSS
7-28
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view events history log.

Before you begin
Instructions
The WebUI supports the following Event history logs: General, State Changes, User
Actions.
...................................................................................................................................................................................................
In the WebUI, select Reports > Logs > Events > {General, State Changes, User
Actions}.
Result: The respective Events Log is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-29
Issue 1 June 2013

General Events Log
....................................................................................................................................................................................................................................
General Events Log

Attribute
Value/Format
Additional Info
Number
{1-2,147,483,647}

sequence when the
the NE.
Time
<date time>

the event was raised.
Source
Identifier of the
component/area on which the
event occurred.
Card

event occurred.
Description
<0-255 chars>

reported event.
Data
<0-255 chars>

event.
....................................................................................................................................................................................................................................
1830 PSS
7-30
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to modify alarm configuration.

Before you begin
Instructions
Note: A user may modify the shelf, card, and port level alarm severity for a selected
condition type. A user may revert to the default severity for all condition types of a
specified category.
...................................................................................................................................................................................................
In the WebUI, select System from the equipment tree and click the Fault function.
Result: Alarmable Conditions screen is displayed.
...................................................................................................................................................................................................
Select a Category and click Retrieve.

Result: The Condition Types are displayed.
...................................................................................................................................................................................................
Select Severity Level and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-31
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute Name
Value/Format
Additional Info
Condition
[List of all alarm conditions

applicable to this network
element.]
Identifies the type of alarm.
Override Severity
None
User-configured value for the

alarm severity.
Critical
Major
Minor
Warning
Not Alarmed
Not Reported
Default Severity
Critical
Major
System default value for the

alarm severity.
Minor
Warning
Not Alarmed
Not Reported
....................................................................................................................................................................................................................................
1830 PSS
7-32
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute Name
Value/Format
Additional Info
Category
1GbE

occurred.
10GbE
100GbE
40GbE
E1 applicable to PSS-4 only.
BITS
CBR2G5
CBRAR
COM
DDR
E1
ENV
ERP
EQPT
FC100
FC200
FC400
FC800
FC1200
FE
LAG
LINEREF
MEP
OC3/STM1
OC12/STM4
OC48/STM16
OC192/STM64
OC768/STM256
OCH
ODU0
ODU1
ODU2
ODU3
ODU4
ODUF
OMS
....................................................................................................................................................................................................................................
1830 PSS
7-33
OPTSG
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute Name
Value/Format
(continued)
OTS
Additional Info
OTU1
OTU2
OTU3
OTU4
PLK
PTPCLOCK
PTPPORT
RMD
RMDIF
RMDIFMAU
RMDMEP
SAP
SVC
SYNC
TOD
TRU
VTS
....................................................................................................................................................................................................................................
1830 PSS
7-34
Issue 1 June 2013

Procedure 7-15: Provision environmental (housekeeping)

alarms
....................................................................................................................................................................................................................................
Procedure 7-15: Provision environmental (housekeeping)

alarms
When to use
Use the following procedure to provision environmental (housekeeping) alarms.

Before you begin
Instructions
For Alcatel-Lucent 1830 PSS-32 and Alcatel-Lucent 1830 PSS-16, the WebUI supports
provisioning of environmental alarms and external controls on the USRPNL card. For the
1830 PSS-32S shelf, environmental alarms and external controls are supported on the
HKPCNTL card. Once provisioned, the user can operate or release the control(s).
Attributes can be set for each port.
...................................................................................................................................................................................................
In the WebUI expand the equipment tree to select System > PSS-32 Shelf > USRPNL and
click on the Alarm Level tab.
Result: The Alarm List screen is displayed.
...................................................................................................................................................................................................
Click on the Environmental Alarms tab.

Result: The Environmental Alarms screen is displayed.
...................................................................................................................................................................................................
Enter parameters and click Submit.

...................................................................................................................................................................................................
Click on the External Controls tab.

Result: The External Controls screen is displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
7-35
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Port
PSS-4: {1-3}
Identifies the Housekeeping

output port on the USRPNL
for PSS-32 and PSS-16
shelves, and PF for PSS-4
shelves.
PSS-16: {1-6}
PSS-32: {1-8}
Alarm Message
<0-56 chars>
Descriptive text included in

the alarm message.
Polarity
Active High
Indicates when the alarm is

active.
Active Low
....................................................................................................................................................................................................................................
1830 PSS
7-36
Issue 1 June 2013
8 DM timing provisioning
T
procedures
Overview
Purpose
This chapter describes the procedures which have to be performed for the configuration
of the system timing of the Alcatel-Lucent 1830 PSS.
Related information
In an optical transport network (OTN), network synchronization can be transported

transparently within the client signals. Hence, no network synchronization chains are
necessary, and the demands on synchronization are lower than those of an SDH/SONET
network, for example. As the individual nodes of an OTN are independent from each
other regarding their system timing, it is sufficient to operate the internal oscillators in
free-running mode for timing purposes. To summarize synchronization and timing for
Alcatel-Lucent 1830 PSS Release 6.0.0:
System timing can be derived from internal oscillators, operated in free-running

mode. The frequency stability in the free-running mode is better than 4.6 ppm, in
compliance with the ITU-T Recommendation G.813, Option 1.
Synchronization interfaces for external timing references are supported.
Important! External synchronization is mandatory for a shelf which provides
SDH/SONET switching functionality. In Release 6.0.0 only E1 (SDH) respectively
DS1 (SONET) external timing is supported.
Contents
8-3
8-5
8-8
8-12
8-15
...................................................................................................................................................................................................................................
1830 PSS
8-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
8-18
8-22
8-24
8-27
Procedure 8-7: Take an external timing reference out of service for maintenance
purposes
8-30
Procedure 8-8: Take an external timing input port out (BITS) out-of-service
8-32
8-34
8-36
Procedure 8-11: Retrieve provisioning and state information of external timing

references
8-38
Procedure 8-12: Retrieve provisioning and state information of external timing

input ports
8-39
8-41
8-43
....................................................................................................................................................................................................................................
1830 PSS
8-2
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to configure the timing references.

Related TL1 command
ED-SYNCN.
Related information
The system timing entity controls the timing selection. It covers everything related to the
NE internal clock and the system timing selection process.
One instance will be created/deleted in the context shelf provisioning/de-provisioning.
The timing reference covers a timing source which is used as input for the system timing
selection process.
2 instances ( 2 EXTERNAL timing references) are created/deleted in the context shelf
provisioning/de-provisioning
Each timing reference can be assigned (that means connected) to a port.
The following port types can be assigned to a timing reference:
BITS port (that means external timing reference) The clock reference selections
controlled by this command are applied uniformly to both CRUs.
Omitting a reference from assignment, if it is currently the active reference on CRG,

causes CRG to switch to another reference or to Holdover.
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
8-3
Issue 1 June 2013
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
If you want to configure ..
Then ...
the external timing references,
see Procedure 8-3: Configure external timing

references (p. 8-15).
the Timing Node within the Shelf.
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System Internal Sync
System Timing
In the main window select SYNC-1-1-0.

...................................................................................................................................................................................................
The select Properties General, either by selecting Action from the main menu bar or
Result: The Alcatel-Lucent 1830 PSS ZIC Properties General window opens.
The timing configuration parameters are shown which are currently assigned
...................................................................................................................................................................................................
From the Sync Messaging drop-down list box, select if the timing reference selection for
system timing is using sync messaging (SSM Qualities) or not.
Yes (default setting)
System timing reference selection is done by SSM quality levels as first criteria and
by priorities as second criteria.
No
Sync Messaging is disabled. System timing reference selection is done only by

priorities.
...................................................................................................................................................................................................
Apply your changes by clicking Apply or OK.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-4
Issue 1 June 2013
....................................................................................................................................................................................................................................

Purpose
These properties are used for provisioning for the following entities:
system timing
timing reference for system timing selection

Field/parameter ...
Meaning...
Command Mode
The Command Execution Mode:
Name
Forced
Normal
Sync Access Identifier, specifies either the timing node for the
system timing entity (delivering the system timing reference T0) or
a timing reference (external port connected to the timing selection
process) to which the command is directed.
Possible values
SYNC-1-<Shelf>-0
Timing Node within a Shelf

Clock Mode Status
Specifies the currently used operation mode for the system timing.
LOCKED
This value indicates, that the system timing is locked to a timing

reference signal
AUTONOMOUS-HOLDOVER
This value indicates that all timing references available for the
system timing selection have failed and the clock is using data
previously acquired (when it was operating in the normal mode)
to control its output signal.
AUTONOMOUS-FREERUNNING
This value indicates that all timing references available for the
system timing selection have failed and that no data previously
acquired (when it was operating in the normal mode) is
available (e.g. after initial power-up).
FORCED-FREERUNNING
This value is caused by a system timing switch command.

Restriction: The parameter is only applicable for the system timing
entity
....................................................................................................................................................................................................................................
1830 PSS
8-5
Issue 1 June 2013
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Active Reference
Specifies either the AID of the currently selected (i.e. active) timing
reference for the system timing:
EXTREF-1-<Shelf>-{0,1}
Timing Reference of a Shelf for an External Timing Input Port.
NONE
No timing reference is currently selected for the system timing.

The value NONE can occur due to no timing reference is
available (all references are unassigned, disabled, failed or
locked-out)
Restriction: The parameter is only applicable for the system timing
entity
Quality Value
Specifies the actual quality value level for the system timing.
PRC
Primary Reference Clock, specified in ITU-T Rec. G.811
SSUL
Synchronization Supply Unit - Local node, specified in ITU-T

Rec. G.812
SSUT
Synchronization Supply Unit -Transfer node, specified in ITU-T

Rec. G.812
SEC
SDH Equipment Clock, specified in G.813 option 1
DUS
Do not USe PRS Stratum 1 Traceable

Used in case of Sync Messaging is disabled (parameter
SYNCMSG=N) in ETSI/SDH NE mode
PRS
Stratum 1 Traceable
ANSI quality level value is fixed to PRS
STU
Synchronized 1 Traceability Unknown

SYNCMSG=N) in ANSI/SONET NE mode
ST2
Stratum 2 Traceable
ST3E
Stratum 3E Traceable
ST3
Stratum 3 Traceable
AUTO
Quality level value is derived from incoming SSM

....................................................................................................................................................................................................................................
1830 PSS
8-6
Issue 1 June 2013
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Sync Messaging
Specifies determines if the timing reference selection for system

timing is using sync messaging (SSM Qualities) or not.
No
Sync Messaging is disabled. System timing reference selection

is done only by priorities.
Yes
Sync Messaging is enabled. System timing reference selection is

done by SSM quality levels as first criteria and by priorities as
second criteria.
Switch Status
Specifies the currently active switch request state of reference

selection for the system timing.
NR
No external switch command is active
Manual
A manual switch command to the currently selected timing

reference is active.
FORCED
A forced switch command to the currently selected timing

reference is active.
....................................................................................................................................................................................................................................
1830 PSS
8-7
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to configure the external timing input ports.

Related TL1 command
ED-BITS.
Related information
This procedure modifies the provisioning of one or more ports dedicated to BITS
(Building Integrated Timing Supply) facilities for clock synchronization purposes. A
BITS is an external timing input signal. 2 BITS entities are created/deleted in the context
of shelf provisioning/de-provisioning.
The following signal types are supported if the node is provisioned to work in SDH
mode:
2 MHz signal
2 Mbit framed signal with no SSM support

2 Mbit framed signal with SSM support.
The following signal types are supported if the node is provisioned to work in SONET
mode:
DS1 signal with ESF format with SSM support
DS1 signal with ESF format with no SSM support

DS1 with SF format (no SSM support).
Type of interface detection
For the timing cabling currently only two possibilities are allowed:
Symmetrical cable (100 Ohm / 120 Ohm) used for SONET mode
Unsymmetricalcable (75 Ohm) used for SDH mode
The adapter detection is used to create an alarm if the NE is configured in SONET mode
(ANSI) and an unsymmetrical cable is detected or if the NE is configured in SDH mode
(ETSI) and a symmetrical cable is detected.
Important! The used cabling is described in more detail in the Alcatel-Lucent
1830 PSS Installation and System Turn-Up Guide (Alcatel-Lucent 1830 PSS-64),
chapter 4, Procedure 4-9: Configure external timing connection.
In case a wrong cable is connected the signal is possibly not recovered and may result
in LOS or other alarms. It will be not detected that a wrong cable is connected.
....................................................................................................................................................................................................................................
1830 PSS
8-8
Issue 1 June 2013
....................................................................................................................................................................................................................................
The type of interface detection can be triggered (in each case for both connectors) by
performing one of the following actions:
Re-configure external timing input ports or

Re-configure the timing references
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Input BITS Ports
In the main window select on of the two BITS Ports.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
Under Signal Format specify the signal type for this timing input port (that means
incoming direction).
....................................................................................................................................................................................................................................
1830 PSS
8-9
Issue 1 June 2013
....................................................................................................................................................................................................................................
Additional info The parameter determines the capabilities of the timing input port in
terms of SSM and fault supervision.
2MBIT-NOSSM
2 Mbit/s framed signal with no SSM support - applicable for node working in
SDH mode
2MBIT-SSM
2 Mbit/s framed signal with SSM support - applicable for node working in SDH
mode.
SF
DS1 Super Frame format (no SSM support)
ESF
DS1 Extended Super Frame format with SSM support - applicable for node
working in SONET mode
ESF-NOSSM
DS1 Extended Super Frame format with non SSM support - applicable for node
working in SONET mode.
...................................................................................................................................................................................................
Under SA Bit Location specify the Sa bit location used to carry the SSM information.
Note: The parameter is only applicable for the following signal types/formats:
2MBIT-SSM 2 Mbit/s framed signal with SSM support
Additional info The parameter determines the capabilities of the timing input port in
SA4
Sa4 bit within of the 2 Mbit/s frame
SA5
SA6
SA7
SA8
Sa8 bit within of the 2 Mbit/s frame.
....................................................................................................................................................................................................................................
1830 PSS
8-10
Issue 1 June 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Under DS1 Line Code specify the line code for the electrical DS1 or external timing
reference source.)
Additional info
AMI
Alternate Mark Inversion
B8ZS
Bipolar with Eight Zero Substitution.

...................................................................................................................................................................................................
Under SA Bit Location nothing has to be specified.

Note: The parameter is only applicable for the following signal types/formats:
2MBIT-SSM 2 Mbit/s framed signal with SSM support.
...................................................................................................................................................................................................
Forced
Normal.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-11
Issue 1 June 2013
....................................................................................................................................................................................................................................

Purpose
These properties are used to provision one or more ports dedicated to BITS (Building
Integrated Timing Supply) facilities for clock synchronization purposes. A BITS is an
external timing input signal.

Table 8-1
Fields and parameters of the Edit BITS window
Field/parameter ...
Meaning...
Command Mode
Name
Forced
Normal
The BITS Access Identifier, specifies the selected BITS facility to

which the command is directed.
BITS-1-<Shelf>-0
BITS-1-<Shelf>-1
In PSS-64 shelves the physical connector for BITS-1-<Shelf>-0 is

located
on PSF3T8 card A(slot 91).
on PSF3T8 card B(slot 94).
In PSS-36 shelves the physical connector for BITS-1-<Shelf>-1 is

located
Primary State
on PFC card A(slot 44).
on PFC card B(slot 45).
The parameter determines the primary state of the facility.
IS
In Service
OOS
Out Of Service
....................................................................................................................................................................................................................................
1830 PSS
8-12
Issue 1 June 2013
....................................................................................................................................................................................................................................
Table 8-1
(continued)
Field/parameter ...
Meaning...
Signal Format
Specifies the signal type for this timing input port (that means
incoming direction).
The parameter determines the capabilities of the timing input port in
2MBIT-NOSSM
2 Mbit/s framed signal with no SSM support - applicable for

node working in SDH mode
2MBIT-SSM
2 Mbit/s framed signal with SSM support - applicable for node

working in SDH mode
SF
DS1 Super Frame format (no SSM support)
ESF
DS1 Extended Super Frame format with SSM support applicable for node working in SONET mode - applicable for
node working in SONET mode
ESF-NOSSM
DS1 Extended Super Frame format with non SSM support applicable for node working in SONET mode
DS2 Line Code
Specifies the line code for the electrical DS1 or external timing
reference source.
AMI
Alternate Mark Inversion
B8ZS
Bipolar with Eight Zero Substitution

SA Bit Location
The parameter is only applicable for the following signal

types/formats: 2MBIT-SSM 2 Mbit/s framed signal with SSM support
SA Bit, specifies the Sa bit location used to carry the SSM
information.
SA4
SA5
SA6
SA7
SA8

....................................................................................................................................................................................................................................
1830 PSS
8-13
Issue 1 June 2013
....................................................................................................................................................................................................................................
Table 8-1
(continued)
Field/parameter ...
Meaning...
ASAP
The Alarm Severity Assignment profile (ASAP) name to use with

this facility
....................................................................................................................................................................................................................................
1830 PSS
8-14
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to configure the external timing input ports.

Related TL1 command
ED-SYNCN.
Related information
This procedure modifies the provisioning of one or more ports dedicated to BITS
(Building Integrated Timing Supply) facilities for clock synchronization purposes. A
BITS is an external timing input signal. 2 BITS entities are created/deleted in the context
of shelf provisioning/de-provisioning.
mode:
2 Mbit framed signal with SSM support.
mode:

DS1 with SF format (no SSM support).
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
8-15
Issue 1 June 2013
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
Timing References - Electrical
In the main window select either EXTREF-1-1-0 or EXTREF-1-1-1.

...................................................................................................................................................................................................
...................................................................................................................................................................................................
In the Assigned Port field, enter the AID of the BITS facility
BITS-{1-7}-{1-9}-{0,1} (Shelf External Timing Input Port).

Reference: Refer to Procedure 8-2: Configure external timing input ports (p. 8-8).
...................................................................................................................................................................................................
From the Priority Drop-down list box, select the priority of the respective timing
reference.
0 Disable (default setting)
1 (highest priority), 2, (lowest priority).
Make sure that all configured timing references have different priorities assigned.
Result: A priority list is created for the configured timing reference signals.
Timing reference selection If the System SSM Mode (can be set via SYNCMSG
drop-down list box) is set to Yes (QL Enable), then initially the signal with the highest
quality level is used as timing reference signal. If it fails, the system switches to the
signal with the next lower quality level. If there are several timing references with the
same quality level, they are used according to the priority list.
If the System SSM Mode is set to No QL Disable, then only the priorities of the timing
reference signals are evaluated.
If all available timing reference signals fail, then the timing generator enters the
autonomous holdover mode.
...................................................................................................................................................................................................
From the Provisioned Quality Value Drop-down list box, select the timing quality to be
assigned to the timing reference.
....................................................................................................................................................................................................................................
1830 PSS
8-16
Issue 1 June 2013
....................................................................................................................................................................................................................................

SDH synchronization mode
SONET synchronization mode
PRC
PRS
SSUT
STU
SSUL
ST2
SEC
ST3E
ST3
AUTO (default)
AUTO (default)
For timing references, it is recommended to select AUTO. This means that the
Synchronization Status Message (SSM) is evaluated (provided that the System SSM Mode
is set to QL Enable). Alternatively, you may assign the actual quality level of the timing
reference source.
Result: The timing references are now used in the order of their quality level.
...................................................................................................................................................................................................
Click Apply.
...................................................................................................................................................................................................
Click Yes to confirm.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-17
Issue 1 June 2013
....................................................................................................................................................................................................................................

Purpose
These properties are used for provisioning external timing references :


Field/parameter ...
Meaning...
Command Mode
Name
Forced
Normal
Sync Access Identifier, specifies either the timing node for the
system timing entity (delivering the system timing reference T0) or
a timing reference (external port connected to the timing selection
process) to which the command is directed.
Possible values
EXTREF-1-<Shelf>-{0,1}
Timing Reference of a Shelf for an External Timing Input Port.

Primary State
The parameter determines the primary state of the facility.
IS
In Service
OOS
Out Of Service
Assigned Port
Specifies whether the timing reference is assigned/connected to port

and if connected it specifies the AID of the port.
The following port types can be used for establishing a connection
towards a timing reference:
BITS-1-<Shelf>-{0,1}
Port connected to a external timing reference
NA
Timing reference is not assigned to a port
....................................................................................................................................................................................................................................
1830 PSS
8-18
Issue 1 June 2013
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Priority
Specifies the priority of a timing reference for the system timing

selection process. It is possible to provision the same priority to
different timing references in order to support a non-revertive
selection process. When Sync Messaging is disabled, the selection
process will be controlled by signal status and priority. The priority
"0" means that the timing reference is disabled from the selection
process. A greater parameter value means a lower the priority for the
selection besides the value "0".
disabled for the system timing selection process
1-2
enabled for the system timing selection process

Provisioned Quality
Value
Specifies the provisioned quality level of a timing reference. Two

different methods are supported; i.e. the quality level is either
derived from the incoming SSM value or a fixed quality value is set.
The value AUTO is only allowed for ports supporting SSM.
Possible values:
AUTO
Quality level value is derived from incoming SSM
PRC
SSUL

Rec. G.812
SSUT

Rec. G.812
SEC
PRS
quality level value is fixed to PRS (Stratum 1 Traceable)
STU

ST2
Stratum 2 Traceable
ST3E
ST3
Stratum 3 Traceable
....................................................................................................................................................................................................................................
1830 PSS
8-19
Issue 1 June 2013
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Actual Quality Value
Specifies the actual quality value level for the timing reference as
forwarded to the system timing selection process. The value is
derived from the incoming SSM value taking also the provisioned
QL value into account. In case of invalid SSM (i.e. not defined for
current application SONET or SDH), the value DUS is replied.
Specifies the actual quality value level for the system timing.
PRC
SSUL

Rec. G.812
SSUT

Rec. G.812
SEC
DUS
Do not USe PRS Stratum 1 Traceable

SYNCMSG=N) in ETSI/SDH NE mode
STU

ST2
Stratum 2 Traceable
ST3E
ST3
Stratum 3 Traceable
....................................................................................................................................................................................................................................
1830 PSS
8-20
Issue 1 June 2013
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Signal Status
Specifies the actual signal status for the timing reference as

forwarded to the system timing selection process.
NORMAL
timing reference is assigned and operating normally without

faults.
SF
timing reference has an SF condition present
WTR
timing reference is in wait-to-restore state after the clearance of

an SF condition
NA
timing reference is not assigned

Lockout
Specifies whether a lockout command for the system timing

selection is present for the timing reference.
Yes
Lockout command is present and the timing reference is not

considered by the system timing selection process.
NO
No lockout command is present for a timing reference within

the system timing selection process.
....................................................................................................................................................................................................................................
1830 PSS
8-21
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to perform a system timing reference switch to internal timing
manually.
The following actions can be performed:
perform a lockout command for the system timing selection.

perform a forced switch command for the system timing selection
perform a manual switch command for the system timing selection.
OPR-SYNCNSW
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select
System Internal Sync System Timing
In the main window select the respective system timing reference:
SYNC-1-1-0
....................................................................................................................................................................................................................................
1830 PSS
8-22
Issue 1 June 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
If you want to
Then
enter the free-running mode
Then select
Switching Enter Free-Running Mode
either by selecting Action from the main menu

the right mouse button.
exit the free-running mode
Then select
Switching Exit Free-Running Mode ,

Result: The Enter Free-Running Mode / Exit Free-Running Mode screen is
displayed.
...................................................................................................................................................................................................
3
To apply your changes, that means to perform the selected
switch request,
click Apply.
To discard your changes,
click Close.
Important! After a timing reference switch, it takes up to 2 minutes (up to 8 minutes

during the warming up phase) for the system to stabilize the holdover filter. Therefore,
it is recommended not to configure any further timing parameters during the holdover
filter stabilization period.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-23
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to perform a external timing reference switch manually.

The following actions can be performed:
perform a lockout command for the system timing selection.

perform a forced switch command for the system timing selection
perform a manual switch command for the system timing selection.
OPR-SYNCNSW
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select
System Internal Sync Timing References
EXTREF-1-1-0
EXTREF-1-1-1
....................................................................................................................................................................................................................................
1830 PSS
8-24
Issue 1 June 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
If you want to
Then
lockout a timing reference from system timing

selection
Then select
Switching Operate Lockout

switch to an other timing reference
Then select
Switching Switch to Reference ,

Result: The Switch To Reference / Operate Lockout screen is displayed.
...................................................................................................................................................................................................
Select the Switch Command in the corresponding field:
MAN Manual Switch To Reference
causes the system to be switched to the selected timing reference only if that timing
reference is working fault free and no other external request is present.
If SSM is enabled then the best incoming reference will be selected to be the active
reference. Thus a manual switch is only possible if the quality of the reference you
want to switch to is equal to the active reference. Switching between two references
of equal quality but different priority is possible while switching to a reference of
lower quality is not possible.
FORCD Forced Switch To Reference
causes the system to be switched to the selected timing references regardless of the
state of the timing reference. Only if a Clear Reference Switch or a Lockout
command is present the Forced Switch is denied. A Forced Switch remains
active until it is removed by a Clear Reference Switch or a Lockout command.
...................................................................................................................................................................................................
4
To apply your changes, that means to perform the selected
switch request,
click Apply.
To discard your changes,
click Close.
Important! After a timing reference switch, it takes up to 2 minutes (up to 8 minutes

during the warming up phase) for the system to stabilize the holdover filter. Therefore,
it is recommended not to configure any further timing parameters during the holdover
....................................................................................................................................................................................................................................
1830 PSS
8-25
Issue 1 June 2013
....................................................................................................................................................................................................................................
filter stabilization period.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-26
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to release a previously executed switch commands for the system
timing entity or for a timing reference entity involved in the system timing reference
selection process.
RLS-SYNCNSW
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
8-27
Issue 1 June 2013
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
Depending if you want to executed the switch commands for the system timing entity or
for a timing reference entity involved in the system timing reference selection process,
you have to select differently.
If you want to release system timing
lockout for
Then
for a Timing Node within a Shelf
In the Alcatel-Lucent 1830 PSS ZIC selection

tree select
System Internal Sync Timing

References
In the main window select the respective

system timing reference:
SYNC-1-1-0
SYNC-1-1-1
Then select Switching Release Lockout,

for a timing reference of a shelf for an
External Timing Input Port
In the Alcatel-Lucent 1830 PSS ZIC selection

tree select
System Internal Sync Timing

References
In the main window select the respective

system timing reference:
EXTREF-1-1-0
EXTREF-1-1-1
Then select Switching Release Lockout,

Result: A confirmation window opens asking you if you want release a previously
executed clock reference switch.

...................................................................................................................................................................................................
Define the switch command to be cleared:
CLOCKSWITCH
clears the forced free-running mode for system timing
REFSWITCH
....................................................................................................................................................................................................................................
1830 PSS
8-28
Issue 1 June 2013
....................................................................................................................................................................................................................................
clears the current active command (Forced or Manual) for system timing selection.
...................................................................................................................................................................................................
To release the switch request,
click Yes.
otherwise,
click No.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-29
Issue 1 June 2013
Procedure 8-7: Take an external timing reference out of

service for maintenance purposes
....................................................................................................................................................................................................................................

When to use
Use this procedure to the system timing reference out-of-service. The system timing
reference is logically removed from facility/clock specific alarm reporting service.
RMV-SYNCN
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree either select
System Internal Sync Timing References - Electrical
EXTREF-1-1-0
EXTREF-1-1-1
...................................................................................................................................................................................................
The select Service States Remove, either by selecting Action from the main menu bar
Result: The Alcatel-Lucent 1830 PSS ZIC Service States Remove window opens.
...................................................................................................................................................................................................
Forced
Normal
....................................................................................................................................................................................................................................
1830 PSS
8-30
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply.
Result: When using the Forced Command Execution Mode a confirmation window
opens.
...................................................................................................................................................................................................
If there is a confirmation window click Yes to confirm.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-31
Issue 1 June 2013
Procedure 8-8: Take an external timing input port out (BITS)

out-of-service
....................................................................................................................................................................................................................................

out-of-service
When to use
Use this procedure to take an external timing input port out of service for maintenance
purposes. The BITS entity is logically removed from facility/clock specific alarm
reporting service.
RMV-BITS
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Input BITS Ports
In the main window select one of the respective BITS Ports.

In the main window select the respective BITS Ports:
BITS-1-1-0
BITS-1-1-1
...................................................................................................................................................................................................
The select Service States Remove, either by selecting Action from the main menu bar
....................................................................................................................................................................................................................................
1830 PSS
8-32
Issue 1 June 2013

out-of-service
....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Service States Remove window opens.
...................................................................................................................................................................................................
Forced
Normal
...................................................................................................................................................................................................
Click Apply.
Result: When using the Forced Command Execution Mode a confirmation window
opens.
...................................................................................................................................................................................................
If there is a confirmation window click Yes to confirm.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-33
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to force a specified facility in IS-NR state. The system timing entity is
restored to facility specific alarm reporting service.
RST-BITS
RST-SYNCN
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree either select
System Internal Sync Input BITS ports
or
System Internal Sync Timing References - Electrical
BITS-1-1-0
BITS-1-1-1
EXTREF-1-1-0
EXTREF-1-1-1
...................................................................................................................................................................................................
The select Service States Restore, either by selecting Action from the main menu bar
....................................................................................................................................................................................................................................
1830 PSS
8-34
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: A confirmation window opens, informing that the specified facility will be
placed in an IS-NR state. The system timing entity will be logically restored to facility
specific alarm reporting service.
...................................................................................................................................................................................................
If you are asked to proceed, click Yes.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-35
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieves information on equipment providing Network Element

synchronization. TThe output will be data for timing entities (matrix boards host the
Clock Reference Units (CRUs) as daughter boards) used by the system.
RD-SYNCN
Related informtion
A BITS is an external timing input port.

mode:

2 Mbit framed signal with SSM support
mode:

DS1 signal with SF format
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
System Timing Internal Sync.
....................................................................................................................................................................................................................................
1830 PSS
8-36
Issue 1 June 2013
....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Then select View Sync Status, either by selecting Action from the main menu bar or by
Result: The Read Synchronization window opens.
For each item the following parameters are described:

Clock Control Status
ACTIVE
The specified clock entity is the active.
STANDBY
The specified clock entity is the standby
NA
Control Path to Timing Entity is not Active.
Clock Tracking Mode

Indicates the CRG to external clock reference tracking mode if the specified entity hosts the
active CRU (as indicated by the CONTSTAT parameter). The Active CRU will never show
NOTTRACKING. The Standby CRU will always show a Clock Tracking Mode of
NORMAL, NOTTRACKING or NA.
FREE-RUNNING
The master clock on the matrix shelf timing entity is operating such
that the output signal is totally internally controlled with no
influence of a present or previous external/master reference.
HOLDOVER
The master clock has lost its previously-connected external

reference source (or has not locked to an external reference source)
and is using data acquired during the Normal mode or using internal
data to control its output.
NORMAL
The slave clock is aligned to and tracking the master clock reference
and the master clock is aligned to and tracking the external clock
reference source.
NOTTRACKING
The slave clock is not aligned to and tracking the master clock
reference. A MISC-1 condition is active.
NA
Control Path to Timing Entity is not Active.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-37
Issue 1 June 2013
Procedure 8-11: Retrieve provisioning and state information

of external timing references
....................................................................................................................................................................................................................................
Procedure 8-11: Retrieve provisioning and state information of

external timing references
When to use
Use this procedure to retrieve provisioning and state information for the following
entities:
system timing (one instance per shelf)

timing reference (2 external instances per shelf)
RTRV-SYNCN
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
System Timing Internal Sync.
...................................................................................................................................................................................................
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-38
Issue 1 June 2013

of external timing input ports
....................................................................................................................................................................................................................................
Procedure 8-12: Retrieve provisioning and state information of

external timing input ports
When to use
Use this procedure to retrieve provisioning and state information for of one or more ports
dedicated to BITS (Building Integrated Timing Supply) facilities for clock
synchronization purposes. A BITS is an external timing input port.
RTRV-BITS
Related information
A BITS is an external timing input port.

mode:
2 MHz signal 2 Mbit framed signal with no SSM support

2 Mbit framed signal with SSM support
mode:

DS1 signal with SF format
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
8-39
Issue 1 June 2013

of external timing input ports
....................................................................................................................................................................................................................................
Instructions
...................................................................................................................................................................................................
Input BITS Ports.
In the main window select BITS-1-1-0 or BITS-1-1-1.
...................................................................................................................................................................................................
Reference: See General properties of external timing input ports (p. 8-12).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
8-40
Issue 1 June 2013
....................................................................................................................................................................................................................................

Overview
Alcatel-Lucent 1830 PSS provides two external timing inputs:
BITS-1-1-0
BITS-1-1-1
The configuration parameters of these external timing inputs are described in the
following.
Related information
None.
Input Signal Format
The Input Signal Format is the format of the external timing input signal.
Table 8-2
External timing input signal format
SDH synchronization mode
2MBIT-FRAMED without SSM support: framed 2-Mbit/s signal
without SSM support

2MBIT-FRAMED with SSM support: framed 2-Mbit/s signal with
SSM support
SONET synchronization
mode
ESF (default; DS1 Extended Super Frame) with SSM support

ESF (default; DS1 Extended Super Frame) without SSM support
SF (DS1 Super Frame) no SSM support
SSM Support
The Synchronization Status Message (SSM) support can be enabled for framed 2-Mbit/s
(SDH synchronization mode) and ESF (SONET synchronization mode) external timing
input signals.
Table 8-3
SSM support settings
SUPPORTED
The SSM support is enabled.

This is the default setting in the SONET synchronization mode.
NOT-SUPPORTED
The SSM support is disabled.

This is the default setting in the SDH synchronization mode.
....................................................................................................................................................................................................................................
1830 PSS
8-41
Issue 1 June 2013
....................................................................................................................................................................................................................................
SA bit Location
This parameter is only applicable in the SDH synchronization mode, and only in case the
selected signal format is 2MBIT-FRAMED, and SSM Support is enabled.
If the SSM Support is disabled, then the value of the SA bit Location parameter is of no
relevance.
If the SSM Support parameter is enabled, then the SSM is extracted from the Sa bits
starting at the location defined by the SA bit Location parameter.
SA4 (default setting)
SA5
SA6
SA7
SA8
....................................................................................................................................................................................................................................
1830 PSS
8-42
Issue 1 June 2013
....................................................................................................................................................................................................................................

Overview
A timing reference is an external signal to which the internal SDH/SONET equipment

clock is locked.
These signals can be used as timing reference:
External timing references

One or two external net clock input signals (2048 kbit/s acc. to ITU-T
recommendations, or DS1 SF or ESF acc. to Telcordia Technologies standards)
Related information
None.
Active system timing reference
Parameter
Possible values
Meaning
Active Timing
Reference
NONE (default setting)
The currently active system timing reference which is used to derive the
system clock in the locked mode of system timing.
EXTREF-1-1-0
Switch Status
EXTREF-1-1-1
The value NONE is displayed if no timing reference is assigned, or if all

timing references have failed or are locked-out.
Manual,
The current system timing reference switch request status.
Forced,
No Request
Timing references
The timing references include the external timing references. The parameters of the line
timing references and the external timing references are explained in the following tables.
Line timing references
These are the valid settings of the line timing references:

Parameter
Possible values
Meaning
Port AID
Not connected
The respective timing reference source is not used.
Port AID of an SDH/SONET

port
The clock information is derived from the respective SDH/SONET

transport signal.
Disable (default setting)
The configured priority of the respective timing reference signal.
Sys. Tim. Ref. Prio.
1 (highest priority), 2, 3,
8 (lowest priority)
....................................................................................................................................................................................................................................
1830 PSS
8-43
Issue 1 June 2013
....................................................................................................................................................................................................................................
Parameter
Possible values
Meaning
Signal Status
Normal
The timing reference signal is fault-free.
Failed
The timing reference signal failed.
Wait-To-Restore
The timing reference signal has failed and is now being restored. A waiting
period is implemented for a defined time (wait-to-restore time) to see
whether the signal is stable, before the system switches back to it.
Not-Connected
The timing reference is not used.
Lockout
The Lockout Status determines if the respective timing reference can be

used as a system timing reference (No Lockout) or not (Lockout).
Lockout Status
No Lockout
QL Value
SDH synchronization mode:
The quality level of the timing reference port.
PRC
If the provisioned quality level (see QL Provisioned) has any value other
than AUTO, then the quality level is the same as the QL Provisioned.
SSUT
SSUL
If the provisioned quality level is AUTO, then the quality level has the same
value as the incoming SSM Value.
SEC
DNU (default setting)
SONET synchronization mode:

PRS
STU
ST2
ST3
DUS (default setting)
Input QL Status
Valid,
An indicator for the validity of the incoming quality level:
Invalid,
Not Applicable
Valid
The quality level is a valid Synchronization Status Message (SSM)

and stable.
Not Supported,
Invalid
The quality level is not a valid SSM, or instable.
Not Supported
Evaluating the SSM is not supported on the respective interface due

to the capabilities of the hardware.
Not Applicable
No port is assigned to the current timing reference, or the assigned

timing reference experiences a reference fail.
....................................................................................................................................................................................................................................
1830 PSS
8-44
Issue 1 June 2013
....................................................................................................................................................................................................................................
Parameter
Possible values
Meaning
QL Provisioned
The quality level of the respective timing reference assigned by

provisioning.
PRC
SSUT
SSUL
SEC
AUTO (default setting)
If the provisioned quality level is AUTO, then the incoming SSM Value is
used as the quality level.
Otherwise, if the provisioned quality level has any value other than AUTO,
then the incoming SSM Value is not used, but this provisioned value is used
as the quality level.

PRS
STU
ST2
ST3
SSM Value

PRC
The quality level as received from the external signal when the signal has a
valid Input QL Status (see above).
SSUT
SSUL
SEC
DNU
UNSTABLE

PRS
STU
ST2
ST3
DUS
Output Ref. Priority
Disabled, 1 (highest priority), 2,

3, ..., 6 (lowest priority)
This parameter is applicable in the SDH synchronization mode only! It

shows the priority assigned to the timing reference signal for the usage as
an output timing reference.
Output Lockout
State
Lockout
This parameter is applicable in the SDH synchronization mode only! It

determines if the respective line timing reference can be used as an output
timing reference (No Lockout) or not (Lockout).
No Lockout
ASAP
Any specific ASAP of type

System Timing, or the default
ASAP of type System Timing
(DEFAULT).
In the SDH synchronization mode, the output signal at the external timing
output ports can be derived from the line timing references (Line 1
Line 6) via the Timing Link Switch (TLS), that means when the Derived
Output Timing: Prov. Source Selection is set to TLS (can be set via
Configuration Timing/Synchronization External Outputs).
The Alarm Severity Assignment Profile (ASAP) of type System Timing
assigned to the respective timing reference.
....................................................................................................................................................................................................................................
1830 PSS
8-45
Issue 1 June 2013
....................................................................................................................................................................................................................................
Parameter
Possible values
Meaning
By means of the Detail button, more detailed information on the available

ASAPs of type System Timing (see ASAP (Alarm Severity Assigned
Profile) AIDs (p. 5-571)) can be retrieved.
Detail
Monitored, Not Monitored
Timing Port Mode
This parameter indicates whether the respective timing port will be

monitored for timing reference failures (Monitored) or not
(Not Monitored).
If a timing port is set to Not Monitored, then no timing reference failure
alarms will be reported for that port.
External timing references
These are the possible settings of the external timing references.

Parameter
Possible values
Meaning
Port AID
Not connected
The respective timing reference source is not used.
Port AID of an external timing

input port (exttmg0, exttmg1)
The clock information is derived from the respective

external timing input port.
Disable (default setting)
The configured priority of the respective timing

reference signal.
Sys. Tim. Ref. Prio.
1 (highest priority), 2, 3,
8 (lowest priority)
Signal Status
Lockout Status
QL Value
Normal
The timing reference signal is fault-free.
Failed
The timing reference signal failed.
Wait-To-Restore
The timing reference signal has failed and is now being

restored. A waiting period is implemented for a defined
time (wait-to-restore time) to see whether the signal is
stable, before the system switches back to it.
Not-Connected
The timing reference is not used.
Lockout
No Lockout
The Lockout Status determines if the respective timing

reference can be used as a system timing reference (No
Lockout) or not (Lockout).
The quality level of the timing reference port.
PRC
If the provisioned quality level (see QL Provisioned)

has any value other than AUTO, then the quality level is
the same as the QL Provisioned.
SSUT
SSUL
SEC
If the provisioned quality level is AUTO, then the quality

level has the same value as the incoming SSM Value.
DNU (default setting)

PRS
STU
ST2
ST3
DUS (default setting)
....................................................................................................................................................................................................................................
1830 PSS
8-46
Issue 1 June 2013
....................................................................................................................................................................................................................................
Parameter
Possible values
Meaning
Input QL Status
Valid,
Indicates the validity of the incoming quality level:
Invalid,
The quality level is a valid Synchronization Status

Message (SSM) and stable.
Not Supported,
Not Applicable
Valid
Invalid
The quality level is not a valid SSM, or instable.
Not Supported
Evaluating the SSM is not supported on the

respective interface due to the chosen format of the
input signal (for instance in case of a 2-MHz
timing input signal).
Not Applicable
No port is assigned to the current timing reference,

or the assigned timing reference experiences a
reference fail.
QL Provisioned

PRC
SSUT (default setting)
SSUL
SEC
AUTO
The quality level of the respective timing reference

assigned by provisioning.
If the provisioned quality level is AUTO, then the
incoming SSM Value is used as the quality level.
Otherwise, if the provisioned quality level has any
value other than AUTO, then the incoming SSM Value is
not used, but this provisioned value is used as the
quality level.
PRS
STU
ST2
ST3
SSM Value

PRC
The quality level as received from the external signal

when the signal has a valid Input QL Status (see above).
SSUT
SSUL
SEC
DNU
UNSTABLE

PRS
STU
ST2
ST3
DUS
....................................................................................................................................................................................................................................
1830 PSS
8-47
Issue 1 June 2013
....................................................................................................................................................................................................................................
Parameter
Possible values
Meaning
Output Ref. Priority
Not applicable
This parameter is not applicable to external timing

references!
In the SDH synchronization mode, the value "Not
applicable" is displayed on the graphical user interface.
In the SONET synchronization mode, the Output Ref.
Priority is not displayed on the graphical user interface.
Output Lockout State
Not applicable
This parameter is not applicable to external timing

references!
In the SDH synchronization mode, the value "Not
applicable" is displayed on the graphical user interface.
In the SONET synchronization mode, the Output
Lockout State is not displayed on the graphical user
interface.
ASAP
Any specific ASAP of type

System Timing, or the default
ASAP of type System Timing
(DEFAULT).
By means of the Detail button, more detailed

information on the available ASAPs of type System
Timing (see ASAP (Alarm Severity Assigned Profile)
AIDs (p. 5-571)) can be retrieved.
Detail
Timing Port Mode
The Alarm Severity Assignment Profile (ASAP) of type

System Timing assigned to the respective timing
reference.
Monitored, Not Monitored
This parameter indicates whether the respective timing

port will be monitored for timing reference failures
(Monitored) or not (Not Monitored).
If a timing port is set to Not Monitored, then no timing
reference failure alarms will be reported for that port.
....................................................................................................................................................................................................................................
1830 PSS
8-48
Issue 1 June 2013
9 DM network
T
configuration procedures
Overview
Purpose
This chapter describes the procedures which have to be performed for the network
configuration. This comprises basically the functions of the cross-connection wizard and
the setup of network protections.
The following figure gives an overview of the available network protection mechanisms.
Figure 9-1 Overview of available network protection mechanisms
Ethernet/MPLS
Ethernet/MPLS
SDH/SONET
SDH/SONET
1830PSS
1870TTS
OTH
OTH vendor2
1830PSS
1870TTS
OTH vendor2
1830PSS
1870TTS
SDH/SONET/Packet
SNCP/UPSR
2G5, 10G, GE, 10GE
OTH
1+1 ODU1/2/2E/3 SNC/N
Restoration
OTM-0.2, OTM-0.3
SDH/SONET/Packet
SNCP/UPSR
2G5, 10G, GE, 10GE
Related information
For conceptual information see Alcatel-Lucent 1830 PSS Product Information and
Planning Guide (PIPG), chapter 5 Provisioning, section Protection switching.
For the basic cross-connection type see Cross-connection types (p. 11-2).
...................................................................................................................................................................................................................................
1830 PSS
9-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Contents
Introduction
9-3
Create Cross Connections window
9-3
Manage Cross Connections window
9-6
9-10
Procedure 9-1: Add a protection leg to a cross-connection
9-10
Procedure 9-2: Remove a protection leg from a cross-connection
9-16
Procedure 9-3: Create an SNCP protection group
9-20
Procedure 9-4: Modify an SNCP protection group
9-27
9-30
Procedure 9-6: Initiate an SNC protection switch
9-32
9-34
Procedure 9-8: Retrieve configuration parameters and status information of an

SNC protection group
9-36
....................................................................................................................................................................................................................................
1830 PSS
9-2
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Introduction
Purpose
The Create Cross Connections window is used to create cross-connections.

The following fields/parameters are relevant for all types of cross-connections (protected,
unprotected), and they are displayed independent of the Display Options:
Field/parameter ...
Meaning...
From Facility
the AID of the source of the cross-connection leg.
To Facility
the AID of the destination of the cross-connection leg.
XC Type
the type of the cross-connection.

Possible values:
Circuit ID
1WAY - unidirectional cross-connection
2WAY - bidirectional cross-connection
1WAYSNCP - unidirectional path-protected cross-connection
2WAYSNCP - bidirectional path-protected cross-connection
allows you to enter an alphanumeric string to be associated with the

cross-connection.
The Circuit ID is a character string of 0 to 36 characters. The
characters
* (asterisk),
; (semicolon),
> (greater-than),
< (less-than),
(double quote), and
/ (backslash)
are excluded.
....................................................................................................................................................................................................................................
1830 PSS
9-3
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
The following parameters are relevant for protected cross-connections only, and they are
only displayed if the Protection Parameters check box is selected under Display
options:
Field/parameter ...
Meaning...
Alternate Facility
the AID of the alternate facility.
Hold Off Time
Hold Off Timer, indicates whether a hold-off time shall pass before
a protection switch is performed.
Possible values:
Revertive
For SDH/SONET path protection:

0, 30, 50, 70, 100, 300, 500, 700, 1000, 3000, 5000, 10000.
For ODUk path protection:

0, 20, 40, 80, and 100 up to 10000, in steps of 100.
Indicates whether or not to revert to protected once the protected

comes into service and the traffic is on protecting.
Possible values:
N Do not revert to protected (non-revertive mode)
Y Yes revert to protected (revertive mode)
Revert Delay Time
Revert Delay Time (wait to restore time) in minutes.
(relevant in revertive
mode only)
Possible values:
Sub Network Protection

Type
Possible values. SNC/N, SNC/NC, SNC/I
0 15
SNC/I protection generally protects against failures in the server

layer. The protection process and the defect detection process are
performed by two adjacent layers. The server layer performs the
defect detection process, and forwards the status to the client layer
by means of the Server Signal Fail (SSF) signal.
SNC/NC Sub Network Connection protection based on ODUkP
Client Signal with Non-intrusive monitoring
SNC/N protection generally protects against failures in the server
layer and against failures and degradation in the client layer. This
means the non-intrusive monitor function on the receive side detects
Signal Fail (SF) and Signal Degrade (SD) events on the incoming
signal and triggers the switch.
....................................................................................................................................................................................................................................
1830 PSS
9-4
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Protected Protection
Method
Different values are supported depending on the value of Sub

Network Protection Type PNIM for SNC/N or SNC/NC
Possible values: TCM-{1-6} or PNIM for SNC/N, PNIM for SNC/NC,
and PADAPT for SNC/I
The protection method can be at the ODUk Path NIM or a TCM
NIM. The protection Method can additionally be set at the ODUk
Path Adaptation.
Protecting Protection
Method
Possible values: TCM-{1-6}, PNIM, PADAPT
Signal Degraded Used

for Switching
Possible values: Y, N
The protection Method can be at the ODUk Path NIM or a TCM

Path Adaptation.
Signal Degrade enable indicating whether or not Signal Degrade is
used for protection switching.
Buttons and actions
The following options are available:

Button
Function
Import
Add
Can be used to add a new row to the cross-connection table.
Wizard
Can be used to open the Connection Wizard which provides various

configuration options for predefined cross-connection topologies.
Remove
Can be used to remove a previously selected row from the

cross-connection table.
Apply
Can be used to apply changes previously made in one or more rows

of the cross-connection table.
Close
Can be used to dismiss the Create Cross Connections window

without a provisioning action.
Help
Can be used to invoke context-sensitive help.
....................................................................................................................................................................................................................................
1830 PSS
9-5
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................

Purpose
The Manage Cross Connections window is used to modify the parameters of

cross-connections.

Field/parameter ...
Meaning...
From Facility
the AID of the source of the cross-connection leg.
To Facility
the AID of the destination of the cross-connection leg.
XC Type
the type of the cross-connection.

Possible values:
Primary Status
Secondary Status
1WAY - unidirectional cross-connection
2WAY - bidirectional cross-connection
1WAYSNCP - unidirectional path-protected cross-connection
2WAYSNCP - bidirectional path-protected cross-connection
Possible values:
IS-NR In-service, Normal
OOS-AUMA Out-of-service, autonomous and management
OOS-AU Out-of-service, autonomous
OOS-MA Out-of-service, management
Possible values:
DSBLD Disabled.
FAF Facility Failure
PMD Performance Monitoring Disabled
SDEE Supported Entity Exists
SGEO Supporting Entity Outage
TRM Supported facilities are connected
UAS Unassigned
....................................................................................................................................................................................................................................
1830 PSS
9-6
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Circuit ID
allows you to enter an alphanumeric string to be associated with the

cross-connection.
The Circuit ID is a character string of 0 to 45 characters. The
characters
* (asterisk),
; (semicolon),
> (greater-than),
< (less-than),
(double quote), and
/ (backslash)
are excluded.
Alternate Facility
the AID of the alternate facility.
Active
The current switch position.
Working
The Working/Protected facilities are currently carrying traffic
Protection
The Protection facilities are currently carrying traffic

Protection Status
the previously defined type of cross-connection.

Possible values are
Hold Off Time
1-Way Point-to-Point,
2-Way Point-to-Point,
UPSR/SNCP Ring Add/Drop
Hold Off Timer, indicates whether a hold-off time shall pass before
a protection switch is performed.
Possible values:
Revertive

0, 30, 50, 70, 100, 300, 500, 700, 1000, 3000, 5000, 10000.

Indicates whether or not to revert to protected once the protected

comes into service and the traffic is on protecting.
Possible values:
N Do not revert to protected (non-revertive mode)
Y Yes revert to protected (revertive mode)
....................................................................................................................................................................................................................................
1830 PSS
9-7
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Field/parameter ...
Meaning...
Revert Delay Time
Revert Delay Time (wait to restore time) in minutes.
(relevant in revertive
mode only)
Possible values:
Sub Network Protection

Type
Possible values. SNC/N, SNC/NC, SNC/I
0 15
SNC/I protection generally protects against failures in the server

layer. The protection process and the defect detection process are
performed by two adjacent layers. The server layer performs the
defect detection process, and forwards the status to the client layer
by means of the Server Signal Fail (SSF) signal.
SNC/NC Sub Network Connection protection based on ODUkP
Client Signal with Non-intrusive monitoring
SNC/N protection generally protects against failures in the server
layer and against failures and degradation in the client layer. This
means the non-intrusive monitor function on the receive side detects
Signal Fail (SF) and Signal Degrade (SD) events on the incoming
signal and triggers the switch.
Protected Protection
Method
Different values are supported depending on the value of Sub

Network Protection Type PNIM for SNC/N or SNC/NC
Possible values: TCM-{1-6} or PNIM for SNC/N, PNIM for SNC/NC,
and PADAPT for SNC/I
The protection method can be at the ODUk Path NIM or a TCM
Path Adaptation.
Protecting Protection
Method
Possible values: TCM-{1-6}, PNIM, PADAPT
Signal Degraded Used

for Switching
Possible values: Y, N
The protection Method can be at the ODUk Path NIM or a TCM

Path Adaptation.
Signal Degrade enable indicating whether or not Signal Degrade is
used for protection switching.
Buttons and actions
The following options are available:

Button
Function
Delete
Can be used to delete an existing, previously selected

cross-connections.
....................................................................................................................................................................................................................................
1830 PSS
9-8
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Button
Function
Protect
This button is relevant for unprotected cross-connections; it opens

the Select the NEWFROM Facility window which can be used to
convert an unprotected cross-connection into a protected
cross-connection.
Unprotect
This button is relevant for protected cross-connections; it opens the

Select the NEWFROM Facility window which can be used to
convert a protected cross-connection into an unprotected

cross-connection.
Join
Can be used to join cross-connections.
Split
Can be used to split cross-connections.
Modify
Can be used to modify configuration parameters of

cross-connections. Note that configuration parameters need to be
changed in the table of cross-connections prior to pressing the
Modify button.
Close
Can be used to close the Manage Cross Connections window

without a provisioning action.
....................................................................................................................................................................................................................................
1830 PSS
9-9
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
When to use
Use this procedure to add a protection leg to a cross-connection

Supported conversions
The following conversions will be supported:
1WAY 1WAYSNCP
2WAY 2WAYSNCP
Figure 9-2 Adding a protection leg to a one way protection
....................................................................................................................................................................................................................................
1830 PSS
9-10
Issue 1 June 2013

....................................................................................................................................................................................................................................
Figure 9-3 Adding a protection leg to a two way protection
The cross-connection to be modified is addressed by the TO parameter. (called original

cross-connection) The cross-connection Identifier is taken over from the already existing
cross-connection if not provided. When adding a protection leg (FROMPING), the
existing source (FROM of the original unprotected cross-connection) is required to be the
new FROMPED (NEWFROMPED).
Note: For an ODUk SNCP or SDH SNCP or SONET UPSR, the following applies:
When adding a protection leg the protection state will be calculated new and may lead
to a protection switch.
SDH/SONET specifics
In a 2WAY cross connection, both legs can be used as role of FROM.

FROMPED = Is the FROMPED facility after the conversion. If the NEWFROMPED
parameter is the same as the FROM from the original cross connection, the FROM
facility from the original cross connection will take over the role of the FROMPED, else
the leg will be newly created.
FROMPING = Is the FROMPING facility after the conversion. If the NEWFROMPING
parameter is the same as the FROM from the original cross connection, the FROM
facility from the original cross connection will take over the role of the FROMPING, else
the leg will be new created.
If the parent facility of one of the unreliable legs of a 1WAYSNCP or 2WAYSNCP cross
connection is placed in LPBK, the SNCP switching may not work.
....................................................................................................................................................................................................................................
1830 PSS
9-11
Issue 1 June 2013

....................................................................................................................................................................................................................................
ODUk specifics
The described operation is also allowed on path terminated cross-connections involving

virtual ODUk path terminated entities (for example, not matrix connections.) The TO
facility is then always the virtual path terminated entity.
Protection connections is allowed for ODUk NIMs and transparent transport ODUk
entities. In such cases, these entities are allowed to be the FROMPED, FROMPING, or
TO facilities. Protection connections are also be allowed for path terminated cross
connections involving virtual ODUk path terminated entities. However these entities
always need to be the TO facility of the connection.
ODUk SNC/Nc based on ODUkP Client Signal Non-Intrusive Monitoring and ODUk
SNC/N based on ODUkP/T Non-Intrusive Monitoring is supported.
SNC/Nc is only allowed when both protected/protecting entities are transparent transport
ODUk entities. Transparent transport ODUk entities are only allowed to be the
FROMPED/PING facilities if the protection type is SNC/Nc; Otherwise they are required
to be the outgoing TO facility.
For path terminated cross connections involving virtual ODUk path terminated entities,
the newly added ODU NIM leg acquires shared attributes from the PTF (see
ED-OTUPTF for shared attributes).
See ENT-CRS-ODUk and ENT-CRSPROT-ODUk for more details on path terminated
cross connections involving virtual ODUk path terminated entities (e.g., not matrix
connections)
When establishing protection, additional parameters must be set identifying the protection
layer (e.g. protection method) from which the switch criteria is to be taken. The possible
layers are ODUk Path and ODUk TCM NIMs (Non Intrusive Monitoring) .
When establishing SNC/N TCM NIM (Non Intrusive Monitoring) protection, the same
TCM layers must be provisioned and used both for the protected and the protecting. The
TCM layers must be provisioned as NIMs for both. When establishing Path NIM
protection, both protected and protecting POMs (Path Overhead Monitoring) must be
enabled.
CNVT-CCTPR-ODU0
CNVT-CCTPR-ODU1
CNVT-CCTPR-ODU2
CNVT-CCTPR-ODU2E
CNVT-CCTPR-ODU3
CNVT-CCTPR-ODU3E2
....................................................................................................................................................................................................................................
1830 PSS
9-12
Issue 1 June 2013

....................................................................................................................................................................................................................................
CNVT-CCTPR-ODU4
CNVT-CCTPR-STS1
CNVT-CCTPR-STS3C
CNVT-CCTPR-STS12C
CNVT-CCTPR-STS48C
CNVT-CCTPR-VC4
CNVT-CCTPR-VC44C
CNVT-CCTPR-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Open the Alcatel-Lucent 1830 PSS ZIC Manage Cross Connections window.
Reference: Refer to Different ways to modify a cross-connection (p. 11-8).
...................................................................................................................................................................................................
In the field Display Options check the checkbox Protection Parameters.

Result: All protection parameters are displayed.
...................................................................................................................................................................................................
Select unprotected cross-connection in the cross connection list.

Result: The selected cross-connection is highlighted and the Protect button enabled.
...................................................................................................................................................................................................
Click Protect.
....................................................................................................................................................................................................................................
1830 PSS
9-13
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result:
The Select NEWFROM Facility window opens.
Note: The NEWFROM=TO option is available for 2WAY cross-connections only.

...................................................................................................................................................................................................
If
then
you want to make the source of the existing

cross-connection to the protected leg of the
new path-protected cross-connection,
select NEWFROM=FROM, and specify the

desired protecting leg of the new
path-protected cross-connection by means of
the ALTERNATE Facility field (clicking on the
button next to the ALTERNATE Facility field
opens the Facility Browser).
you want to make the source of the existing

cross-connection to the protecting leg of the
new path-protected cross-connection,
select NEWFROM=ALTERNATE, and specify the

desired protected leg of the new path-protected
cross-connection by means of the ALTERNATE
Facility field (clicking on the button next to
the ALTERNATE Facility field opens the
Facility Browser).
you want to add a protection leg to the input

tributary corresponding to the destination of
the existing cross-connection,
select NEWFROM=TO, and specify the desired

protecting leg of the new path-protected
cross-connection by means of the ALTERNATE
Facility field (clicking on the button next to
the ALTERNATE Facility field opens the
Facility Browser).
...................................................................................................................................................................................................
Click Apply.
....................................................................................................................................................................................................................................
1830 PSS
9-14
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: A confirmation window opens, stating that modifying a cross-connection is
service affecting.
...................................................................................................................................................................................................
Click OK.
Result: The cross-connection is modified.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-15
Issue 1 June 2013

Procedure 9-2: Remove a protection leg from a

cross-connection
....................................................................................................................................................................................................................................

cross-connection
When to use
Use this procedure to remove a protection leg from a cross-connection.

Supported conversions
The following conversions will be supported:
1WAYSNCP -> 1WAY

2WAYSNCP -> 2WAY
Figure 9-4 Removing a protection leg from a one way protection
....................................................................................................................................................................................................................................
1830 PSS
9-16
Issue 1 June 2013


cross-connection
....................................................................................................................................................................................................................................
Figure 9-5 Removing a protection leg from a two way protection
The cross-connection to be modified is addressed by the TO parameter (called original

cross-connection). The cross-connection Identifier is taken over from the already existing
cross-connection if not provided. When deleting a protection leg it can be specified which
leg (FROMPING or FROMPED) will be the new FROM (NEWFROM) of the
unprotected cross-connection. The NEWFROM parameter of the command must be one
of the FROMPED or FROMPING of the original path protection cross-connection.
Deleting a protection leg may lead to a re-connection of the new FROM and TO
depending of the protection state.
CNVT-CCTU-ODU0
CNVT-CCTU-ODU1
CNVT-CCTU-ODU2
CNVT-CCTU-ODU2E
CNVT-CCTU-ODU3
CNVT-CCTU-ODU3E2
CNVT-CCTPR-ODU4
CNVT-CCTPR-STS1
CNVT-CCTPR-STS3C
CNVT-CCTPR-STS12C
....................................................................................................................................................................................................................................
1830 PSS
9-17
Issue 1 June 2013


cross-connection
....................................................................................................................................................................................................................................
CNVT-CCTPR-STS48C
CNVT-CCTPR-VC4
CNVT-CCTPR-VC44C
CNVT-CCTPR-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select protected cross-connection in the cross connection list.

Result:
The selected cross-connection is highlighted and the Unprotectbutton is enabled.
....................................................................................................................................................................................................................................
1830 PSS
9-18
Issue 1 June 2013


cross-connection
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Unprotect.
Result:
The Select NEWFROM Facility window opens.
...................................................................................................................................................................................................
If
then
you want to make the protected leg of the

existing path-protected cross-connection to the
source of the new unprotected
cross-connection (remove the protecting leg),
select NEWFROM=FROM, and click Apply in

the Select NEWFROM Facility window.
you want to make the protecting leg of the

existing path-protected cross-connection to the
source of the new unprotected
cross-connection (remove the protected leg),
select NEWFROM=ALTERNATE, and click

Apply in the Select NEWFROM Facility
window.

service affecting.
...................................................................................................................................................................................................
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-19
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create an SNCP (Sub-Network Connection Protection) for OTH
applications.
1+1 SNCP for:
ODU0
ODU1
ODU2
ODU2E
ODU3
ODU3E2
ODU4
SNCP/UPSR protection schemes are realized via a broadcast in transmission direction

and the protection switch in receive direction on time slot level. Configure the SNCP for
the two NEs between which the protected path is to be established.
SONET/SDH specifics
If 1WAYSNCP cross-connections is specified, a one-way SNCP cross-connection is

established between the unprotected receive side (the FROMPED facility, unprotected
from the network, unprotected source of cross connection), the protecting receive side
(the FROMPING facility, protecting from the network, protecting source of
cross-connection) and the transmit side ( the TO facility, to the network, sink of the cross
connection).
If 2WAYSNCP cross-connections is specified, a two-way SNCP cross-connection is
established between the unprotected FROMPED facility, the protecting FROMPING
facility and the TO facility. In the FROMPED / FROMPING -> TO direction the
protection switch will select one of the FROMPED and FROMPING facilities as the
active one, while in the TO -> FROMPED / FROMPING direction the cross-connection
works as a bridge.
It is possible to add to the FROMPED and FROMPING facilities 1 WAY multicast
connections.
Several SNCP cross-connections can be established with the same FROMPED and
FROMPING facilities (but different TO facilities). This SNCP cross-connections can be
of different SNCP types (SNCP/I or SNCP/N).
....................................................................................................................................................................................................................................
1830 PSS
9-20
Issue 1 June 2013

....................................................................................................................................................................................................................................
UPSR type connections are supported via SNCP.
A UPSR 2WAYPR type connection is the same as 2WAYSNCP described above.
A UPSR 1WAYTHRU/THRU type connections is the same as 1WAY/2WAY

described above. It shall be up to the user to ensure that the through paths are the
same "ring" time slots.
ODUk specifics
Protection connections are allowed for ODUk NIMs and transparent transport ODUk
entities. In such cases, these entities are allowed to be the FROMPED, FROMPING, or
TO facilities.
Protection connections are also allowed for path terminated cross connections involving
virtual ODUk path terminated entities. However these entities always need to be the TO
facility of the connection. ODUk SNC/NC based on ODUkP Client Signal Non-Intrusive
Monitoring and ODUk SNC/N based on ODUkP/T Non-Intrusive Monitoring is
supported.
Transparent transport ODUk entities are only allowed to be the FROMPED/PING
facilities if the protection type is SNC/NC; Otherwise they are required to be the outgoing
TO facility.
SNC/NC protection for STM-n / OC-n clients
SNC/NC is only allowed when both protected/protecting entities are transparent transport
ODUk entities.
SNC/NC is only allowed, when both incoming protected and protecting transparent
tranport ODUs carry SDH/SONET client traffic. SNC/NC is only allowed, when in case
of SDH/SONET client signals both incoming protected and protecting client signals have
equal SDH/SONET rate.
The following SDH/SONET client traffic is supported:
STM-64/OC-192 transparently mapped into ODU2.

STM-16/OC-48 transparently mapped into ODU1.
STM-1/STM-4/OC-3/OC-12 transparently mapped into ODU0.
SNC/I protection
SNC/I protection generally protects against failures in the server layer. The protection
process and the defect detection process are performed by two adjacent layers. The server
layer performs the defect detection process, and forwards the status to the client layer by
means of the Server Signal Fail (SSF) signal.
....................................................................................................................................................................................................................................
1830 PSS
9-21
Issue 1 June 2013

....................................................................................................................................................................................................................................
ENT-CRSPROT-ODU0
ENT-CRSPROT-ODU1
ENT-CRSPROT-ODU2
ENT-CRSPROT-ODU2E
ENT-CRSPROT-ODU3
ENT-CRSPROT-ODU3E2
ENT-CRSPROT-ODU4
ENT-CRSPROT-STS1
ENT-CRSPROT-STS3C
ENT-CRSPROT-STS12C
ENT-CRSPROT-STS48C
ENT-CRSPROT-VC4
ENT-CRSPROT-VC44C
ENT-CRSPROT-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectCrossConnection.

Then select Create Cross Connections, either by selecting Action from the main menu
....................................................................................................................................................................................................................................
1830 PSS
9-22
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Create Cross Connections window opens.
For an alternative way to navigate directly from a facility to the Alcatel-Lucent

1830 PSS ZIC Create Cross Connections window, see How to navigate directly
from a facility to the Create Cross Connections window (p. 11-13).
...................................................................................................................................................................................................
Click the Wizard button.

Result: The Alcatel-Lucent 1830 PSS ZIC Connection Wizard window opens.
...................................................................................................................................................................................................
In the field Connection Type select the type of cross-connection you want to set up.
Additional info: Connection Type
1WAYSNCP
One-way SNCP cross-connection (unidirectional SNCP cross-connection)
2WAYSNCP
Two-way SNCP cross-connection (bidirectional SNCP cross-connection)

...................................................................................................................................................................................................
In the facility area, use the FROM and TO fields to populate the respective fields with the
needed facilities.
A transmission facility may be one of the following (both for unidirectional and
bidirectional transmission):
ODU0
ODU1
ODU2
ODU2E
ODU3
ODU3E2
ODU4
In SDH networks:
VC-4
VC-4-4c
VC-4-16c
In SONET networks:
STS-1
STS-3c
....................................................................................................................................................................................................................................
1830 PSS
9-23
Issue 1 June 2013

....................................................................................................................................................................................................................................
STS-12c
STS-48c
Repeat Count: By using the Repeat Count field, you can create a range of multiple
similar SNCP protection groups whereby the specified FROM and TO facility and the
facilities subsequent to these facilities will be used.

...................................................................................................................................................................................................
Click Apply.
Result: The From Facility and To Facility fields of the table in the Create Cross
Connections window is populated with the selected facilities. In case you entered a
repeat count greater than 1, the corresponding number of rows will be displayed.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the Sub Network Protection Type:

Protection Type
SNC/N
SubNetwork Connection Protection with Nonintrusive monitoring
SNC/NC
Sub Network Connection protection based on ODUkP Client Signal with

Non-intrusive monitoring
SNC/I
Sub Network Connection protection with Inherent monitoring

...................................................................................................................................................................................................
Select the Protected Protection Mode:

Protecting Protection Method. The protection Method can be at the ODUk Path NIM or a
TCM NIM.
Protected Protection Mode
PM Overhead
TCM-1 Overhead
TCM-2 Overhead
TCM-4 Overhead
TCM-3 Overhead
....................................................................................................................................................................................................................................
1830 PSS
9-24
Issue 1 June 2013

....................................................................................................................................................................................................................................
TCM-5 Overhead
TCM-6 Overhead
...................................................................................................................................................................................................
Select the Hold Off Timer.

Possible values:

0, 30, 50, 70, 100, 300, 500, 700, 1000, 3000, 5000, 10000.
Note that the hold-off time should be configured that an interaction with other protection
schemes (equipment protection) is taken into consideration. Via different hold-off times it
can be defined which protection should switch first. That avoids doubled switches.
...................................................................................................................................................................................................
10
Using the Revertive field, define whether the SNCP shall operate in revertive or
non-revertive mode.
N - No, do not revert to protected (non-revertive mode).
Y - Yes, revert to protected (revertive mode).
In revertive mode, traffic will be reverted to the protected leg of the SNCP/UPSR
once the protected leg becomes available again after a protection switch to the
protecting leg.
...................................................................................................................................................................................................
11
Select the Revert Delay Time (Wait to restore (WTR) time) if the SNCP/UPSR is
working in revertive mode. Values between 0 and 15 min are allowed.
Important! When re-configuring a WTR (Wait to restore) timer during WTR state,
the WTR is restarted with the new provisioned time regardless of the already elapsed
time of the previous setting.
...................................................................................................................................................................................................
12
Select if Signal Degrade is to used is used for protection switching or not.

...................................................................................................................................................................................................
13
Click the Apply button to apply your settings.
....................................................................................................................................................................................................................................
1830 PSS
9-25
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: A confirmation window opens, stating that deleting a cross-connection is
service affecting.
...................................................................................................................................................................................................
14
Click OK.
Result: The cross-connection is created.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-26
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify an SNCP protection group.

ED-CRSPROT-ODU01
ED-CRSPROT-ODU1
ED-CRSPROT-ODU2
ED-CRSPROT-ODU2E
ED-CRSPROT-ODU3
ED-CRSPROT-ODU3E2
ED-CRSPROT-ODU4
ED-CRSPROT-STS1
ED-CRSPROT-STS3C
ED-CRSPROT-STS12C
ED-CRSPROT-STS48C
ED-CRSPROT-VC4
ED-CRSPROT-VC44C
ED-CRSPROT-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
9-27
Issue 1 June 2013

....................................................................................................................................................................................................................................

...................................................................................................................................................................................................

Result: All Protection parameters are displayed.
...................................................................................................................................................................................................
Select the Sub Network Protection Type:
SNC/N
Sub Network Connection protection with Nonintrusive monitoring
SNC/NC
Sub Network Connection protection based on ODUkP Client Signal with

Non-intrusive monitoring
SNC/I
Sub Network Connection protection with Inherent monitoring. SNC/I protection

generally protects against failures in the server layer. The protection process and the
defect detection process are performed by two adjacent layers. The server layer
performs the defect detection process, and forwards the status to the client layer by
means of the Server Signal Fail (SSF) signal.
...................................................................................................................................................................................................

Possible values:
0, 30, 50, 70, 100, 300, 500, 700, 1000, 3000, 5000, 10000.
Note that the hold-off time should be configured , that an interaction with other protection
schemes (equipment protection) is taken into consideration. Via different hold-off times it
can be defined which protection should switch first.
...................................................................................................................................................................................................
Using the Revertive field, define whether the SNCP shall operate in revertive or
non-revertive mode.
N - No, do not revert to protected (non-revertive mode).
Y - Yes, revert to protected (revertive mode).
....................................................................................................................................................................................................................................
1830 PSS
9-28
Issue 1 June 2013

....................................................................................................................................................................................................................................
In revertive mode, traffic will be reverted to the protected leg of the SNCP/UPSR
once the protected leg becomes available again after a protection switch to the
protecting leg.
...................................................................................................................................................................................................
Select the Revert Delay Time (Wait to restore (WTR) time) if the SNCP/UPSR is
working in revertive mode. Values between 0 and 15 min are allowed.
...................................................................................................................................................................................................

service affecting.
...................................................................................................................................................................................................
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-29
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete an SNC protection group.

DLT-CRSPROT-ODU0
DLT-CRSPROT-ODU1
DLT-CRSPROT-ODU2
DLT-CRSPROT-ODU2E
DLT-CRSPROT-ODU3
DLT-CRSPROT-ODU3E2
DLT-CRSPROT-ODU4
DLT-CRSPROT-STS1
DLT-CRSPROT-STS3C
DLT-CRSPROT-STS12C
DLT-CRSPROT-STS48C
DLT-CRSPROT-VC4
DLT-CRSPROT-VC44C
DLT-CRSPROT-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select Manage Cross Connections, either by selecting Action from the main menu
....................................................................................................................................................................................................................................
1830 PSS
9-30
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS ZIC Manage Cross Connections window
opens.
...................................................................................................................................................................................................
In the field Cross Connection Type select either 1WAYSNCP or 2WAYSNCP.

...................................................................................................................................................................................................
Click Retrieve.
Result: A confirmation window opens, stating that retrieval of cross-connection may
take some time.

...................................................................................................................................................................................................
Click OK.
take some time.

...................................................................................................................................................................................................
Click OK.
Result: All cross-connections of the selected type are displayed.
...................................................................................................................................................................................................
Select the SNCP protection group to be deleted in the list.

...................................................................................................................................................................................................
Click Delete.
service affecting.
...................................................................................................................................................................................................
Click OK.
Result: The cross-connection is deleted.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-31
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to initiate an SNC protection switch.

OPR-PROTNSW-ODU0
OPR-PROTNSW-ODU1
OPR-PROTNSW-ODU2
OPR-PROTNSW-ODU2E
OPR-PROTNSW-ODU3
OPR-PROTNSW-ODU3E2
OPR-PROTNSW-ODU4
OPR-PROTNSW-STS1
OPR-PROTNSW-STS3C
OPR-PROTNSW-STS12C
OPR-PROTNSW-STS48C
OPR-PROTNSW-VC4
OPR-PROTNSW-VC44C
OPR-PROTNSW-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectProtection.

Then select the protection group for which you want to initiate a protection switch
....................................................................................................................................................................................................................................
1830 PSS
9-32
Issue 1 June 2013

....................................................................................................................................................................................................................................
Then select Operate Switch, either by selecting Action from the main menu bar or by
Result: The Alcatel-Lucent 1830 PSS ZIC Operate Protection Switch Dialogue
window opens.
...................................................................................................................................................................................................
Select if it should be switched from working to protection or vice versa in the field
Destination Of Switch.
The following options are possible:
Protected Facility
Protecting Facility
...................................................................................................................................................................................................
Select the desired switch request in the field Switch Command Mode.
The following options are possible:
Lockout of Protection (for ODUk SNCP only)
Forced Switch
Manual Switch
...................................................................................................................................................................................................
Click Apply.
Result: The SNC protection group is switched.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-33
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to release an SNC protection switch.

RLS-PROTNSW-ODU0
RLS-PROTNSW-ODU1
RLS-PROTNSW-ODU2
RLS-PROTNSW-ODU2E
RLS-PROTNSW-ODU3
RLS-PROTNSW-ODU3E2
RLS-PROTNSW-ODU4
RLS-PROTNSW-STS1
RLS-PROTNSW-STS3C
RLS-PROTNSW-STS12C
RLS-PROTNSW-STS48C
RLS-PROTNSW-VC4
RLS-PROTNSW-VC44C
RLS-PROTNSW-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree selectProtection.

Then select the protection group for which you want to release a protection switch
....................................................................................................................................................................................................................................
1830 PSS
9-34
Issue 1 June 2013

....................................................................................................................................................................................................................................
Then select Release Switch, either by selecting Action from the main menu bar or by
Result: The Alcatel-Lucent 1830 PSS ZIC Release Protection Switch Dialogue
window opens.
...................................................................................................................................................................................................
Click Apply.
Result: The SNCP/UPSR protection switch is released.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-35
Issue 1 June 2013

Procedure 9-8: Retrieve configuration parameters and

status information of an SNC protection group
....................................................................................................................................................................................................................................
Procedure 9-8: Retrieve configuration parameters and status

information of an SNC protection group
When to use
Use this procedure to retrieve configuration parameters and status information of an SNC
protection group.
RTRV-CRSPROT-ODU0
RTRV-CRSPROT-ODU1
RTRV-CRSPROT-ODU2
RTRV-CRSPROT-ODU2E
RTRV-CRSPROT-ODU3
RTRV-CRSPROT-ODU3E2
RTRV-CRSPROT-ODU4
RTRV-CRSPROT-STS1
RTRV-CRSPROT-STS3C
RTRV-CRSPROT-STS12C
RTRV-CRSPROT-STS48C
RTRV-CRSPROT-VC4
RTRV-CRSPROT-VC44C
RTRV-CRSPROT-VC416C
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
9-36
Issue 1 June 2013


....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Retrieve.
take some time.

...................................................................................................................................................................................................
Click OK.
...................................................................................................................................................................................................
To display all protection parameters select the Protection Parameters check box in the
Display Options field.
Result: The parameters as described in Manage Cross Connections window
(p. 9-6)are displayed

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
9-37
Issue 1 June 2013

....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
9-38
Issue 1 June 2013
10
10 network
WDM
configuration procedures
Overview
Purpose
This chapter describes the procedures which have to be performed for the WDM network
configuration. This comprises basically the setup of WDM network protections,
Wavelength Tracker, FOADM / FOADM-TOADM system, and power settings.
Related information
For conceptual information see Alcatel-Lucent 1830 PSS Product Information and
Planning Guide (PIPG), chapter 5 Provisioning, section Protection switching.
For the basic cross-connection type see Cross-connection types (p. 11-2).
Contents
Introduction
10-4
Protection
10-4
10-16
10-16
Create APS Group
10-17
Create APS Group
10-19
Procedure 10-2: View all protection groups
10-22
Automatic Protection Switch Groups
10-23
Procedure 10-3: View/modify protection group
10-26
10-27
Procedure 10-5: Request protection switch
10-28
10-29
Procedure 10-7: Configure E-SNCP protection
10-34
...................................................................................................................................................................................................................................
1830 PSS
10-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 10-8: Configure OPS client side protection
10-36
10-40
Wavelength Tracker
10-50
Procedure 10-10: Provision wave keys on an encoder port to support dangling

OT procedure
10-55
Wave Key Encoder
10-57
Procedure 10-11: Set expected network output power
10-58
Procedure 10-12: View wave keys (decoder ports)
10-59
Wave Key Decoder
10-60
Procedure 10-13: Clear wave keys
10-62
Procedure 10-14: Set power
10-63
Set Power
10-64
10-65
Wavelength Tracker Power Summary
10-66
Procedure 10-16: View unexpected wave keys
10-67
Unexpected Wave Keys
10-68
10-69
Wave Keys
10-70
Procedure 10-18: View unexpected/missing wave keys at NE level
10-72
10-73
Missing Wave Keys
10-74
Procedure 10-19: Provision optical line's monitoring (WT mode or WTOCM

mode)
10-75
Port Power Management
10-76
Procedure 10-20: Add a service to a FOADM system or mixed

FOADM-TOADM system
10-78
Procedure 10-21: Add an Anydirection Add/Drop block to ROADM
10-83
Power settings
10-86
Procedure 10-22: Power management
10-89
10-90
Procedure 10-23: Power adjustment
10-92
Power Adjustment
10-94
Procedure 10-24: View/modify power commissioning values
10-96
....................................................................................................................................................................................................................................
1830 PSS
10-2
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Power Commissioning
10-97
10-109
10-114
Power Adjustment
10-115
Procedure 10-26: GMRE settings
10-116
10-117
Procedure 10-28: GMRE OMS line parameters
10-118
10-119
Procedure 10-30: Cross-phase modulation allowed wavelength set
10-120
....................................................................................................................................................................................................................................
1830 PSS
10-3
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
Introduction
Protection
Y-cable protection
Y-cable protection is a line side (network side) protection mechanism which protects line
card, client side laser, network side laser, and network side fibers (assuming diverse fiber
routes). Y-cable protection is based on permanent head-end bridging and tail-end
selection, with a pair of OT cards at each end. The head-end bridge is done by employing
a 50% splitter on the Rx of the client-side ports. The incoming signal from the customer
equipment is split and received by both the working and protection OT cards. The tail-end
selection is done by having one of the working/protection OT cards turn its Tx client-side
laser on, while the other turns its laser off. This Tx signal is channelled through a joiner
(splitter in reverse direction) and sent to the customer equipment. Either the working or
the protection card can drive the signal through the joiner. The same configuration is used
in the reverse direction to provide protection in both directions.
Y-cable supports the protected OT configuration. A passive splitter/joiner (Y-cable) is
connected to a pair of client ports on redundant transponder packs (OTs) at one end of the
network, with the same arrangement at the other end of a point-to-point link across the
network. The OT line ports must be connected to diversely routed working and protection
lines across the network (no shared risk groups in common). The customer is responsible
for establishing diverse routes; there is no software verification of this.
Port numbers for Y-cable protection must match. In other words, port #1 can only be
paired in Y-cable protection arrangement with port #1 on the adjacent card. Similarly, port
#2 works with port #2 on the adjacent card, and so on.
Y-cable protection can be used with any supported type of OT, but the near-end working
OT must be connected to the far-end working OT and the near-end protection OT must be
connected to the far-end protection OT. The customer is responsible for seeing to it that
near-end and far-end OTs are the same. The ports must be provisioned for the same signal
rate and format at both ends of the network. The customer should normally configure
working and protection ports with the same threshold values.
Note: Both unidirectional and bidirectional are supported for Y-cable protection.
Note: Combination of E-SNCP and Y-cable protection on the same OT is not
supported.
....................................................................................................................................................................................................................................
1830 PSS
10-4
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
Protection groups
The NE supports the definition of a Y-cable protection group. This logical object is the
basis for automatic and manual protection switching operations and notifications. A
Y-cable protection group represents the protection association between two client-side
ports of adjacent OT packs. Protection switching is performed only within an established
protection group. When there is no protection group, no protection switching can occur,
either manual or automatic.
An OT with 10 client ports can have up to 10 separate Y-cable protection groups.
Switching operations, both manual and automatic, are on a per protection group basis.
Each protection group operates completely independently of the others, with its own
protection state machine. For the first Y-cable protection group between a pair of adjacent
OT ports, the user is free to specify either port as the working port, and the other port as
the protection port. This choice designates one OT as the working card, and the other as
the protection card.
When there are multiple Y-cable protection groups between the same pair of OTs, the
working/protection port role designations must be specified consistently (i.e. all working
ports must be on one OT, and all protection ports must be on the other OT).
The WebUI supports create, modify, delete, and view functionality for protection groups
associated with a port. The following cards support Y-cable: 112SCX10, 112SNX10,
130SCX10, 11DPE12A, 11DPM12, 11QPA4, 11QPEN4, 11STAR1, 11STAR1A,
11STGE12, 11STMM10, 43SCX4, 43SCX4E, 43STA1P, 43STX4(P) and 4DPA4
(FlexMux).
Note: Alcatel-Lucent 1830 PSS does not support Y-cable protection on the 11STAR1,
11STAR1A, 11QPA4, 11QPEN4 packs when the client signal type is OTU2.
Note: For 11QPA4 8GFC/OC192/STM64/10GFC client ports, bi-directional and
uni-directional Y-Cable are supported. For Ethernet client ports (10GBE):
bi-directional Y-cable is supported. The 11QPA4 OT cannot support Y-cable
protection with OTM0.2 client.
112SCX10/112SNX10/130SCX10 Y-cable supports unidirectional and bidirectional
and non-revertive only. Revertive switching is not supported.
Note: For 11DPM12 the following applies:
The oduk cross-connect must be created from client ports Lo-oduk entity to L1 port
Lo-oduk entity. L2 port is not permitted to create oduk cross-connect with client port
in Y-cable protection group.
The Lo-ODUk ID in line port associated with client ports should be the same for local
working and protection ports.
....................................................................................................................................................................................................................................
1830 PSS
10-5
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
Note: Y-cable performance times may not be met on MUX OTs if more than 4 ports
on each OT belong to a protection group. Under this condition, the switch time can
exceed 50ms,
Uni-directional switching
In uni-directional switching, each end makes an independent switching decision based on

defects affecting the direction of transmission received from the line side, or based on
user command. One end may select from the working line while the other end is selecting
from protection. Uni-directional protection switching can be used to protect either
uni-directional or bi-directional customer services. There is no difference in protection
group provisioning or behavior for the two types of traffic.
Uni-directional Y-cable is subject to the following limitations on Ethernet client ports.
When Ethernet autoneg=enabled on the client port, uni-directional Y-cable cannot be

supported on any card
When Ethernet autoneg=disabled on the client port, uni-directional Y-cable support

varies by card type
11STAR1, 11STAR1A: uni-directional Y-cable is supported with CBR client
mapping, but is not supported with GFP-F client mapping.
1STMM10: uni-directional Y-cable is supported.
11STGE12: uni-directional Y-cable is not currently supported
43STX4, 43STX4P: uni-directional Y-cable is supported
43SCX4(E): uni-directional Y-cable is supported

112SCX10, 112SNX10: uni-directional Y-cable is supported
11QPA4: uni-directional Y-cable is supported with CBR client mapping, but is not
supported with GFP-F client mapping
11DPM12: uni-directional Y-cable is supported
Bidirectional switching
In bidirectional switching, an end-to-end APS message protocol is used to guarantee that

the selectors at both ends of a circuit are always synchronized - either both on working, or
both on protection. Whether the switch is caused by a defect or a user command, both
ends always switch together.
Bidirectional protection switching can be used to protect only bi-directional customer
traffic. If a bi-directional Y-cable protection group is connected to a unidirectional Y-cable
protection group across the network, the bidirectional group will operate as a
unidirectional group for switching compatibility (the bidirectional end will raise an
alarm).
....................................................................................................................................................................................................................................
1830 PSS
10-6
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
In non-revertive switching, the protection side remains active after the working line has
recovered from the failure that caused the automatic switch to protection, or after the user
switch-to-protection command is cleared.
Note: For 43STA1P and 43STX4(P), 4DPA2, and 4DPA4 OTs switching type must be
non-revertive.
Revertive switching
In revertive switching, the traffic is automatically switched back to the working line when
the working line has recovered from the failure or the user command is cleared. In the
failure-recovery case, the switch back to working is delayed until working has been
continuously good for the number of minutes specified by the WTR parameter. In the case
of clearing a user switch command, there is no delay.
Note: If Direction = Unidirectional, then Type must be Non-Revertive. For
Bidirectional, both Revertive and Non-Revertive are supported. Optical connections
must be created before a protection group, and a protection group must be deleted
before its optical connections.
OPS protection
For OPS protection of optical channels, the OPS is placed at the Optical Channel (OC)
layer, between the Optical Multiplexing layer and the Optical Channel to Optical Signal
(OCH/OS) adaptation, (i.e., the OT function).
The OPS supports two types of protected line configurations. In both cases, there is a
single unprotected OT at each end. In both cases, the working and protection lines must
be diversely routed across the network (no shared risk groups in common).
Internal OT, no SVACs - The OT line port is connected to the OPS SIG port. The OPS
A port and B port are connected to two different lines, either via SFD filter ports, or
via CWR8 colorless ports.
Alien/External OT, redundant SVACs - The alien OT is connected to the OPS SIG
port. The OPS A port and B port are connected to two different SVACs. The two
SVACs are connected to two different lines, either via SFD filter ports, or via CWR8
colorless ports.
Note: OPS protection can be used with two MVACs. For this type of protection an
OPS card is placed on the client-side optical path of the MVACs. Protection is
provided against both fiber cuts and MVAC failure.
OPS protection can be used with any supported type of OT (130SCX10, 112SCA1,
112SNA1, 112SCX10, 112SNX10, 11QPA4, 11QPEN4, 11STAR1, 11STAR1A,
11STGE12, 11STMM10). There is no restriction on physical location within the NE of
the associated OT, OPSA, SFD, CWR, or SVAC circuit packs. The packs can all be in
different shelves if desired. For packs in the same shelf, there is no requirement for
....................................................................................................................................................................................................................................
1830 PSS
10-7
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
physical adjacency. In the receive direction (selector function), the two SFD/CWR ports
connected to the OPS A and B ports can have different frequencies. In the transmit
direction (splitter function), the two SFD/CWR ports must have the same frequency.
Protection groups
The NE supports the definition of an OPS protection group. This logical object is the
basis for automatic and manual protection switching operations and notifications. An OPS
protection group represents the protection association between the two line-side ports (A
and B) of a single OPSA pack. Protection switching is performed only within an
established protection group. When there is no protection group, no protection switching
occurs, either manual or automatic. The user is free to specify either of the line-side ports
(A or B) as the working port, and the other port as the protection port.
Note: For OPS protection group creation, ports A and B cannot be in-service. They
must be down or in maintenance state (mt). The default OPS port state is down.
OPS protection groups support only uni-directional protection switching. In

uni-directional protection switching, each end of an optical channel operates
independently of the other. A failure affecting only one direction of transmission will
cause a protection switch of only that direction. The unaffected direction of transmission
is not switched. OPS protection groups do not use any end-to-end APS protocol. All
switch requests are local. The two ends have no knowledge of each other.
OPS protection groups support only non-revertive protection switching. There is no

automatic switch from protection back to working because of a recovery of working, or
because a user switch to protection is cleared.
Client- side OPS protection
In the client side OPS protection configuration, two OTs are used. Protection is provided
against a line failure (such as fiber cut or LD failure), OT failure and shelf power failure.
The OPSB board with non-latching switch is used for client side OPS protection. The
following applies:
The OPSB board is only used in Client Side OPS Protection (OTUP: Optical
Translator Unit Protection). The user can not provision the protection mode type.
Only the OPSB board can be used as OPS type board in the Client Side OPS
Protection configuration.
The Client Side OPS Protection is supported in TOADM, ROADM and FOADM
nodes. The OPS type board is positioned between unprotected client equipment and
OT client side port.
....................................................................................................................................................................................................................................
1830 PSS
10-8
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
The OT's supported in the Client Side OPS Protection include:
11QPA4
11STAR1
11STAR1A
11STMM10
The working and protection OT combinations supported in the Client Side OPS
Protection include.
11QPA4 with 11QPA4

11QPA4 with 11STAR1
11QPA4 with 11STAR1A
11STAR1 with 11STAR1

11STAR1A with 11STAR1
11STAR1A with 11STAR1A

11STMM10 with 11STMM10
For additional details see 1830 PSS Product Information and Planning Guide.
E-SNCP protection
Subnetwork Connection Protection (SNCP) is a dedicated protection mechanism

providing path-level protection for individual optical channels that are routed
independently across any network. It may be applied at any path layer in a layered
network. SNCP is a dedicated 1+1 protection architecture in which the traffic is
permanently bridged onto two SNCs at head-end, carried through any number of facilities
of any type, and selected from one of the two SNCs at the tail-end. One SNC is called the
working SNC and the other is called the protection SNC. The path selection is based on
purely local information: server layer information (SNC/I), client layer information
(SNC/N) or TC monitoring information (SNC/S).
E-SNCP on 11DPE12, 11DPE12A, 11DPE12E, 11DPM12, 11QPA4, 11QPEN4, 4DPA4,
and 4DPA2 OT is a line side (network side) protection mechanism which protects against
network side SFP related failure, line signal failure caused by network side fiber
disconnection or intermediate NE nodes malfunction.
E-SNCP protection is implemented by permanent head-end bridging and dynamic tail end
selection. The E-SNCP function is realized within one OT. Each client port (plus the two
line ports) form an independent protection group. But due to hardware restriction, the
bridging is performed at ODU1 level. As a result, all client ports assigned to the working
line are bridged simultaneously to the protection line. (From this perspective, E-SNCP is
a board level behavior.)
....................................................................................................................................................................................................................................
1830 PSS
10-9
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
In the source direction, traffic from the client ports is aggregated into one ODU1 line
signal, then the ODU1 signal is bridged into two parts, one for working path and another
for protection path. Both parts are inserted with OTU1 overhead and FEC code being sent
to the lines. The optical wavelengths are then modulated with WT encoder/eVOA before
sending to the SFD or FOADM.
In the receiving direction, the OT receives two OTU1 line signals (working and
protection). After FEC error correction and OTU1/ODU1 overhead termination
respectively, client traffic is extracted independently from the two line signals according
to the OPTS mapping structure determined for the outgoing direction. Then, depending
on the external switch commands for individual protection groups, or signal quality, the
traffic for each client port is selected independently from the working or protection line
port.
Note: On a given 4DPA4/4DPA2 card, either all services are protected, or all services
are unprotected. There can be no mixing or combining protected/unprotected services.
Note: Protection is not supported on a 11DPE12(E) card if Operational Mode =
Sub-rate. For 11DPE12(E) OT both revertive and non-revertive are supported when
Direction = Unidirectional.
Note: Combination of E-SNCP and Y-cable protection on the same 11QPA4 OT is not
supported.
Protection groups
Each protection group consists of one client port, plus the working line port and
protection line port. Up to 4 protection groups can be created - one for each client port.
Switching operations, both automatic switching and user commands, are on a per
protection group basis. Each protection group operates completely independently of the
others, with its own protection state machine.
Before starting the creation of protection group, at least one line port must be in IDLE
state (no client port has timeslot assignments to this line port). Otherwise, creation of
protection group is denied.
If initially both line ports are in IDLE state (no timeslot assignments), the user is free
to specify either line port as the working port and the other line port as the protection
port for the first protection group, but the subsequent protection group creations have
to follow working/protection designation by the first protection group.
If initially one line port has timeslot assignments, then all protection group creations
have to specify this line port as the working line port. Otherwise, creation of
protection group is denied.
For 11DPE12(A/E) and 4DPA4 OTs, if one or both of the line ports (L1 and/or L2) is
unassigned, then the protection group cannot be created. For 11DPE12(A/E), both line
ports must have Signal Rate = OTU2.
....................................................................................................................................................................................................................................
1830 PSS
10-10
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
On the 11DPE12(A/E) with Operational Mode = QinQ, up to 10 protection groups

may be supported per client port, one per VTS.
For 11QPA4 OT, the line port associated with the selected client port must be assigned
and have Operational Mode = Add/Drop or DropRegen in order to create a protection
group.
For 11DPM12, each ODU0 /ODU1/ODUflex encapsulating client signals (plus the
two-line ports) form an independent protection group. If client ports encapsulated into
one ODUPTF through OPTSG, the ODUPTF can be protected on ODU1 level. That
means all of the client signal encapsulating into OPTSG under the ODUPTF will be
protected simultaneously (all of the related client signals will be switched to the
protected line in case of a failure).
Note: When the time slot assignments on both OPTSG service ends are the same,
provisioning different OPTSG ID on each OPTSG service end could cause TS
mismatch (Time Slot assignment MISMATCH) against the OPTSG. The user should
use the same OPTSG ID.
Note: The switch time may exceed 50ms when the user provisions > 32 circuits.
ODUk Protection
The WebUI supports create, modify, delete and view of ODUk protection groups. These
protection groups are supported on the following ODU facilities:
WDM cards
11DPM12 client HO ODU NIM: OTUODU1

11DPM12 client transparent ODU: ODU0, ODU1, ODUFlex
11DPM12 ODU1PTF{1-8}
4QPA8 client transparent ODU: ODU0
4QPA8 ODU1PTF{1-4}
Client/Line
HO ODU NIM (physical card): OTUODU2, OTUODU2e, OTUODU4

Client transparent ODU (physical card): ODU0, ODU1, ODU2, ODU2e
LO ODU NIM (virtual): ODU2ODU0-{1-160}-{1-8}, ODU4ODU0-{1-16}-{1-80},
ODU2ODU1-{1-160}-{1-8}, ODU4ODU1-{1-16}-{1-80}, ODU4ODU2-{1-16}-{180}, ODU4ODU2e-{1-16}-{1-80}
HO ODU PTF (virtual) : ODU2-{1-160}, ODU4-{1-16}

ODUPOOL (virtual)
For WDM Cards: When creating a protection group, the current ODU will be designated
as the Client. Working and Protection ODUs are on the line ports on the same card as the
Client.
....................................................................................................................................................................................................................................
1830 PSS
10-11
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
The WebUI will allow selection of working and protection ODUs as follows:
If the Client is an endpoint of an ODUk cross-connect, then Working is the other

endpoint of the cross-connect. Else, any line port may be used for Working.
For both the working and protection ODU, the ODU rate (i.e. ODU0, ODU1 or
ODUFlex) must match the ODU rate of the Client.
If an ODU on one line port is selected for the working port, then an ODU on a
different line port must be used for the protection port.
The NE will automatically create the working and protection ODUk XCs (if client XC
does not exist) or protection ODUk XC (if client XC does exist) when the protection
group is created.
For Client/Line: When creating a protection group, the current ODU will be designated as
the Client.
The WebUI will allow selection of working and protection ODUs as follows:
If the Client is an endpoint of an ODUk cross-connect, then Working is the other

endpoint of the cross-connect.
For both the working and protection ODU, the ODU rate (i.e. ODU0, ODU1 or
ODUFlex) must match the ODU rate of the Client.
The NE will automatically create the working and protection ODUk XCs (if client XC
does not exist) or protection ODUk XC (if client XC does exist) when the protection
group is created.
Protection switch requests
Protection switching is implemented via automatic switch events, or from user switch
commands (override automatic switching). The WebUI allows the user to request a
protection switch and supports the following switch commands:
Clear - Clears any existing user switch command. Does not clear any existing WTR
state. In some cases a clear command can result in an immediate switch.
Lockout of Protection - Makes working active and prevents any subsequent switch to
protection for any reason until the lockout is cleared.
Forced Switch to Protection - Makes protection active.
Forced Switch to Working - Makes working active.
Manual Switch to Protection - Makes protection active.
Manual Switch to Working - Makes working active.
Note: These commands will be denied if an equal or higher priority request is already
in effect. Also, these commands will be denied if operation on the OT circuit packs is
not possible, whether due to circuit pack missing/failed, shelf or card communication
failed, or any other reason.
....................................................................................................................................................................................................................................
1830 PSS
10-12
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
OMSP protection (Optical Multiplex Section Protection)
The OPSA card is used for 1+1 OMSP protection. The automatic protection switching is
based on optical LOS (Loss Of Signal) detection. In the transmit direction, all output
channels from SFD/ITLB card are split into two separate optical multiplex sections routed
to working and protection optical paths. In the receive direction, the OPSA selector picks
one of the two lines as the active path based on power monitoring or user manual
selection.
The following OT cards support OMSP protection:
11DPE12
11DPM12 (Note: OMSP performance times may not be met on 11DPM12 1GbE ports
which have autoneg=enabled.)
11QPA4
11QPEN4
11STAR1
11STMM10
112PDM11
112SCX10
112SNX10
Note: The switching threshold for OMSP should be set approximately 5 dB below the
total input power at each of the A and B ports. In addition, a minimum channel
loading is needed to optimize the switching speed. If there are no ILAs on either the
working or protection paths, a single channel is required. If there are ILAs on either or
both paths, then set the maximum number of spans on either path to M. At least 2M
channels should be loaded on the system for optimum switching speed.
When the A or B port is placed OOS (administrative down) the attenuator is set to
maximum attenuation (applies only to OPSA used in OCH protection mode).
When an OT is protected by OMSP, the laser protection parameter for its client or
clients must be set to laser on.
Attention: OMSP must not be mixed with other existing protection types.
Manual power management
For OMSP protection, power management can only be set as manual on the working and
protection path (this is a system default setting). To ensure the transmission performance,
LDs gain should be manually set and all channels power should be equalized by
modifying target output power at each OTs line port according to Alcatel-Lucent's Power
Budget table.
....................................................................................................................................................................................................................................
1830 PSS
10-13
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
OMSP only supports uni-directional protection switching. In uni-directional protection

switching, each end of an optical multiplex section operates independently of the other.
OMSP only supports non-revertive protection switching. There is no automatic switch

from protection back to working upon recovery of working path, or upon a user switch to
protection being cleared.
OLP protection (Optical Line Protection)
Optical Line Protection is a 1+1 protection scheme for the optical line OTS layer,
providing two separate fiber connections between adjacent network element degrees.
(These separate connections could be diversely physically routed.) An optical protection
switch pack provides the optical bridging function at the source end and switch selection
of one of the signals from the two possibilities at the receiving end.
The following LD type packs are supported in networks using OLP:
Node Config
DFOADM
Valid Ingress LDs
Valid Egress LDs
AHPHG
None
AHPLG
AHPHG
AHPLG
A2325A
ROADM
AHPHG
None
AHPLG
AHPHG
A2325A
AHPLG
A2325A
ILA
AHPHG
Not applicable
AHPLG
A2325A
The following OT cards support OLP protection:
11DPE12A
11DPE12E
11DPM12 (Note: OLP performance times may not be met on 11DPM12 1GbE ports
which have autoneg=enabled.)
11QPA4
11STAR1
11STAR1A
....................................................................................................................................................................................................................................
1830 PSS
10-14
Issue 1 June 2013

Introduction
Protection
....................................................................................................................................................................................................................................
112SNA1
112SNX10
....................................................................................................................................................................................................................................
1830 PSS
10-15
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
When to use
Use the following procedure to create a protection group.

Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI equipment tree, select the port and click the Port Protection tab.
Result: The create APS Group screen is displayed.
...................................................................................................................................................................................................
Enter the APS group parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-16
Issue 1 June 2013

Create APS Group
....................................................................................................................................................................................................................................
Create APS Group

Attribute
Value/Format
Additional Info
Group ID
<integer>
Unique identifier of the

protection group.
This attribute is pre-populated
with the lowest available
Group ID that is not in use by
another protection group, but
a different value may be
specified.
Protection Mode
1+1 Optical Splitter

1+1 OPS
Indicates the type of

protection:
1+1 E-SNCP
1+1 Optical Splitter is
for Y-cable protection
1+1 OPS is for OPS
protection
1+1 E-SNCP is for
E-SNCP protection
Description
<0-50 chars>
the protection group.
Client Port
shelf/slot/port or
shelf/slot/port/vts
The client port in the

protection group. E-SNCP
protection only.
Working Port
<shelf/slot/port>or
<shelf/slot/port/vts>
The working port in the

protection group.
Protection Port
<shelf/slot/port> or
The protection port in the

protection group.
Switch Direction
Unidirectional (default)
In unidirectional switching,
local and remote ends switch
independently. In
bidirectional switching, local
and remote ends are
coordinated by an end-to-end
protocol so that both are on
working or both are on
protection. Only Y-cable
protection groups support
bidirectional operation.
Bidirectional
....................................................................................................................................................................................................................................
1830 PSS
10-17
Issue 1 June 2013

Create APS Group
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Type
Revertive
Indicates whether or not the

switching operation is
revertive. In non-revertive
switching, protection remains
active after working has
recovered from the failure
that caused the automatic
switch to protection or after
the user-initiated switch has
been cleared.
Non-revertive
In revertive switching, traffic

is automatically switched
back to working once the
cause of an automatic
protection switch has been
repaired, or the user-initiated
switch has been cleared. An
automatic switch does not
revert immediately, but waits
for the period of time
specified by Wait To Restore.
A user-initiated switch reverts
immediately. Revertive is
only supported for
Wait To Restore (minutes)
{1-20}
The protection group will

wait until working has been
continuously clear for this
number of minutes before
switching back to working.
Applies only for revertive
operation.
....................................................................................................................................................................................................................................
1830 PSS
10-18
Issue 1 June 2013

Create APS Group
....................................................................................................................................................................................................................................
Create APS Group

Attribute
Value/Format
Additional Info
Group ID
<integer>
Unique identifier of the

protection group.
This attribute is pre-populated
with the lowest available
Group ID that is not in use by
another protection group, but
a different value may be
specified.
Applicable when the
Protection Mode field is set to
1+1 Optical Splitter.
Protection Mode

1+1 E-SNCP

protection:
1+1 E-SNCP is for
E-SNCP protection
Description
<0-50 chars>
Client Port
<shelf/slot/port>
The client port in the

protection group. E-SNCP
protection only.
ODU1PTF
<shelf/slot/odu1ptfid>
The ODU1PTF in a
LO-ODUk E-SNCP
protection group.
Working Port
<shelf/slot/port>or
<shelf/slot/port/
oduid>

protection group.
Protection Port
<shelf/slot/port/
oduid>

protection group.
....................................................................................................................................................................................................................................
1830 PSS
10-19
Issue 1 June 2013

Create APS Group
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Connection Direction
Bidirectional
The direction for the ODUk

cross-connect.
Unidirectional
When creating an E-SNCP

protection group, this field is
required if the client port is
not the endpoint of an ODUk
cross-connect; otherwise this
field is not applicable.
Switch Direction
Unidirectional
independently. In
and remote ends are
bidirectional operation. When
creating a protection group,
this field is required if the
client port is not the endpoint
of an ODUk cross-connect;
otherwise this field is not
applicable.
....................................................................................................................................................................................................................................
1830 PSS
10-20
Issue 1 June 2013

Create APS Group
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Type
Non-revertive

been cleared.
only supported for
....................................................................................................................................................................................................................................
1830 PSS
10-21
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view all protection groups.

Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI equipment tree, select Reports > APS Groups

Result: The Automatic Protection Switch Groups screen is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-22
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Group ID
<integer>
Identifier of the protection

group
Description
<0-50 chars>
Protection Mode

1+1 OPS

protection:
1+1 E-SNCP
1+1 OPS is for OPS

protection
1+1 E-SNCP is for
E-SNCP protection
Client
shelf/slot/port or
shelf/slot/port/vts
The client port in a E-SNCP

protection group.
Line
The line port in a 3-line port

E-SNCP group.
Working

protection group.
Protection

protection group.
Switch Status
Protection Lockout
Indicates the current

switching status of the
protection group.
Forced Switch
Signal Failure
Signal Degrade
Manual Switch
Wait to Restore
Far End Request
Do Not Revert
No Request
Unknown
....................................................................................................................................................................................................................................
1830 PSS
10-23
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Switch Direction
Unidirectional
independently. In
and remote ends are
Bidirectional
Type
Revertive
Non-revertive

been cleared.
only supported for
....................................................................................................................................................................................................................................
1830 PSS
10-24
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
WTR (mins)
{1-20}
Wait to Restore: The

protection group will wait
until working has been
continuously clear for this
number of minutes before
switching back to working.
Applies only for revertive
operation.
....................................................................................................................................................................................................................................
1830 PSS
10-25
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view/modify a protection group.

Before you begin

Instructions
...................................................................................................................................................................................................
Result: The create APS Group screen is displayed if the selected port is not already a
member of an APS group. The APS Group Details screen is displayed if the selected
port is a member of an APS group.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-26
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to delete a protection group.

Before you begin

Instructions
Note: Deletion of a protection group will be denied if there are still cross connects
that depend on the protection group.
...................................................................................................................................................................................................
Result: The APS Group Details screen is displayed if the selected port is a member of
an APS group.
...................................................................................................................................................................................................
Select Delete this Protection Group and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-27
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to request a protection switch.

Before you begin

Instructions
Note: The WebUI does not allow the user to execute a switch command if the card is
not equipped. When a protection switch is requested, the WebUI displays a warning
message indicating that the switch could be service affecting (although traffic may be
unaffected). The user can continue with the request or cancel.
...................................................................................................................................................................................................
Result: The APS Group Details screen is displayed if the selected port is a member of
an APS group.
...................................................................................................................................................................................................
Select the switch request for the port and click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-28
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to configure OMSP protection.

Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI equipment tree, click the OPSA card and select OMSP mode in the
Protection Mode tab.
...................................................................................................................................................................................................
In the WebUI equipment tree, select OPSA A or B port. On Port Details tab the switch
threshold for OPSA A/B port should be set by user independently. The switch threshold
can be manually provisioned by user for different configurations.
...................................................................................................................................................................................................
The switch threshold should normally be provisioned to -4 dBm for the A and B inputs.
This will ensure that traffic restoration time will meet the target time.
...................................................................................................................................................................................................
On Port Protection tab, the protection group can be established for OMSP. If OPSA A
port is assigned for working path, protection group should be provisioned on A Port
Protection tab.
E...................................................................................................................................................................................................
N D O F S T E P S
LD provisioning
...................................................................................................................................................................................................
For OMSP configuration, two ingress LDs should be placed on each NE for working and
protection OMS paths. An egress LD may be required for long fiber span transmission.
....................................................................................................................................................................................................................................
1830 PSS
10-29
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Two parameters LOS Mode and APR Delay Enabled should be checked on each LDs SIG
and Line ports.
...................................................................................................................................................................................................
On the WebUI equipment tree, click AHPHGs SIG port, select SIG Details tab, and check
the LOS Mode as Auto.
...................................................................................................................................................................................................
In the WebUI equipment tree, click AHPHG Line port and select Port Details tab.
...................................................................................................................................................................................................
Check that APR Delay Enabled has NOT been selected.

E...................................................................................................................................................................................................
N D O F S T E P S
11STMM10 provisioning
...................................................................................................................................................................................................
To ensure 50ms traffic interrupt time on 11STMM10 OT, the parameters of holdoff timer
on line port and Los Propagation on client port must be enabled.
...................................................................................................................................................................................................
In WebUI equipment tree, click OTU2 port on 11STMM10 and select OTU2 Details tab.
...................................................................................................................................................................................................
Select Defect Holdoff Timer Enabled.

...................................................................................................................................................................................................
In WebUI equipment tree, click each client port on 11STMM10 and select Port Details
tab.
...................................................................................................................................................................................................
Check that LOS Propagation parameter is provisioned as Laser On.

E...................................................................................................................................................................................................
N D O F S T E P S
11DPM12 provisioning
...................................................................................................................................................................................................
To ensure 50ms traffic interrupt time on 11DPM12 OT, the parameters of holdoff timer on
line port must be enabled.
....................................................................................................................................................................................................................................
1830 PSS
10-30
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the WebUI equipment tree, click Client port for Port Details tab.
Note: For 1GbE client, the 50ms restoration time can only be met for the Ethernet
service if auto-negotiation is disabled.
E...................................................................................................................................................................................................
N D O F S T E P S
11QPA4/11STAR1/112SCX10 provisioning
...................................................................................................................................................................................................
To ensure 50ms traffic interrupt time on 11QPA4/11STAR1/112SCX10 OT, the parameter

of LOS Propagation on client port must provisioned as Laser ON.
...................................................................................................................................................................................................
In the WebUI equipment tree, click Client port for Port Details tab.
...................................................................................................................................................................................................
Check that LOS Propagation parameter is provisioned as Laser On.

...................................................................................................................................................................................................
If FC800 has been applied on 11QPA4 pack, the switch threshold values on OPSA A/B
ports should be provisioned as the A/B total input power minus 6dB.
E...................................................................................................................................................................................................
N D O F S T E P S
Physical topology and XC (cross connection) configuration

...................................................................................................................................................................................................
Open physical topology view and establish bidirectional fiber connection for OMSP
configuration.
...................................................................................................................................................................................................
Check that protection group has been established on OPSA

...................................................................................................................................................................................................
Open OCH XC view to establish two OCH XCs from OTU line port to ingress LDs line
port. One is working XC and one is protection XC.
...................................................................................................................................................................................................
For pairs of XCs created on each OT pack, the working/protection attributes should be
specified consistently, i.e. all working XCs must be on the same ingress LD which has
topology association with OPSA working port (for example A port), and all protection
....................................................................................................................................................................................................................................
1830 PSS
10-31
Issue 1 June 2013

....................................................................................................................................................................................................................................
XCs should be on the same ingress LD which has topology association with OPSA
protection port (for example B port).
E...................................................................................................................................................................................................
N D O F S T E P S
Manual power management
In OMSP configuration, working and protection paths Power Management Type should
only be set to Manual. The power level along the path must be manually adjusted by the
user and would include operations such as modifying the OT target output power and
setting the working and protection LDs gain according to Power Budget Table. For
egress power adjustment on FOADM end terminal, OT target output power or/and egress
LDs gain should be adjusted to guarantee that the services leaves the node at the target
egress power per channel for working path. For protection path only egress LDs gain
should be allowed to be adjusted to achieve the target total egress power. (User does not
need to change OPSA VOA setting from default value (0dB)). For ingress power
adjustment on FOADM end terminal, ingress LDs gain adjust should be made to achieve
the target ingress power at the ingress LD Sig Out port. The target ingress power for
ingress LDs on working and protection path should be the same. The following procedure
is used to View/modify OA gain and tilt values.
...................................................................................................................................................................................................
In the WebUI, select OAs SIG port with SIG Details tab.
...................................................................................................................................................................................................
To modify gain in provisionable attributes, enter the Gain value according to the power
budget table and click Apply.
...................................................................................................................................................................................................
To modify tilt in provisionable attributes, enter the Target Tilt value according to the
power budget table and click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
View/modify OT target output power values

...................................................................................................................................................................................................
In WebUI, select OT line port with Wave Keys Tab for OT with single tunable
transponder.
...................................................................................................................................................................................................
To modify Expected Network Output Power attributes enter the value according to
power budget table.
....................................................................................................................................................................................................................................
1830 PSS
10-32
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
For OT with VOA equipped select OT VA port with Wave Keys Tab and modify the
above attributes. The allowable setting value is from -5.5dBm to -20dBm.
...................................................................................................................................................................................................
Retrieve the measured channel power on ingress LDs line port Wave Keys OUT tab of
working path.
Note: Power-per-channel parameter should be enabled on ingress LDs line port for
retrieving the information
...................................................................................................................................................................................................
If the value has not achieved the target egress power, calculate the offset and change the
OTs output power by an amount equal to this offset to ensure each channel leaves the
node at the same target power.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-33
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to configure E-SNCP protection.

Before you begin

Instructions
...................................................................................................................................................................................................
Verify the resources in the network. Verify that the 11QPA4 transponders, XFP's, etc. are
installed and not in use.
In an initial state:
All related ports are unassigned.

No physical topology is defined.
No protection groups are defined.
...................................................................................................................................................................................................
Assign the client ports. The client ports must be assigned before a protection group can be
created.
Note: Only the client ports that are matching the Working or Protected Line ports
should be assigned.
...................................................................................................................................................................................................
Assign the network ports. The working or protected network ports must be assigned
before a protection group can be created.
...................................................................................................................................................................................................
Configure the working network ports.

The working or protected network ports should be configured:
Physical topology
ITU programmed
...................................................................................................................................................................................................
Create the protection groups. A protection group logically connects the Client port and the
Network ports that are used for the E-SNCP protection.
....................................................................................................................................................................................................................................
1830 PSS
10-34
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The create APS Group screen is displayed.
...................................................................................................................................................................................................
To create a protection group:

1.
2.
3.
4.
Select the Client port that corresponds with the protected (working) line port.
Use the right mouse control and select Configure Protection Group.
Verify/modify the field Protection Port to select the protecting (protection) line port.
Select Apply to create t he protection group.

Note: To create the protection group, the protection network port must be unassigned.
The protection group parameters Wait To Restore and Direction cannot be modified.
Result: The state of the protection line port will change from unassigned to assigned.
...................................................................................................................................................................................................
Configure the protection network ports.

The protection network ports should be configured:
Physical topology
ITU programmed
...................................................................................................................................................................................................
Create the E-SNCP protected service.

To create the service:
1.
2.
3.
4.
Select the service terminating nodes.

Select Provision - Provision Wavelength Service...
Select the A End CTP and Z End CTP.
Select PARTIALLY PROTECTED as Protection parameter.
5. Verify/adapt the routing.

6. Select the service attributes.
7. Verify the light-path.
...................................................................................................................................................................................................
Configure the client port parameters.

Some client port parameters should be configured after the protection group is created.
The most important parameter to verify/configure: Encapsulation mode.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-35
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to configure OPS client side protection with OPSB card.
Before you begin

Instructions
...................................................................................................................................................................................................
Provision the OPSB card and 2 OT cards on the network element.

...................................................................................................................................................................................................
Configure the switching threshold on the OPSB card.

In the WebUI equipment tree, select the OPSB A port.
On the Port Details tab, set the value for Switching Threshold.
Repeat for the OPSB B port.
CLI command example:
config interface opsb 1/31/a switch switchthre -10
config interface opsb 1/31/b switch switchthre -10
...................................................................................................................................................................................................
Create protection group on the OPSB card.

In the WebUI equipment tree, select the OPSB A/B port. If the A port is designated as the
working path, then the protection group is created on the OPSB A port. If the B port is
designated as the working path, then the protection group is created on the OPSB B port.
Select the Port Protection tab.
See Procedure 9-1 for provisioning details.
config aps group 1 create 1/31/b 1/31/a (port a as working path)
config aps group 1 create 1/31/a 1/31/b (port b as working path)
....................................................................................................................................................................................................................................
1830 PSS
10-36
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Provision the physical topology for the OPSB and OT cards.

Open physical topology view and establish bidirectional fiber connection for OPSB
configuration.
Note: For client side protection, there are 4 cases:
1. The OPSB A port connects to an OT that resides with the OPSB in the same shelf.
The OPSB B port connects to an OT in another 1830 NE.
The OPSB B port connects to an OT in another non-1830 NE.
4. The working OT, protection OT and OPSB card reside in three separate shelves, in the
same NE or different NEs.
In the WebUI, select Connections > Physical Topology (see Procedure 11-1).
Create a link between the OPSB SIG port and the external client signal. This is for all 4
cases.
Select the OSPB SIG port.
Select External and enter the External Address and Direction.
config interface topology 1/31/sig external ext bi
Create a link between the OPSB A or B port and an OT that resides on the same NE
(Cases a, b, c, d).
Select the OSPB A|B port.
Select the OT client port.
Select BiDir.
config interface topology 1/31/a internal 1/13/c1 bi
Create a link between the OPSB A|B port and an OT that resides on a different NE.
(Cases b, c, d)
Select the OSPB A|B port.
Select External and enter the External Address and Direction
config interface topology 1/31/b external ext bi
....................................................................................................................................................................................................................................
1830 PSS
10-37
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Create working and protection cross-connects.

In the WebUI, select Connections > OCH Cross Connects (see Procedure 11-3).
Select Create to display the Create Cross Connect page and provision a cross-connect.
For the working cross-connect, A-End Port = the line port of the OT that is connected
to the OPSB working port, as specified in the protection group. Set Protection
Mode= Working.
For the protection cross-connect, A-End Port = the line port of the OT that is
connected to the OPSB protection port, as specified in the protection group. Set
Protection Mode= Protection.
For both cross-connects, Z-end Port= the LD line port where the working and
protection paths exit the NE, respectively.
Note that for the cross-connects at the Z-end of an end-to-end service, the A-End Port
= the LD line port and the Z-End Port= OT line port.

config xc 1/13/l1 1/2/line 9210 create 9210 bi work
config xc 1/34/l1 1/6/line 9440 create 9440 bi prot
...................................................................................................................................................................................................
Note: Additional provisioning on 11STMM10/11QPA4/11STAR1/11STAR1A OTs.

To ensure less than 50ms traffic interruption time on 11STMM10, 11QPA4, 11STAR1
and 11STAR1A OTs, LOS Propagation on the client port must provisioned as Laser
Off.
In the WebUI equipment tree, select the OT Client port.
On the Port Details tab, set LOS Propagation= Laser Off.
config interface 11stmm10 1/15/c1 oc3 losprop laseroff
config interface 11star1 1/13/c1 oc192 losprop laseroff
config interface 11qpa4 1/12/c1 tenGige losprop laseroff
Note: The working OT and protection OT do not need to be the same OT type. The
following OT combinations are supported:
11QPA4 with 11QPA4

11STAR1 with 11STAR1
11STAR1A with 11STAR1A
11STMM10 with 11STMM10
11QPA4 with 11STAR1
....................................................................................................................................................................................................................................
1830 PSS
10-38
Issue 1 June 2013

....................................................................................................................................................................................................................................
11QPA4 with 11STAR1A

11STAR1 with 11STAR1A
Note: On 11QPA4 line ports, hold-off timer must be provisioned as disabled.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-39
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to configure OLP (Optical Line Protection) protection.
Before you begin

Important! Do not use OLP in combination with other optical protection schemes.
Instructions
Note: These instructions assume packs required to build the main WDM nodal
topology have been inserted into the shelf, and have completed auto-provisioning of
the slot and pack.
...................................................................................................................................................................................................
In the WebUI equipment tree, click the OPSA card to be used to protect a degree and
select OLP mode in the Protection Mode tab.
...................................................................................................................................................................................................
In the WeUI equipment tree select OPSA A or B port. On the Port Details tab, the switch
threshold for the OPSA A/B port should be set by the user independently. The switch
threshold can be manually provisioned by the user for different configurations.
...................................................................................................................................................................................................
The switch threshold should be initially at its default value of -32 dBm. Evaluate if the
threshold needs to be modified, based on the OSC channel power that can be expected to
be received at the OPSA A/B In port by considering the loss from fiber attenuation and
SRS effect that may occur. As general guidelines:
SS-16.20 OSC SFP - use -28 dBm.

SL-16.20 OSC SFP - use -28 dBm.
SUL-1.20 OSC SFP - use -28 dBm for span loss up to 21.5 dB.
SUL-1.20 OSC SFP - use -31.5 dBm for span loss up to 25 dB.
SEU-1.20 OSC SFP - use default of -28 dBm for span loss up to 21.5 dB.
SEU-1.20 OSC SFP - use -31.5 dBm for span loss up to 25 dB.
Note: The span losses are given at 1510 nm.
....................................................................................................................................................................................................................................
1830 PSS
10-40
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
The nodal topology for the ROADM, FOADM or ILA node should be provisioned
through the normal provisioning process for these node types.
Note: Note the power management type of each degree must be Manual.
Note: Note the Wavelength Tracker usage type of each degree must be set to a value
other than the default.
Note: Refer to the Manual Power Management sub-section (included in this topic) for
how to make these settings.
...................................................................................................................................................................................................
To protect a span by OLP, create a topological connection between the OPSA SIG port
and LD port nearest the span (LINE port):
Open the Physical Topology window from the Connections menu.
Click the SIG port of the OPSA pack and the LINE port of the LD pack to be
connected.
Connect the ports together with a bidirectional connection by clicking the BiDir
button.
Click the Close button when done.
...................................................................................................................................................................................................
Set the Admin state of the OPSA A, B and SIG ports to Admin up:
In the WebUIs equipment tree, select the OPSA pack, and the port of interest.
In the Port Details tab, set the Primary State to In Service - Normal.
...................................................................................................................................................................................................
Set the external topology address of each OPSA A/B port used in OLP protection mode:
Open the Physical Topology window from the Connections menu.
Click the A or B port of the OPSA pack to be modified and click the Modify button.
Enter the External Address of the upstream line (A/B port of mate OPSA) in the form
of IP- loopback address and shelf/slot/port number. For example 37.37.37.37 1/35/2.
Use 2 for port A, and 3 for port B.

Click the Close button when done.
Note: The protection group is automatically created for the OLP protection mode
OPSA pack. Port A is assigned the working role, and port B is assigned the protection
role. Normally a user will want to connect port A to port A across the span, and port B
to port B across the protection span.
....................................................................................................................................................................................................................................
1830 PSS
10-41
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: The following settings will be made automatically when the OLP protection
mode OPSA is topologically connected to a node degree, but the user may wish to
review the settings by viewing the appropriate port in the equipment tree.
LD LINE port connecting to OPSA, Port Details: APR Delay Enabled is Yes
Ingress LD SIG port SIG Details: LOS Mode is LOS N.
(If equipped) Egress LD SIG port, SIG Details: LOS Mode is LOS N.
(If equipped) Egress LD LINE port, Port Details: APR Delay Enabled is Yes
(If equipped) WR2-88 SIG port, Port Details: APR Delay Enabled checkbox
ticked.
(If equipped) WR8-88A SIG port, Port Details: APR Delay Enabled checkbox
ticked.
(If equipped) WR8-88AF SIG port, Port Details: APR Delay Enabled checkbox
ticked.
E...................................................................................................................................................................................................
N D O F S T E P S
Additional LD provisioning:
Attention: If there are other degrees in the same optical network that are in the same
optical domain and are not OLP protected, the user must configure the APR hold-off
timer/delay to enabled. CLI commands must be used to make this configuration at the
externally connecting LD port of an un-protected degree.
Refer to the Alcatel-Lucent CLI Command Guide and the command:
Config interface [LDTYPE] [shelf/slot/port] aprholdoff.
Provision the NE degree normally, then use the CLI command to configure the APR
hold-off timer.
OT defect hold off configuration:
Note: Certain OT packs supported for the OLP feature require a defect hold-off timer
to be configured in order to meet 50 ms restoration time.
The following packs require configuration when OTU2 rate is used for the line port:
11STMM10
11DPE12
11DPE12A
11DPE12E
11QPA4
....................................................................................................................................................................................................................................
1830 PSS
10-42
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
To configure the hold-off timer:
In the WebUI equipment tree, select the OT and the line port (e.g. L1).
...................................................................................................................................................................................................
Select the OTU2 Details tab.

...................................................................................................................................................................................................
Select Defect Holdoff Timer Enabled.

...................................................................................................................................................................................................
Click the Submit button.

E...................................................................................................................................................................................................
N D O F S T E P S
LOS propagation configuration:
To ensure 50 ms restoration time, the LOS propagation for client ports must be
provisioned as laser on:
...................................................................................................................................................................................................
In the WebUI equipment tree, select the OT and the client port (e.g. C1).
...................................................................................................................................................................................................
Select the Port Details tab.

...................................................................................................................................................................................................
Provision the LOS Propagation parameter to Laser On.

...................................................................................................................................................................................................
Click the Submit button.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-43
Issue 1 June 2013

....................................................................................................................................................................................................................................
Photonic cross connection configuration:
Note: Optical channel (OCH) cross-connects are made as unprotected connects to the
LD ports nearest to the OPSA pack providing OLP protection. OLP protection
provides essentially facility protection to the OTS entity.
An LD LINE port is valid if it is an unprotected External connected port (for an

un-protected degree).
An LD LINE port is valid if it is a protected Internal connected port (for an OLP

protected degree). The attribute can be checked by viewing the LINE port Port
Details tab. If Internal Port is Valid XC Endpoint is Yes, the port can be used as an
endpoint in an XC
Note: Usually the NMS will create the OCH XCs when services are provisioned,
however the following steps can be used to manually provision individual OCH XCs.
...................................................................................................................................................................................................
To manually create an add/drop cross connect use the following steps:
Open the OCH cross connections list from the Connections menu by selecting from it
OCH Cross Connects.
...................................................................................................................................................................................................
Click the Create button.

...................................................................................................................................................................................................
Provide A-End Port and Z-End Port corresponding to the correct direction. One end
should be the OT port, and the other end should be the LD LINE port.
...................................................................................................................................................................................................
Fill in the rest of the XC details.

...................................................................................................................................................................................................
The Protection Mode should be Unprotected.

...................................................................................................................................................................................................
Click the Apply button.

Note: OT parameters may need to be configured prior to using the line facing port in a
cross-connect.
...................................................................................................................................................................................................
To manually create a through cross connect use the following steps:
Open the OCH cross connections list from the Connections menu by selecting from it
OCH Cross Connects.
....................................................................................................................................................................................................................................
1830 PSS
10-44
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Provide A-End Port and Z-End Port corresponding to the correct direction. One end
should be the LD LINE port for one degree, and the other end should be an LD LINE port
for the other degree.
...................................................................................................................................................................................................
Fill in the rest of the XC details.

...................................................................................................................................................................................................
10
The Protection Mode should be Unprotected.

...................................................................................................................................................................................................
11
Click the Apply button.

E...................................................................................................................................................................................................
N D O F S T E P S
Manual power management:
In nodal configurations where one or more degrees are OLP protected, the optically
interconnected degrees must be Manually power managed. Manual power managed is the
default state of the network element, therefore the user does not need to explicitly
provision degrees to Manual unless re-configuring a previously configured network
element. Refer to the procedures under section Port Power Management for details about
switching the power management type. For an OLP protected line, the power
management interface port remains the LD LINE port closest to the span (the one
connected to the OPSA in OLP mode).
...................................................................................................................................................................................................
Note: The Wavelength Tracker usage type for a degree is set using the port Power
Management tab. The WT usage type must be set prior to operating the system.
In the WebUIs equipment tree, select the LD LINE port closest to the span, and
the Power Management tab.
In the Wavelength Tracker Settings box, set the Wavelength Tracker Decoder
Usage value from the drop down list:
- WTD PPC On /Alarm On if the degree does not use the WTOCM pack for
channel monitoring.
- WTD PPC Off /Alarm Off if the degree is an ILA in a segment that uses
WTOCM packs.
- WTOCM if the degree uses a WTOCM pack for channel monitoring.
Click the Submit button to apply the change.
LD optical amplifier (OA) gain and tilt values can be adjusted through the port interfaces:
....................................................................................................................................................................................................................................
1830 PSS
10-45
Issue 1 June 2013

....................................................................................................................................................................................................................................
In the WebUI's equipment tree, select the LD SIG port and then the SIG Details tab.
...................................................................................................................................................................................................
To modify OA gain, enter the gain value according to the link planning output in the Gain
entry location. The user may also want to set the Minimum Gain and Maximum Gain
limits to remind him of the planned limits according to the network planning exercise, but
this is optional.
...................................................................................................................................................................................................
To modify OA gain tilt, enter the gain tilt value according to the link planning output in
the Target Tilt entry location.
...................................................................................................................................................................................................
Click the Submit button to apply the changes.

Note: The power-per-channel target for the ingress LD SIG port and the LD LINE
port connecting to the OPSA protecting the span (or external for unprotected degrees)
should be set to values determined from the network planning process. These targets
are used to set the WT expected power at these important locations when a new
cross-connect is provisioned. These targets can be set using the following steps:
...................................................................................................................................................................................................
In the WebUI's equipment tree, select the LD SIG port of the ingress LD and then the SIG
Details tab.
...................................................................................................................................................................................................
To modify the per channel target power, change the Per-Channel Output Power value and
click the Submit button.
...................................................................................................................................................................................................
In the WebUI's equipment tree, select the LD LINE port (connecting to External or the
OLP mode OPSA pack), change the Per-Channel Output Power value and click the
Submit button.
E...................................................................................................................................................................................................
N D O F S T E P S
The OLP protection splits the optical signal at the head end of a span, and selects one of
the two spans at the sink end of a span through a switch. The total optical power at the
receiving end of a protected span must be kept in balance between the A and B In ports. A
PWRUNBALANCE condition indicates if the input power is not correctly balanced
(when both paths are lit and received at the sink end).
....................................................................................................................................................................................................................................
1830 PSS
10-46
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Power can be balanced into the far end by adjusting the bridge end OPSA A/B Out
attenuator values through the port interfaces.
Note: These steps assume the bridge end OPSA A port connects to the sink end OPSA
A port.
In the WebUI's equipment tree of the downstream node of the span, select the OPSA A
port and on the Port Details tab note the Total Input Power. Call this Power_Ain.
...................................................................................................................................................................................................
In the WebUI's equipment tree of the downstream node of the span, select the OPSA B
port and on the Port Details tab note the Total Input Power. Call this Power_Bin.
Note: Note the power difference Power_Delta = Power_Ain - Power_Bin.
...................................................................................................................................................................................................
In the WebUI's equipment tree of the upstream node of the span, select the OPSA A port
and on the Port Details tab note the VOA Attenuation. Call this VOA_A
...................................................................................................................................................................................................
In the WebUI's equipment tree of the upstream node of the span, select the OPSA B port
and on the Port Details tab note the VOA Attenuation. Call this VOA_B
...................................................................................................................................................................................................
If Power_Delta is greater than 0:
Calculate Remainder = VOA_B - abs(Power_Delta)

If Remainder < 0, set VOA Attenuation of the upstream B port to 0 dB, and set VOA
Attenuation of the upstream A port to VOA_A plus Remainder dB.
Else, set VOA Attenuation of the upstream B port to Remainder dB.
To apply the attenuation change, change the value in VOA Attenuation and click the
Submit button.
Done.
If Power_Delta is less than 0:
Calculate Remainder = VOA_A - Power_Delta
If Remainder < 0, set VOA Attenuation of the upstream A port to 0 dB, and set VOA
Attenuation of the upstream B port to VOA_B plus Remainder dB.
Else, set VOA Attenuation of the upstream A port to Remainder dB.
To apply the attenuation change, change the value in VOA Attenuation and click the
Submit button.
Done.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-47
Issue 1 June 2013

....................................................................................................................................................................................................................................
Manual power management for ROADM with OLP
For ROADM nodes, the channel Wavelength Tracker expected powers at the input and
output port of the WR2-88/WR8-88A/WR8-88AF need to be set to configure the WSS
(Wavelength Selective Switch). Refer to the Wave Key procedures section for information
about how to set a channel's expected power value at a port.
After making changes to initially provision a new channel, wait a few minutes to allow
the WSS adjustment to occur.
Manual power management for OTs with OLP:
To modify or adjust the transmit power from an OT towards the WDM line, use the
following procedures:
...................................................................................................................................................................................................
In the WebUI equipment tree, select the OT of interest, and expand to view its ports.
...................................................................................................................................................................................................
Select the Line port (e.g. L1) for an OT with WT encoding done directly by the Line port.
...................................................................................................................................................................................................
Select the VA port (e.g. VA1) for an OT with WT encoding done by a fast VOA SFP.
...................................................................................................................................................................................................
Select the Wave Keys tab.

...................................................................................................................................................................................................
To modify the power transmitted to the line, change the Expected Network Output Power
and click the Submit button.
...................................................................................................................................................................................................
Wait for the pack to converge to the new target before making further adjustments. Use
the Refresh button to update the displayed data.
...................................................................................................................................................................................................
Target the per channel power indicated by the WT expected power at the LINE port
connecting to the OLP mode OPSA.
In the WebUI equipment tree, select the LD LINE port of interest, and select the Wave
Keys Out tab.
Use the Refresh button to update the displayed data.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-48
Issue 1 June 2013

....................................................................................................................................................................................................................................
Setting Wavelength Tracker Expected Powers:
In general, Manually power managed degrees require that the user configure the
Wavelength Tracker expected powers for newly provisioned channels. As a maintenance
activity, the user may need to update the expected powers for in-service channels. Refer
to the Wave Key procedures section for information about how to set a channel's expected
power value at a port.
....................................................................................................................................................................................................................................
1830 PSS
10-49
Issue 1 June 2013

Wavelength Tracker
....................................................................................................................................................................................................................................
Wavelength Tracker
Overview
Wavelength Tracker is a technology used to:
encode a unique identifier onto a signal as it enters the network

detect the identifier at various points in the network.
The Wavelength Tracker identifier consists of a pair of numbers, called wave keys, that
are assigned to a wavelength. The wave key pair assigned to a wavelength is unique in the
network. A unique wave key pair is assigned for each individual circuit, or optical trail, in
the network. Thus if there are two or more circuits in a network that use the same
wavelength, each circuit is assigned a unique pair of wave keys. A network can support
multiple occurrences of the same wavelength only if they do not share a common fiber. In
order for a wave key pair to be unique, it can share one of its wave keys with another
optical trail in the network, but not both.
Encoding Wavelength Tracker identifiers
The Wavelength Tracker wave keys are encoded onto the wavelength for an optical trail at
network ingress. The following cards support wave key encoding:
112SCA1
112SCX10
112SNA1
112SNX10
130SCX10
130SCUP
11DPE12(A/E)
11DPM12
11QCUPC
11QPA4
11QPE24
11QPEN4
11STAR1
11STAR1A
11STMM10
11STGE12
43SCA1
43SCGE1
43SCX4
....................................................................................................................................................................................................................................
1830 PSS
10-50
Issue 1 June 2013

Wavelength Tracker
....................................................................................................................................................................................................................................
43SCX4E
43STA1P
43STX4
43STX4P
4DPA4
SVAC
MVAC
MVAC8B
Detecting Wavelength Tracker identifiers
In order to trace a wavelength through the network, its presence at a port must be
detected. The presence or absence of a wavelength at a port is determined by equipping a
port with a Wavelength Tracker detector, which is able to detect and identify the wave
keys encoded onto a wavelength. In addition to detecting the wave keys encoded onto a
wavelength, the Wavelength Tracker detectors can also measure the optical power for
each encoded channel that passes through the port.
Associating the wave keys with an optical trail
The wave keys for an optical trail are assigned when the optical trail (service) is created.
Typically, the wave keys are automatically assigned by the NE software (ROADM rings
only) or the 1354 RM-PhM (ROADM, static, and mixed networks). Manual assignment is
also possible, though not recommended.
The following actions are performed when the optical trail is created:
the wave keys associated with the trail are assigned and are encoded at the service
endpoints (at a transponder or SVAC). A different wave key pair is assigned for each
direction.
the wave keys assigned to the trail are propagated to each Wavelength Tracker detect
point along the service path (as determined from the programmed fiber topology).
Each detect point is then programmed to expect to receive a certain set of wave keys.
Features provided by Wavelength Tracker
Wavelength Tracker makes it possible to check and confirm the path that a wavelength
takes through the network. This capability allows the operator to ensure that the network
connections are correct. Since the Wavelength Tracker detection points are programmed
to expect a certain set of wave keys, wave keys that are unexpectedly received at a
detection point are flagged, and typically indicate a faulty cross-connection. Wavelength
Tracker, with its multiple detection points, immediately flags and pinpoints the location of
these faulty connections, allowing them to be discovered and corrected quickly and easily.
....................................................................................................................................................................................................................................
1830 PSS
10-51
Issue 1 June 2013

Wavelength Tracker
....................................................................................................................................................................................................................................
The ability of the Wavelength Tracker detection points to measure the optical power of
each channel passing through the port allows for:
interactive power monitoring

notification of changes in the power levels for all channels in the network at all
detection points.
When a service is provisioned, the system assigns expected power levels at the detection
points along the path of the service at the Auto power managed lines using data from the
Engineering Planning Tool. If any of the lines along the path of the service are Manual
power managed lines, the user will set the expected power levels at the detection points to
the observed power levels after adjusting the optical power control points.
Adding services to a network
If the new service path through the network crosses lines whose optical power
management type is set to Auto, the service will automatically ramp up to the target
egress power at the launch node. Along the lightpath, control loops will adjust attenuation
settings to bring the services optical power level into alignment with the target points
along the lightpath. Wavelength Tracker power deviation thresholds are set up around
expected powers along the entire lightpath automatically.
For a FOADM system or mixed FOADM-TOADM system containing lines that are auto
power managed and lines that manually power managed, the user must ensure that the
service reaches the correct operational power levels and that Wavelength Tracker
monitoring points are set correctly (see Instructions (p. 10-78)).
Reported information
Using the Wavelength Tracker information, the NE is able to identify all of the
wavelengths that pass through a Wavelength Tracker detect point. For each wavelength,
Wavelength Tracker reports the following information:
the ITU channel being used to transport the wavelength
whether the channel is expected at the port or not (based on the service topology)
the optical power of the wavelength
The information is displayed graphically in the WebUI. The 1354 RM-PhM can display
data for the entire network, for example it can display a graph showing the optical power
for a service at all of the Wavelength Tracker detect points through which the service
passes.
Long haul Wavelength Tracker
The Alcatel-Lucent 1830 PSS supports both "standard" Wavelength Tracker (WT), for
regional applications, and Long-Haul Wavelength Tracker (LH-WT), for long haul
applications. LH-WT is supported by the WTOCM/WTOCMA card, which is connected
to the external facing LD on an optical line.
....................................................................................................................................................................................................................................
1830 PSS
10-52
Issue 1 June 2013

Wavelength Tracker
....................................................................................................................................................................................................................................
The WTOCM/WTOCMA is supported with the following LDs:
A2P2125
A2325A
AHPHG
AHPLG
ALPHG
AM2125A
AM2125B
AM2318A
For Bidirectional LDs:
The WTOCM/WTOCMA is connected to the external facing ingress LD on an optical

line. Each WTOCM/WTOCMA can provide LH-WT for any 2 LDs
For the single-node anydirection configuration, a WTOCM/WTOCMA is also
connnected to the LDs within the add/drop block.
The connectivity between a WTOCM/WTOCMA IN port and a LD MON RX or TX
port is specified as an attribute on the WTOCM/WTOCMA port; topological links are
not created for this connection.
The MON TX and MON RX on an LD must connect to the same
WTOCM/WTOCMA.
For Unidirectional LDs:
The WTOCM/WTOCMA is connected to the external facing ingress LD and egress

LD on an optical line. Each WTOCM/WTOCMA can provide LH-WT for any 4
unidirectional LDs, or 2 unidirectional LDs and one bidirectional LD
For the single-node anydirection configuration, a WTOCM/WTOCMA is also
connnected to the LDs within the add/drop block.
The connectivity between a WTOCM/WTOCMA IN port and a LD MON port is

specified as an attribute on the WTOCM/WTOCMA port; topological links are not
created for this connection.
The MON ports for each LD on an optical line must connect to the same
WTOCM/WTOCMA.
The 1830 PSS supports both keyed and unkeyed optical channels. For keyed optical
channels, Wavelength Tracker functionality is enabled. For most unkeyed optical channels
(also referred to as unmanaged), Wavelength Tracker functionality is not enabled encoders/fVOAs on OTs are not populated or not enabled for integrated eVOA and
decoder points are not used in maintenance/monitoring functions. Ther following applies:
The NE supports both keyed and unkeyed optical channels.
The NE allows mixing keyed and unkeyed optical channels on the same optical line.
....................................................................................................................................................................................................................................
1830 PSS
10-53
Issue 1 June 2013

Wavelength Tracker
....................................................................................................................................................................................................................................
An optical channel trail must be made up of all unkeyed OCH cross-connects or all
keyed OCH cross-connects for its entire length.
An unkeyed optical channel is not supported on an auto-power managed line if the
channel monitoring type is embedded WT (i.e. standard WT).
An unkeyed optical channel is supported on an auto-power managed line for the
following node types if the channel monitoring type is WTOCM/WTOCMA.
ILA
FOADM
TOADM
Note: The NE will not preclude support for the following node types: ROADM,
ROADM with Anydirection Add/Drop (Single Node, i.e. Config D), , but it is not
required by EPT.
Each line within an optical node, and each endpoint on an OMS span, must be configured
with the same WT capability, either long haul (with WTOCM/WTOCMA), or standard
(without WTOCM/WTOCMA).
Note: Creation of unkeyed cross connection is allowed when a CWR pack is involved
in the physical topology connection on a manual power management configuration.
The WTOCM/WTOCMA is used on the following node types for long haul
configurations:
TOADM
ROADM
Anydirection
FOADM end terminal with DGE in path
WTOCM/WTOCMA is optional for the following node types:
2D+FOADM
FOADM end terminal, with no DGE in path
ILA
....................................................................................................................................................................................................................................
1830 PSS
10-54
Issue 1 June 2013

Procedure 10-10: Provision wave keys on an encoder port to

support dangling OT procedure
....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision wave keys on an encoder port to support
dangling OT procedure.
Before you begin

Instructions for L1 port

...................................................................................................................................................................................................
In the WebUI, from the equipment tree select the L1 port for the OT.
...................................................................................................................................................................................................

Result: The Wave Key Encoder screen is displayed.
...................................................................................................................................................................................................
Set values for Wave Key 1 and Wave Key 2.

Note: Wave Keys can only be modified if Connection Type = External and Frequency
has been set (i.e. does not equal None). Connection Type and Frequency are displayed
on the Details page.
Note: Cannot use dangling OTs connecting to the add/drop block of an Anydirection
Single-Node node.
E...................................................................................................................................................................................................
N D O F S T E P S
Instructions for VA port

...................................................................................................................................................................................................
In the WebUI, from the equipment tree select the VA port for the OT.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
10-55
Issue 1 June 2013


....................................................................................................................................................................................................................................
Result: The Wave Key Encoder screen is displayed.

...................................................................................................................................................................................................
Set values for Wave Key 1 and Wave Key 2.

Wave Keys can be modified if the following conditions are met:
Connection Type (To) = External

Connection Type (From) = Internal
Connected From = a line port on the same card.
The Frequency on the connected Line port != 0
Other validations:
Wave Key 1 and Wave Key 2 must both equal 0 or both not equal 0 at the time the
user submits the request
If Wave Key 1 and/or Wave Key 2 are modified, both attributes will be sent to the NE
(i.e., even if only one attribute is modified, both are sent to the NE).
The WebUI will display a pick list of valid wave keys per frequency. In addition, 0 is a
valid wave key value for each frequency
Note: Connection Type and Frequency are displayed on the Details page.
Note: If the conditions for modification are not met, then Wave Key 1 and Wave Key
2 are displayed as view-only.
Note: For OTs that support the 11 additional frequency values outside of the 88
channels supported by the 1830, only Wave Key 1 and Wave Key 2 = 0 are allowed.
Note: Cannot use dangling OTs connecting to the add/drop block of an Anydirection
Single-Node node.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-56
Issue 1 June 2013

Wave Key Encoder
....................................................................................................................................................................................................................................
Wave Key Encoder

Attribute
Value/Format
Additional Info
Wave Key 1
{0-4096}
Programmed wave key value.
Wave Key 2
{0-4096}
Programmed wave key value.
Wave Key Transmit Status
Up
Indicates whether or not wave

keys are transmitted.
Down
Measured Network Output
Power (dBm)
(as displayed)
The measured total egress

power of the optical signal.
Expected Network Output

Power (dBm)
112SCA1, 112SCX10,
112SNA1, 112SNX10,
130SCUP, 130SCX10,
43SCA1, 43SCGE1, 43SCX4,
43SCX4E Line ports: {-17 to
+4}
The expected total egress

power of the optical signal.
11DPE12, 11DPE12A,
11DPE12E, 11QCUPC,
11QPA4, 11QPE24,
11QPEN4, 4DPA4, 4QPA8VA
ports: {-20 to -5.5}
11DPM12 VA ports: {-15 to
-5.5}
43STA1P, 43STX4 and
43STX4P line ports: {-20 to
-0.5}
{-20 to +4} for all other ports
....................................................................................................................................................................................................................................
1830 PSS
10-57
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to set expected network output power.

Before you begin

Instructions
Note: These operations can only be done if the port is manually managed. If the port
is auto managed, it belongs to an auto managed cross connect, and the keys can only
be modified as attributes of the cross connect. Power cannot be modified.
...................................................................................................................................................................................................
In the WebUI equipment tree, select the appropriate port, select the Wave Keys tab, and
set Expected Network Output Power.
...................................................................................................................................................................................................
Set expected output power and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-58
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view wave keys (decoder ports)

Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI equipment tree select the appropriate port, select Wave Keys In or Wave
Keys Out tab.
...................................................................................................................................................................................................
The Wave Keys Decoder In/Out screen is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-59
Issue 1 June 2013

Wave Key Decoder
....................................................................................................................................................................................................................................
Wave Key Decoder

Attribute
Value/Format
Additional Info
Frequency
{9170~9605}
Specific channel on the port.
Expected Wave Key 1
{0-4096}
One of many possible wave

keys expected to be riding on
a particular channel.A value
of zero indicates no wave key
expected.
Expected Wave Key 2
{0-4096}

a particular channel. A value
expected.
Expected Power (dBm)
{-40 to 11}
The expected power

associated with the received
wave keys.
Off
Cannot be modified for CWR

OMD IN and CWR CLS IN
ports.
Measured Power (dBm)
The measured power

wave keys.
Expected Power Deviation

(dB)
{0-10}
The threshold for declaring a

power out of range alarm. If
the Measured Power is
outside Expected Power +/Deviation, an alarm is raised.
Expected Power Tolerance

(dB)
{0-5}
The Expected Power

Tolerance is the threshold for
clearing a power out-of-range
alarm (deviation - tolerance).
If the Measured Power is
inside Expected Power +/(Deviation - Tolerance), the
alarm is cleared.
....................................................................................................................................................................................................................................
1830 PSS
10-60
Issue 1 June 2013

Wave Key Decoder
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Channel Status
Up
Status of the channel.
Down
Testing
Unassigned
Wave Keys Present
Yes
No
Indicates that the two

expected wave keys are
present on the channel.
Clear Wave Keys
Request to set the expected

wave keys to 0 for a selected
channel.
Set Power
Request to set the expected

power to a specified value or
to Off for a selected
channel.
....................................................................................................................................................................................................................................
1830 PSS
10-61
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to clear wave keys.

Before you begin

Instructions
Note: Wave keys can only be cleared for manually power managed ports.
...................................................................................................................................................................................................
In the WebUI equipment tree, select the appropriate port and click on the Wave Keys In or
Wave Keys Out tab.
Result: The Wave Keys Decoder In/Out screen is displayed.
...................................................................................................................................................................................................
Select the record and click Clear Wave Keys.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-62
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to set power.

Before you begin

Instructions
Note: Expected Power can only be set for manually power managed ports.
...................................................................................................................................................................................................
Wave Keys Out tab.
...................................................................................................................................................................................................
Select the record and click Set Power.

Result: The Set Power screen is displayed.
...................................................................................................................................................................................................
Set expected power attributes and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-63
Issue 1 June 2013

Set Power
....................................................................................................................................................................................................................................
Set Power
Attribute
Value/Format
Power Value Set
Additional Info
Select this to set one or more
Expected Power attributes. If
not selected, Expected Power
will be set to Off.
{-40 to 11}
The expected power

wave keys.
Expected Power Deviation

(dB)
{0-10}

Expected Power Tolerance

(dB)
{0-5}
The Expected Power

alarm is cleared.
....................................................................................................................................................................................................................................
1830 PSS
10-64
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view channel power summary.

Before you begin

Instructions
...................................................................................................................................................................................................
Wave Keys Out tab.
...................................................................................................................................................................................................
Click Power Summary.

Result: A graphical Power Summary is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-65
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
{-99 to 11}, where -99 = Off
The expected power

wave keys at a specific port.
The measured power

Delta (dB)
Difference between Measured

Power and Expected Power
Expected Deviation (dB)
{0-10}

power out-of-range alarm. If
....................................................................................................................................................................................................................................
1830 PSS
10-66
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view unexpected wave keys.

Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI equipment tree, select the appropriate port and click on the Unexpected
Wave Keys tab.
Note: The following ports support unexpected wave key data when WTD is enabled.
A2325A LINE, SIG, DCM port
ALPHG LINE, SIG, DCM port

AHPHG LINE, SIG, DCM port
AHPLG LINE, SIG, DCM port
AM2125A/AM2125B/AM2318A LINEIN, LINEOUT
CWR8 SIG, THRU port

CWR-88 SIG, THRU port
MESH4 SIGIN
OPSA SIG, A, B port
WR2-88 SIG
WR8-88A/WR8-88AF SIG, THRU
WTOCM IN{1-4} port
WTOCMA IN{1-4} port
Result: The Unexpected Wave Keys screen is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-67
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Direction
In
Out
Indicates whether the signal is

ingress or egress.
Frequency
{9170~9605}
Wave Key
{0-4096}
Unexpected wave key value
The measured power

wave key.
....................................................................................................................................................................................................................................
1830 PSS
10-68
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view wave key data at NE level.

Before you begin

Instructions
The WebUI displays wave key data for wave keys in use on the NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Wavelength Tracker > Port Wave Keys.
...................................................................................................................................................................................................
On the ensuing Wave Keys screen, select Port, Direction, Frequency, or All and click
Retrieve.
Result: The selected wave key data is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-69
Issue 1 June 2013

Wave Keys
....................................................................................................................................................................................................................................
Wave Keys
Attribute
Value/Format
Additional Info
Port
<shelf/slot/port>
Port identifier.
Frequency
{9170~9605}
Direction
In
Direction of the signal on the

port.
Out
Expected WK 1
{0-4096}

expected.
Expected WK 2
{0-4096}

expected.
{-99 to 11}, where -99 = Off
The expected power

wave keys.
The measured power

wave keys.
Exp. Power Deviation (dB)
{0-10}

outside Expected Power +/Deviation, an alarm is raised
Exp. Power Tolerance (dB)
{0-5}
The Expected Power

alarm is cleared.
....................................................................................................................................................................................................................................
1830 PSS
10-70
Issue 1 June 2013

Wave Keys
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Channel Status
Up
Status of the channel.
Down
Testing
Unassigned
WK Present
Yes
No
Indicates that the two

expected wave keys are
present on the channel.
....................................................................................................................................................................................................................................
1830 PSS
10-71
Issue 1 June 2013

Procedure 10-18: View unexpected/missing wave keys at NE

level
....................................................................................................................................................................................................................................
Procedure 10-18: View unexpected/missing wave keys at NE

level
When to use
Use the following procedure to view unexpected/missing wave keys at NE level.

Before you begin

Instructions
The WebUI displays all unexpected wave keys detected on the NE, or all missing wave
keys on the NE.
...................................................................................................................................................................................................
In the WebUI, select Reports > Wavelength Tracker > {Unexpected Wave Keys/Missing
Wave Keys}.
Result: The respective Wave Key data is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-72
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Port
<shelf/slot/port>
Port where unexpected wave

key is detected.
Frequency
{9170~9605}
Direction
In
Out

ingress or egress.
{0-4096}
Unexpected wave key value.
Wave Key
The measured power

wave key.
....................................................................................................................................................................................................................................
1830 PSS
10-73
Issue 1 June 2013

Missing Wave Keys
....................................................................................................................................................................................................................................
Missing Wave Keys

Attribute
Value/Format
Additional Info
Port
<shelf/slot/port>
Port where missing wave key

is detected.
Frequency
{9170~9605}
Direction
In

ingress or egress.
Out
Expected WK 1
{0-4096}
The wave key expected to be

riding on a particular channel.
Expected WK 2
{0-4096}
The wave key expected to be

riding on a particular channel.
....................................................................................................................................................................................................................................
1830 PSS
10-74
Issue 1 June 2013

Procedure 10-19: Provision optical line's monitoring (WT

mode or WTOCM mode)
....................................................................................................................................................................................................................................
Procedure 10-19: Provision optical line's monitoring (WT mode

or WTOCM mode)
When to use
Use the following procedure to provision optical line's monitoring (WT mode or
WTOCM mode)
Before you begin

Instructions
...................................................................................................................................................................................................
After WTOCM pack is installed and provisioned, an association to the line side port that
it monitors must be provisioned.
Note: If the node is commissioned via the commissioning process, this association is
provisioned automatically for the user.
...................................................................................................................................................................................................
After association of a WTOCM pack with a line side port, a setting must be made for the
line operation mode. This setting is made at the external Line port of the ingress LD of
the line.
...................................................................................................................................................................................................
Regardless of WTOCM usage or not, a line setting needs to be made at the external Line
port now for all optical lines that defines the WT power display and OCh alarms
functionality.
Note: If the NE is provisioned by the commissioning process, these settings are made
automatically by the 1354 PhM / CPB tools which provision the EPT commissioning
file(s).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-75
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Power Management
Power Management Type
Automatic
Manual
Service Launch Attenuation

Offset (dB)
{0-10}
Indicates the type of power

management for this port.
EPT parameter used by the
NE to facilitate
commissioning and in-service
adjustments.
This field is only applicable
when Power Management
Type is set to Automatic.
Span Loss Tilt
{0-3.00}
Auto Gain Adjustment

Enabled
(checkbox)
Enables or disables the

automatic gain adjustment
routine.
Auto Tilt Adjustment Enabled
(checkbox)

automatic tilt adjustment
routine.
Auto Tilt Maintenance Mode

Enabled
(checkbox)

maintenance tilt adjustment
routine. This field can only be
set if the Auto Tilt Adjustment
Enabled field is checked.
Commissioned Status
In Progress
Indicates status of power

commissioning for this optical
line.
Completed
Gain Adjustment Settings
Time Offset Past Hour
{00:00:00.0 - 23:59:59.9}
translated to/from
{0-86399.9}
Base period past the hour for

scheduled gain adjustments.
NE to facilitate
gain adjustments
....................................................................................................................................................................................................................................
1830 PSS
10-76
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Time Period Between

Adjustments
{00:00:00.0 - 23:59:59.9}
translated to/from
{0-86399.9}
Length of time between

{00:00.0 - 59:59.9}
Length of time allocated for

Allocated Adjustment Time

NE to facilitate
gain adjustments.

NE to facilitate
gain adjustments.
Wavelength Tracker Settings
Wavelength Tracker Decoder
Usage
WTD PPC On / Alarm On

WTD PPC On /Alarm Off
WTD PPC Off / Alarm Off
Indicates whether this optical

line uses classic wavelength
tracker decoder or a WTOCM
card.
WTD Inferred
WTOCM
....................................................................................................................................................................................................................................
1830 PSS
10-77
Issue 1 June 2013


FOADM-TOADM system
....................................................................................................................................................................................................................................

FOADM-TOADM system
When to use
Use the following procedure to add a service to a FOADM system or mixed

FOADM-TOADM system.
Before you begin

Instructions
A FOADM system or mixed FOADM-TOADM system contains lines that are Auto
power managed and lines that Manually power managed.
...................................................................................................................................................................................................
View the power management type by selecting the Power Management tab of the Line
port of the ingress LD of a line.
Note: If the lightpath of the service traverses only lines that are Auto power managed,
then no further steps are required by the user. If the lightpath traverses a mix or Auto
power managed lines and Manually power managed lines, the following steps must be
followed:
...................................................................................................................................................................................................
Starting at the node where the service originates:
If the egress line of the origination point of the service is Automatically optical power
managed wait for one minute for the optical power to ramp up.
If the egress line of the origination point of the service is Manually optical power
managed adjust the setpoint (target output power) of the OT or SVAC Line port to
increase the optical power. If the service is an OT protected by OPSA, change the
OPSA VOA attenuation setting instead of the OT setpoint. Iteratively adjust the power
by steps of 5 dB or less, wait for thirty seconds to observe the result and check the
WT measured power at the egress point onto the line (the reverse direction ingress LD
Line Out port). The target output power range at the egress point is the WT expected
power +/- 0.5 dB.
....................................................................................................................................................................................................................................
1830 PSS
10-78
Issue 1 June 2013


FOADM-TOADM system
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Set the Expected Network Output Power field of the Wave Keys tab for the L1 port of
the OT or SVAC or for OPSA, set the voa attenuation field of the Switch tab for the A or
B port of the OPSA.
Set the VA1 or VA2 port setpoint if the OT is a 4DPA4, 11QPA4, and 11DPE12(E) using
a fast eVOA pluggable module in the VA1 (or VA2) port. If OT does not have a VA
(variable attenuator) port, set the L1 port target output power. If the OT does have a VA
port, set the VA port target output power. If the OT is protected by an OPSA pack, set the
OPSA A or B port VOA attenuation setting to adjust the optical power.
Note: If the optical output power of the OT or SVAC Line, or OPSA A/B port fails to
increase when the setpoint is increased use the Alcatel-Lucent 1830 Photonic Service
Switch (PSS) Release 6.0 Maintenance and Trouble-Clearing Guide to clear the
problem.
If the WT optical output power at the egress point onto the line cannot reach within
0.5 dB of the WT expected power use the Alcatel-Lucent 1830 Photonic Service
Switch (PSS) Release 6.0 Maintenance and Trouble-Clearing Guide to clear the
problem.
Changes to the power levels of existing services are expected and these services may
fall outside the range of 0.5 dB from the target power at line out. The already existing
services should remain within their WT deviation thresholds at line out.
...................................................................................................................................................................................................
If the egress line for this network element is manually power managed, set the WT
expected powers at the WT detect points through the node.
...................................................................................................................................................................................................
Note: Only follow this step if there are more than 2 NEs including the add and drop
NEs along the lightpath.
Locate the next ingress line of the lightpath.
If the ingress line of this through path is Auto optical power managed, then proceed to
the egress line.
If the ingress line of this through path is Manually optical power managed, review
whether the ingress LD gain needs to be set. View the ingress LD Sig Out target
power per channel. Select the Sig Details tab to view the Per-Channel Output Power
field. Note the value of the per channel target power.
...................................................................................................................................................................................................
View the current WT power(s) of any service(s) present at the Sig port Out. Select the
Wave Keys Out tab for the Sig port of the ingress LD to view the Wave Key power for
each channel.
....................................................................................................................................................................................................................................
1830 PSS
10-79
Issue 1 June 2013


FOADM-TOADM system
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Change the gain of the ingress LD until the WT power(s) are centered around the target
power. For example, if there is one wavelength present and its optical power is -2 dBm
and the target is 0 dBm, increase the gain setting of the LD by 2 dB. Set the value of the
Gain field of the Sig tab.
...................................................................................................................................................................................................
After each gain adjustment wait for ten seconds to ensure the reported WT power(s) fully
reflect the gain change. If this is a manually optical power managed TOADM line set the
CWR8 Sig In expected power to the measured power after completing the ingress LD gain
change.
...................................................................................................................................................................................................
Select the Wave Keys Out tab for the Sig port of the CWR8 to set the Wave Key power
for the channel.
...................................................................................................................................................................................................
10
If the egress line of this through path is Automatically optical power managed, move on
to the next line at the next NE.
If the egress line of this through path is Manually optical power managed, view the egress
point (reverse direction ingress LD Line Out port) target output power per channel. Select
the Port Details tab to view the Per-Channel Output Power field.
...................................................................................................................................................................................................
11
View the current WT power of the new service at the Line port Out. Select the Wave Keys
Out tab for the Line port to view the Wave Key power for the channel.
...................................................................................................................................................................................................
12
Calculate the difference between the WT measured power and the target power. If this is a
FOADM line, instruct the field personnel to change the attenuating pad on the path
between the ingress line and this egress line by this same amount only if the channel is
directed through the NE using the channel ports. For example, if the WT power is 2 dB
less than the target power, the attenuating pad value should be decreased by 2 dB. If the
WT power is 2 dB greater than the target power, the attenuating pad value should be
increased by 2 dB. If the WT power is within 1.0 dB of the target power, consider the
error acceptable and make no further changes. For a channel directed through the NE
using the express ports, the user should not need to change the pad value already in place.
Note that changes to the power levels of existing services are expected and these services
may fall outside the range of 1.0 dB from the target power at line out. The already
existing services should remain within their WT deviation thresholds at line out.
....................................................................................................................................................................................................................................
1830 PSS
10-80
Issue 1 June 2013


FOADM-TOADM system
....................................................................................................................................................................................................................................
If this is a TOADM line, change the expected power at the Thru Out port of the CWR8
until the WT power is within 0.5 dB of the target power. Wait at least one minute before
adjusting the power set point again to allow the control loop adjust. (Note that in the case
of a TOADM line, initially the measured WT will be very low or not measurable until the
expected power of the CWR8 Thru Out port has been set for the first time).
If the NE egress line is a Manually managed TOADM line change the expected power at
the Thru Out or CLS Out port of the CWR8 until the WT power is within 0.5 dB of the
target power. (In the case of a TOADM line, initially the measured WT will be very low
or not measurable until the expected power of the CWR8 Thru Out port has been set for
the first time). Follow an iterative process until the power observed at the egress Line Out
is in range. The controller converges slowly, therefore allow up to 2 minutes after making
a change for the power to converge to a new setpoint.
...................................................................................................................................................................................................
13
Select the Wave Keys Out tab for the Thru port to set the Wave Key power for the
channel.
...................................................................................................................................................................................................
14
If the ingress or egress line for this through network element is manually power managed,
set the WT expected powers at the WT detect points through the node.
...................................................................................................................................................................................................
15
Repeat this process for every through network element along the services lightpath.
...................................................................................................................................................................................................
16
At the last NE in the services path:

If the ingress line of this through path is Manually optical power managed, review
whether the ingress LD gain needs to be set. View the ingress LD Sig Out target power
per channel. Select the Sig Details tab to view the Per-Channel Output Power field. Note
the value of the per channel target power.
...................................................................................................................................................................................................
17
View the current WT power(s) of any service(s) present at the Sig port Out. Select the
Wave Keys Out tab for the Sig port of the ingress LD to view the Wave Key power for
each channel.
...................................................................................................................................................................................................
18
Change the gain of the ingress LD until the WT power(s) are centered around the target
power. For example, if there is one wavelength present and its optical power is -2 dBm
and the target is 0 dBm, increase the gain setting of the LD by 2 dB. Set the value of the
Gain field of the Sig tab.
....................................................................................................................................................................................................................................
1830 PSS
10-81
Issue 1 June 2013


FOADM-TOADM system
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
19
After each gain adjustment, wait for ten seconds to ensure the reported WT power(s) fully
reflect the gain change. If this is a manually optical power managed TOADM line, set the
CWR8 Sig In expected power to the measured power after completing the ingress LD
gain change.
...................................................................................................................................................................................................
20
Select the Wave Keys Out tab for the Sig port of the CWR8 to set the Wave Key power
for the channel.
...................................................................................................................................................................................................
21
If the ingress line of this drop path is a Manually optical power managed TOADM line
and the service uses the CLS port, set the WT expected power at the drop port to the
default drop target power. View the drop target power. Select the CLS port details of the
CWR8 to view the drop target. Set the WT expected power to the same value.
...................................................................................................................................................................................................
22
Select the Wave Keys Out tab for the CLS port of the CWR8 to set the Wave Key power
for the channel. Wait for at least two minutes for the power level to reach the target value.
...................................................................................................................................................................................................
23
If the ingress line for this drop network element is manually power managed, set the WT
expected powers at the WT detect points through the node. If the service is an OPSA
protected service the A or B port WT expected power value must be set.
...................................................................................................................................................................................................
24
Repeat the procedure steps above for the other direction of the service for a bi-directional
service.
...................................................................................................................................................................................................
25
Repeat the procedure steps above for the protection service, if applicable.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-82
Issue 1 June 2013

Procedure 10-21: Add an Anydirection Add/Drop block to

ROADM
....................................................................................................................................................................................................................................

ROADM
When to use
This describes the procedure for adding an Add/Drop block to an existing ROADM to
create a node that supports the Anydirection/Anycolor configuration. The initial
configuration is a multi-degree ROADM composed of inter-connected WR8-88As. The
Anydirection configuration supports up to 8 degrees with no local add/drop on the
WR8-88As, or up to 7 degrees with local add/drop.
Before you begin

Instructions
...................................................................................................................................................................................................
Provision a MESH4 card for each WR8-88A in a Connection block (optional).

With the Anydirection configuration, if local Add/Drop is configured on the Connection
block, the configuration supports up to N+M=5 (where N=degree of the Connection block
and M=# of Add/Drop blocks) without the need for an additional MESH4 card. If a user
wants to maintain the option for a hitless increase of Anydirection connectivity beyond
N+M=5, then the MESH4 card must be added when the 5th Add/Drop block or 5th
degree is added.
If starting with a 4-degree ROADM (N=4), then a MESH4 card is needed when an
anydirection, colorless Add/Drop block (M=1) is added.
...................................................................................................................................................................................................
Provision each of the cards in the Add/Drop block.

An Add/Drop block consists of the following cards:
1 MESH4 card. If the initial configuration is >= 5 degree, then a MESH4 card is
needed with the top WR8-88A.
1 WR8-88A (top)
1 LD for Drop direction (A2325A)
1 LD for Add direction (AHPLG or AM2318A)

1 WR8-88A (middle)
1 MESH4 for the middle WR8-88A, if >5 CWR8-88s
....................................................................................................................................................................................................................................
1830 PSS
10-83
Issue 1 June 2013


ROADM
....................................................................................................................................................................................................................................
Up to 8 CWR8-88s
Up to 8 OTs per CWR8-88 (a total of 64 OTs per A/D block can be supported)
Optional: WTOCMs for the LDs.
...................................................................................................................................................................................................
Provision Level parameter for each WR card in the Add/Drop block. In WebUI:
WR8-88A card > WR tab or CWR8-88 Card > CWR tab.
Top WR8-88A = Level 1

Middle WR8-88A = Level 2
CWR8-88s = Level 3
When the top WR8-88A is configured as Level 1, this will automatically set the power
management type on WR8-88A SIG port to Auto, which is the required setting for an
Add/Drop block.
WR8-88As in the connection block will have Level = 0. This is the default value for the
WR cards, so should not need to be provisioned.
Note: The Level parameter must be provisioned before topological links are
provisioned.
...................................................................................................................................................................................................
Provision topological links between cards.

The topological links are provisioned between the add/drop block cards and between the
add/drop block and each of the WR8-88As in the connection block.
The Level 1 WR8-88A is connected to/from each of the Connection block WR8-88As
(directly or through a MESH4 card).
The Level 2 WR8-88A is connected to/from each of the CWR8-88s (directly or

through a MESH4 card).
An Add/Drop block is not connected to any other Add/Drop block.
...................................................................................................................................................................................................
Provision WTD Usage parameter for the add and drop directions. WTD Usage
(Wavelength Tracker Decoder Usage) is provisioned on the Level 1 WR8-88A in the
Add/Drop block.
Add direction:
In WebUI: WR8-88A SIG port > Power Management tab.
If WTD is used in the Add direction, this will normally be provisioned with WTD
Usage = wtdonon (-per-channel measurements = on, Channel alarms = on)
If WTOCM is used in the Add direction, this will normally be provisioned with WTD
Usage = wtocmad
Drop direction:
....................................................................................................................................................................................................................................
1830 PSS
10-84
Issue 1 June 2013


ROADM
....................................................................................................................................................................................................................................
In WebUI: WR8-88A SIG port ? Power Management tab.
If WTD is used in the Drop direction, this will normally be provisioned with WTD
Usage = wtdonon (Power-per-channel measurements = on, Channel alarms = on)
If WTOCM is used in the Drop direction, this will normally be provisioned with
WTD Usage = wtocm
...................................................................................................................................................................................................
Run add adjustment and drop adjustment for the Add/Drop block. Add adjustment and
drop adjustment are run on the Level 1 WR8-88A card.
Add adjustment:
In WebUI: WR8-88A card > Power Adjustment tab.
Drop adjustment
In WebUI: WR8-88A card > Power Adjustment tab.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-85
Issue 1 June 2013

Power settings
....................................................................................................................................................................................................................................
Power settings
Rebalancing in-service optical power levels
In-service rebalancing of the optical powers is supported on all of the NEs in a network.
A network rebalance may be required if the network is re-engineered, or it may be
performed as a preventive maintenance exercise.
If the network has been re-engineered, the user can reset targets and re-adjust power
levels around the network. When the rebalancing is performed as a preventive
maintenance exercise, the current power targets are used to re-adjust power levels
Only NE lines that are auto power managed can be power balanced using the Ingress
Adjustment or Egress Adjustment functions found in the Power Management tab (see
Instructions (p. 10-89)).
Lines that are manually power managed must be manually adjusted by the user and would
include tasks such as modifying the OT or SVAC target output power, OPSA VOA
attenuation, setting the LD gain, and re-setting WT expected power levels (if necessary).
Target Power Offset
The WebUI supports viewing and setting target power offset for the following ports:
A2325A, AHPHG, AHPLG, ALPHG, and AM2325B LINE ports

AM2125A, AM2125B, AM2318A and RA2P LINEIN ports (Ingress only)
AM2125A, AM2125B and AM2318A LINEOUT ports (Egress only)
Whether a particular card supports setting target power offset is dependent on its current
topology. The WebUI determines whether a given port supports egress, ingress, both, or
neither by the following:
For A2325A, AHPHG, AHPLG, ALPHG and AM2325B LINE ports:

If the LINE port Opposite Direction Port is set to itself, then both Ingress and
Egress are supported.
If the LINE port Opposite Direction Port is set to another port, then only Egress is
supported.
If the LINE port Opposite Direction Port is unassigned, then neither Ingress nor
Egress are supported.
For AM2125A, AM2125B, AM2318A and RA2P LINEIN ports:
If the LINEIN port Opposite Direction Port is set, then Ingress is supported.
If the LINEIN port Opposite Direction Port is unassigned, then Ingress is not
supported.
....................................................................................................................................................................................................................................
1830 PSS
10-86
Issue 1 June 2013

Power settings
....................................................................................................................................................................................................................................
For AM2125A, AM2125B and AM2318A LINEOUT ports:

If the LINEOUT Opposite Direction Port is set, then Egress is supported.
If the LINEOUT Opposite Direction Port is unassigned, then Egress is not
supported.
The WebUI supports modify and view of target power offset by technology type (see
Technology types (p. 10-87)) for each direction supported (ingress and/or egress).
Power Offset cannot be modified for technology types where OTU Bit Rate and/or
Encoding = {9001 10000}.
Per-channel target power offset
The WebUI supports modify and view of ingress and egress target power attributes per
optical channel. This is supported for the ingress and egress power adjust points. The
following applies:
A card supports modify/view of the ingress target power attributes if the card supports
ingress power adjustment.
Likewise, a card supports modify/view of the egress target power attributes if the card
supports egress power adjustment.
The WebUI does not allow modify/view of the target power attributes if the card is not
present in the shelf (i.e. the card is pre-provisioned). The WebUI displays a table of target
power data per frequency for each direction supported (ingress and/or egress).
Technology types
The WebUI supports create, modify and view of system-wide technology types. The
index to a technology type is the Bit Rate Key and Encoding Key as specified in the
following table.
Table 10-1
Attribute
Technology Type index table

MIB Attribute
Value/Format
Create
Modify
View
Bit Rate Key
tnPowerMgmtBitRate
{1-10000} for
view
{1001-9000} for
create
Bit Rate
Description
tnPowerMgmtTechnologyTypesBitRateText
<0-50 chars>
Encoding Key
tnPowerMgmtEncoding
{1-10000} for
view
{1001-9000} for
create
....................................................................................................................................................................................................................................
1830 PSS
10-87
Issue 1 June 2013

Power settings
....................................................................................................................................................................................................................................
Table 10-1
Attribute
Technology Type index table
(continued)
MIB Attribute
Value/Format
Create
Modify
View
Encoding
Description
tnPowerMgmtTechnologyTypesEncodingText
<0-50 chars>
WTOCM
Calibration
(dB)
tnPowerMgmtTechnologyTypesWtocmCalib
{-5.00 to 5.00}
Default = 0
WTOCMA
Calibration
(dB)
tnPowerMgmtTechnologyTypesWtocmaCalib
{-5.00 to 5.00}
Default = 0
OSNR
Calibration
(dB)
nPowerMgmtTechnologyTypesOsnrCalib
{-5.00 to 5.00}
Default = 0
Note: The WebUI will not allow creation of a technology type that already exists. The
WebUI will not allow modify of OTU Bit Rate Description and Encoding Description
for reserved enum values (1-1000 and 9001-10000). The WebUI will not allow
modify of WTOCM Calibration for reserved enum values (9001-10000).
The WebUI supports deletion of a technology type if it meets the following conditions:
It is not a reserved type. Reserved types have OTU Bit Rate or Encoding = {1-1000,
9001-10000}.
It is not associated with a cross-connect. OTU Bit Rate/Encoding do not match the
AZ/ZA user-settable OTU Bit Rate/Encoding nor the AZ/ZA received OTU Bit
Rate/Encoding on a cross-connect.
....................................................................................................................................................................................................................................
1830 PSS
10-88
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision power management.

Before you begin

Instructions
...................................................................................................................................................................................................
Select the appropriate port from the equipment tree and click the Power Management
tab.
Result: The Port Power Management screen is displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-89
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Power Management
Power Management Type
Automatic
Manual

Offset (dB)
{0-10}
Indicates the type of power

management for this port.
NE to facilitate
adjustments.
when Power Management
Type is set to Automatic.
Span Loss Tilt
{0-3.00}

Enabled
(checkbox)

routine.
(checkbox)

routine.
Auto Tilt Maintenance Mode

Enabled
(checkbox)

maintenance tilt adjustment
routine. This field can only be
set if the Auto Tilt Adjustment
Enabled field is checked.
Commissioned Status
In Progress
Indicates status of power

commissioning for this optical
line.
Completed
Gain Adjustment Settings
{00:00:00.0 - 23:59:59.9}
translated to/from
{0-86399.9}

NE to facilitate
gain adjustments
....................................................................................................................................................................................................................................
1830 PSS
10-90
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Time Period Between

Adjustments
{00:00:00.0 - 23:59:59.9}
translated to/from
{0-86399.9}

{00:00.0 - 59:59.9}


NE to facilitate
gain adjustments.

NE to facilitate
gain adjustments.
Wavelength Tracker Settings
Wavelength Tracker Decoder
Usage
WTD PPC On / Alarm On

WTD PPC On /Alarm Off
WTD PPC Off / Alarm Off
Indicates whether this optical

line uses classic wavelength
tracker decoder or a WTOCM
card.
WTD Inferred
WTOCM
....................................................................................................................................................................................................................................
1830 PSS
10-91
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to adjust LD power.

Before you begin

Power adjustment procedure

...................................................................................................................................................................................................
The WebUI supports egress and/or ingress power adjustments for A2P2125, A2325A,
AHPHG, AHPLG, ALPHG, AM2125A, AM2125B, AM2318A, and RA2P cards. Select
the appropriate card from the equipment tree and click the Power Adjustment tab.
Result: The Egress Power Adjustment or Ingress Power Adjustment screen is
displayed.
...................................................................................................................................................................................................
Select Perform Power Adjustment on this port: and click Submit.

Result: The Power Adjust Status: and Power Adjust Result: are displayed and
automatically updated with current status.

Note: Whether a particular card supports power adjustment is dependent on its current
topology. The WebUI will determine whether a given card supports an egress power
adjustment, ingress power adjustment, both or neither according to the following:
For A2325A, AHPHG, AHPLG, ALPHG:
If the LINE port Opposite Direction Port is set to itself, then both Ingress and
Egress adjust are supported.
If the LINE port Opposite Direction Port is set to another port, then only Egress
adjust is supported.
If the LINE port Opposite Direction Port is unassigned, then neither Ingress nor
Egress adjust is supported.
For A2P2125, AM2125A/AM2125B/AM2318A and RA2P:
If the LINEIN port Opposite Direction Port is set, then Ingress adjust is supported.
If the LINEIN port Opposite Direction Port is unassigned, then Ingress adjust is
not supported.
....................................................................................................................................................................................................................................
1830 PSS
10-92
Issue 1 June 2013

....................................................................................................................................................................................................................................
If the LINEOUT Opposite Direction Port is set, then Egress adjust is supported.
If the LINEOUT Opposite Direction Port is unassigned, then Egress adjust is not
supported.
Note: For power management alarm clearing procedures, see the Alcatel-Lucent 1830
Photonic Service Switch (PSS) Release 6.0 Maintenance and Trouble-Clearing Guide.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-93
Issue 1 June 2013

Power Adjustment
....................................................................................................................................................................................................................................
Power Adjustment
Attribute
Value/Format
Additional Info
Egress In-Service Power Adjustment

Power Adjust Status
In Progress
Completed
Indicates status of the latest

power adjustment.
Power Adjust Result
<0-255 chars>
Indicates result of the latest

power adjustment.
Perform In-Service Power

Adjustment
(checkbox)
Enables/disables a request to
start an in-service power
adjustment.
Abort in-progress Power

Adjustment
(checkbox)
abort the power adjustment
and return the power levels to
their original values.
Ingress In-Service Power Adjustment

WSS Overhead (dB)
{0-10}

NE to facilitate
power adjustments.
Only applicable if port is Auto
power-managed.
Gain Adjustment Calculation

Offset (dB)
{-3 to 3}
Value added to the result of

the gain adjustment
calculation.
Calculated Required Gain

(dB)
(as displayed)

NE to facilitate
power adjustments.
power-managed.
Gain at Commissioning
Complete (dB)
{0-33}
Gain value set while

Commissioned Status is not
complete.
Power Adjust Status
In Progress

power adjustment.
Completed
Power Adjust Result
<0-255 chars>

power adjustment.
....................................................................................................................................................................................................................................
1830 PSS
10-94
Issue 1 June 2013

Power Adjustment
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info

Adjustment
(checkbox)
start an in-service power
adjustment.
....................................................................................................................................................................................................................................
1830 PSS
10-95
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to view / modify power commissioning values

Note: To facilitate NE commissioning, the WebUI provides a screen with port power
attributes for all LD and CWR8 cards in the NE. The intent is for the user to input
data from the EPT Commissioning report directly in this screen and then initiate the
necessary power adjustments.
Before you begin

View / modify power commissioning values
Note: On the Power Commissioning screen, the WebUI supports modify and view of
up to 20 A2P2125, A2325A, AHPHG, AHPLG, ALPHG, AM2125A AM2125B,
AM2318A, OSCT), up to 16 RA2P cards, up to 16 MESH4 cards, up to 16 CWR8 or
CWR8-88 cards, and up to 16 WR2-88, WR8-88A, WR8-88AF cards on the NE.
...................................................................................................................................................................................................
In the WebUI, select Administration > Power Commissioning.

Result: The Power Commissioning window is displayed.
...................................................................................................................................................................................................
To modify power attributes, enter values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-96
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Power Commissioning
Attribute
Value/Format
Additional Info
A2325A, AHPHG, AHPLG, ALPHG and AM2325B

Egress Per-Channel Output
Power (dBm)
{-30 to 11}
The per-channel target egress

power on the SIG port.
NE to facilitate
power adjustments.
Egress Per-Channel Output

Power Deviation
{0-10}
Allowed per-channel egress

power deviation.
NE to facilitate
power adjustments.
Ingress or Add/Drop
Per-Channel Output Power
(dBm)
{-30 to 11}
Per-Channel Input Power

Deviation (dB)
{0-10}

power on the LINE port.
NE to facilitate
power adjustments.
Allowed per-channel ingress
power deviation.
NE to facilitate
power adjustments.
Ingress Per-Channel Output

Power Deviation (dB)
{0-10}

power deviation.
NE to facilitate
power adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-97
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Maximum Flat Gain Offset
Value/Format
{-5 to 5}
Additional Info
Provides a correction to the
assumed maximum flat gain
value.
NE to facilitate
adjustments.
Target Tilt (dB)
{-3 to 0}

NE to facilitate
power adjustments.
Tilt Calculation Coefficient

for DCM
{0-10000}
Modeling coefficient for the

SRS Tilt equation, for DCM.
NE to facilitate
tilt adjustments.
Tilt Calculation Multiplier
{0-300}
Used to modify the calculated

SRS tilt of the span.
NE to facilitate
tilt adjustments.
{0-10000}

SRS Tilt equation.
NE to facilitate
tilt adjustments.
Minimum Gain (dB)
A2325A: {16-32}
Desired minimum gain.
AHPHG: {13-33}

NE to facilitate
power adjustments.
AHPLG: {6-24}
ALPHG: {10-30}
AM2325B: {16-32}
....................................................................................................................................................................................................................................
1830 PSS
10-98
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Maximum Gain (dB)
Value/Format
Additional Info
A2325A: {16-32}
Desired maximum gain.
AHPHG: {13-33}

NE to facilitate
power adjustments.
AHPLG: {6-24}
ALPHG: {10-30}
AM2325B: {16-32}
Allowed Gain Delta (dB)
{0-5}

NE to facilitate
power adjustments.
WSS Overhead (dB)
{0-10}

NE to facilitate
power adjustments.
power-managed.
NOTE: This field is not
provisionable in the WebUI if
the pack is in Manual mode.
This field is only
provisionable once the pack is
in Auto mode. Please refer to
the required EPT model for
information.
Splice Margin (dB)
{0-10}

NE to facilitate
power adjustments.
power-managed.
Pre-Compensated Span Loss

Tilt (dB)
{0-3.00}
This field is for advanced

users who need to override
EPT values. For fiber span
attenuation versus frequency
tilt.
....................................................................................................................................................................................................................................
1830 PSS
10-99
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Post-Compensated Tilt
Fraction
Value/Format
{0-3.00}
Additional Info
Used to modify the fraction of
upstream span SRS tilt post
compensated.
NE to facilitate
tilt adjustments.
This field is only
information.
{0-86399.9}

NE to facilitate
gain adjustments.
Time Period Between

Adjustments
{0-86399.9}

NE to facilitate
gain adjustments.
{0-35999}

NE to facilitate
gain adjustments.

Offset
{0-10}

NE to facilitate
adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-100
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Span Loss Tilt
{0-3.00}

EPT values. Used to record
fiber span attenuation versus
frequency tilt for the span
following the egress port.
Connector Loss to Span
{0-10}
Configurable loss from the

egress Line Out to the fiber
span input.
NE to facilitate
tilt adjustments.

Offset
{-3 to 3}

the gain adjustment
calculation.
This field is only
information.
AM2318A, AM2125A and AM2125B

(dBm)
{-30 to 11}

power.
NE to facilitate
power adjustments.

Deviation (dB)
{0-10}

power deviation.
NE to facilitate
power adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-101
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Deviation (dB)
Value/Format
{0-10}
Additional Info
power deviation.
NE to facilitate
power adjustments.
Target Tilt (dB)
{-3 to 0}

NE to facilitate
power adjustments.

for DCM
{0-10000}

SRS Tilt equation, for DCM.
NE to facilitate
tilt adjustments.
Tilt Calculation Multiplier
{0-300}

NE to facilitate
tilt adjustments.
{0-10000}

SRS Tilt equation.
NE to facilitate
tilt adjustments.
Minimum Gain (dB)
Maximum Gain (dB)
AM2318A: {7-24}
AM2125A and AM2125B:

{15-31}

NE to facilitate
power adjustments.
AM2318A: {7-24}
AM2125A and AM2125B:

{15-31}

NE to facilitate
power adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-102
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Allowed Gain Delta (dB)
{0-5}

NE to facilitate
power adjustments.
WSS Overhead (dB)
{0-10}

NE to facilitate
power adjustments.
power-managed.
This field is only
information.
Splice Margin (dB)
{0-10}

NE to facilitate
power adjustments.
power-managed.
Output VOA Setting (dB)
{0-18}
Specifies the setting for the

VOA after the VGOAM.
Pre-Compensated Tilt
Fraction
{0-3.00}

following span SRS tilt pre
compensated.
NE to facilitate
tilt adjustments.

Tilt
{0-3.00}

tilt.
....................................................................................................................................................................................................................................
1830 PSS
10-103
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Post-Compensated Tilt
Fraction
Value/Format
{0-3.00}
Additional Info
compensated.
NE to facilitate
tilt adjustments.
This field is only
information.
{0-35999}

NE to facilitate
gain adjustments.
Time Period Between

Adjustments
{0-35999}

NE to facilitate
gain adjustments.
{0-35999}

NE to facilitate
gain adjustments.

Offset
{0-10}

NE to facilitate
adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-104
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Span Loss Tilt
{0-3.00}
This settings is for advanced


Enabled
(checkbox)

routine.
(checkbox)

routine.
{0-10}

span input.
NE to facilitate
tilt adjustments.

Offset
{-3 to 3}

the gain adjustment
calculation.
This field is only
information.
CWR8 and CWR8-88

Add Path Target Power (dBm)
{-10 to 10}

NE to facilitate
power adjustments.
Drop Path Target Power

(dBm)
{-26.5 to -4}

NE to facilitate
power adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-105
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Value/Format
Maximum Add Channel

Count
CWR8: {8-44}
Optical Interconnect Line

Count
{1-8}
CWR8-88: {8-88}
Additional Info
NE to facilitate
power adjustments.
NE to facilitate
power adjustments.
MESH4
(dBm)
{-30 to 11}

power.
NE to facilitate
power adjustments.
Output VOA Setting (dB)
{0-18}

Minimum Gain (dB)
{7-24}

NE to facilitate
power adjustments.
Maximum Gain (dB)
{7-24}

NE to facilitate
power adjustments.
Target Tilt (dB)
{-3 to 0}

NE to facilitate
power adjustments.
OSCT
Ingress Per-Channel Input

Power (dBm)
{-30 to 11}
The per-channel target ingress

power on the LINE port.
NE to facilitate
power adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-106
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
(dBm)
Value/Format
{-30 to 11}
Additional Info
power.
NE to facilitate
power adjustments.

Deviation (dB)
{0-10}

power deviation.
NE to facilitate
power adjustments.

Deviation (dB)
{0-10}

power deviation.
NE to facilitate
power adjustments.
RA2P
Fiber Type
ELEAF
SSMF
The expected fiber type of

RA2P.
TWRS
Target Tilt (dB)
{-3 to 0}

NE to facilitate
power adjustments.
Operational Mode
Power
Specifies the operating mode

for the amplifier.
Gain
Maximum Power
Expected Minimum Gain
{7.00} default
{0.00-25.00}

NE to facilitate
power adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-107
Issue 1 June 2013

Power Commissioning
....................................................................................................................................................................................................................................
Attribute
Expected Maximum Gain
Target Gain (dB)
Value/Format
Additional Info
{25.00} default
{0.00-25.00}

NE to facilitate
power adjustments.
{10.00} default
Target gain when Operational

Mode field is set to Gain.
{2.00 to 20.00}
WR2-88
Count
{1-2}

NE to facilitate
power adjustments.
WR8-88A and WR8-88AF

Count
{1-8}

NE to facilitate
power adjustments.
Level in Optical Node
{0-3}
Specifies the architecture

level value for WSS
containing packs in the
Anydirection Add/Drop
block. The value increases
from 0 for the WR8-88A pack
closest to the external optical
line to a maximum of 3 for
the CWR8-88 back furthest
from the external optical line.
....................................................................................................................................................................................................................................
1830 PSS
10-108
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Raman Operational Mode
Value/Format
Gain
Maximum Power
Raman Fiber Type
ELEAF
SSMF
Additional Info
Specifies the operating mode
for the amplifier.
The expected fiber type of the
A2P2125.
TWRS
Raman Expected Minimum
Gain (dB)
{0.00-25.00}
Raman Expected Maximum

Gain (dB)
{0.00-25.00}
Raman Initial Target Gain
{2.00 to 20.00}
Indicates the initial Raman

AGC target gain.
Mid EVOA Initial Loss
{0.00-25.00}
Specifies the target loss

between the Raman and
EDFA amplifiers for auto
power management mode.
Mid EVOA Attenuation
{0.00-25.00}
Specifies the attenuation of

the mid-VOA. This value can
only be specified in manual
power management mode.

NE to facilitate
power adjustments.
NE to facilitate
power adjustments.
If the value is set outside of

the range defined by Mid
EVOA Minimum Attenuation
and Mid EVOA Maximum
Attenuation, then the new
values will be set to the

nearest edge of the range.
Mid EVOA Minimum
Attenuation (dB)
{0.00-25.00}
Specifies the minimum

attenuation of the mid-VOA.
Mid EVOA Maximum

Attenuation (dB)
{0.00-25.00}
Specifies the maximum

attenuation of the mid-VOA.
....................................................................................................................................................................................................................................
1830 PSS
10-109
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
(dBm)
Value/Format
{-30 to 11}
Additional Info
power.
NE to facilitate
power adjustments.

Deviation (dB)
{0-10}

power deviation.
NE to facilitate
power adjustments.
EDFA Target Tilt (dB)
{-3 to 0}

NE to facilitate
power adjustments.
SRS Tilt Calculation

Multiplier
{0-300}

NE to facilitate
tilt adjustments.
SRS Tilt Calculation

Coefficient
{0-10000}

SRS Tilt equation.
NE to facilitate
tilt adjustments.
Span Loss Tilt
{0-3.00}

EDFA Minimum Gain (dB)
{15-31}

NE to facilitate
power adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-110
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
EDFA Maximum Gain (dB)
Value/Format
{15-31}
Additional Info
NE to facilitate
power adjustments.
EDFA Allowed Gain Delta

(dB)
{0-5}

NE to facilitate
power adjustments.
EDFA Output VOA Setting

(dB)
{0-18}

EDFA WSS Overhead (dB)
{0-10}

NE to facilitate
power adjustments.
power-managed.
This field is only
information.
EDFA Splice Margin (dB)
{0-10}

NE to facilitate
power adjustments.
power-managed.
Pre-Compensated SRS Tilt

Fraction
{0-3.00}

following span SRS tilt pre
compensated.
NE to facilitate
tilt adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-111
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Post-Compensated SRS Tilt
Fraction
Value/Format
{0-3.00}
Additional Info
compensated. EPT parameter
used by the NE to facilitate
tilt adjustments.
This field is only
information.

Tilt (dB)
{0-3.00}

tilt.
{0-86399.9}

NE to facilitate
gain adjustments.
Time Period Between

Adjustments
{0-86399.9}

NE to facilitate
gain adjustments.
{0-35999}

NE to facilitate
gain adjustments.
....................................................................................................................................................................................................................................
1830 PSS
10-112
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info

Offset
{0-10}

NE to facilitate
adjustments.

Enabled
(checkbox)

routine.
(checkbox)

routine.
{0-10}

span input.
NE to facilitate
tilt adjustments.

Offset
{-3 to 3}

the gain adjustment
calculation.
This field is only
information.
....................................................................................................................................................................................................................................
1830 PSS
10-113
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to adjust LD power.

Before you begin

Power adjustment
Note: For each LD, the WebUI supports Egress and Ingress power adjustment for
both Ring (ASE Adjust) and Linear (Forced X-Conn Reqd) topologies.
...................................................................................................................................................................................................
In the WebUI, select Administration > Power Commissioning.

Result: The Power Commissioning window is displayed.
...................................................................................................................................................................................................
Click Power Adjust.

Result: The Power Adjustment window is displayed.
...................................................................................................................................................................................................
Enter attribute values and click Submit.

Note: If the power adjustment fails, check the OT line admin state and if it is down,
change it to up and rerun the adjustment.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-114
Issue 1 June 2013

Power Adjustment
....................................................................................................................................................................................................................................
Power Adjustment
Attribute
Value/Format
LD
Side
Shelf/slot of the LD card.

Ingress
Egress
Topology
Ring (ASE Adjust)

Linear (Forced X-Conn
Reqd)
Power Adjust Status
Additional Info
In Progress
Complete
Specifies ingress or egress

power adjustment.
Specifies ASE or in-service
power adjustment.
power adjustment.
Power Adjust Result
<0-255 chars>

power adjustment.
ASE Mode
Enter
Specifies whether to start or

stop an ASE power
adjustment
Exit
Perform ASE Power
Adjustment
Request to start an ASE

power adjustment. Only
applies to Ring topology.

Adjustment
Request to start an in-service

power adjustment. Only
applies to Linear topology.
Abort in-progress Power

Adjustment
Request to abort the power

adjustment and return the
power levels to their original
values. Only applies to
Egress, Linear power
adjustment.
....................................................................................................................................................................................................................................
1830 PSS
10-115
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision GMRE settings.

Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > GMRE > settings.

Result: The GMRE settings window is displayed.
...................................................................................................................................................................................................
Enter values for IP Settings and CORBA settings.

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-116
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure for file transfer.

Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > GMRE > Feasibility File Transfer.
Result: The Feasibility File Transfer window is displayed.
...................................................................................................................................................................................................
Enter values for Remote Server Configuration fields.

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-117
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision OMS line parameters.

Before you begin

Instructions
Note: The WebUI supports provisioning of OMS Line and Optical Impairment
parameters for each of the following port types:
A2325A, AHPHG, AHPLG, ALPHG: LINE ports.

A2P2125, AM2125A, AM2125B, AM2318A, and RA2P: LINEIN ports.
...................................................................................................................................................................................................
In the WebUI, select Administration > GMRE Commissioning > OMS Line Parameters.
Result: The OMS Line Parameters window is displayed.
...................................................................................................................................................................................................
Enter desired values.

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-118
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision optical impairment parameters.

Before you begin

Instructions
Note: The WebUI supports provisioning of OMS Line and Optical Impairment
parameters for each of the following port types:
A2325A, AHPHG, AHPLG, ALPHG: LINE ports.

A2P2125, AM2125A, AM2125B, AM2318A, and RA2P: LINEIN ports.
The WebUI supports import of the EPT GMRE commissioning file in XML
format. If necessary, the WebUI will round the value from the EPT file before
displaying/sending to the NE.
...................................................................................................................................................................................................
In the WebUI, select Administration > GMRE Commissioning > Optical Impairment
Parameters.
Result: The Optical Impairment Parameters window is displayed.
...................................................................................................................................................................................................
Select an LD from the pull-down list.

...................................................................................................................................................................................................
Click Retrieve.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-119
Issue 1 June 2013

Procedure 10-30: Cross-phase modulation allowed

wavelength set
....................................................................................................................................................................................................................................
Procedure 10-30: Cross-phase modulation allowed wavelength

set
When to use
Use the following procedure to provision cross-phase modulation allowed wavelength set.
Before you begin

Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > GMRE Commissioning > XPM Allowed
Wavelength Set.
Result: The Cross-Phase Modulation Allowed Wavelength Set window is displayed.
...................................................................................................................................................................................................
Select an LD from the pull-down list.

...................................................................................................................................................................................................
Click Retrieve.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
10-120
Issue 1 June 2013
11
11 traffic provisioning
TDM
procedures
Overview
Purpose
Contents
Introduction
11-2
Cross-connection types
11-2
Different ways to create a cross-connection
11-7
Different ways to modify a cross-connection
11-8
11-9
11-10
11-15
11-18
Procedure 11-4: Retrieve a list of cross-connections
11-21
...................................................................................................................................................................................................................................
1830 PSS
11-1
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Introduction
Overview
Alcatel-Lucent 1830 PSS systems support unidirectional, bidirectional and broadcast

cross-connections, unprotected as well as protected.
In addition, drop & continue connections are supported.
Unidirectional Connection
Information is transmitted exclusively from the input termination point to the output
termination point (point-to-point); there is no routing in reverse direction.
Input TP
Output TP
Bidirectional Connection
Information is transmitted between input termination point and output termination point
in both directions (point-to-point).
Input TP
Output TP
Broadcast Connection (Multi-leg / Multipoint)
In contrast to a cross-connection between just two points (point-to-point), one source and
one sink, a broadcast connection consists of one source and several sinks, different 'legs'
that share the same source termination point.
In the following example, information is broadcast from one input termination point to
the output termination points A, B and C on three legs.
....................................................................................................................................................................................................................................
1830 PSS
11-2
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
output A
leg 1
input TP
leg 2
output B
leg 3
output C
A warning box indicates when the resources available for broadcast connections are
exhausted.
Note: Up to 10 tails are allowed for one broadcast/multicast cross connection.
Note: Adding a protection leg to a unidirectional cross-connection offers the ability to
perform non-intrusive monitoring on this cross-connection. No errors are introduced
to the original cross-connection with applying or removing the protection leg.
Protected unidirectional connection
A unidirectional connection is routed from Input A to the output termination point

(primary route). In the case of a failure on the primary route, the system automatically
switches to the protection path from protection Input B to the output termination point.
This second connection is permanently kept in hot standby operation.
input A
output TP
prot.
input B
in case of
failure
Protected bidirectional connection
A bidirectional connection is routed from input A to the output C (primary route). Input A
can be protected as shown in the following diagram:
....................................................................................................................................................................................................................................
1830 PSS
11-3
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
A
C
B
in case of
failure
Note: This type of cross-connection topology is used to configure a sub-network

connection protection (SNCP).
Protected broadcast connection
The protected broadcast is realized as a set of independent, protected, unidirectional

connections using the same pair of input termination points, as illustrated in the following
diagram. Each protection can be forced, locked out or switched independently. Therefore,
if a failure occurs at a certain input, it is possible that only some of the protections of the
protected broadcast actually switch to the protection input.
leg 1
output A
input A
leg 2
output B
prot.
input B
leg 3
in case of
failure
output C
The diagram shows a broadcast connection from input A to the outputs A, B and C. The
legs 2 and 3 are protected via the protecting input B, whereas leg 1 is not protected.
Note: The current release only supports 1 to 2 broadcast.
Drop & continue connection
A drop & continue connection consists of the following connections:
a unidirectional broadcast connection routed from input A to the output C and to

output B (not supported for ODUk cross-connections).
a unidirectional connection from protecting input B to output C.
a unidirectional connection from output C to input A.
Output C is protected; when output C receives its input from the main input A, then the
connection is called normal, when output C receives its input from the protecting input B,
then the connection is called inverse.
All the connections are created in a single step of configuration.
....................................................................................................................................................................................................................................
1830 PSS
11-4
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
Drop & continue - normal

B
A
Input
Prot. input
C
Output
Drop & continue insert connection
The following diagram shows an example of a drop & continue insert connection:
B
A
Input
C
Prot. input
Output
A drop & continue insert connection consists of two cross-connections:
First connection:
a unidirectional broadcast connection routed from Input A to Output B and C
Second connection:
a protected unidirectional connection routed from Input C to Output A, with
protecting Input B
SDH/SONET to OTH Gateway operation
The matrix provides on a single pack either SDH/SONET switching or OTN switching,
but no gateway functionality (i.e. cross conection on VC/STS level and mapping the
resulting STMn/OCn signal into an ODU).
This functionality can be achieved via external optical fiber connection between the
SDH/SONET switching cards and TDM client cards.
....................................................................................................................................................................................................................................
1830 PSS
11-5
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................
VC4
STM-64
VC4
XC
24xAN S
24xAN S
24SDM
SDH/SONET
Switching
VC4
optical fiber
STM-16
Matrix
ODU
ODU2
XC
STM-64
I/O Pack with

I/O Pack with
10
x10 Client
G ANYLoad
TDM
TDM Client Load
TDM Client Load
OTN
Switching
OTN Capacity
OTM-0 .3
24xAN S
2x40G
24xAN
ANY
S
Network Load
Tota l Cap acity:

3T8, 1T9, 960G
10 x10G S
10x10G S
10SD10G
SDH/SONET Cap acity:

Up to 640G
The following diagram shows an example how VC4s from STM-16 ports are groomed
into an STM-64 signal, which is then mapped into an ODU2 and sent out in an ODU3:
ODU
Note: It is required to have an optical fiber between the 10SD10G pack and the
10x10G ANY TDM Client load card.
Possible IO cards are:


This optical connection is not modeled by the system. Thus no special alarming is
done for this connection, i.e. the normal LOS alarming is applied.
....................................................................................................................................................................................................................................
1830 PSS
11-6
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................

Introduction
The central dialog box to create a cross-connection by means of the Alcatel-Lucent

1830 PSS ZIC is the Create Cross Connections window.
This section describes different ways to open the Create Cross Connections window.
Related information
For a description of the configuration options available in the Create Cross Connections
window, refer to Create Cross Connections window (p. 9-3).
Different ways
In principle, the following ways exist to open the Create Cross Connections window:
SelectCrossConnection in the navigation pane of the Alcatel-Lucent 1830 PSS ZIC ,

and then select Create Cross Connections in the display pane.
Using this option, the Create Cross Connections window will open with a basically
empty table of relevant configuration parameters, for which you will need to enter the
corresponding values manually.
Navigate to the facility for which you want to create a cross-connection, and then
select either Action Go To Create Cross Connection from the main menu bar,
or right click on the selected facility, and select Go To Create Cross Connection
Using this option, the Create Cross Connections window will have the source facility
of the cross-connection already populated with the facility selected in the previous
steps, and you will need to enter the remaining values.
....................................................................................................................................................................................................................................
1830 PSS
11-7
Issue 1 June 2013

Introduction
....................................................................................................................................................................................................................................

Introduction
The central dialog box to modify a cross-connection by means of the Alcatel-Lucent

1830 PSS ZIC is the Manage Cross Connections window.
This section describes different ways to open the Manage Cross Connections window.
Related information
For a description of the configuration options available in the Manage Cross Connections
window, refer to Manage Cross Connections window (p. 9-6) .
Different ways
In principle, the following ways exist to open the Manage Cross Connections window:
SelectCrossConnection in the navigation pane of the Alcatel-Lucent 1830 PSS ZIC,

and then select Manage Cross Connections in the display pane.
Using this option, the Manage Cross Connections window will open with a basically
empty table of relevant configuration parameters, and you will need to find the
desired cross-connection out of all existing cross-connections in the system. When
you have selected the cross-connection, you can modify the configuration parameters
according to your needs.
Navigate to the facility for which you want to create a cross-connection, and then
select either Action Go To Supporting Cross Connection from the main menu
bar, or right click on the selected facility, and select Go To Supporting Cross
Connection from the context menu that opens.
Using this option, the Manage Cross Connections window will have the
configuration parameters of the cross-connection already populated with the values of
the existing cross-connection selected in the previous steps, and you can modify these
configuration parameters according to your needs.
....................................................................................................................................................................................................................................
1830 PSS
11-8
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
Overview
Purpose
Contents
11-10
11-15
11-18
11-21
....................................................................................................................................................................................................................................
1830 PSS
11-9
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create a cross-connection.

ENT-CRS-ODU0
ENT-CRS-ODU1
ENT-CRS-ODU2
ENT-CRS-ODU2E
ENT-CRS-ODU3
ENT-CRS-ODU3E2
ENT-CRS-ODU4
ENT-CRSPROT-ODU0
ENT-CRSPROT-ODU1
ENT-CRSPROT-ODU2
ENT-CRSPROT-ODU2E
ENT-CRSPROT-ODU3
ENT-CRSPROT-ODU3E2
ENT-CRSPROT-ODU4
ENT-CRS-VC-4
ENT-CRS-VC-4-4C
ENT-CRS-VC-4-16C
ENT-CRS-STS1
ENT-CRS-STS3C
ENT-CRS-STS12C
ENT-CRS-STS48C
ENT-CRSPROT-STS1
ENT-CRSPROT-STS3C
ENT-CRSPROT-STS12C
ENT-CRSPROT-STS48C
ENT-CRSPROT-VC4
ENT-CRSPROT-VC4-4C
ENT-CRSPROT-VC4-16C
....................................................................................................................................................................................................................................
1830 PSS
11-10
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
There are different ways for setting up a cross connection.

Then select Create Cross Connections, either by selecting Action from the main
navigation tree underFacilities, and navigate through the facility group and select a
specific facility.
Then select Go to Create Cross Connections, either by selecting Action from the
...................................................................................................................................................................................................
Click the Wizard button.

Result: The Alcatel-Lucent 1830 PSS ZIC Connection Wizard window opens.
...................................................................................................................................................................................................
In the field Connection Type select the type of cross-connection you want to set up.
...................................................................................................................................................................................................
In the facility area populate the respective fields with the needed facilities.
...................................................................................................................................................................................................
Set the Repeat Count as needed.

...................................................................................................................................................................................................
Click Apply.
....................................................................................................................................................................................................................................
1830 PSS
11-11
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................

Possible values:

0, 30, 50, 70, 100, 300, 500, 700, 1000, 3000, 5000, 10000.
Note that the hold-off time should be configured , that an interaction with other protection
schemes (equipment protection or MS-SPRing /BLSR) is taken into consideration. Via
different hold-off times it can be defined which protection should switch first.
...................................................................................................................................................................................................
Select the Revert Delay Time if the SNCP/UPSR is working in revertive mode. Values
between 0 and 15 min are allowed.
...................................................................................................................................................................................................
10

service affecting.
...................................................................................................................................................................................................
11
Click OK.
Result: The cross-connection is created.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
11-12
Issue 1 June 2013

....................................................................................................................................................................................................................................
How to navigate directly from a facility to the Create Cross Connections window
An alternative way to invoke the Create Cross Connections window is to select a

cross-connectable facility, such as an ODU1, or STS-1 for example, and then select
Action Go To Create Cross Connection from the Alcatel-Lucent 1830 PSS ZIC
main menu bar, or right-click on the selected facility, and choose Go To Create Cross
Connection from the context menu that opens.
The following figure illustrates this alternative way using an ODU2, an STS-1, and an
STS-48c facility as an example.
Figure 11-1 Navigating directly from a facility to the Create Cross Connections
window (1 of 2)
....................................................................................................................................................................................................................................
1830 PSS
11-13
Issue 1 June 2013

....................................................................................................................................................................................................................................
Figure 11-1 Navigating directly from a facility to the Create Cross Connections
window (2 of 2)
....................................................................................................................................................................................................................................
1830 PSS
11-14
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to modify a cross-connection.

ED-CRS-ODU0
ED-CRS-ODU1
ED-CRS-ODU2
ED-CRS-ODU2E
ED-CRS-ODU3
ED-CRS-ODU3E2
ED-CRS-ODU4
ED-CRSPROT-ODU0
ED-CRSPROT-ODU1
ED-CRSPROT-ODU2
ED-CRSPROT-ODU2E
ED-CRSPROT-ODU3
ED-CRSPROT-ODU3E2
ED-CRSPROT-ODU4
ED-CRS-VC4
ED-CRS-VC4-4C
ED-CRS-VC4-16C
ED-CRS-STS1
ED-CRS-STS3C
ED-CRS-STS12C
ED-CRS-STS48C
ED-CRSPROT-VC4
ED-CRSPROT-VC4-4C
ED-CRSPROT-VC4-16C
ED-CRSPROT-STS1
ED-CRSPROT-STS3C
ED-CRSPROT-STS12C
ED-CRSPROT-STS48C
....................................................................................................................................................................................................................................
1830 PSS
11-15
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select Manage Cross Connections, either by selecting Action from the main
specific facility.
Then select Go to Supporting Cross Connections, either by selecting Action from
opens.
...................................................................................................................................................................................................
In the field Cross Connection Type select All .

...................................................................................................................................................................................................
Click Retrieve.
take some time.

...................................................................................................................................................................................................
Click OK.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
11-16
Issue 1 June 2013

....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the cross-connection to be modified in the list.

...................................................................................................................................................................................................
If
Then
you haven't selectet an SNCP
continue with the next step
you have selectet an SNCP
continue with Procedure 9-4: Modify an

SNCP protection group (p. 9-27).
...................................................................................................................................................................................................
Modify the desired parameters.

...................................................................................................................................................................................................
You can modify the Circuit ID.

0 to 45 ASCII characters within enclosing double quotes. Semicolon, asterisk,
greater-than, less-than, double quote, and backslash characters are prohibited.
...................................................................................................................................................................................................
10

service affecting.
...................................................................................................................................................................................................
11
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
11-17
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete a cross-connection.

DLT-CRS-ODU0
DLT-CRS-ODU1
DLT-CRS-ODU2
DLT-CRS-ODU2E
DLT-CRS-ODU3
DLT-CRS-ODU3E2
DLT-CRS-ODU4
DLT-CRSPROT-ODU0
DLT-CRSPROT-ODU1
DLT-CRSPROT-ODU2
DLT-CRSPROT-ODU2E
DLT-CRSPROT-ODU3
DLT-CRSPROT-ODU3E2
DLT-CRSPROT-ODU4
DLT-CRS-STS1
DLT-CRS-STS3C
DLT-CRS-STS12C
DLT-CRS-STS48C
DLT-CRS-VC4
DLT-CRS-VC416C
DLT-CRS-VC44C
DLT-CRSPROT-STS1
DLT-CRSPROT-STS3C
DLT-CRSPROT-STS12C
DLT-CRSPROT-STS48C
DLT-CRSPROT-VC4
DLT-CRSPROT-VC44C
DLT-CRSPROT-VC416C
....................................................................................................................................................................................................................................
1830 PSS
11-18
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

navigation tree under Facilities, and navigate through the facility group and select a
specific facility.
opens.
...................................................................................................................................................................................................

Then select Manage Cross Connections, either by selecting Action from the main menu
opens.
...................................................................................................................................................................................................
In the field Cross Connection Type select All.

...................................................................................................................................................................................................
Click Retrieve.
....................................................................................................................................................................................................................................
1830 PSS
11-19
Issue 1 June 2013

....................................................................................................................................................................................................................................
take some time.

...................................................................................................................................................................................................
Click OK.
...................................................................................................................................................................................................
Select the cross-connection to be deleted in the list.

...................................................................................................................................................................................................
Click Delete.
service affecting.
...................................................................................................................................................................................................
Click OK.
Result: The cross-connection is deleted.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
11-20
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve a list of cross-connections.

RTRV-CRS-ODU0
RTRV-CRS-ODU1
RTRV-CRS-ODU2
RTRV-CRS-ODU2E
RTRV-CRS-ODU3
RTRV-CRS-ODU3E2
RTRV-CRS-ODU4
RTRV-CRSPROT-ODU0
RTRV-CRSPROT-ODU1
RTRV-CRSPROT-ODU2
RTRV-CRSPROT-ODU2E
RTRV-CRSPROT-ODU3
RTRV-CRSPROT-ODU3E2
RTRV-CRSPROT-ODU4
RTRV-CRS-VC4
RTRV-CRS-VC4-4C
RTRV-CRS-VC4-16C
RTRV-CRS-STS1
RTRV-CRS-STS3C
RTRV-CRS-STS12C
RTRV-CRS-STS48C
RTRV-CRSPROT-VC4
RTRV-CRSPROT-VC4-4C
RTRV-CRSPROT-VC4-16C
RTRV-CRSPROT-STS1
RTRV-CRSPROT-STS3C
RTRV-CRSPROT-STS12C
RTRV-CRSPROT-STS48C
....................................................................................................................................................................................................................................
1830 PSS
11-21
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
There are different ways for selecting a cross connection.

specific facility.
Result: The Alcatel-Lucent 1830 PSS ZIC Mange Cross Connections window opens.
...................................................................................................................................................................................................
In the field Cross Connection Type select All.

...................................................................................................................................................................................................
Click Retrieve.
take some time.
...................................................................................................................................................................................................
Click OK.
Result: All cross-connections are displayed.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
11-22
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: All Protection parameters are displayed.
Note: PST values for unidirectional cross connections may be inconsistent and
misleading in certain cases.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
11-23
Issue 1 June 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
11-24
Issue 1 June 2013
12
12 traffic provisioning
WDM
procedures
Overview
Purpose
This chapter describes the connection functionality supported by the Alcatel-Lucent

1830 PSS WDM application..
Contents
Description
12-3
Procedure 12-1: Display NE physical topology
12-8
Physical Topology
12-9
12-10
12-11
OCH Cross-Connects
12-13
Create OCH Cross-Connect
12-15
12-17
12-19
ODUk Cross-Connects
12-20
12-21
Procedure 12-6: Provision EVPL connections
12-22
12-23
Create EVPL Connection (SubRate)
12-24
12-26
Procedure 12-7: Display the cross connect topology
12-28
12-29
12-30
...................................................................................................................................................................................................................................
1830 PSS
12-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Cross-Connect Power Trace
12-31
Procedure 12-9: Display network power trace
12-32
Network Power Trace
12-33
Procedure 12-10: Connect Alcatel-Lucent 1830 PSS-1 to 1830

PSS-32/PSS-16/PSS-32S
12-34
....................................................................................................................................................................................................................................
1830 PSS
12-2
Issue 1 June 2013
Description
....................................................................................................................................................................................................................................
Description
Physical topology
The WebUI displays a physical view of the NE topology. This view includes the shelves,
cards and ports applicable to fiber connection management, as well as the existing fiber
connections between ports on the NE.
The Physical Topology view allows the user to create a new fiber connection by selecting
2 ports on the displayed shelves and clicking Connect. Only those ports that are not
already part of a fiber connection are available for creating a new fiber connection. The
connection can be made between 2 ports on the same shelf or on different shelves.
A loopback connection can be created via the Physical Topology view by selecting an
A2325A/AHPHG/AHPLG/ALPHG DCM port, clicking Loopback, and then clicking
Connect.
The Physical Topology view allows the user to create an external connection by selecting
1 port on the shelf and clicking External. Only certain ports are valid external connection
points and these are the CWR8/CWR8-88 CLS port, LD Line port, OT Line port, SFC
OMD port, SFD OMD port, SFD channel ports, MVAC ports, ITLB SIG port, OPSA SIG
port, OT client ports, and SVAC client port. Enter the IP address and shelf/slot/port of the
external NE if configuring an LD line port as external and click Connect. If connecting a
different port type as external, enter identifying information for the destination port.
The Physical Topology view allows the user to delete an existing fiber connection by
selecting the line representing the fiber connection and clicking Disconnect. A fiber
connection cannot be deleted if there is a cross-connect associated with the fiber
connection.
A physical topology connection or assignment is denied by the system if making such a
connection or assignment would result in an invalid topology.
Note: Creation of unkeyed cross connection is allowed when a CWR pack is involved
in the physical topology connection on a manual power management configuration.
Note: When there is a topology change (adding branching topology to existing
topology) a warm reset of the EC must be performed to avoid unexpected channel
alarms.
Bidirectional / unidirectional fiber connection
The Physical Topology view allows the user to create a new fiber connection by selecting
2 ports on the displayed shelves, selecting the directionality (bidirectional or
unidirectional) and clicking Connect. The WebUI distinguishes between unidirectional
and bidirectional fiber connections on the physical topology graphical display by
displaying the unidirectional fiber connections with an arrow at the end of the line to
indicate the direction.
....................................................................................................................................................................................................................................
1830 PSS
12-3
Issue 1 June 2013
Description
....................................................................................................................................................................................................................................
A bidirectional fiber connection may be made between a port and an external interface.
For this connection, the user selects one NE port and selects External. The user may
optionally enter address information for the external port.
A unidirectional fiber connection may be made between a port and an external interface.
The unidirectional connection may start on a port on the NE (i.e. the NE port is the
from port) or may end on a port on the NE (i.e. the NE port is the to port). For this
connection, the WebUI allows the user to indicate whether the internal port is the start or
end port of the connection. The user may optionally enter address information for the
external port.
Note: For a bidirectional connection, only those ports that are not already part of a
fiber connection are available for creating a new fiber connection.
For a unidirectional connection, only those ports that are not already part of a
bidirectional fiber connection, or part of a unidirectional fiber connection in the same
direction, are available for creating a new fiber connection.
For additional information on bidirectional/unidirectional fiber, see the Alcatel-Lucent
1830 Photonic Service Switch Release 6.0 Product Information and Planning Guide. .
Bidirectional single-fiber transmission
Some applications require bi-directional transmission over a single fiber. A PSS-32

FOADM CWDM node can be configured to support such an application using CWDM
filters. Each bidirectional transmission requires different CWDM wavelengths in each
direction.
This is accomplished with 2 fiber connections (transmit and receive) from the OT to two
adjacent wavelengths connections on the MUX (in) side of the filter. The wavelengths
pass between the MUX side of the filter and the OMD out port in both the receive and
transmit directions. The single fiber connected to the OMD out port carries signals in both
directions on their assigned wavelengths.
Bidirectional transmission over a single fiber is supported with any of the following
filters and OTs:
SFC-2(A, B, C, or D)
SFC-4(A or B)
SFC-8
4DPA4
11STAR1
11STMM10
11DPE12(E)
For additional details regarding bidirectional single-fiber transmission, see the

Alcatel-Lucent 1830 Photonic Service Switch Release 6.0 Product Information and
Planning Guide.
....................................................................................................................................................................................................................................
1830 PSS
12-4
Issue 1 June 2013
Description
....................................................................................................................................................................................................................................
EVPL connections
Ethernet Virtual Private Line (EVPL) connections are full-rate or sub-rate cross-connects
within an 11DPE12(E) card. The WebUI supports provisioning of EVPL connections. All
EVPL connections are modeled as unidirectional in the NE. When creating a new
connection, the WebUI allows the user to request that a 2nd ZA connection be created. If
so requested, then the WebUI automatically creates 2 unidirectional connections stored
separately in the NE. The WebUI allows EVPL connections to be deleted if the GbE client
port has AdminState = Down.
Optical cross-connect
An optical cross-connect defines the optical path a service channel takes through the NE.
Cross-connects use the provisioned NE fiber topology to traverse the path through the NE
between the two ports that define the endpoints of the cross-connect. Within an NE, a
valid cross-connect is identified by an optical channel and the two ports at the endpoints
of the cross-connect. To add/drop a service, the cross-connect terminates at an OT line
port and the NE's network ingress/egress port (typically the Line port of the LD). For an
optical pass through service, the cross-connect terminates at network ports (typically LD
Line In/Out ports) at the entry and exit point of the NE. Within the network consisting of
the connected NEs, the service is identified by an Optical Channel (OCH) trail which
consists of several cross-connects hosted by each NE.
ODUk Cross Connects
ODUk Cross Connects are supported within an 11DPM12, 112PDM11, and the client/line
cards. The WebUI displays a list of all ODUk cross-connects on the NE. The WebUI
supports create, modify and view of an ODUk cross-connects and the WebUI supports
deletion of an ODUk cross-connect.
Note: ODUk cross connects need to all be built the same way (client to line, relative
to A to Z) on all client to line ports of the same MUX card. A-End and Z-End must be
on the same 11DPM12, 112PDM11, or client/line card (i.e. have the same values for
<shelf/slot>).
Connection service
The connection service allows OCH Trails to be connected through ports of the network
element by means of all optical switching. Optical trails can be added or dropped at each
network element that provides the appropriate transponders for the signal type. An optical
trail is composed of a series of optical cross-connects beginning at the source with an add
connection where a wavelength tracker key is applied to the optical signal, followed by a
series of through connections that route a signal to its destination, and culminating in a
drop connection at that destination where the signal is converted back to the appropriate
....................................................................................................................................................................................................................................
1830 PSS
12-5
Issue 1 June 2013
Description
....................................................................................................................................................................................................................................
client wavelength and format. Optical trails can be uni-directional or bi-directional, 1+1
protected or unprotected. Services are, for the purpose of this document Optical Channel
Trails (OCH Trails) which are composed of optical cross-connects.
The opposite direction port parameter defines the association between two uni-directional
ports so a bi-directional cross connection can be used with different uni-directional
topology connections. For the opposite direction port, the value "0" is used to unassign
the provisioned value.
For service additions to DWDM FOADM Optical Networks, or to verify the addition of
unplanned (not included in the original network design) services on TOADM or mixed
networks, (e.g., unplanned OPS protection, alien services, or 2.5G wavelengths) use the
following procedure:
1. Enter the new service (demand) into the 1830 PSS Engineering and Planning Tool
(EPT), "run design", and "verify the design". See the Alcatel-Lucent 1830 Photonic
Service Switch (PSS) Release 6.0 Engineering and Planning Tool User Guide, the
sub-section on "WDM Demands" under the section titled "Traffic Design".
2. Create the commissioning file(s) in the EPT for the systems which the service
traverses, to send to the PhM.
3. Provision the new cards for the service using the procedure "Provision the System" in
Part III, Section 7, of the Alcatel-Lucent 1830 Photonic Service Switch 36/32/16
(PSS-36/32/16) Release 3.5.1 Installation and System Turn-Up Guide. This will use
the EPT commissioning files, which now contain the cards for the new service and
new provisioning information.
4. Re-adjust the power of the spans along the route of the new service, if necessary. For
TOADM or DWDM FOADM lines, for each of the spans where the new service
demand is added, passing through (if any) and dropped, run Egress and Ingress
adjustments to make the new EPT values effective. Use the procedure "Complete
commissioning on a mixed TOADM/FOADM system" from the Alcatel-Lucent 1830
Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.5.1 Installation and
System Turn-Up Guide procedures in Part III, Section 7, starting with the procedure
step 1 (skip the information on commissioning services as this is for greenfield
applications), for help in this activity.
Important! The EPT design must be up-to-date with the currently deployed network
before using the procedure above to add a new service to the network.
Connecting Alcatel-Lucent 1830 PSS OT with Alcatel-Lucent 1696 ROADM
The line interface of the 1830 OTs can be fibered directly to a 1696R node for transport in
a 1696-based network. For this application, the 1830 OT provides a signal (with
WaveTracker encoding and power management) to the 1696R node. The OT itself is
installed in an 1830 shelf, and is managed by the 1830 node. This 1696R/1830
interworking application is sometimes called the dangling OT.
....................................................................................................................................................................................................................................
1830 PSS
12-6
Issue 1 June 2013
Description
....................................................................................................................................................................................................................................
A dangling OT, or a group of dangling OTs, are 1830 optical transponders which are
plugged into an 1830 shelf and managed by the 1830 node. However, the dangling OT
line side optical ports (transmit and receive) are not fiber-connected to a CWR or OMD
pack in the 1830 NE. Instead, the line side ports are fibered to a 1696R node. In the CLI
user commands, there is a provisionable parameter (CONNTO) that is used to set up an
external connection (i.e., CONNTO=external) from the OT to the 1696R node. When
CONNTO=external, the user can enable wave key modulation functionality and control
the optical output power on the line side interface of the OT (see Instructions for L1
port (p. 10-55)). The 1696R equipment will then receive this signal (with wave keys
already encoded) from the 1830 OT.
Note: If a port is Auto power-managed, and either Tx or Rx for that port is changed
from External to NotConnected, then both Tx and Rx will be automatically changed
from Auto to Manual power management.
Note: An alien wavelength can enter the 1830 system through a variable attenuator
card (VAC) or via direct connection to a SFD channel or CWR CLS port.
If a VAC is used, the 1830 system is capable of encoding wave keys on the
wavelength.
If a VAC is not used, wavekeys will not be added to the wavelength by the 1830
system.
The SFD channel/CWR CLS port is provisioned with an external TL.

The XC provisioned for this configuration terminates on the SFD channel/ CWR
CLS port.
Connecting Alcatel-Lucent 1696 ROADM transponder with Alcatel-Lucent 1830 PSS
The system supports the configuration where the 1696R transponder is plugged into the
1696R shelf and the network port of the transponder is connected to 1830 SVAC channel
port. The SVAC itself can be part of 1830 TOADM or FOADM node. The 1830 SVAC
does encoding and power control for the 1696R transponder transmitter. The 1696R shelf
will manage the laser on and WT encoding off. The Alcatel-Lucent 1830 PSS and 1696R
shelf each has its own TID.
....................................................................................................................................................................................................................................
1830 PSS
12-7
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to display NE physical topology.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Connections > Physical Topology.

Result: NE Physical Topology is displayed.
...................................................................................................................................................................................................
Loopback, External, Disconnect, and Connect functions can be made via the display.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-8
Issue 1 June 2013
Physical Topology
....................................................................................................................................................................................................................................
Physical Topology
Attribute
Shelf
Value/Format
{1-64}
Additional Info
Identifies the shelf number
that is currently displayed.
Select a different number to
display another shelf.
Clear
Clears a port selection or

pending connection.
BiDir
Request to create an internal

bidirectional fiber connection.
UniDir
Request to create an internal

unidirectional fiber
connection. The direction is
indicated as A to Z or Z to A.
External
Request to create an external

fiber connection.
InterCompound
Request to create a
connection to an OCS shelf.
Loopback
Request to create a fiber

connection that loops back on
itself. Applies to LD DCM
ports only.
Modify
Request to modify a selected

fiber connection.
Delete
Request to delete a selected

fiber connection.
....................................................................................................................................................................................................................................
1830 PSS
12-9
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to display NE logical topology.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Connections > Logical Topology.

Result: NE Logical Topology is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-10
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision OCH cross-connects.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Connections > OCH Cross Connects.

Result: Cross-connects are displayed. The following cross-connect options are
available: Create, Details, A-Z Topology, Z-A Topology, A-Z Power, Z-A Power, A-Z
Trace, Z-A Trace, Delete.
E...................................................................................................................................................................................................
N D O F S T E P S
112PDM11 cross-connection provisioning

...................................................................................................................................................................................................
Create the 10GbE LAN port. Then ODU2e has been created automatically when 10GbE
LAN has been provisioned.
CLI command: config interface 112PDM11 shelf/slot/port type tengige.
...................................................................................................................................................................................................
Line side ODU4 has been substructured automatically by ten ODU2e with continuous
timeslots.
CLI command: show oduptf odu4 shelf/slot/port odu substructure.
...................................................................................................................................................................................................
Create cross-connection between 10GbE Client port and ODU2e in line ODU2e with fix
association as below:
CLI commands:
config odukxc 1/5/L1/1 1/5/C1 create odu2e bi
....................................................................................................................................................................................................................................
1830 PSS
12-11
Issue 1 June 2013
....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Set the client port State, line port state, client ODU2e,line ODU4 state to IN-Service
(UP).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-12
Issue 1 June 2013
OCH Cross-Connects
....................................................................................................................................................................................................................................
OCH Cross-Connects
Attribute
Values/Format
Additional Info
A-End Port
<shelf/slot/port>
Source port of the OCH

cross-connect.
Z-End Port
<shelf/slot/port>
Destination port of the OCH

cross-connect.
Frequency
{9170~9605} for DWDM
The specific channel of the

OCH cross-connect.
{1471~1611} for CWDM

Connection ID
<integer>
OCH Trail Name
<0-60 chars>
Name of the OCH trail that

the OCH cross-connect is a
part of.
Primary State
In Service

state of the OCH
cross-connect.
Out of Service
WK Configuration
Auto
Unkeyed
Manual
Specifies whether the wave

keys will be automatically
selected by the NE or
manually entered by the user.
For CWDM cross-connects,
this field is set to Unkeyed.
Direction
Bidirectional
Unidirectional
Indicates whether the

cross-connect is bidirectional
or unidirectional.
Create
Displays the Create OCH

Cross-Connect window.
Details
Displays the OCH

Cross-Connect Details
window.
A-Z Topology
Displays the Cross Connect

Topology window.
Z-A Topology

Topology window.
A-Z Power

Power Trace window.
Z-A Power

Power Trace window.
....................................................................................................................................................................................................................................
1830 PSS
12-13
Issue 1 June 2013
OCH Cross-Connects
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
A-Z Trace
Displays the Network Power

Trace window.
Z-A Trace
Displays the Network Power

Trace window.
Delete
Deletes the OCH

cross-connect.
....................................................................................................................................................................................................................................
1830 PSS
12-14
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Connection Attributes
Frequency
{9170~9605} for DWDM

{1471~1611} for CWDM
The specific channel of the

OCH cross-connect.
A-End Port
<shelf/slot/port>
Source port of the OCH

cross-connect.
Z-End Port
<shelf/slot/port>
Destination port of the OCH

cross-connect.
OCH Trail Name
<0-60 chars>
Name of the OCH trail that

the OCH cross-connect is a
part of.
Direction
Bidirectional

cross-connect is bidirectional
or unidirectional.
Unidirectional
Protection Mode
Unprotected
Protection
Working
Primary State
In Service
Out of Service
Indicates if the cross-connect

is on the working or
protection path of the OCH
trail, or if there is no
protection.
state of the OCH
cross-connect.
Wave Key Attributes

Wave Key Configuration
Auto
Unkeyed
Manual
Specifies whether the wave

keys will be automatically
selected by the NE or
manually entered by the user.
For CWDM cross-connects,
this field is set to Unkeyed.
A-Z Wave Key 1

A-Z Wave Key 2
{0-4096}
Wave keys for the A-Z

direction of the cross-connect.
NOTE:For Auto and
Unkeyed cross-connects, this
field is read-only.
....................................................................................................................................................................................................................................
1830 PSS
12-15
Issue 1 June 2013
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Z-A Wave Key 1
{0-4096}
Wave keys for the Z-A

direction of the cross-connect.
Z-A Wave Key 2
NOTE: For Auto and

Unkeyed cross-connects, this
field is read-only.
A to Z User Technology
Z to A User Technology
Bit Rate
Unassigned; {1-9000, 9998}
The bit rate in Gbps.
Encoding
Unassigned; {1-9000, 9998}
The type of
encoding/modulation.
....................................................................................................................................................................................................................................
1830 PSS
12-16
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to create an OCH cross-connect group.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Connections > OCH Cross Connect Groups.

Result: The OCH Cross-Connect Groups screen is displayed.
...................................................................................................................................................................................................
Click Create.
Result: The Create OCH Cross-Connect Group screen is displayed.
...................................................................................................................................................................................................
Provision the Connection attributes by selecting the appropriate A-End port, Z-End port
details.
...................................................................................................................................................................................................
Enter a OCH Trail Name.

...................................................................................................................................................................................................
Select the appropriate Direction, Protection Mode, and Admin State from their
respective lists.
...................................................................................................................................................................................................
Select the appropriate frequencies from the list for Frequency 1 to Frequency 4. The
available frequency range is 9170 ~ 9605.
...................................................................................................................................................................................................
Select the appropriate Wavekey configuration.

...................................................................................................................................................................................................
For the A-Z/Z-A User technology, select the appropriate Bit Rate and Encoding values.
Note: Z-A is enabled only if the Cross-connect is Bidirectional.
....................................................................................................................................................................................................................................
1830 PSS
12-17
Issue 1 June 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click Apply to create the OCH cross-connect group.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-18
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision ODUk cross-connects.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Connections > ODUk Cross Connects.

Result: ODUk cross-connects are displayed. The following cross-connect options are
available: Create, Details, Delete..
Note: ODUk cross connects need to all be built the same way. (client to line,
relative to A to Z) on all client to line ports of the same MUX card.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-19
Issue 1 June 2013
ODUk Cross-Connects
....................................................................................................................................................................................................................................
ODUk Cross-Connects
Attribute
Values/Format
Additional Info
A-End
<ODU facility ID>
Source facility of the ODUk

cross-connect.
Z-End
<ODU facility ID>
Destination facility of the

ODUk cross-connect.
Rate
ODU0
ODU rate of the ODUk

cross-connect.
ODU1
ODU2
ODU2e
ODU4
ODUflex 3GSDI
ODUflex FC400
OPTSG
Name
<0-60 chars>
The user-specified name for

this cross-connect.
Direction
Bidirectional
Indicates the direction of the

ODUk cross-connect.
Unidirectional
Protection Mode
Unprotected (default)
Working
Protection

protection path, or if there is
no protection.
Create

cross-connect.
Details
Displays details of a selected

cross-connect.
Delete
Deletes the selected

cross-connect.
....................................................................................................................................................................................................................................
1830 PSS
12-20
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
A-End
<ODU facility ID>
Source facility of the ODUk

cross-connect.
Z-End
<ODU facility ID>
Destination facility of the

ODUk cross-connect.
Rate
ODU0
ODU rate of the ODUk

cross-connect.
ODU1
ODU2
ODU2e
ODU4
ODUflex 3GSDI
ODUflex FC400
OPTSG
Name
<0-60 chars>
The user-specified name for

this cross-connect.
Direction
Bidirectional

ODUk cross-connect.
Unidirectional
....................................................................................................................................................................................................................................
1830 PSS
12-21
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to provision EVPL connections.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Connections > EVPL > FullRate or Connections > EVPL > SubRate
and QinQ.
Result: The EVPL Connections window is displayed.
...................................................................................................................................................................................................
Select Create.
Result: The Create EVPL Connection window is displayed.
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-22
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
A-End Port
<shelf/slot/port>
Source port of the Ethernet

Virtual Private Line (EVPL).
A-End VTS
{1-10}
Virtual time slot within the

A-end port.
Z-End Port
<shelf/slot/port>
Destination port of the EVPL.
Z-End VTS
{1-10}
Virtual time slot within the

Z-end port.
Create 2nd Connection in

Reverse Direction
Automatically creates another

unidirectional EVPL with the
Source and Destination ports
reversed.
....................................................................................................................................................................................................................................
1830 PSS
12-23
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Connection Name
<0-60 chars>
Name of the EVPL

connection.
A-End Port
<shelf/slot/port>

A-End VTS
{1-10} for client port

{1-32} for line port
Indicates the virtual time slot

within the line port.
Z-End Port
<shelf/slot/port>
Z-End VTS


Direction
Bidirectional
Unidirectional

EVPL connection. If the
Operational Mode field is set
to 11DPE12: SubRate, the
Direction is Bidirectional.
If the Operational Mode field
is set to 11DPE12(E): QinQ,
Direction is Unidirectional.
Primary State
CIR (Mbps}
PIR (Mbps)
In Service
Out of Service

state of the EVPL connection.
Default: 100
Committed Information Rate
Range: {0-1000} Mbps
100 Mbps granularity
Default: 1000
Excess Information Rate
100 Mbps granularity
EIR must be greater than or

equal to CIR.
....................................................................................................................................................................................................................................
1830 PSS
12-24
Issue 1 June 2013
....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
PBS (Kbytes)
16
Committed Burst Size
32
64
128
256 (default)
512
1024
2048
4096
8192
16384
EBS (Kbytes)
16
Excess Burst Size
32
EBS must be greater than or

equal to CBS.
64
128
256
512
1024
2048
4096 (default)
8192
16384
....................................................................................................................................................................................................................................
1830 PSS
12-25
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Connection Name
<0-60 chars>
Name of the EVPL

connection.
A-End Port
<shelf/slot/lag>

A-End VTS


{1-10} for LAG
Z-End Port
<shelf/slot/lag>
Z-End VTS


{1-10} for LAG
Direction
Unidirectional

EVPL connection.
Primary State
In Service

state of the EVPL connection.
Out of Service
Protection Mode
None
Protection
Working

protection path, or if there is
no protection.
when the card Operational
Mode is set to QinQ.
CIR (Mbps}
Default: 10
1 Mbps granularity up to
10 Mbps
5 Mbps granularity from

10 Mbps to 100 Mbps

100 Mbps to 1000 Mbps

Committed Information Rate
....................................................................................................................................................................................................................................
1830 PSS
12-26
Issue 1 June 2013
....................................................................................................................................................................................................................................
Attribute
PIR (Mbps)
CBS (Kbytes)
Values/Format
Additional Info
Default: 1000
Excess Information Rate
1 Mbps granularity up to
10 Mbps
PIR must be greater than or

equal to CIR.

10 Mbps to 100 Mbps


16
Committed Burst Size
32
64
128
256 (default)
512
1024
2048
4096
8192
16384
PBS (Kbytes)
16
Excess Burst Size
32
PBS must be greater than or

equal to CBS.
64
128
256
512
1024
2048
4096 (default)
8192
16384
....................................................................................................................................................................................................................................
1830 PSS
12-27
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to Display Cross Connect Topology.

Before you begin
Instructions
Displays a list of the ports that this cross-connect traverses on the NE in the A-Z or Z-A
direction.
...................................................................................................................................................................................................
In the WebUI, select Connections > Cross Connects.

Result: Cross-connects are displayed.
...................................................................................................................................................................................................
Select the cross-connect and click A-Z Topology or Z-A Topology.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-28
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Order
<integer>
Identifies the sequence of

ports in the selected
cross-connect.
Card Name
Type of card.
Port Name
<shelf/slot/port>
Port identifier.
Direction
In

port.
Out
....................................................................................................................................................................................................................................
1830 PSS
12-29
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to display the NE power trace.

Before you begin
Instructions
Note: NE power trace is not applicable for CWDM cross-connects.

For a selected cross-connect, the WebUI will graphically display the ports and associated
power levels across the NE. Two different graphs will be supported: one for A-Z direction
and one for Z-A direction.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the cross-connect and click A-Z Power or Z-A Power.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-30
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
{-99 to 11}, where -99 = Off
The expected power

The measured power

Delta (dB)
Difference between Measured

Power and Expected Power
{0-10}

....................................................................................................................................................................................................................................
1830 PSS
12-31
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedure to display network power trace.

Before you begin
Instructions
Note: Network power trace is not applicable for CWDM cross-connects

For the OCH trail of a selected cross connect, the WebUI displays a table with a list of
ports and associated power levels across the network.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the cross-connect and click A-Z Trace or Z-A Trace.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-32
Issue 1 June 2013
Network Power Trace
....................................................................................................................................................................................................................................
Network Power Trace

Attribute
Value/Format
Additional Info
Name of the network element.
Port Name
Port on the network element

where power measurements
are taken.
Card Type
The type of card where the

port resides.
Expected (dBm)
{-40 to 11}
Measured (dBm)
The expected power

The measured power
{0-5}

....................................................................................................................................................................................................................................
1830 PSS
12-33
Issue 1 June 2013
Procedure 12-10: Connect Alcatel-Lucent 1830 PSS-1 to

1830 PSS-32/PSS-16/PSS-32S
....................................................................................................................................................................................................................................
Procedure 12-10: Connect Alcatel-Lucent 1830 PSS-1 to 1830

PSS-32/PSS-16/PSS-32S
When to use
Use the following procedure to connect Alcatel-Lucent 1830 PSS-1 to 1830

PSS-32/PSS-16/PSS-32S.
Before you begin
Instructions
On the PSS-32, the 11STAR1 client port needs to be provisioned as follows from PhM:
...................................................................................................................................................................................................
In the Inventory view:
Assign the port to = OTU2

Provision the Domain Edge = false
Provision GCC to = enable
Provision the ITU = X (one of 8 CWDM channels)
Provision FEC = g709FEC

Provision OTU Rate = otm11G096
...................................................................................................................................................................................................
In the Topology view:
provision an external connection from the 11STAR client port to the 1/7/X (where X
is 1 for line 1 and 2 for line 2)
...................................................................................................................................................................................................
Put the admin state to up, or up AINS.

...................................................................................................................................................................................................
On the PSS-1 using the WebUI:
Select the line port

Under the OTU provisioning set the gcc enabled
Set the FEC to RSFEC

Set the channel if necessary or to auto, and it will detect the CWDM wavelength.
....................................................................................................................................................................................................................................
1830 PSS
12-34
Issue 1 June 2013

1830 PSS-32/PSS-16/PSS-32S
....................................................................................................................................................................................................................................
Provision the external topology connection to connect the Line port to the 1/X/2
where X is slot of the 11STAR
Provision the admin state to up
Result: Once this is done you should be able to ping the PSS-1 through the PSS-32s.
This would also work if the PSS-1 is the IPGNE and you would be able to ping the
PSS-32 from the PSS-1.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
12-35
Issue 1 June 2013

1830 PSS-32/PSS-16/PSS-32S
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
12-36
Issue 1 June 2013
13
13 traffic maintenance
TDM
procedures
Overview
Purpose
This chapter describes the TDM maintenance procedures.

Contents
Procedure 13-1: Configure port loopback
13-2
13-7
Procedure 13-3: View loopback
13-9
View Loopback
13-10
...................................................................................................................................................................................................................................
1830 PSS
13-1
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to perform a loopback on a TDM port.

Note: Loopbacks affect the traffic on the facility involved in a loopback. Therefore, a
loopback should not set on a facility that is expected to support live traffic or operate
as a member of a protection group. In the case of a loopback on a protection group
member, you have to ensure that the traffic will not switch to the looped back facility
since the looped back facility has been removed from service, is assumed to be under
test, and not carrying either valid traffic or overhead.
Note that a properly implemented terminal loopback will overwrite all ingress data in
both transparent and non transparent (e.g. AIS insertion) applications. Therefore
ingress signal and overhead monitoring during a terminal loopback cannot be
assumed to be reliable.
Attention: Do not use loopback when live traffic could get impacted especially in
combination with network protection schemes.
Terminal loopback on I/O card ports
When having established a terminal loopback on a port of an I/O card this loop only
works if there is at least one XFP/SFP provisioned and plugged for any port within the
portgroup of the looped port.
Note: It is not necessary that the port where the loopback is established itself has an
XFP/SFP plugged.
Data links and loopback switching
The following types of loopback are supported for the OTH-TDM technology:
Facility loopback on an OTU facility - with or without AIS consequent action enabled
downstream
Terminal loopback on an OTU facility - with or without AIS consequent action
enabled downstream
Facility and terminal loopback on Data Links of class DROP
Facility and terminal loopback switching is supported without restrictions on OTU

facilities assigned as supporting facilities to Data Links of class DROP.
facilities connected to HO ODU termination facilities assigned as supporting facilities to
Data Links of class DROP.
....................................................................................................................................................................................................................................
1830 PSS
13-2
Issue 1 June 2013
....................................................................................................................................................................................................................................
Depending on the type of loopback switched and on the fact, whether consequent action
downstream is enabled or not, a loopback switched on a facility will cause specific traffic
outages. As, however, traffic outages on DROP side in general shall not influence CP
behavior, no related requirements are needed for loopbacks on CP side.
Facility and terminal loopback on Data Links of class INNI

facilities assigned as supporting facilities to Data Links of class INNI.
In case of a Data Link of class INNI having Maintenance Mode not set consistently for
this Data Link in both related adjacent nodes, the following behavior is guaranteed:
Switching of a loopback on an OTU facility assigned as supporting facility for this

Data Link in one of the adjacent nodes leads to any service via this Data Link affected
by the loopback being restored or set to the failed state in the usual way according to
its protection type.
Release of a loopback switched before on an OTU facility assigned as supporting
facility for this Data Link in one of the adjacent nodes leads to any affected service
via this Data Link affected by the loopback being restored or set to the failed state
before it is reverted to the original state in the usual way.
It is assumed that this behavior is fulfilled automatically using usual INNI Data Link
supervision via TCM entities, if dTIM and dBDI are included as trigger for Fast Defect
Reporting on INNI Data Links.
Note: In case of a Data Link having Maintenance Mode set consistently in both
related nodes, loopback switching on one or both of the related OTU facilities
assigned as supporting facility for this Data Link will not cause any consequences for
services via this Data Link. This is due to the properties defined for the Maintenance
Mode.
OPR-LPBK-OC192
OPR-LPBK-OC48
OPR-LPBK-OC12
OPR-LPBK-OC3
OPR-LPBK-OTU
OPR-LPBK-STMN
....................................................................................................................................................................................................................................
1830 PSS
13-3
Issue 1 June 2013
....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
Important! If you want to switch a facility loopback on a port involved in a Line

protection scheme (Line protection), it is highly recommended to put the
corresponding protection group in the lockout or forced switch state before switching
the facility loopback to avoid an unintended protection switch or failure of protocol
(FOP) events.
...................................................................................................................................................................................................
Make sure that the port on which you want to operate a facility loopback is not
assigned/locked as timing reference, and that no DCC is enabled for that port.
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select Facilty OC OC

Additional info The following facilities can be selected:
OC48-1-<shelf>-<slot>-{1-24} (OC-48 on a 24XANYMR)

OC12-1-<shelf>-<slot>-{1-24} (OC12 on a 24XANYMR)
OC192-1-<shelf>-<slot>-<port> (OC192 on a 10G ANY Multiport Card)
OC3-1-<shelf>-<slot>-{1-24} (OC3 on a 24XANYMR)
STM1-1-<shelf>-<slot>-{1-24} (STM1 on a 24XANYMR)

STM64-1-<shelf>-<slot>-<port> (STM64 port on a 10G ANY Multiport Card)
OTU-1-<shelf>-<slot>-{1} (OTU4 on a 130SCUP)

OTU-1-<shelf>-<slot>-{1,2} (OTU3 on a 2XANY40G)
OTU-1-<shelf>-<slot>-{1} (OTU3E2 on a 43SCUP)
OTU-1-<shelf>-<slot>-<port> (OTU2 on a 10G ANY Multiport Card)

OTU-1-<shelf>-<slot>-<port> (OTU2E on a 10G ANY Multiport Card)
....................................................................................................................................................................................................................................
1830 PSS
13-4
Issue 1 June 2013
....................................................................................................................................................................................................................................
OTU-1-<shelf>-<slot>-{1-4} (OTU2 on a 11QCUP)

OTU-1-<shelf>-<slot>-{1-4} (OTU2E on a 11QCUP)
Note: When setting up a terminal loopback on an STM-64, OC192, OTU2 or OTU2E

port on a 10G ANY Multiport Card with AIS-insertion enabled (i.e. CA=Y) the signal
is looped as expected. However, the signal transmitted at the OTU2/OTU2E port is
not replaced by OTU-AIS.
...................................................................................................................................................................................................
Select the entity for which you want to configure port loopback.
Note: The port must be in the OOS-[AI]MA state to perform a loopback. Otherwise
the Operate menu will be disabled
...................................................................................................................................................................................................
Then select Loopback Operate, either by selecting Action from the main menu bar or
Result: The Operate Loopback window opens.
...................................................................................................................................................................................................
By means of the read-only field AID, verify that you selected the desired port,.
...................................................................................................................................................................................................
Select the location, in which the loopback is to be performed by means of the Location
drop-down list box.:
NEND
Near End
No value .
...................................................................................................................................................................................................
Define whether a consequent action is performed in the context of loopback switching, by

means of the LPBKCONSACT drop-down list box:
Insert AIS
Consequent Action is enabled and therefore AIS is inserted into downstream direction
after looping the signal.
Don't insert AIS
Consequent Action is disabled and therefore the signal continues after the loop in
downstream direction without an AIS indication.
...................................................................................................................................................................................................
Select the Loopback Type, by means of the Loopback Type drop-down list box.:
FACILITY
....................................................................................................................................................................................................................................
1830 PSS
13-5
Issue 1 June 2013
....................................................................................................................................................................................................................................
Specifies a loopback at the receive side (from the network) to the transmit side (to the
network) of the specified facility.
TERMINAL .
Specifies a loopback where the signal that is about to be transmitted is connected to

the associated incoming receiver.
...................................................................................................................................................................................................
Important! Operating a facility loopback may be service affecting!

Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
13-6
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to releases a loopback previously established on a particular TDM

port.
RLS-LPBK-OC3
RLS-LPBK-OC12
RLS-LPBK-OC48
RLS-LPBK-OC192
RLS-LPBK-OTU
RLS-LPBK-STMN
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

...................................................................................................................................................................................................
Select the entity for which you want to release port loopback.
...................................................................................................................................................................................................
Then select Loopback Release, either by selecting Action from the main menu bar or
Result: The Release Loopback window opens.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
13-7
Issue 1 June 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the location, in which the loopback is operating by means of the Location
NEND
Near End
No value .
...................................................................................................................................................................................................
FACILITY
TERMINAL .

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
13-8
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve the TDM ports that are in a loopback within the specified
range of OC-. AIDs.
RTRV-LPBK-OC192
RTRV-LPBK-OC48
RTRV-LPBK-OC12
RTRV-LPBK-OC3
RTRV-LPBK-OTU
RTRV-LPBK-STMN
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

...................................................................................................................................................................................................
...................................................................................................................................................................................................
Then select Loopback View, either by selecting Action from the main menu bar or by
Result: The View Loopback window opens.
See .View Loopback (p. 13-10)

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
13-9
Issue 1 June 2013
View Loopback
....................................................................................................................................................................................................................................
View Loopback
Purpose
The View Loopback window can be used to request information whether a particular
TDM port is involved in a loopback.
Loopback information
For each TDM port that is involved in a loopback, the following information is displayed:
Parameter
Value
Description
Name
for example OC192-{1-7}-{1-9}{1-16,33-48}-{1-10} ANSI

(OC192 on a 10XANY10G)
The access identifier (AID) of the

TDM port (see also Overview of
access identifiers (p. 5-548)).
Location
Near End
The location in which the loopback

is performed.
Loopback Type
FACILITY,
The type of loopback:
TERMINAL
FACILITY specifies a loopback at

the receive side (from the
network) to the transmit side (to
the network) of the specified
facility.
TERMINAL specifies a loopback
where the signal that is about to

be transmitted is connected to
the associated incoming
receiver.
Consequent Action
Yes (Consequent Action is
enabled; CSF (Client Signal Fail)

inserted in downstream
direction),
specifies whether a consequent

action is performed in the context of
loopback switching.
No (Consequent Action is
disabled; Signal is continued in
downstream direction)
....................................................................................................................................................................................................................................
1830 PSS
13-10
Issue 1 June 2013
14
14 traffic maintenance
WDM
procedures
Overview
Purpose
This chapter describes the WDM maintenance procedures.

Contents
Loopbacks
14-2
Procedure 14-1: Display, set, release loopbacks
14-4
Port Loopback Control
14-6
...................................................................................................................................................................................................................................
1830 PSS
14-1
Issue 1 June 2013
Loopbacks
....................................................................................................................................................................................................................................
Loopbacks
Overview
Loopbacks are typically used in a process of installation, system maintenance and

troubleshooting. The basic idea is to allow the user to test the circuit or isolate the failure
by connecting the test equipment to the system interface and creating the loopback at
different points in the transmission path. Loopbacks aid in the process of troubleshooting
by isolating segments of the transmission path and associating the addition/removal of a
monitored segment with presence of a failure.
The two basic types of loopbacks (depicted in Figure 14-1, Loopback Types (p. 14-3))
are:
Line (Facility) loopbacks - The received optical external transmission signal on the
target facility is capable of being looped from the port function input back toward the
port function output. It is permissible to loopback the electrical signal of the optical
interfaces as opposed to the optical signal. Each interface of a multiple interface port
function is capable of being looped back independently.
Terminal loopbacks - The electrical transmission signal on an optical interface port
function is capable of being looped from the port function output back toward the port
function input. Port functions include optical interfaces at various rates. The
placement of the terminal loopback on any particular port function is a compromise
between having the loopback be as close as possible to the physical interface and
having the terminal loopback support transparent data flow.
Note: Line terminal loopback release can take several minutes for traffic to recover
(10 minute maximum).
Note: Terminal and facility loopbacks are supported on all OT line and client ports
(not VA ports) with the exception of the 43STA1P client port.
Note: When a line facility loopback is established on an 11STAR1 OT pack, there is a
30 second delay from initiating the loopback to when it comes into effect. The reason
for this delay is because establishing the loopback requires changing the line-side PLL
settings, and it takes about 30 seconds for the PLL to lock after its settings have been
changed. The same 30 second delay applies to removing the line facility loopback.
Note: 11STMM10 line facility loopback terminates OTU2 and ODU2 overhead.
There is a lack of transparency with this type of loopback.
Note: To apply a loopback to a port it must first be set into Maintenance mode. This is
a safeguard that prevents the user from accidentally applying a loopback and
interrupting traffic. In order to put a network (line) port into maintenance, all of the
client ports associated with it must be in maintenance or admin down. Also, when a
port is in maintenance, it will flash green and any alarms that were present become
conditions.
....................................................................................................................................................................................................................................
1830 PSS
14-2
Issue 1 June 2013
Loopbacks
....................................................................................................................................................................................................................................
Figure 14-1 Loopback Types
....................................................................................................................................................................................................................................
1830 PSS
14-3
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use the following procedures to display, set, and release loopbacks.

Before you begin

Note: To apply a loopback to a port it must first be set into Maintenance mode. This is
a safeguard that prevents the user from accidentally applying a loopback and
interrupting traffic. In order to put a network (line) port into maintenance, all of the
client ports associated with it must be in maintenance or admin down. Also, when a
port is in maintenance, it will flash green and any alarms that were present become
conditions.
Enable loopback
...................................................................................................................................................................................................
From the WebUI, expand the equipment tree in the left pane to select the card and port for
loopback. Left click the port. Select the Provision/Info function.
...................................................................................................................................................................................................
In the Primary State field, select Maintenance from the drop-down list. Click Submit.
Note: the Maintenance option will not appear for a Line port until all associated
Client ports are in Maintenance state.
...................................................................................................................................................................................................
Select the Test/Analysis function for the port. Provision the loopback as desired. A green
checkmark in the box means the loopback is Enabled. Click Submit.
...................................................................................................................................................................................................
A warning message will appear that Enabling loopback will affect any service on the port.
Click OK.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
14-4
Issue 1 June 2013
....................................................................................................................................................................................................................................
Disable loopback and remove from maintenance mode.
Note: After performing all necessary maintenance procedures, you should disable the
loopback and remove the ports from Maintenance mode.
...................................................................................................................................................................................................
From the WebUI, expand the equipment tree in the left pane to select the card and port for
loopback. Left click the port.
...................................................................................................................................................................................................
Select the Test/Analysis function for the port. Remove the loopback as desired. A blank
box means the loopback is Disabled. Click Submit.
...................................................................................................................................................................................................
Select the Provision/Info function. In the Primary State field, select In-Service/AINS
or In-Service from the drop-down list. Click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
14-5
Issue 1 June 2013
....................................................................................................................................................................................................................................

Attribute
Additional Info
Facility Loopback Enabled
Select to request a facility loopback on the

port. Only one loopback (facility or terminal)
may be set on a port at any given time.
Deselect to disable an existing facility
loopback on the port.
Terminal Loopback Enabled
Select to request a terminal loopback on the

port. Only one loopback (facility or terminal)
may be set on a port at any given time.
Deselect to disable an existing terminal
loopback on the port.
Test Signal Loopback Enabled
Select to request a test signal loopback on the

port. Only one loopback may be set on a port
at any given time. Deselect to disable an
existing terminal loopback on the port.
112SA1L and 112SCA1 client ports only.
....................................................................................................................................................................................................................................
1830 PSS
14-6
Issue 1 June 2013
15
15 Ethernet/Data traffic
TDM
maintenance procedures
Overview
Purpose
This chapter describes the Ethernet/data traffic maintenance procedures.

Contents
15-2
Procedure 15-2: Release loopback
15-5
15-7
15-8
...................................................................................................................................................................................................................................
1830 PSS
15-1
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to perform a loopback on a particular 1 Gigabit Ethernet or 10 Gigabit

Ethernet port.
Note: Loopbacks affect the traffic on the facility involved in a loopback. Therefore, a
loopback should not set on a facility that is expected to support live traffic or operate
as a member of a protection group. In the case of a loopback on a protection group
member, you have to ensure that the traffic will not switch to the looped back facility
since the looped back facility has been removed from service, is assumed to be under
test, and not carrying either valid traffic or overhead.
Note that a properly implemented terminal loopback will overwrite all ingress data in
both transparent and non transparent (e.g. AIS insertion) applications. Therefore
ingress signal and overhead monitoring during a terminal loopback cannot be
assumed to be reliable.
Important! Do not use loopback when live traffic could get impacted especially in
combination with network protection schemes.
OPR-LPBK-GBE
OPR-LPBK-GBE10
Before you begin

Required equipment
....................................................................................................................................................................................................................................
1830 PSS
15-2
Issue 1 June 2013
....................................................................................................................................................................................................................................
Instructions
Important! If you want to switch a facility loopback on a port involved in a Line

protection scheme (Line protection), it is highly recommended to put the
corresponding protection group in the lockout or forced switch state before switching
the facility loopback to avoid an unintended protection switch or failure of protocol
(FOP) events.
...................................................................................................................................................................................................
Make sure that the port on which you want to operate a facility loopback is not
assigned/locked as timing reference, and that no DCC is enabled for that port.
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select Facility GBE GBE-Facility
...................................................................................................................................................................................................
Select the entity for which you want to configure port loopback.
...................................................................................................................................................................................................
Then select Loopback Operate, either by selecting Action from the main menu bar or
Result: The Operate Loopback window opens.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the location, in which the loopback is to be performed by means of the Location
NEND
Near End
No value .
...................................................................................................................................................................................................
FACILITY
TERMINAL .

....................................................................................................................................................................................................................................
1830 PSS
15-3
Issue 1 June 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select if Consequent Action is enabled, by means of the Consequent Action drop-down

list box.:
Insert CSF
Consequent Action is enabled; CSF (Client Signal Fail inserted in the downstream
direction
Dont insert CSF .
Consequent Action is disabled; Signal is continued in downstream direction

...................................................................................................................................................................................................
Important! Operating a facility loopback may be service affecting!

Click Apply.
Result: Facility loopback is operated.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
15-4
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to releases a loopback previously established on a particular 1 Gigabit

Ethernet or 10 Gigabit Ethernet port.
RLS-LPBK-GBE10
RLS-LPBK-GBE
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select Facilty GBE GBE-Facilty
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Then select Loopback Release, either by selecting Action from the main menu bar or
Result: The Release Loopback window opens.
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the location, in which the loopback is operating by means of the Location
NEND
....................................................................................................................................................................................................................................
1830 PSS
15-5
Issue 1 June 2013
....................................................................................................................................................................................................................................
Near End
No value .
...................................................................................................................................................................................................
FACILITY
TERMINAL .

...................................................................................................................................................................................................
Click Apply.
Result: The loopback is released.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
15-6
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve the GBE/GBE10 facilities that are in a loopback within the
specified range of GBE/GBE10 AIDs.
RTRV-LPBK-GBE
RTRV-LPBK-GBE10
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select Facilty GBE GBE-Facilty
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Then select Loopback View, either by selecting Action from the main menu bar or by
Result: The View Loopback window opens.
See . The View Loopback window (p. 15-8)

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
15-7
Issue 1 June 2013
....................................................................................................................................................................................................................................

Purpose
The View Loopback window can be used to request information whether a particular
1 Gigabit Ethernet or 10 Gigabit Ethernet port is involved in a loopback.
Loopback information
For each 1 Gigabit Ethernet or 10 Gigabit Ethernet port that is involved in a loopback, the
following information is displayed:
Parameter
Value
Description
AID
for example GBE10-{1}-{1-31}{1-16,33-48}-{1-10}} (GBE10

port on a 10XANY10G module)
The access identifier (AID) of the

Gigabit Ethernet port (see also
(p. 5-548)).
Location
Near End
The location in which the loopback

is performed.
Loopback Type
FACILITY,
The type of loopback:
TERMINAL
FACILITY specifies a loopback at

the receive side (from the
network) to the transmit side (to
the network) of the specified
facility.
TERMINAL specifies a loopback
where the signal that is about to

be transmitted is connected to
the associated incoming
receiver.
Consequent Action
Insert CSF (Consequent Action is
enabled; CSF (Client Signal Fail)

inserted in downstream
direction),
specifies whether a consequent

action is performed in the context of
loopback switching.
Dont insert CSF (Consequent
Action is disabled; Signal is

continued in downstream
direction)
....................................................................................................................................................................................................................................
1830 PSS
15-8
Issue 1 June 2013
16
16
Performance
monitoring
procedures
Overview
Purpose
This chapter describes the performance monitoring process and the procedures for
configuring the performance monitoring (PM) functions of Alcatel-Lucent 1830 PSS
systems.
Contents
16-3
16-6
Performance measurements
16-8
SES declaration threshold
16-15
Thresholding
16-17
16-25

16-27
16-27
16-38
Procedure 16-1: Enable or disable PM data collection
16-39
Procedure 16-2: Retrieve PM activation status
16-43
Procedure 16-3: Retrieve PM data
16-47
16-52
16-55
16-58
16-61
Procedure 16-8: Modify the threshold settings of a TCA profile
16-63
...................................................................................................................................................................................................................................
1830 PSS
16-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Procedure 16-9: Retrieve the threshold settings of a TCA profile
16-65
Procedure 16-10: Delete a TCA profile
16-66
16-67
16-68
Procedure 16-12: Display PM data for EC/MTC1T9 card
16-69
PM Data [Card]
16-70
16-72
Clear Bins [Card]
16-73
16-74
16-75
Procedure 16-15: Modify TCA profile
16-76
16-77
PM Data
16-78
Procedure 16-17: Set bins for port
16-80
Clear Bins
16-81
Procedure 16-18: Set baseline values for port
16-82
Port Baseline
16-84
16-86
Configuration parameters related to performance monitoring
16-87
PM reports General
16-89
PM reports SDH Regenerator Section
16-92
16-93
16-94
16-95
PM reports Ethernet
16-96
16-97
PM reports ODUk Path
16-98
16-99
16-100
....................................................................................................................................................................................................................................
1830 PSS
16-2
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
The purpose of performance monitoring is:

1. to detect degraded performance of the transport functionality to support pro-active
maintenance activities, for example replacing equipment before the impact of the
performance degradation on service becomes unacceptable (maintenance-oriented
performance monitoring).
2. to collect performance data over a long period (typically months) in order to verify the
quality of the transport service (quality-of-service-oriented performance monitoring).
Near-end and far-end performance monitoring
In principle, two kinds of performance monitoring can be distinguished:
Near-end performance monitoring

Performance parameters are derived from bit errors and defects in the incoming
signal.
Far-end performance monitoring

Performance parameters are derived from the remote information (REI/RDI) in the
incoming signal. The meaning of the remote information will be explained in more
detail afterwards in this chapter.
Performance monitoring of a bidirectional path
To monitor the performance of a bidirectional path, near-end and far-end performance

monitoring information is correlated. The bidirectional path is considered unavailable if at
least one of the directions is unavailable.
Figure 16-1 Performance monitoring of a bidirectional path (example)
NE A
NE B
NE I
REI
RDI
REI
RDI
TTP
NE Z
CTP
CTP
TTP
....................................................................................................................................................................................................................................
1830 PSS
16-3
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
At NE A, the near-end information represents the performance of the unidirectional trail

from NE Z to NE A, while the far-end information represents the performance of the
unidirectional trail from NE A to NE Z.
At NE Z, the near-end information represents the performance of the unidirectional trail
from NE A to NE Z, while the far-end information represents the performance of the
unidirectional trail from NE Z to NE A.
At an intermediate NE I, the near-end information in the direction from NE A to NE Z
represents the performance of the unidirectional trail segment from NE A to NE I, while
the far-end information represents the performance of the unidirectional trail from NE Z
to NE A. The near-end information in the direction from NE Z to NE A represents the
performance of the unidirectional trail segment from NE Z to NE I, while the far-end
information represents the performance of the unidirectional trail from NE A to NE Z.
At either end of the trail (NE A or NE Z) the combination of near-end and far-end
information represents the performance of the two directions of the trail. At an
intermediate NE I, the combination of far-end information in the trail signal from NE A to
NE Z and far-end information in the trail signal from NE Z to NE A presents the
performance of the two directions of the trail.
Selection between SDH and SONET behavior
The selection between SDH and SONET behavior of performance monitoring is made by
setting the REGION parameter.
The REGION parameter can take on one of the following values:
ANSI - corresponds to SONET behavior
ETSI - corresponds to SDH behavior
Depending on that SDH/SONET selection, there is a different behavior regarding

performance monitoring and thresholding.
Note: Enabling/disabling performance monitoring and setting TCA for Ethernet and
OTH is depending on the setting of the REGION parameter.
Bit errors and block errors
A distinction has to be made between SDH and SONET concerning the underlying
performance monitoring concepts. SDH performance monitoring is based on the
evaluation of block errors while SONET performance monitoring is based on the
evaluation of bit errors (code violations).
....................................................................................................................................................................................................................................
1830 PSS
16-4
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................
SDH performance monitoring
SDH performance monitoring is based on the evaluation of block errors, where the block
size depends on the transmission layer. At the Regenerator Section (RS) layer, a block is
equivalent in size to an SDH frame. Therefore, the number of bits in an RS block is
dependent on the signal rate. One or more errored bits in the RS parity byte (B1 byte in
the RSOH) constitutes a single RS block error.
SONET performance monitoring
In SONET performance monitoring, at the transmission layers (section) a bit-interleaved

parity (BIP) word is calculated at the transmitter and forwarded downstream to the
receiver. At the receive side, the BIP is re-calculated and compared on a bit-by-bit basis
with the BIP received from the transmit side. The number of mismatches between the
re-calculated BIP and the BIP received is the code violations (CV) count.
OTH performance monitoring
OTH performance monitoring is based on the evaluation of block errors, where the block
size depends on the transmission layer. Block errors are detected by means of a
bit-interleaved parity-8 (BIP-8) code.
At the OTUk Section layer, one or more errored bits in the Section Monitoring (SM) field
of the OTUk Section Overhead constitutes a single block error. At the ODUk path layer,
one or more errored bits in the Path Monitoring (PM) field of the ODUk Path Overhead
constitutes a single block error.
Contents
16-6
16-8
16-15
Thresholding
16-17
16-25
....................................................................................................................................................................................................................................
1830 PSS
16-5
Issue 1 June 2013

....................................................................................................................................................................................................................................

Process description
The performance monitoring process is a three-stage process:
Primary processing
Parameter processing
Binning and reporting
Figure 16-2 Performance monitoring process

Multiplex section,
line
Regenerator section,
section
Primitive
processing
Event
processing
Binning
and
reporting
Path
g-upg-0010
Primary processing
Fundamental parameters are derived from errors detected in the transport signal,
classified into bit errors and defects, and accumulated over one-second periods.
Parameter processing
Performance parameters are calculated based on the evaluation and correlation of the
fundamental parameters obtained during the primary processing. Please also refer to
Performance parameters (p. 16-9) .
Binning and reporting
In the binning and reporting phase, the performance parameters obtained during the
parameter processing are accumulated in registers over measurement periods of 15
minutes and 1 day. The collection of registers associated to a monitoring point and
accumulation period is called a bin.
The start of the 15-minutes measurement periods is aligned with the quarter boundaries
(00,15,30, 45) of the NE clock. The 1-day measurement periods start at 00:00 (midnight)
related to UTC.
....................................................................................................................................................................................................................................
1830 PSS
16-6
Issue 1 June 2013

....................................................................................................................................................................................................................................
Counting is done in current bins. At the end of the measurement period the bin is kept in
store as the first recent bin. In case more than one past measurement period is kept in
store, that entire collection is called the history bins. The first recent bin is also called
previous bin.
For each performance monitoring point (see Performance measurements (p. 16-8)), the
following bins exist:
Table 16-1
Performance monitoring - Available bins
Types of bins
Number of 15-minutes bins
Number of 1-day bins
Current bins
Previous
Recent
31
History bins
At the end of each 15-minutes boundary, the contents of the current 15-minutes bin is
transferred to the previous 15-minutes bin. The current 15-minutes bins are then
automatically initialized to zero.
The 31 recent 15-minutes bins are stored in a first-in-first-out (FIFO) manner. At the end
of each 15-minutes boundary, the content of the previous bin is transferred to the recent
bins. When the storage capacity of 31 recent 15-minutes bins is reached, then with each
additional recent bin, the oldest of the existing recent bins is dropped. The 31 recent
15-minutes bins thus always contain the 31 most recent 15-minutes PM data.
Analogously, the same applies to the recent 1-day bins.
Effect of changing the NE time
When the time-of-day setting in the NE is changed, then the collection of PM counts in
each of the current 15-minutes and 1-day bins continues uninterruptedly. However, the
end time associated with the current bin will be changed according to the new time.
Important! Changing the date and time of the system may result in unreliable PM
data.
PM counts stored in previous and recent bins are not affected by changing the NE time.
....................................................................................................................................................................................................................................
1830 PSS
16-7
Issue 1 June 2013

....................................................................................................................................................................................................................................
Performance monitoring points
Performance monitoring points can be any trail termination point (TTP) or connection
termination point (CTP) in the network element.
Possible TTPs and CTPs are:
Trail termination points (TTPs):

SDH: Regenerator Section Termination (RST),
SONET: Section termination
OTH: OTUk termination and ODUk termination

Connection termination points (CTPs):
OTH: Path monitoring at non-intrusive monitoring (NIM) points.
Autonomous creation and deletion of PM registers
When a facility is created, then, depending on the NE operation mode, the associated PM
registers will be created or not created by default according to the following table:
Table 16-2
Facility
NE operation mode
ANSI
ETSI
SONET Section
No autocreation of PM
registers (PMSTATE = OFF)
SDH RS
SDH/SONET higher order path

- terminated
PM registers autonomously
created and counting
(PMSTATE = ON)
SDH/SONET higher order path

- not terminated (non-intrusive
monitoring)
GbE
(PMSTATE = ON)
OTU
(PMSTATE = ON)
....................................................................................................................................................................................................................................
1830 PSS
16-8
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 16-2
Facility
(continued)
NE operation mode
ODUk non-terminated
(NIM)
ODUk Terminated
(ODUkPTF)
ODUk TCM layer
(both NIM and terminated)
ANSI
ETSI
(PMSTATE = ON)
When a facility is deleted via command or by using autodeletion procedures, all related
PM registers will be deleted.
Performance parameters
These performance parameters are supported by the Alcatel-Lucent 1830 PSS systems:
SDH/SONET near-end performance parameters (p. 16-9)
Ethernet performance parameters (p. 16-10)
OTH performance parameters (p. 16-12)

Note: In Alcatel-Lucent 1830 PSS , far-end performance monitoring is not supported.
SDH/SONET near-end performance parameters
These are the SDH/SONET near-end performance parameters supported by

Alcatel-Lucent 1830 PSS systems:
Table 16-3
Parameter
Errored Seconds (ES)
SDH
SONET
A near-end errored second is a one-second interval with one or more block errors (SDH) or bit errors
(SONET) or one or more defects ( RDI) in the incoming signal.
The ES counter is not incremented during a period of unavailability (see Unavailable Seconds).
Severely Errored Seconds (SES)
A near-end SES is a one-second interval in which the amount of block errors (SDH) or bit errors
(SONET) has exceeded the SES threshold (see SES declaration threshold (p. 16-15)), or in which
at least one defect has been detected ( RDI) in the incoming signal.
The SES counter is not incremented during a period of unavailability (see Unavailable Seconds).
....................................................................................................................................................................................................................................
1830 PSS
16-9
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 16-3
Parameter
Background Block Errors (BBE)
(continued)
SDH
SONET
The BBE count is the accumulated number of block errors not occurring as part of a severely errored
second.
Code Violations (CV)
The CV count is the SONET equivalent to the SDH BBE count.
Unavailable Seconds (UAS)
Near-end UAS determine the period of time during which the transmission route in the receive
direction is in the unavailability state. A period of unavailability begins at the onset of ten
consecutive near-end severely errored seconds. These ten seconds are considered to be part of the
unavailability period (UAP). A new period of availability begins at the onset of ten consecutive
non-severely-errored seconds. These ten seconds are considered to be part of the availability period.
The ES and SES counters are not incremented during a period of unavailability.
Severely Errored Framing Seconds (SEFS)
An SEFS is a second in which frame alignment has temporarily been lost (out-of-frame (OOF)
condition).
Out of Frame Seconds - Near End Regenerator Section (OFS-RS)
An OUFS is a number of one-second intervals containing at least one out-of-frame
error.(out-of-frame (OOF) condition).
Related information
Please also refer to:
Overview of SONET performance parameters (p. 16-13)
SES declaration thresholds SDH (p. 16-15)
SES declaration thresholds SONET (p. 16-15)
Ethernet performance parameters are collected by means of MAC layer monitoring at the
1 GbE and 10 GbE LAN side.
The following Ethernet performance parameters are supported:
Table 16-4
Parameter
Meaning
EINB
Ethernet Incoming Number of Bytes

The EINB counter indicates the number of received bytes in good and bad
frames.
....................................................................................................................................................................................................................................
1830 PSS
16-10
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 16-4
Parameter
Meaning
EONB
Ethernet Outgoing Number of Bytes
(continued)
The EONB counter indicates the number of successfully transmitted bytes.

EINF
Ethernet Incoming Number of Frames

The EINF counter indicates the number of the received good unicast,
multicast and broadcast frames as well as received bad frames.
EONF
Ethernet Outgoing Number of Frames

The EONF counter indicates the number of successfully transmitted
unicast, multicast and broadcast frames.
EIFE
Ethernet Incoming Frame Errors

The EIFE counter indicates the number of errored frames received.
A received frame is counted as errored if it:
EOFE
contains CRC errors
contains alignment errors
is undersized or oversized with or without FCS errors

Note: In case of jumbo frames (1GBE TTT transport over ODU0)
some may be wrongly counted as frames with errors resulting in a too
high frame error count. In case of smaller frames the counts are
unaffected.
has a valid length field not matching the actual frame length
has an invalid length field.
Ethernet Outgoing Frame Errors

The EOFE counter indicates the number of errored frames transmitted.
A transmitted frame is counted as errored if it:
ETH-SYMERR
contains CRC errors
contains alignment errors
is undersized or oversized with or without FCS errors

Note: In case of jumbo frames (1GBE TTT transport over ODU0)
some may be wrongly counted as frames with errors resulting in a too
high frame error count. In case of smaller frames the counts are
unaffected.
has a valid length field not matching the actual frame length
has an invalid length field.
Ethernet Symbol Errors

The ETH-SYMERR counter indicates the number of line code violations.
....................................................................................................................................................................................................................................
1830 PSS
16-11
Issue 1 June 2013

....................................................................................................................................................................................................................................
Notes:
1.
The EINB, EONB, and EINF EONF, counters are rather traffic monitoring counters than
performance monitoring counters, as they monitor the traffic load in the network. The EIFE
and EOFE counter is a real performance monitoring counter as it gives an indication about
the performance of the network.
2.
Because of the difference in units, bytes versus frames, the counters cannot be correlated
with each other.
OTH performance parameters
These are the OTH performance parameters supported by Alcatel-Lucent 1830 PSS
systems:
Table 16-5
Parameter
OTUk
ODUk Path
Section
Errored Seconds (ES)
A near-end errored second is a one-second interval with one or more block errors or one or more
defects (for OTUk Section: LOS, LOF, LOM, TIM-S or AIS; for ODUk Path: OCI, LCK, PLM-P,
TIM-P or AIS) in the incoming signal.
The ES counter is not incremented during a period of unavailability (see Unavailable Seconds).
Severely Errored Seconds (SES)
A near-end SES is a one-second interval in which the amount of block errors has exceeded the
OTUk/ODUk SES threshold (see SES declaration threshold OTH (p. 16-16)), or in which at
least one defect (for OTUk Section: LOS, LOF, LOM, TIM-S or AIS; for ODUk Path: OCI, LCK,
PLM-P, TIM-P or AIS) has been detected in the incoming signal.
The SES counter is not incremented during a period of unavailability (see Unavailable Seconds).
Background Block Errors (BBE)
The BBE count is the accumulated number of block errors not occurring as part of a severely errored
second.
Unavailable Seconds (UAS)
Near-end UAS determine the period of time during which the transmission route in the receive
direction is in the unavailability state. A period of unavailability begins at the onset of ten
consecutive near-end severely errored seconds. These ten seconds are considered to be part of the
unavailability period (UAP). A new period of availability begins at the onset of ten consecutive
non-severely-errored seconds. These ten seconds are considered to be part of the availability period.
The ES and SES counters are not incremented during a period of unavailability.
Forward Error Correction corrected (FECC)
The FECC count is the accumulated number of detected and corrected FEC code violations per
frame.
The FECC counter is not incremented during a period when a LOS, LOF, LOM or AIS defect is
present.
....................................................................................................................................................................................................................................
1830 PSS
16-12
Issue 1 June 2013

....................................................................................................................................................................................................................................
Notes:
1.
The PLM-P defect is only relevant in case the ODUk path is terminated.
2.
See the Alcatel-Lucent 1830 PSS Maintenance and Trouble-Clearing Guide for defect definitions.
Related information
Please also refer to:
Overview of OTH performance parameters (p. 16-14)
SES declaration threshold OTH (p. 16-16)
Overview of SDH performance parameters
The following overview shows the available SDH performance parameters and their
association to the monitoring points Regenerator Section (RS) and higher order path (path
termination and path monitoring at non-intrusive monitoring (NIM) points):
Table 16-6
Parameter
SDH performance parameters

Regenerator Section
Path
ES
ES-RS
ES-HOVC
SES
SES-RS
SES-HOVC
BBE
BBE-RS
BBE-HOVC
UAS
UAS-RS
UAS-HOVC
Notes:
1.
In Alcatel-Lucent 1830 PSS , far-end performance monitoring is not supported.
2.
Please also see PM reports SDH Regenerator Section (p. 16-92), and PM reports
SDH higher order path (p. 16-93).
Overview of SONET performance parameters
The following overview shows the available SONET performance parameters and their
association to the monitoring points Section, Line and path (path termination and path
monitoring at non-intrusive monitoring (NIM) points):
Table 16-7
Parameter

Section
Path
CV
CVS
CVP
ES
ESS
ESP
SES
SESS
SESP
UAS
UASP
....................................................................................................................................................................................................................................
1830 PSS
16-13
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 16-7
Parameter
Section
SEFS
(continued)
Path
SEFSS
Notes:
1.
Please also see PM reports SONET Section (p. 16-94) and PM reports SONET path
(p. 16-95).
Overview of OTH performance parameters
The following overview shows the available OTH performance parameters:

Table 16-8
Parameter
OTUk Section
ODUk Path
ODUk TCM layer
ES
ES-OTU
ES-ODU
ES-TCM
SES
SES-OTU
SES-ODU
SES-TCM
BBE
BBE-OTU
BBE-ODU
BBE-TCM
UAS
UAS-OTU
UAS-ODU
UAS-TCM
FECC
FECC
Notes:
1.
In Alcatel-Lucent 1830 PSS , far-end performance monitoring is not supported.
2.
Please also see PM reports OTUk Section (p. 16-97) and PM reports ODUk Path
(p. 16-98).
....................................................................................................................................................................................................................................
1830 PSS
16-14
Issue 1 June 2013

....................................................................................................................................................................................................................................

Introduction
The SES declaration threshold indicates the number of errored blocks (SDH) or code
violations (SONET) per second that must be exceeded to declare a second severely
errored.
Important! The value of the SES declaration threshold is preset to a meaningful
value (30% of the number of blocks per second) and cannot be changed.
SES declaration thresholds SDH
For SDH performance monitoring, the SES declaration threshold is the number of block
errors per second that must be exceeded to declare a second severely errored.
These SES declaration thresholds are defined for SDH performance monitoring:
Table 16-9
SES declaration thresholds (SDH)
SDH layer and signal level
Regenerator Section (all STM-N signal levels)
2400
STM-64
3668400
Higher order (HOVC) path
VC-4/VC-4-XC (X=4, 16, 64)
2400
SES declaration thresholds SONET
For SONET performance monitoring, the SES declaration threshold is the number of
code violations per second that must be exceeded to declare a second severely errored.
These SES declaration thresholds are defined for SONET performance monitoring:
Table 16-10
SES declaration thresholds (SONET)
SONET layer and signal level
Section
OC-3
155
OC-12
616
OC-48
2392
OC-192
8554
STS-1/STS-1-Xc (X=3, 12, 48, 192)
2400
Path
....................................................................................................................................................................................................................................
1830 PSS
16-15
Issue 1 June 2013

....................................................................................................................................................................................................................................
SES declaration threshold OTH
Depending on the considered OTUk or ODUk signal level, the following table shows the
number of BIP-8 block errors that must be exceeded to declare a second severely errored:
Table 16-11
SES declaration thresholds (OTH)
OTUk or ODUk signal

level
BIP-8 block error count for SES
OTU2
12304 BIP-8 errors

(Section Monitoring (SM) field in OTU2 overhead)
OTU2E
12748 BIP-8 errors

(Section Monitoring (SM) field in OTU2E overhead)
OTU3
49424 BIP-8 errors

OTU3E2
51222 BIP-8 errors

OTU4
128459 BIP-8 errors

ODU0
1526 BIP-8 errors

(Path Monitoring (PM) field in ODU1 overhead)
ODU1
3064 BIP-8 errors

ODU2
12304 BIP-8 errors

ODU2E
12748 BIP-8 errors

ODU3
49424 BIP-8 errors

ODU3E2
51222 BIP-8 errors

(Path Monitoring (PM) field in ODU3E2 overhead)
ODU4
128459 BIP-8 errors

....................................................................................................................................................................................................................................
1830 PSS
16-16
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
Thresholding
Threshold crossing alerts (TCAs) and TCA profiles
Alcatel-Lucent 1830 PSS systems support threshold crossing alerts (TCAs) on a per
performance parameter basis by using TCA profiles. The TCA profiles are used to store
the threshold values of the performance parameters related to a specific parameter group
(for example parameters related to the SONET Section).
When thresholding is activated for a performance parameter (see Enabling/disabling
thresholding (p. 16-20)), the value of the parameter is compared aiganst the threshold
value on a second by second basis. When the current counter value equals or exceeds the
threshold value, then a threshold crossing alert will be reported as an event notification
with a resolution of one second.
As threshold crossing alerts are events, they are stored in the network element event log,
and displayed in the list of TCA events ).
Types of TCA profiles
The following types of TCA profiles are supported:
In ANSI mode:
OC-3 (SONET Section and Line)

STS-1 (SONET path)
STS-3c (SONET path)

STS-12c (SONET path)
STS-48c (SONET path)
In ETSI mode:
STM-1 (SDH Regenerator Section and Multiplex Section)

VC-4 (SDH higher order path)

VC-4-4c (SDH higher order path)
VC-4-16c (SDH higher order path)
....................................................................................................................................................................................................................................
1830 PSS
16-17
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
OTN profile types:

OTU2
OTU2E
OTU3
OTU3E2
OTU4
ODU0
ODU1
ODU2
ODU2E
ODU3
ODU3E2
ODU4
ODU0TCM
ODU1TCM
ODU2TCM
ODU2ETCM
ODU3TCM
ODU3E2TCM
ODU4TCM
A default profile (DEFAULT) is predefined for each of these TCA profile types.
Additionally a predefined NULL profile exists. Predefined profiles cant not be changed.
Furthermore, you can modify or delete TCA profiles of these types.
The DEFAULT0 TCA profile is used to deactivate (disable) thresholding.
Default threshold settings
Refer to:
SONET Section (p. 16-22)
SDH Regenerator Section (p. 16-20)
TCA modes
Two different TCA modes (or thresholding methods) can be distinguished:

1. Transient condition method (TR only mode).
2. Standing condition method (TR/RTR mode).
Subsequently, these TCA modes will be explained in more detail.
....................................................................................................................................................................................................................................
1830 PSS
16-18
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
Transient condition method
In the transient condition method, only one threshold, the so-called threshold report (TR)
threshold, is defined.
Note: The transient condition method is used for SONET interfaces and is a
configuration option for SDH interfaces.
When the counter value of a performance parameter equals or exceeds this threshold, then
a threshold report (TR, synonymous to threshold crossing alert) is generated and stored in
the network element alarm log.
No more than one threshold crossing alert will be generated per performance parameter
during a measurement interval unless the threshold value has been changed, or the
performance parameter has been reset (to zero). When the counter value again reaches or
exceeds the threshold, another threshold crossing alert will be reported.
The following figure illustrates the transient condition method:
Figure 16-3 Thresholding - Transient condition method
1
t
TR
TR
TR
g-upg-0037
Legend:
Threshold for generating a threshold report (TR).
Standing condition method
In the standing condition method, two thresholds are defined, a threshold report (TR)
threshold and a reset threshold report (RTR) threshold.
Note: The standing condition method is the default TCA mode for SDH interfaces,
and is used for all 15 minutes performance registers for which thresholding is
supported. However, for SDH interfaces also the transient condition method can be
chosen as a configuration option.
When the counter value of a performance parameter equals or exceeds the TR threshold,
then a threshold report (TR, synonymous to threshold crossing alert) is generated.
Only the first threshold crossing in a sequence of measurement intervals is reported. At
the end of the first interval in which the counter value did not exceed the RTR threshold, a
reset threshold report (RTR) is generated.
....................................................................................................................................................................................................................................
1830 PSS
16-19
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
The following figure illustrates the standing condition method:

Figure 16-4 Thresholding - Standing condition method
1
2
t
TR
RTR
g-upg-0038
Legend:
Threshold for generating a threshold report (TR).
Threshold for generating a reset threshold report (RTR).
Enabling/disabling thresholding
Thresholding can be enabled or disabled for each performance parameter individually.

Thresholding is enabled for a specific performance parameter, when the following
applies:
The associated port or tributary has a corresponding TCA profile assigned.

The threshold value of the performance parameter is unequal to zero.
Thresholding can be disabled for each performance parameter individually by setting the
associated threshold value to zero.
Assigning a TCA profile with all parameter thresholds set to zero (DEFAULT0 TCA
profile) can be used to disable thresholding for all performance parameters associated to a
particular port or tributary.
Default threshold settings
In the following tables, the default threshold settings of the TCA profiles are listed for
15-minutes and 1-day measurement intervals.
The threshold values for the 15-minutes measurement intervals indicate an unacceptable
performance level.
The threshold values for the 1-day measurement intervals indicate a degraded
performance level.
SDH Regenerator Section
These are the default parameter thresholds related to the SDH Regenerator Section:
....................................................................................................................................................................................................................................
1830 PSS
16-20
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
Table 16-12
Performance parameter
Default thresholds - SDH Regenerator Section

Default threshold values
15-minutes measurements
1-day measurements
TR threshold
TR threshold
RTR threshold
OFS-RS
900
86400
BBE-RS
24000
200
36000
ES-RS
50
150
SES-RS
10
15
UAS-RS
10
10
Notes:
1.
The threshold values apply to STM-1, STM-4, STM-16 as well as STM-64 signal levels.
2.
See PM reports SDH Regenerator Section (p. 16-92) for the value ranges.
3.
Please also see TCA modes (p. 16-18).
SDH higher order path
These are the default parameter thresholds related to the SDH higher order path:
Table 16-13
Default thresholds - SDH higher order path

1-day measurements
TR threshold
RTR threshold
TR threshold
36000
200
48000
ES-HOVC
180
20
1500
SES-HOVC
15
20
UAS-HOVC
10
10
BBE-HOVC
....................................................................................................................................................................................................................................
1830 PSS
16-21
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
SONET Section
These are the default parameter thresholds related to the SONET Section:
Table 16-14
Default thresholds - SONET Section

CVS
ESS
SESS
SEFSS
UASS
1-day measurements
OC-3
27
270
OC-12
77
770
OC-48
252
2520
OC-192
752
7520
OC-3
22
220
OC-12
62
620
OC-48
202
2020
OC-192
602
6020
OC-3
OC-12
OC-48
OC-192
OC-3
OC-12
OC-48
OC-192
OC-3
10
10
OC-12
10
10
OC-48
10
10
OC-192
10
10
Notes:
1.
See PM reports SONET Section (p. 16-94) for the value ranges.
....................................................................................................................................................................................................................................
1830 PSS
16-22
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
SONET path
These are the default parameter thresholds related to the SONET path:
Table 16-15
Default thresholds - SONET path

CVP
ESP
SESP
UASP
1-day measurements
STS-1
15
125
STS-3c
25
250
STS-12c
75
750
STS-48c
225
2250
STS-1
12
100
STS-3c
20
200
STS-12c
60
600
STS-48c
180
1800
STS-1
STS-3c
STS-12c
STS-48c
STS-1
10
10
STS-3c
10
10
STS-12c
10
10
STS-48c
10
10
Notes:
1.
See for the value ranges.
ODUk
These are the performance monitoring parameters related to the ODUk Path that are
returned by the NE:
Table 16-16
Parameter
Default thresholds - ODUk
Description

15-minutes
1-day measurements
measurements
ES-ODU
Errored Seconds (ES) - ODU
50
150
SES-ODU
Severely Errored Seconds (SES) - ODU
10
15
....................................................................................................................................................................................................................................
1830 PSS
16-23
Issue 1 June 2013

Thresholding
....................................................................................................................................................................................................................................
Table 16-16
Parameter
Default thresholds - ODUk
(continued)
Description

15-minutes
1-day measurements
measurements
BBE-ODU
UAS-ODU
Background Block Errors (BBE) - ODU
ODU0
6600
950447
ODU1
13200
1900894
ODU2
26401
3801788
ODU2E
26401
3801788
ODU3
212900
30672473
ODU3E2
221278
31788289
10
10
Unavailable Seconds (UAS) - ODU
Notes:
1.
See PM reports ODUk Path (p. 16-98) for the value ranges.
OTUk
These are the performance monitoring parameters related to the OTUk Path that are
returned by the NE:
Table 16-17
Parameter
Default thresholds - OTUk
Description

15-minutes
1-day measurements
measurements
ES-OTU
Errored Seconds (ES) - OTU
50
150
SES-OTU
Severely Errored Seconds (SES) - OTU
10
15
BBE-OTU
Background Block Errors (BBE) - OTU
OTU2
26401
3801788
OTU2E
26401
3801788
OTU3
212900
30672473
OTU3E2
221278
31788289
10
10
UAS-OTU
Unavailable Seconds (UAS) - OTU
Notes:
1.
See PM reports OTUk Section (p. 16-97) for the value ranges.
....................................................................................................................................................................................................................................
1830 PSS
16-24
Issue 1 June 2013

....................................................................................................................................................................................................................................

Deletion of performance monitoring points
When a performance monitoring point is removed from the system, the associated
performance monitoring processing is stopped, and all associated current bins are
discarded.
Besides the explicit deletion of performance monitoring points via dedicated management
commands performance monitoring points will implictely be deleted as follows:
If a port unit is deleted all monitoring points related to that port unit will be removed.
Performance monitoring history data
The performance monitoring history bins belonging to a certain performance monitoring

point will only be deleted if the circuit pack on which the performance monitoring point
resides is explicitly deleted.
In the case of
disabling performance monitoring points manually, or
the related performance monitoring points will be deleted but the history bins for those
monitoring points might still be visible (retrievable) for up to eight hours in the case of
15-minutes measurements and for up to one day in the case of 1-day measurements.
Therefore, ignore performance monitoring history data belonging to a date and time
outside the current activation period of individual performance monitoring points.
Interface standard of a port
The Alcatel-Lucent 1830 PSS system allows ports to be operated according to the SDH or
SONET standard.
Forward Error Correction (FEC)
The Alcatel-Lucent 1830 PSS system supports in-service enabling or disabling of

Forward Error Correction (FEC); see .
In-service enabling or disabling of FEC has the following effects:
When FEC is enabled on a port with MS/Line performance monitoring enabled, then
the FECC counter will be started.
When FEC is disabled on a port with MS/Line performance monitoring enabled, then
the FECC counter will be reset to zero.
MTX equipment protection
All performance monitoring event processing as well as binning and reporting is

performed on the active cross-connection and timing unit (MTX).
....................................................................................................................................................................................................................................
1830 PSS
16-25
Issue 1 June 2013

....................................................................................................................................................................................................................................
On a cross-connection and timing unit, performance monitoring data is stored in the

current bin and one recent bin. Both cross-connection and timing units operate in a
hot-standby mode with regard to performance monitoring. However, no transfer of the
performance monitoring data is performed in case of an MTX equipment protection
switch. Thus, an MTX equipment protection switch may result in loss of performance
monitoring data, depending on the time the standby MTX was plugged into the system.
Important! Prior to an (intentional) MTX equipment protection switch the standby
MTX should have been present in the system for a full 1-day binning period.
Otherwise, performance monitoring data may be lost.
Inhibit matrix equipment protection
While matrix equipment protection is inhibited, WARM resets of the active SLC can
cause loss of line PM data for several minutes until the active MTX is up and running
again.
FLC initialization
FLC initialization (via INIT-SYS command) occurs without equipment protection during
the accumulation period. Executing the initialization, the redundancy of the PM collection
is lost for some minutes. During this period, an initialization of the active card (FLC,
SLC) causes loss of PM data.
....................................................................................................................................................................................................................................
1830 PSS
16-26
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
Performance monitoring (PM) refers to the in-service, non-intrusive monitoring of

transmission quality and equipment health. The Alcatel-Lucent 1830 PSS tracks the signal
quality and equipment health through continuous collection and analysis of performance
data. The user can retrieve current and past values of the system to get an overview of the
health of the system. The performance monitoring capability exists for optical lines,
channels, and equipment monitoring. Users have the ability to provision threshold
parameters to levels that might be indicative of impending performance degradation.
Responding to a performance degradation before there is a failure and system alarms are
raised is termed proactive maintenance. Responding to system alarms is termed reactive
maintenance. Crossing of a performance parameter threshold indicates a potential
network quality or performance degradation while the services being transported have not
been impacted. If a condition continues to deteriorate, then alarms are raised and
immediate attention may be required to resolve or repair the problem.
Performance monitoring statistics are gathered for all service cards and for all interface
ports that perform OEO conversions or protection switching. The statistics are grouped by
functional category. Each category has several monitored parameters for which you can
configure threshold crossing alerts (TCAs). A threshold is the mechanism for generating a
defined notification resulting from changes in PM parameter values. The Alcatel-Lucent
1830 PSS allows provisioning of performance parameter thresholds, which can be set by
the user to show degraded performance. You can configure how much data is gathered,
how it is stored, and how and when you are notified if certain thresholds levels are
crossed.
Note: The user can inhibit individual monitor type TCA messages by setting the
threshold value in a TCA profile assigned to a facility to 0 if the parameter is digital or
to -99.99dB if the parameter is analog.
Note: Threshold crossing alerts based on code violations are not currently supported
for the following client signal types: FE, HDSID, SDSDI and DVB-ASI. However,
code violation performance monitoring data for each of these signal types are
counted/binned, and can be retrieved by the User.
....................................................................................................................................................................................................................................
1830 PSS
16-27
Issue 1 June 2013

....................................................................................................................................................................................................................................
Cards and Ports that support PM Data
Table 16-18, Cards and Ports that Support PM Data (p. 16-28) specifies which cards
and ports support PM data.
Table 16-18
Cards and Ports that Support PM Data

Card
Port
10AN10G
{1-10}
10ET1G
112PDM11
L{1-4}, C{1-10}
112SCA1
L1, C1
112SNA1
112SCX10
L1, C{1-10}
112SNX10
130SCX10
11DPE12
L{1,2}, VA{1,2}, C{1-12}
11DPE12A
11DPE12E
11DPM12
L{1,2}, VA{1,2}, C{1-12}
11QCUPC
L{1-4}, VA{1-4}
11QPA4
L{1-4}, VA{1-4}, C{1-4}
11QPEN4
11QPE24
X{1-4}, VA{1-4}, C{1-22}
11STAR1
L1 ,C1
11STAR1A
11STGE12
L1, C{1-10}
11STMM10
L1, C{1-10}
130SCUP
L1
1DPP24M
L1, C{1-21}
24ANM
{1-24}
24ET1GB
43SCA1
L1, C1
43SCGE1
L1, C1
43SCX4
L1, C{1-4}
43SCX4E
....................................................................................................................................................................................................................................
1830 PSS
16-28
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 16-18
Cards and Ports that Support PM Data
(continued)
Card
Port
43STA1P
L1, C1
43STX4
L1, C{1-4}
43STX4P
4AN10G
{1-4}
4DPA2
L{1,2}, C{1,2}
4DPA4
L{1,2}, C{1-4}, VA{1,2}
(Card Mode = FlexMux)

4DPA4
L{1,2}, C{1,3}, VA{1,2}
(Card Mode = DualTran)

4QPA8
L{1-4}, C{1-4}, VA{1-4}
8ET1GB
{1-8}
A2325A
OSC, LINE, LINE-{9170~9605}
AHPHG
AHPLG
ALPHG
A2P2125
AM2125A
OSCSFP, LINEIN, LINEIN-{9170~9605}, LINEOUT,

LINEOUT-{9170~9605}
AM2125B
AM2318A
EC
No port, PM data collected for card.
OSCT
OSCSFP, LINE, LINE-{9170~9605}
MVAC
G{1-8}
MVAC8B
L{1-8}, C{1-8}
RA2P
LINEIN
SVAC
L1, C1
WTOCMA
IN{1-4}-{9170~9605}
MTC1T9
No port. PM data collected for card.
PTPCTL
P {1-6}
PTPIO
TP {1,2}, ITP {1,2}
Note: 11STMM10 hardware does not support GbE PM statistics in egress direction.
TX side PM data is not displayed for 4DPA2 client or line ports.
....................................................................................................................................................................................................................................
1830 PSS
16-29
Issue 1 June 2013

....................................................................................................................................................................................................................................
43STX4 does not support PM in TX direction (only supported in RX direction)

For 112SCA/112SNA1:
OPR and OPT (Total CFP Lane power) are supported on Client Port
RX and Tx Individual Lane powers are displayed at port level
Note: Some cards support reporting of the PM parameters Rx SM Incoming

Alignment Error seconds and Rx SM FarEnd Incoming Alignment Error seconds.
For those cards that do not support these PM parameters, the PM report will display
these fields as blank (has no value).
Note: Transmit side PCS layer monitoring on client ports of the 43SCX4 OT is not
supported.
How performance monitoring works
Performance monitoring (PM) statistics provide counts or measurements of significant

information that can be used to gauge the performance of the network element and the
services running on it. The statistics gathered are used primarily for the following:
to provide instant notification, via alarms, that acceptable thresholds for data such as
CPU utilization or dropped packets have been crossed.
to provide a historical view of the performance of the network element over a given
period of time.
Performance monitoring functions are performed on physical and logical points within
the Alcatel-Lucent 1830 PSS NE which represent the boundary with other NEs or
external system. This allows user to define and monitor Quality Of Service at individual
points in which local NE interacts with other network entities. Figure 16-5, Performance
monitoring points in an 1830 PSS NE (p. 16-31) gives an illustration of PM points in an
Alcatel-Lucent 1830 PSS NE.
....................................................................................................................................................................................................................................
1830 PSS
16-30
Issue 1 June 2013

....................................................................................................................................................................................................................................
Figure 16-5 Performance monitoring points in an 1830 PSS NE
The identified points in Figure 16-5, Performance monitoring points in an 1830 PSS
NE (p. 16-31) provide the following transport layer and PM monitoring types:
1. OTS layer -> monitored type(s): Total OPR
OCh channel within the OTS -> monitored types: (individual channel)
OPR
2. OTS layer -> monitored type(s): Total OPT
OCh channel within the OTS -> monitored types: (individual channel)
OPT
3. OPS layer -> monitored type(s): OPR & OPT
OTUk (Section Monitoring) layer -> monitored types: BBE (BIP-8), ES, SES, UAS,
FEC-EC & FEC-UBC
ODUk (Path Monitoring) layer -> monitored types: BBE (BIP-8), ES, SES & UAS
4. Client Optical -> monitored type(s): OPR & OPT
Client Digital -> refer to client specific monitored type specification in the next
section.
5. OSC Receive direction -> monitored type(s): OPR, CV, ES, SES, SEFS, Ethernet
Interface group
6. OSC Transmit direction -> monitored type(s): OPT
....................................................................................................................................................................................................................................
1830 PSS
16-31
Issue 1 June 2013

....................................................................................................................................................................................................................................
While digital monitoring types provide progressive accumulation of monitored

performance event counts, analog monitoring types provide watermark points (High and
Low watermarks) as well as average value of analog monitored parameter over an
accumulation period.
Note: SES is declared considering the number of packets with errors in a second, and
not based on error rate. Also with high error rate, but with few packets with error, SES
is not incremented.
Bins and intervals
Data from a card or interface is continually gathered for the performance monitoring
group, or groups, that apply to the interface or card. For each group, the data is placed
into two bins that collect the data over a specified time interval. The time interval for the
interval bins is 15 minutes or 24 hours. 24-hour bins collect data from midnight to
midnight based on UTC, not local time. Performance data is also placed into a raw bin.
The statistics in the raw bin accumulate until the contents of the raw bin are cleared.
At the end of each interval, the PM data is moved to the subsequent bin at the end of the
interval period, such that the contents of bin 0 (the active bin) are moved to bin 1, bin 1 to
bin 2, and so on. The contents of the last bin are discarded. You can configure each data
collection point for cards to use up to 8 bins for one day (24-hour) data, and up to 33 bins
for 15-minute data.
Note: Provisioning of number of bins is not supported for IO cards.
Note: After a cold reboot of a card, it is necessary to perform an INIT-REG command
in order to have a clean PM collection period.
Note: For IO and Uplink cards, PM collection is not impacted by FLC reboot.
Thresholds and threshold crossing alerts (TCAs)
Threshold values are considered as crossed when the value in the Current Register is
equal to or exceeds the value in the corresponding Threshold Register. No threshold for
clearing is supported. TCAs are reported via messages upon recognition of the threshold
crossings. A TCA is not considered as a standing condition. No clearance is reported at
the end of any monitoring period.
TCA messages for digital parameters identify the monitored facility, monitored parameter
register, current threshold value, current register value, time and date of the occurrence.
TCA messages for analog parameters identify the monitored facility, monitored parameter
register, current threshold value, current register value, baselined value, time and date of
the occurrence. TCA message output contains absolute measure value for the current
register value and not the deviation from associated baselined value.
....................................................................................................................................................................................................................................
1830 PSS
16-32
Issue 1 June 2013

....................................................................................................................................................................................................................................
Performance parameter thresholds are set to show degraded performance. A threshold is

the mechanism for generating a defined notification resulting from changes in parameter
values. There are two types of thresholds:
counter-threshold: associated with digital parameters

gauge-threshold: associated with analog parameters
Unlike the value of a counter parameter that can only increase in value unless its value
is reset, the value for a gauge parameter can increase or decrease continuously over time.
Analog parameters have two user configurable thresholds (notifyHigh and notifyLow) as
a high threshold and low threshold associated with the parameter respectively.
These threshold values are checked against the appropriate tidemark low and tidemark
high monitors and TCA notification raised if tidemark high exceeds the defined
notifyHigh value for the parameter and time period, or if tidemark low drops below the
defined notifyLow value for the parameter and time period.
Figure 16-6 Analog parameter TCA
Note: Term exceed used with tidemark low/high monitored parameters indicates that
tidemark high value is greater than the corresponding threshold or that tidemark low
is below the corresponding threshold.
For OT physical layer OPR, OPT parameters TCA profiles contain values for positive and
negative deviation relative to established baselined analog value for that port. Baselining
of OPR/OPT values can be established automatically (at the point the input signal is
applied to the port initially or laser initially enabled) or manually by user command.
....................................................................................................................................................................................................................................
1830 PSS
16-33
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: There are two ways of baselining optical signal power levels:
Via a user command (manual baselining or re-baselining)
Automatic baselining
Automatic baselining of OPR and OPT parameters on OT ports is performed only
after the initial port creation and dLOS clearing or laser ON so that baseline value
can be established without user action. After initial auto-baselining, analog
parameters on OT ports will need to be manually baselined to acknowledge the
change in power reference.
Unlike manual baselining, auto-baselining does not occur if a baseline value is
already established.
Baselining applies to OT and OSC ports but not OCh and OTS ports. OCh and OTS port
thresholds are established during the commissioning phase.
For each threshold on a Current register, only one TCA is sent during an accumulation
period, unless the Current register is reset. If the Current register is reset and subsequently
its value again reaches or exceeds the threshold value, another TCA is sent. When a
threshold is crossed, the NE does not reset the register, but continues counting to the end
of the accumulation period.
Client/Line card and Uplink card PM TCA Operation
If a Client/Line card or Uplink card is already in service, and the card is subsequently
re-set, PM TCAs may still be reported during the time that the card is re-initializing.
In traditional WDM configurations with optical transponders (OTs), PM TCA reporting is
supported when the OT facility state is UP. For Client/Line and Uplink cards, PM TCAs
will be reported regardless of the facility state.
TCA profiles
As the PM data is collected, the attribute counters in the active bin (bin 0) get
incremented or updated each time an event, such as a SONET/SDH errored second,
occurs. If desired, you can configure and assign a profile to an interval to monitor the
value of each attribute in the active bin and raise a log event when a certain threshold
level is reached. When a specified threshold is crossed a log event is raised.
You can configure each PM group with up to eight profiles, all having different threshold
levels. The NE provides the ability to modify all TCA profiles. The threshold levels you
define in the profiles depend on two factors:
the interval length. For example, if you were gathering statistics for an interface over
15 minute and 24 hour intervals you would need to define two profiles, one that
defines the threshold values for the 15 minute interval and one that defines thresholds
for the 24 hour interval.
the service level of the traffic using the interface.
....................................................................................................................................................................................................................................
1830 PSS
16-34
Issue 1 June 2013

....................................................................................................................................................................................................................................
There are 9 instances of each profile type supported. The user can inhibit individual
monitor type TCA messages by setting the threshold value in a TCA profile assigned to a
facility to 0 if the parameter is digital or to -99.99dB if the parameter is analog. Profiles
with index 7 contain factory default data with 15-min defaults preloaded while profile
with index 8 contains 1-day defaults preloaded. Instances 1-6 are initialized with all 0
values and can be customized by the user.
Note:
1. There is no restriction in assigning profile numbers to PM intervals.
2. PM profile supports default 15 minute and default 1 day values
3. The maximum value allowed for 15 minute threshold vs 1 day are not the same.
The system supports the following TCA profile types:
OC_N (SONET port section monitoring)
STM_N (SDH port section monitoring)

DW (OTU and ODU layer PM parameters)
ETH (Ethernet group)
INF (Interface group)

PCS (PCS layer monitoring for Ethernet/FC ports)
CP (Equipment PM parameters, applicable to EC)
OPR (Optical Power Received on OT and OSC ports)

OPT (Optical Power Transmitted on OT and OSC ports)
OTUPM (OTU layer PM for client/line and uplink cards)
ODURX (HO-ODU and LO-ODU layer receive-direction PM supported on
ODUNIM facilities and ODUPTF facilities on the PSS-32S shelf)
ODUTX (HO-ODU and LO-ODU layer-transmit direction PM supported on
ODUNIM facilities on the PSS-32S shelf)
Note: The WebUI allows the user to select one or more PM Groups (including All)
and one or more Bin types (15-Minute, 1-Day, or Raw Counts) in a single user
request.
Note: For 112SCA/112SNA1 the following applies:
For CFP pluggable modules on the client interface, the system displays a snapshot
of the per lane CFP optical power levels (transmit and receive).
For the C113G4C and C113G4Cd pluggable modules, the system displays four
receive optical power lanes (RxPwr Lane {1-4}) and four transmit power lanes
(TxPwr Lane {1-4}).
....................................................................................................................................................................................................................................
1830 PSS
16-35
Issue 1 June 2013

....................................................................................................................................................................................................................................
For the C113G10C pluggable module, the system displays ten receive optical
power lanes (RxPwr Lane {1-10}) and ten transmit power lanes (TxPwr Lane
{1-10}).
The per lane power levels are reported in real time. No binning or thresholding is
supported.
Configuring performance monitoring
The major steps in high-level performance monitoring configuration are as follows:

1. Determine the interfaces and cards you need to configure to collect performance
monitoring data.
2. Configure the profiles to define the threshold levels at which log events are generated
for the PM groups you will be monitoring on the network element.
3. Configure each of the interfaces and cards on the network element for which you will
be collecting performance monitoring statistics. You need to define which PM
statistics are gathered, the interval period over which they are gathered, and the
profile used for each interval period.
Viewing performance monitoring data
Performance monitoring data is recorded in logs or in bins. The logs record all of the
threshold crossing events that occurred on the network element. The bins hold data
gathered on a specific card or interface over a specific interval. In addition to the interval
bins, there is a raw bin for each PM group that continues to gather data until cleared.
Note: When PM data is not available, PM attribute names are displayed with their
values as "blank".
Note: As a result of a Loss of Signal (LOS) defect at a receive OT port, the user
interfaces will report an Out of Range indication.
1830 PSS-32S performance monitoring
When the OTUk/ODUNIM/ODUPTF facilities on the client/line and uplink cards in the
PSS-32S shelf are created, Performance Monitoring data collection is defined by the
following table.
Table 16-19
PSS-32S Facilities
Ingress PM
Facility
OCH (of OTUk
section of
DWDM uplink)
NE in SONET
mode
Enabled and
counting
NE in SDH
mode
Enabled and
counting
Egress PM
NE in SONET
mode
Enabled and
counting
NE in SDH
mode
Enabled and
counting
....................................................................................................................................................................................................................................
1830 PSS
16-36
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 16-19
PSS-32S Facilities
(continued)
Ingress PM
Facility
NE in SONET
mode
NE in SDH
mode
Egress PM
NE in SONET
mode
NE in SDH
mode
OTU
Enabled and
counting
Enabled and
counting
Not Applicable
Not Applicable
ODU (NIM)
Not Created
(PMMODE=
Disabled)
Not Created
(PMMODE=
Disabled)
Not Created
(PMMODE=
Disabled)
Not Created
(PMMODE=
Disabled)
ODUkPTF
Not Created
(PMMODE=
Enabled)
Not Created
(PMMODE=
Enabled)
Not Applicable
Not Applicable
ODUk TCM
layer (both NIM
and terminated)
Not Created
(PMMODE=
Disabled)
Not Created
(PMMODE=
Disabled)
Not Applicable
Not Applicable
When the PMMODE parameter is set to Enabled for the ingress direction (DIRN=RCV),
the ingress ODUNIM PM registers are created and counted only if the corresponding
POM parameter functionality is enabled. A POM value of Disabled is equivalent to the
PMMODE=Disabled. When the PMMODE parameter is set to Enabled for the egress
direction (DIRN=TRMT), the egress ODUNIM PM registers are created and counted
only if the corresponding EGPOM functionality is enabled. An EGPOM value of NO is
equivalent to PMMODE=Disabled.
....................................................................................................................................................................................................................................
1830 PSS
16-37
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
Contents
16-39
16-43
16-47
16-52
16-55
16-58
16-61
16-63
Procedure 16-9: Retrieve the threshold settings of a TCA profile
16-65
16-66
16-67
....................................................................................................................................................................................................................................
1830 PSS
16-38
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to enable or disable PM data collection.

SET-PMMODE-GBE
SET-PMMODE-GBE10
SET-PMMODE-OC192
SET-PMMODE-OC48
SET-PMMODE-OC12
SET-PMMODE-OC3
SET-PMMODE-ODU0
SET-PMMODE-ODU1
SET-PMMODE-ODU2
SET-PMMODE-ODU2E
SET-PMMODE-ODU3
SET-PMMODE-ODU3E2
SET-PMMODE-ODU4
SET-PMMODE-OTU
SET-PMMODE-TCM
SET-PMMODE-STM1
SET-PMMODE-STM4
SET-PMMODE-STM16
SET-PMMODE-STM64
SET-PMMODE-STS1
SET-PMMODE-STS3C
SET-PMMODE-STS12C
SET-PMMODE-STS48C
SET-PMMODE-VC4
SET-PMMODE-VC44C
SET-PMMODE-VC416C
....................................................................................................................................................................................................................................
1830 PSS
16-39
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
port in the navigation tree underFacilities.
illustrates this structure using an OTU2 facility as an example.
Facility type
Facility group
Port
g-upg-0059
...................................................................................................................................................................................................
If
then
you want to enable or disable PM data

collection on port level (PM data for GBE,
GBE10, STM-1, STM-4, STM-16, STM-64,
OC-3, OC-12, OC-48, OC-192, OTU2 or
OTU3)
you want to enable or disable PM data

collection on path level (PM data for GBE,
GBE10, STM-1, STM-4, STM-16, STM-64,
OC-3, OC-12, OC-48, OC-192, OTU2 or
OTU3)
select the desired path-level facility in the

display pane, and then continue with the next
step.
....................................................................................................................................................................................................................................
1830 PSS
16-40
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Right-click on the selected facility, and select Performance Monitoring Modify PM

Mode from the context menu that opens.
In the Action menu, select Performance Monitoring Modify PM Mode.
Result: The Modify PM Mode window opens.
...................................................................................................................................................................................................
In the Location field, specify whether near-end or far-end parameters (or both) are to be
monitored.
...................................................................................................................................................................................................
In the Mode Type field, specify the type of PM parameters to be monitored.

Values are:
PM parameters for Gigabit Ethernet:

MAC - MAC parameters
ALL - All applicable parameters
PM parameters for SDH facilities:
P - Path parameters (VC-4, VC-4-4c, VC-4-16c)
S - Regenerator Section (RS) parameters (STM-1, STM-4, STM-16, STM-64)
ALL - All applicable parameters:
PM parameters for SONET facilities:
P - Path parameters (STS-1, STS-3c, STS-12c, STS-48c)
S - Section parameters (OC-3, OC-12, OC-48, OC-192)
PM parameters for OTH facilities:

P - ODU Path parameters
S - OTU parameters
...................................................................................................................................................................................................
In the TIME Period field, specify whether the 15-minute or 1-day (24 hour) PM collection
register is to be enabled/disabled.
15-MIN
15 minutes registers
1-DAY
....................................................................................................................................................................................................................................
1830 PSS
16-41
Issue 1 June 2013

....................................................................................................................................................................................................................................
24 hour registers
BOTH
15 minutes and 24 hour registers

Restriction:
Note: The parameter is applicable only when the global REGION parameter is set to
ETSI. If this parameter is specified on an NE that has REGION parameter set to
ANSI, the command will be denied.
...................................................................................................................................................................................................
In the PM State field, select ON to enable PM data collection or DISABLED to disable PM

data collection.
...................................................................................................................................................................................................

...................................................................................................................................................................................................
If
then
you want to activate your changes,
click Apply.
you want to discard your changes,
click Cancel.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-42
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve the PM activation status of a facility.

RTRV-PMMODE-GBE
RTRV-PMMODE-GBE10
RTRV-PMMODE-OC3
RTRV-PMMODE-OC12
RTRV-PMMODE-OC48
RTRV-PMMODE-OC192
RTRV-PMMODE-ODU0
RTRV-PMMODE-ODU1
RTRV-PMMODE-ODU21
RTRV-PMMODE-ODU2E
RTRV-PMMODE-ODU3
RTRV-PMMODE-ODU3E2
RTRV-PMMODE-ODU4
RTRV-PMMODE-TCM
RTRV-PMMODE-OTU
RTRV-PMMODE-OCH
RTRV-PMMODE-STM1
RTRV-PMMODE-STM4
RTRV-PMMODE-STM16
RTRV-PMMODE-STM64
RTRV-PMMODE-STS1
RTRV-PMMODE-STS3C
RTRV-PMMODE-STS12C
RTRV-PMMODE-STS48C
RTRV-PMMODE-VC4
RTRV-PMMODE-VC44C
RTRV-PMMODE-VC416C
....................................................................................................................................................................................................................................
1830 PSS
16-43
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Facility type
Facility group
Port
g-upg-0059
...................................................................................................................................................................................................
If
then
you want to retrieve the PM activation status on

port level (PM data for GBE, GBE10, STM-1,
STM-4, STM-16, STM-64, OC-3, OC-12,
OC-48, OC-192, OTU2, OTU2E, OTU3 or
OTU4)
you want to retrieve the PM activation status on

path level (PM data for ODU0, ODU1, ODU2,
ODU2E, ODU3, ODU3E2 or ODU4)

step.
....................................................................................................................................................................................................................................
1830 PSS
16-44
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Right-click on the selected facility, and select Performance Monitoring View PM

Mode from the context menu that opens.
In the Action menu, select Performance Monitoring View PM Mode.
Result: The Retrieve PM Mode window opens.
Note: A table with the PM mode settings is displayed in the lower part of the
Retrieve PM Mode window. The table is populated with values for retrieval with
default settings.
...................................................................................................................................................................................................
In the Location field, specify whether performance monitoring relates to near-end or

far-end parameters (or both).
NEND - Near end
ALL - Near end and far end
Note: For Alcatel-Lucent 1830 PSS , far-end performance monitoring is not

supported.
...................................................................................................................................................................................................
In the Direction field, specify whether the signal in the receive direction or the signal in
the transmit direction is to be monitored (or both).
ALL - Receive direction and transmit direction
...................................................................................................................................................................................................
In the Time Period field, specify whether the 15-minutes or 1-day PM register or both are
to be reported
15-MIN - 15-minutes PM register
1-DAY - 1-day PM register
BOTH - 15-minutes PM register and 1-day PM register
...................................................................................................................................................................................................
Click Send to retrieve the PM activation status of the selected facility.
....................................................................................................................................................................................................................................
1830 PSS
16-45
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: A table with the current PM mode settings is displayed in the lower part of the
Retrieve PM Mode window.
Reference: See Configuration parameters related to performance monitoring
(p. 16-87).
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-46
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve performance monitoring data.

RTRV-PM-GBE
RTRV-PM-GBE10
RTRV-PM-OC192
RTRV-PM-OC48
RTRV-PM-OC12
RTRV-PM-OC3
RTRV-PM-ODU0
RTRV-PM-ODU1
RTRV-PM-ODU2
RTRV-PM-ODU2E
RTRV-PM-ODU3
RTRV-PM-ODU3E2
RTRV-PM-ODU4
RTRV-PM-TCM
RTRV-PM-OTU
RTRV-PM-STM1
RTRV-PM-STM4
RTRV-PM-STM16
RTRV-PM-STM64
RTRV-PM-STS1
RTRV-PM-STS3C
RTRV-PM-STS12C
RTRV-PM-STS48C
RTRV-PM-VC4
RTRV-PM-VC44C
RTRV-PM-VC416C
....................................................................................................................................................................................................................................
1830 PSS
16-47
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required privileges
You must have at least a User Community Authorization Level of 1 to perform this task.
Required equipment
Instructions
...................................................................................................................................................................................................
Facility type
Facility group
Port
g-upg-0059
...................................................................................................................................................................................................
If
then
you want to retrieve port-level PM data (PM

data for GBE, GBE10, STM-1, STM-4,
STM-16, STM-64, OC-3, OC-12, OC-48,
OC-192, OTU2, OTU2E or OTU3)
you want to retrieve path-level PM data (PM

data for ODU0, ODU1, ODU2, ODU2E,
ODU3, ODU3E2 or ODU4)

step.
....................................................................................................................................................................................................................................
1830 PSS
16-48
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Right-click on the selected facility, and select Performance Monitoring View PM

Data from the context menu that opens.
In the Action menu, select Performance Monitoring View PM Data.
Result: The View PM Data window opens.
Note: A table with the PM mode settings is displayed in the lower part of the View
PM Data window. The table is populated with values for retrieval with default
settings.
...................................................................................................................................................................................................
In the View PM Data window, specify the desired parameters for the PM data selection.
For the available parameters, see PM reports General (p. 16-89).
Result: In the lower part of the View PM Data window, a PM report is displayed
according to the facility and parameter selection.

Reference: See Elements of a PM report (p. 16-49).
E...................................................................................................................................................................................................
N D O F S T E P S
Elements of a PM report
The following table describes the elements that make up a PM report:

Table 16-20
Parameter
Details
Name
The designation of the facility to which the monitored PM parameter relates.
Monitored Type
The type of monitored PM parameter.

The supported parameters depend on the type of facility; please also refer to:
PM reports Ethernet (p. 16-96)
....................................................................................................................................................................................................................................
1830 PSS
16-49
Issue 1 June 2013

....................................................................................................................................................................................................................................
Table 16-20
(continued)
Parameter
Details
Monitored Value
The measured value of the monitored PM parameter.

Any measurement value in the range 0 - 4294967295.
NA, when the validity indication of the respective PM register is NA

(Data is not available).
For the value ranges of the monitored PM parameters, refer to PM reports SDH
Regenerator Section (p. 16-92).
This parameter indicates whether the near-end or far-end PM register is reported.
Location
NEND - Near end PM register
FEND - Far end PM register
For Alcatel-Lucent 1830 PSS , far-end performance monitoring is not supported.

Validity
See Validity indication (p. 16-50).
Direction
This parameter indicates the direction of the signal being monitored.

This parameter indicates whether the 15-minutes or 1-day PM register is reported.
Time Period
This parameter indicates the date when the PM collection period began.
Monitor Date
The format of the Monitor Date parameter is MM-DD (month-day).

This parameter indicates the time of day when the PM collection period began.
Monitor Time
The format of the Monitor Time parameter is HH-MM (hour-minute).

Elapsed Time
Elapsed Time.
(ETSI mode only)
This parameter indicates the elapsed time for the current monitoring period or the
actual elapsed time for history monitoring periods.
This parameter is only relevant if the NE operates in ETSI mode.
Validity indication
The validity indication shows the validity of the register (bin) whose value is reported.
....................................................................................................................................................................................................................................
1830 PSS
16-50
Issue 1 June 2013

....................................................................................................................................................................................................................................
The validity indication can take on one of the following values:

Table 16-21
Validity indication
Value
Meaning
LONG
Data accumulated over longer than the indicated time period.

The time of day has been changed and as a result the current data collection period
is longer than the normal accumulation period (10 seconds or more).
PRTL
Data accumulated over some portion of the time period.

PM data is collected only for a part of the accumulation period due to one of the
following reasons:
Collection of the PM data endet before the end of the period.
Failure (lasting more than 10 seconds) of a module involved in PM data

collection.
Board initialization (via INIT-SYS command) occured without equipment

protection during the accumulation period. Executing the initialization, the
redundancy of the PM data collection is lost for some minutes. During this
period, an initialization of the active card (FLC, SLC) raises loss of PM data.
The time of day has been changed and as a result the current data collection
period is shorter than the normal accumulation period (10 seconds or more).
ADJ
Data was manually adjusted (reset via initialization command) during the
accumulation period.
NA
Data is not available.

PM data is prevented for the entire accumulation period due to one of the
following reasons:
COMPL
Inability to fetch the PM data from the I/O module.
Board initialization (via INIT-SYS command) occured without equipment

protection during the accumulation period. Executing the initialization, the
redundancy of the PM data collection is lost for some minutes. During this
period, an initialization of the active card (FLC, SLC) raises loss of PM data.
Data accumulated during entire time period.
....................................................................................................................................................................................................................................
1830 PSS
16-51
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to initialize the current 15-minutes or 1-day PM data registers, that is
reset the counter values in the respective register to zero.
INIT-REG-GBE10
INIT-REG-GBE
INIT-REG-OC192
INIT-REG-OC48
INIT-REG-OC12
INIT-REG-OC3
INIT-REG-OTU
INIT-REG-TCM
INIT-REG-ODU0
INIT-REG-ODU1
INIT-REG-ODU2
INIT-REG-ODU2E
INIT-REG-ODU3
INIT-REG-ODU3E2
INIT-REG-ODU4
INIT-REG-STM1
INIT-REG-STM4
INIT-REG-STM16
INIT-REG-STM64
INIT-REG-STS1
INIT-REG-STS3C
INIT-REG-STS12C
INIT-REG-STS48C
INIT-REG-VC4
INIT-REG-VC44C
INIT-REG-VC416C
....................................................................................................................................................................................................................................
1830 PSS
16-52
Issue 1 June 2013

....................................................................................................................................................................................................................................
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Facility type
Facility group
Port
g-upg-0059
...................................................................................................................................................................................................
If
then
you want to initialize registers for port-level

PM data (PM data for GBE, GBE10, STM-1,
STM-4, STM-16, STM-64, OC-3, OC-12,
OC-48, OC-192, OTU2, OTU2E, OTU3 or
OTU4)
you want to initialize registers for path-level

PM data (PM data for ODU0, ODU1, ODU2,
ODU2E, ODU3, ODU3E2 or ODU4)

step.
....................................................................................................................................................................................................................................
1830 PSS
16-53
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Right-click on the selected facility, and select Performance Monitoring Initialize

Registers from the context menu that opens.
In the Action menu, select Performance Monitoring Initialize Registers.
Result: The Initialize Registers window opens.
Note: The menu is only enabled, when PM is enabled.

...................................................................................................................................................................................................
In the Initialize Registers window, use the Time Period list to specify whether the
current 15-minutes or 1-day PM data registers are to be initialized by selecting 15-MIN or
1-DAY.
...................................................................................................................................................................................................
To initialize the corresponding PM data register, click Apply.

Result: The the counter values in the PM data register will be reset to zero.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-54
Issue 1 June 2013

Procedure 16-5: Upload the NE PM data to a remote file

server
....................................................................................................................................................................................................................................

server
When to use
Use this procedure to upload PM data of an NE to a remote file server.

Important! Avoid PM File transfers during in-service upgrade.
COPY-RFILE
Important Information
The system state should be saved regularly both as a safety measure and a maintenance
activity in order to be able to restore the saved state at any future time.
Before you begin

have a running FTP server to transfer the database to
The Alcatel-Lucent 1830 PSS must be in a stable state, that is no configuration changes or
maintenance actions must be started or must be in progress.
Required equipment
Instructions
...................................................................................................................................................................................................

Then select File Transfer Start Copy, either by selecting Action from the main menu
Result: The Alcatel-Lucent 1830 PSS ZIC File Transfer Start window opens.
...................................................................................................................................................................................................
In the field From select LOCPMGLB.
....................................................................................................................................................................................................................................
1830 PSS
16-55
Issue 1 June 2013


server
....................................................................................................................................................................................................................................
The PM global file collection in the local NE. There is a maximum of one instance of
LOCPMGLB in the NE.
...................................................................................................................................................................................................
In the field To select RFSPMGLB.

The PM Global file collection on a remote file server. Multiple instances of RFSPMGLB
can exist in different locations on an remote file server.
...................................................................................................................................................................................................
In the field LOCATION:FTPHost: enter the IP address of the host (the remote file server).
...................................................................................................................................................................................................
In the field LOCATION:Port: enter the port number to connect to.

The default port number for ftp is 21.
When using the fish protocol the default port number 22.
...................................................................................................................................................................................................
In the field Protocol: select the protocol to be used for file transfer.
fish
secure file transfer over ssh
ftp
file transfer protocol according to RFC959

...................................................................................................................................................................................................
RFS.
...................................................................................................................................................................................................
RFS.
Note: For use of the local ftp host, the user/password are defined during the ftp server
configuration on the CT.
...................................................................................................................................................................................................
In the field LOCATION:Url-Path enter the Remote File Path:
....................................................................................................................................................................................................................................
1830 PSS
16-56
Issue 1 June 2013


server
....................................................................................................................................................................................................................................
This value supplies the details of how the specified resource (that is the directory where
the file(s) reside) can be accessed. It has the following syntax: [/]cwd1/cwd2/.../cwdN
where cwd1 to cwdN are strings that identify directories. For the ftp protocol, the cwd1cwdN portion of the url-path is interpreted as a series of FTP commands. Each of the cwd
elements is to be supplied sequentially, as the argument to an FTP CWD (change working
directory) command. For the fish protocol, the cwd1- cwdN portion of the url-path is
interpreted as an absolute file system.
...................................................................................................................................................................................................
10
The Command Mode must not be defined.

...................................................................................................................................................................................................
11
Click on Send to start the upload operation.

...................................................................................................................................................................................................
12
If you want to abort the backup operation, proceed as follows

Then select File Transfer Stop Copy, either by selecting Action from the main menu
Result: The Alcatel-Lucent 1830 PSS ZIC Cancel Copy Remote File window opens.
...................................................................................................................................................................................................
13
In the field From select LOCPMGLB.

The system's secondary backup database.
...................................................................................................................................................................................................
14
In the field To select RFSPMGLB.

A database backup on a remote file server.
...................................................................................................................................................................................................
15
Click on Apply to stop operation.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-57
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to create a new TCA profile instance of a specified profile type.
The new instance of TCA profile is created as a clone of the factory default TCA profilef
the specified type.
ENT-TH-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Select the Facilities node in the Alcatel-Lucent 1830 PSS ZIC selection tree.
...................................................................................................................................................................................................
Then select Threshold Profiles Create, either by selecting Action from the main
Result: The TCA Assignment Profile Creation window is displayed.
...................................................................................................................................................................................................
Using the Profile Type drop down list box select the TCA profile type for the TCA profile
that shall be created.
SONET profile types:
OC192
OC48
OC12
OC3
....................................................................................................................................................................................................................................
1830 PSS
16-58
Issue 1 June 2013

....................................................................................................................................................................................................................................
SDH profile types:
STM16
STM64
STM4
STM1
OTN profile types:
OCH
OTU2
OTU2E
OTU3
OTU3E2
OTU4,
ODU0
ODU1
ODU2
ODU2E
ODU3
ODU3E2
ODU4,
ODU0TCM
ODU1TCM
ODU2TCM
ODU2ETCM
ODU3TCM
ODU3E2TCM
ODU4TCM}
...................................................................................................................................................................................................
Using the drop down list box Set as Default specify if the created TCA profile shall
become the default TCA profile for the entered TCA profile type or not.
Yes
No
...................................................................................................................................................................................................
In the field User Label enter as string to address the TCA profile in place of the AID.
....................................................................................................................................................................................................................................
1830 PSS
16-59
Issue 1 June 2013

....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-60
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to rename a TCA profile instance.

ED-TH-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Select theFacilities node in the Alcatel-Lucent 1830 PSS ZIC selection tree.
...................................................................................................................................................................................................
Then select Threshold Profiles . Manage, either by selecting Action from the main
Result: The Show All TCA Assignment Profiles window is displayed.
...................................................................................................................................................................................................
In the displayed list select the TCA profile to be renamed.

...................................................................................................................................................................................................
Click Modify.
Result: The Edit Alarm Profile window is displayed.
...................................................................................................................................................................................................
In the field User Label you can change the string to address the TCA profile in place of
the AID.
....................................................................................................................................................................................................................................
1830 PSS
16-61
Issue 1 June 2013

....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-62
Issue 1 June 2013

Procedure 16-8: Modify the threshold settings of a TCA

profile
....................................................................................................................................................................................................................................

When to use
Use this procedure to modify the threshold settings of a TCA profile.

ED-TH-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Then select Threshold Profiles . Edit, either by selecting Action from the main menu
Result: The Retrieve TCA Assignment Profile window is displayed.
...................................................................................................................................................................................................
In the field User Label select the related user label of the TCA profile to be modified.
...................................................................................................................................................................................................
Click Send.
Result: All related TCA profiles are displayed.
...................................................................................................................................................................................................
In the displayed list select the TCA profile to be modified.

...................................................................................................................................................................................................
Click Modify
....................................................................................................................................................................................................................................
1830 PSS
16-63
Issue 1 June 2013

Procedure 16-8: Modify the threshold settings of a TCA

profile
....................................................................................................................................................................................................................................
Result: The Edit TCA Assignment Profile window is displayed.

...................................................................................................................................................................................................
In the field TCA threshold value you can enter the new value for the TCA threshold.
...................................................................................................................................................................................................
In the field Threshold Level Clear you can enter the new value that indicates the value of
the threshold that will be used to clear an alert.
Note: This parameter is only supported if region is ETSI and only for 15 minutes
periods...
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-64
Issue 1 June 2013

Procedure 16-9: Retrieve the threshold settings of a TCA

profile
....................................................................................................................................................................................................................................
Procedure 16-9: Retrieve the threshold settings of a TCA

profile
When to use
Use this procedure to retrieve values of thresholds for the specified monitored types in a
specified profile.
RTRV-TH-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Then select Threshold Profiles Edit, either by selecting Action from the main menu
Result: The Retrieve TCA Assignment Profile window is displayed.
...................................................................................................................................................................................................
In the field User Label select the related user label of the TCA profile to be displayed.
...................................................................................................................................................................................................
Click Send.
Result: All related TCA profiles are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-65
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to delete a TCA profile instance.

DLT-TH-PROF
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
Select theFacilities node in the Alcatel-Lucent 1830 PSS ZIC selection tree.
...................................................................................................................................................................................................
Then select Threshold Profiles . Manage, either by selecting Action from the main
Result: The Show All TCA Assignment Profiles window is displayed.
...................................................................................................................................................................................................
In the displayed list select the TCA profile to be deleted.

...................................................................................................................................................................................................
Click Delete.
Result: The Delete Alarm Profile window is displayed.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-66
Issue 1 June 2013

Procedure 16-11: Retrieve a list of facilities that use a

particular TCA profile
....................................................................................................................................................................................................................................
Procedure 16-11: Retrieve a list of facilities that use a

particular TCA profile
When to use
Use this procedure to retrieve a list of facilities that use a particular TCA profile
RTRV-TCAP-ASGNMT
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................
...................................................................................................................................................................................................
Then select Threshold Profiles View Assignments, either by selecting Action from
Result: The View Assignments window is displayed.
...................................................................................................................................................................................................
In the fields User Label and Profile Type select the values to retrieve a list of the related
facilities.
...................................................................................................................................................................................................
Click Send.
Result: All related facilities are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-67
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
Contents
16-69
PM Data [Card]
16-70
16-72
Clear Bins [Card]
16-73
16-74
16-75
16-76
16-77
PM Data
16-78
16-80
Clear Bins
16-81
16-82
Port Baseline
16-84
....................................................................................................................................................................................................................................
1830 PSS
16-68
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to display PM data for EC/MTC1T9 card.

Before you begin
Instructions
Note: Card performance monitoring is supported for the EC/MTC1T9 card.

Card-level PM is not supported for other cards types.
...................................................................................................................................................................................................
In the WebUI, select the EC/MTC1T9 card and click the Performance function.
Result: The PM Data screen is displayed under the PM Report tab.
...................................................................................................................................................................................................
The WebUI allows a user to clear current 15-min, 1-day, and/or free running (i.e. raw
counter) bins on an EC/MTC1T9 card. This request will clear the bins for all monitored
types on the card. To clear bins, click on the Bins tab, check the appropriate box(es), and
click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-69
Issue 1 June 2013

PM Data [Card]
....................................................................................................................................................................................................................................
PM Data [Card]
Attribute
Value/Format
Additional Info
Date and Time
Date in MM/DD/YY format
Start date/time of the

collection period.
and Time in HH:MM:SS

AM/PM format
Time Period
{15-min, 1-day, Raw Count},

Bin {0-49}
The accumulation time period

for the retrieved PM
information and the bin
number.
Monitored Type
CPU Average
The type of monitored

parameter.
Heap Usage
Pool Usage
Monitored Value (%)
1-100
The value of the monitored

parameter.
Validity
Adjusted

information for the time
period was accumulated over
the entire time period or some
portion of the time period.
Complete
Long
Not Available
Partial
Adjusted data was manually

adjusted (that is reset via
Clear Bins) during the
accumulation time period.
Complete data was
accumulated during the entire
time period
Long data was accumulated
over longer than the indicated
time period.
Not Available data is not
available.
Parital data was
accumulated over some
No value default validity
value before any of the above
conditions are met.
....................................................................................................................................................................................................................................
1830 PSS
16-70
Issue 1 June 2013

PM Data [Card]
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Auto Refresh
(checkbox)
Specifies the time interval to

refresh the table.
....................................................................................................................................................................................................................................
1830 PSS
16-71
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to set bins for EC/MTC1T9 card.

Before you begin
Instructions
Note: Up to fifty historical bins for 1-day and 15-min are supported.
...................................................................................................................................................................................................
In the WebUI, select the EC/MTC1T9 card and click the Performance function.
Result: The PM Data screen is displayed.
...................................................................................................................................................................................................
Select the Settings tab.

Result: The PM Configuration screen is displayed.
...................................................................................................................................................................................................
To change settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-72
Issue 1 June 2013

Clear Bins [Card]
....................................................................................................................................................................................................................................
Clear Bins [Card]

Attribute
Additional Info
15-Minute
Select to reset the current 15-minute bin

(15-min, Bin 0) for the card.
1-Day
Select to reset the current 1-Day bin (1-day,

Bin 0) for the card.
Raw Counts
Select to reset the Raw Counts for the card.
....................................................................................................................................................................................................................................
1830 PSS
16-73
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to display all TCA profile assignments.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select System from the equipment tree and select Reports > TCA
Assignment.
Result: The TCA Profile Assignments are displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-74
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Value/Format
Additional Info
Source
<shelf/slot>,
<shelf/slot/port>
Card or Port identifier.
Profile Type
Card
The type of PM data. Each

Profile type has several
monitored parameters for
which threshold crossing
alerts (TCAs) can be
configured.
Digital Wrapper
DM
E1
Ethernet
Interface
OPR
OPT
ODURX
ODUTX
OTU
PCS
SDH
SONET
15-min Profile ID
{1-8}
Unique identifier of the TCA

profile for the profile type for
the 15-min collection interval.
1-day Profile ID
{1-8}
Unique identifier of the TCA

profile for the profile type for
the 1-day collection interval.
....................................................................................................................................................................................................................................
1830 PSS
16-75
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to modify TCA profile.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select System from the equipment tree and click the Performance
function.
Result: The TCA Profile Data screen is displayed.
...................................................................................................................................................................................................
Select the Profile Type and click Retrieve.

Result: Profile Data is displayed.
...................................................................................................................................................................................................
Select the Profile ID and click Details.

Result: Profile attributes are displayed.
...................................................................................................................................................................................................
To modify, enter the desired values and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-76
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to display PM data for port.

Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select the port and click the Performance function.
Result: The PM Data screen is displayed under the PM Report tab.
...................................................................................................................................................................................................
Select the PM group and click Retrieve.

Result: The PM report is displayed.
...................................................................................................................................................................................................
The WebUI will allow a user to clear current 15-min, 1-day, and/or free running (i.e. raw
counter) bins on a port. This request will clear the bins for all monitored types on the port.
To clear bins, click Clear Bins.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-77
Issue 1 June 2013

PM Data
....................................................................................................................................................................................................................................
PM Data
Attribute
Value/Format
Additional Info
PM Group
CD
Indicates the type of PM data

to retrieve. List of PM Groups
displayed is dependent on the
port type
DGD
Digital Wrapper
E1
Encryption
Ethernet
FOFF
Interface
OPIN
OPOCHIN
OPOCHOUT
OPOUT
OPR
OPT
OSNR
PCS
PreFEC Bits
SDH
SONET
Frequency
{9170~9605}
Date and Time

Time Period
Applicable to OPOCHIN,
OPOCHOUT and OSNR
groups only.
Start date/time of the
collection period.
{15-min, 1-day, Raw Count},

Bin {0-32}
The accumulation time period

for the retrieved PM
information and the bin
number.
Monitored Type
The type of monitored

parameter.
Monitored Value

monitored parameter.
....................................................................................................................................................................................................................................
1830 PSS
16-78
Issue 1 June 2013

PM Data
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Validity
Adjusted

information for the time
period was accumulated over
the entire time period or some
Complete
Long
Not Available
Partial
Adjusted data was manually

adjusted (that is reset via
Clear Bins) during the
accumulation time period.
Completedata was
accumulated during the entire
time period
Long data was accumulated
over longer than the indicated
time period.
Not Available data is not
available.
Parital data was
accumulated over some
No value default validity
value before any of the above
conditions are met.
Status
Updated
Not Updated
Auto Refresh
(checkbox)
Applicable to OSNR groups

only
Specifies the time interval to
refresh the table.
....................................................................................................................................................................................................................................
1830 PSS
16-79
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to set bins for port.

Before you begin
Instructions
Note: The WebUI will support setting the number of 15-min. and/or 1-day
accumulation bins on a port. Up to thirty-three 15-min historical bins and up to eight
1-day historical bins are supported.
...................................................................................................................................................................................................
Result: The PM Data screen is displayed.
...................................................................................................................................................................................................
Select Settings tab. Select the Profile Type and click Retrieve.
Result: The Port Configuration is displayed.
...................................................................................................................................................................................................
To change settings, enter parameters and click Submit.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-80
Issue 1 June 2013

Clear Bins
....................................................................................................................................................................................................................................
Clear Bins
Attribute
Additional Info
PM Group
Indicates the type of PM data.

If All is selected, this will reset the current
15-minute and 1-day bins for all PM groups on
the port.
15-Minute
Select to reset the current 15-minute bin

(15-min, Bin 0) for the selected PM Group.
1-Day
Select to reset the current 1-Day bin (1-day,

Bin 0) for the selected PM Group.
Raw Counts
Select to reset the Raw Counts for the selected

PM Group.
....................................................................................................................................................................................................................................
1830 PSS
16-81
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedure to set baseline values for port.

Before you begin
Instructions
Note: The WebUI will allow a user to view and set a baseline value for analog
parameters (OPR, OPT) on a port. The following port types support baselining:
10AN10G: {1-10}
10ET1G: {1-10}
24ANM: {1-24}
24ET1GB: {1-24}
112PDM11: L(1-4), C(1-10)
112SCA1, 112SNA1: L1
112SCA1, 112SNA1: C1
130SCUP: L1
130SCX10, 112SCX10, 112SNX10: L1,C{1-10}
11QCUPC: L(1-4), VA(1-4)
11STMM10: L1, C(1-10)

11STAR1, 11STAR1A: L1, C1
11STGE12: L1, C(1-10)
11DPE12, 11DPE12A, 11DPE12E: L{1,2}, VA{1,2}, C{1-12}

11DPM12: L{1,2}, VA{1,2}, C{1-12}
11QPA4, 11QPEN4: L(1-4), C(1-4), VA(1-4)

11QPE24: X{1-4}, VA{1-4}, C{1-22}
4DPA4: L(1,2), C(1-4), VA(1,2) for Card Mode = FlexMux
4DPA4: L(1,2), C(1,3), VA(1,2) for Card Mode = DualTran

4DPA2: L(1,2), C(1,2)
A2325A, AHPHG, AHPLG, ALPHG: OSC
OSCT: OSCSFP
A2P2125, AM2125A, AM2125B, AM2318A: OSCSFP
43SCA1: L1, C1
....................................................................................................................................................................................................................................
1830 PSS
16-82
Issue 1 June 2013

....................................................................................................................................................................................................................................
43SCGE1: L1
43STA1P: L1, C1
43SCX4, 43SCX4E, 43STX4, 43STX4P: L1, C(1-4)
MVAC: G{1-8}
MVAC8B: L(1-8), C(1-8)
SVAC: L1, C1
PTPCTL: P{1-6}
Note: For SVAC ports, OPT baselining is not supported on client ports and OPR
baselining is not supported on line ports.
...................................................................................................................................................................................................
Result: The PM Configuration screen is displayed.
...................................................................................................................................................................................................
Select Baseline tab.

Result: The Port Baseline screen is displayed.
...................................................................................................................................................................................................
To set baseline values, select Establish Baseline and enter Reason. Click Submit.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
16-83
Issue 1 June 2013

Port Baseline
....................................................................................................................................................................................................................................
Port Baseline
Attribute
Value/Format
Additional Info
Total Power Transmitted

Last Baselined Time
Date and time of the last

baseline.
Reason
Indicates the reason for the

last baseline.
Baselined Value (dBm)
Indicates the current baselined

value.
Establish Baseline
(checkbox)
Select to establish a baseline

OPR or OPT value for the
port. The purpose of the
baseline value is to provide a
basis from which to measure
parameter value deviation
from nominal.
Reason
New System
Specifies the reason for

baselining. {0-9} may be used
for user-defined values.
OT Replaced
{0-9}
LOS Cleared is not applicable

to OPT baseline.
Total Power Received
Last Baselined Time
Date and time of the last

baseline.
Reason
Indicates the reason for the

last baseline.
Baselined Value (dBm)
Indicates the current baselined

value.
Establish Baseline
(checkbox)
Select to establish a baseline

OPR or OPT value for the
port. The purpose of the
baseline value is to provide a
basis from which to measure
parameter value deviation
from nominal.
....................................................................................................................................................................................................................................
1830 PSS
16-84
Issue 1 June 2013

Port Baseline
....................................................................................................................................................................................................................................
Attribute
Reason
Value/Format
LOS Cleared
New System
OT Replaced
{0-9}
Additional Info
Specifies the reason for
baselining. {0-9} may be used
for user-defined values.
LOS Cleared is not applicable
to OPT baseline.
....................................................................................................................................................................................................................................
1830 PSS
16-85
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
Contents
16-87
PM reports General
16-89
16-92
16-93
16-94
16-95
PM reports Ethernet
16-96
16-97
16-98
16-99
16-100
....................................................................................................................................................................................................................................
1830 PSS
16-86
Issue 1 June 2013

Configuration parameters related to performance

monitoring
....................................................................................................................................................................................................................................

PM mode settings
Table 16-22
Parameters for the PM mode settings
Parameter
Details
Location
Specifies the location where PM data collection is to be enabled or disabled.

ALL - Near End and Far End
NEND - Near end
FEND Far End
For Alcatel-Lucent 1830 PSS , only near-end performance monitoring is supported.

Mode Type
Indicates the type of PM parameters to be monitored.

Values are:
Direction
PM parameters for Gigabit Ethernet:

MAC - MAC parameters
PM parameters for SDH facilities:

S - Regenerator Section (RS) parameters (STM-1, STM-4, STM-16, STM-64)
MS parameters are not applicable to transparent mapping applications.
PM parameters for SONET facilities:

S - Section parameters (OC-3, OC-12, OC-48, OC-192)
Line parameters are not applicable to transparent mapping applications.
PM parameters for OTH facilities:

P - ODU path parameters
S - OTU parameters
T - TCM layer parameters
O Optical physical layer parameters
Specifies the direction of the signal being monitored.

ALL - All supported directions
For Alcatel-Lucent 1830 PSS , only performance monitoring in the receive direction is
supported.
....................................................................................................................................................................................................................................
1830 PSS
16-87
Issue 1 June 2013

Configuration parameters related to performance

monitoring
....................................................................................................................................................................................................................................
Table 16-22
Parameters for the PM mode settings
(continued)
Parameter
Details
PM State
Specifies whether the PM data collection for the corresponding Mode Type is enabled or
disabled.
Values are:
Time Period
ON - PM for the specified Mode Type is enabled.
DISABLED - PM for the specified Mode Type is disabled.
This parameter specifies whether the 15-minutes or 1-day PM register or both are to be
reported.
Related information
See also PM reports General (p. 16-89).
....................................................................................................................................................................................................................................
1830 PSS
16-88
Issue 1 June 2013

PM reports General
....................................................................................................................................................................................................................................
PM reports General
PM data selection
The following parameters are available for the PM data selection:

Table 16-23
Parameters for the PM data selection
Parameter
Details
AID
In the AID field, you can specify whether PM data retrieval shall be triggered for a
particular type of facility or for all facilities of a particular type.
Monitored
parameter type
This parameter can be used to select the desired PM parameter to be monitored.

It is possible to restrict a PM report to a particular PM parameter, for example CVS
(Number of code violations in the SONET Section), or, as an alternative, the values of
all PM parameters pertaining to the specified facility can be retrieved by selecting
ALL.
The supported parameters depend on the type of facility; see:
PM reports Ethernet (p. 16-96)
The default setting is ALL.

Monitor level
This parameter specifies the discrimination level of PM parameter values to be

reported for the specified Monitored parameter type.
The format and possible values of the Monitor level are as follows:
{0-4294967295} - DN (for example: 2400 - DN)
<Level> - Down; only those PM data for the specified parameter are reported that
are less-than or equal-to () the given level (2400 in the example).
{0-4294967295} - DNORNCMPL (for example: 2400 - DNORNCMPL)
<Level> - Down or Not Complete; only those PM data for the specified parameter
are reported that are less-than or equal-to () the given level (2400 in the example),
or which do not have a validity indication of COMPL (complete).
{0-4294967295} - UP (for example: 2400 - UP)
<Level> - Up; only those PM data for the specified parameter are reported that are
greater-than or equal-to () the given level (2400 in the example).
{0-4294967295} - UPORNCMPL (for example: 2400 - UPORNCMPL)
<Level> - Up or Not Complete; only those PM data for the specified parameter are
reported that are greater-than or equal-to () the given level (2400 in the example),
or which do not have a validity indication of COMPL (complete).
....................................................................................................................................................................................................................................
1830 PSS
16-89
Issue 1 June 2013

PM reports General
....................................................................................................................................................................................................................................
Table 16-23
(continued)
Parameter
Details
Location
This parameter specifies the location where PM data collection is to be enabled or

disabled.
Direction
NEND - Near end
FEND - Far end
This parameter specifies the direction of the signal being monitored.

For Alcatel-Lucent 1830 PSS , only performance monitoring in the receive direction is
supported.
Time Period
This parameter specifies whether the 15-minutes or 1-day PM register or both are to be
reported.
Monitor Date
This parameter specifies the (starting) date of the PM collection period for which PM
data is to be reported. The format of the Monitor Date is MM-DD (month-day).
The default setting is the current date.
Monitor Time
If the Time Period is set to 15-MIN or BOTH, then the Monitor Time parameter
specifies the (starting) time of the PM collection period for which PM data is to be
retrieved. If the Time Period is set to 1-DAY, then the value of the Monitor Time
parameter is ignored. The format of the Monitor Time is HH-MM (hour-minute).
The minutes {0-14}, {15-29}, {30-44}, and {45-59} specify the first, second, third,
and fourth 15-minutes period, respectively, within the specified hour.
The default setting is the current hour and beginning of the current 15-minutes window.
Number of
15-minute registers
This parameter indicates how many historical 15-minutes registers are to be reported in
addition to that PM register specified by means of the Monitor Date and Monitor Time
parameters.
The register specified by means of the Monitor Date and Monitor Time parameters will
be the first output followed by the Number of 15-minute registers previous registers.
0-32 - 0-32 historical 15-minutes PM data registers are to be reported.
ALL - All historical 15-minutes PM data registers are to be reported.
....................................................................................................................................................................................................................................
1830 PSS
16-90
Issue 1 June 2013

PM reports General
....................................................................................................................................................................................................................................
Table 16-23
(continued)
Parameter
Details
Number of 1-day
registers
This parameter indicates how many historical 1-day registers are to be reported in
addition to that PM register specified by means of the Monitor Date and Monitor Time
parameters.
The register specified by means of the Monitor Date and Monitor Time parameters will
be the first output followed by the Number of 1-day registers previous registers.
0-7 - 0-7 historical 1-day PM data registers are to be reported.
ALL - All historical 1-day PM data registers are to be reported.
....................................................................................................................................................................................................................................
1830 PSS
16-91
Issue 1 June 2013

....................................................................................................................................................................................................................................

Parameters and value ranges
These are the parameters of the SDH Regenerator Section performance monitoring
reports that are returned by the NE:
Parameter
Description
Value range
15-minutes
measurements
1-day measurements
OFS-RS
Out Of Frame Seconds - Regenerator Section
0 - 900
0 - 86400
BBE-RS
Background Block Errors (BBE) - Regenerator Section
0 - 2159100
0 - 207273600
ES-RS
Errored Seconds (ES) - Regenerator Section
0 - 900
0 - 86400
SES-RS
Severely Errored Seconds (SES) - Regenerator Section
0 - 810
0 - 77760
UAS-RS
Unavailable Seconds (UAS) - Regenerator Section
0 - 900
0 - 86400
Notes:
1.
The value ranges apply to STM-1, STM-4, STM-16 as well as STM-64 signal levels.
2.
All listed parameters are related to near-end performance monitoring. There is no far-end performance
monitoring for the SDH Regenerator Section.
3.
In addition to the value of each parameter, the time, date, and validity of the data (see Validity indication
(p. 16-50)) is returned by the NE for each parameter.
Related information
Please also see SDH/SONET near-end performance parameters (p. 16-9).
....................................................................................................................................................................................................................................
1830 PSS
16-92
Issue 1 June 2013

....................................................................................................................................................................................................................................

These are the parameters of the SDH higher order path performance monitoring reports
that are returned by the NE:
Parameter
Description
Value range
15-minutes
measurements
1-day measurements
BBE-HOVC
Background Block Errors (BBE) - SDH higher order

path
0 - 7199100
0 - 691113600
ES-HOVC
Errored Seconds (ES) - SDH higher order path
0 - 900
0 - 86400
SES-HOVC
Severely Errored Seconds (SES) - SDH higher order

path
0 - 810
0 - 77760
UAS-HOVC
Unavailable Seconds (UAS) - SDH higher order path
0 - 900
0 - 86400
Notes:
1.
The value ranges apply to all signal levels (VC-4, VC-4-4c, VC-4-16c, VC-4-64c for terminated higher order
paths, AU-4, AU-4-4c, AU-4-16c, AU-4-64c for unterminated higher order paths).
2.
Related information
Please also see SDH/SONET near-end performance parameters (p. 16-9) .
....................................................................................................................................................................................................................................
1830 PSS
16-93
Issue 1 June 2013

....................................................................................................................................................................................................................................

These are the parameters of the SONET Section performance monitoring reports that are
returned by the NE:
Parameter
Description
Value range
15-minutes
measurements
1-day measurements
CVS
Code Violations (CV) - Section
0 - 16383
0 - 1048575
ESS
Errored Seconds (ES) - Section
0 - 900
0 - 65535
SESS
Severely Errored Seconds (SES) - Section
0 - 900
0 - 65535
SEFSS
Severely Errored Framing Seconds (SEFS) - Section
0 - 900
0 - 65535
UASS
Unavailable Seconds (UAS) - Section
0 - 900
0 - 65535
Notes:
1.
The value ranges apply to OC-3, OC-12, OC-48 as well as OC-192 signal levels.
2.
All listed parameters are related to near-end performance monitoring. There is no far-end performance
monitoring for the SONET Section.
3.
Related information
Please also see SDH/SONET near-end performance parameters (p. 16-9).
....................................................................................................................................................................................................................................
1830 PSS
16-94
Issue 1 June 2013

....................................................................................................................................................................................................................................

These are the parameters of the SONET path performance monitoring reports that are
returned by the NE:
Parameter
Description
Value range
15-minutes
measurements
1-day measurements
CVP
Code Violations (CV) - Path
0 - 16383
0 - 1048575
ESP
Errored Seconds (ES) - Path
0 - 900
0 - 65535
SESP
Severely Errored Seconds (SES) - Path
0 - 900
0 - 65535
UASP
Unavailable Seconds (UAS) - Path
0 - 900
0 - 65535
Notes:
1.
SONET path includes the signal rates STS-1, STS-3c, STS-12c, STS-48c, and STS-192c.
2.
Related information
Please also see SDH/SONET near-end performance parameters (p. 16-9) .
....................................................................................................................................................................................................................................
1830 PSS
16-95
Issue 1 June 2013

PM reports Ethernet
....................................................................................................................................................................................................................................
PM reports Ethernet
These are the Ethernet performance parameters (1 GbE and 10 GbE) that are returned by
the NE:
Parameter
Description
Value range
1-day measurements
EINB
Ethernet Incoming Number of Bytes
0 - 281474976710655
0 - 281474976710655
EONB
Ethernet Outgoing Number of Bytes
0 - 281474976710655
0 - 281474976710655
EINF
Ethernet Incoming Number of Frames
0 - 281474976710655
0 - 281474976710655
EONF
Ethernet Outgoing Number of Frames
0 - 281474976710655
0 - 281474976710655
EIFE
0 - 281474976710655
0 - 281474976710655
EOFE
0 - 281474976710655
0 - 281474976710655
ETH-SYMERR
0 - 4294967295
0 - 4294967295
Notes:
1.
2.
For the ETH-SYMERR parameter, no historical data are stored.
Related information
Please also see Ethernet performance parameters (p. 16-10).
....................................................................................................................................................................................................................................
1830 PSS
16-96
Issue 1 June 2013

....................................................................................................................................................................................................................................

These are the performance monitoring parameters related to the OTUk Section that are
returned by the NE:
Parameter
Description
Value range
15-minutes
measurements
1-day measurements
ES-OTU
Errored Seconds (ES) - OTU
0 - 900
0 - 86400
SES-OTU
Severely Errored Seconds (SES) - OTU
0 - 810
0 - 77760
BBE-OTU
Background Block Errors (BBE) - OTU
OTU2
11073600
1063065600
OTU2E
11473110
1101418560
OTU3
44481600
4270233600
OTU3E2
46099584
4294967295
OTU4
115612380
11098788480
0 - 900
0 - 86400
0 - 4294967295
0 - 4294967295
0 - 1006289762112
0 - 96603817162752
UAS-OTU
Unavailable Seconds (UAS) - OTU
FECC
Forward Error Correction - corrected
OTU2
OTU2E
OTU3
OTU3E2
OTU4
Notes:
1.
The FECC count is the accumulated number of detected and corrected FEC code violations per frame, over
the current accumulation period. Note that the FECC counter is not incremented during the times when a
LOS, LOF, LOM or AIS defect is present.
....................................................................................................................................................................................................................................
1830 PSS
16-97
Issue 1 June 2013

....................................................................................................................................................................................................................................

These are the performance monitoring parameters related to the ODUk Path that are
returned by the NE:
Parameter
Description
Value range
15-minutes
measurements
1-day measurements
ES-ODU
Errored Seconds (ES) - ODU
0 - 900
0 - 86400
SES-ODU
Severely Errored Seconds (SES) - ODU
0 - 810
0 - 77760
BBE-ODU
Background Block Errors (BBE) - ODU
ODU0
1378350
132321600
ODU1
2757600
264643200
ODU2
11073600
1063065600
ODU2E
11473110
1101418560
ODU3
44481600
4270233600
ODU3E2
46099584
4294967295
ODU4
115612380
11098788480
0 - 900
0 - 86400
UAS-ODU
Unavailable Seconds (UAS) - ODU
....................................................................................................................................................................................................................................
1830 PSS
16-98
Issue 1 June 2013

....................................................................................................................................................................................................................................

These are the performance monitoring parameters related to the ODUk TCM Layer that
are returned by the NE:
Parameter
Description
Value range
15-minutes
measurements
1-day measurements
ES-TCM
Errored Seconds (ES) - ODU TCM Layer
0 - 900
0 - 86400
SES-TCM
Severely Errored Seconds (SES) - ODU TCM Layer
0 - 810
0 - 77760
BBE-TCM
Background Block Errors (BBE) - ODU TCM

Layer
ODU0T
1378350
132321600
ODU1T
2756700
264643200
ODU2T
11073600
1063065600
ODU2ET
11473110
1101418560
ODU3T
44481600
4270233600
ODU3E2T 46099584
4294967295
ODU4T
115612380
11098788480
0 - 900
0 - 86400
UAS-TCM
Unavailable Seconds (UAS) - ODU TCM Layer
....................................................................................................................................................................................................................................
1830 PSS
16-99
Issue 1 June 2013

....................................................................................................................................................................................................................................

Purpose
OCH near-end section layer parameters are monitored on DWDM uplink OCH on OTU2,
OTU2e, and OTU3e2 ports of the switchponder card 43SCUP and 130SCUP.
These are the performance monitoring parameters related to the OCH section near end
that are returned by the NE:
Parameter
Region
Description
Direction
Value range
15-minutes
measurements
1-day
measurements
OPR-AVG
ANSI
Optical Power Received -Average
RCV
NA
NA
OPR-H
ANSI
Optical Power Received -Tide Mark

High
RCV
4 to 9.9
4 to 9.9
ETSI

High
RCV
4 to 9.9
4 to 9.9
ANSI

Low
RCV
-5 to -9.9
-5 to -9.9
ETSI

Low
RCV
-5 to -9.9
-5 to -9.9
OPT-AVG
ANSI
Optical Power Transmitted -Average
TRMT
NA
NA
OPT-H
ANSI
Optical Power Transmitted -Tide

Mark High
TRMT
4 to 9.9
4 to 9.9
ETSI

Mark High
TRMT
4 to 9.9
4 to 9.9
ANSI

Mark Low
TRMT
-5 to -9.9
-5 to -9.9
ETSI

Mark Low
TRMT
-5 to -9.9
-5 to -9.9
OPR-L
OPT-L
....................................................................................................................................................................................................................................
1830 PSS
16-100
Issue 1 June 2013
17
17
Database
backup and
restore procedures
Overview
Purpose
This chapter describes the procedures for Alcatel-Lucent 1830 PSS NE database backup
and Alcatel-Lucent 1830 PSS NE database restore. Furthermore, the procedure for
retrieving information about the current NE database is provided.
Contents
17-3
Configuration backup and restoration
17-4
Backup and restore principle
17-5
17-6
Database management
17-7
Database backup
17-12
Database restore
17-14
17-16
Procedure 17-1: Backup the active database to the standby database
17-17
Procedure 17-2: Transfer the NE standby database to a remote file server
17-18
Procedure 17-3: Retrieve information related to transferred files on a remote file

server
17-22
Information related to database backups stored on a remote file server.
17-24
Procedure 17-4: Download a database from a remote file server to the standby
database
17-27
Procedure 17-5: Restore database
17-30

Procedure 17-6: Backup database
17-32
17-33
...................................................................................................................................................................................................................................
1830 PSS
17-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
Database Backup and Restore
17-34
17-36
....................................................................................................................................................................................................................................
1830 PSS
17-2
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides descriptive information on features related to NE database backup

and restore.
Related information
For step by step operating instructions, see OCS backup and restore procedures
(p. 17-16).
Contents
17-4
17-5
....................................................................................................................................................................................................................................
1830 PSS
17-3
Issue 1 June 2013

....................................................................................................................................................................................................................................

Overview
The volatile memory database (ACTV CPU DB) is maintained by the NE and reflects the
NE configuration, its alarm states and conditions. Two non-volatile disk database types
shall exist for the NE: the primary backup database (ACTV DSK DB) and the secondary
backup data base (STBY DB).
The databases also contain control plane related configuration, alarm states and
conditions. These control plane related data are seen as an integral part of the NE
database.
The primary backup database is maintained implicitly by the NE during its normal
operation. At any time, it reflects the state of the NE's volatile memory database.
Updating the primary backup database occurs online without interrupting the NE's normal
service operation.
The primary backup database can be copied to the secondary backup database by an
operator command (backup). The secondary backup database can be copied to the
primary backup database. After an FLC restart (or FLC switch) the memory database will
be reloaded from the restored disk database.
The secondary backup database can be copied to/from a remote file server (RFS) by
operator commands.
The NE supports autonomous reporting of memory database changes, in particular,
changes to provisioning state of the equipment and the facilities.
The backup and restore mechanism provides additional safety, for instance if a HW
problem occurs, which cannot be solved by redundancy mechanisms. In such a situation
the system is not operable anymore. Usually the defective HW (for instance the FLC) will
be changed and the software will be installed again. If you have saved the latest
configuration as a backup, you can easily restore that configuration.
Therefore, it is recommended to make a backup of the NE configuration database, each
time after you have made an important change of the NE's configuration, like for instance
after creation of new cross-connections or changing the Control System configuration.
....................................................................................................................................................................................................................................
1830 PSS
17-4
Issue 1 June 2013

....................................................................................................................................................................................................................................

Mass Storage
The system is equipped with redundant mass storage devices (SSD), that store all system
non-volatile data (for instance SW images, DB configurations, log files). The database
and NE software is only stored on the main shelf FLCs. The active FLC performs a file
replication mechanism with the standby FLC to keep them synchronized.
Backup storage
A backup is stored on the Alcatel-Lucent 1830 PSS. Making another backup will
overwrite the last one. If you want to keep a backup, you have to upload the backup from
the Alcatel-Lucent 1830 PSS to a remote server or to the Alcatel-Lucent 1830 PSS ZIC
supporting host. The other way round, if you want to restore any backup that you have
stored on a server, you have to download that backup to the Alcatel-Lucent 1830 PSS
before you can restore it.
To ensure that a backup is kept safely, make a second copy on another storage medium
like for instance CD-ROM (storing on CD-ROM is not explicitly described in this
chapter).
The figure below shows different locations of backups and the necessary operations to
transfer a backup to another location:
Alcatel-Lucent 1830 PSS
Server
CD-ROM
upload
manually
copy
download
g-upg-0074
....................................................................................................................................................................................................................................
1830 PSS
17-5
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section provides descriptive information on features related to NE database backup

and restore.
Related information
For step by step operating instructions, see WDM backup and restore procedures using
WebUI (p. 17-32).
Contents
Database management
17-7
Database backup
17-12
Database restore
17-14
....................................................................................................................................................................................................................................
1830 PSS
17-6
Issue 1 June 2013

Database management
....................................................................................................................................................................................................................................
Database management
Introduction
An Alcatel-Lucent 1830 PSS NE maintains all of its configuration data in an active

non-volatile memory database. The NE provides mechanisms that allow a user to backup
the active non-volatile memory database to a database file on a Remote File Server (RFS)
and to restore the active database from a file on the RFS. In the database backup process,
a temporary copy of the active database is first created and then transferred to the RFS. In
the database restore process, the remote database file is first transferred to the NE where it
is validated. If the transferred database is valid and restored, then the NE automatically
restarts as part of the installation of the newly downloaded database. After the restart, the
restored database becomes the active database.
As a maintenance feature, the NE allows the operator to reset its active database to a
factory installed default configuration.
The NE supports autonomous messages to report all changes to the provisioning database,
equipment installation or removal, equipment or facility failure or recovery.
Database overview
Before the NE can access the software and database servers, the NE must be configured
to point at the servers. Separate commands are used to configure the databases and
software servers. The servers must reside on a computer that is accessible from the NE.
The servers can be on the same computer or they can reside on two different computers.
The active non-volatile memory database is maintained by the NE and reflects the NE
configuration and NE provisioning. A temporary copy of the active database is created by
the NE before file transfer to an RFS. A temporary database space is also the destination
for remote file transfer from the RFS. The NE supports autonomous reporting of changes
to the active database that come about as the result of provisioning and configuration
changes.
Redundancy
The NE non-volatile memory (flash memory card) is considered to be part of the active
main EC. In the case of a redundant controller configuration, the system assures
consistency of non-volatile memory contents between the active and standby main shelf
controllers.
The system is responsible for replicating any change to the NE active database on the
active Main EC to the corresponding database on the standby Main EC (if available). In
particular, the implementation of the operations for creation of a database backup and
download of a database backup to the active Main EC is expected to have the
corresponding effects on the standby Main EC.
....................................................................................................................................................................................................................................
1830 PSS
17-7
Issue 1 June 2013

Database management
....................................................................................................................................................................................................................................
After reboot or insertion of a standby EC, an EC LED will indicate a status of Software
Download (flashing amber) until the standby database image is synchronized with the
primary.
Note: For 1830 multi-shelf configuration, if one shelf is redundant, all shelves should
be redundant.
Local database operations
Any failures in updating the database are reported by the NE. After a power failure, or in
the cases of severe faults, the system is capable of being automatically restored from the
active non-volatile memory database to the latest stable and consistent configuration that
existed before the failure occurred.
The system provides the ability to restore the active database (from the remote database),
and thus enable normal operations via each of the supported user interfaces. NE
software has a method for verifying the valid state of locally stored databases (e.g.,
checksum procedure).
The NE software checks to make sure that the SW database version is compatible with the
software generic. If not, or if the NE detects existence of an obsolete (i.e. no longer
supported) database, a corrupt or empty database, or a database from another system, the
database is marked as being invalid. No more than one database backup, database restore,
active and standby database synchronization, or software download operation is allowed
at the same time on the NE.
Remote database operations
The NE provides the capability to transfer database files from the local storage area on
the disk to a remote storage area on a RFS and vice-versa. Using this capability, operators
can perform remote database backup and remote database restore.
The NE supports the ability to retrieve information on a backed up database currently
existing on an RFS. Information includes the SID, NE type, and release of the NE on
which the backup took place, and the date and time at which the backup occurred. The
NE supports the ability to back up the active database to a database file on a Remote File
Server and to restore the NE database from a backup database on a Remote File Server.
The file transfer functionality works with any RFS supporting an IP connection, a
standard FTP file server, and also in an environment in which the Secure Shell transport
protocol (SSH), running on top of TCP/IP, yields a secure FTP file transport capability.
Note: The system does not automatically resume a previously started remote file
transfer operation (either direction) that was interrupted by an NE restart or Main EC
protection switch.
....................................................................................................................................................................................................................................
1830 PSS
17-8
Issue 1 June 2013

Database management
....................................................................................................................................................................................................................................
Database file identification data
Each database file that is created with the BackupDatabase command maintains the
following data identifiers:
SYSTYPE - System Type on which the database was created.

RLSID <1-20 CHARACTER> - Software Release identifier of the system software
the database was created with.
SID <1-20 CHARACTER SID> - System Identifier, identifies the provisioned system
identification.
BACKUP-DATE {YY-MM-DD:{08-99}-{1-12}-{1-31}} - Backup Date
BACKUP-TIME {HH:MM:SS:{0-23}:{0-59}:{0-59}} - Backup Time
Note: the active database, and for RFS database files, the BACKUP-DATE and
BACKUP-TIME values are the date and time, as reported by the NE, when the
backup was actually done.
CRC <8 UPPER CASE HEXADECIMAL CRC CHARACTERS> - 32-bit Cyclic

Redundancy Code calculated over the backed-up data.
Database information records
The active database contains records indicating when the database has been backed up.
The following specifies initial and subsequent values of that data:
Until a database backup is first done, the BACKUP-DATE and BACKUP-TIME

values associated with a database is null.
When a database is backed up, the following records are modified:
the Remote File Server (RFS) IP address
the RFS port number to which the file transfer is to connect
the directory on the RFS to which the database is backed up. This is equivalent to
the path on the RFS, to the directory where the database file resides.
the name of the remote database file
the BACKUP-DATE and BACKUP-TIME.
The NE writes or modifies all of the data specified above before the active Main
EC-resident temporary database copy is made.
The default filename format for each remote backup database file on the RFS is:
NEname_SWgeneric_yyyy-mm-dd_hh-mm-ss.bak
Note: It is possible for the user to override the default filename format, but the .bak
file extension must be used.
....................................................................................................................................................................................................................................
1830 PSS
17-9
Issue 1 June 2013

Database management
....................................................................................................................................................................................................................................
Database failure and/or loss of synchronization
The following conditions apply:
A download of a database backup from the RFS (part of the database restore process)
will fail if there is not enough free space on the Active Main ECs flash memory. A
database failure condition-local (DBFL alarm) is raised.
A database backup (to an RFS database file) will fail if a copy of the active database
cannot be created because there is not enough free space on the Main ECs
non-volatile memory. If this occurs, a database failure condition-local (DBFL alarm)
is raised.
Any database failure condition that occurs during a database backup is cleared the
next time that a database backup is attempted.
In a duplex controller environment:
If the active Main EC database fails, the NE effects an automatic switch to the
standby Main EC.
If the standby Main EC controller fails, the standby EC becomes unavailable for
automatic protection, and an appropriate alarm/condition is raised.
A database synchronization failure alarm is raised if the active EC card is unable
to synchronize its database with the standby EC card.
In a simplex controller environment, if the NE database fails, an alarm is raised

indicating the issue with the database.
Note: When switching from active Main EC to standby Main EC, OSC data link
down alarm is raised on adjacent nodes for a few seconds and then the alarms are
cleared.
Note: There is a limit of one software download at a time over OTU1 rate GCC.
Simultaneous remote software downloads should not be performed over OTU1 rate
GCC.
Secure file transfer
The database backup and restore operations support the option of encrypted file transfer,
SFTP, using SSH (see System security features (p. 2-26)). The following applies:
Database backup and restore commands using SFTP will be denied if the Network
Element SSH Key is not initialized.
When the 1830 PSS-32/PSS-16/PSS-32S database server is configured for the SFTP
protocol and the NE receives a backup database or restore database command, the NE
will establish an SSH connection with the external SSH server on the RFS over which
the encrypted file transfer can take place.
....................................................................................................................................................................................................................................
1830 PSS
17-10
Issue 1 June 2013

Database management
....................................................................................................................................................................................................................................
The database server protocol parameter is independent of the security mode

parameter. Regardless of the security mode of the NE (encrypted or normal), the file
transfer protocol supports provisioning as SFTP, FTP or TFTP.
At the beginning of an encrypted file transfer backup database or restore database

command execution, the command software checks whether the NE has a valid SSH
key, and denies the command if one does not exist for this NE.
....................................................................................................................................................................................................................................
1830 PSS
17-11
Issue 1 June 2013

Database backup
....................................................................................................................................................................................................................................
Database backup
Overview
The system provides the capability for the user to backup the NE active database to a
Remote File Server. The process of doing a remote backup can be split into two different
phases: first, create a temporary copy of the active database on the NE; second, send this
database file to its remote storage destination. The following sequence outlines the
general principle for the backup of an NE database on a Remote File Server:
1. An initiator, often a managing system, sends a command to initiate the database
backup.
2. The NE makes a temporary copy of the active database.
3. After the temporary database has been created, the NE sends a message to the RFS
initiating the file transfer.
The following conditions apply to a database backup:
The database is updated after configuration-affecting commands have been processed,

and after any autonomous configuration changes have been performed by the NE, in
such a way as to guarantee that no configuration changes of the database changes are
lost.
Note: The NE does not maintain the current alarm situation of the system in the
database. The actual alarm situation is recovered from the NE at restart time.
Database backup operation occurs with minimal impact to normal service operations
and does not impact service.
Only one database backup, database restore, or software download is allowed on a

system at any given time. Input of a second instance of any of these commands will
be denied if the action of the previous command has not yet completed.
User commands are not rejected due to ongoing backup activity; they are instead
queued and are executed after completion of an in-progress command that is
accessing the database.
Note: This applies primarily during creation of the temporary database on the EC.
Thus new commands are allowed while transfer of a database file to the RFS is
occurring.
A database backup operation will backup the entire database content. The following
items are not part of the database and therefore are not backed up.
event logs
active alarms and conditions
site-specific data
The database backup operation writes database file identification information to
records in the active DB and the backed up database on the Remote File Server.
....................................................................................................................................................................................................................................
1830 PSS
17-12
Issue 1 June 2013

Database backup
....................................................................................................................................................................................................................................
The database backup operation includes a data integrity verification of the temporary
database.
The NE accomplishes the generation of database backups in 15 minutes or less.
Database backup failure conditions
If the temporary database cannot be read (meaning that the database cannot be
transported to the RFS) , a database failure condition-local (DBFL alarm) is set
against common equipment.
If the file transfer of the database to the RFS does not succeed, a database failure
condition-transport is set against common equipment.
The NE denies a request to back up the active database when:
a database backup event is currently in progress
a database restore event is currently in progress
an in-service upgrade event is in progress

an Initialize System event is in progress (via an Initialize System request).
Each of the Database Backup Failure condition types is a standing condition declared
against the COM entity. Each such condition is cleared when a Database Backup or
Database Restore is next attempted.
....................................................................................................................................................................................................................................
1830 PSS
17-13
Issue 1 June 2013

Database restore
....................................................................................................................................................................................................................................
Database restore
Overview
The system provides the capability for the user to download a previously backed up
database from a Remote File Server and to then have this database automatically
activated on the NE. The process of restoring an NEs working database is twofold - first,
download a backup from a remote location onto a target NE; second, restart the NE with
the downloaded database. The following sequence outlines the general principle for the
restoration of an NE's active database from a Remote File Server:
1. An initiator (often an OS) sends a command (RestoreDatabase) to the NE to initiate
the process of downloading a database from the RFS and then activating it on the NE.
2. The NE requests the download from the RFS and begins storing the downloaded file
as a temporary database on the active Main EC.
3. The NE marks the temporary database as the active database.
4. System software restarts the NE.
The following conditions apply to a database restore:
The NE outputs an autonomous message for each of the following database

restoration occurrences:
Database restoration has completed successfully meaning that the transfer and
data validation of the remote database file has completed successfully.
Database restoration has failed meaning that the transfer and data validation of
the remote database file has failed.
Database restoration has begun meaning that the external FTP session has begun.
The following conditions apply to SID
The NE SID is preserved in a database restoration if the database file being
restored came from the same SID (i.e. the database is being restored to the NE
from which the database was backed up)
If the restored database comes from a different NE, the SID will be changed to the
SID that is in the database being restored.
An NE's SID survives all types of NE restarts.

When the database is restored, site-specific configuration data (e.g. NE network
addresses, routing configuration) are not preserved.
Note: When the NE restarts, all active alarms and conditions are reported.
Database restoration does not interrupt or interfere with traffic on connections that are
not altered by the restoration.
....................................................................................................................................................................................................................................
1830 PSS
17-14
Issue 1 June 2013

Database restore
....................................................................................................................................................................................................................................
Nativity check
The database restore command checks that the serial number of the User Panel is the
same as that in the database being restored. If not, the database is marked invalid after the
restore operation completion. It is possible to restore to an NE any remote database file
whose SID is the same as the SID of the NE that has received a database restore request.
In other words, the nativity of the database file to be restored must be that it originated
on the NE that is initiating the restore.
Note: For a User Panel replacement, the database restore operation supports a
forced option, where the restore is allowed despite failed nativity checks (see
Procedure 17-7: Restore database (p. 17-36)).
Database restore failure conditions
Important! On any restart, if the database is not aligned with the SW, or is otherwise
corrupted, the database is declared invalid. It is then the user's responsibility to either
restore a proper database or to clear the database. The NE saves some parameters
(SID, OAMP IP address, etc.) to SEEPROM. In case of a database corruption, the NE
will still be reachable and will have network connectivity. This will allow the user to
attempt to restore a good known database to the NE.
The NE system will deny the Restore Database request for any of the following reasons:
When software release upgrade is in progress (via a Start In-Service Upgrade

request).
When a system restart is in progress (via an Initialize System request).
The database to be restored has a database read error or the CRC does not match the
calculated CRC on the media.
A database restore event is presently in progress.
A database backup event is currently in progress.
The remote database version number is not compatible with the software generic that
is currently on the NE.
....................................................................................................................................................................................................................................
1830 PSS
17-15
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section describes the procedures for Alcatel-Lucent 1830 PSS NE database backup
and Alcatel-Lucent 1830 PSS NE database restore for the OCS application.
Contents
Procedure 17-1: Backup the active database to the standby database
17-17
Procedure 17-2: Transfer the NE standby database to a remote file server
17-18

server
17-22
Information related to database backups stored on a remote file server.
17-24
database
17-27
17-30
....................................................................................................................................................................................................................................
1830 PSS
17-16
Issue 1 June 2013

Procedure 17-1: Backup the active database to the standby

database
....................................................................................................................................................................................................................................
Procedure 17-1: Backup the active database to the standby

database
When to use
Use this procedure to backup the primary backup data base to the secondary backup data
base (STBYDB) of the Alcatel-Lucent 1830 PSS NE.
ACT-DB-BACKUP
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select Database Operations Start DB Backup, either by selecting Action from
Result: The Alcatel-Lucent 1830 PSS ZIC Start Database Backup window opens.
...................................................................................................................................................................................................
Click Send.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
17-17
Issue 1 June 2013

Procedure 17-2: Transfer the NE standby database to a

remote file server
....................................................................................................................................................................................................................................
Procedure 17-2: Transfer the NE standby database to a remote

file server
When to use
Use this procedure to transfer the configuration data of an NE to a remote file server.
COPY-RFILE
ACT-DB-BACKUP
The system state should be saved regularly both as a safety measure and a maintenance
activity in order to be able to restore the saved state at any future time.
Important! Ensure that a backup is made after you have changed the configuration of
the Alcatel-Lucent 1830 PSS.
The backup will be stored on the Alcatel-Lucent 1830 PSS (on both FLCs).
During the backup procedure, the persistency data, application configuration data and
control system configuration data of the NE are saved. If the NE supports GMRE, the
GMRE configuration is saved as well.
For redundant systems (that means with redundant FLCs)
Due to the redundant system control, there is no interruption on the active FLC during
the backup.
While the backup procedure is running, the standby FLC is not available.
For stand-alone systems (that means with only one FLC):
The FLC is not available while the backup procedure is running,

The NE cannot be controlled or managed during this time.
Before you begin

have a running SFTP server to transfer the database to
....................................................................................................................................................................................................................................
1830 PSS
17-18
Issue 1 June 2013


remote file server
....................................................................................................................................................................................................................................
Required equipment
Instructions
...................................................................................................................................................................................................
At first backup the active database to the standby database.

See Procedure 17-1: Backup the active database to the standby database (p. 17-17).
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS ZIC selection tree select System .

...................................................................................................................................................................................................
In the field From select STBYDB.

...................................................................................................................................................................................................
In the field To select RFSDB.

...................................................................................................................................................................................................
In the field LOCATION:Remote File Server(IP Addr.) enter the IP address of the host (the
remote file server).
...................................................................................................................................................................................................

...................................................................................................................................................................................................
In the field Protocol select the protocol to be used for file transfer.
sftp
secure file transfer protocol
....................................................................................................................................................................................................................................
1830 PSS
17-19
Issue 1 June 2013


remote file server
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
RFS.
...................................................................................................................................................................................................
RFS.
Note: For use of the local sftp host, the user/password are defined during the sftp
server configuration on the RFS.
...................................................................................................................................................................................................
10
In the field LOCATION:Url-Path enter the Remote File Server Path:

This value supplies the details of how the specified resource (that means the directory
where the file(s) reside) can be accessed. It has the following syntax:
[/]<cwd1>/<cwd2>/.../<cwdN> where <cwd1> to <cwdN> are strings that identify
directories. With a leading '/' character, the path is interpreted as an absolute file path
inside the Remote File Server's file system. Without the optional leading '/' character, the
path is interpreted as a file path relative to the users's login directory.
...................................................................................................................................................................................................
11
Keep the Command Execution mode set to NoValue.

...................................................................................................................................................................................................
12
Click on Send to start the backup operation.

Write down the pathname and the description of the saved backup. Keep a record of all
saved backups. You will need this information later to download and restore a certain
backup.
Result: If the progress section displays 100% and State: Success the backup is saved
on the RFS.
...................................................................................................................................................................................................
13
If you want to abort the backup operation, proceed as follows

Result: The Alcatel-Lucent 1830 PSS ZICfemur Stop File Transfer window opens.
...................................................................................................................................................................................................
14
In the field From select STBYDB.
....................................................................................................................................................................................................................................
1830 PSS
17-20
Issue 1 June 2013


remote file server
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
15
In the field To select RFSDB.

...................................................................................................................................................................................................
16
Click on Send to stop operation.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
17-21
Issue 1 June 2013

Procedure 17-3: Retrieve information related to transferred

files on a remote file server
....................................................................................................................................................................................................................................

When to use
Use this procedure to retrieve information related to transferred files on a remote file
server.
RTRV-RFILE
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select View Remote Files, either by selecting Action from the main menu bar or by
Result: The Alcatel-Lucent 1830 PSS ZIC Retrieve RFILE window opens.
...................................................................................................................................................................................................
In the field Name select RFSDB.

Identifies the database for which the information is retrieved.
...................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
17-22
Issue 1 June 2013


....................................................................................................................................................................................................................................
sftp
...................................................................................................................................................................................................
RFS.
...................................................................................................................................................................................................
RFS.
server configuration on the CT.
...................................................................................................................................................................................................
...................................................................................................................................................................................................

Most schemes designate protocols that have a default port number. The default port
number for sftp is 22.
...................................................................................................................................................................................................

[/]/<cwd1>/<cwd2>/.../<cwdN> where <cwd1> to <cwdN> are strings that identify
...................................................................................................................................................................................................
Click on Send to start the operation.

Result: The information related to transferred files on a remote file server are
displayed.
Reference: See Information related to database backups stored on a remote file
server. (p. 17-24).

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
17-23
Issue 1 June 2013

Information related to database backups stored on a

remote file server.
....................................................................................................................................................................................................................................
Information related to database backups stored on a remote

file server.
Overview
The following information can be retrieved for database backups stored on a remote file
server:
Parameter
Values
Details
Name
RFSDB
Identifies the database for which the

information is retrieved.
A database backup on a
Remote File Server
System Type
1830 PSS
Indicates the system type, 1830 PSS.
....................................................................................................................................................................................................................................
1830 PSS
17-24
Issue 1 June 2013


remote file server.
....................................................................................................................................................................................................................................
Parameter
Values
Details
Release
Identification
{E, F, P,
R}{00-99}.{00-99}.{0099}
Indicates the release ID of the system

software, that is the identifier of the actual
product release (R05.01.01 for example).
Explanation:
SID
Site Identifier
A database backup on a
Remote File Server
E
Engineering Load. When software has
progressed to the point where
components and functions are brought
together in a single testable load (Internal
load only).
F
First Office Application, the software
load is intended for FOA evaluation and
testing and is qualified to carry traffic
under specified conditions or constraints
development that could be changed to an
R load pending customer acceptance).
P
Preliminary, the software load is only
intended for evaluation and testing under
controlled, nontraffic-bearing conditions
development, not meant for deployment
or real traffic).
R
Released, the software load is fully
qualified to carry traffic per applicable
ALU specifications.
The first pair of digits indicates the

major release.
The second pair of digits indicates the

minor release.
The third and last pair of digits indicates

the maintenance release.
Site Identifier, indicates the SID of the

system that was used to create the backup
file. This parameter is only returned when
the AID is RFSDB.
....................................................................................................................................................................................................................................
1830 PSS
17-25
Issue 1 June 2013


remote file server.
....................................................................................................................................................................................................................................
Parameter
Values
Details
Matrix Type
MT960C
Matrix type equipped in the system when the

backup was created.
MT1T9
MT1T9C
MT3T8
Backup Date
Date, identifies the database backup date

creation date in the format of YY-MM-DD.
This parameter is only returned when the
AID is RFSDB.
Backup Time
Time, identifies the database backup time

creation time in the format of HH-MM-SS.
This parameter is only returned when the
AID is RFSDB.
REGION
ANSI, ETSI
The type of NE application:
ANSI the NE operates in SONET

mode.
ETSI the NE operates in SDH mode.
....................................................................................................................................................................................................................................
1830 PSS
17-26
Issue 1 June 2013

Procedure 17-4: Download a database from a remote file

server to the standby database
....................................................................................................................................................................................................................................

When to use
Use this procedure to download a database from a remote file server to the standby
database.
COPY-RFILE
For redundant systems (that means with redundant FLCs)
Due to the redundant system control, there is no interruption on the active FLC during
the download.
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

...................................................................................................................................................................................................
In the field From select RFSDB.
....................................................................................................................................................................................................................................
1830 PSS
17-27
Issue 1 June 2013


....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
In the field To select STBYDB.

...................................................................................................................................................................................................
...................................................................................................................................................................................................

number for sftp is 22.
...................................................................................................................................................................................................
In the field Protocol select the protocol to be used for file transfer.
sftp
secure file transfer protocol

...................................................................................................................................................................................................
RFS.
...................................................................................................................................................................................................
RFS.
...................................................................................................................................................................................................
In the field LOCATION:Url-Path enter the Remote File Server Path:

[/]/<cwd1>/<cwd2>/.../<cwdN> where <cwd1> to <cwdN> are strings that identify
....................................................................................................................................................................................................................................
1830 PSS
17-28
Issue 1 June 2013


....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
10
Define the Command Execution mode using the Command Mode.
Forced
The operation is performed, regardless of the following:

the BACKUP-DATE and BACKUP-TIME on the RFS DB (represented in the
label on the RFS database) is older/prior to the BACKUP-DATE and
BACKUP-TIME on the system (represented in label on the active hard disk
database)
the SID indicated on the RFS DB does not match the SID of the system.
the software release identifier indicated for RFS DB does not match the software
release identifier indicated for the system.
the REGION indicated on the RFS DB does not match the REGION of the
system.
Normal
The command is denied if there is a mismatch between

the SID, the release identifier, system type or the backup time stamp of the system
and the information stored in the source database.
a mismatch between the REGION indicated on the RFS DB and the REGION of
the system.
...................................................................................................................................................................................................
11

...................................................................................................................................................................................................
12
If you want to abort the download operation, proceed as follows

Result: The Alcatel-Lucent 1830 PSS ZIC Stop File Transfer window opens.
...................................................................................................................................................................................................
13
In the field From select RFSDB.

...................................................................................................................................................................................................
14
In the field To select STBYDB.

...................................................................................................................................................................................................
15
Click on Send to stop operation.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
17-29
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to copy the backup database stored on STBYDB to the primary
backup database (ACT-DSK-DB) and resets the system to activate the new database.
RESTORE-DB
Before you begin

Note: If GMRE is used, move transit traffic away from the node to be restored using
OMS.
Required equipment
Instructions
...................................................................................................................................................................................................

Then select Database Operations Restore DB, either by selecting Action from the
Result: The Alcatel-Lucent 1830 PSS ZIC Restore Database window opens.
...................................................................................................................................................................................................
In the field Command Execution Mode specify the execution mode.
Forced
The database restore operation is performed regardless of the following:

The BACKUP-DATE and BACKUP-TIME indicated for the STBYDB is
older/prior to the BACKUP-DATE and BACKUP-TIME on the system
(represented in label of the Active Local Primary disk Database).
The SID indicated on the STBY DB does not match the SID of the system.
....................................................................................................................................................................................................................................
1830 PSS
17-30
Issue 1 June 2013

....................................................................................................................................................................................................................................
The software release identifier indicated for the STBYDB does not match the
software release identifier indicated for the system.
The REGION parameter indicated for the STBYDB does not match the REGION
parameter indicated for the system.
Normal
The command is denied if there is a mismatch between the SID, the software release
identifier, system type, Region parameter, or the backup time stamp of the system and
the information stored in the STBYDB.
Note: Independent from Command Execution Mode restoration of the database is not
possible in case of system or matrix type or shelf type mismatch.A detailed list of
command denials can be found in the Alcatel-Lucent 1830 PSS OCS TL1 Command
Guide, when searching for RESTORE-DB.
...................................................................................................................................................................................................
Click Apply.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
17-31
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section describes the procedures for Alcatel-Lucent 1830 PSS NE database backup
and Alcatel-Lucent 1830 PSS NE database restore.
Contents
17-33
17-34
17-36
....................................................................................................................................................................................................................................
1830 PSS
17-32
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to backup database.

Before you begin
Instructions
Note: The information here describes procedures using the WebUI. For procedures
using 1354 RM-PhM or CLI, see the Alcatel-Lucent 1354 RM-PhM Release 11.0
Photonic Manager EMS Reference Guide and Alcatel-Lucent 1830 Photonic Service
...................................................................................................................................................................................................
In the WebUI, select Administration > Database > Backup and Restore.
Result: The database Backup and Restore screen is displayed.
...................................................................................................................................................................................................
Enter Backup/Restore settings (Server IP Address = IP address of the PC in which the

TFTP/SFTP server is running; Directory = the path in the TFTP/SFTP server). Click
Apply, then click Backup.
Note: In encrypted mode (SFTP), User ID and Password must be entered. (See
System security features (p. 2-26) for SFTP details).
Result: A window is displayed indicating that the backup has been initiated.
...................................................................................................................................................................................................
Click OK. Next, click Refresh to display the status of the Backup.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
17-33
Issue 1 June 2013

....................................................................................................................................................................................................................................

Attribute
Values/Format
Additional Info
Backup/Restore Settings
Protocol
FTP
TFTP
File transfer protocol used for

the backup/restore request.
SFTP
User ID
<0-32 chars>
The user ID for accessing the

database server. Not
applicable for TFTP.
Password
<0-32 chars>
The password corresponding

to the user ID for accessing
the database server. Not
applicable for TFTP.
Confirm Password
<0-32 chars>
Re-enter the password

corresponding to the user ID
for accessing the database
server. Must match Password.
Not applicable for TFTP.
Server IP
<IP address>
IP address of remote server

where backup file is stored.
Directory
<1-255 chars>
Directory on remote server

where backup file is stored.
Filename
<1-255 chars>
Filename of backup file.
Last Backup Data

Last Backup Filename
<1-255 chars>
Last Backup Date/Time

Last Command
The date/time of the last

backup request.
Unknown
Backup
Restore
Last Command Status
Last Command Progress
The filename of the last

backup.
Indicates the last

backup/restore command that
was issued.
Indicates the success or
failure of the last
backup/restore command.
<0-100> %
The completion percentage

for the last backup/restore
command.
....................................................................................................................................................................................................................................
1830 PSS
17-34
Issue 1 June 2013

....................................................................................................................................................................................................................................
Attribute
Values/Format
Additional Info
Backup
Request a backup of the NE

database.
Restore
Request to restore a
previously backed up
database to the NE.
Force Restore
Request to force the restore of

a previously backed up
database to the NE.
....................................................................................................................................................................................................................................
1830 PSS
17-35
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to restore the database.

Before you begin
Note: The information here describes procedures using the WebUI. For procedures
using 1354 RM-PhM or CLI, see the Alcatel-Lucent 1354 RM-PhM Release 11.0
Photonic Manager EMS Reference Guide and Alcatel-Lucent 1830 Photonic Service
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Database > Backup and Restore.
Result: The database Backup and Restore screen is displayed.
...................................................................................................................................................................................................
Enter Backup/Restore settings (Server IP Address = IP address of the PC in which the

FTP server is running; Directory = the path in the FTP server; File Name = the name of
the file to be restored from the FTP server). Click Apply, then click Restore.
Note: A forced restore can be made by clicking Force Restore. This runs the
restore despite the existence of failure conditions. A forced restore causes a bypass
of all checks that the restore operation would run before it actually executes.
Note: In encrypted mode (SFTP), User ID and Password must be entered. (See
System security features (p. 2-26) for SFTP details).
Result: A window is displayed indicating that this may be service affecting and that
after the database has been restored, the system will automatically restart.
...................................................................................................................................................................................................
Click OK. Next, click Refresh to display the status of the restore.
Result: When the NE resets, the WebUI will be refreshed and will navigate to the
main screen. Select Administration > Database to see the status of the database
restore.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
17-36
Issue 1 June 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
17-37
Issue 1 June 2013
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
17-38
Issue 1 June 2013
18
18
Software
installation and
upgrade procedures
Overview
Purpose
This chapter describes both the procedures which have to be carried out for the first
installation and the procedures for the software upgrade of the Alcatel-Lucent 1830 PSS.
Important! An Alcatel-Lucent 1830 PSS NE consisting of an OCS and an DWDM
compound can be installed and upgraded each compound independently.
Contents
18-2
Procedure 18-1: Upgrade to a new release of the NE software
18-3
Procedure 18-2: Download a software generic from a remote file server to the
standby software load
18-9
18-14
Procedure 18-4: Switch from the current release to the new release
18-18
Procedure 18-5: Switch back from the current release and database to previous
release
18-20
Procedure 18-6: Make the current release software the permanent active
software
18-22
18-24
Procedure 18-7: Software upgrade procedure
18-25
FTP Server Settings
18-27
Software Upgrade
18-28
18-31
...................................................................................................................................................................................................................................
1830 PSS
18-1
Issue 1 June 2013

....................................................................................................................................................................................................................................

Purpose
This chapter describes both the procedures which have to be carried out for the first
installation and the procedures for the software upgrade of the Alcatel-Lucent 1830 PSS
application OCS using the Alcatel-Lucent 1830 PSS ZIC.
Contents
18-3
Procedure 18-2: Download a software generic from a remote file server to the
18-9
18-14
Procedure 18-4: Switch from the current release to the new release
18-18
Procedure 18-5: Switch back from the current release and database to previous
release
18-20
Procedure 18-6: Make the current release software the permanent active
software
18-22
....................................................................................................................................................................................................................................
1830 PSS
18-2
Issue 1 June 2013

Procedure 18-1: Upgrade to a new release of the NE

software
....................................................................................................................................................................................................................................

When to use
Use this procedure to upgrade to a new release of the NE software.

Important! Run this procedure during quiet provisioning hours. Don't download from
server while other download/upload of generic or Performance Monitoring Data is in
progress.
Initializing the Network Element New will cause traffic impact if new IOC firmware
is activated.
If GMRE application is active do not upgrade adjacent Network Elements at the same
time.
COPY-RFILE
INIT-SYS-NEW
RTRV-ISU-STATUS
RMV-ISU-OLD
Before you begin

1. Have a valid login on both the ZIC and all subject NE(s).
2. Create a NE database backup and store this on an remote file server, see Procedure
17-2: Transfer the NE standby database to a remote file server (p. 17-18);
3. Acquire the DVD that contains the new generic/version of the NE software.
4. Connect the PC locally to the subject NE.
5. Make sure that there is no configuration (write) access to the NE from management
systems during the software download.
During the upgrade procedure, starting with the database backup until the complete
error free start up of the New Release, the following must be avoided:
provisioning, including provisioning in other parts of the network
changing cables,
un-powering HW or opening latches
changing HW,
replacing defect HW.
....................................................................................................................................................................................................................................
1830 PSS
18-3
Issue 1 June 2013


software
....................................................................................................................................................................................................................................
Note: Prior to In-Service-Upgrade (ISU), verify if Remote Inventory (RI) data is

available for the main shelf (SHELF-1-1). See Procedure 5-45: Retrieve remote
inventory for a system component (p. 5-451).
In case no RI data is replied for the main shelf, do not attempt to perform the
upgrade.Contact Alcatel-Lucent customer support team for main shelf RI repair.
Upgrade-preconditions for the Network Element
The following preconditions have to be fulfilled by the NE to be upgraded:
All alarms on the NE (for instance alarm list, UPL) are cleared. If it is not possible to
clear all alarms the cause for the remaining alarms must be fully understood and clear.
Protection switches (for instance equipment protection, traffic protection) should be
avoided during the upgrade.
Release all loopbacks before performing the SW upgrade. See Chapter 13, TDM
traffic maintenance procedures and Chapter 15, TDM Ethernet/Data traffic
maintenance procedures .
During new release restart it may come to a MTX side switch. To avoid this perform
Procedure 5-23: Inhibit equipment protection switching (p. 5-113).
Upgrading Control Plane managed NEs
The following has to be fulfilled for upgrading of NEs managed via Control Plane and
located within one Control Plane network domain.
GMRE supports a phased approach in order to In-Service-Upgrade all nodes within an
ASON, by distinguishing between
the Active SW Version, and

the Installed SW Version.
Before starting the In-Service-Upgrade of a NE, Active and Installed SW version must be
equal. Once the In-Service-Upgrade of a single NE is completed, its Installed SW
Version is increased to the GMRE version of the new SW release, while its Active SW
Version remains at the old value, thus providing backward compatibility of the CP
protocols with all NEs that have not been upgraded yet to the new SW release.
When the In-Service-Upgrade of all NEs is completed, i.e. all nodes belonging to the
ASON have the same Installed SW Version, the value of the Active SW Version is
increased to the Installed SW Version. This enables the GMRE features of the new SW
release. In order to raise the Active SW Version simultaneously on all nodes of the
ASON domain, the operation is to be performed via 1350 OMS.
....................................................................................................................................................................................................................................
1830 PSS
18-4
Issue 1 June 2013


software
....................................................................................................................................................................................................................................
During deployment of a new software release in a Alcatel-Lucent 1830 PSS network, the
following has to be done:
1. first all nodes receive the new release SW (see Procedure 18-2: Download a
software generic from a remote file server to the standby software load (p. 18-9).)
2. start with one node and set each port in use by Control Plane into link maintenance on
this node and its direct adjacency port in neighbor node, if all IOC Firmware shall be
upgraded together with the new software release
3. upgraded the node command to the new software release as described below
4. set back the link maintenance for the neighbour node's ports and on the upgraded
node if it was set before. During this phase an Control Plane interworking of new SW
releases with current SW releases shall be supported, due to all nodes still running
their Control Plane network protocols on the same Active SW Version.
5. Repeat steps 2 to 4 for all nodes in the network domain.
If the IOC firmware was not upgraded together with the release software, the firmware
shall now be upgraded according to the operator planning.
On a PortGroup or slot basis, depending on the affected IOC, use a sequence of:
1. Enable link maintenance for the affected neighbor node's ports affected from the
PortGroup/slot under upgrade and on the ports of the node where the firmware
upgrade shall take place using OMS.
2. ED-PORTGP or INIT-SYS TL1 commands, to update the firmware on the PortGroup
or IOC
3. Disable link maintenance for the port using OMS
4. Repeat steps 1 to 3 until all PortGroups/slot are updated
5. Continue with next node, execute steps 1 to 4 for each node.
To verify all firmware being upgraded, apply the TL1 commands RTRVPORTGP::ALL and RTRV-EQPT::ALL on each node and make sure no
FWUPGRADEABLE=YES is reported.
At this point on each node the Active Software Version (ASV) can be provisioned by
the operator via ED-CPNODE TL1 command to use the latest version deployed; than also
the control plane is on the new release SW function. Backward CP compatiblity from here
on is no longer supported.
The control plane isolates a node from the CP network if its "Installed Software Version"
is less than the "Activated Software Version" of its control plane neighbors.
Prior to initializing the new release, set all NNI physical connections of this node to link
maintenance state Enabled using OMS. Be aware that links in this mode will not react on
interruptions and permanent traffic outage can occur.
....................................................................................................................................................................................................................................
1830 PSS
18-5
Issue 1 June 2013


software
....................................................................................................................................................................................................................................
Required equipment
The following equipment is required for upgrading the Alcatel-Lucent 1830 PSS software
from a former release to Release 6.0.0:
Software for Alcatel-Lucent 1830 PSS, Release 6.0.0.

Software for Alcatel-Lucent 1830 PSS, supported predecessor release (used for
disaster recovery).
That means, in accordance with the allowed upgrade path, exactly the release that
comes before the release, to which the NE should be upgraded.
Instructions
Follow the procedure carefully to upgrade to a new release of the NE software.

...................................................................................................................................................................................................
Download the software generic from the remote file server to the standby software load.
See Procedure 18-2: Download a software generic from a remote file server to the
standby software load (p. 18-9).
Note: In case of active GMRE application, set all NNI physical connections of this
node to link maintenance state Enabled using OMS.
...................................................................................................................................................................................................

Then select System Commands Initialize NE New, either by selecting Action from the
Result: The Initialize Network Element - New window opens.
...................................................................................................................................................................................................
In the field Firmware Upgrade select Enabled to allow FPGA upgrades.

...................................................................................................................................................................................................
Click on Apply to start the operation.

...................................................................................................................................................................................................
Check the status of the ongoing upgrade procedure

Select System Command View ISU Status, either by selecting Action from the main
Result: The Alcatel-Lucent 1830 PSS ZIC View ISU Status window opens showing
the current status of the upgrade procedure.

Initialize New Completed, indicates the INIT-SYS-NEW system
initialization process completed successfully and the system is restarted on the
new release.
INITNC
....................................................................................................................................................................................................................................
1830 PSS
18-6
Issue 1 June 2013


software
....................................................................................................................................................................................................................................
Initialize New In Progress, indicates the INIT-SYS-NEW system

initialization process is in progress.
INITNIP
STAF
STA-ISU command Failed.
STArt ISU Completed, indicates that the STA-ISU command completed

successfully and is awaiting the issuance of the INIT-SYS-NEW command.
STAC
Important! If the ISU takes longer than accounted for, it may occur that a timeout
exceeded, which is used for awaiting the pre-loading autonomous actions
finishing. TheISU status is then Pre-load-Fail (PRELF).
In ISU state PRELF, which can be seen, trigger the ISU preparation newly with
STA-ISU command. The repetition of the ISU pre-loading will be accumulative
and the timeout will not expire for the same reason again.
Additional information If during in-service upgrade only one FLC was used or one
FLC was pulled out or it's latches where opened, and in ISU state Init-NewCompleted (INITNC) a second FLC is equipped again (plugged in or latches closed),
the FLC replacement procedure does not take place immediately but is delayed to ISU
state No-STArt-isu-In-Progress (NOSTAIP) - after the ISU is finished completely. No
TL1 indication other than Software-Downloading (SWDL) is provided during that
time on TL1 for this pack and for the group state TL1 reports a change to recovery
(RECCOVERY).
...................................................................................................................................................................................................
IF
THEN
the upgrade was successful,
The upgrade is complete and the system works with the

new release SW.
In case of active GMRE application: Set all NNI
physical connections of this node to link maintenance
state Disabled using OMS.m
Continue with Procedure 18-6: Make the current
release software the permanent active software
(p. 18-22).
the upgrade was not successful and

the system is running with the old
software,
End of Steps
the upgrade was not successful and

the system is inoperable (for
instance cyclic reboot),
perform a fall back to the Old Release, proceed with

Procedure 18-5: Switch back from the current release
and database to previous release (p. 18-20)
....................................................................................................................................................................................................................................
1830 PSS
18-7
Issue 1 June 2013


software
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In case of active GMRE application, after upgrading the last NE in a network, please refer
to the Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 6.0 GMRE/GMPLS
Configuration Guide for increasing the Active Network Version.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-8
Issue 1 June 2013

Procedure 18-2: Download a software generic from a

remote file server to the standby software load
....................................................................................................................................................................................................................................
Procedure 18-2: Download a software generic from a remote

file server to the standby software load
When to use
Use this procedure to download a software generic from a remote file server to the
Important! Run this procedure during quiet provisioning hours. Dont download
from server while other download/upload of generic or Performance Monitoring Data
is in progress.
During Start In-Service-Upgrade In Progress (STAIP), provisioning is limited.
COPY-RFILE
Before you begin

Acquire the DVD that contains the new generic/version of the NE software.
Note: The NE SW can also be downloaded from ALED Web Portal
(https://download.support.lucent.com/cgi-bin/Download.pl) to the customer managed
remote file server. There exists a dedicated ALU download plug in which must be
used. To unpack the received NE Software (ISO format) use 7-Zip instead of WinZip.
Have loaded the software generic to onto a specific folder on the remote file server
(therefor create a folder on the file server; example: /download/1830/R05_00_
00/builds) If the remote file server is not a local PC this has to be done by the
owner of the remote file server.
The Alcatel-Lucent 1830 PSS must be in a stable state, that means no configuration
changes or maintenance actions must be started or must be in progress.
Note: The system must use the loopback IP address to initiate SFTP, as no other
source IP address can be used on the unnumbered interfaces (GCCs).
On the GNE, one of the addresses on OAMP-LAN will be used.
Therefore you must ensure that the SFTP server is able to route the loopback address
of the NE. This can be achieved by running OSPF on the SFTP server, attaching the
SFTP server to a router, or adding static routes to the SFTP server.
....................................................................................................................................................................................................................................
1830 PSS
18-9
Issue 1 June 2013


....................................................................................................................................................................................................................................
Required equipment
Instructions
...................................................................................................................................................................................................

Note: The initialization of the Backup & Restore dialog box may take some time.
During this time the command buttons are greyed.
...................................................................................................................................................................................................
In the field From select RFSSW.

...................................................................................................................................................................................................
In the field To select STBYSW.

...................................................................................................................................................................................................
sftp
file transfer protocol

...................................................................................................................................................................................................
In the field LOCATION:FTPHost: enter the IP address of the host (the remote file server).
...................................................................................................................................................................................................

number for SFTP is 22.
...................................................................................................................................................................................................
RFS.
...................................................................................................................................................................................................
RFS.
....................................................................................................................................................................................................................................
1830 PSS
18-10
Issue 1 June 2013


....................................................................................................................................................................................................................................
Note: For use of the local SFTP host, the user/password are defined during the SFTP
...................................................................................................................................................................................................

where the file(s) reside) can be accessed.
It has the following syntax:
[/]<cwd1;>/<cwd2;>/.../<cwdN;>
where <cwd1;> through <cwdN;> are strings that identify directories.

With a leading '/' character, the path is interpreted as an absolute file path inside the
Remote File Server's file system.
Without the optional leading `/` character, the path is interpreted as a file path relative to
the users's login directory.
If sftp host is not the local host, there is no browsing, the user shall type in the relative
path, and the directory does not get created, except for the last level, created by the NE.
Example: /download/1830/R05_00_00/
...................................................................................................................................................................................................
10

Result: The operation is denied, if the ISU-STATE is different to NOSTAIP and the
COPY-RFILE is about a software release upgrade.

The download completion time is at maximum
15 minutes for download via an ethernet LAN connection (10 Mb/s).
3.5 hours for download via LAN and one hop ODU-2 GCC connection, when the
GCC bandwidth is exclusively used for this download.
1 hour for download via LAN and one hop ODU-3 GCC connection, when the
0.25 hour for download via LAN and one hop ODU-4 GCC connection, when the
....................................................................................................................................................................................................................................
1830 PSS
18-11
Issue 1 June 2013


....................................................................................................................................................................................................................................
Additional information As consequent action of a successful SW download the
FPGA firmware of the new release is distributed onto available Flash RAM storage on
I/O packs. The FPGA firmware distribution onto the Flash RAM on I/O packs as
consequent action of a successful SW download has a completion time maximum of 2
hours for a fully equipped system. As consequent action of a successful FPGA
firmware distribution the system autonomously performs a feasibility check that the
current system configuration allows a successful upgrade to the new release. The
feasibility check on the current system configuration as consequent action of a
successful FPGA image distribution has a completion time maximum of 15 minutes
for a fully equipped system.
...................................................................................................................................................................................................
11
To check the status of the ongoing upgrade procedure


The following status can be displayed
Download In Progress, indicates that a COPY-RFILE command for
software package transfer is ongoing.
DLIP
PRELIP
PRELoad of I/O card FPGA images In Progress
Start ISU In Progress, indicates that an in-service upgrade procedure is in

progress.
STAIP
PRELF
STAF
PRELoad of I/O card FPGA images Failed

STA-ISU command Failed
A successful SW generic download and its consequent actions lead to an

ISU STAC.
STAC
Note: The first ISU step starts from the initial state NOSTAIP and remains in the ISU
state DLIP until the file transfer is finished. Afterwards the ISU states PRELIP and
STAIP are traversed automatically (performing some consequent actions after the
software release download succeeded) to reach the first stable interim ISU state
STAC.
....................................................................................................................................................................................................................................
1830 PSS
18-12
Issue 1 June 2013


....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
12
IF ISU state STAC is not

reached, but
THEN
state PRELF is reached,
Perform the following,

1. In the Alcatel-Lucent 1830 PSS ZIC selection tree
select System.
Start in-service upgrade by selecting System
Commands Start Upgrade, either by selecting
Action from the main menu bar or by using the
2. If the in-service upgrade fails, select System
Commands Stop Upgrade, either by selecting
state STAF (STArt ISU Failure) is

reached,
Perform the following,

1. In the Alcatel-Lucent 1830 PSS ZIC selection tree
select System.
Start in-service upgrade by selecting System
Commands Start Upgrade, either by selecting
2. If the in-service upgrade fails, select System
Commands Stop Upgrade, either by selecting
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-13
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use this procedure to install the Alcatel-Lucent 1830 PSS system software after a
catastrophic failure which causes complete or partial loss of both FLCs` disk contents.
The software is initially delivered to the customer on a DVD. The software generic has to
be copied from the DVD to an empty USB flash drive. In addition the software can be
downloaded (via a special browser add-on) from the ALED (Alcatel-Lucent web portal) to
a customers computer (file server or PC) for creating a DVD on customer premises.
Afterwards, the USB flash drive is used to transfer and to load the software generic onto
the disk of the FLC.
Safety precautions
NOTICE
ESD hazard
Circuit packs must therefore always be kept in antistatic covers. Use the original
antistatic packaging if possible. Always observe the ESD instructions (see Electrostatic
discharge (p. 1-26)).
To assure both personal safety and the proper functioning of the Alcatel-Lucent 1830 PSS
product, it is imperative to observe the preceding precautions.
Before you begin
make sure that the most recent database backup is available on a remote file server
(RFS) or Laptop.
Required equipment
USB flash drive

DVD that contains the new generic/version of the Alcatel-Lucent 1830 PSS NE
software
PC/Laptop with
PC/Laptop with USB 2.0 interface, sftp capabilities and a web-browser, connected to
the F/.DBG connector on main shelf via LAN cable
Java 1.6.0_31 and above is recommended.
....................................................................................................................................................................................................................................
1830 PSS
18-14
Issue 1 June 2013

....................................................................................................................................................................................................................................
Technical requirements
The USB flash drive (USB stick) to be used is not part of the Alcatel-Lucent delivery.
Table 18-1
USB flash drive specifications
Property
Value
Capacity
4 GB
Interface type
USB 2.0
Formatted with
1 single FAT32 partition
Alcatel-Lucent successfully tested several types of USB flash drives. For further
information contact your Local Customer Support or the Alcatel-Lucent support team
(http://www.alcatel-lucent.com/support/).
If the USB flash drive is supplied with a smart device, application auto start, or
password protection option, these have to be removed by the operator using the tools
provided by the USB flash drive vendor before it can be used for the Alcatel-Lucent
1830 PSS software. The USB flash drive used must be empty before the software load is
copied to it.
Instructions
...................................................................................................................................................................................................
Power up the PC and log into Windows . If you are already logged in, close any open
window.
...................................................................................................................................................................................................
Copy the NE software from the DVD to the USB flash drive.
To do this, proceed as follows.
...................................................................................................................................................................................................
Insert the Alcatel-Lucent 1830 PSS DVD with the new NE software.
...................................................................................................................................................................................................
Insert the USB flash drive into a free USB plug of the PC.
...................................................................................................................................................................................................
Start Windows Explorer .

...................................................................................................................................................................................................
In the Windows Explorer , right-click the DVD-ROM drive of your computer and select
Explore.
....................................................................................................................................................................................................................................
1830 PSS
18-15
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Select the complete directories and the files in the root directory of the DVD (i.e.
1830PSS.DSC, release.info, TRANS.TBL) and copy them to the USB flash drive.
...................................................................................................................................................................................................
The Copying filesmessage will disappear when the file transfer is complete.
...................................................................................................................................................................................................
If the USB driver software you are using requires you to stop the USB flash drive before
ejecting it, stop the USB flash drive now.
...................................................................................................................................................................................................
10
Eject the USB flash drive from the USB plug of the PC.
...................................................................................................................................................................................................
11
Depending which FLC is plugged in, the procedure has to be continued as follows
If
then
no FLC is plugged in
plug in the first FLC (at slot 73), (at slot 23),
and continue with the next step.
one FLC is plugged in
insert second FLC (at slot 75), (at slot 40), and
leave open both latches only and continue with
the next step.
both FLCs are plugged in
on second FLC (at slot 75), (at slot 40), open

both latches and leave open only and continue
with the next step.
...................................................................................................................................................................................................
12
Insert the USB flash drive containing the system software into the USB plug of the FLC
located at worker slot (slot number 23). Please observe ESD instructions.
Insert the USB flash drive containing the system software into the USB plug of the FLC
located at worker slot (slot number 73). Please observe ESD instructions.
...................................................................................................................................................................................................
13
Press the reset button R on the FLC (This will initiate a hard reset of the FLC)
...................................................................................................................................................................................................
14
Press the ACO button

(approx: 20 seconds).
on the FLC and hold it until the LED STAT is flashing green
....................................................................................................................................................................................................................................
1830 PSS
18-16
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: The progress of the initial SW installation from the USB flash drive is
indicated by the LED STAT on the FLC. The LED STAT lits until the FLC has booted
the release software with the default name FLCHCA and the default IP address
18.70.1.3.
After approx. 30 minutes the SW installation has finished and the FLC is ready
(indicates to be in active state) when both, the STAT and the EPS LEDs display
Green color.
After the FLC has booted the release software, a TL1 and/or http connection can be
established on the CIT interface via a point-to-point connection with a PC.
...................................................................................................................................................................................................
15
After installing the NE software you have to perform a database restore. Therefore
proceed with the following procedures as needed:

server (p. 17-22)
database (p. 17-27)
Procedure 17-5: Restore database (p. 17-30).
...................................................................................................................................................................................................
16
After successful database restore, close both latches of the standby FLC, await FLC
replacement procedure to finish.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-17
Issue 1 June 2013

Procedure 18-4: Switch from the current release to the new

release
....................................................................................................................................................................................................................................

release
When to use
Use this procedure to perform the actual switch over from the current release to the new
release.
Important! Initializing the Network Element New will cause traffic impact if new I/O
card firmware is activated.
INIT-SYS-NEW
Before you begin


assure that the NE is in ISU state STAC.
Note: If GMRE application is active
do not upgrade adjacent Network Elements at the same time.

set all NNI physical connections of this node to link maintenance state "Enabled"
using OMS. Do not forget to revert the link maintenance state after the ISU
activity has been completed.
Required equipment
Instructions
...................................................................................................................................................................................................

Then select System Commands Initialize NE New, either by selecting Action from the
....................................................................................................................................................................................................................................
1830 PSS
18-18
Issue 1 June 2013


release
....................................................................................................................................................................................................................................

...................................................................................................................................................................................................
In the field Firmware Upgrade select Enabled to allow FPGA upgrades.

...................................................................................................................................................................................................
Click on Yes to start the operation.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-19
Issue 1 June 2013

Procedure 18-5: Switch back from the current release and

database to previous release
....................................................................................................................................................................................................................................

When to use
Use this procedure to switch back from the current release and database to previous
release.
Important! Initializing the Network Element Old will cause traffic impact if old I/O
card firmware is activated.
INIT-SYS-OLD
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select System Commands Initialize NE OLD either by selecting Action from the
...................................................................................................................................................................................................

...................................................................................................................................................................................................
In case of active GMRE application, set all NNI physical connections of this node to link
maintenance state "Disabled" using OMS.
Note: This step needs to be executed after the Initialize NE Old has been completed.
....................................................................................................................................................................................................................................
1830 PSS
18-20
Issue 1 June 2013


....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Check the status of the ongoing operation


new release.
INITNC
No Status In Progress, indicates that no generic in-service upgrade

procedure is in progress or has been attempted.
NOSTAIP
Initialize Old In Progress, indicates the INIT-SYS-OLD system

initialization process is in progress.
INITOIP
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-21
Issue 1 June 2013

Procedure 18-6: Make the current release software the

permanent active software
....................................................................................................................................................................................................................................

When to use
Use this procedure to make the current release software the permanent active software.
It effectively prevents reversion to a previous release.
RMV-ISU-OLD
Before you begin

Required equipment
Instructions
...................................................................................................................................................................................................

Then select System Commands Remove ISU OLD either by selecting Action from the
...................................................................................................................................................................................................

Result: After successful completion of the procedure, all software/database indicators
are set to indicate that the current release is now the permanently active one. The
system remains in service on the currently active release and all system functionality
remains operational.
Note: In case of active GMRE application, set all NNI physical connections of this
node to link maintenance state "Disabled" using OMS.
....................................................................................................................................................................................................................................
1830 PSS
18-22
Issue 1 June 2013


....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Check the status of the ongoing operation


new release.
INITNC
No Status In Progress, indicates that no generic in-service upgrade

procedure is in progress or has been attempted.
NOSTAIP
RMVOIP
RMV-ISU-OLD command In Progress
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-23
Issue 1 June 2013

Overview
....................................................................................................................................................................................................................................

Purpose
The WebUI supports the steps of an upgrade to a later release (load, activate) and any
steps needed during installation (commit), or a back out or downgrade from a newer
release.
The following actions can be performed via the WebUI with respect to a software
upgrade:
Audit
Download
Activate
Commit
Revert
Contents
18-25
FTP Server Settings
18-27
Software Upgrade
18-28
18-31
....................................................................................................................................................................................................................................
1830 PSS
18-24
Issue 1 June 2013

....................................................................................................................................................................................................................................

When to use
Use the following procedures to upgrade the NE software.

Note: If software upgrade procedure is aborted, the user must wait a few minutes
before reattempting to load/audit. Otherwise a failure may occur.
Note: While performing a software release upgrade from Release OLD to Release
NEW, the Revert action may be used to return to the OLD release and database, as it
was before the software release upgrade started. After the NEW release is committed,
the Revert command has no affect and a "downgrade" procedure must be used to back
down to the OLD release.
Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Software > FTP Server. Enter the FTP Server
settings.
Note: PM and log (event log, security log, etc.) information will be lost as a result of
the system restart that occurs during software release upgrade. This information
should be retrieved if you would like to retain it for your records.
...................................................................................................................................................................................................
In the WebUI, select Administration > Software > Upgrade.

Result: The Software Upgrade window is displayed.
...................................................................................................................................................................................................
Enter the folder name containing the NE software in the Release Directory. Select Audit
for the Action Type and click Apply.
Note: If this is a software downgrade, check the Force Upgrade box. This field can
only be chosen after Audit has been selected for the Action Type.
...................................................................................................................................................................................................
Select Download for the Action Type and click Apply.

...................................................................................................................................................................................................
Select Activate for the Action Type and click Apply.
....................................................................................................................................................................................................................................
1830 PSS
18-25
Issue 1 June 2013

....................................................................................................................................................................................................................................
Note: When Activate is requested as part of the software upgrade process, the WebUI
displays a warning message to the user, indicating that activating the software will
cause the NE to reboot. As a result, the WebUI will lose connectivity with the NE and
the user must login after activate is complete. The user will be allowed to continue
with the Activate request or cancel.
Result: The NE will reboot and the WebUI connection will drop.
...................................................................................................................................................................................................
Wait about 2 minutes after the fan speed drops back down to normal speed and log back
into the NE.
Note: 1830 PSS-32/PSS-16/PSS-32S supports the ability to control fan speed via the
WebUI. When the Fan module is selected in the WebUI equipment tree, the fan speed
can be set to the following values:
normal - automatic speed control

maximum - constant full speed (100% RPMs)
Note: The WebUI does not reconnect automatically.

...................................................................................................................................................................................................
In the WebUI, select Administration > Software > Upgrade.

Result: The Software Upgrade window is displayed.
...................................................................................................................................................................................................
Verify the Software Status now indicates Completed, and verify the Result is
Success. Check the alarms on the system and make sure traffic is still unaffected.
Note: This is the last point where a software back out can be performed. After this a
downgrade procedure is required.
...................................................................................................................................................................................................
Select Commit for the Action Type and click Apply.

Important! A one step software back out can not be performed after the software is
committed. After commit is completed, the software downgrade is supported via a full
downgrade procedure (upgrade to a lower release).
Result: The software release upgrade is now complete. A database backup should be
performed.
...................................................................................................................................................................................................
10
Generate commissioning files via 1830 PSS Engineering and Planning Tool User Guide,
then use 1830 PSS Commissioning and Power Balancing Tool User Guide to provision
the impairments and transfer the feasibility file.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-26
Issue 1 June 2013

FTP Server Settings
....................................................................................................................................................................................................................................
FTP Server Settings

Attribute
Value/Format
Additional Info
Protocol
FTP
The type of protocol used to

access the software server.
SFTP
Server IP
<IP address>
IP address of the software

server where the software
package is stored.
Root Directory
<0-255 chars>
Specifies the directory for the

software on the software
server. This directory is
relative to the servers root
directory.
User ID
<0-32 chars>
The user ID for accessing the

software download server.
Password
<0-32 chars>
The password corresponding

to the user ID for accessing
the software download server.
Confirm Password
<0-32 chars>
Re-enter the password

corresponding to the user ID
for accessing the software
download server.
Must match New Password.
....................................................................................................................................................................................................................................
1830 PSS
18-27
Issue 1 June 2013

Software Upgrade
....................................................................................................................................................................................................................................
Software Upgrade
Attribute
Value/Format
Additional Info
Release Directory
<0-255 chars>
Specifies the directory on the

remote server where the
release-specific software
resides. This directory is
relative to the Root Directory,
specified in FTP Server
Settings.
Force Upgrade
(checkbox)
Indicates whether the NE

should perform the upgrade
path check during the Audit
operation, or force the
upgrade to proceed without
this check.
Backup
(checkbox)
Indicates whether a database

backup should be performed
during the Download
operation.
Activate
The last requested software

upgrade action.
Audit Settings
Software Status
Action
Audit
Auto Install
Auto Upgrade
Card Activate
Card Load
Commit
Download
No Action
Revert
Unknown
Status
Complete
In Progress
Status of the last requested

software upgrade action.
Failed
None
....................................................................................................................................................................................................................................
1830 PSS
18-28
Issue 1 June 2013

Software Upgrade
....................................................................................................................................................................................................................................
Attribute
Value/Format
Additional Info
Percent Complete
<0-100>
Indicates the progress of the

software upgrade action.
Result
<0-255 chars>
Additional result details about

the software upgrade action if
the action failed.
FTP Server IP
<IP address>
IP address of the software

server.
FTP Server Directory
<0-255 chars>
Specifies the directory for the

software on the software
server. This directory is
relative to the root directory.
Release Directory
<0-255 chars>
Specifies the directory on the

remote server where the
release-specific software
resides. This directory is
relative to the Root Directory,
specified in FTP Server
Settings.
Active Release
<0-20 chars>
The software release that is

currently running on the NE.
Working Release
<0-20 chars>
This is the software release

that the NE is in the process
of upgrading or downgrading
to. The value is blank if a
software release upgrade is
not currently in progress.
Committed Release
<0-20 chars>
The software release version

that was last committed on
this network element.
Upgrade Path Available
Yes
Indicates whether or not a

valid upgrade path is
available, indicating a
successful audit.
No
Action
Audit
Download
Requested software upgrade

operation.
Activate
Commit
Revert
....................................................................................................................................................................................................................................
1830 PSS
18-29
Issue 1 June 2013

Software Upgrade
....................................................................................................................................................................................................................................
Attribute
Abort
Value/Format
Additional Info
Request to cancel a software
upgrade action.
....................................................................................................................................................................................................................................
1830 PSS
18-30
Issue 1 June 2013

Procedure 18-8: Modify/view software NE attributes

procedure
....................................................................................................................................................................................................................................

procedure
When to use
Use the following procedure to modify and view the software NE attributes.
Before you begin
Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Software > Software NE.

...................................................................................................................................................................................................
Modifications can be made for FTP Server Enabled and Password.

Note: The WebUI will verify the format of the Password. Valid values for the
Password are 3-8 case-sensitive alphabetic [a-z, A-Z], numeric [0-9] or special
characters. A valid password must contain at least 1 lower case alphabetic, 1 upper
case alphabetic, 1 numeric and 1 special character. The following special characters
are accepted as valid characters for the password: % (percent sign), + (plus sign), #
(pound sign), _ (underscore), ! (exclamation point), @ (at sign), $ (dollar sign),
(double quotation mark), & (ampersand), (apostrophe), ( (left parenthesis), ) (right
parenthesis), * (asterisk), \ (back slash) and . (period). The first character can be any
alphabetic, numeric or valid special character, excluding # (pound sign). The
password must not have three consecutive identical characters.
For password modification, the WebUI will prompt the user to enter the new
password and confirm password and will verify that the values match. If they do not
match, an error will be displayed. If they do match, the modify request will be sent to
the NE.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
18-31
Issue 1 June 2013

procedure
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
18-32
Issue 1 June 2013
19
Routine procedures
19
Overview
Purpose
This section describes periodic activities for maintaining the system.

Contents
19-2
Procedure 19-1: Replace the dust filter
19-3
Procedure 19-2: Replace a Fan Unit (FAN3T8)
19-6
Procedure 19-3: Common card mounting rules
19-10
...................................................................................................................................................................................................................................
1830 PSS
19-1
Issue 1 June 2013
Routine procedures
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
This section describes periodic activities for maintaining OCS parts of the system.
Contents
19-3
19-6
19-10
....................................................................................................................................................................................................................................
1830 PSS
19-2
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................

When to use
The following procedure illustrates the dust filter replacement in the PSS-64 subrack. For
a replacement of the dust filter in the PSS-36 subrack, see the Alcatel-Lucent 1830 PSS
Installation and System Turn-Up Guide for the Alcatel-Lucent 1830 PSS-36 - Air filter
installation and replacement.
Use this procedure to replace the dust filter
As a part of routine fan maintenance.

When construction work is done near the equipment in service the filters should be
inspected during and short after the construction work on a weekly interval.
When instructed to do so as a part of a trouble-clearing task.

Important! When the dust filter is replaced as part of a trouble-clearing procedure to
clear one of the alarms , , or , then the corresponding alarm will not be cleared
immediately. This applies to the PSS-36 subrack as well as to the PSS-64 subrack, and
is due to the fact that the air filter supervision runs regular checks of these dust filter
conditions only once a day.
The Air Filter is replaceable by the craft
Without need of special tools.

Without removing other parts of the subrack mechanics.
Without affecting the traffic.
Dust filter
The dust filter is a replacable unit, its part number is 3AG33589AA.

Service Interval
Short Term Service Interval

Under normal conditions the maintenance interval of the dust filter is at least 3
months. This requirement is not derived from a standard but from experience of
service staff.
Long Term Service Interval

Under normal conditions the maintenance interval of the dust filter shall be at least 12
months. This requirement is not derived from a standard but from experience of
service staff.
Filters lasting for 12 months are thicker than those lasting for 3 months. The height
allocation for the filter within the subrack is increased.
....................................................................................................................................................................................................................................
1830 PSS
19-3
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Before you begin
A replacement dust filter (either a new or a cleaned dust filter)
Instructions
Complete the following steps to replace the dust filter.

...................................................................................................................................................................................................
Remove the subrack cover plate of the dust filter carrier (A).
Result: The cover is opened and carrier is visible.
...................................................................................................................................................................................................
Take out the carrier

...................................................................................................................................................................................................
Pull out the wire mesh dust filter

...................................................................................................................................................................................................
On the replacement filter check that the protective adhesive film has been removed from
the wire mesh.
...................................................................................................................................................................................................
Insert the replacing wire mesh dust filter into the carrier.
Observe that the foam is covered by the wire mesh and foam is correctly placed beneath
the wire mesh. Observe correct orientation and assembly as shown in the following
picture.
....................................................................................................................................................................................................................................
1830 PSS
19-4
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Insert the dust filter carrier beneath the fan into the subrack.
...................................................................................................................................................................................................
Discard or clean the dirty dust filter.

Additional info There are four easy ways recommended to clean Universal's
Windowpane, Quadrafoam and Uni-Foam Air Filters:

1. Cleaning using a vacuum cleaner
A few passes of a vacuum cleaner will remove accumulated dust and dirt in
seconds.
2. Cleaning using compressed air
Point compressed air nozzle in opposite direction of operating air flow (blow from
exhaust side toward intake side).
3. Cleaning using cold water
Under normal conditions the foam media used in Universal's Windowpane,
Quadrafoam and Uni-Foam filters require no oily adhesives. Collected dirt is
washed away quickly and easily using just a standard hose nozzle with plain
water.
4. Cleaning using warm, soapy water
Where stubborn air-borne dirt is present, the filter may be dipped in a solution of
warm water and mild detergent. Then simply rinse in clear water, let stand until
completely dry and free of moisture, and return to service.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
19-5
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................

When to use
Use this procedure to replace the Fan Unit (FAN3T8) or in case of initial installation (then
start on Step 3).
Recommended tools
Small Phillips screwdriver.

Location
The following figure illustrates the position of the fan units in the Alcatel-Lucent
1830 PSS-64 subrack (slots 92 and 93) as an example..
Figure 19-1 Fan Unit positions
Fan unit exchange interval
The fan unit exchange interval is 7.5 years at the latest.
....................................................................................................................................................................................................................................
1830 PSS
19-6
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Fan unit replacement
During the fan unit replacement in the Alcatel-Lucent 1830 PSS-64 subrack, cooling air
for the subrack is supplied only by one fan unit. Therefore only one fan unit can be
exchanged at once. Due to the heat capacities involved, the system can sustain this
condition for a short period of time. The target for the fan unit replacement is 2 minutes. 5
minutes can be used as long as the ambient temperature does not exceed 40 C (104 F).
During the fan unit replacement in the Alcatel-Lucent 1830 PSS-36 subrack, the only fan
unit supplying cooling air for the subrack is removed. Therefore, the fan unit should never
be removed for more than 2 minutes.
Before you begin
The Alcatel-Lucent 1830 PSS subracks and the related cabling are designed to make it
possible to exchange the fan unit within less than 2 minutes because the running system
can not be operated longer without getting damaged. Of course preparation time and
re-installation time (for loosening/fixing screws of the fan unit) are not included in these 2
minutes.
Unpack the new fan unit and check installation materials.
Note: The following information is provided in case of maintenance and repair. For
initial installation proceed with Step 3.
(Some figs. may refer to preceding figures but are still valid as reference from the
location and function perspective.)
Instructions
NOTICE
Replacing both fan units at the same time can lead to overheating and cause serious
equipment damage.
Always replace only one fan unit at a time.
...................................................................................................................................................................................................
Identify the fan unit to be replaced. In the Alcatel-Lucent 1830 PSS-64 subrack it is
located in slot 92 at the top part or slot 93 at the bottom part as depicted before.
....................................................................................................................................................................................................................................
1830 PSS
19-7
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Identify the fan unit to be replaced. In the Alcatel-Lucent 1830 PSS-36 subrack, it is
located in slot 41.
Figure 19-2 Fan Unit fixing screws
...................................................................................................................................................................................................
CAUTION
Hot-surface hazard
Uninstall the Fan Unit to be replaced by loosening the marked screws (see previous
image), open the slide latches at the Fan Unit (details see Correct operations for card
extraction (p. 19-13)) and pull out the unit using the slide latches as shown.
Note: Do not use any tools to pull out the Fan Unit.
Note: Do not detach finger guards positioned above the fans after extraction.
Figure 19-3 Fan Unit extraction
...................................................................................................................................................................................................
CAUTION
Pinch hazard
Do not place your fingers on top of the fan unit when sliding it into the subrack.
....................................................................................................................................................................................................................................
1830 PSS
19-8
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Slide in the new Fan Unit and push it carefully using the slide latches.
Figure 19-4 Fan Unit insertion
...................................................................................................................................................................................................
The Fan Unit must be pushed against the gasket to allow proper screw to thread
positioning.
Note: Do not use any tools to push the Fan Unit.
Fix the inserted Fan Unit using the marked screws.
Figure 19-5 Fan Unit fastening
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
19-9
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................

When to use
This procedure describes common rules for mounting cards, to
prevent power arcs while pack extraction

graceful shut-down SW (e.g. unmounting of file systems to avoid disk corruption)
Before you begin
Prior to the insertion of circuit packs please
handle all the circuit packs with care, especially the fairly heavy Matrix card
visually check that the connector blocks of circuit packs and NE backplanes are
undamaged
do not insert a circuit pack in the case of a damaged connector block!
Following cards have slide latches:
First-Level Controller card

All types of Agnostic Matrix card
All kinds of I/O cards
Full slot blank front plate
Fan Unit.
The following cards have handles:

Bus Termination Card CMISS (except BTC in 1830 PSS-36 system)
Power Supply, Filter, and Clock Interface Card

Growth controller slot blank front plate.
....................................................................................................................................................................................................................................
1830 PSS
19-10
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Correct operations for card insertion

...................................................................................................................................................................................................
Open the latches prior to the plug-in of the unit (see (A) and (B) on fig. following).
Figure 19-6 Correct insert operations
Slide
latches
...................................................................................................................................................................................................
To mate the plastic body of the connectors push on the front panel, balancing the strain
without push on the latches (see (C) on preceding fig.).
....................................................................................................................................................................................................................................
1830 PSS
19-11
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Result: As long as both latches are open:
The board is supplied with the service voltage.
The condition IMPROPRMVL is cleared after validation time.
...................................................................................................................................................................................................
Close the first latch. (see (D) on preceding fig.) and follow next step at the same time.
Result: After the first latch is closed:
it is guaranteed that service voltage can be used.

the 48 V supply voltage of the card is still off.
condition LATCHOPEN raised after polling and validation time.
...................................................................................................................................................................................................
Close the second latch (see (D) on preceding fig.).

Result: After the second latch is closed:
FLC, MTX, FAN:

The 48 V supply voltage is switched on by HW.
I/O cards:
The SLC on the active MTX first checks whether the I/O card can be powered or
not (e.g. due to provisioning constraints). Only if there are none the 48 V supply
voltage for the I/O card is switched on by the SLC.
Condition LATCHOPEN cleared after validation time, if it was raised.
Note: The 48 V supply voltage will only be switched-on automatically for controller
cards (which get also automatically provisioned).
...................................................................................................................................................................................................
Fix the unit to the subrack by means of screws (if applicable), before to insert another
unit.
Note: For some cards are designed with self-locking latches (for example,
10XANY10G, 24XANYMR, 2XANY40G, and their substituting blank front plate) no
fasting screws are applied.
Note: For blank front plates that are designed without latches fasten screws in any
case after insertion.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
19-12
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Forbidden operations for card insertion
Refer to graphic after this procedure.

...................................................................................................................................................................................................
Don't push just on one latch only.

...................................................................................................................................................................................................
Don't force the units.

...................................................................................................................................................................................................
Avoid impact during the units handling.

Figure 19-7 Forbidden insertion operations
NO
NO
NO
E...................................................................................................................................................................................................
N D O F S T E P S
Correct operations for card extraction
Note: Some cards will need unscrewing them from the subrack first by means of
screws.
....................................................................................................................................................................................................................................
1830 PSS
19-13
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Open the first latch. Shift the latch according to the figure, see (A). Act on the latch
opening gently as shown on (B) in the figure.
Figure 19-8 Slide latch usage
Note: Not shifting the slide will damage either the latch or the locking mechanism of
the card.
....................................................................................................................................................................................................................................
1830 PSS
19-14
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Result: If the first latch is opened on card without graceful shutdown support:
Condition LATCHOPEN raised after polling and validation time
CARD STATUS LED remains in current state
48 V supply voltage of the card is still present. No impact on transmission.

Service voltage of the card still present. Latch state can still be evaluated.
If the first latch is opened on card with graceful shutdown support:

Condition LATCHOPEN raised after polling and validation time
An interrupt is initiated to trigger graceful shutdown of the software
CARD STATUS LED according graceful shutdown (green blinking)
Condition INTLANFAIL raised and OOS for the card after validation time (no
secondary voltages anymore)
48 V supply voltage of the card is still present.
Service voltage of the card still present.
After successful shutdown the 48 V power supply is switched off
After successful shutdown the CARD STATUS LED changes to off, based on HW
consequent action. (No restart after 15 min.)
...................................................................................................................................................................................................
Open the second latch. Shift the latch according to the figure, see (A). Act on the latch
opening gently as shown on (B) in the figure.
Note: Not shifting the slide will damage either the latch or the locking mechanism of
the card.
Result: If the second latch is opened on card without graceful shutdown support:
48 V supply voltage is switched off

Condition LATCHOPEN raised after polling and validation time, if not already
performed by step 1.
Condition HWFAIL raised and OOS for the card after validation time (no
secondary voltages anymore)
Note that in case of the MTX card the Condition LSSC will be additionally raised
after validation time (no secondary voltages anymore)
Service voltage from the backplane still present. Latch state can still be evaluated.
CARD STATUS LED changed to permanent RED, based on HW consequent
action.
If the second latch is opened on card with graceful shutdown support:

48 V supply voltage is switched off
Condition LATCHOPEN raised after polling and validation time, if not already
performed by step 1.
....................................................................................................................................................................................................................................
1830 PSS
19-15
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Condition INTLANFAIL raised and OOS for the card after validation time, if not
already performed by step 1.
Service voltage from the backplane still present. Latch state can still be evaluated.
CARD STATUS LED changed to permanent off, based on HW consequent action.
Important! For the FLC, it may happen that a graceful shutdown is not possible. In
that case the FLC is stopped immediately after the first latch has been opened, no
LED indications and no "Latch open" alarming takes place. The FLC can be removed.
...................................................................................................................................................................................................
Pull the card as shown in the picture.

Figure 19-9 Correct card extraction
Result: If a card has been removed:
Condition LATCHOPEN cleared after validation time, as the Latch state can not be
evaluated anymore.
Condition IMPROPRMVL raised after validation time.
other standing conditions for this card cleared after validation time.
Additional (common) behavior, if both card latches are open:

As the service voltage is still available, the RI can still be retrieved.
But due to the fact that 48 V supply is switched off other functionalities do not
work anymore. This can result in equipment defects of the card (for example,
dHWFail or dTransmHW)
....................................................................................................................................................................................................................................
1830 PSS
19-16
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
Additional behavior of the active FLC on latch open:

If latches are opened on active FLC, an FLC EQP occurs.
Reporting of conditions is suspended and resumed after the previous standby FLC
takes over the active role.
Latch closed before card is extracted: If the first latch is closed before or after the
graceful shutdown period has finished:
If an FLC is currently in the phase of graceful shutdown (power still on), then this
FLC restarts at the end of the shutdown if both latches are closed at that time (no
power off to take place).
If an FLC has been shutdown its power at the end of the graceful shutdown
period, then this FLC starts up again upon closure of that single-opened latch.
Note: For all cards that are designed without latches (for example, blank front plates,
BT3T8 and BTC3T8) use relating handle to pull for extraction, after loosening the
screws.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
19-17
Issue 1 June 2013
Routine procedures
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
19-18
Issue 1 June 2013
20
20
Overview
Purpose
The purpose of this chapter is to describe the installation procedures of the Alcatel-Lucent
1830 PSS Zero Installation Craft Terminal (ZIC) and WebUI application software on a PC
and to give basic operating instructions.
The Alcatel-Lucent 1830 PSS ZIC application has a graphical user interface (GUI)
allowing the user to interact with the NE through visual and graphical elements along
with text navigation representing the information and actions available to the user.
Compared to the Command Line Interface (CLI) which required numerous commands to
be typed on the keyboard, the Alcatel-Lucent 1830 PSS ZIC application allows greater
efficiency and ease of use through its GUI.
For Alcatel-Lucent 1830 PSS Release 6.0.0 the WebUI interface is started from within the
Alcatel-Lucent 1830 PSS ZIC for managing the WDM application of the NE.
For WDM only application the WebUI is to be used.
For configuring WDM specific parts the WebUI is to be used.
(p. 20-3)).
Contents
The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC)
20-3
General information
20-5
...................................................................................................................................................................................................................................
1830 PSS
20-1
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................
20-6
Navigation pane
20-8
Toolbar
20-10
Context menu
20-11
Property window
20-12
Configurable dialog box
20-13
Response Dialog Box
20-14
20-15
Tool tip
20-16
Error dialog box
20-17
Common Commands
20-18
Search function
20-19
Go To menu
20-21
View menu
20-22
Show Alarms menu
20-23
20-24
Concepts for connecting the Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC) to the NE
20-25
Combined Alcatel-Lucent 1830 PSS ZIC / WebUI
20-26
Procedure 20-1: Initialize the NE using EZ setup tool
20-27
Procedure 20-2: Call up the Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC)
20-37
Procedure 20-3: Logout from Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC)
20-41

Using the WebUI
20-42
20-43
20-45
Procedure 20-4: Log into the WebUI
20-46
20-48
Procedure 20-6: Initial NE configuration
20-49
20-51
20-52
....................................................................................................................................................................................................................................
1830 PSS
20-2
Issue 1 June 2013
The Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC)
....................................................................................................................................................................................................................................

Terminal (ZIC)
Purpose
This section describes the basic functions of the Alcatel-Lucent 1830 PSS ZIC .
Relationship between Alcatel-Lucent 1830 PSS ZIC and the WebUI
The Navigation Pane of the Alcatel-Lucent 1830 PSS ZIC Management Window allows
the user to navigate through the NE equipment in a hierarchical fashion from the system
level down to the port level and select a single entity from the hierarchy. The navigation
panel provides the equipment selection mechanism for all the NE management functions
supported. The selection on the NE Equipment Tree is always in sync with the
information displayed in the display pane.
If WDM application is to be handled you have to simple click on the WDM tab on top of
the frame. Then the WebUI is opened in the ZIC browser.
Note: Once opened all WebUI functions are available.
Relationship between Alcatel-Lucent 1830 PSS ZIC and TL1
System administration is performed through Alcatel-Lucent 1830 PSS ZIC and

Transaction Language 1 (TL1). TL1/TL1DAT - Enter Transaction Language 1 (TL1)
commands with the assistance of the TL1 Direct Access Terminal (TL1DAT) interface.
Certain commands that are unavailable through the Alcatel-Lucent 1830 PSS ZIC may be
performed with TL1DAT.
Contents
General information
20-5
20-6
Navigation pane
20-8
Toolbar
20-10
Context menu
20-11
Property window
20-12
20-13
Response Dialog Box
20-14
20-15
....................................................................................................................................................................................................................................
1830 PSS
20-3
Issue 1 June 2013
Terminal (ZIC)
....................................................................................................................................................................................................................................
Tool tip
20-16
Error dialog box
20-17
Common Commands
20-18
Search function
20-19
Go To menu
20-21
View menu
20-22
Show Alarms menu
20-23
....................................................................................................................................................................................................................................
1830 PSS
20-4
Issue 1 June 2013
General information
Terminal (ZIC)
....................................................................................................................................................................................................................................
General information
The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) is a web interface
embedded in the NE software. As it does not require any special installation, it is called
Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC), or short Alcatel-Lucent
1830 PSS ZIC because it is especially used to configure NE units.
The Alcatel-Lucent 1830 PSS ZIC runs as a Java Application, which requires as a
prerequisite a Java runtime environment to be installed on the ZIC host. The Java
Application is loaded from the NE via https requests.
The Java version running on the Alcatel-Lucent 1830 PSS ZIC PC must be Java
version 1.6.0_31 or higher. You can verify the used version using http://www.java.com/
verify/.
For the User Assistance functionality of the Alcatel-Lucent 1830 PSS Zero Installation
Craft Terminal (ZIC) application a weblication is used that displays information in
HTML. Therefore the off-the-shelf browsers Mozilla Firefox, Version 3 (or newer) or
Internet Explorer 7.0 (or newer) are recommended. It is recommended only to use the 32
bit versions of the browsers. The browser to be used must be set the default browser on
the personal computer on which the Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC) is running.
Alcatel-Lucent 1830 PSS ZIC functions
The Alcatel-Lucent 1830 PSS ZIC is capable of performing the following:
Supports general management functions such as port configuration, resets, etc.

Supports the configuration management of the NE
Supports the alarm handling and the performance monitoring (PM) of the NE.
....................................................................................................................................................................................................................................
1830 PSS
20-5
Issue 1 June 2013
Terminal (ZIC)
....................................................................................................................................................................................................................................

Overview of the Alcatel-Lucent 1830 PSS ZIC window
The components of the Alcatel-Lucent 1830 PSS ZIC Management window are the
following (see Figure 20-1, Alcatel-Lucent 1830 PSS ZIC Management Window
(p. 20-7)):
Title Bar
Shows the name of the NE for which the console has been launched.
Main Menu Bar
Provides control options for the NE.
Tool Bar
Provides navigation buttons that are always available. See Toolbar (p. 20-10).
Navigation Pane
Displays the navigation tree and node configurations. See Navigation pane
(p. 20-8).
Display Pane
Displays the contents of the node selected in the Navigation Pane in either Details
View or Graphical View. In Details View, click a column heading to sort data.
....................................................................................................................................................................................................................................
1830 PSS
20-6
Issue 1 June 2013
Terminal (ZIC)
....................................................................................................................................................................................................................................
Figure 20-1 Alcatel-Lucent 1830 PSS ZIC Management Window

Toolbar
Main Menu Bar
Scroll Bar Navigation Pane
Title Bar
Display Pane
....................................................................................................................................................................................................................................
1830 PSS
20-7
Issue 1 June 2013
Navigation pane
Terminal (ZIC)
....................................................................................................................................................................................................................................
Navigation pane
Navigation tree
The Navigation Tree in the Navigation Pane displays all domains and nodes supported by
Alcatel-Lucent 1830 PSS ZIC for the selected NE. Next to each node is a folder icon, or
an alarm icon, or both.
Domains
Domains are top-level entities. The following domains are available at the first-level of
the Navigation Tree: Equipment, Facilities, Protection, Cross-Connection, and System.
Each domain contains at least one node.
Nodes
Nodes are parts of a domain. In the Navigation Tree, nodes are indicated by folders that
begin at the second level and branch out into deeper detail. Some nodes contain other
nodes. For example, the NE Security folder in the System domain may contain a Users
folder to perform general user account tasks, and a User Instances folder to manage
specific user accounts.
Folder icon
Indicates that more information is available inside the node. Click the folder icon to open
a folder (expand) or close a folder (collapse).
Alarm icon
Indicates the highest-level alarm among all of the contents of the node.
Alarm icons are colored balls with a letter indicating the highest-level alarm.
Four alarm icons are defined as follows:
Critical alarm icon

Red ball
Major alarm icon

Orange ball
Minor alarm icon

Yellow ball
....................................................................................................................................................................................................................................
1830 PSS
20-8
Issue 1 June 2013
Navigation pane
Terminal (ZIC)
....................................................................................................................................................................................................................................
Primary state icon
Primary State icons are colored balls indicating the primary state of the entity.
Three primary state icons are defined as follows:
In-Service (IS) icon

Green ball
Out-Of-Service (OOS) icon

Red ball
Out-Of-Service (OOS) with Secondary State Unassigned (UAS) icon

Gray ball
....................................................................................................................................................................................................................................
1830 PSS
20-9
Issue 1 June 2013
Toolbar
Terminal (ZIC)
....................................................................................................................................................................................................................................
Toolbar
The tool bar provides push-button access to common menu options.
Home
Click the Home button to move to the top level in the Navigation Tree in the Navigation
Pane.
Parent
Click the Go To Parent button to move up one level in the Navigation Tree in the
Navigation Pane.
Back
Click the Go Backward button to move to the previous location visited.

Forward
Click the Go Forward button to move to the next location visited. This button is available
only if used in conjunction with the Go Backward button.
....................................................................................................................................................................................................................................
1830 PSS
20-10
Issue 1 June 2013
Context menu
Terminal (ZIC)
....................................................................................................................................................................................................................................
Context menu
A context menu is a list of command shortcuts that changes based on the actions available
for the selected entity. Context menus are available from the Navigation Tree, Display
Pane, inside tables, and other parts of the Alcatel-Lucent 1830 PSS ZIC. Context menus
are accessed by right-clicking the selected entity.
If multiple entities are selected, only the actions valid for all selected entities are shown.
Actions unavailable due to the state of the selected entity are shown in gray. Actions
unavailable due to security access privileges are not shown.
Figure 20-2 Example: Context menu
Context menu
Context submenu
....................................................................................................................................................................................................................................
1830 PSS
20-11
Issue 1 June 2013
Property window
Terminal (ZIC)
....................................................................................................................................................................................................................................
Property window
Entity properties are displayed and edited in a property window. Property windows
typically use mutable tables, which contain editable or non-editable text fields, spinners,
or combo boxes.
Click the arrow inside a column heading to sort the column in ascending or descending
order. In some cases, click the drop-down arrow inside a cell to launch a browser. The
first cell of a mutable table typically contains the AID of the entity and its alarm status.
A red triangle at the top, left corner of a cell indicates that a change has been made. If the
value of the cell is changed back to its original value, the red triangle is removed. All red
triangles in a table are removed when the Apply button at the bottom of the property
window is clicked. A red plus sign at the top, left corner of a cell indicates that a conflict
exists. The red plus sign is removed when the conflict is resolved.
Figure 20-3 Example: Properties window
....................................................................................................................................................................................................................................
1830 PSS
20-12
Issue 1 June 2013
Terminal (ZIC)
....................................................................................................................................................................................................................................

A configurable dialog box is an interactive tool that simplifies certain command tasks that
require a series of operations. Each dialog box consists of one page that lists all
parameters for that task. Mandatory fields are indicated in red.
Figure 20-4 Example: Configurable dialog box
If an error occurs and the dialog box is relaunched, it opens with the values that were
previously entered. This data is available only for the relaunched session. Data is not
saved and is not available if a user logs out, then logs back into the NE.
....................................................................................................................................................................................................................................
1830 PSS
20-13
Issue 1 June 2013
Response Dialog Box
Terminal (ZIC)
....................................................................................................................................................................................................................................
Response Dialog Box

A response dialog box allows the user to select input parameters and then send the TL1
command to the NE. Results from the command are displayed in a table below the input
parameters. If no results are returned from the command, the area below the input
parameters will display information on the commands success or failure.
Figure 20-5 Example: Response dialog box
The data displayed in this table is static and cannot be changed directly. Click Send to
refresh information.
If any parameters can be modified or deleted, a Modify or Delete button will be displayed
at the bottom of the table. Select a single row, then click the Modify or Delete button to
launch a separate dialog box. Click Send again to update the information when the
modify or delete is complete.
....................................................................................................................................................................................................................................
1830 PSS
20-14
Issue 1 June 2013
Terminal (ZIC)
....................................................................................................................................................................................................................................

A confirmation dialog box provides information, obtains a user response, or confirms a
potentially dangerous choice.
Figure 20-6 Example: Confirmation dialog box
There are three types of confirmation dialog boxes:
Informational confirmation dialog box

An informational confirmation dialog box provides information about results of a
command. The OK button at the bottom of the box is used to acknowledge the
message.
Warning confirmation dialog box

A warning confirmation dialog box provides information about a condition that
requires input. The option to back out of the action is provided.
Critical confirmation dialog box

A critical confirmation dialog box provides information about a serious problem that
requires intervention or correction before work can continue. The OK button at the
bottom of the box is used to acknowledge the message.
....................................................................................................................................................................................................................................
1830 PSS
20-15
Issue 1 June 2013
Tool tip
Terminal (ZIC)
....................................................................................................................................................................................................................................
Tool tip
To display a tool tip, place the cursor over any part of the Navigation Pane or inside
views, tables, and dialog boxes in the Display Pane.
Figure 20-7 Example: Tool tip
....................................................................................................................................................................................................................................
1830 PSS
20-16
Issue 1 June 2013
Error dialog box
Terminal (ZIC)
....................................................................................................................................................................................................................................
Error dialog box

An error dialog box displays when a command fails. The error message consists of a
description of the error and the reason for failure. Click Details to display the error
response from the NE. If multiple errors occur, each error displays an individual error
dialog box.
Figure 20-8 Example: Error dialog box
....................................................................................................................................................................................................................................
1830 PSS
20-17
Issue 1 June 2013
Common Commands
Terminal (ZIC)
....................................................................................................................................................................................................................................
Common Commands
Purpose
The following commands are common to most domains through the Main Menu Bar or
Context Menus.
Open
The Open menu option displays contents of the selected node. In the Navigation Tree,
click the key symbol to the left of the node. In the Display Pane, double-click a folder.
Open in New Window
The Open in New Window menu option opens a new ALMC window with the selected
node in the Navigation Pane and its contents in the Display Pane.
Refresh
The Refresh menu option verifies that displayed data is the same as the data on the NE.
The Refresh command performs the following:
All attributes for the selected node are re-retrieved from the NE.
The contents of the selected node are re-retrieved. Contents that are unavailable on the
NE are removed, and new contents are added.
General
The General menu option launches a properties window that displays general properties
of the current selection.
Figure 20-9 Example: General properties window
....................................................................................................................................................................................................................................
1830 PSS
20-18
Issue 1 June 2013
Search function
Terminal (ZIC)
....................................................................................................................................................................................................................................
Search function
The search function is available from many node drop-down menus. Search can be used
to quickly find specific boards or facilities. The search function looks for matches based
upon a selected criteria, starting from the currently selected folder and sub-folders
Figure 20-10 Example: Search command
The following criteria are available for the search function in the Equipment Management
domain (see Figure 20-11, Example: Search dialog (p. 20-20)):
EMA AID (default)
NE AID
Part Number
Serial Number
The following criteria are available for the search function in the Facility Management
domain:
EMA AID (default)
FACNAME (if the NE supports facility naming)
NE AID
....................................................................................................................................................................................................................................
1830 PSS
20-19
Issue 1 June 2013
Search function
Terminal (ZIC)
....................................................................................................................................................................................................................................
Figure 20-11 Example: Search dialog
EMA AID searches for an object based on the AID as presented in the EMA while an NE
AID searches for an object based on the AID as on the NE. For most equipment and
facilities, these are the same.
A percent sign (%) is a wildcard character that is used to search for multiple matching
entities. If only one match is found, the EMA navigates directly to the matched item. If
multiple matches are found, a table of search results is displayed with the matched items.
See Figure 20-12, Example: Search result (p. 20-20). The wildcard character may not
be used to search on an NE AID.
Figure 20-12 Example: Search result
Double-click a row in the search results table to navigate to the selected equipment or
facility.
....................................................................................................................................................................................................................................
1830 PSS
20-20
Issue 1 June 2013
Go To menu
Terminal (ZIC)
....................................................................................................................................................................................................................................
Go To menu
The Go To menu provides fast navigation to the most common functions based on the
current selection.
Figure 20-13 Example: Go to
The Go To command menu provides the following domain navigation short cuts:
Equipment Management Facility Management
Facility Management CrossConnection Management

Facility Management Equipment Management
Facility Management Protection Management
Facility Management Test Access Management
CrossConnection Management Facility Management
CrossConnection Management Test Access Management
Protection Management Facility Management
Protection Management CrossConnection Management
....................................................................................................................................................................................................................................
1830 PSS
20-21
Issue 1 June 2013
View menu
Terminal (ZIC)
....................................................................................................................................................................................................................................
View menu
Equipment selected in the navigation tree is displayed in different ways:
In a list called the Details View.
An overview of the equipment Properties.
Graphical representation of the equipment called the Graphical View.
An overview of the inventory data of the selected equipment called Inventory view.
Figure 20-14 Example: View menu
The View menu option toggles between each display method.
....................................................................................................................................................................................................................................
1830 PSS
20-22
Issue 1 June 2013
Show Alarms menu
Terminal (ZIC)
....................................................................................................................................................................................................................................
Show Alarms menu

The Show Alarms menu option, available from the Navigation command in the Main
Menu Bar, launches the Alarm Surveillance application.
....................................................................................................................................................................................................................................
1830 PSS
20-23
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
The purpose of this section is to describe the installation procedures of the Alcatel-Lucent
1830 PSS Zero Installation Craft Terminal (ZIC) application software on a PC and how to
log into and log out from the Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal
(ZIC).
Contents
Concepts for connecting the Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC) to the NE
20-25
20-26
20-27
Procedure 20-2: Call up the Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC)
20-37
Procedure 20-3: Logout from Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC)
20-41
....................................................................................................................................................................................................................................
1830 PSS
20-24
Issue 1 June 2013
Concepts for connecting the Alcatel-Lucent 1830 PSS Zero

Installation Craft Terminal (ZIC) to the NE
....................................................................................................................................................................................................................................
Concepts for connecting the Alcatel-Lucent 1830 PSS Zero

Installation Craft Terminal (ZIC) to the NE
Purpose
The purpose of this section is to describe how the Alcatel-Lucent 1830 PSS Zero
Installation Craft Terminal (ZIC) can be connected to an NE and how you can establish a
connection to the NE on the Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal
(ZIC).
Ways of connecting the Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) to a
network element
The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) can be connected to
a network element in different ways:
Direct LAN Access (point-to-point)

LAN Access (network)
Remote Access via TCP/IP.
Direct LAN access (point-to-point)
The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) (LAN card) is
connected to the Alcatel-Lucent 1830 PSS via the CIT port on one of the two FLCs. A
crossover LAN cable (CAT5) with RJ-45 connectors must be used for this connection.
NOTE: The crossing can also be realized by a C5XOVER adapter (female to female).
This adapter works inline with two CAT5 straight cables.
The usage of shielded 100BaseT LAN cables is only allowed if the applicable national
safety requirements have been met by the user. Otherwise, there is a risk of electrical
shock and/or serious injury.
Important! Use a static ground wrist strap whenever handling circuit packs or
working on a Alcatel-Lucent 1830 PSS system, to prevent electrostatic discharge
damage to sensitive components.
Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) access via TCP/IP
The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) can be connected to
NEs via TCP/IP in the following ways:
Direct connection to the LAN port

through an IP network (Intranet)
through Gateway NE.
....................................................................................................................................................................................................................................
1830 PSS
20-25
Issue 1 June 2013
....................................................................................................................................................................................................................................

Setting up combined Alcatel-Lucent 1830 PSS ZIC / WebUI
Before accessing the WDM functionality via the ZIC, the following needs to be
provisioned.
1. The Connected Photonic Compound / Partner NE has to be entered on the OCS
compound. This is the IP address of the WDM compound. The converged
Alcatel-Lucent 1830 PSS ZIC / WebUI uses this to access the WDM compound. If the
Partner NE is not provisioned on the OCS compound, then the WDM functionality
can only be accessed via the stand-alone WebUI.
How to enter the Connected Photonic Compound / Partner NE on the OCS
compound is described in Procedure 20-1: Initialize the NE using EZ setup tool
(p. 20-27).
2. The user ID and password that is used to access the Alcatel-Lucent 1830 PSS ZIC
must also be provisioned on the WDM compound. This could be provisioned via the
stand-alone WebUI (see Procedure 2-25: Create a user (p. 2-93)).
If the User ID/Password is not provisioned on the WDM compound and the Partner
NE is provisioned using the Alcatel-Lucent 1830 PSS ZIC, then the ZIC displays the
WebUI login screen when trying to access the WDM compound.
When prompted with the WebUI login screen, the user must enter a valid User ID and
password that pertains to the WDM compound (see Procedure 20-4: Log into the
WebUI (p. 20-46)).
Changing Partner NE
If the Connected Photonic Compound / Partner NE on the OCS compound is modified,
the FLC has to be restarted, refer to Procedure 5-25: Initiate a circuit pack reset
(p. 5-117).
....................................................................................................................................................................................................................................
1830 PSS
20-26
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
Use this procedure to initialize the NE using EZ setup tool.

Before you begin
Prior to performing this task, you have to assure that:
if a firewall is running on the PC, that it is disabled.
the pop-up blocker is disabled, if enabled.

you have a temporary certification on secure http (for example, https://). Customers
can get it, following the browser indications.
Assure that the PC LAN interface is either setup manually in the 169.254 subnet or
DHCP with APIPA (Zero config) is enabled on the PC.
you have a valid user login and password.
Java 1.6 is installed on the PC.
use either:
Mozilla Firefox 3.0 or newer is installed on the PC (32 bit versions only).
Internet Explorer 7.0 or newer is installed on the PC (32 bit versions only).
Note: For entering IP address data certain steps require to use dashes - instead of
dots for number separation. (as common IP notation). Compare Step 13 to Step 17,
Step 23, Step 25, and Step 29.
Instructions
...................................................................................................................................................................................................
Connect your PC to the CIT interface located on the FLC cards using a LAN cable.
On the FLC in an Alcatel-Lucent 1830 PSS-64 subrack the interface is identified by

CIT.
On the FLC in an Alcatel-Lucent 1830 PSS-36 subrack the interface is identified by

CIT.
...................................................................................................................................................................................................
Start the default browser and enter https://<NE IP Address>.

Enter: https://169.254.129.111/ .
....................................................................................................................................................................................................................................
1830 PSS
20-27
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: If a dialog box opens telling that there is a problem with the security
certificate accept the security exception.

When opening this web page for the first time the following or similar security issues
are mentioned by different Web-Browsers:
The security certificate presented by this website was not issued by a trusted
certificate authority.
The security certificate presented by this website was issued for a different
website`s address.
In this release the system supports only a self-signed certificate to build up a secure
SSL/HTTPS connection between NE and Client PC.
In a future release the NE will be enhanced, that customer related certificates can be
installed. This avoids the security messages above.
Additional info: You can check if the secure SSL/HTTPS connection is originated
from the 1830 NE, by displaying the certificate. To display the certificate act as
recommended in the Online Help of your used browser.
The self-signed certificate must have the following content:
CN = Alcatel-Lucent
OU = Optics
O = Alcatel-Lucent
L = Nuremberg
S = Germany
C = DE
Thumbprint is: 2e 61 2b 78 c4 0c fb b1 ea 5e df fc 74 f6 9c 11 41 b6 a8 21
...................................................................................................................................................................................................
If the above mentioned messages are displayed, click on

Continue to this website (not recommended).
....................................................................................................................................................................................................................................
1830 PSS
20-28
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: The Alcatel-Lucent 1830 PSS window opens.
...................................................................................................................................................................................................
Note: The very first thing to do is to Change the Password. Everything else will fail
otherwise.
Important! If the session is dropped due to 3 minutes idle time after login please
leave Easy Setup by clicking on Home and start Easy Setup again.
The following steps have to be performed using this tool, either sequentially (it is
recommended to follow the wizard in the right order), or, if needed, in single steps:
If you want to
then
perform the steps sequentially
change the password
set the region parameter
Select EZ SETUP Change Region and continue with Step

11.
define the FLC IP addresses
Select EZ SETUP Change FLC IP Address and continue

with Step 13.
define the Loopback IP Address
Select EZ SETUP Change Loopback IP Address and

define the Control Plane IP

address
Select EZ SETUP Change GMRE IP Address and continue

with Step 25.
create the NTP Server
Select EZ SETUP Change NTP Server IP Address and

define the OCS Shelf Type and

define Connected Photonic
Compound / Partner NE
Select EZ SETUP Create OCS Shelf and continue with

Step 32.
....................................................................................................................................................................................................................................
1830 PSS
20-29
Issue 1 June 2013
....................................................................................................................................................................................................................................
If you want to
then
define Connected Photonic

Compound / Partner NE
Select EZ SETUP Change Partner IP Address and

define the OCS Shelf Type
Select EZ SETUP Create OCS Shelf and continue with

Step 32.
define the NE name
Select EZ SETUP NE Name Init and continue with Step

35.
...................................................................................................................................................................................................
Select EZ SETUP Change Password.

Result: A login window is displayed.
...................................................................................................................................................................................................
In the field User Name enter a User Identifier (UID) and the respective Password
Identifier (PID).
You can use your User Identifier (UID) or one of the following predefined user types:
Table 20-1
Default User
USER05
SERVICE
EML001
EML002
Default Password
identifier
ADMIn005
Ansi_4GX
Eml__001
Eml__002
Result: The Network Element Initialization : Change Password window is
displayed.
...................................................................................................................................................................................................
Place the cursor in the Current Password text box, then type in the current password.
...................................................................................................................................................................................................
Place the cursor in the New Password text box, then type in your new password.
...................................................................................................................................................................................................
Place the cursor in the Confirm New Password text box, then type in your new password
again.
...................................................................................................................................................................................................
10
Click Submit.
....................................................................................................................................................................................................................................
1830 PSS
20-30
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: The Network Element Initialization : Change Region window is displayed.

...................................................................................................................................................................................................
11
Using the Network Element Region spin box, select the region, either ETSI or ANSI.
...................................................................................................................................................................................................
12
Click Submit.
Result: The Network Element Initialization : Change FLC IP window is displayed.
...................................................................................................................................................................................................
13
In the field Active FLC IP Address enter the IP address for the active FLC.
Note: The IP address must be entered with - (dashes) as separator between the
segment numbers.
This address follows the active FLC on each FLC EPS switch.
...................................................................................................................................................................................................
14
In the field FLCA IP Address modify the IP address of the left FLC.
The factory default is 18-70-1-1. This address is always configured on the (front
view) leftmost FLC card (Slot 73 in PSS-64 system, slot 23 in PSS-36 system)
...................................................................................................................................................................................................
15
In the field FLCB IP Address modify the IP address of the right FLC.
The factory default is 18-70-1-2. This address is always configured on the rightmost
FLC card (Slot 75 in PSS-64 system, slot 40 in PSS-36 system)
...................................................................................................................................................................................................
16
In the field LAN Gateway IP Address: enter the IP address of the Customer LAN default
gateway router (connected to the OAMP LAN).
....................................................................................................................................................................................................................................
1830 PSS
20-31
Issue 1 June 2013
....................................................................................................................................................................................................................................
Additional information: {1-99,101-126,128-223} - {0-255} - {0-255} - {0-255}
Internet Protocol address of the gateway router, connected to the OAMP LAN. The
address must be part of the IP subnet configured on the OAMP LAN via the
identical to any of the ACTIVEFLCIP, FLCAIP, FLCBIP addresses. Neither the
network nor the host portion of the address (with respect to the value of the MASK
parameter) when viewed in binary format may be all 0s or all 1s.
The factory default is 0-0-0-0, meaning that no default route is set via the OAMP
LAN. Changing the value back to 0-0-0-0 is equivalent to removing the default route.
...................................................................................................................................................................................................
17
In the field Subnet Mask enter the subnet mask of the network the NE is connected to on
the Customer LAN.
Additional information: {128-255} - {0-255} - {0-255} - {0-248}
Alternatively the mask can be provided in CIDR notation: {1-29}

network portion) followed by a contiguous string of 0s (the host portion). All IP
addresses specified have to be in the same subnet.
...................................................................................................................................................................................................
18
Click Submit.
Result: The ZIC Server Logout Page is displayed.
Additional information: After submitting the previous settings (FLC IP addresses
and gateway) the communication to the NE is lost.

From then on a different LAN port (the LAN interface OAMP) on the FLC has to be
used (connecting via the new provisioned IP address). In order to connect to the NE
via the OAMP LAN interface, a fixed IP address has to be set on your PC before. In
the same subnet as the NE, but different from any used IP.
...................................................................................................................................................................................................
19
You can either return to the main page or logout by clicking on the respective button.
Result: In the Welcome to Alcatel-Lucent 1830 PSS Craft Terminal window the
following text is displayed:

1.
2.
3.
4.
To start the ZIC client:

Disconnect the ZIC PC from the CIT LAN
Connect the ZIC PC to the OAMP LAN
Configure the ZIC PC to use a free address from the OAMP LAN
subnet
....................................................................................................................................................................................................................................
1830 PSS
20-32
Issue 1 June 2013
....................................................................................................................................................................................................................................
5. Connect to the Web-server on the NE , by using the active FLC IP

address See IP address above
...................................................................................................................................................................................................
20
Disconnect your PC from the CIT LAN.

...................................................................................................................................................................................................
21
Select EZ SETUP Change Loopback IP Address.

...................................................................................................................................................................................................
22
Connect your PC to the OAMP LAN.

...................................................................................................................................................................................................
23
The Network Element Initialization : Change Loopback IP window is displayed.

In the field Loopback IP Address enter the Loopback IP address.
The NE loopback address is also used as OSPF Router Id. The address must not be
part of the IP subnet configured on the customer LAN via the ACTIVEFLCIP,
FLCAIP, FLCBIP, MASK parameters. The address must not be identical to the
GMRE IP address.
The factory default is 0-0-0-0. Once changed, this parameter cannot be reset to factory
default.
...................................................................................................................................................................................................
24
Click Submit.
Result: The Network Element Initialization : Change Control Plane IP window is
displayed.
...................................................................................................................................................................................................
25
In the field GMRE IP Address: enter the IP address of the Control Plane.
....................................................................................................................................................................................................................................
1830 PSS
20-33
Issue 1 June 2013
....................................................................................................................................................................................................................................
The address must not be part of the IP subnet configured on the customer LAN via the
identical to the LOOPBACK IP address.
The factory default is 0-0-0-0. Once changed, this parameter cannot be reset to factory
default.
...................................................................................................................................................................................................
26
Click Submit.
Result: The Network Element Initialization : Create NTP Server window is
displayed.
...................................................................................................................................................................................................
27
In the field Server IP enter the network address of the NTP server.
Note: To separate the fields use a hyphen instead of a dot.
Additional info: NTP servers are used for time of day synchronization. You can enter
up to 10 NTP trusted servers.

Note: It is expected that all external time servers are running on the same
time-base, i.e. that all of them are synchronized from a reliable wall-clock.
...................................................................................................................................................................................................
28
Click Submit.
Result: The Create Partner NE window is displayed.
...................................................................................................................................................................................................
29
In the field Connected Photonic Compound / Partner NE: enter the IP Address of the
WDM Partner NE to define to which WDM Partner NE the OCS node belongs.
The factory default is 0-0-0-0. The default value is not valid if a photonic shelf is
connected.
The converged ZIC uses this to access the WDM compound. If Partner NE is not
provisioned on the OCS compound, then the WDM functionality can only be accessed
via the stand-alone WebUI.
...................................................................................................................................................................................................
30
Click Submit.
....................................................................................................................................................................................................................................
1830 PSS
20-34
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: A screen is displayed showing the following:

This change needs a restart of the ZIC server application.
All logged-in user sessions will be closed. Are you sure?
...................................................................................................................................................................................................
31
Click Yes.
Result: The ZIC server application is restarted. All logged-in user sessions will be
closed.
...................................................................................................................................................................................................
32
Using the Main Shelf Type spin box, select the used Shelf Type, either PSS36 or PSS64.
Additional info: When selecting a shelf type the respective matrix capacity will be
defined, too:
for PSS64:
3840 Gb/s
1920 Gb/s
for PSS36:
1920 Gb/s
960 Gb/s
...................................................................................................................................................................................................
33
Using the Shelf Position In Rack: spin box, select the used Shelf Position in the rack.
Additional info: Possible values
Upper Subrack: (for Alcatel-Lucent 1830 PSS-36 shelf)
Center: (for Alcatel-Lucent 1830 PSS-64 shelf)
Lower Subrack: (for Alcatel-Lucent 1830 PSS-36 shelf)
...................................................................................................................................................................................................
34
Click Submit.
Result: The Network Element Initialization : NE Name Init window is displayed.
...................................................................................................................................................................................................
35
Place the cursor in the Network Element Name text box, then type in the Network
Element Name (SID).
Each NE name must be unique within the network.

The following characters are allowed in an NE name:
Uppercase letters (A .. Z),
Lowercase letters (a .. z),
....................................................................................................................................................................................................................................
1830 PSS
20-35
Issue 1 June 2013
....................................................................................................................................................................................................................................
Special characters (-),

Digits (0 .. 9).
Each NE name must be at most 20 characters in length.
The SID must start with a letter and must end with an alphanumeric character.
Consecutive hyphens (-) are not allowed.
Number of hyphens must not be greater than 4.
If a lower-case character string is entered for the SID, it is automatically converted to

an uppercase character string for comparison to any TID value entered in a command.
...................................................................................................................................................................................................
36
Click Submit.
Result: The ZIC Server Logout Page is displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
20-36
Issue 1 June 2013
Procedure 20-2: Call up the Alcatel-Lucent 1830 PSS Zero

Installation Craft Terminal (ZIC)
....................................................................................................................................................................................................................................

Purpose
Use this procedure to call up the Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC).
The Alcatel-Lucent 1830 PSS ZIC software is embedded on the NE.
Required equipment
Table 20-2
Minimum hardware/software requirements

Requirements
CPU
Pentium III 2 GHz, single core
RAM
2 GB
Hard Disk
40 GB
Interface
100BaseT LAN interface
Display Resolution
1024768
Java Runtime Environment (JRE)
Release 1.6.0_31 or higher
Content of Installation Package
The Alcatel-Lucent 1830 PSS ZIC has the following components :

1. Alcatel-Lucent 1830 PSS ZIC.
2. URL for enabling the download of the relevant JRE (Java Runtime Environment),
which is a third party component used by Alcatel-Lucent 1830 PSS ZIC
Required web browser
For the User Assistance functionality of the Alcatel-Lucent 1830 PSS Zero Installation
Craft Terminal (ZIC) application a weblication is used that displays information in
HTML. Therefore the off-the-shelf browsers Mozilla Firefox, Version 3 (or newer) or
Internet Explorer 7.0 (or newer) are recommended. It is recommended only to use the 32
bit versions of the browsers. The browser to be used must be set the default browser on
the personal computer on which the Alcatel-Lucent 1830 PSS Zero Installation Craft
Terminal (ZIC) is running.
....................................................................................................................................................................................................................................
1830 PSS
20-37
Issue 1 June 2013

....................................................................................................................................................................................................................................
Required Java version
The Java version running on the Alcatel-Lucent 1830 PSS ZIC PC must be Java
version 1.6.0_31 or higher. You can verify the used version using http://www.java.com/
verify/.
Before you begin
The installation program cannot install system files or update shared files if they are in
use by other programs. For this reason you should stop as many Windows applications
as possible, before starting with the installation procedure.
Prior to performing this task, you have to assure that:
if a firewall is running on the PC, that it is disabled.

the pop-up blocker is disabled, if enabled.
you have a temporary certification on secure http (for example, https://). Customers
can get it, following the browser indications.
a fixed IP address has to be set on your PC before. In the same subnet as the NE, but
different from any used IP (the subnet mask as configured using Procedure 20-1:
Initialize the NE using EZ setup tool (p. 20-27)).
Instructions
...................................................................................................................................................................................................
Power up the PC and log into Windows 7 / Windows XP . If you are already logged in,
close any open window.
...................................................................................................................................................................................................
Connect your PC to the DCN (OAMP) interface located on the FLC boards using a LAN
cable.
...................................................................................................................................................................................................
Download the respective software from the NE.

The NE provides a web page to download the required software to install the ZIC on your
PC.
The NE IP address has to be used.-->
Start the default browser and enterhttps://<NE IP Address>. Enter the IP address
provisioned as Active FLC IP Address when performing Procedure 20-1: Initialize the
NE using EZ setup tool (p. 20-27)..
....................................................................................................................................................................................................................................
1830 PSS
20-38
Issue 1 June 2013

....................................................................................................................................................................................................................................
Result: When opening this web page for the first time the following or similar
security issues are mentioned by different Web-Browsers:
The security certificate presented by this website was not issued by a trusted
certificate authority.
The security certificate presented by this website was issued for a different
website`s address.
In this release the system supports only a self-signed certificate to build up a secure
SSL/HTTPS connection between NE and Client PC.
In a future release the NE will be enhanced, that customer related certificates can be
installed. This avoids the security messages above.
Additional info: You can check if the secure SSL/HTTPS connection is originated
from the 1830 NE, by displaying the certificate. To display the certificate act as
recommended in the Online Help of your used browser.
The self-signed certificate must have the following content:
CN = Alcatel-Lucent
OU = Optics
O = Alcatel-Lucent
L = Nuremberg
S = Germany
C = DE
Thumbprint is: 2e 61 2b 78 c4 0c fb b1 ea 5e df fc 74 f6 9c 11 41 b6 a8 21
...................................................................................................................................................................................................
If the above mentioned messages are displayed, click on

Continue to this website (not recommended).
Result: The Alcatel-Lucent 1830 PSS window opens.
....................................................................................................................................................................................................................................
1830 PSS
20-39
Issue 1 June 2013

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Download the ZIC application by clicking on Click to Launch ZIC.

Result: After that the Connection Information / User Identification window opens.
...................................................................................................................................................................................................
Enter your User Identifier (UID) and the respective Password Identifier (PID).
...................................................................................................................................................................................................
Click OK to connect.
Note: If the Alcatel-Lucent 1830 PSS ZIC is used with Internet Explorer the
following Security Warning is displayed:
Do you want to view only the weppage content that was
delivered securely?
Accept the security risk!

Result: The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) GUI is
displayed.
E...................................................................................................................................................................................................
N D O F S T E P S
Regional and language settings
Important! It is strongly recommended to provision the regional and language

settings of the PC to English (United States).
....................................................................................................................................................................................................................................
1830 PSS
20-40
Issue 1 June 2013
Procedure 20-3: Logout from Alcatel-Lucent 1830 PSS Zero

....................................................................................................................................................................................................................................
Procedure 20-3: Logout from Alcatel-Lucent 1830 PSS Zero

Purpose
Many procedures throughout this document require the user log out of the Alcatel-Lucent
1830 PSS Zero Installation Craft Terminal (ZIC) GUI. The following procedure describes
how this is accomplished.
Instructions
...................................................................................................................................................................................................
In the Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) main window,
click File Exit.
Result: An confirmation window window appears.
...................................................................................................................................................................................................
IF
THEN
you are sure you want to exit
click Yes in the confirmation window.
you do not want to exit,
press the No pushbutton.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
20-41
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
For Alcatel-Lucent 1830 PSS Release 6.0.0 the WebUI interface is started from the
Alcatel-Lucent 1830 PSS ZIC for managing the WDM application of the NE. But
For WDM only application the WebUI is to be used.

For configuring WDM specific parts the WebUI interface is started from within the
Alcatel-Lucent 1830 PSS ZIC for managing the WDM application of the NE (see
The Alcatel-Lucent 1830 PSS Zero Installation Craft Terminal (ZIC) (p. 20-3)).
(p. 20-3)).
Contents
Using the WebUI
20-43
....................................................................................................................................................................................................................................
1830 PSS
20-42
Issue 1 June 2013
Using the WebUI
....................................................................................................................................................................................................................................
Using the WebUI

Overview
You access the WebUI interface using Internet Explorer running on a computer that is
connected via Ethernet to the NE, either directly or over a LAN.
WebUI hardware requirements
Laptop or desktop computer capable of running the required software.

Ethernet card (10 Mb/s minimum, 10/100 Mb/s recommended).
It is recommended that you use a monitor capable of displaying at a resolution of
1024x768 or greater.
WebUI software requirements
Windows XP, Windows 2000, or Windows 7 updated to the most recent patch level.
Internet Explorer 6.0, 7.0, 8.0, or 9.0 updated to the most recent patch level
or
Firefox 15
Note: The following functionality is not supported with the Firefox browser:
Power Commissioning page
Export to Excel
Show in separate window
Note: It is recommended only to use the 32 bit versions of the browsers.

Note: For newer version of Firefox, the click and play feature is enabled for java
plugin and the user will need to allow the java applets to run.
J2SE Java Runtime Environment (JRE) version 5.0 or later. The supported version for
the NE software version you are running is included on the NE software CD-ROM.
MAC OS 10.8 (with Firefox browser only)

Note: Vista is not supported for WebUI.
Navigating the WebUI
The Equipment Tree allows the user to navigate through the NE equipment in a
hierarchical fashion from the system level down to the port level and select a single entity
from the hierarchy. The NE Equipment Tree provides the equipment selection mechanism
for all the NE management functions supported. The selection on the NE Equipment Tree
is always in sync with the information displayed in the Display Panel.
....................................................................................................................................................................................................................................
1830 PSS
20-43
Issue 1 June 2013
Using the WebUI
....................................................................................................................................................................................................................................
When navigating the equipment tree, the following applies:
Click on the plus sign (+) next to the piece of equipment to expand the tree.
Click on the minus sign (-) next to a piece of equipment to collapse the tree.
Click on a piece of equipment to select it.
Equipment tree hierarchy
Figure 20-15, Equipment tree hierarchy (p. 20-44) depicts the equipment tree hierarchy:
Figure 20-15 Equipment tree hierarchy
The user will traverse the hierarchy and select a specific equipment to access the
functions supported by that equipment.
....................................................................................................................................................................................................................................
1830 PSS
20-44
Issue 1 June 2013
Overview
....................................................................................................................................................................................................................................

Overview
Purpose
The purpose of this section is to describe basic Alcatel-Lucent 1830 PSS WebUI
procedures
Contents
20-46
20-48
20-49
20-51
20-52
....................................................................................................................................................................................................................................
1830 PSS
20-45
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
The following procedure to log into the WebUI.

Instructions
...................................................................................................................................................................................................
If the WebUI was
then
started from the ZIC
The WebUI interface login window is

displayed.
not started from the ZIC
continue with the next step .
...................................................................................................................................................................................................
Launch the Internet Explorer browser.

...................................................................................................................................................................................................
Enter the IP address of the network element.

Result: The WebUI interface login window is displayed.
...................................................................................................................................................................................................
Note: If you are logging into the NE for the first time (that is, the NE has not yet been
provisioned), see Instructions (p. 20-49)
When a user connects to an NE after the initial NE configuration, the WebUI displays
a window where the user can enter their User ID and Password and submit the login
request.
...................................................................................................................................................................................................
Enter your User ID in the User: field.

...................................................................................................................................................................................................
Enter the password associated with the User ID in the Password: field. The characters you
enter for the password are not displayed.
Note: Passwords are case sensitive. If you experience difficulty logging in, verify that
the Caps Lock key is off.
...................................................................................................................................................................................................
Click on the Login button, or press the Enter key.
....................................................................................................................................................................................................................................
1830 PSS
20-46
Issue 1 June 2013
....................................................................................................................................................................................................................................
Result: Upon successful login, the System Details screen is displayed.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
20-47
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
The following procedure is used if a WDM stand alone application is implemented.

Instructions
...................................................................................................................................................................................................
To end the WebUI session, click on Logout.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
20-48
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
The following procedure is used if a WDM stand alone application is implemented.

Instructions
...................................................................................................................................................................................................
When connecting to an NE for the first time, connect the Ethernet cable (RJ45) from the
PC to the EC CIT port on the NE and type in the default IP address of 172.16.0.1 in order
to connect to the NE.
Result: A window is displayed where the user can enter their User ID and Password
and submit the login request.

...................................................................................................................................................................................................
Enter your User ID in the Username: field.

...................................................................................................................................................................................................
Enter the password associated with the User ID in the Password: field. The characters you
enter for the password are not displayed.
Note: Passwords are case sensitive. If you experience difficulty logging in, verify that
the Caps Lock key is off.
...................................................................................................................................................................................................
If the login is successful, the WebUI displays a message indicating that the database needs
to be initialized. The user will be given 2 options:
OK upon selection, the WebUI sends a request to the NE to initialize the database.
Note: Initializing the database causes the NE to reboot.

Cancel upon selection, the WebUI displays the System Details screen. From here,
the user can navigate to the Admin screens to configure the NE as needed (for
example, restore a previously backed up database).
Result: The following informational text will be displayed on the screen: The
database is invalid.
...................................................................................................................................................................................................
Select one of the following:
Click OK to initialize the database. The NE will automatically restart after

initialization is complete. This will interrupt service if the NE has live traffic.
Click Cancel to bypass initialization and proceed to the WebUI. Use this option when
the NE has services that you do not want to interrupt. You will be asked to supply an
NE Name and then the NE will automatically restart without affecting service.
....................................................................................................................................................................................................................................
1830 PSS
20-49
Issue 1 June 2013
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................
When the user logs into the NE after database initialization, the WebUI prompts the user
to enter NE information (NE Name). Enter and submit this information.
Result: The WebUI sends the data to the NE resulting in another NE reboot. The NE
and WebUI are now ready for normal operation. The WebUI will automatically
reconnect to the NE when it is available.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
20-50
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
The following procedure is used to submit a ping request.

Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Tools > Ping.

Result: The Ping screen is displayed.
...................................................................................................................................................................................................
Enter desired settings and click Apply.

E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
20-51
Issue 1 June 2013
....................................................................................................................................................................................................................................

When to use
The following procedure is used to submit a traceroute request.

Instructions
...................................................................................................................................................................................................
In the WebUI, select Administration > Tools > Traceroute.

Result: The Traceroute screen is displayed.
...................................................................................................................................................................................................
Enter desired settings and click Apply.

Result: The WebUI will display a text string in response to the traceroute request.
E...................................................................................................................................................................................................
N D O F S T E P S
....................................................................................................................................................................................................................................
1830 PSS
20-52
Issue 1 June 2013
Glossary
...................................................................................................................................................................................................................................
Numerics
16FS
16 columns with Fixed Stuff

3R
Reamplification, Reshaping and Retiming

...................................................................................................................................................................................................................................
ABN
Abnormal (condition)
ABS (Absent)
Used to indicate that a given circuit pack is not installed.

Accepted trace identifier
A received trace identifier is considered accepted if the same trace identifier value has been
received at least three times in sequence.
ACO (Alarm Cut-Off)
A button on the user panel used to clear the network element alarm indicators (LEDs on the active
FLC, rack top lamp interface, the remote alarms interface).
ACT (Active)
Used to indicate that a circuit pack or module is in-service and currently providing service
functions.
ACT
Activation (in the TCM ACT byte)

Adaptive-rate tributary operation of a port (Pipe mode)
Mode of operation of a port in which tributaries are not explicitly provisioned for the expected
signal rates. The signal rates are automatically identified.
AEL
Accessible Emission Limits

Agent
Performs operations on managed objects and issues events on behalf of these managed objects.
All SDH managed objects will support at least an agent. Control of distant agents is possible via
....................................................................................................................................................................................................................................
1830 PSS
GL-1
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
local Managers.
AGNE
Alarm Gateway Network Element

AI
Adapted Information
AID (Access Identifier)
A technical specification for explicitly naming entities (both physical and logical) of an NE using
a grammar comprised of ASCII text, keywords, and grammar rules.
AINS (Automatic In-Service)
One possible state of a port or slot. When a port is in the AINS state and a good signal is detected,
the port automatically enters the IS (in-service) state. When a port or slot is in the AINS state and
a circuit pack is detected, the slot/port automatically enters the IS state. The important things
about AINS state is that alarms are suppressed. Absence of the circuit pack is not alarmed.
Absence of a signal is not alarmed on the port.
AIS (Alarm Indication Signal)
A code transmitted downstream in a digital network that indicates that an upstream failure has
been detected and alarmed if the upstream alarm has not been suppressed.
Alarm
An alarm is a human observable alerting indication, for example visually, to a condition that may
have immediate or potential negative impact on the state of the monitoring network element.
Alarm Correlation
The search for a directly-reported alarm that can account for a given symptomatic condition.
Alarm Severity
An attribute defining the priority of the alarm message. The way alarms are processed depends on
the severity.
Alarm Suppression
Selective removal of alarm messages from being forwarded to the GUI or to network management
layer OSs.
AMCC
Applied Micro Circuits Corporation

AMI (Alternate Mark Inversion)
A line code that employs a ternary signal to convert binary digits, in which successive binary ones
are represented by signal elements that are normally of alternative positive and negative polarity
but equal in amplitude and in which binary zeros are represented by signal elements that have
zero amplitude.
....................................................................................................................................................................................................................................
1830 PSS
GL-2
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
AMP
Asynchronous Mapping Procedure

Anomaly
A difference between the actual and desired operation of a function.

ANSI
American National Standards Institute

APD
Avalanche Photo Diode

API
Access point identifier

APIPA
Automatic Private IP Addressing

APS (Automatic Protection Switch)
A protection switch that occurs automatically in response to an automatically detected fault

condition.
ASN.1
Abstract Syntax Notation 1

ASON
Automatically switched optical network

Assembly
Gathering together of payload data with overhead and pointer information (an indication of the
direction of the signal).
Association
A logical connection between manager and agent through which management information can be
exchanged.
ASTN
Automatic Switched-Transport Network

Attribute
Alarm indication level: critical, major, minor, or no alarm.

AU
Administrative Unit
Autolock
Action taken by the system in the event of circuit pack failure/trouble. System switches to
protection and prevents a return to the working circuit pack even if the trouble clears. Multiple
protection switches on a circuit pack during a short period of time cause the system to autolock
....................................................................................................................................................................................................................................
1830 PSS
GL-3
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
the pack.
Autonomous Message
A message transmitted from the controlled Network Element to a management system which was
not a response to a management system originated command.
AVAIL
Available
...................................................................................................................................................................................................................................
Bandwidth
The difference in Hz between the highest and lowest frequencies in a transmission channel. The
data rate that can be carried by a given communications circuit.
Baud Rate
Transmission rate of data (bits per second) on a network link.

BDI
Backward Defect Indication

BDI-O
Backward Defect Indication Overhead

BDI-P
Backward Defect Indication Payload

BEI
Backward Error Indication

BER (Bit Error Rate )
The ratio of error bits received to the total number of bits transmitted.
BI
Backward Indication
BIAE
Backward Incoming Alignment Error

Bidirectional Line
A transmission path consisting of two fibers that handle traffic in both the transmit and receive
directions.
Bidirectional Switch
Protection switching performed in both the transmit and receive directions.

BIP-N (Bit Interleaved Parity-N)
A method of error monitoring over a specified number of bits (BIP-3 or BIP-8).
....................................................................................................................................................................................................................................
1830 PSS
GL-4
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Bit Error Rate Threshold
The point at which an alarm is issued for bit errors.

BITS
Building Integrated Timing Supply

BMP
Bit-synchronous Mapping Procedure

Bridge a cross-connection
The setting up of a cross-connection leg with the same input tributary as that of an existing
cross-connection leg. Thus, forming a 1:2 bridge from an input tributary to two output tributaries.
Broadband Communications
Voice, data, and/or video communications at greater than 2 Mbit/s rates.

Broadband Service Transport
STM-1 concatenation transport over the 1675 LambdaUnite MSS for ATM applications.
...................................................................................................................................................................................................................................
Container
CAUI
Chip to 100Gb/s Attachment Unit Interface

CB
Control Block
CBR
Constant Bit Rate

CC (Clear Channel)
A digital circuit where no framing or control bits are required, thus making the full bandwidth
available for communications.
CC (Cross-connection)
Path-level connections between input and output tributaries or specific ports within a single NE.
Cross-connections are made in a consistent way even though there are various types of ports and
various types of port protection. Cross-connections are re-configurable interconnections between
tributaries of transmission interfaces.
CFP (C form-factor pluggable)
A CFP is a pluggable optical module with either 40 or 100 Gb/s transmission rate. The CFP layout
has been standardized by a consortium of leading suppliers of telecommunications equipment.
Channel
A sub-unit of transmission capacity within a defined higher level of transmission capacity.

....................................................................................................................................................................................................................................
1830 PSS
GL-5
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
CI
Characteristic Information
Circuit
A set of transmission channels through one or more network elements that provides transmission
of signals between two points, to support a single communications path.
CISPR
Comit International Spcial des Perturbations Radiolectriques

CL
Clear
CLEI code
COMMON LANGUAGE equipment code

Client
Computer in a computer network that generally offers a user interface to a server.

CLLI
Common Language Location Identifier

Closed Ring Network
A network formed of a ring-shaped configuration of network elements. Each network element

connects to two others, one on each side.
CM (Configuration Management)
Subsystem that configures the network and processes messages from the network.
Cm
number of m-bit client data entities

CM
Connection Monitoring
CMEP
Connection Monitoring End Point

CMGPON_D
Continuous Mode GPON Downstream

CMGPON_U2
Continuous Mode GPON Upstream 2

CMI
Coded Mark Inversion

CMISSSER
Serialized CMISS information

....................................................................................................................................................................................................................................
1830 PSS
GL-6
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
CMOH
Connection Monitoring Overhead

Cn
number of n-bit client data entities

CnD
difference between Cn and (m/n x Cm)

CO (Central Office)
A building where common carriers terminate customer circuits.

Co-Resident
A hardware configuration where two applications can be active at the same time independently on
the same hardware and software platform without interfering with each others functioning.
Collocated
System elements that are located in the same location.

Command Group
An administrator-defined group that defines commands to which a user has access.

Concatenation
A procedure whereby multiple virtual containers are associated one with each other resulting in a
combined capacity that can be used as a single container across which bit sequence integrity is
maintained.
Correlation
A process where related hard failure alarms are identified.

CP
This abbreviation has the following possible expansions:

1. Circuit Pack
2. Control Plane.
CPE
Customer Premises Equipment

CPR (Control Plane Routing)
IP routing performed by an NE for RSVP notify messages, and for management traffic. OSPF is
used as routing protocol. A CPR domain contains NEs and Network Operation Centers (NOCs).
CPR domains can be decoupled from IP routing in the operator's DCN, by setting up IP-in-IP
tunnels between NEs attached to the Out-of-band DCN, and NOCs.
CPRI
Common Public Radio Interface

CR (Critical (alarm))
....................................................................................................................................................................................................................................
1830 PSS
GL-7
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Alarm that indicates a severe, service-affecting condition.

CRC
Cyclic Redundancy Check

Crosstalk
An unwanted signal introduced into one transmission line from another.

CRU
Clock Recovery Unit

CS
Client Specific
CSF
Client Signal Fail

CSMA/CD
Carrier Sense Multiple Access with Collision Detection

CTRL
Control word sent from source to sink

Current Value
The value currently assigned to a provisionable parameter.

Cyclic Redundancy Check (CRC)
Cyclic redundancy checking is a widespread error detection method based on parity bit
calculations.
...................................................................................................................................................................................................................................
DAPI
Destination access point identifier

Data
A collection of system parameters and their associated values.

Database Administrator
A user who administers the database of the application.

Databearer
A databearer represents a physical link connection between two nodes in the transport plane.
DCE (Data Communications Equipment)
The equipment that provides signal conversion and coding between the data terminating
equipment (DTE) and the line. The DCE may be separate equipment or an integral part of the
DTE or of intermediate equipment. A DCE may perform other functions usually performed at the
network end of the line.
....................................................................................................................................................................................................................................
1830 PSS
GL-8
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
DCF
Data Communications Function; Dispersion Compensation Fiber

DCM (Dispersion Compensation Module)
A device used to compensate the dispersion, the pulse spreading properties of an optical fiber.
DCMs are necessary for very-long-haul applications and high bit rates.
DCN
Data Communications Network

Default
An operation or value that the system or application assumes, unless a user makes an explicit
choice.
Default Provisioning
The parameter values that are pre-programmed as shipped from the factory.
Defect
A limited interruption of the ability of an item to perform a required function. It may or may not
lead to maintenance action depending on the results of additional analysis.
Demultiplexing
A process applied to a multiplexed signal for recovering signals combined within it and for
restoring the distinct individual channels of these signals.
DEMUX (Demultiplexer)
A device that splits a combined signal into individual signals at the receiver end of transmission.
Deprovisioning
The inverse order of provisioning. To manually remove/delete a parameter that has (or parameters
that have) previously been provisioned.
Digital Multiplexer
Equipment that combines by time-division multiplexing several digital signals into a single
composite digital signal.
Digital Section
A transmission span such as an STM-N signal. A digital section may contain multiple digital
channels.
Disassembly
Splitting up a signal into its constituents as payload data and overhead (an indication of the
direction of a signal).
Dispersion
Time-broadening of a transmitted light pulse.
....................................................................................................................................................................................................................................
1830 PSS
GL-9
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Dispersion Shifted Optical Fiber
1330/1550 nm minimum dispersion wavelength.

Divergence
When there is unequal amplification of incoming wavelengths, the result is a power divergence
between wavelengths.
DMp
Delay Measurement of ODUk path

DMti
Delay Measurement of TCMi

DNI (Dual Node Ring Interworking)
A topology in which two rings are interconnected at two nodes on each ring and operate so that
inter-ring traffic is not lost in the event of a node or link failure at an interconnecting point.
DNU
Do Not Use
Doping
The addition of impurities to a substance in order to attain desired properties.

Downstream
At or towards the destination of the considered transmission stream, for example, looking in the
same direction of transmission.
DPR
Data Plane Routing

DRAM
Dynamic Random Access Memory

Drop and Continue
A circuit configuration that provides redundant signal appearances at the outputs of two network
elements in a ring. Can be used for Dual Node Ring Interworking (DNI) and for video distribution
applications.
DS1
Digital Signal - Level 1 (1.544 Mbit/s)

DS3
Digital Signal - Level 3 (44.736 Mbit/s)

DTE (Data Terminating Equipment)
The equipment that originates data for transmission and accepts transmitted data.
DWDM (Dense Wavelength Division Multiplexing)
Transmitting two or more signals of different wavelengths simultaneously over a single fiber.
....................................................................................................................................................................................................................................
1830 PSS
GL-10
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
EBCN
Ethernet-based communication network

EBER (Excessive Bit Error Rate)
The calculated average bit error rate over a data stream.

EC
ECC
Embedded Control Channel

EDC
Error Detection Code

EEPROM
Electrically Erasable and Programmable Read-Only Memory

EIA (Electronic Industries Association)
A trade association of the electronic industry that establishes electrical and functional standards.
EMC (Electromagnetic Compatibility)
A measure of equipment tolerance to external electromagnetic fields.

EMI (Electromagnetic Interference)
High-energy, electrically induced magnetic fields that cause data corruption in cables passing
through the fields.
EMS
Element Management System

Entity
A specific piece of hardware (usually a circuit pack, slot, or module) that has been assigned a
name recognized by the system.
Entity Identifier
The name used by the system to refer to a circuit pack, memory device, or communications link.
EOS
End of Sequence
ES (Errored Seconds)
A performance monitoring parameter. ES type A is a second with exactly one error; ES type
B is a second with more than one and less than the number of errors in a severely errored second
for the given signal. ES by itself means the sum of the type A and type B ESs.
....................................................................................................................................................................................................................................
1830 PSS
GL-11
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
ESD
Electrostatic Discharge
ESNCP
Electrical sub-block network connection protection

ESP
Electrostatic Protection
Establish
A user-initiated command, at the Alcatel-Lucent 1830 PSS ZIC, to create an entity and its
associated attributes in the absence of certain hardware.
ETR
Extended temperature range

ETSI
European Telecommunications Standards Institute

Event
A significant change. Events in controlled Network Elements include signal failures, equipment
failures, signals exceeding thresholds, and protection switch activity. When an event occurs in a
controlled Network Element, the controlled Network Element will generate an alarm or status
message and send it to the management system.
Event Driven
A required characteristic of network element software system: NEs are reactive systems, primarily
viewed as systems that wait for and then handle events. Events are provided by the external
interface packages, the hardware resource packages, and also by the software itself.
EXP
Experimental
Externally Timed
An operating condition of a clock in which it is locked to an external reference and is using time
constants that are altered to quickly bring the local oscillators frequency into approximate
agreement with the synchronization reference frequency.
ExTI
Expected Trace Identifier

Extra traffic
Unprotected traffic that is carried over protection channels when their capacity is not used for the
protection of working traffic.
...................................................................................................................................................................................................................................
FAS
Frame alignment signal

....................................................................................................................................................................................................................................
1830 PSS
GL-12
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
FAS
Frame Alignment Signal

Fault
Term used when a circuit pack or signal has a hard (not temporary) fault and cannot perform its
normal function. For signals the fault may be temporary.
Fault Management
Collecting, processing, and forwarding of autonomous messages from network elements.

FC
Flag Continuation
FCC
Federal Communications Commission

FDA/CDRH
The Food and Drug Administration's Center for Devices and Radiological Health.
FDDI (Fiber Distributed Data Interface)
Fiber interface that connects computers and distributes data among them.
FDI
Forward Defect Indication

FDI-O
Forward Defect Indication Overhead

FDI-P
Forward Defect Indication Payload

FE (Far End )
Any other network element in a maintenance subnetwork other than the one the user is at or
working on. Also called remote.
FEBE (Far-End Block Error)
An indication returned to the transmitting node that an errored block has been detected at the
receiving node. A block is a specified grouping of bits.
FEC (Forward Error Correction)
An error correction technique in which redundant bits are added to the payload signal enabling the
receiving station to detect and correct bit errors that unavoidably occur when an optical line signal
is transmitted over longer distances over an optical fiber. FEC is used to increase the transmission
span length.
FEPROM (Flash EPROM)
A technology that combines the non-volatility of EPROM with the in-circuit re-programmability
of EEPROM.
....................................................................................................................................................................................................................................
1830 PSS
GL-13
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
FERF (Far-End Receive Failure)
An indication returned to a transmitting Network Element that the receiving Network Element has
detected an incoming section failure. Also known as RDI.
FIT (Failures in Time)
Circuit pack failure rates per 109 hours as calculated using the method described in Reliability
Prediction Procedure for Electronic Equipment, BellCore Method I, Issue 6, December 1997.
Fixed-rate tributary operation of a port
Mode of operation of a port in which tributaries are provisioned for the expected signal rates. This
provisioning information is used for cross-connection rate validation and for alarm handling (for
example Loss of Pointer).
FLC
First-Level Controller
Folded Rings
Folded (collapsed) rings are rings without fiber diversity. The terminology derives from the image
of folding a ring into a linear segment.
Forced
Term used when a circuit pack (either working or protection) has been locked into a
service-providing state by user command.
FPS
Facility Protection Switching

FR (Frame Relay)
A form of packet switching that relies on high-quality phone lines to minimize errors. It is very
good at handling high-speed, bursty data over wide area networks. The frames are variable
lengths and error checking is done at the end points.
Frame
The smallest block of digital data being transmitted.

Framework
An assembly of equipment units capable of housing shelves, such as a bay framework.

Free Running
An operating condition of a clock in which its local oscillator is not locked to an internal
synchronization reference and is using no storage techniques to sustain its accuracy.
...................................................................................................................................................................................................................................
GCC
General Communications Channel

GID
Group Identification
....................................................................................................................................................................................................................................
1830 PSS
GL-14
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Global Wait to Restore Time
Corresponds to the time to wait before switching back to the timing reference. It occurs after a
timing link failure has cleared. This time applies for all timing sources in a system hence the name
global. This can be between 0 and 60 minutes, in increments of one minute.
GMP
Generic Mapping Procedure

GMPLS (generalized multi-protocol label switching)
A protocol suite (defined by IETF) that extends the label switching paradigm introduced in MPLS
to include both packet-switched and circuit-switched networks and that provides the distributed
intelligence required to build efficient and resilient multi-layer networks.
GMRE
GMPLS Routing Engine

GNE (Gateway Network Element)
A network element that passes information between other network elements and management
systems through a data communication network.
GPON
Gigabit-capable passive optical networks

Grooming
In telecommunications, the process of separating and segregating channels, as by combing, such

that the broadest channel possible can be assembled and sent across the longest practical link. The
aim is to minimize de-multiplexing traffic and reshuffling it electrically.
...................................................................................................................................................................................................................................
Hard Failure
An unrecoverable non-symptomatic (primary) failure that causes signal impairment or interferes

with critical network functions.
HDB3 (High Density Bipolar 3 Code)
Line code for 2 Mbit/s transmission systems.

HDLC (High Level Data Link Control)
OSI reference model data link layer protocol.

HO
Higher Order
Holdover
An operating condition of a clock in which its local oscillator is not locked to an external
reference but is using storage techniques to maintain its accuracy with respect to the last known
frequency comparison with a synchronization reference.
....................................................................................................................................................................................................................................
1830 PSS
GL-15
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Hot Standby
A circuit pack ready for fast, automatic placement into operation to replace an active circuit pack.
It has the same signal as the service going through it, so that choice is all that is required.
HPCFAP
High Power Connection Fuse and Alarm Panel

...................................................................................................................................................................................................................................
I/O
Input/Output
IaDI
Intra-Domain Interface
IAE
Incoming Alignment Error

ID
Identifier
IEC
International Electro-Technical Commission

IEEE
Institute of Electrical and Electronics Engineers

IMF
Infant Mortality Factor

Insert
To physically insert a circuit pack into a slot, thus causing a system initiated restore of an entity
into service and/or creation of an entity and associated attributes.
Interface Capacity
The total number of STM-1 equivalents (bidirectional) tributaries in all transmission interfaces
with which a given transmission interface subrack can be equipped at one time. The interface
capacity varies with equipage.
Intermediate System (IS)
A system which routes/relays management information. An SDH Network Element may be a

combined intermediate and end system.
IP
Internet Protocol
IPCP (IP Control Protocol)
IPCP is the Network Control Protocol for IPv4.

....................................................................................................................................................................................................................................
1830 PSS
GL-16
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
IPL
Inter-processor link
IrDI
Inter-Domain Interface
IS (In-Service)
A memory administrative state for ports. IS refers to a port that is fully monitored and alarmed.
ISDN
Integrated Services Digital Network

ITU-T
International Telecommunications Union Telecommunication standardization sector. Formerly

known as CCITT: Comit Consultatif International Tlgraphique & Tlphonique; International
Telegraph and Telephone Consultative Committee.
...................................................................................................................................................................................................................................
JC
Justification Control
Jitter
Short term variations of amplitude and frequency components of a digital signal from their ideal
position in time.
JOH
Justification Overhead
...................................................................................................................................................................................................................................
LAN (Local Area Network)
A communications network that covers a limited geographic area, is privately owned and user
administered, is mostly used for internal transfer of information within a business, is normally
contained within a single building or adjacent group of buildings, and transmits data at a very
rapid speed.
LBC
Laser Bias Current

LBFC
Laser Backface Currents

LBO (Lightguide Build-Out )
An attenuating (signal-reducing) element used to keep an optical output signal strength within
desired limits.
....................................................................................................................................................................................................................................
1830 PSS
GL-17
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
LC
Lucent Connector (also called Little Connector or Local Connector an optical fiber
connector type according to IEC 61754-20 using a ferrule diameter of 1.25 mm.
LCAS
Link Capacity Adjustment Scheme

LCN
Local Communications Network

LCP
Link Control Protocol

LCS
Local Customer Support

LDC
Local Data Controller

LED
Light-Emitting Diode
LF
Local Fault
LH
Long Haul
Line
A transmission medium, together with the associated equipment, required to provide the means of
transporting information between two consecutive network elements. One network element
originates the line signal; the other terminates it.
Line Protection
The optical interfaces can be protected by line protection. Line protection switching protects
against failures of line facilities, including the interfaces at both ends of a line, the optical fibers,
and any equipment between the two ends. Line protection includes protection of equipment
failures.
Line Timing
Refers to a network element that derives its timing from an incoming STM-N signal.
Link
The mapping between in-ports and out-ports. It specifies how components are connected to one
another.
LLM
Logical Lane Marker

....................................................................................................................................................................................................................................
1830 PSS
GL-18
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
LMP
Link Management Protocol

LO
Lower Order
Location
An identifier for a specific circuit pack, interface module, interface port, or communications link.
Lockout of Protection
The Alcatel-Lucent 1830 PSS ZIC command that prevents the system from switching traffic to
the protection line from a working line. If the protection line is active when a Lockout of
Protection is entered this command causes the working line to be selected. The protection line
is then locked from any Automatic, Manual, or Forced protection switches.
Lockout State
The Lockout State is defined for each working or protection circuit pack. The two permitted states
are: None meaning no lockout is set for the circuit pack, set meaning the circuit pack has been
locked out. The values (None & Set) are taken independently for each working or protection
circuit pack.
LOF (Loss of Frame)
A failure to synchronize an incoming signal.

LOM
Loss of Multiframe
Loop Timing
A special case of line timing. It applies to network elements that have only one STM-N/OC-N
interface. For example, terminating nodes in a linear network are loop timed.
Loopback
Type of diagnostic test used to compare an original transmitted signal with the resulting received
signal. A loopback is established when the received optical or electrical external transmission
signal is sent from a port or tributary input directly back toward the output.
LOP (Loss of Pointer)
A failure to detect the signal structure in an incoming signal.

LOS (Loss of Signal)
The complete absence of an incoming signal.

Loss Budget
Loss (in dB) of optical power due to the span transmission medium (includes fiber loss and splice
losses).
LSB
Least Significant Bit

....................................................................................................................................................................................................................................
1830 PSS
GL-19
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
LTE
Line Terminating Equipment

...................................................................................................................................................................................................................................
MAF
Management Application Function

Manager
Capable of issuing network management operations and receiving events. The manager
communicates with the agent in the controlled network element.
Manual Switch State
A protection group enters the Manual Switch State upon the initiation and successful completion
of the Manual Switch command. The protection group leaves the Manual Switch state by means
of the Clear or Forced Switch commands. While in the Manual Switch state the system may
switch the active unit automatically if required for protection switching.
MCF (Message Communications Function)
Function that provides facilities for the transport and routing of Telecommunications Management
Network messages to and from the Network Manager.
MD (Mediation Device)
Allows for exchange of management information between Operations System and Network
Elements.
MEC (Manufacturer Executable Code)
Network Element system software in binary format that after being downloaded to one of the
stores can be executed by the system controller of the network element.
MEM
Memory
MFAS
MultiFrame Alignment Signal

MFI
Multiframe Indicator
MJ (Major (alarm))
Indicates a service-affecting failure, main or unit controller failure, or power supply failure.
MMF
Multi-Mode Fiber
MN (Minor (alarm))
Indicates a non-service-affecting failure of equipment or facility.
....................................................................................................................................................................................................................................
1830 PSS
GL-20
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
MO
Managed Object
MPLS
Multi Protocol Label Switching

MS
Maintenance Signal
MSB
Most Significant Bit

MSI
Multiplex Structure Identifier

MST
Member Status
MTBF
Mean Time Between Failures

MTBMA
Mean Time Between Maintenance Activities

MTIE
Maximum Time Interval Error

MTTR
Mean Time To Repair

Multiplexer
A device (circuit pack) that combines two or more transmission signals into a combined signal on
a shared medium.
Multiplexing
A procedure by which multiple lower order path layer signals are adapted into a higher order path,
or the multiple higher order path layer signals are adapted into a multiplex section.
...................................................................................................................................................................................................................................
NA
Not Applicable
naOH
non associated overhead

NE (Network Element)
A node in a telecommunication network that supports network transport services and is directly
manageable by a management system.
....................................................................................................................................................................................................................................
1830 PSS
GL-21
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
NEBS
Network Equipment-Building System

NMI
Network Management Interface

NMON (Not Monitored )
A provisioning state for equipment that is not monitored or alarmed.

NNI
Network-Network Interface
NNI
Network Node Interface

No Request State
This is the routine-operation quiet state in which no external command activities are occurring.
NOC
Network Operation Center

Node
A network element in a ring or, more generally, in any type of network. In a network element
supporting interfaces to more than one ring, node refers to an interface that is in a particular ring.
Node is also defined as all equipment that is controlled by one system controller. A node is not
always directly manageable by a management system.
Non-Revertive Switching
In non-revertive switching, an active and standby line exist on the network. When a protection
switch occurs, the standby line is selected to support traffic, thereby becoming the active line. The
original active line then becomes the standby line. This status remains in effect even when the
fault clears. That is, there is no automatic switch back to the original status.
Non-Synchronous
The essential characteristic of time-scales or signals such that their corresponding significant
instants do not necessarily occur at the same average rate.
NORM
Normal Operating Mode

NORM
Normal Operating Mode

NOS
Not Operational primitive Sequence

NPI
Null Pointer Indication

....................................................................................................................................................................................................................................
1830 PSS
GL-22
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
NRZ
Non-Return to Zero
NSA
Non-Service Affecting
...................................................................................................................................................................................................................................
OA
Optical Amplifier
OAM&P
Operations, Administration, Maintenance, and Provisioning

OC-192
Optical Carrier, Level 192 (9953.28 Mbit/s) (10 Gbit/s)

OC-48
Optical Carrier, Level 48 (2488.32 Mbit/s) (2.5 Gbit/s)

OC, OC-n
Optical Carrier
OCC
Optical Channel Carrier

OCCo
Optical Channel Carrier overhead

OCCp
Optical Channel Carrier payload

OCCr
Optical Channel Carrier with reduced functionality

OCG
Optical Carrier Group

OCGr
Optical Carrier Group with reduced functionality

OCh
Optical channel with full functionality

OChr
Optical channel with reduced functionality

OCI
Open Connection Indication

....................................................................................................................................................................................................................................
1830 PSS
GL-23
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
ODTUG
Optical channel Data Tributary Unit Group

ODTUjk
Optical channel Data Tributary Unit j into k

ODTUk.ts
Optical channel Data Tributary Unit k with ts tributary slots

ODU
Optical Channel Data Unit

ODUk (Optical Channel Data Unit k)
According to the ITU-T Recommendation G.709, the ODUk is an information structure consisting
of the information payload (OPUk, Optical Channel Payload Unit) and ODUk related overhead.
ODUk capacities are defined for k = 0, 1, 2, 2e, 3, 3e2, and 4 where k indicates the bit rate of the
client signa (1.2 Gbit/s, 2.5 Gbit/s, 10.0 Gbit/s, 10.4 Gbit/s, 40.4 Gbit/s, 41.8 Gbit/s, 104.8 Gbit/s).
ODUk-Xv
X virtually concatenated ODUks
ODUkP
Optical Channel Data Unit-k Path Monitoring level

ODUkT
Optical Channel Data Unit-k Tandem Connection Monitoring level

OFCS
Optical fiber communications

OH
Overhead
OI (Operations Interworking)
The capability to access, operate, provision, and administer remote systems through craft interface
access from any site in an SDH network or from a centralized operations system.
OMD
Optical Multiplex/Demultiplex
OMFI
OPU Multi-Frame Identifier

OMS
Optical Multiplex Section

OMS-OH
Optical Multiplex Section Overhead

....................................................................................................................................................................................................................................
1830 PSS
GL-24
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
OMU
Optical Multiplex Unit

ONNI
Optical Network Node Interface

OOB
Out of band
OOBDCN
Out-of-band DCN
OOF
Out-of-Frame
OOS (Out-of-Service)
An equipment entity is not providing its normal service function (removed from either the
working or protection state) either because of a system problem or because the pack has been
removed from service.
OOS
OTM Overhead Signal

OOS-AU (Out-of-Service - Autonomous)
An equipment entity is in an out-of-service state caused solely by an autonomous event.

OOS-AUMA (Out-of-Service - Autonomous and Management)
An equipment entity is in an out-of-service state caused by both an autonomous event and a

management event.
OOS-MA (Out-of-Service - Management)
An equipment entity is in an out-of-service state caused solely by a management event.

Open shortest path first (OSPF)
A hierarchical link-state protocol for network routing, developed by the Internet Engineering Task
Force (IETF).
Operations Interface
Any interface providing you with information on the system behavior or control. These include
the equipment LEDs, user panel, Alcatel-Lucent 1830 PSS ZIC, office alarms, and all telemetry
interfaces.
Operator
A user of the system with operator-level user privileges.

OPS
Optical Physical Section
....................................................................................................................................................................................................................................
1830 PSS
GL-25
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
OPSM
Optical Physical Section Multilane

Optical Channel
A STM-n wavelength within an optical line signal. Multiple channels, differing by 1.5 m in
wavelength, are multiplexed into one signal.

Optical Line Signal
A multiplexed optical signal containing multiple wavelengths or channels.

OPU
Optical Channel Payload Unit

OPUk (Optical Channel Payload Unit k)
According to the ITU-T Recommendation G.709, the OPUk is the information structure used to
adapt client information for the transport over an optical channel. It comprises client information
together with any overhead needed to perform rate adaptation between the client signal rate and
the OPUk payload rate and other OPUk overhead supporting the client signal transport. This
overhead is adaptation specific.
OPUk capacities are defined for k = 0, 1, 2, 2e, 3, 3e2, and 4 where k indicates the bit rate of the
OPUk-Xv
X virtually concatenated OPUks

OS (Operations System)
A central computer-based system used to provide operations, administration, and maintenance

functions.
OSC
Optical Supervisory Channel

OSNCP
Optical sub-block network connection protection

OSP
Outside plant
OSPF
Open shortest path first

OTH
Optical Transport Hierarchy

OTL
Optical channel Transport Lane
....................................................................................................................................................................................................................................
1830 PSS
GL-26
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
OTLC
Optical Transport Lane Carrier

OTLCG
Optical Transport Lane Carrier Group

OTM
Optical Transport Module

OTN
Optical Transport Network

OTS (Optical Transport Segment)
The physical link between equipment at two different NEs; may be referred to the as OTS
transmit line, or OTS receive line, or the OTS link.
OTS
Optical Transmission Section

OTS-OH
Optical Transmission Section Overhead

OTU
Optical Channel Transport Unit

OTUk (Optical Channel Transport Unit k)
According to the ITU-T Recommendation G.709, the OTUk is the information structure used for
the transport of an ODUk over one or more optical channel connections. It consists of the optical
channel data unit and OTUk related overhead (FEC and overhead for management of an optical
channel connection). It is characterized by its frame structure, bit rate, and bandwidth.
OTUk capacities are defined for k = 0, 1, 2, 2e, 3, 3e2, and 4 where k indicates the bit rate of the
OTUk-v
Optical Channel Transport Unit-k with vendor specific OTU FEC

OTUkV
Functionally standardized Optical Channel Transport Unit k (acc. to ITU-T Recommendation

G.709)
OTUkV
functionally standardized Optical Channel Transport Unit-k

Outage
A disruption of service that lasts for more than 1 second.
....................................................................................................................................................................................................................................
1830 PSS
GL-27
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
P-CMEP
Path-Connection Monitoring End Point

Parameter
A variable that is given a value for a specified application. A constant, variable, or expression that
is used to pass values between components.
Parity Check
Tests whether the number of ones (or zeros) in an array of binary bits is odd or even; used to
determine that the received signal is the same as the transmitted signal.
Pass-Through
Paths that are cross-connected directly across an intermediate node in a network.

Path
A logical connection between the point at which a standard frame format for the signal at the
given rate is assembled, and the point at which the standard frame format for the signal is
disassembled.
Path Terminating Equipment
Network elements in which the path overhead is terminated.

PCB
Printed Circuit Board

PCC
Protection Communication Channel

PCM
Pulse Code Modulation

PCS
Physical Coding Sublayer

PDU1C, PDU2C
The Power Distribution Unit is used to provide the Alcatel-Lucent 1830 PSS-36 subrack with
power. PDU1C is the ETSI market version, PDU2C is used for the ANSI market.
PFC
PSS-36 Power filter card

PI
Physical Interface
Platform
A family of equipment and software configurations designed to support a particular application.

....................................................................................................................................................................................................................................
1830 PSS
GL-28
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
PLD
Payload
Plesiochronous Network
A network that contains multiple subnetworks, each internally synchronous and all operating at
the same nominal frequency, but whose timing may be slightly different at any particular instant.
PM (Performance Monitoring)
Measures the quality of service and identifies degrading or marginally operating systems (before
an alarm would be generated).
PM
Path Monitoring
PMA
Physical Medium Attachment sublayer

PMD (Polarization Mode Dispersion)
Output pulse broadening due to random coupling of the two polarization modes in an optical fiber.
PMI
Payload Missing Indication

PMOH
Path Monitoring OverHead

PMP
Performance monitoring process

PN
Pseudo-random Number
POP
Point of Presence
Port State Provisioning
A feature that allows a user to suppress alarm reporting and performance monitoring during
provisioning by supporting multiple states (automatic, in-service, and not monitored) for
low-speed ports.
POS
Position field
POTS
Plain Old Telephone Service

PPP
Point to point protocol

....................................................................................................................................................................................................................................
1830 PSS
GL-29
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
PRBS
See pseudo-random binary sequence (p. GL-31).

Preprovisioning
The process by which the user specifies parameter values for an entity in advance of some of the
equipment being present. These parameters are maintained only in NVM. These modifications are
initiated locally or remotely by a management system (such as Alcatel-Lucent 1830 PSS ZIC for
example). Preprovisioning provides for the decoupling of manual intervention tasks (for example,
install circuit packs) from those tasks associated with configuring the node to provide services
(for example, specifying the entities to be cross-connected).
PRI
Primary
Proactive Maintenance
Refers to the process of detecting degrading conditions not severe enough to initiate protection
switching or alarming, but indicative of an impending signal fail or signal degrade defect.
Protection Access
To provision traffic to be carried by protection tributaries when the port tributaries are not being
used to carry the protected working traffic.
Protection Group Configuration
The members of a group and their roles, for example, working protection, line number, etc.
Protection Path
One of two signals entering a path selector used for path protection switching or dual ring
interworking. The other is the working path. The designations working and protection are
provisioned by the user, whereas the terms active path and standby path indicate the current
protection state.
Protection State
When the working unit is currently considered active by the system and that it is carrying traffic.
The active unit state specifically refers to the receive direction of operation since protection
switching is unidirectional.
PROTN (Protection)
Extra capacity (channels, circuit packs) in transmission equipment that is not intended to be used
for service, but rather to serve as backup against equipment failures.
PROV (Provisioned)
Indicating that a circuit pack is ready to perform its intended function. A provisioned circuit pack
can be active (ACT), in-service (IS), standby (STBY), provisioned out-of-service (POS), or
out-of-service (OOS).
....................................................................................................................................................................................................................................
1830 PSS
GL-30
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
PSDN
Public Switched Data Network

pseudo-random binary sequence (PRBS)
A sequence of bits commonly used for testing.

PSF3T8
PSS-64 Power Supply, Filter, and Clock Interface Card

PSI
Payload Structure Identifier

PT
Payload Type
PTF
Path termination function

PTM
Pluggable transmission module (commonly, SFP, XFP, or CFP)

PWR
Power
PWR ON
Power On
...................................................................................................................................................................................................................................
QOS
Quality of Service
...................................................................................................................................................................................................................................
RADIUS
Remote Authentication Dial In User Service

RAM
Random Access Memory

RDI (Remote Defect Indication)
An indication returned to a transmitting terminal that the receiving terminal has detected an
incoming section failure. [Previously called far-end-receive failure (FERF).]
Reactive Maintenance
Refers to detecting defects/failures and clearing them.

Receive-Direction
The direction towards the Network Element.

....................................................................................................................................................................................................................................
1830 PSS
GL-31
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Regeneration
The process of reconstructing a digital signal to eliminate the effects of noise and distortion.
Regenerator Section Termination (RST)
Function that generates the Regenerator Section Overhead (RSOH) in the transmit direction and
terminates the RSOH in the receive direction.
Reliability
The ability of a software system performing its required functions under stated conditions for a
stated period of time. The probability for an equipment to fulfill its function. Some of the ways in
which reliability is measured are: MTBF (Mean Time Between Failures) expressed in hours;
Availability = (MTBF)/(MTBF+MTTR)(%) [where MTTR = mean time to restore]; outage in
minutes per year; failures per hour; percentage of failures per 1,000 hours.
Remote Network Element
Any Network Element that is connected to the referenced Network Element through either an
electrical or optical link. It may be the adjacent node on a ring, or N nodes away from the
reference. It also may be at the same physical location but is usually at another (remote) site.
Restore Timer
Counts down the time (in minutes) during which the switch waits to let the worker line recover
before switching back to it. This option can be set to prevent the protection switch continually
switching if a line has a continual transient fault.
Revertive
A protection switching mode in which, after a protection switch occurs, the equipment returns to
the nominal configuration (that is, the working equipment is active, and the protection equipment
is standby) after any failure conditions that caused a protection switch to occur, clear, or after any
external switch commands are reset. (See Non-Revertive.)
Revertive Switching
In revertive switching, there is a working and protection high-speed line, circuit pack, etc. When a
protection switch occurs, the protection line, circuit pack, etc. is selected. When the fault clears,
service reverts to the working line.
RF
Remote Fault
RJ45
Registered jack, standardized according to IEC60603-7.

Route
A series of contiguous digital sections.

Router
An interface between two networks. While routers are like bridges, they work differently. Routers
provide more functionality than bridges. For example, they can find the best route between any
two networks, even if there are several different networks in between. Routers also provide
....................................................................................................................................................................................................................................
1830 PSS
GL-32
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
network management capabilities such as load balancing, partitioning of the network, and
trouble-shooting.
RS
Regenerator Section
RS
Reed-Solomon
RS-Ack
Re-sequence acknowledge
RSOH
Regenerator Section OverHead; part of SOH

RST
Regenerator Section Termination

RSVP
Reservation Protocol
RZ (Return to Zero)
A code form having two information states (termed zero and one) and having a third state or an
at-rest condition to which the signal returns during each period.
...................................................................................................................................................................................................................................
SA
Service Affecting
SAPI
Source access point identifier

SD
Signal Degrade
SDH (Synchronous Digital Hierarchy)
A hierarchical set of digital transport structures, standardized for the transport of suitable adapted
payloads over transmission networks.
SDS
Standard Directory Service based on ANSI recommendation T1.245

Section
The portion of a transmission facility, including terminating points, between a terminal network
element and a line-terminating network element, or two line-terminating network elements.
Self-Healing
A networks ability to automatically recover from the failure of one or more of its components.
....................................................................................................................................................................................................................................
1830 PSS
GL-33
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Server
Computer in a computer network that performs dedicated main tasks which generally require
sufficient performance.
Service
The operational mode of a physical entity that indicates that the entity is providing service. This
designation will change with each switch action.
SES (Severely Errored Seconds)
This performance monitoring parameter is a second in which a signal failure occurs, or more than
a preset amount of coding violations (dependent on the type of signal) occurs.
SFP (small form-factor pluggable)
An SFP is a hot-pluggable compact transceiver used for data communications and

telecommunications. It interfaces a so-called parent board to a fiber optic. The SFP layout has
been standardized by a consortium of leading suppliers of telecommunications equipment.
SH
Short Haul
Single-Ended Operations
Provides operations support from a single location to remote Network Elements in the same SDH
subnetwork. With this capability you can perform operations, administration, maintenance, and
provisioning on a centralized basis. The remote Network Elements can be those that are specified
for the current release.
Site Address
The unique address for a Network Element.

Sk
Sink
SLC
Second-level controller
Slot
A physical position in a subrack designed for holding a circuit pack and connecting it to the
backplane. This term is also used loosely to refer to the collection of ports or tributaries connected
to a physical circuit pack placed in a slot.
SM
Section Monitoring
SM or SMF (Single-Mode Fiber)
A low-loss, long-span optical fiber typically operating at either 1310 nm, 1550 nm, or both.
SMOH
Section Monitoring OverHead

....................................................................................................................................................................................................................................
1830 PSS
GL-34
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
SNBF
Single Network Bay Frame, rack type used in ANSI equipment.

SNC
Subnetwork Connection
SNC/I
Subnetwork Connection (protection) / Inherent monitoring

SNC/N
Subnetwork Connection (protection) / Non-intrusive monitoring

SNC/S
Subnetwork connection protection with sublayer monitoring

SNR (Signal-to-Noise Ratio)
The relative strength of signal compared to noise.

So
Source
Software Backup
The process of saving an image of the current network elements databases, which are contained
in its NVM, to a remote location.
Software Download
The process of transferring a software release generic from a remote file server to the network
elements memory.
Software ID
Number that provides the software version information for the system.
SONET (Synchronous Optical Network)
The North American standard for the rates and formats that defines optical signals and their
constituents.
Span
An uninterrupted bidirectional fiber section between two network elements.

Span Growth
A type of growth in which one wavelength is added to all lines before the next wavelength is
added.
SPE
Synchronous Payload Envelope

SPF (Single point of failure)
A single failure in the network that causes isolation of more than one nodek. The use of IS-IS
areas, without obeying all rules and guidelines, increases the risk of a single point of failure in the
....................................................................................................................................................................................................................................
1830 PSS
GL-35
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
network.
SPI
Serial Peripheral Inventory

SQ
Sequence Indicator
Standby Path
One of two signals entering a constituent path selector, the standby path is the path not currently
being selected.
State
The state of a circuit pack indicates whether it is defective or normal (ready for normal use).
Operational state indicates dynamic system view: defective or normal. Administrate state
indicates provisioned user view: in-service, out-of-service, maintenance. Alarms are generated
only when administrative state is in-service.
Status
The indication of a short-term change in the system.

STBY (Standby)
The circuit pack is in service but is not providing service functions. It is ready to be used to
replace a similar circuit pack either by protection or by duplex switching.
STM-N (Synchronous Transport Module, Level N)
A building block information structure that supports SDH section layer connections, where N
represents a multiple of 155.52 Mbit/s. Normally N = 1, 4, 16, 64 or 256.
Supervisor
A user of the application with supervisor user privileges.

Suppression
A process where service-affecting alarms that have been identified as an effect are not displayed
to a user.
SYNC
Synchronizer
Synchronization Messaging
Synchronization messaging is used to communicate the quality of network timing, internal timing
status, and timing states throughout a subnetwork.
Synchronous
The essential characteristic of time scales or signals such that their corresponding significant
instances occur at precisely the same average rate, generally traceable to a single Stratum 1
source.
....................................................................................................................................................................................................................................
1830 PSS
GL-36
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
System Administrator
A user of the computer system on which the systems OS software application can be installed.
...................................................................................................................................................................................................................................
TC
Tandem Connection
TC-CMEP
Tandem Connection-Connection Monitoring End Point

TCA (Threshold-Crossing Alert)
A message type sent from a Network Element that indicates that a certain performance monitoring
parameter has exceeded a specified threshold.
TCM
Tandem Connection Monitoring

TCMOH
Tandem Connection Monitoring OverHead

TCP/IP
Transmission Control Protocol / Internet Protocol

TDM (Time Division Multiplexing)
A technique for transmitting a number of separate data, voice, and/or video signals simultaneously
over one communications medium by interleaving a portion of each signal one after another.
Through (or continue) cross-connection
A cross-connection within a ring, where the input and output tributaries have the same tributary
number but are in lines opposite each other.
TID (Target Identifier)
A provisionable parameter that is used to identify a particular Network Element within a network.
It is a character string of up 20 characters where the characters are letters, digits, or hyphens (-).
TIM
Trace identifier mismatch

TL1 (Transaction Language One)
A management protocol developed by Bellcore in 1984 for man-machine and machine-machine

communications. TL1 is defined in Telcordia Requirement GR-831-CORE.
TM (Terminal multiplexer)
An Add/drop multiplexer with only one stream interface.
....................................................................................................................................................................................................................................
1830 PSS
GL-37
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
TMN
Telecommunications Management Network

TPID (Tag protocol identifier, Ethertype)
Indicates the presence of a VLAN tag in a MAC frame. Furthermore, it indicates that the
length/type field can be found at a different position in the frame (moved by 4 bytes).
Transmit Direction
The direction outwards from the Network Element.

Tributary
This term may refer to the following definitions:

1. A signal of a specific rate (2 Mbit/s, 34 Mbit/s, 140 Mbit/s, VC-12, VC-3, VC-4, STM-1 or
STM-4) that may be added to or dropped from a line signal.
2. A path-level unit of bandwidth within a port, or the constituent signal(s) being carried in this
unit of bandwidth, for example, an STM-1 tributary within an STM-N port.
TRU
Top Rack Unit

TS
Tributary Slot
TSOH
Tributary Slot Overhead

TTI
Trail trace identifier

TTP
Trail Termination Point

TTT
Timing Transparent Transcoding

TU (Tributary Unit)
An information structure which provides adaptation between the lower order path layer and the
higher path layer. Consists of a VC-n plus a tributary unit pointer (TU PTR).
Two-Way Point-to-Point Cross-Connection
A two-legged interconnection, that supports two-way transmission, between two and only two
tributaries.
TxTI
Transmitted Trace Identifier
....................................................................................................................................................................................................................................
1830 PSS
GL-38
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
UAS (Unavailable Seconds )
In performance monitoring, the count of seconds in which a signal is declared failed or in which
10 consecutively severely errored seconds (SES) occurred, until the time when 10 consecutive
non-SES occur.
UITS (Unacknowledged Information Transfer Service)
Unconfirmed mode of LAPD operation.

UNI
User-to-Network Interface
Upstream
At or towards the source of the considered transmission stream, for example, looking in the
opposite direction of transmission.
USB
Universal Serial Bus

User Privilege
Permissions a user must perform on the computer system on which the system software runs.
UTC (Universal Time Coordinated )
A time-zone independent indication of an event. The local time can be calculated from the
Universal Coordinated Time.
...................................................................................................................................................................................................................................
Value
A number, text string, or other menu selection associated with a parameter.

Variable
An item of data named by an identifier. Each variable has a type, such as int or Object, and a
scope.
VCG
Virtual Concatenation Group

VCOH
Virtual Concatenation Overhead

vcPT
virtual concatenated Payload Type

VF
Voice frequency
Virtual Circuit
A logical connection through a data communication (for example, X.25) network.

....................................................................................................................................................................................................................................
1830 PSS
GL-39
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
Voice Frequency (VF) Circuit
A 64 kilobit per second digitized signal.

Volatile Memory
Type of memory that is lost if electrical power is interrupted.

VSR
Very short reach

...................................................................................................................................................................................................................................
WAN (Wide Area Network )
A communication network that uses common-carrier provided lines and covers an extended
geographical area.
Wavelength Interchange
The ability to change the wavelength associated with an STM-N signal into another wavelength.
WDM (Wavelength Division Multiplexing)
A means of increasing the information-carrying capacity of an optical fiber by simultaneously

transmitting signals at different wavelengths.
Wideband Communications
Voice, data, and/or video communication at digital rates from 64 kbit/s to 2 Mbit/s.
Working
Label attached to a physical entity. In case of revertive switching the working line or unit is the
entity that is carrying service under normal operation. In case of non-revertive switching the label
has no particular meaning. Working/Protection assignments are provisioned and do not change
dynamically. Active/Standby status changes dynamically. When the "working" entity is failed, the
protection entity is active and the working entity is standby. Otherwise the working entity is active
and the protection entity is standby. "Protection" is the label attached to the *other* entity, not one
that is active when the "Working" entity is failed.
WRK (Working)
Secondary state of system components. In case of revertive switching the working line or unit is
the entity that is carrying service under normal operation. In case of non-revertive switching the
label has no particular meaning. Working/Protection assignments are provisioned and do not
change dynamically. Active/Standby status changes dynamically. When the "working" entity is
failed, the protection entity is active and the working entity is standby. Otherwise the working
entity is active and the protection entity is standby. "Protection" is the label attached to the
*other* entity, not one that is active when the "Working" entity is failed.
WRT (Wait to Restore Time)
Corresponds to the time to wait before switching back after a failure has cleared, in a revertive
protection scheme. This can be between 0 and 15 minutes, in increments of one minute.
....................................................................................................................................................................................................................................
1830 PSS
GL-40
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
WS
Work Station
WTR (Wait to Restore)
Applies to revertive switching operation. The protection group enters the WTR state when all
Equipment Fail (EF) conditions are cleared, but the system has not yet reverted back to its
working line. The protection group remains in the WTR state until the Wait-to-Restore timer
completes the WTR time interval.
...................................................................................................................................................................................................................................
XC
Cross-connect
XFP (extended form-factor pluggable)
An XFP is a hot-pluggable compact transceiver used for data communications and

telecommunications. It interfaces a so-called parent board to a fiber optic. The XFP layout has
been standardized by a consortium of leading suppliers of telecommunications equipment.
...................................................................................................................................................................................................................................
Zero Code Suppression
A technique used to reduce the number of consecutive zeros in a line-coded signal (B3ZS, B8ZS).
....................................................................................................................................................................................................................................
1830 PSS
GL-41
Issue 1 June 2013
Glossary
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS
GL-42
Issue 1 June 2013
Index
A access control lists (ACL), 2-10
Access identifier, 5-548

ACL
See: access control lists (ACL)
.............................................................
.............................................................
C card
D Data Communication Channel
common mounting rules, 19-11
(DCC), 3-5
Data Communication Network
(DCN), 3-5
Active system timing reference,

8-43
CCAL
See: command community
authorization levels (CCAL)
AID, 5-548
Characters allowed in a SID, 3-27
default users, 2-8
antistatic covers, 1-38
Client selection mode, 5-11
Deprovisioning, 5-9
ASAP, 7-7
climatic conditions
DHCP, 20-27
ASAP profile
stationery operation, 1-58
Default user, 2-13
dust filter
delete, 7-18
Code violations, 16-4, 16-5
manage, 7-12, 7-14
Code Violations (CV), 16-10
.............................................................
command community
authorization levels (CCAL), 2-9
E EIFE
authentication, 2-7, 2-38

Autoprovisioning, 5-6, 5-8
.............................................................
B B1 byte, 16-5
B2 bytes, 16-5
B3 byte, 16-5
Background Block Errors (BBE),
16-10, 16-12
Configure
External timing SDH, 8-15
Configure BITS
in SDH, 8-8
Control plane IP address, 3-36
Control Plane IP address, 20-27
barred-hand symbol, 1-26
Cooling, 5-15
BIP
See: Bit-interleaved parity
Cross-connection
Bit errors, 16-4

Bit-interleaved parity (BIP), 16-5
Block errors, 16-4
modify, 11-15
Current timing configurationNew
for Release R6.0, 8-36
replace, 19-3
See: Ethernet Incoming Frame

Errors
EINB
See: Ethernet Incoming
Number of Bytes
EINF
See: Ethernet Incoming
Number of Frames
electrostatic discharge (ESD),
1-26, 1-38, 1-43, 1-55, 1-65
electrostatic protection (ESP),
1-27
environmental conditions, 1-39
storage, 1-39
transportation, 1-36
....................................................................................................................................................................................................................................
1830 PSS
IN-1
Issue 1 June 2013
Index
....................................................................................................................................................................................................................................
EOFE
See: Ethernet Outgoing Frame
Errors
External timing reference

manual switch, 8-24
out-of-service, 8-30
EONB
See: Ethernet Outgoing
Number of Bytes
EONF
See: Ethernet Outgoing
Number of Frames
Equipment provisioning, 5-6
External timing references, 8-3,

8-43, 8-46
EZ setup, 20-27
.............................................................
F Fan Unit (FAN3T8), 1-51, 1-54
replace, 19-6
Errored Seconds (ES), 16-9, 16-12
FDA/CDRH laser classification,

1-18, 1-20
ESD
See: electrostatic discharge
(ESD)
FDA/CDRH regulations, 1-20
ESD bonding point, 1-27
firewall traversal, 2-11
ESP
See: electrostatic protection
(ESP)
FLC IP addresses, 20-27

Forward Error Correction
corrected (FECC), 16-12
Ethernet, 3-6
(EIFE), 16-11
Ethernet Incoming Number of
Bytes (EINB), 16-10
Ethernet Incoming Number of
Frames (EINF), 16-11
Forward Error Correction (FEC),

16-25
invisible laser radiation, 1-49,

1-53, 1-63, 1-66
I/O cards
Provision, 5-53
.............................................................
L LAPD protocol, 3-6
laser classes, 1-18

laser safety instructions, 1-18
laser warning labels, 1-43, 1-54
Line timing references, 8-3, 8-43,
8-43
Loopback IP Address, 20-27
.............................................................
M MAC Address, 3-29
Main Shelf Type, 20-27

Maintenance user, 2-13
.............................................................
G General user, 2-13
.............................................................
H Hazard level, 1-22

(EOFE), 16-11
High Power Connection, Fuse &

Alarm Panel (HPCFAP), 1-50,
1-53, 1-56, 1-63
Ethernet Outgoing Number of

Bytes (EONB), 16-11
Ethernet Outgoing Number of
Frames (EONF), 16-11
Ethernet performance parameters,
16-10
Mandatory equipment
components, 5-6
Manual provisioning, 5-8
Media access protocols, 3-6
Menu Topic
Disable User Login, 8-12
Holdover mode, 8-4
Edit SYNCN, 8-5, 8-18
hot surfaces, 1-55, 1-64
View MAC Addresses, 3-30
.............................................................
I
Maintenance-oriented performance
monitoring, 16-3
History bin, 16-25
HPCFAP
See: High Power Connection,
Fuse & Alarm Panel

(ETH-SYMERR), 16-11
ETH-SYMERR
See: Ethernet Symbol Errors
insertion and removal facilities,

1-27
IEC laser classification, 1-18, 1-21
Exchangeability, 5-9
IEC requirements, 1-20
External timing input, 8-41
In-band FEC, 16-25
multi-shelf compound, 3-59

.............................................................
N NE name, 3-27, 20-27
Near-end performance parameters,

16-9
take out-of-service, 8-32

....................................................................................................................................................................................................................................
1830 PSS
IN-2
Issue 1 June 2013
Index
....................................................................................................................................................................................................................................
Node Manager
NE Equipment Tree, 20-3,
20-43
nominal voltage, 1-51
Non-mandatory equipment
components, 5-7
Notification code, 7-16
NTP server, 2-7, 2-38
NTP Server, 20-27
.............................................................
O ODU path termination, 5-84, 5-89,
5-92
Optical modules
provisioning, 5-57
optical transponder
112SCA1 OT, 5-168
112SCX10 OT, 5-169
OSI network protocol, 3-6
OTH performance monitoring,
16-5
OTH performance parameters,
16-12
Out of Frame Seconds - Near End
Regenerator Section (OFS-RS),
16-10
Out-of-band FEC, 16-25
.............................................................
P passwords, 2-10
Path Monitoring (PM) byte, 16-5
Performance parameters
Optical Channel (OCh), 16-14
SDH, 16-13
SONET, 16-13
PM byte, 16-5
Port group, 5-9, 5-9
Port group mode, 5-9, 5-11
Power Supply, Filter, and Clock
Interface Card (PSF3T8), 1-50,
1-51, 1-53, 1-54, 1-56, 1-57,
1-63
power wiring, 1-49
PRBS
See: pseudo-random binary
sequence
Preprovisioning, 5-8
Priority level, 2-42, 2-45, 2-49,
2-52, 2-53, 2-54, 2-55, 2-56,
2-59, 2-60, 2-65, 2-67, 2-70,
2-75, 2-76, 2-77, 2-79, 2-81,
2-83, 2-86, 2-88, 2-90, 3-41,
3-42, 3-43, 3-44
Privileged user, 2-13
Protection leg, 9-16
Provisioning, 5-8
pseudo-random binary sequence,
GL-31
PSF3T8
See: Power Supply, Filter, and
Clock Interface Card
(PSF3T8)
.............................................................
PC requirements
CPU, 20-37
Display Resolution, 20-37
Operating System, 20-37
RAM, 20-37
Performance monitoring points,
16-8
Q Q-LAN, 3-5
Quality-of-service-oriented
performance monitoring, 16-3
REI
See: Remote Error Indication
Remote Error Indication (REI),
16-5, 16-5
Reports only (user), 2-13
Reprovisioning, 5-9
RTRV-BITS, 8-39
RTRV-SYNCN, 8-38
.............................................................
S Sa bit Location, 8-42
Safety of laser products, 1-20,

1-20
SDH management network, 3-5
SDH performance monitoring,
16-4, 16-5
SDH performance parameters,
16-13
Section Monitoring (SM) byte,
16-5
security, 2-7
security log, 2-11
SES declaration threshold, 16-15
OTH, 16-16
SDH, 16-15
SONET, 16-15
Severely Errored Framing Seconds
(SEFS), 16-10
Severely Errored Seconds (SES),
16-9, 16-12
shelf interconnection
multi-shelf configuration, 5-46,
5-50
SM byte, 16-5
.............................................................
SNC protection switch, 9-34
R RADIUS server, 2-7
SONET performance monitoring,

16-4, 16-5
Region parameter, 20-27
....................................................................................................................................................................................................................................
1830 PSS
IN-3
Issue 1 June 2013
Index
....................................................................................................................................................................................................................................
SONET performance parameters,

16-13
SSM
See: Synchronization Status
Message
Standards compliance, 1-20
Super user, 2-13
super users, 2-9
Synchronization Status Message
(SSM), 8-41
System timing, 8-22
System timing reference, 8-43
.............................................................
T Target identifier (TID), 3-27
TCA mode, 16-18

Threshold crossing alert (TCA)
TCA mode, 16-18
TCA profile, 16-17
Thresholding, 16-18
Standing condition method,
16-19
USB flash drive, 18-14

user authentication, 2-7
user community authorization
levels (UCAL), 2-9
User Identifier, 20-27
user IDs, 2-8
User login, 2-1
user privilege categories, 2-9
User privilege codes, 2-42, 2-45,
2-49, 2-52, 2-53, 2-54, 2-55,
2-56, 2-59, 2-60, 2-65, 2-67,
2-70, 2-75, 2-76, 2-77, 2-79,
2-81, 2-83, 2-86, 2-88, 2-90,
3-41, 3-42, 3-43, 3-44
User type, 2-42, 2-45, 2-49, 2-52,
2-53, 2-54, 2-55, 2-56, 2-59,
2-60, 2-65, 2-67, 2-70, 2-75,
2-76, 2-77, 2-79, 2-81, 2-83,
2-86, 2-88, 2-90, 3-41, 3-42,
3-43, 3-44
User types, 2-13
User types; Predefined user types,
2-13, 2-13
Transient condition method,

16-19
Timing generator, 8-4
Timing input signal format, 8-41
Timing reference switch
Clear, 8-27
Timing references, 8-3, 8-43
.............................................................
U UCAL
See: user community

authorization levels (UCAL)
Unavailability period (UAP),
16-10
Unavailable Seconds (UAS),
16-10, 16-12
USB 2.0, 18-14
....................................................................................................................................................................................................................................
1830 PSS
IN-4
Issue 1 June 2013

8DG61259AAAATCZZA V1 Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 6.0 User Provisioning Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

8DG61259AAAATCZZA V1 Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 6.0 User Provisioning Guide

Transféré par

Droits d'auteur :

Formats disponibles

Title page

How to comment ............................................................................................................................................................................ lili

Potential sources of danger ................................................................................................................................................. 1-12

Electrostatic discharge .......................................................................................................................................................... 1-26

Transportation .......................................................................................................................................................................... 1-35

Operation and maintenance

Event of failure ........................................................................................................................................................................ 1-66

Security administration procedures

Security management and user administration on the WDM application

User accounts and privileges .............................................................................................................................................. 2-15

System security features

Procedure 2-1: Create a user login ................................................................................................................................... 2-42

System-wide user security parameters ............................................................................................................................ 2-50

Command access security level assigned to a TL1 command ............................................................................... 2-68

Procedure 2-16: Configure SSL authentication for ZIC to NE communication (high-level

Procedure 2-18: Generate a new SSL key for SSL authentication

Procedure 2-19: Request a new certificate for SSL authentication

Certificate for SSL authentication

Procedure 2-20: Generate a new SSL key for SSL authentication

Procedure 2-21: Configure RADIUS server attributes

Procedure 2-23: Set RADIUS server authentication parameters

Procedure 2-25: Create a user ............................................................................................................................................ 2-93

Procedure 2-26: View or modify user details ............................................................................................................... 2-97

Procedure 2-27: Delete a user ............................................................................................................................................ 2-99

Procedure 2-29: View / terminate sessions ................................................................................................................. 2-101

Procedure 2-30: View SNMP v3 users ......................................................................................................................... 2-104

Procedure 2-33: View / modify system security attributes ................................................................................... 2-108

Syslog Administration ........................................................................................................................................................ 2-110

Procedure 2-37: View security log ................................................................................................................................. 2-115

Procedure 2-38: View all logs

Procedure 2-39: Save a retrieved log to a file ............................................................................................................ 2-119

User Preferences ................................................................................................................................................................... 2-121

Create RADIUS Server ...................................................................................................................................................... 2-123

Procedure 2-44: Provision RADIUS properties

RADIUS Properties ............................................................................................................................................................. 2-128

The Create SNMP Trap Destinations screen

Procedure 2-47: View trap destinations ....................................................................................................................... 2-132

Procedure 2-48: View/modify community strings ................................................................................................... 2-135

Data communication setup procedures

DCN protocols and services .................................................................................................................................................. 3-9

Data communication on the WDM application

User interfaces ......................................................................................................................................................................... 3-13

Gateway NE (GNE) management .................................................................................................................................... 3-21

Procedure 3-1: Change the Site Identifier (SID) ......................................................................................................... 3-27

Procedure 3-3: Set the FLC IP Addresses of the NE ................................................................................................. 3-31

Procedure 3-8: Modify an existing access control rule

Procedure 3-9: Delete an internet protocol access rule

Procedure 3-10: Retrieve internet protocol access list

Internet Protocol Access Control Lists

Procedure 3-15: Add a GCC leg to an ECC protection group

Procedure 3-17: Enable or disable a network interface ............................................................................................ 3-71

Procedure 3-20: Set the alarm severity profile of an IP-in-IP tunnel

Procedure 3-29: Modify an OSPF area

Procedure 3-30: Delete an OSPF area .......................................................................................................................... 3-100

Procedure 3-33: Configure OSPF interface parameters ......................................................................................... 3-106

WDM setup procedures

Network Map ......................................................................................................................................................................... 3-114

Procedure 3-40: Create OSPF area ................................................................................................................................ 3-122

OSPF Areas ............................................................................................................................................................................ 3-128

NTP Properties ...................................................................................................................................................................... 3-145

Procedure 3-48: Set date and time manually

Date and Time Administration ........................................................................................................................................ 3-149

Converged node set up procedures

Equipment provisioning procedures