PEC 323-1855-310

Nortel

Optical Multiservice Edge 6130

Provisioning and Protection Switching
Procedures

Standard Rel 2.0 Issue 1 June 2007

What’s inside...
Security
Provisioning interfaces
Traffic protection switching
Timing facility provisioning
Provisioning DCN
Equipment provisioning
Maintenance operations
Copyright © 2006-2007 Nortel Networks, All Rights Reserved.
This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual property
rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel Networks,
the holder is granted no rights to use the information contained herein and this document shall not be published, copied, produced
or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.

The information is provided “as is” and Nortel Networks does not make or provide any warranty of any kind, expressed or implied,
including any implied warranties of merchantability, non-infringement of third party intellectual property rights, and fitness for a
particular purpose.

Nortel, the Nortel logo and the Globemark are trademarks of Nortel Networks.
Internet Explorer is a trademark of Microsoft Corporation.
Netscape is a trademark of Netscape Communications Corporation.

Printed in Canada
 iii

Contents 0

About this document vii

Security 1-1
Lockout users 1-2
Radius Server 1-2
List of procedures
1-1 Creating a new user account 1-5
1-2 Editing an existing user account 1-7
1-3 Deleting a user account 1-9
1-4 Changing password of the logged in user 1-11
1-5 Provisioning Radius server 1-13
1-6 Enabling Radius authentication 1-15
1-7 Querying and editing Radius Settings 1-16

Provisioning interfaces 2-1

Redundancy mode 2-1
Automatic laser shutdown 2-3
Topology adjacency 2-4
Ethernet switching 2-4
List of procedures
2-1 Querying or provisioning STM-1/4/OC-3/12 parameters or STM-16/OC-48
parameters 2-6
2-2 Editing STM-1/4/OC-3/12 or STM-16/OC-48 performance monitoring
thresholds 2-10
2-3 Editing ALS mode of laser 2-13
2-4 Querying or provisioning an AUG/STS-3 2-15
2-5 Querying or provisioning AU/STS parameters 2-17
2-6 Editing AU/STS level performance monitoring thresholds 2-24
2-7 Querying or provisioning TU/VT parameters 2-27
2-8 Editing TU/VT level performance monitoring thresholds 2-32
2-9 Querying or provisioning E1/DS1/E3/DS3 facilities 2-35
2-10 Querying or provisioning Ethernet ports 2-39
2-11 Querying or provisioning WAN interfaces 2-43
2-12 Provisioning topology adjacency 2-47
2-13 Querying or deleting topology adjacency 2-51
2-14 Editing topology adjacency 2-53

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
iv Contents

Traffic protection switching 3-1

Unprotected 3-1
1+1 MSP/APS 3-2
SNCP/UPSR 3-5
List of procedures
3-1 Querying an MSP/APS group 3-11
3-2 Creating an MSP/APS group 3-12
3-3 Deleting an MSP/APS group 3-17
3-4 Editing an MSP/APS group 3-19
3-5 Operating or releasing an external switch command on MSP/APS protection
group 3-21
3-6 Operating or releasing external switch command on an SNCP/UPSR
cross-connect 3-23

Timing facility provisioning 4-1

Quality mode 4-2
Synchronization protection 4-3
List of procedures
4-1 Querying or configuring synchronization status 4-8
4-2 Nominating timing reference 4-12
4-3 Querying the status of nominated timing references 4-15
4-4 Editing the nominated timing reference 4-17
4-5 Deleting external synchronization sources 4-19
4-6 Operating or releasing an external switch command on a nominated
synchronization source 4-21
4-7 Provisioning and clearing a lockout request for the nominated clock
source 4-23

Provisioning DCN 5-1

OSPF 5-2
iISIS 5-2
Static route 5-3
Proxy ARP 5-3
Data communication channel 5-3
Serial port 5-4
Overhead tunnel 5-4
List of procedures
5-1 Provisioning static routes 5-6
5-2 Viewing or deleting static routes 5-9
5-3 Viewing and adding the Proxy ARP neighbours 5-11
5-4 Deleting the Proxy ARP neighbours 5-13
5-5 Configuring OSPF area 5-14
5-6 Disabling OSPF 5-15
5-7 Querying or provisioning iISIS parameters 5-16
5-8 Provisioning a network interface 5-18
5-9 Querying or editing network interfaces 5-24
5-10 Deleting a network interface 5-29
5-11 Querying or provisioning serial port parameters 5-31

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Contents v

5-12 Querying status of overhead tunnel 5-37

5-13 Creating an overhead tunnel 5-38
5-14 Deleting an overhead tunnel 5-41

Equipment provisioning 6-1

List of procedures
6-1 Querying network element data 6-4
6-2 Editing network element data 6-6
6-3 Editing the time settings for the network element 6-8
6-4 Querying circuit packs 6-15
6-5 Deleting a circuit pack 6-16
6-6 Editing the alarm and performance monitoring mode 6-18
6-7 Provisioning E1/T1 ports 6-20
6-8 Provisioning E3/DS3 ports 6-22

Maintenance operations 7-1

Loopbacks 7-1
Diagnostics 7-4
SNMP traps 7-4
Configuration management 7-4
Upgrade operation 7-5
List of procedures
7-1 Provisioning loopback on STM/OCn ports 7-7
7-2 Provisioning loopback on PDH/DSn ports 7-9
7-3 Provisioning loopback on Ethernet ports 7-11
7-4 Backing up the network element configuration data 7-13
7-5 Restoring the network element configuration data 7-15
7-6 Restoring the factory defaults 7-19
7-7 Provisioning system settings 7-21
7-8 Provisioning SNMP trap destination IP addresses 7-22
7-9 Viewing the diagnostics information 7-24

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
vi Contents

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
vii

About this document 0

This document contains the provisioning and protection switching procedures

for the Optical Multiservice Edge 6130 (OME6130) network element. These
procedures are performed from the network element web user interface. Topics
covered are:
• security
• provisioning interfaces
• traffic protection switching
• timing facility provisioning
• provisioning DCN
• equipment provisioning
• maintenance operations

Supported Software
This document is compliant to the software release 2.0 of the Nortel Optical
Multiservice Edge 6130 (OME6130).

Supported Hardware
This document supports the OME6130 network element.

Audience
This document is intended for the following members of the operating
company:
• maintenance personnel
• network administrators
• planners
• provisioners
• transmission standards engineers

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
viii About this document

Procedure summary for Provisioning and Protection Switching

Main tasks
• Security
— Creating a new user account (Procedure 1-1).
— Editing an existing user account (Procedure 1-2).
— Deleting a user account (Procedure 1-3).
— Changing your password (Procedure 1-4).
— Enabling Radius authentication (Procedure 1-5).
— Provisioning Radius server (Procedure 1-6).
— Querying and editing Radius settings (Procedure 1-7).

• Provisioning interfaces
— Querying or provisioning STM-1/OC-3 /4 parameters (Procedure 2-1).
— Editing STM-1/4/OC-3 performance monitoring thresholds (Procedure 2-2).
— Editing ALS mode of laser (Procedure 2-3).
— Querying or provisioning an AUG//STS-3 (Procedure 2-4).
— Querying or provisioning AU/STS parameters (Procedure 2-5).
— Editing AU/STS level Performance Monitoring thresholds (Procedure 2-6).
— Querying or provisioning TU/VT parameters (Procedure 2-7).
— Editing TU/VT level Performance Monitoring Thresholds (Procedure 2-8).
— Querying or provisioning E1/E3/DS1/DS3 facilities (Procedure 2-9).
— Querying or provisioning Ethernet ports (Procedure 2-10).
— Querying or provisioning WAN interfaces (Procedure 2-11).
— Provisioning topology adjacency (Procedure 2-12).
— Querying or deleting topology adjacency (Procedure 2-13).
— Editing topology adjacency (Procedure 2-14).

• Traffic protection switching

— Querying an MSP/APS group (Procedure 3-1).
— Creating an MSP/APS group (Procedure 3-2).
— Deleting an MSP/APS group (Procedure 3-3).
— Editing an MSP/APS group (Procedure 3-4).
— Operating or releasing an external switch command on MSP/APS protection group (Procedure 3-5).
— Operating or releasing an external switch command on SNCP/UPSR cross connection
(Procedure 3-6).

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 About this document ix

• Timing facility provisioning

— Querying or configuring the synchronization status (Procedure 4-1).
— Nominating timing reference (Procedure 4-2).
— Querying the status of the nominated timing references (Procedure 4-3).
— Editing the nominated timing reference (Procedure 4-4).
— Deleting external synchronization sources (Procedure 4-5).
— Operating or releasing an external switch command on a nominated synchronization source
(Procedure 4-6).
— Provisioning and clearing a lockout request for the nominated clock source (Procedure 4-7).

• Provisioning DCN
— Provisioning static routes (Procedure 5-1).
— Viewing or deleting static routes (Procedure 5-2).
— Viewing and adding the Proxy ARP neighbours (Procedure 5-3).
— Deleting the Proxy ARP neighbors (Procedure 5-4).
— Configuring OSPF parameters (Procedure 5-5).
— Disabling OSPF (Procedure 5-6).
— Querying or provisioning iISIS parameters (Procedure 5-7).
— Provisioning a network interface (Procedure 5-8).
— Querying or editing network interfaces (Procedure 5-9).
— Deleting a network interface (Procedure 5-10).
— Querying or provisioning serial port parameters (Procedure 5-11).
— Querying status of overhead tunnel (Procedure 5-12).
— Creating an overhead tunnel (Procedure 5-13).
— Deleting an overhead tunnel (Procedure 5-14).

• Equipment provisioning
— Querying network element data (Procedure 6-1).
— Editing network element data (Procedure 6-2).
— Editing the time settings for the network element (Procedure 6-3).
— Querying circuit packs (Procedure 6-4).
— Deleting a circuit pack (Procedure 6-5).
— Editing the alarm and performance monitoring mode (Procedure 6-6).
— Provisioning E1/T1 port (Procedure 6-7).
— Provisioning E3/T3 port (Procedure 6-8).

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
x About this document

• Maintenance operations
— Provisioning loopback on SDH ports (Procedure 7-1).
— Provisioning loopback on PDH ports (Procedure 7-2).
— Provisioning loopback on Ethernet ports (Procedure 7-3).
— Backing up the network element configuration data (Procedure 7-4).
— Restoring the network element configuration data (Procedure 7-5).
— Restoring the factory defaults (Procedure 7-6).
— Provisioning system setting (Procedure 7-7).
— Provisioning SNMP trap destination IP addresses (Procedure 7-8).
— Viewing the diagnostics information (Procedure 7-9).

Introduction to high level procedures

This document contains procedures that provide information necessary for an
experienced user to perform a particular task. Requirements, main procedure
tasks, and expected results are consolidated into a single procedure. The step
numbers in parenthesis provide links to specific steps in the detailed
procedure.

Warnings, caution or danger messages are embedded in the procedure along

with the precautionary message icons.

Example of a high level procedure

Before you start
• Obtain a user account and password that allows you to access the Optical Multiservice Edge 6130
(OME6130) network element with privileges for creating and modifying user accounts.
• Be familiar with the Optical Multiservice Edge 6130 (OME6130) network element user interface as
described in the Local Craft Access User Guide, 323-1855-195.

Procedure tasks
• Log into the Optical Multiservice Edge 6130 (OME6130) network element with appropriate access
privileges (step 1).
• Create a new user account (step 2).
• Assign a password to the new user account (step 4).

Expected results
• The new user account is created.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 About this document xi

Optical Multiservice Edge 6130 NTP Library

Planning a Installing, Managing and Maintenance and Supporting

documentation
Network Commissioning and Provisioning Troubleshooting for the OME6130
Testing a Network a Network a Network Library

Network
Interworking Guide
(NTCA68CA)

Data
About the Installation, Provisioning and Trouble Clearing and Application Guide
OME6130 Commissioning and Protection Switching Module Replacement (NTRN15BA)
NTP Library Testing Procedures Procedures Procedures
(323-1855-090) (323-1855-201) (323-1855-310) (323-1855-543)

Bandwidth and
Planning Guide Data Services
(NT6Q92MB) Procedures
(323-1855-320)

TL1 Reference
(323-1855-190)

Local Craft Access

User Guide
(323-1855-195)

References
This document refers to the following NTPs:
• About the Optical Multiservice Edge 6130 NTP Library, 323-1855-090
• Planning Guide, NT6Q92MB
• Local Craft Access User Guide, 323-1855-195
• TL1 Reference, 323-1855-190
• Installation, Commissioning and Testing Procedures, 323-1855-201
• Trouble Clearing and Module Replacement Procedures, 323-1855-543
• Bandwidth and Data Services Procedures, 323-1855-320

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
xii About this document

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
1-1

Security 1-

This chapter contains procedures to create and manage users accounts for the
Optical Multiservice Edge 6130 (OME6130) network element.

The OME6130 network element provides four (administrator, operator2,

operator, user) different user access classes. Table 1-1 lists the user access
classes with their privileges.
Table 1-1
User access and supported operations

User Access Classes Privileges

USER The user

• has read-only access to all the management information including
configuration, faults, and performance.
• can change his own password.

OPERATOR The operator can:

• configure interfaces and cross-connects.
• reset the performance statistics.

OPERATOR2 The operator2 can:

• configure node name.
• configure Router ID and Ethernet IP.
• perform maintenance operations such as software or configuration
backup and restore, loopbacks, etc.
• perform other operations as operator.

ADMIN The administrator can:

• create and delete login access for the network element.
• access network element configurable parameters like mode,
location, contact as well as management parameters such as
Ethernet/router IP address/masks, OSPF parameters.
• change other user account passwords (see Note).

Note: In addition to the listed privileges, the administrator has all the privileges that are provided to
operator.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-2 Security

Note 1: Up to ten user accounts including diag user can be created on the
OME6130 network element.
Note 2: Refer to Table 1-1 on page 1-1 for guidelines on user access and
supported operations.
Note 3: Refer to Table 1-2 on page 1-2 for guidelines on setting the User
Name and Password for a user account.
Table 1-2 lists the user name and password details for user accounts on the
network element.
Table 1-2
User ID and password details

User Name • is unique.

• can be alphabetic/numeric/alphanumeric.
• supports special characters except space.
• supports up to 32 characters.
• is case sensitive.

Password • is unique.
• must be exactly eight characters long.
• can be alphabetic/numeric/alphanumeric.
• supports special characters except space.
• is case sensitive.
• cannot be identical to user name.

CAUTION
Risk of unauthorized access
Change the initial password of the default user account on the
network element. The default user accounts and passwords are
widely known.

Lockout users
The users with Admin privilege level can disable a user account by setting the
‘User lockout’ parameter. When the user is locked out during an active session,
the authentication information stored in the cache is used for the session till the
user logs out. The next time the user tries to log into the network element,
access is denied.

Radius Server
Remote Authentication Dial-In User Service (Radius) is an IETF protocol for
communication between Radius clients on remote network elements and a
Radius server. The Radius server provides centralized authentication,
authorization and accounting (AAA) services.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Security 1-3

When Radius setting is enabled on the OME6130 network element, the

network element will use the authentication details configured on a remote
server rather than the authentication details present on the network element.

The feature supports a primary and a secondary Radius server, synchronized

to each other. When the primary server is not reachable, the secondary server
is used for authentication. The secondary Radius server will be used only if the
primary is not reachable. If the primary is reachable, but the user name is not
authenticated (because of incorrect password or username missing), the
authentication process will fail independent of the secondary server.

Note 1: The ‘root’ and ‘DIAGUSER’ user accounts will use the
authentication details configured on the network element even when
Radius is enabled on the network element.
Note 2: If a user account is not authenticated, the user is allowed a
maximum of three retries, after which the user account is blocked.
A caching mechanism is implemented in the OME6130 network element so
that every command or web-page access does not go to the Radius server(s) for
authentication. Hence an already logged in session does not terminate if
connectivity to the Radius server is lost or if username or password
information is changed on the Radius server. However, when the Radius server
is reachable, the cached authetication information is valid only for an hour,
after which authentication failed message is displayed and the user is prompted
to login again with the new username and password. If the Radius server is not
reachable, the active session continues.

Note 1: The cache expiry is not applicable for TL1 sessions. TL1 sessions
will continue to be valid unless explicitly logged out or timed out of the
session.
Note 2: If the password has been changed in the Radius server, and if a
user uses the new password to log into the OME6130 network element, all
logged in users will have to re-login with the new password.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-4 Security

Chapter procedure list

Table 1-3 lists the procedures that are described in this chapter. To manage the
user access classes for the OME6130 network element perform these
procedures.
Table 1-3
Chapter procedure list

Action Details

Creating a new user account Procedure 1-1

Editing an existing user account Procedure 1-2

Deleting a user account Procedure 1-3

Changing password of the logged in user Procedure 1-4

Provisioning Radius server Procedure 1-5

Provisioning Radius server Procedure 1-6

Querying and editing Radius Settings Procedure 1-7

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Security 1-5

Procedure 1-1
Creating a new user account

Use this procedure to create a new user account in the OME6130 network
element. This procedure allows you to:
• add the user account
• define the user account's access class to the OME6130 network element
• lockout or grant access to a user account
• assign a password to the user account
Table 1-4 lists the parameters on the New User/Modify user page.
Table 1-4
Parameters on the New User/Modify user page

Field Description

User Name Displays the label identifying user.

Access Allows you to select a privilege from the following:

• User
• Operator
• Operator2
• Admin

User lockout Allows you to select one of the following:

• Allows access
• Deny access

Password Allows you to enter the password required for

accessing the network element.

Confirm Password Allows you to re-enter the password for confirmation.

Note 1: You must assign a password to the new user account before the user can
log into the OME6130 network element. Password must contain exactly 8
characters.
Note 2: Refer to Table 1-1 on page 1-1 and Table 1-2 on page 1-2 for guidelines on
setting the User Name and Password for a user account.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-6 Security

Procedure 1-1 (continued)

Creating a new user account

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in the Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Log into the OME6130 network element with appropriate access privileges (step 1).
• Create a new user account (step 4).
• Assign a password to the new user account (step 5).

Expected results
• A new user account is created.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Log into the OME6130 network element. Refer to Local Craft Access User
Guide, 323-1855-195 for details.
The Optical Multiservice Edge 6130 network element default view is
displayed.
2 Click Security in the Navigation menu.
3 Click Manage users.
The Manage users page is displayed. A list of all the existing user account
details is displayed.
4 Click Add User.
The New User page is displayed.
5 Select from the pull down menu or enter the appropriate values against the
fields. For details regarding the parameters, refer to Table 1-4 on page 1-5.
Note: The user name and password are case sensitive.
6 Click Submit.
A Success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Security 1-7

Procedure 1-2
Editing an existing user account

Use this procedure to modify an existing user account. This includes

modifying the user access class and the user account password of the Optical
Multiservice Edge 6130 network element. This allows you to:
• change the user account's access class of the OME6130 network element.
• assign a new password to the user account.
• lockout or grant access to the user account.
Note 1: You must assign a password to the modified user account before
the user can log into the OME6130 network element. Only the Admin user
can edit an existing user account.
Note 2: If you want to change the password of your own active user
account, then refer to Procedure 1-4, Changing password of the logged in
user.
.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Log into the OME6130 network element with admin access privileges (step 1).
• Change an existing user account information (step 4).
• Assign a password to the modified user account (step 5).

Expected results
• User account parameters are successfully edited.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-8 Security

Procedure 1-2 (continued)

Editing an existing user account

Action
Step Action

1 Log into the OME6130 network element. Refer to Local Craft Access User
Guide, 323-1855-195 for details.
The Optical Multiservice Edge 6130 network element default view is
displayed.
2 Click Security in the Navigation menu.
3 Click Manage users.
The Manage users page is displayed. A list of all the existing user account
details is displayed.
4 Click the desired user name link.
The Modify User page is displayed. For details regarding the parameters,
refer to Table 1-4 on page 1-5.
5 Determine your next step.
If you want to Then
edit the access level and password select the desired access level
from the Access pull-down menu
and enter the password.
edit the password enter the password against the
Password and confirm Password
fields.
set User Lockout select Allow access or Deny
access from the User Lockout
pull-down menu.

6 Click Submit.
A Success message is displayed.
Note: If you change the password of a user which has an active session, the
login screen will appear and the user will be prompted to enter the new
password. In this case, the user has to enter the new password to log back
into the network element.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Security 1-9

Procedure 1-3
Deleting a user account

Use this procedure to delete an existing user account.

Note 1: Only an administrator has the privilege of deleting existing user

accounts.
Note 2: The default factory login ADMIN cannot be deleted by any of the
user access classes.
Note 3: Only an administrator can delete his own account.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Log into the OME6130 network element with appropriate access privileges (step 1).
• Delete the desired user account (step 4).

Expected results
• User account is deleted.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-10 Security

Procedure 1-3 (continued)

Deleting a user account

Action
Step Action

1 Log into the Optical Multiservice Edge 6130 network element. Refer to Local
Craft Access User Guide, 323-1855-195 for details.
The Optical Multiservice Edge 6130 network element default view is
displayed.
2 Click Security in the Navigation menu.
3 Click Manage users.
The Manage users page is displayed. A list of all the existing user account
details is displayed.
4 Select the user account to be deleted. To select a specific user account for
deletion, check the corresponding delete checkbox.
5 Click Submit.
A Success message is displayed.
Note: When a user account is deleted, other active sessions using this
account will be automatically closed or logged off and the user will be
prompted to log back in with another valid user account.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Security 1-11

Procedure 1-4
Changing password of the logged in user

Use this procedure to change the password of the currently logged in user
account.

Note: An administrator can change the password for any user account. For
details regarding changing user account passwords, see Procedure 1-2,
Editing an existing user account.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Log into the OME6130 network element with appropriate access privileges (step 1).
• Change your password (step 5).

Expected results
• Your password is changed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-12 Security

Procedure 1-4 (continued)

Changing password of the logged in user

Action
Step Action

1 Log into the OME6130 network element. Refer to Local Craft Access User
Guide, 323-1855-195 for details regarding procedures to log into the
OME6130 network element.
The OME6130 network element default view is displayed.
2 Click Security in the Navigation menu.
3 Click Manage users.
The Manage users page is displayed. A list of all the existing user account
details is displayed.
4 Determine your next step.
If you are logged in Then
with
an admin level user click on current logged in user name link (the Modify
name User page is displayed). Go to step 5.
a non-admin level Enter the new password, confirm the password. Go to
user name step 6.

5 Enter the new password that is exactly eight characters long against the
Password and the Confirm Password fields.
6 Click Submit.
A success message is displayed.
Note: If active sessions are currently open with the same user account, the
login screen will appear and the user will be prompted to enter the new
password. In this case, the user has to enter the new password to log back
into the network element.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Security 1-13

Procedure 1-5
Provisioning Radius server

Use this procedure to provision Remote Authentication Dial-In User Service

(Radius) server on the OME6130 network element. You can configure the
following Radius server parameters:
• Radius server IP
• Radius secret
• Radius server Time out
• Radius server Port
• priority
Note: A maximum of four Radius servers can be provisioned on a 6130
network element.

Table 1-5 lists the configurable Radius server parameters with default and
acceptable values.
Table 1-5
configurable Radius server parameters

Field Default Value Acceptable Value

Radius Server 192.168.0.0 Any valid IP address

Radius Secret - Any alphanumeric code for

encrypting the data sent to
the Radius server. (see
Note)

Radius Server Timeout 5 1 - 30 sec.

Radius Server Port 1812 -

Priority 1 1-10

Note: Radius Secret is configurable only by the “DIAGUSER” and “ADMIN” users.
The Radius secret can have a maximum length of 128 characters.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-14 Security

Procedure 1-5 (continued)

Provisioning Radius server

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in the Local Craft Access User
Guide, 323-1853-195.

Procedure tasks
• Reach the Provision New RadiusServer page (step 3).
• Enter values in the fields (step 4).

Expected results
• A new Radius server is created.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Security in the Navigation menu.

2 Click Radius settings.
The View Radius page is displayed. All Provisioned Radius server are listed
on this page.
3 Click Provision a new RadiusServer.
The Provision New RadiusServer page is displayed.
4 Enter values referring to Table 1-5.
5 Click Create.
Success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Security 1-15

Procedure 1-6
Enabling Radius authentication

Use this procedure to enable Remote Authentication Dial-In User Service

(Radius) authentication on the OME6130 network element. This procedure
allows you to:
• Enable Radius settings

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in the Local Craft Access User
Guide, 323-1853-195.

Procedure tasks
• Reach the View Radius page (step 1).
• Enable Radius Authentication (step 3).

Expected results
• Radius authentication is enabled on the network element.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Security in the Navigation menu.

2 Click Radius settings.
The View Radius page is displayed.
3 Select Enable for Radius Authentication field, present above the View
Radius page.
4 Click Submit.
A Success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
1-16 Security

Procedure 1-7
Querying and editing Radius Settings

Use this procedure to view or edit the Remote Authentication Dial-In User
Service (Radius) authentication settings on the OME6130 network element.
.

Before you start

• Log into the network element user interface with the appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1853-195.

Procedure tasks
• Reach the View Radius page (step 1).

Expected results
• The details of the Radius authentication settings provisioned on the network element are displayed.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Security in the Navigation menu.

2 Click Radius settings.
The View Radius page is displayed.
If you want to edit the Radius settings, continue with step 3. Otherwise, you
have completed the procedure.
3 Click the edit link for the Radius server, that you want to edit.
The Edit Radius server page is displayed.
4 Enter values in the relevant fields referring to Table 1-5.
5 Click Submit.
A confirmation page is displayed.
6 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
2-1

Provisioning interfaces 2-

This chapter contains procedures for the provisioning and operation of traffic
interfaces on the OME6130 network element.

Redundancy mode
The OME6130 network element operates as non-redundant or redundant
system (aggregate cards). The term “redundant” applies to equipment
redundancy for the aggregate card only. Non-redundant mode is only
applicable for STM-1/4/OC-3/12 systems. In STM-16/OC-48 systems there is
only redundant mode, hence this mode would be selected automatically.

In redundant mode, two aggregate cards are inserted in slots 6 and 7 and offer
equipment protection for the line circuit packs. The aggregate cards supported
in a redundant mode are:

• 1x155/622MAgg when the node is configured for STM-1/OC-3 or

STM-4/OC-12 modes.
• 1x2G5Agg when the node is configured for STM-16/OC-48 mode.
Note: Operating the system with mix of 155/622MAgg and 1x2G5Agg
card is not a valid combination.

In non-redundant mode, the two line ports are supported on the same circuit
pack. The aggregate line card is inserted in slot 6 only and slot 7 is equipped
with a filler circuit pack. The aggregate card supported in non-redundant mode
is:

• 2x155/622M when the node is configured for STM-1/OC-3 or

STM-4/OC-12 modes.
The OME6130 supports the following traffic interfaces:
• STM-1/4/OC-3/12 (redundant and non-redundant aggregate)
• STM-16/OC-48 (redundant aggregate only)
• E1/E3/DS1/DS3 interfaces
• Ethernet interfaces
• WAN interfaces

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-2 Provisioning interfaces

Provisioning each of these interfaces involves the configuration of the

parameters associated with the interfaces. For the STM-1/4/OC-3/12 or
STM-16/OC-48 interface in addition to provisioning the port, you can also
provision the mapping structure for the administrative unit group
(AUG/STS-3). The mapping_disable option is used when there is sharing of
bandwidth by more than one channel for the 2x155M/622M or 1x2G5
cross-connect controller card. This feature is used when the user wants to
unallocate the bandwidth provisioned for the channel.

For the E1/DS1 facilities, framing is supported on the 28xE1/DS1 circuit pack.
For E3/DS3 facilties, framing is supported on the 3xE3/DS3 circuit packs.

Table 2-1 lists the PDH framing types available for OME6130 network
element.
Table 2-1
PDH framing type

Ports Framing type Line Coding

E1 CRC4 HDB3

DS1 ESF B8ZS

E3 G.751 HDB3

DS3 ASYNC D3Z8

Line Build Out (LBO) is supported for the DS1 and DS3 interfaces. When
LBO is enabled, it enhances the signal so as to meet pulse mask specifications
at the end of the fiber. LBO is not independently configurable for transmit and
receive paths. Any provisioning is applied to both transmit and receive
direction. The default value is to disable the LBO. LBO is supported only in
the transmit path.

The following range of cable lengths is supported for DS1:

• 0 - 133 ft
• 133 - 266 ft
• 266 – 399 ft
• 399 – 533 ft
• 533 – 655 ft

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-3

The following range of cable lengths is supported for DS3:

• 0-225ft
• 225-450ft

Ethernet port is service facing while the corresponding WAN port is line facing
interface. WAN is a logical port.

The OME6130 network element allows you to:

• provision the performance monitoring thresholds like the TCA values,
signal degrade, and signal fail for the regenerator section (RS)/section
overhead, multiplex section (MS)/line overhead, higher order path (HP)
and lower order path (LP)
• enable or disable the automatic laser shutdown feature
• provision the DCN parameters
• provision the 2xGE/FX + 8x10/100 BT L2 622M for ethernet switching
The consequent actions for the trace identifier mismatch and payload label
mismatch are:
• ignore
• report but do not send downstream AIS
• report and send downstream AIS

Automatic laser shutdown

The optical channel is equipped with an Automatic laser shutdown (ALS)
mechanism for laser safety reasons. This shuts down the laser transmitter
whenever a remote link is broken. ALS is supported on all optical interfaces.
This shall be provisionable on a per port basis. By default ALS is disabled. The
implementation is as per ITU-T G.664. At receiver port the network element
continuously checks for LOS i.e. whether it receives signal from far end. In
case of link failure or fiber cut, it receives LOS. On receiving LOS, laser shuts
down at the transmitter port due to action of ALS. This also results in the laser
shutdown at the far end transmitter port if ALS mode is enabled at the far end
network element.

ALS checks the link periodically by switching on the laser, if in turn signal is
received at receiver port, it switches on the laser automatically. This can be
done in manual or automatic mode. In the automatic mode, it periodically
checks the link after every 90-100 seconds. In manual mode, link needs to be
checked manually. The link can be checked in manual mode either by manual
restart or manual restart test mode. In manual restart, laser which is switched
on by ALS for testing link remains on for two seconds, while in manual restart
for test mode it remains on for hundred seconds.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-4 Provisioning interfaces

Topology adjacency
Through OMEA management,the topology adjacency feature on OME6130
provide the capability to manual provision the neighbor status information or
to automatically discover it.

Ethernet switching
The Ethernet switching card is a layer 2 switching card, designed for adding
packet switching capabilities to the OME6130 node. The circuit pack enables
service providers to give point-to-point, point-to-multipoint and transparent
LAN services for applications such as internet access, video on demand,
IP-TV. The 2xGE/FX + 8x10/100BT L2 622M card differentiates services and
provides different quality of service (QoS) with 622M or STM-4/OC-12
uplink bandwidth.

For details on Layer 2 data services, refer to Data Application Guide,

NTRN15BA. For more information on provisioning L2PA circuit pack, refer to
Bandwidth and Data Services Procedures, NTP 323-1855-320.

Chapter procedure list

Table 2-2 lists the procedures that are described in this chapter. Perform the
following procedures to provision the interfaces on the OME6130 network
element.
Table 2-2
Chapter procedure list

Action Details

Querying or provisioning STM-1/4/OC-3/12 parameters or Procedure 2-1

STM-16/OC-48 parameters

Editing STM-1/4/OC-3/12 or STM-16/OC-48 performance Procedure 2-2

monitoring thresholds

Editing ALS mode of laser Procedure 2-3

Querying or provisioning an AUG/STS-3 Procedure 2-4

Querying or provisioning AU/STS parameters Procedure 2-5

Editing AU/STS level performance monitoring thresholds Procedure 2-6

Querying or provisioning TU/VT parameters Procedure 2-7

Editing TU/VT level performance monitoring thresholds Procedure 2-8

Querying or provisioning E1/DS1/E3/DS3 facilities Procedure 2-9

Querying or provisioning Ethernet ports Procedure 2-10

Querying or provisioning WAN interfaces Procedure 2-11

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-5

Table 2-2 (continued)

Chapter procedure list

Action Details

Provisioning topology adjacency Procedure 2-12

Querying or deleting topology adjacency Procedure 2-13

Editing topology adjacency Procedure 2-14

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-6 Provisioning interfaces

Procedure 2-1
Querying or provisioning STM-1/4/OC-3/12 parameters or
STM-16/OC-48 parameters

Use this procedure to view or provision the STM-1/4/OC-3/12 or

STM-16/OC-48 ports on the OME6130 network element.

This allows you to view or configure the following parameters associated with
each of the STM-1/4/ OC-3/12 or STM-16/OC-48 ports:
• Admin Status
• Admin Reporting Status
• STM /OCn Port Profile
• Line Coding (view only)
• Laser
• ECC Byte Selection (view only)
• ECC Path (view only, if applicable)
• Transmit J0
• Transmit J0 Length
• Expected J0
• Expected J0 Length
• Received J0 (view only)
• TIM Action
• Signal Fail BER Threshold (B2)
• Signal Degrade BER Threshold (B2)
• Threshold (for TCA-15min)
• Threshold (for TCA-1Day)
• Identifier

Refer to Local Craft Access User Guide, 323-1855-195 for description of the
above listed configurable parameters.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-7

Procedure 2-1 (continued)

Querying or provisioning STM-1/4/OC-3/12 parameters or STM-16/OC-48 parameters

Configurable STM-1/4/OC-3/12 parameters or STM-16/OC-48

parameters
Table 2-3 lists the configurable STM-1/4/OC-3/12 parameters or
STM-16/OC-48 parameters with their default and acceptable values.
Table 2-3
Configurable STM/OC port parameters

Parameter Default value Acceptable value

Admin Status Down • Up

• Down

Alarm Reporting Status Alarm • No-Report

• Report

STM/OCn Port Profile Internal-NNI • Internal-NNI

• External-NNI

Transmit J0 Tx_Unallocated Trace message of 1 or 16

characters

Transmit J0 Length 16 1 or 16 (see Note 2)

Expected J0 Rx_Unallocated Trace message of 1 or 16

characters

Expected J0 Length 16 1 or 16 (see Note 2)

TIM Action tim_ignore • tim_ignore

• tim_report
• tim_downstream_ais

Signal Fail BER Threshold 10e-3 • Disable

(B2) • 10e-3
• 10e-4
• 10e-5

Signal Degrade BER 10e-6 • Disable

Threshold (B2) • 10e-5
• 10e-6
• 10e-7
• 10e-8
• 10e-9

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-8 Provisioning interfaces

Table 2-3 (continued)

Configurable STM/OC port parameters

Parameter Default value Acceptable value

Threshold (for TCA-15min) Disable • Disable

• Enable
• Default

Threshold (for TCA-1Day) Disable • Disable

• Enable
• Default

Identifier - Any string identifier that the creator

may like to associate with a
STMn/OCn port.

Note 1: In case of LOS on an optical port, the last received J0 trace value is
retained.
Note 2: One byte length trace is not supported for the Transmit J0 Length and
Expected J0 Length.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-9

Procedure 2-1 (continued)

Querying or provisioning STM-1/4/OC-3/12 parameters or STM-16/OC-48 parameters

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the STMn/OCn Interface Configuration page (step 1).
• Reach the corresponding Provisioning page (step 4).
• Enter the appropriate values against the corresponding fields (step 5).

Expected results
• The STM-1/4/OC-3/12 parameters or STM-16/OC-48 parameters are displayed.
• STMn/OCn port level configuration is completed.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click STMn/OCn.
The STM/OC Port interface configuration page is displayed.
4 Click the desired STM-1/4/OC-3/12. For STM-16 /OC-48 capacity, Click the
desired STM-16/OC-48.
The corresponding Provisioning Interface STM-1/4/OC-3/12 or
STM-16/OC-48 page is displayed.
If you want to edit the STM-1/4/OC-3/12 or STM-16/OC-48 parameters,
continue with step 5. Otherwise, you have completed the procedure.
5 Select from the pull down menu or enter the appropriate values in the
corresponding fields. Refer to Table 2-3 on page 2-7 for details.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-10 Provisioning interfaces

Procedure 2-2
Editing STM-1/4/OC-3/12 or STM-16/OC-48 performance monitoring
thresholds

Use this procedure to edit the STM-1/4/OC-3/12 or STM-16/OC-48

Regenerator section (RS) or Multiplex section (MS) performance monitoring
thresholds when OME6130 network element is in SDH mode and OC-3/12/48
section or line performance monitoring thresholds when OME6130 network
element is in SONET mode for the 15-minutes or 1-day duration.

For details on retrieving performance monitoring statistics or TCA events,

refer to Trouble Clearing and Module Replacement Procedures,
323-1855-543.

Note: To reset PM thresholds of the STM-1/4/OC-3/12 port or

STM-16/OC-48 port to their default values, the Threshold field (for TCA
15-min or 1-day) for the port should be set to default. For details, refer to
Procedure 2-1, Querying or provisioning STM-1/4/OC-3/12 parameters or
STM-16/OC-48 parameters.

This allows you to edit the threshold values for the following parameters:
• Errored Seconds—Section
• Severely Errored Seconds—Section
• Background Block Errors/Code Violations—Section
• Errored Seconds—Line
• Severely Errored Seconds—Line
• Background Blocked Errors/Code Violations—Line

Configurable port level TCA parameters

Table 2-4 lists the configurable TCA parameters with their default and
acceptable values.

Note: You can configure the TCA parameters for 15 minutes and 1 day
only if the corresponding threshold fields are enabled in the Provisioning
Interface STM-1/4/OC-3/12 or STM-16/OC-48 page.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-11

Procedure 2-2 (continued)

Editing STM-1/4/OC-3/12 or STM-16/OC-48 performance monitoring thresholds

Table 2-4
Configurable STM-1/4/OC-3/12 and STM-16/OC-48 TCA parameters

Parameter Default value Acceptable value

15 min 1 day 15 min 1 day

Threshold ES-S 114 10944 0-900 0-86400

Threshold SES-S 10 960 0-900 0-86400

Threshold 27000 2592000 0-16777215 0-1610612640

BBE-S/CV-S

Threshold ES-L 114 10944 0-900 0-86400

Threshold SES-L 10 960 0-900 0-86400

Threshold 27000 2592000 0-16777215 0-1610612640

BBE-L/CV-L

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Make sure the Threshold field (for TCA 15-min or 1-day) for the STM-1/4/OC-3/12 port or STM-16/OC-48
port is Enable. For more information, refer to Procedure 2-1, Querying or provisioning STM-1/4/OC-3/12
parameters or STM-16/OC-48 parameters.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
.

Procedure tasks
• Reach the STMn/OCn Interface Configuration page (step 1).
• Reach the corresponding TCA settings page (step 4).
• Enter the threshold values against the corresponding fields (step 6).

Expected results
• The PM threshold values for STM-1/ 4/OC-3/12 or STM-16/OC-48 interfaces are changed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-12 Provisioning interfaces

Procedure 2-2 (continued)

Editing STM-1/4/OC-3/12 or STM-16/OC-48 performance monitoring thresholds

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click STM/OCn.
The STM/OCn Port interface configuration page is displayed.
4 Click the desired STM-1/4/OC-3/12 or for STM -16/OC-48 capacity, click
STM-16/OC-48 interface link.
The corresponding Provisioning interface STM-1/4/OC-3/12 or
STM-16/OC-48 page is displayed.
5 Select the Performance Monitoring (PM) period for which the TCA need to be
set.
If you want to set Then select
TCA for 15 minutes TCA settings for 15 min
duration
TCA for 1 day TCA settings for 1 day
duration

The corresponding TCA settings page is displayed.

6 Enter the appropriate values against the fields. Refer to Table 2-4 on
page 2-11 for details.
Note: If the threshold value for the STM-1/4/OC-3/12 port or STM-16/OC-48
is set to default, then the STM-1/4/OC-3/12 or STM-16/OC-48 PM threshold
values are automatically provisioned to default and do not need to be set by
the user.
7 Click Submit.
A confirmation page is displayed.
8 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-13

Procedure 2-3
Editing ALS mode of laser

Use this procedure to edit the ALS mode of the laser for optical ports and GE
ports on 2xGE card and GE ports on L2PA card.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the corresponding Edit facility page (step 4).
• Select the desired ALS mode (step 6).

Expected results
• The ALS mode is changed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-14 Provisioning interfaces

Procedure 2-3 (continued)

Editing ALS mode of laser

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
If you want to edit ALS mode for Then click
Optical port STMn/OCn
GE port Ethernet

The corresponding interface page is displayed.

3 Click the desired STM-1/4/OC-3/12 or GE port. For STM-16/OC-48 mode,
click STM-16/OC-48 port.
The corresponding Provisioning interface page is displayed.
4 Click the Laser field link.
The corresponding laser page is displayed. P155M /P622M page is
displayed.
Note: For STM-16/OC-48, P2488M page is displayed. For STM-1/OC-3,
P155M page is displayed. For STM-4/OC-12, P622M page is displayed. For
GE port, PGEFC page is displayed.
5 Click Edit.
The Edit facility page is displayed.
6 Select the ALS mode Automatic/Manual/Disable for Laser.
7 Click Submit.
A confirmation page is displayed.
8 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-15

Procedure 2-4
Querying or provisioning an AUG/STS-3

Use this procedure to view an Administrative Unit Group (AUG/STS-3) or to

provision the mapping structure of the AUG/STS-3.

Note: In the MSP/APS configuration, the AUG/STS-3 needs to be

provisioned only for the working STM-1/4/OC-3/12 or STM-16/OC-48
port of the protection group. The provisioned values are automatically
propagated to the protection port.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the STMn /OCn Interface Configuration page (step 1).
• Reach the corresponding Provision AUG/STS-3 page (step 4).
• Select the desired mapping structure (step 5).

Expected results
• The mapping structure is changed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-16 Provisioning interfaces

Procedure 2-4 (continued)

Querying or provisioning an AUG/STS-3

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click STM/OC.
The STMn/OCn Port Interface Configuration page is displayed.
4 Click the desired AUG/STS-3 link.
The corresponding Provision AUG/STS-3 page is displayed.
If you want to change the mapping structure, continue with step 5. Otherwise,
you have completed the procedure.
Note: If the STM-1/4/OC-3/12 or STM-16/OC-48 ports are in MSP/APS
configuration, then select the working port in order to edit the AUG/STS-3
mapping.
5 Select the desired value against the Mapping Structure field.
If you want to set Then select
AU4 mapping/STS-1/STS-3c AU4/STS-1/STS-3c
mapping
disable mapping Disable

Note: When there is a provisioned cross-connect, mapping structure cannot

be changed.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-17

Procedure 2-5
Querying or provisioning AU/STS parameters

Use this procedure to view or provision the AU/STS-1 parameters.

Note 1: In the MSP/APS configuration, the AU/STS-1 parameters need to

be provisioned only for the working STM-1/4/OC-3/12 or STM-16/OC-48
port of the protection group. The provisioned values are automatically
propagated to the protection port.
Note 2: The signal label field is provisionable but must not be edited as it
will be automatically assigned a value depending on the type of
cross-connect provisioned.
Note 3: AU/STS-1 can be provisioned if all the cross-connects associated
with that AU/STS-1 are unprovisioned or deleted.
Refer to Local Craft Access User Guide, 323-1855-195 for the description of
parameters on provisioning AU/STS-1 page.

This allows you to view or configure the following AU/STS-1 parameters:

• Signal Label
• Received Signal Label (view only)
• Transmit Trace
• Transmit Trace Length
• Expected Trace
• Expected Trace Length
• Received Trace (view only)
• Signal Fail BER Threshold
• Signal Degrade BER Threshold
• Alarm Reporting Status
• Connection Type
• Path Alarm Profile

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-18 Provisioning interfaces

Procedure 2-5 (continued)

Querying or provisioning AU/STS parameters

Configurable AU/STS-1 parameters

Table 2-5 lists the configurable AU parameters with their default and
acceptable values when OME6130 network element is in SDH mode.
Table 2-5
Configurable AU parameters

Parameter Default value is Acceptable value

Signal Label • Unequipped if there are no • unequipped

(see Note 1) cross-connects provisioned • equipped_non_specific
• Tug_structure if the lower order • tug_structure
path (VC-3, VC-12) is AU4
mapped • locked_tu_n

• Asynchronous_container4 if the • asynchronous_container3

higher order path (VC4) is AU4 • asynchronous_container4
mapped • atm_mapping
• Tug_structure if the lower order • dqdb_mapping
path (VC-12) is AU3 mapped
• fddi_mapping
• Asynchronous_container3 if the
higher order path (VC-3) is AU4 • hdlc_ppp
mapped • sdl_sss
• hdlc_laps
• sdl_srs
• eth_10g
• gfp
• test_O181
• vc_ais

Received Signal Label Read only

Transmit Trace Tx_Unallocated Trace message of 16 or 64 characters

Transmit Trace Length 16 16 or 64

(see Note 2)

Expected Trace Rx_Unallocated Trace message of 16 or 64 characters

Expected Trace Length 16 16 or 64

(see Note 2)

Received Trace Read only

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-19

Table 2-5 (continued)

Configurable AU parameters

Parameter Default value is Acceptable value

Signal Fail BER 1e-3 • Disable

Threshold • 1e-3
• 1e-4
• 1e-5

Signal Degrade BER 1e-6 • Disable

Threshold • 1e-3
• 1e-4
• 1e-5
• 1e-6
• 1e-7
• 1e-8
• 1e-9

Alarm Reporting Status Report • No-Report

• Report

Connection Type Allow both lower order and higher • Allow Both Lower Order And Higher
connection Connection
• Allow Only Lower Order Connections
• In Use Higher Order Connection

Path Alarm Profile Mask TIM • mask TIM

• suppress TIM
• mask all except LOP
• mask all

Note 1: Signal Label field will be automatically assigned a value depending on the type of
cross-connect provisioned.
Note 2: Transmit Trace Length and Expected Trace Length must be the same.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-20 Provisioning interfaces

Procedure 2-5 (continued)

Querying or provisioning AU/STS parameters

Table 2-6 on page 2-20 lists the configurable STS-1 parameters with their
default and acceptable values when OME6130 network element is in SONET
mode.
Table 2-6
Configurable STS-1 parameters

Parameter Default value is Acceptable value

Signal Label • Unequipped if there are • Unequipped

(see Note 1) no cross-connects • Equipped_Non_specific
provisioned
• VT-Structured STS-1
• Tug_structure if the lower SPE
order path (STS-1, VT-2)
is STS-3 mapped • Locked VT mode

• Asynchronous_Mapping • Asynchronous Mapping

DS3 if the higher order DS3
path (STS-3c) is STS3 • ATM Mapping
mapped • DQDB Mapping
• Tug_structure if the lower • FDDI Mapping
order path (VT2) is STS
mapped • HDLC-PPP

• GFP if Ethernet traffic is • SDL-SSS

provisioned • HDLC-LAPS
• SDL-SRS
• Ethernet-10G
• GFP
• Test_O181
• VC-AIS

Received Signal Label Read only

Transmit Trace Tx_Unallocated. Trace message of 16 or 64

characters

Transmit Trace Length 16 16 or 64

(see Note 2)

Expected Trace Rx_Unallocated. Trace message of 16 or 64

characters

Expected Trace Length 16 16 or 64

(see Note 2)

Received Trace Read only

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-21

Table 2-6 (continued)

Configurable STS-1 parameters

Parameter Default value is Acceptable value

Signal Fail BER Threshold 1e-3 • Disable

• 1e-3
• 1e-4
• 1e-5

Signal Degrade BER 1e-6 • Disable

Threshold • 1e-3
• 1e-4
• 1e-5
• 1e-6
• 1e-7
• 1e-8
• 1e-9

Alarm Reporting Status Report • No-Report

• Report

Connection Type - • Allow Both Lower Order

And Higher Connection
• Allow Only Lower Order
Connections
• In Use Higher Order
Connection

Path Alarm Profile Mask TIM • mask TIM

• suppress TIM
• mask all except LOP
• mask all
(see Note 4)

Note 1: Signal Label field will be automatically assigned a value depending on the
type of cross-connect provisioned.
Note 2: Transmit Trace Length and Expected Trace Length must be the same.
Note 3: Transmit Trace and Length will not be available for editing when connection
is passthrough. This is not applicable in SDH mode.
Note 4: If the user has created Path Alarm Profile, they will be available in the drop
down menu.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-22 Provisioning interfaces

Procedure 2-5 (continued)

Querying or provisioning AU/STS parameters

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the STMn/OCn interface configuration page as shown in the user interface path (step 1).
• Reach the corresponding Provision AU/STS page (step 4).
• Enter the desired values against the corresponding fields (step 5).

Expected results
• The AU/STS-1 parameters are displayed.
• AU/STS-1 level configuration is completed.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-23

Procedure 2-5 (continued)

Querying or provisioning AU/STS parameters

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click STM/OC.
The STMn/OCn Port interface configuration page is displayed.
4 Click the desired AU/STS-1 link.
The corresponding Provision AU/STS-1 page is displayed.
If you want to edit the AU/STS-1 parameters, continue with step 5. Otherwise,
you have completed the procedure.
Note: If the STM-1/4/OC-3/12 ports or STM-16/OC-48 are in MSP/APS
configuration, then you need to select the working port in order to edit the
AU/STS-1 parameters.
5 Select from the pull down menu or enter the desired values against the
corresponding fields. For details regarding the configurable parameters, refer
to Table 2-5 on page 2-18 in SDH mode, or to Table 2-6 on page 2-20 in
SONET mode.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-24 Provisioning interfaces

Procedure 2-6
Editing AU/STS level performance monitoring thresholds

Use this procedure to edit the AU/STS-1 Performance Monitoring (PM)

thresholds for 15-minutes and 1-day intervals.

Note 1: To reset the PM thresholds of AU/STS-1 to their default values,

the Threshold field (for TCA 15-min or 1-day) need to be set to default.
Note 2: To edit the AU/STS-1 PM thresholds, set the Threshold field to
enable. For details, refer to Procedure 2-1, Querying or provisioning
STM-1/4/OC-3/12 parameters or STM-16/OC-48 parameters.
This allows you to edit the threshold values for the following parameters:
• Errored Seconds
• Severely Errored Seconds
• Background Block Errors

Configurable AU/STS-1 TCA parameters

Table 2-7 lists the editable TCA parameters with their default and acceptable
values.

Note: You can configure the TCA parameters for 15 minutes and 1 day
only if the corresponding Threshold fields are enabled in the provisioning
STM/OC port page.
Table 2-7
Configurable AU/STS-1 TCA parameters

Parameter Default value Acceptable value

15 min 1 day 15 min 1 day

Threshold ES 180 17280 0-900 0-86400

Threshold SES 15 1440 0-900 0-86400

Threshold BBE/CV 1100 105600 0-65535 0-6291360

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-25

Procedure 2-6 (continued)

Editing AU/STS level performance monitoring thresholds

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
• Make sure the Threshold field for TCA 15-min or 1-day for the STM-1/4/OC-3/12 or STM-16/OC-48 port is
set to Enable. For more information, refer to Procedure 2-1, Querying or provisioning STM-1/4/OC-3/12
parameters or STM-16/OC-48 parameters.

Procedure tasks
• Reach the corresponding TCA settings page (step 6).
• Enter the threshold values against the corresponding fields (step 6).

Expected results
• The threshold values are changed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-26 Provisioning interfaces

Procedure 2-6 (continued)

Editing AU/STS level performance monitoring thresholds

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click STM/OC.
The STM/OCn Port Interface Configuration page is displayed.
4 Click the desired AU/STS-1 link.
The corresponding provision AU/STS-1 page is displayed.
5 Select the PM period for which the TCA need to be set.
If you want to set Then click
TCA for 15 minutes TCA settings for 15 min
duration
TCA for 1 day TCA settings for 1 day
duration

The corresponding TCA settings page is displayed.

6 Enter the appropriate values against the fields. For details regarding the
configurable parameters, refer to Table 2-7 on page 2-24.
Note: If the threshold value for the STM-1/4/OC-3/12 or STM-16/OC-48 port
is set to default, then the AU/STS-1 Performance Monitoring threshold
values are automatically provisioned to default and need not be set by the
user.
7 Click Submit.
A confirmation page is displayed.
8 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-27

Procedure 2-7
Querying or provisioning TU/VT parameters

Use this procedure to view or provision the TU/VT parameters.

This allows you to view or configure the following TU/VT parameters:

• Signal Label
• Extended Signal Label
• Received Signal Label (view only)
• Transmit Trace
• Transmit Trace Length
• Expected Trace
• Expected Trace Length
• Received Trace (view only)
• Signal Fail BER Threshold
• Signal Degrade BER Threshold
• Alarm Reporting Status
• Path Alarm Profile
Refer to Local Craft Access User Guide, 323-1855-195 for the description of
the above listed parameters.

Note 1: When TU/VT is acting as a protecting member for a connection

then it is only possible to retrieve or view the TU/VT parameters.
Note 2: The Transmit Trace and Transmit Trace Length fields are editable
only for add/drop cross-connects. The Transmit Trace and Transmit Trace
Length fields are not editable for pass through cross-connects.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-28 Provisioning interfaces

Procedure 2-7 (continued)

Querying or provisioning TU/VT parameters

Configurable TU/VT parameters

Table 2-8 list the editable TU/VT parameters with their default and acceptable
values.
Table 2-8
Configurable TU/VT parameters

Field Default value is Acceptable value

Signal Label Unequipped when there are no • unequipped

(see Note 1 and Note 2) cross-connects provisioned • equipped_non_specific
• asynchronous
• bit_synchronous
• byte_synchronous
• test_O181
• vc_ais
• extended

Extended Signal Label GFP for add drop Ethernet • ATM

(see Note 1 and Note 3) cross-connects • HDLC_PPP
• HDLC_LAPS
• VCAT_TEST
• GFP

Received Signal Label Read-only

Transmit Trace (see Note 4) TX_Unallocated Trace message of 16 or 64

characters

Transmit Trace Length (see 16 16 or 64

Note 4)

Expected Trace RX_Unallocated Trace message of 16 or 64

characters

Expected Trace Length 16 16 or 64

Received Trace Read-only

Signal Fail BER Threshold 1e-3 • Disable

• 1e-3
• 1e-4
• 1e-5

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-29

Table 2-8 (continued)

Configurable TU/VT parameters

Field Default value is Acceptable value

Signal Degrade BER Threshold 1e-6 • Disable

• 1e-3
• 1e-4
• 1e-5
• 1e-6
• 1e-7
• 1e-8
• 1e-9

Alarm Reporting Status Report • No-Report

• Report

Path Alarm Profile Mask TIM • Mask TIM

• Suppress TIM
• Mask all except LOP
• Mask all

Note 1: The Signal Label, Extended Signal Label and Signal Label Mismatch action fields will be
assigned a value depending on the type of cross-connect provisioned.
Note 2: The Signal Label field is made user provisionable to avoid the Signal Label Mismatch in case
of connectivity between network elements of multi vendor networks.
Note 3: The Extended Signal Label option is ignored for TU-3/STS-1 and TU-12/VT-2 pass through
cross-connects.
Note 4: The Transmit Trace and Transmit Trace Length fields are editable only for add/drop
cross-connects. The Transmit Trace and Transmit Trace Length fields are not editable for pass through
cross-connects.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-30 Provisioning interfaces

Procedure 2-7 (continued)

Querying or provisioning TU/VT parameters

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the STMn/OCn Interface Configuration page as shown in the user interface path (step 1).
• Reach the corresponding Provision TU/VT page (step 5).
• Enter the desired values against the corresponding fields (step 6).

Expected results
• The TU/VT parameters are displayed.
• TU/VT level configuration is completed.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-31

Procedure 2-7 (continued)

Querying or provisioning TU/VT parameters

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click STM/OCn.
The STM/OCn Port Interface Configuration page is displayed.
4 Click the desired AU/STS-1 link.
The corresponding Provision AU/STS-1 page is displayed.
5 Click the desired TU/VT link.
The corresponding Provision TU/VT page is displayed.
If you want to edit the TU/VT parameters, continue with step 6. Otherwise,
you have completed the procedure.
6 Select from the pull down menu or enter the desired values against the
corresponding fields. For details regarding the configurable parameters, refer
to Table 2-8 on page 2-28.
Note 1: If the Threshold parameter is set to Disabled, then the user cannot
provision it. Refer to Procedure 2-1, to enable the TCA.
Note 2: If the STM-1/4/OC-3/12 or STM-16/OC-48 ports are provisioned in
an MSP configuration, then you need to select the TU/VT for the
corresponding working port in order to edit the TU/VT parameters. The
settings will be automatically propagated to the protection TU/VT.
7 Click Submit.
A confirmation page is displayed.
8 Click Accept Valid Modifications.
A success message is displayed.
Note: Presence of unprovisioned TU/VT on the far end network element lead
to no VCAT overhead transmission. The alarm raised due to the above
consequence is Loss of VCAT multiframe on TU/VT.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-32 Provisioning interfaces

Procedure 2-8
Editing TU/VT level performance monitoring thresholds

Use this procedure to edit the TU/VT performance monitoring thresholds for
15 minutes and 1 day intervals.

Note: Threshold (TCA 15-min or 1-day) must be enabled to modify the

TU/VT Performance Monitoring thresholds.

This allows you to edit the TU/VT Performance Monitoring thresholds for the
following parameters:
• Errored Seconds
• Severely Errored Seconds
• Background Blocked Errors

Configurable TU/VT TCA parameters

Table 2-9 lists the editable TCA parameters with their default and acceptable
values.

Note: You can configure the TCA parameters for 15 minutes and 1 day
only if the corresponding Threshold fields are enabled in the provisioning
STM//OCn port page.

Table 2-9
Configurable TU/VT TCA parameters

Parameter Default value Acceptable value

15 min 1 day 15 min 1 day

Threshold ES 120 11520 0-900 0-86400

Threshold SES 15 1440 0-900 0-86400

Threshold BBE/CV 300 28800 0-65536 0-6291360

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-33

Procedure 2-8 (continued)

Editing TU/VT level performance monitoring thresholds

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
• Make sure that the Threshold field for the STM-1/4/OC-3/12 port or STM-16/OC-48 is set to be enabled for
the 15-min or 1-day interval.

Procedure tasks
• Reach the corresponding TCA settings page (step 6).
• Enter the threshold values against the corresponding fields (step 7).

Expected results
• The threshold values are changed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-34 Provisioning interfaces

Procedure 2-8 (continued)

Editing TU/VT level performance monitoring thresholds

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click STM/OC.
The STM/OC Port Interface Configuration page is displayed.
4 Click the desired AU/STS-1 link.
The corresponding provision AU/STS-1 page is displayed.
5 Click the desired TU/VT link.
The corresponding Provision TU/VT page is displayed.
6 Select the PM period for which the TCA need to be modified.
If you want to set Then click
TCA for 15 minutes TCA settings for 15- min
duration
TCA for 1 day TCA settings for 1- day
duration

The corresponding TCA settings page is displayed.

7 Enter the appropriate values against the fields. For details regarding the
configurable parameters, refer to Table 2-9 on page 2-32.
Note 1: If the Threshold parameter is set to default, then the default
threshold values are automatically applied. The user does not have to
provision them. Refer to Procedure 2-1, for more information.
Note 2: If the STM-1/4/OC-3/12 ports or STM-16/OC-48 ports are in
MSP/APS configuration, then threshold values can only be set for the working
port. The threshold values will automatically be propagated to the protection
port.
8 Click Accept Valid Modifications.
A success message is displayed.
9 Click Submit.
A confirmation page is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-35

Procedure 2-9
Querying or provisioning E1/DS1/E3/DS3 facilities

Use this procedure to view or configure the E1/DS1/E3/DS3 facilities on the

OME6130 network element. This allows you to configure the ports as either
up or down.

This allows you to edit the E1/DS3/E3//DS3 facilities for the following
parameters:
• Admin Status
• Alarm Reporting Status
• Threshold (for TCA-15min/24-hour)
• Identifier
• Framing Application (view only)
• Framing Type
• Line Build Out Type

Configurable E1/DS1/E3/DS3 interface parameters

Table 2-10 lists the editable E1/DS1/E3/DS3 interface parameters with their
default and acceptable values.

Table 2-10
Configurable E1/DS1/E3/DS3 parameters

Parameter Default value Acceptable value

Admin Status Down Down

Up

Alarm Reporting Status Report No-Report

Report

Threshold Disable • Disable

(for TCA-15min/24-hour) • Default TCA Profile

Identifier - Any string identifier that the creator

may like to associate with a
E1/DS1/E3/DS3 port. This string can
be used to search on list of port.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-36 Provisioning interfaces

Table 2-10 (continued)

Configurable E1/DS1/E3/DS3 parameters

Parameter Default value Acceptable value

Framing Type Unframed • Unframed

• Framed

Line Build Out Type DSx_0_133ft For DS1:

(for DS1) • DSx_0_133ft
• DSx_133_266ft
• DSx_266_399ft
• DSx_399_533ft
• DSx_533_655ft
DS3_0_225ft For DS3:
(for DS3) • DS3_0_225ft
• DS3_225_450ft
(see Note)

Note: The Line Build Out Type is not applicable for E1/E3 port.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-37

Procedure 2-9 (continued)

Querying or provisioning E1/DS1/E3/DS3 facilities

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the E1/DS1/E3/DS3 configuration page (step 1).
• Select the desired E1/DS1/E3/DS3 port (step 4).

Expected results
• The E1/DS1/E3/DS3 port parameters are displayed.
• The E1/DS1/E3/DS3 ports are provisioned.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-38 Provisioning interfaces

Procedure 2-9 (continued)

Querying or provisioning E1/DS1/E3/DS3 facilities

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click E1/E3/DS1/DS3.
The E1/E3/DS1/DS3 Interface configuration page is displayed.
4 Click the desire E1/E3/DS1/DS3 port.
The corresponding Provisioning interface E1/E3/DS1/DS3 page is displayed.
If you want to edit the port status, continue with step 6. Otherwise, you have
completed the procedure.
5 Select from the pull down menu or enter the desired values against the
corresponding fields. For details regarding the configurable parameters, refer
to Table 2-10 on page 2-35.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-39

Procedure 2-10
Querying or provisioning Ethernet ports

Use this procedure to view or configure the Ethernet interfaces on the 8xETH
card and L2PA card, and the GE/FX ports on the 2xGE card and the L2PA card
of the OME6130 network element.

This allows you to view or configure the following parameters associated with
each of the Ethernet ports:
• Admin Status
• Alarm Reporting Status
• Link Status (view only)
• Link Integrity (not applicable for L2PA card)
• MTU
• Laser (applicable for GE/FX ports)
• AutoNegotiation
• Flow Control
• Speed and Duplex (view only)
• AutoNegotiation Status (view only)
• Link Partner Capabilities (view only)
• Link Partner Flow Control (view only)
• Link Integrity Status (view only, not applicable only for L2PA card)
• Medium Type (view only)
• Manual speed setting (applicable only when AutoNegotiation is disabled)
• Manual Duplex Mode setting (applicable only when AutoNegotiation is
disabled)
• Identifier
• LCAP (applicable only for L2PA card)
Refer to Local Craft Access User Guide, 323-1855-195 for the description of
parameters on the provisioning Ethernet ports page.

Note: Auto negotiation cannot interrupt GE ports when auto negotiation

is enabled at the local OME6130 and disabled at the far end network
element. The OME6130 will stop forwarding the traffic when the auto
negotiation is enabled at the local end network element and disabled at the
far end network element.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-40 Provisioning interfaces

Procedure 2-10 (continued)

Querying or provisioning Ethernet ports

Configurable Ethernet port parameters

Table 2-11 lists the configurable Ethernet port parameters with their default
and acceptable values.
Table 2-11
Configurable Ethernet port parameters

Parameter Default value Acceptable value

Admin Status Down • Up

• Down

Alarm Reporting Status Report • No-Report

• Report

Link Integrity Enable Disable or Enable

MTU 9600 64 - 9600

AutoNegotiation Enable Disable or Enable

Flow Control Manual Tx-Rx • Manual Disable

• Manual Tx-Rx
• Manual Tx-only
• Manual Rx-only
• Advertize None
• Advertize Both
• Advertize Sym
• Advertize Asym
(see Note 2)

Manual Speed Setting (see 100Mbps 10 or 100 Mbps

Note 1)

Manual Duplex Mode Setting Full Duplex • Full Duplex

(see Note 1) • Half Duplex

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-41

Table 2-11 (continued)

Configurable Ethernet port parameters

Parameter Default value Acceptable value

Identifier Ethernet 1-32 characters string.

Supports space character also.

LACP Mode Enable Disable or Enable (see Note 3)

Note 1: The speed and duplex mode of the ethernet port can be manually
provisioned only if autonegotiation is set to disable. Speed and Mode settings are
applicable only to 10/100 Mb ports.
Note 2: The Advertise None, Advertize Both, Advertize Sym, Advertize Asym
values for the Flow Control field are available only when autonegotiation is enabled.
Note 3: The LACP mode is applicable to the 2xGE/FX + 8xETH (L2PA) card only.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Provisioning Ethernet Interface page (step 3).
• Enter the desired values against the corresponding fields (step 5).

Expected results
• The Ethernet port parameters are displayed.
• Ethernet port level configuration is completed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-42 Provisioning interfaces

Procedure 2-10 (continued)

Querying or provisioning Ethernet ports

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click Ethernet.
The Provisioning ethernet configuration page is displayed.
4 Click the desired Ethernet port.
The corresponding Provisioning ethernet Interface port page is displayed.
If you want to edit the Ethernet port parameters, continue with step 5.
Otherwise, you have completed the procedure.
5 Select from the pull down menu or enter appropriate values against the fields.
For details regarding the configurable parameters, refer to Table 2-11 on
page 2-40.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
Note: Allocation of PDH channels at different locations inside a SDH/SONET
SPE is likely to result in sections that are unusable for data packets. This is
because these data packets are used up for allocation of PDH channels. This
fragmentation causes failure to provision new traffic through telecom bus
capacity though it is seemingly available.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-43

Procedure 2-11
Querying or provisioning WAN interfaces

Use this procedure to view or configure WAN interfaces on the 8xETH, 2xGE,
and L2PA card of the OME6130 network element.

This procedure allows you to configure the following parameters associated

with the WANs:
• Admin Status (editable for L2PA card)
• Alarm Reporting Status
• LCAS support
• Framing Type
• Max Diff Delay Allowed (view only)
• CRC Type (view only)
• VCAT
• Operating Granularity
• Payload FCS
• Remove channel with SD
• Circuit Identifier
• No of Channels (view only)
• LACP mode (only applicable to L2PA card)
Refer to Local Craft Access User Guide, 323-1855-195 for description of
parameters on the provisioning WAN interfaces page.

Note 1: For 2xGE and 8xETH card, the admin status of the WAN port is
edited by editing the admin status of the corresponding Ethernet Interface.
For L2PA card, the admin status of the WAN ports are provisioned
independent of the admin status of the Ethernet ports.
Note 2: In order to edit LCAS you need to delete all the VCG associations
with WAN port.
Note 3: Admin status of WAN interface is determined by the admin status
of corresponding Ethernet interface only for 2xGE and 8xETH cards. For
L2PA card, the admin status of WAN ports are provisioned independent of
the ETH ports.
Note 4: For L2PA card, while provisioning WAN, you need to configure
VLAN with Ethernet and WAN ports and assign the VLAN ID to the
participating ports. You should also configure the protocol version for the
switch. For information on Provisioning VLAN, refer to Bandwidth and
Data Service Procedures, 323-1855-320.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-44 Provisioning interfaces

Procedure 2-11 (continued)

Querying or provisioning WAN interfaces

Configurable WAN parameters

Table 2-12 lists the configurable WAN parameters.
Table 2-12
Editable WAN parameters

Parameter Default value Acceptable value

Admin Status • Up
• Down
(see Note 2)

Alarm Reporting • Report

Status • No Report
(see Note 2)

LCAS Support Enable • Enable

• Disable

Framing Type GFP-F • GFP-F

VCAT Enable • Disable

• Enable
(see Note 3)

Operating Granularity VC-12/VT1.5 • VC-12/VT1.5

• VC-11/VT1.5
• VC-3/STS-1
• VC-4/STS-3c

Payload FCS Enable • Disable

• Enable
(see Note 1)

Remove channel with Disable • Disable

SD • Enable
(see Note 4)

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-45

Table 2-12 (continued)

Editable WAN parameters

Parameter Default value Acceptable value

Circuit Identifier Nortel Networks 1-32 characters string

Supports space character also.

LACP Mode Enable Disable or Enable (see Note 5)

Note 1: It is recommended to keep the Payload FCS enabled.

Note 2: The Admin Status and Alarm Reporting Status are only editable for the
WAN ports on the L2PA card. On the 8xETH and 2xGE cards, the Admin Status and
Alarm Reporting Status are determined by the Ethernet port.
Note 3: VCAT is always enabled for the L2PA card.
Note 4: The Remove Channel with SD field is always disabled for the L2PA card.
Note 5: The LACP Mode is only supported for the L2PA circuit pack.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Provisioning WAN Interface (step 1).
• Enter the desired values against the corresponding fields (step 7).

Expected results
• The details of all the WAN associations associated with the network element is displayed. The WAN
interface is successfully provisioned.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-46 Provisioning interfaces

Procedure 2-11 (continued)

Querying or provisioning WAN interfaces

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Facilities.
3 Click WAN.
The WAN interface configuration page is displayed.
4 Click on the desired WAN interface link.
The Provisioning WAN interface page is displayed.
5 Determine your next step.
If you want to Then go to
view the VC/VT/STS groups step 6
provision the WAN interface step 7

6 Click View VC/VT Group.

The Corresponding View VC/VT Group page is displayed.
You have completed the procedure.
7 Select from the pull down menu or enter appropriate values against the fields.
For details regarding the configurable parameters, refer to Table 2-12 on
page 2-44.
8 Click Submit.
A confirmation page is displayed.
9 Click Accept Valid Modifications.
A success message is displayed.
Note: Unprovisioning VC/VTs in the WAN lead to Loss of frame delineation
alarm on the local OME6130 network element.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-47

Procedure 2-12
Provisioning topology adjacency

Use this procedure to create new topology adjacency. The OME6130 provides
the capability to manually provision network element Network topology
adjacencies.

This allows you to view or configure the following parameters:

• Port
• TYPE
• Layer
• Mechanism Enabled
• Mechanism
• Tx Version
• Tx Signature
• Rx Version
• Rx Actual
• Rx Expected
• Rx Reliability
• Rx Terminated
• Rx Accepted

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-48 Provisioning interfaces

Procedure 2-12 (continued)

Provisioning topology adjacency

Configurable topology adjacency parameters

Table 2-13 lists the configurable topology adjacency parameters with their
default and acceptable values. The desired value can be chosen from the drop
down menu.
Table 2-13
Configurable topology adjacency parameters

Parameter Default value Acceptable values

Port STM4/OC3-1-6-1 • STM1/OC3-1-N-1

• STM1/OC3-1-N-1
Where N is the slot number which
can have values 4, 5, 6, 7, 8 or 9 for
STM1/OC3.
• STM4/OC-12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1 (see Note 5)
For STM-16/OC-48 capacity
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1
(see Note 1)

TYPE Manual • Manual

• Automatic

Layer Physical • Physical

• Section
• Line

Mechanism Enabled No YES

NO

Mechanism Manual Manual

IS-IS

Tx Version - Version number

Tx Signature - The Tx Topology Adjacency

signature
(see Note 2)

Rx Version Version number

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-49

Table 2-13 (continued)

Configurable topology adjacency parameters

Parameter Default value Acceptable values

Rx Actual - The Rx Actual Adjacency signature

(see Note 2 and Note 3)

Rx Expected - The Rx Expected Adjacency

signature
(see Note 4)

Rx Reliability Unreliable • Reliable

• Unreliable

Rx Terminated Terminated • Observed

• Terminated

Rx Accepted Unaccepted • Accepted

• Unaccepted

Note 1: Acceptable values includes any of the STM/OCn port.

Note 2: For adjacency provisioning between two OME6130 network elements, the
signature must adhere to the following format:
TID-SH-SL-PORT
where
– TID: is the network element Name
– SH: is the shelf of the network element. In this release, the shelf is always 1.
– SL: is the slot of for the optical interface.
– PORT: is the port number of the optical interface.
Note 3: The format of the Rx Actual parameter must correspond to the Tx signature
format provisioned at the adjacent network element. If required, retrieve the Tx
signature of the adjacent network element in order to provision the Rx actual
parameter on OME6130.
Note 4: Rx Expected is not supported in this release.
Note 5: For a redundant system, only one port is available for provisioning. Hence
for STM4/OC12, redundant mode, ports STM4/OC12-1-6-2 is not available for
provisioning.
Note 6: OME6130 does not support autonegotiation of Maximum Transfer Unit
(MTU) size over a PPP link, but only supports magic number negotiation. So, if MTU
sizes at the OME6130 end and the OME6500 ends of a PPP link differ, the IIH PDUs
containing AD tags will be of different sizes and autodiscovery will not work properly.
For autodiscovery to work properly with OME6500, the MTU size of the PPP link on
OME6130 end should be set to the same value as that on the OME6500 end.
Additionally, for autodiscovery interop of OME6130 with OME6500 to work over PPP,
the MTU size on 6130 end should be set to less than or equal to 1500 as the
OME6500 can autonegotiate the MTU size only upto a maximum size of 1500.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-50 Provisioning interfaces

Procedure 2-12 (continued)

Provisioning topology adjacency

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Topology adjacency (step 2).
• Enter the desired values against the corresponding fields (step 4).

Expected results
• A new topology adjacency in provisioned.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Topology Adjacency.
The View Topology Adjacency page is displayed.
3 Click Provision a new Topology Adjacency.
The corresponding Provision New Topology Adjacency page is displayed.
4 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 2-13 on page 2-48 for details.
5 Click on Create.
A confirmation dialog is displayed.
6 Click on Yes.
A success message is displayed.
Note: The topology adjacency information is used by the network
management application to build the network topology. The adjacency values
must be accurately provisioned in order to allow the proper creation of the
network topology. Refer to Table 2-13 on page 2-48 for more details.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-51

Procedure 2-13
Querying or deleting topology adjacency

Use this procedure to view or delete topology adjacency on the OME6130

network element.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Topology adjacency (step 2).
• Delete the desired topology adjacency layer (step 3).

Expected results
• Desired topology adjacency is deleted.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-52 Provisioning interfaces

Procedure 2-13 (continued)

Querying or deleting topology adjacency

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Topology Adjacency.
The View Topology Adjacency page is displayed. The details regarding the
provisioned topology adjacency are displayed.
If Then
you want to delete a topology adjacency entry go to step 3.
otherwise you have completed
the procedure.

3 Select the Topology adjacency entry to be deleted by putting a check mark in

the delete field.
4 Click Delete.
The confirmation page is displayed.
5 Click Confirm Delete to delete the selected Topology or NO to cancel the
delete action.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning interfaces 2-53

Procedure 2-14
Editing topology adjacency

Use this procedure to edit topology adjacency on the network element. For
details regarding the topology adjacency parameters, see Table 2-13 on
page 2-48.

This allows you to edit the following parameters associated with the topology
adjacency:
• TYPE
• Mechanism
• Mechanism Enabled
• Tx Signature
• Tx Version
• Rx Actual
• Rx Expected
• Rx Version
• Rx Terminated
• Rx Reliability

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
2-54 Provisioning interfaces

Procedure 2-14 (continued)

Editing topology adjacency

Action
Before you start
• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Topology adjacency (step 1).
• Edit the Topology adjacency parameters (step 4).

Expected results
• The topology adjacency parameters are edited.
• If the expected results do not occur, contact your next level of support.

Step Action

1 Click Configuration in the Navigation menu.

2 Click Topology Adjacency.
The View Topology Adjacency page is displayed.
3 Click edit against the topology adjacency to be edited.
The corresponding Edit STM-n/OC-n page is displayed.
4 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 2-13 on page 2-48 for details.
5 Click Submit.
A confirmation dialog is displayed.
6 Click Accept Valid Modifications.
A success message is displayed.
Note: The topology adjacency information is used by the network
management application to build the network topology. The adjacency values
must be accurately provisioned in order to allow the proper creation of the
network topology. Refer to Table 2-13 on page 2-48 for more details.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
3-1

Traffic protection switching 3-

This chapter contains procedures to perform traffic protection switching from

the network element web user interface. The OME6130 network element
supports the following traffic protection configurations:
• unprotected
• 1+1 multiplex section protection/automatic protection switching
(MSP/APS)
• sub-network connection protection/unidirectional path switch ring
(SNCP/UPSR)

Unprotected
In an unprotected topology, a connection can be configured between any two
interfaces. This is the default configuration for the STM-1/4/OC-3/12 ports or
STM-16/OC-48 ports.

Note: The STM-1/4/OC-3/12 ports or STM-16/OC-48 ports are set to

unprotected configuration by default (i.e, on auto provisioning the network
element, the STM-1/4/OC-3/12 or STM-16/OC-48 ports are set to
unprotected).

Table 3-1 lists the details of maximum number of connections supported in the
unprotected configuration.
Table 3-1
Maximum number of connections in the unprotected configuration

Capacity Maximum number Maximum number Maximum number

of connections for of connections for of connections for
STM-1/OC-3 STM-4/OC-12 STM-16/OC-48

VC11/VT1.5 168 672 2688

VC12/VT2 126 504 2016

VC3/STS-1 6 24 96

VC4/STS-3c 2 8 32

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-2 Traffic protection switching

1+1 MSP/APS
1+1 MSP/APS is a port level protection supported on the STM-1/4/OC-3/12 or
STM-16/OC-48 interfaces. The protection conforms to G.841. The term
MSP/APS differentiates it from ring systems. The 1+1 protection scheme uses
a complete duplication of services and implies that two identical lines are
active at the same time (both working and protection lines are transmitting the
same signal) allowing for a transparent switch from the working to the
protection line. In other words, the traffic is permanently bridged on both the
working and protection lines.

Protection switching can be initiated by multiplexed section protection (MSP)

when OME6130 is in SDH mode or automatic protection switching (APS)
when OME6130 is in SONET mode or user initiated switching commands.

Protection switching can be configured either in revertive or non-revertive

mode. In revertive mode, traffic switches back to the work channel once the
fault condition has cleared when the wait to restore (WTR) period has elapsed.
In non-revertive mode, traffic remains on the protect channel and does not
automatically switch back to the work channel when the fault condition has
cleared. The wait to restore time is configurable from 1 to 12 minutes in one
minute increments when in revertive mode.

Table 3-2 lists the details regarding the maximum number of connections
supported in the 1+1 MSP/APS configuration.
Table 3-2
Maximum number of connections supported for 1+1 MSP/APS configuration

Capacity Maximum number of Maximum number of Maximum number of

connections for connections for connections for
STM-1/OC-3 STM-4/OC-12 STM-16/OC-48

VC 11/VT1.5 84 336 1344

VC12/VT2 63 252 1008

VC3/STS1 3 12 48

VC4/STS3c 1 4 16

The MSP/APS groups can be configured as uni-directional or bi-directional.

Figure 3-1 shows the switching scheme that takes effect in each of the
configurations.

Note 1: The local and remote network element must be provisioned with
the same protection configuration.
Note 2: Configure the MSP/APS group before creating the desired
cross-connects on the working port.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-3

Note 3: 1+1 MSP/APS configuration is applicable to STM-1/4/OC-3/12

or STM-16/OC-48 ports, only one MSP/APS protection group can be
provisioned per network element. The SNCP configuration is supported on
STM-1/4/OC-3/12 or STM-16/OC-48 interface.
Note 4: In redundant aggregate card configuration, work and protect ports
must be on aggregate cards (one in slot 6 and one in slot 7). However, if
aggregate card is non-redundant, the work and protect ports must be in slot
6.
The 1+1 MSP/APS can be provisioned in both redundant and non-redundant
mode in an OME6130 network element. The redundant aggregate cards have
the working and protection ports on separate cards. The redundant mode is
supported in 1xSTM-1/4OC-3/12 card and the STM-16/OC-48 card. The
non-redundant mode cards have the working and protection ports on the same
circuit pack (in slot 6 only). The non-redundant configuration is supported in
2xSTM-1/4/OC-3/12 card only. A filler panel must be placed in slot 7 when
1+1 MSP/ASP protection is configured in non-redundant mode.

The OME6130 tributary has the capability to automatically switch traffic from
a faulty working port to the protection port. Automatic protection switches are
initiated by the network element and are triggered by:
• Signal Fail (SF)
• Signal Degrade (SD)

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-4 Traffic protection switching

Figure 3-1
1+1 MSP/APS configuration

Normal Operation

A B

Switching in case of uni-directional configuration

A B

Switching in case of bi-directional configuration

A B

Working Path
Protection Path
Bridging

The bolder line indicates the current active path

(the path carrying traffic)

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-5

Table 3-3 gives the switching hierarchy criteria for MSP/APS mode and also
lists the priority for each switching mode.
Table 3-3
MSP/APS traffic protection hierarchy

Switching request Priority Type Alarm raised

Lockout 1 (highest) User

Signal Fail (SF) on 2 Automatic

Protection

Forced switch 3 User MSP/APS forced

switch to Port

Signal Fail (SF) on 4 Automatic

Working

Signal Degrade (SD) 5 Automatic

Manual switch to 6 User MSP/APS Manual

Protection switch to Port

Manual switch to 7 User MSP/APS Manual

Working switch to Port

Wait to restore time 8 Automatic

Note: Refer to Trouble Clearing and Module Replacement Procedures,

323-1855-543 for more details regarding the alarms raised on user initiated
switches.

SNCP/UPSR
Sub-network connection protection (SNCP) is path protection switching that
is initiated in the path terminating equipment when OME6130 is in SDH
mode. Unidirectional path switched ring (UPSR) is path protection switching
that is initiated in the path terminating equipment when OME6130 is in
SONET mode. In SNCP/UPSR, protection is initiated on a failure in the path.
It is required to create two paths for each circuit–one working and one
protection. Traffic in the source network element is bridged on both the
working and the protection paths while the destination network element selects
the best of the signals from the working or protection paths. SNCP/UPSR is a
dedicated protection mechanism. SNCP/UPSR operates in a unidirectional
protection switching manner. SNCP/UPSR is a protection scheme, which can
be applied on an individual basis to VC-n/STS-n (both HOVC and LOVC)
signals. The entry and the exit network elements are designated at connection
provisioning time. A network element can be both entry and exit network
element in case of bidirectional SNCP/UPSR ring connection. SNCP/UPSR

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-6 Traffic protection switching

ring groups are formed from unprotected facilities. When SNCP/UPSR ring
connections are provisioned on these facilities, all intermediate nodes have
pass-through connections.

Note 1: SNCP/UPSR can be provisioned only if the port used for working
or protection is not a part of MSP/APS.
Note 2: There should be availability of minimum bandwidth on both the
working and protection port. For example, to provision SNCP/UPSR for
add/drop E1/DS1 cross-connect, there should be at least one TU12/VT2
available on the working and protection ports.
Note 3: SNCP/UPSR configuration is supported on STM-1/4/OC-3/12 or
STM-16/OC-48 interface.
In SNCP/UPSR configuration, the reversion mode can be provisioned. In
revertive mode, traffic switches back to the work path once the fault condition
has cleared when the WTR period has elapsed. In non-revertive mode, traffic
remains on the protect path and does not automatically switch back to the work
path when the fault condition has cleared.

Table 3-4 lists the details regarding the maximum number of connections
supported in the SNCP/UPSR configuration.
Table 3-4
Maximum number of connections supported for SNCP/UPSR configuration

Capacity Maximum number Maximum number Maximum number of

of connections for of connections for connections for
STM-1/OC-3 STM-4/OC-12 STM-16 /OC-48

VT1.5/VC11 84 336 1344

VC12/VT2 63 252 1008

VC3/STS1 3 12 48

VC4/STS3c 1 4 16

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-7

Figure 3-2 shows the switching scheme in case of single and dual fiber cut.
Figure 3-2
SNCP/UPSR configuration

Normal Operation

A B

C D

Switching in case of single fiber cut

A B

C D

Switching in case of dual fiber cut

A B

C D

Working Path
Protection Path
Bridging

Bolder line indicates the currently active path

(the path carrying traffic )

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-8 Traffic protection switching

The OME6130 tributary has the capability to automatically switch traffic from
a faulty working path to the protection path. Automatic protection switches are
initiated by the network element and are triggered by one of the following fault
conditions:
• path Loss of Pointer (P-LOP)
• path alarm indication signal (P_AIS)
• unequipped path signal (UNEQ)
• path signal fail (P_SF)
• path signal degrade (P_SD)
Note: Path switch criteria for SNCP/UPSR can be manually provisioned
by the user.

Table 3-5 lists the switching hierarchy criteria for SNCP/UPSR mode and also
lists the priority for each switching mode.
Table 3-5
SNCP/UPSR traffic protection hierarchy

Switching request Priority Type Alarm Raised

Lockout 1 (highest) User -

Forced switch 2 Automatic Force switch to

channel

P-SF 4 Automatic -

P-AIS, P-LOP, and 3 Automatic -

P-UNEQ

P-SD 5 Automatic -

Manual switch on 6 User Manual switch to

protection path channel

Manual switch on 7 User Manual switch to

working path channel

Wait to restore time 8 Automatic Revertive switch from

channel on the path

Note: Refer to Trouble Clearing and Module Replacement Procedures,

323-1855-543 for more details regarding the alarms raised on user initiated
switch.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-9

User switch commands

The protection switching can be either automatic or user initiated.

Table 3-6 gives the brief description for the user initiated switches.

Note: The user initiated switches (or External Commands) are the same
for both MSP/APS and SNCP/UPSR protection configurations.
Table 3-6
User initiated switches

Switch Description

Lockout Prevents the traffic from switching to the protection

path.

Forced This switch can be used to force the traffic to working or

protection path regardless of the signal fail /degrade
condition.

Manual This switch can be used to switch traffic to working or

protection path manually and cannot be done when
there is signal fail/degrade condition on that path. The
manual request works only if there is no higher switch
request than itself.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-10 Traffic protection switching

Chapter procedure list

Table 3-7 lists the procedures that are described in this chapter.
Table 3-7
Chapter procedure list

Action Details

Querying an MSP/APS group Procedure 3-1

Creating an MSP/APS group Procedure 3-2

Deleting an MSP/APS group Procedure 3-3

Editing an MSP/APS group Procedure 3-4

Operating or releasing an external switch command on MSP/APS Procedure 3-5

protection group

Operating or releasing external switch command on an Procedure 3-6

SNCP/UPSR cross-connect

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-11

Procedure 3-1
Querying an MSP/APS group

Use this procedure to view the status of the Multiplex Section Protection
(MSP)/Automatic Protection Switching (APS) group provisioned on the
OME6130 network element.

Before you start

• Log into the network element user interface with the appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View MSP/APS Groups page (step 1).

Expected results
• The details of the MSP/APS groups provisioned on the network element are displayed.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click MSP/APS groups.
The View MSP/APS groups page is displayed.
Note: To view the protection switch status, click on the hyperlink of the
MSP/APS name.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-12 Traffic protection switching

Procedure 3-2
Creating an MSP/APS group

Use this procedure to create an Multiplex Section Protection (MSP)/Automatic

Protection Switching (APS) group on the STM-1/4/OC-3/12 ports or
STM-16/OC-48 ports of an OME6130 network element. This allows you to
associate a working channel with a protection channel. The protection channel
automatically duplicates the connection settings of the working channel.

Note 1: For the 2x155M circuit pack, Route diversity is always ON.
Note 2: When creating a MSP/APS with the 2xSTM-1/4/OC-3/12 circuit
pack, the aggregate card must be provisioned in slot 6 and a filler panel
over slot 7. When provisioning the MSP/APS group with redundant
aggregate cards, insert a 1xSTM-1/4/OC-3/12 card or 1xSTM-16/OC-48
card into both slots 6 and 7.
This allows you to configure the following parameters associated with the
protection group:
• Working port
• Protection port
• Reversion Mode
• WTR Time
• Current status
• Protection Switching Mode
• Route Diversity
• delete

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-13

Procedure 3-2 (continued)

Creating an MSP/APS group

Configurable parameters
Table 3-8 lists the configurable MSP/APS protection group parameters with
default and acceptable values.
Table 3-8
Configurable MSP/APS parameters

Parameter Default value Acceptable value

Working port STM1/OC3-1- • STM1/OC3-1-N-1

N-1/ • STM1/OC3-1-N-2
(see Note 3) • STM1/OC3-1-7-1
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2 (see Note 5)
where N is the slot number which can have the
value 4, 5, 6, 8 or 9.
For STM-16 capacity
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1

Protection port STM1/OC3-1- • STM1/OC3-1-N-1

N-2/ • STM1/OC3-1-N-2
(see Note 4) • STM1/OC3-1-7-1
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2 (see Note 5)
where N is the slot number which can have the
value 4, 5, 6, 8 or 9.
For STM-16/OC-48 capacity
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1

Protection Mode 1+1 1+1

Admin Reversion Non-Revertive • Non-Revertive

Mode • Revertive

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-14 Traffic protection switching

Table 3-8 (continued)

Configurable MSP/APS parameters

Parameter Default value Acceptable value

WTRTime 5 1 to 12
(see Note 2)

Protection 1 Way • 1 Way

Switching mode • 2 Way

Route Diversity Disable • Disable

• Enable

Note 1: There must not be any cross-connects provisioned on the unprotected

STM/OCn ports prior to provisioning the MSP/APS configuration.
Note 2: The WTR Time is applicable and provisionable only if the reversion mode
is set to revertive.
Note 3: The default value for the work port is the first available port (in the ascending
order either STM-1/OC-3 or STM-4/OC-12 interface).
Note 4: The default value for the protect port will be the next available port after
default work port, depending upon the type of interface chosen in the work port.
Note 5: For a redundant system, only one port is available for provisioning. Hence
for STM4/OC-12, redundant mode, ports STM4/OC12-1-6-2, and
STM4/OC12-1-7-2 are not available for provisioning.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-15

Procedure 3-2 (continued)

Creating an MSP/APS group

Before you start

• Log into the network element user interface with the appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
• Make sure that there are no connections provisioned on the STM-1/4 /OC-3/12 ports or on STM-16/OC-48
ports.

Procedure tasks
• Reach the view MSP/APS group page (step 1).
• Reach the Port Protection Provisioning page (step 3).
• Enter the desired values against the corresponding fields (step 4).

Expected results
• An MSP/APS protection group is created.
• If the expected results do not occur:
— Ensure that the STM-1/4/OC-3/12 ports or STM-16/OC-48 have no cross-connects provisioned.
— Contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-16 Traffic protection switching

Procedure 3-2 (continued)

Creating an MSP/APS group

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click MSP/APS groups.
The View MSP/APS groups page is displayed.
3 Click Create MSP/APS group.
The Provision port protection page is displayed.
Note: Ensure that there are no connections provisioned on the unprotected
STM-1/4/OC-3/12 ports or STM-16/OC-48 ports.
4 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 3-8 on page 3-13 for details regarding the configurable
parameters.
5 Click Submit.
A confirmation page is displayed.
6 Click Yes.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-17

Procedure 3-3
Deleting an MSP/APS group

Use this procedure to delete the Multiplex Section Protection

(MSP)/Automatic Protection Switching (APS) group on the network element.

Note 1: Ensure that the MSP/APS group to be deleted does not have
cross-connects provisioned on the relevant STM-1/4/OC-3/12 or
STM-16/OC-48 interfaces.
Note 2: When the route diversity is disabled at the far end network element
and the local OME6130 network element is in Unidirectional MSP/APS
mode, ensure that the far end network element is also switched to working
port while deleting the MSP/APS group.
.

Before you start

• Log into the network element user interface with the appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View MSP/APS groups page (step 1).
• Delete the desired MSP/APS group (step 3).

Expected results
• The desired MSP/APS group is deleted.
• If the expected results do not occur:
— Make sure that there are no cross-connects provisioned on the interface.
— Contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-18 Traffic protection switching

Procedure 3-3 (continued)

Deleting an MSP/APS group

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click MSP/APS groups.
The View MSP/APS groups page is displayed.
3 Check the box against the MSP/APS group to be deleted in the delete check
box.
4 Click Submit.
A confirmation page is displayed.
5 Click Confirm Delete.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-19

Procedure 3-4
Editing an MSP/APS group

Use this procedure to edit the Route diversity and the revertive mode.

Note: There must not be any external request given from the user prior to
editing the revertive mode parameters of MSP/APS group.

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
• Ensure that there is no external request given from the user prior to editing the revertive mode parameters
of MSP/APS group.

Procedure tasks
• Reach the View MSP/APS groups page (step 1).
• Reach the provisioning page of the desired MSP/APS group (step 3).
• Edit the revertive mode, Route diversity and WTR time (step 4).
• Set the revertive mode and the corresponding WTR time (step 5 and step 9).

Expected results
• The revertive mode of an MSP/APS group is edited.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-20 Traffic protection switching

Procedure 3-4 (continued)

Editing an MSP/APS group

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click MSP/APS groups.
The View MSP/APS groups page is displayed.
3 Click the desired MSP/APS name link.
The Protection Provisioning page is displayed.
4 Determine the next step:

If you want to edit Then go to

Admin Reversion Mode step 5
Route diversity step 7
WTRTime step 9

5 Select the appropriate value for Admin Reversion Mode from the pull-down
menu. Select Revertive or Non-Revertive.
Note: Ensure that the Admin Revertive Mode settings match the far-end
network element.
6 Go to step 10.
7 Select the appropriate value for Route diversity from the pull-down menu.
Select Enable or Disable.
Note: Ensure that Route diversity settings match the far-end network
element.
8 Go to step 10.
9 Select the appropriate values for WTR Time from the pull-down menu. Select
a value from 1 to 12.
Note: WTR Time can be set from1 to 12 minutes and can only be provisioned
when the MSP/ASP group is set to revertive.
10 If you want to edit more parameters, go to step 4. Otherwise, go to step 11.
11 Click Submit.
A confirmation dialog is displayed.
12 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-21

Procedure 3-5
Operating or releasing an external switch command on MSP/APS
protection group

Use this procedure to execute external commands on the configured Multiplex

Section Protection (MSP)/Automatic Protection Switching (APS) group.

This procedure allows you to:

• clear active switch requests on the protection port
• prevent the traffic from switching to the protection port (Lockout
Protection)
• force switch the traffic to the protection port
• force switch the traffic to the working port
• manual switch the traffic to the protection port
• manual switch the traffic to the working port
Note 1: You cannot perform a protection switch if a higher-priority switch
is already active on the protection group.
Note 2: The manual switch command is successfully executed only if the
working or the protection path to which the traffic is being switched is error
or alarm free.

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Protection provisioning page for MSP/APS group (step 1).
• Reach the provisioning page of the desired MSP/APS group (step 3).
• Execute the desired external command (step 4).

Expected results
• External command is executed for the MSP/APS.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-22 Traffic protection switching

Procedure 3-5 (continued)

Operating or releasing an external switch command on MSP/APS protection group

Action
Step Action

1 Click Protection in the Navigation menu.

2 Click MSP/APS groups.
The MSP/APS groups page is displayed.
3 Click the name link of the desired MSP/APS group.
The Protection Provisioning page is displayed.
4 Issue the external switch command.
The Protection Provisioning page is displayed.
If you want to Then click
lockout protection Lockout Protection
force switch to protection path Forced Switch to Protect
force switch to working path Forced Switch to Working
manual switch to protection path Manual Switch to Protect
manual switch to working path Manual Switch to Working
clear an active external request Release

5 Click confirm request.

A success message is displayed.
Note: The external commands are arranged in order of their priority in
decreasing order. The external command having the higher priority takes
precedence over an existing active external request on the protection group.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Traffic protection switching 3-23

Procedure 3-6
Operating or releasing external switch command on an SNCP/UPSR
cross-connect

Use this procedure to execute external commands on the source or destination

path of a sub-network connection protection (SNCP)/unidirectional path
switch ring (UPSR) cross-connect.

This allows you to:

• force switch the traffic to the protection path
• force switch the traffic to the working path
• prevent the traffic from switching to the protection path (Lockout
Protection)
• manual switch the traffic to the protection path
• manual switch the traffic to the working path
• clear active switch requests on the protection port
Note 1: You cannot perform a protection switch if a higher priority switch
is already active on the protection group.
Note 2: The manual switch command is successfully executed only if the
working or the protection path to which the traffic is being switched is error
or alarm free.
.

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Connection protection requests page (step 1).
• Execute the desired external command (step 4).

Expected results
• External Command is executed for the SNCP/UPSR.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
3-24 Traffic protection switching

Procedure 3-6 (continued)

Operating or releasing external switch command on an SNCP/UPSR cross-connect

Action
Step Action

1 Click Protection in the Navigation menu.

2 Click Connections.
The Connection protection requests page is displayed.
3 Click edit link corresponding to the filtered cross-connect.
The Protection request page is displayed.
4 Select the desired protection connection and Click on it.
If you want to Then click
lockout protection Lockout Protection
force switch to the protection path Forced Switch to Protect
force switch to the working path Forced Switch to Working
manual switch to the protection path Manual Switch to Protect
manual switch to the working path Manual Switch to Working
clear an active external request Release

A confirmation message is displayed.

Click confirm request.
5 A success message is displayed.
Note: The external commands are enforced in order of their priority. The
external command having a higher priority takes precedence over an existing
active external request on the cross-connect.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
4-1

Timing facility provisioning 4-

This chapter contains procedures for provisioning and operation of timing

facilities associated with the external synchronization interface (ESI) on the
OME6130 network element. The synchronization provides the timing and
synchronization management functionality for the network element.

The selection of a timing generation source is made from a set of nominated

clock sources. You can nominate a maximum of two clock sources. The
following are the possible clock sources:
• internal
• BITS1/BITS2
• E1/DS1 interfaces from 28xE1/DS1 circuit pack
• two optical interfaces on the 2x155/622M interface
or

• one optical interface on the 1x155/622MAgg interface

• one optical interface on the 1x2G5Agg interface

The selection of the clock sources is based either on the quality or priority of
the nominated clock source. This depends on the timing manager
configuration. When the quality mode is enabled in the timing manager, the
network element locks to one of the nominated clock sources based on the
quality level and/or priority of the clock sources. When two clock sources have
the same quality level, the priority of the clock sources is processed. The
priority of the clock sources is user-provisionable and from 1 (highest) to 2
(lowest), the priority 0 indicates that the clock source is not available for
selection. When the quality level is disabled in the timing manager, the
network element selects the clock source based on the priority assigned to the
clock source. However, the network element fails to lock to a clock source if
the clock source has a lockout request against it and/or is degraded.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-2 Timing facility provisioning

The timing sources provide 2:1 protection (2 sources available for 1 selection).
The active synchronization source that is selected from the set of nominated
synchronization sources depends on:
• user or automatic timing protection switch requests in the network element
• validity of the nominated sources (synchronizaion status values)
• priorities assigned to the source (user provisionable)
• quality of the available signal on the nominated source (ppm offset less
than or equal to 17ppm)
• alarm present on the source (Loss of Signal or Alarm Indication Signal)
Note: The hold over update time for 1x155/622MAgg or 2x155/622M
circuit pack is at least 10 minutes. If the network element is pushed to
holdover in time less than 10 minutes at a particular ppm (say 0ppm -
12ppm), the node goes to holdover, but the output ppm may be less than
12ppm.

Quality mode
The quality of a clock is automatically detected in case of STM/SONET clocks
from their S1 byte. The user can configure the QL label of the BITS/PDH
clocks manually. When a BITS/PDH clock is nominated it comes up with an
Invalid quality label.

The following quality modes are available to the user:

• If the QL Mode is Disabled: Nominated clock input QL is not considered

for clock selection. In this mode, the clock with the highest priority is
selected. The next highest priority clock is selected as the secondary
reference.
• If the QL Mode is Enabled: Nominated clock input QL is considered for
clock selection. In this mode, the clock with better QL is selected. In case
of two inputs having the same QL label, the user configured priorities are
used to determine the clock selected.
Output quality (QL) mode
Depending on network element configuration (SDH/SONET mode) and
output QL mode, a differing ranges of output QL values can be selected.

The following is the list of options available to you for configuring the QL
mode:
• Auto: Synchronous status messaging (SSM) sends a quality level label of
the selected clock as network element quality to all interfaces connected to
network element.
• Manual: SSM sends a user (operator) specified value as a network element
Quality to all interfaces connected to the network element.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-3

Note: Irrespective of the output QL mode, a DNU/DUS is sent on the

selected clock interface and its MSP/APS mate port, if any.

Table 4-1 lists the parameters associated with bits squelching.

Table 4-1
Bits squelching in SSM

Switching mode Description

BITS Squelching An AIS signal is transmitted on the BITS Data output and
BITS Clock output is inhibited (if present).

QL_minimum This is a user defined Quality level. If the output quality level
of the node falls below the QL_minimum, the BITS is
squelched.

Defaults The default of this user-configured parameter will be set as

DNU/DUS/INVALID. This implies that Bits squelching is
disabled as default and the user must configure to enable it.

Quality Disabled BITS squelching is not available.

Mode

Comparison of output quality mode in SDH/SONET mode

In both SDH and SONET mode, the comparison between the output Quality
and the user specified minimum quality will be made. This implies that if the
output quality level of the network element is greater than or equal to the user
configured minimum quality level, the BITS outputs are not to be squelched.

Synchronization protection
Table 4-2 lists the switching hierarchy criteria for the timing reference.
Table 4-2
Switching hierarchy for the timing reference

Switching Mode Priority

lockout request 1 (highest)

signal fail 2

forced switch 3

manual switch 4

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-4 Timing facility provisioning

For details on switching modes of synchronization sources, refer to

Procedure 4-6, Operating or releasing an external switch command on a
nominated synchronization source and Procedure 4-7, Provisioning and
clearing a lockout request for the nominated clock source.
Table 4-3
User switch commands

User switch Description

Manual The network element switches to the selected clock source

on manual switch external request.

Forced The network element switches to the selected clock source

on forced switch external request and cannot be switched to
other clock sources unless the external request is cleared.
Forced switch has a higher priority over manual switch.

Lockout The clock source will be excluded from selection if this switch
is on. This has the highest priority over other request.

Note 1: Signal fail takes precedence in relation to the sequence of

operation of the forced switch and the condition of the timing reference.
For example, if a forced switch is active on a clock source and the network
element is locked to the same source and there is signal failure on the
timing reference, the forced switch is dropped and the network element
locks to the next available valid clock source. If there is a signal fail on the
nominated clock source and a forced switch operation is performed, the
network element switches to the clock source and enters into the holdover
mode.
Note 2: In the event of a forced switch operation on a clock source
generating an invalid signal (signal fail condition), the network element
switches to this clock source and enters into the holdover mode. The
network element remains in the holdover mode for 24 hours before
entering into the free-running mode. In the event of recovery of the clock
source, the network element locks to the recovered clock source.
You can derive a maximum of two synchronization outputs from a network
element. In SDH mode, you can use data of 48 Mbit/s or clock of 2 Mbit/s.

The output quality level under synchronization status of the network element
is not configurable, when the output quality mode is set to auto. The clock
output quality level is configurable if the output quality mode is set to manual.

Note: The output quality level can be overridden by selecting the output
quality mode as manual and assigning the override value for the output
quality level.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-5

Table 4-4 list the supported BITS signals for an OME6130 chassis.
Table 4-4
Supported BITS signals for NT6Q01AA chassis

BITSIN-1-2-1 BITSIN-1-2-2 NE
SONET/SDH
IN OUT IN OUT Mode

E1 E1 2M 2M SDH

DS1 DS1 DS1 DS1 SONET

Table 4-5 lists the various Synchronization states arranged in the order of
performance.
Table 4-5
Synchronization status

Synchronization states Quality Description

level
order

SDH mode

QL-PRC 2 Primary Reference Clock

QL-SSUA 4 Synchronization Status Unit A

QL-SSUB 8 Synchronization Status Unit B

QL-SEC 11 SDH Equipment Clock

QL-DNU 15 Do not Use

SONET mode

PRS 1 Primary Reference Source

STU 2 Synchronized - Traceability Unknown

ST2 3 Stratum 3 Traceable

TNC 4 Transit Node Clock Traceable

ST3E 5 Stratum 3E Traceable

ST3 6 Stratum 3 Traceable

SMC 7 SONET Minimum Clock Traceable

ST4 8 Stratum 4 Traceable

DUS 9 Do not use for Synchronization

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-6 Timing facility provisioning

The maximum number of timing reference ports on the OME6130 network

element is two. You can set the priority of the synchronization source to one or
two. If the priority of a clock source is set to 0, the source is not available for
selection.

The timing references that can be nominated on the OME6130 network

element are:
• selective 10 E1/DS1 ports on the 28xE1DS1 circuit pack
• first two external synchronous inputs
• two optical ports, either STM-1/4/16/OC-3/12/48
• the internal clock
Note: Make sure that priority is not set to ‘0’ as it is an invalid priority.

The 10 E1/DS1 ports on the 28xE1/DS1 circuit pack are:

• E1-1-N-1/DS1-1-N-1
• E1-1-N-4/DS1-1-N- 4
• E1-1-N-7/DS1-1-N-7
• E1-1-N-10/DS1-1-N-10
• E1-1-N-13/DS1-1-N-13
• E1-1-N-16/DS1-1-N-16
• E1-1-N-19/DS1-1-N-19
• E1-1-N-22/DS1-1-N-22
• E1-1-4-25/DS1-1-N-25
• E1-1-4-28/DS1-1-N-28
where N can take the values 4, 5, 8 or 9.

First two external synchronous inputs are:

• BITSIN-1-2-1
• BITSIN-1-2-2

The first two STM-1/4/OC-3/12 ports are:

• STM1/OC3-1-N-1
• STM1/OC3-1-N-2
• STM1/OC3-1-7-1
or

• STM4/OC12-1-6-1

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-7

• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2
where N can take the values 4, 5, 6, 8 or 9 for STM-1/4/OC-3/12.

For STM-16/OC-48 mode

• STM16/OC48-1-6-1
• STM16/OC48-1-7-1
Note: The BITSIN-1-2-1 interface can be used to provision a 2 MHz clock
to the network element, while the BITSIN-1-2-2 interface supports a
2Mbits data clock input.

Chapter procedure list

Table 4-6 lists the procedures that are described in this chapter.
Table 4-6
Chapter procedure list

Action Details

Querying or configuring synchronization status Procedure 4-1

Nominating timing reference Procedure 4-2

Querying the status of nominated timing references Procedure 4-3

Editing the nominated timing reference Procedure 4-4

Deleting external synchronization sources Procedure 4-5

Operating or releasing an external switch command on a Procedure 4-6

nominated synchronization source

Provisioning and clearing a lockout request for the nominated Procedure 4-7
clock source

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-8 Timing facility provisioning

Procedure 4-1
Querying or configuring synchronization status

Use this procedure to view or configure the synchronization Status. You can
also use this procedure to view alarms raised on the external synchronization
interfaces (ESI).

This allows you to view or configure the following parameters associated with
the synchronization status:
• QL Mode
• Output QL Mode
• Reversion Mode
• WTRTime
• Node output quality level
• Node Minimum quality level
• Output quality Level (view only)
• SETG (Synchronization Equipment Timing Generator) Status (view only)
• Selected Clock Source (view only)
• External Request on Selected source (view only)

Configurable synchronization status parameters

Table 4-7 lists the configurable parameters associated with synchronization
status with their default and acceptable values when OME6130 network
element is in the SDH mode.
Table 4-7
Configurable synchronization status parameters in SDH mode

Parameter Default value Acceptable value

QL Mode Disabled • Disabled

• Enabled

Output QL Mode Manual • Manual

• Auto

Reversion Mode Manual • Manual

• Auto

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-9

Table 4-7 (continued)

Configurable synchronization status parameters in SDH mode

Parameter Default value Acceptable value

WTR Time 5 1-12

Node output quality level INVALID • PRC

• SSU_A
• SSU_B
• SEC
• DNU
• INVALID

Node Minimum quality level INVALID • PRC

• SSU_A
• SSU_B
• SEC
• DNU
• INVALID

Table 4-8 lists the configurable parameters associated with synchronization

status with their default and acceptable values when OME6130 network
element is in the SONET mode.

Table 4-8
Configurable synchronization status parameters in SONET mode

Parameter Default value Acceptable value

QL Mode Disabled • Disabled

• Enabled

Output QL Mode Manual • Manual

• Auto

Reversion Mode Manual • Manual

• Auto

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-10 Timing facility provisioning

Table 4-8 (continued)

Configurable synchronization status parameters in SONET mode

Parameter Default value Acceptable value

WTR Time 5 1-12

Node output quality level INVALID • PRS

• STU
• ST2
• TNC
• ST3E
• ST3
• SMC
• DUS
• INVALID

Node Minimum quality level INVALID • PRS

• STU
• ST2
• TNC
• ST3E
• ST3
• SMC
• DUS
• INVALID

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-11

Procedure 4-1 (continued)

Querying or configuring synchronization status

Before you start

• Log into the network element user interface at the default view level with the appropriate user access
privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Synchronization state page (step 1).
• Select the appropriate values against the fields (step 4).

Expected results
• The current synchronization status is displayed.
• The synchronization status parameters are edited.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Synchronization.
3 Click Synchronization status.
The Synchronization state page is displayed and also alarms are displayed in
the status and alarms area.
If you want to configure the parameters, go to step 4, Otherwise you have
completed the procedure.
4 Select the appropriate values against the fields. For more details regarding
the configurable parameters, refer to Table 4-7 on page 4-8 and Table 4-8 on
page 4-9 when OME6130 network element is in SDH and SONET modes
respectively.
5 Click Submit.
A confirmation page is displayed.
6 Click Accept Valid Modifications.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-12 Timing facility provisioning

Procedure 4-2
Nominating timing reference

Use this procedure to nominate synchronization sources on the OME6130

network element. The network element locks to one of the nominated clock
sources based on the quality or the priority of the nominated clock sources.

The OME6130 network element allows you to assign a priority to the

following synchronization sources that can be nominated:
• internal
• BITS
• port
Note: The network element goes to internal freerun mode instead of
holdover mode when the clock source is internal clock and other locked
synchronous sources fail.

Configurable synchronization sources parameters

Table 4-9 lists the ports that can be selected as clock references associated with
synchronization sources in OME6130 network element.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-13

Table 4-9
Configurable synchronization source parameters
Parameter Default value Acceptable value

Clock Reference internal • internal

• port
• bits

Clock Reference Port

If E1/DS1 port from 28xE1/DS1 circuit pack is the clock
reference then the options are:
• E1-1-N-1/DS1-1-N-1
• E1-1-N-4/DS1-1-N-4
• E1-1-N-7/DS1-1-N-7
• E1-1-N-10/DS1-1-N-10
• E1-1-N-13/DS1-1-N-13
• E1-1-N-16/DS1-1-N-16
• E1-1-N-19/DS1-1-N-19
• E1-1-N-22/DS1-1-N-22
• E1-1-N-25/DS1-1-N-25
• E1-1-N-28/DS1-1-N-28
where N can take the values 4, 5, 8 or 9.
If STM-1/4/OC-3/12 port is the clock reference then the
options are:
• STM1/OC3-1-N-1
• STM1/OC3-1-N-2
• STM1/OC3-1-7-1
or
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2 (see Note 1)
• STM4/OC12-1-7-1
where N can take the values 4, 5, 6, 8 or 9.
For STM-16/OC-48 capacity then the options are:
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1
If BITS is the clock reference then the options are:
• BITSIN-1-2-1
• BITSIN-1-2-2

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-14 Timing facility provisioning

Parameter Default value Acceptable value

Priority 0 0, 1, 2 (see Note 2)

Note 1: For a redundant system, only one port is available for provisioning. Hence for STM-4/OC-12,
redundant mode, ports STM4/OC12-1-6-2, and STM4/OC12-1-7-2 are not available for provisioning.
Note 2: 1 has the highest priority and 2 the lowest. Priority 0 means the clock source is not used for
selection.

Before you start

• Log into the network element user interface at the default view level with the appropriate user access
privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Nominate timing reference page (step 1).
• Select the appropriate values against the fields (step 4).

Expected results
• You have nominated the synchronization sources for the OME6130.
• The synchronization source parameters are edited.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Synchronization.
3 Click Nominate timing reference.
The Nominate timing references page is displayed.
4 Select appropriate values against the fields. Refer to Table 4-9 on page 4-13
for more details on configurable parameters.
5 Click Submit.
A success message is displayed.
Note: When nominating an E1/DS1 or BITS-1/BITS-2 as a timing reference,
the user must manually set the quality level for the timing source, as they are
set to INVALID by default. For details, refer to Procedure 4-4, Editing the
nominated timing reference.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-15

Procedure 4-3
Querying the status of nominated timing references

Use this procedure to view the status of all the nominated synchronization
sources of the network element. This allows you to view the following
parameters associated with the nominated synchronization sources:

• Current Source
• Clock Source
• Priority
• Quality Level
• Clock Status
• Lockout Request
Note: You can view the quality level of a nominated synchronization
source only if the QL Mode is enabled in the Synchronization status.

Before you start

• Log into the network element user interface with the appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View nominated timing references page (step 1).

Expected results
• Synchronization source parameters are displayed.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-16 Timing facility provisioning

Procedure 4-3 (continued)

Querying the status of nominated timing references

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Synchronization.
3 Click View Nominated timing references.
The View nominated timing references page is displayed.
The details associated with all the nominated synchronization interfaces on
the network element is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-17

Procedure 4-4
Editing the nominated timing reference

Use this procedure to edit the following parameters:

• Priority of the timing reference source
• Quality level (for BITS and E1/DS1 timing reference sources)
Note: 0 is an invalid priority. It indicates that the clock source is not
available for selection.

CAUTION
If the quality level mode is disabled or the quality level
of the timing references are the same, changing the
priority for the timing source will cause a switch in the
timing reference.

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View nominated timing references page (step 1).
• Edit the priority of the desired timing generation source member (step 6).
• Select the desired quality level from the pull down menu against the Quality Level field (step 8).

Expected results
• The priority of the desired timing generation source member is edited.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-18 Timing facility provisioning

Procedure 4-4 (continued)

Editing the nominated timing reference

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Synchronization.
3 Click View Nominated timing references.
The View nominated timing references page is displayed.
A list of all the nominated synchronization sources on the network element is
displayed.
4 Click the desired clock source link.
The Edit ClockSel page is displayed.
5 Determine your next step.
If you want to edit Then go to
priority of the timing step 6
reference
Quality Level of the step 8
timing reference

To edit priority of the timing reference

6 Select the desired priority against the Priority field from the pull down menu.
Note: The priority can be 1 or 2. 1 indicates highest priority, while 0 indicates
the clock source is not available for selection.
CAUTION
Priority level change
Changing the priority level may cause a timing
reference switch.

7 Click Submit.
A success message is displayed.
To edit the quality level of the timing reference
8 Select the desired quality level from the pull down menu against the Quality
Level field.
9 Click Submit.
A success message is displayed.
Note: If you are nominating a BITS clock or an E1/DS1 port as a clock
source, you can change the quality level.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-19

Procedure 4-5
Deleting external synchronization sources

Use this procedure to delete the nominated synchronization references.

Note 1: Deleting an active synchronization source causes a timing

reference to switch to the next available synchronization source based on
the quality level and/or priority according to the selection of QL mode as
Disabled/Enabled.
Note 2: Before deleting an active synchronization source, lockout of the
timing reference should be done.
Note 3: Deleting the last synchronization source causes the network
element to go into holdover mode, if it was locked previously.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View nominated timing reference page (step 1).
• Delete the desired nominated synchronization source (step 3).

Expected results
• The synchronization source is deleted.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-20 Timing facility provisioning

Procedure 4-5 (continued)

Deleting external synchronization sources

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Synchronization.
3 Click View Nominated timing references.
The View nominated timing references page is displayed.
4 Select the clock source to be deleted against the delete field.
Note: The user should manually switch away from the timing reference
source to be deleted before proceeding with the delete command.
5 Click Submit.
A confirmation page is displayed.
6 Click Yes.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-21

Procedure 4-6
Operating or releasing an external switch command on a nominated
synchronization source

Use this procedure to operate or release a switching command on a nominated

synchronization source. This allows you to perform force switch or manual
switch on a nominated clock source.

Note: If you want to provision a lockout request on a nominated

synchronization source, refer to Procedure 4-7, Provisioning and clearing
a lockout request for the nominated clock source.

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the External request page (step 1).
• Select the desired synchronization source and the desired protection switch operation you need to perform
(step 3).

Expected results
• A user-initiated switch request is issued or cleared.
• A timing reference protection switch operation occurs.
• If the expected results do not occur:
— Ensure that there is no active external request on the network element.
— Contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-22 Timing facility provisioning

Procedure 4-6 (continued)

Operating or releasing an external switch command on a nominated synchronization source

Action
Step Action

1 Click Protection in the Navigation menu.

2 Click Timing manager.
The Timing manager protection request page is displayed.
3 Select the desired synchronization source against the Synchronization
Source field.
4 Issue/clear an external switch command.
If you want to Then click
release an active external request Release
force switch the network element to lock to a Forced Switch
nominated source
manual switch the network element to lock to a Manual Switch
nominated source
Lockout nominated clock source Lockout Source
clear lockout of network element from a nominated Clear Lockout
source

A confirmation page is displayed.

5 Click Confirm request.
A success message is displayed.
Note: To successfully execute the external request, you must clear any
existing active higher priority external requests on the nominated
synchronization sources.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Timing facility provisioning 4-23

Procedure 4-7
Provisioning and clearing a lockout request for the nominated clock
source

Use this procedure to operate or release a lockout request on a nominated clock

source.

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View nominated timing references page (step 1).
• Reach the View clock sel page (step 3).
• Select the desired synchronization source to provision lockout request for the clock source (step 6).

Expected results
• A lockout request is issued or cleared.
• A timing reference protection switch may occur.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
4-24 Timing facility provisioning

Procedure 4-7 (continued)

Provisioning and clearing a lockout request for the nominated clock source

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Synchronization.
3 Click View Nominated timing references.
The View nominated timing references page is displayed.
4 Click the desired clock source link in the clock source field.
The Edit ClockSel page will be displayed.
5 Select your next step.
If you want to Then go to
operate a lockout step 6
clear a lockout step 8

6 Edit the Lockout request field as On to provision the lockout request for the
nominated clock source.
Note: If a lockout is applied to the currently active clock source, a timing
reference switch will occur to the next available timing reference.
7 Click Submit.
A success message is displayed. You have completed the procedure.
8 Edit the Lockout request field as Off to clear the lockout request for the
nominated clock source.
9 Click Submit.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
5-1

Provisioning DCN 5-

This chapter contains procedures for provisioning and operation of data

communication channels (DCC) on the OME6130 network element.

The OME6130 can be provisioned to act as an iISIS or OSPF router for DCC
in remote management. It can exchange and maintain the routing information
on both the DCC and LAN to which it is connected using the LAN port. The
network element processes the router information on the LAN port if the OSPF
Ethernet parameter is enabled. Similarly, the routing information on the Data
communication channel is processed. The user can enable iISIS as a routing
protocol at the nodal level and at the interface level also for ECC interfaces.

The OME6130 has the capability to use either IP or OSI as Layer 3 protocol
for routing the data communication packets from the element management
system. It also supports overhead tunneling. Using overhead tunneling you can
transfer transparently the overhead data belonging to a different network
element across the STM-1/4/OC-3/12 ports or STM-16/OC-48 ports.

The OME6130 also supports the remote management using the embedded
communication channel (ECC) to allow the remote EMS/NMS to
communicate to the network element for OAM&P applications. The
OME6130 supports provisioning of the ECC over the following bytes/sets of
bytes:
• DCC-R/SDCC
• DCC-M/LDCC
• F1
• F2
• F3
• F2F3
Note: If the ECC_bytes are enabled on the STM-1/4/OC-3/12 port or
STM-16/OC-48 port then the corresponding bytes cannot be used for
tunneling.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-2 Provisioning DCN

OSPF
The OSPF is an interior gateway routing protocol based on the shortest path
first or link-state algorithm. Routers use link-state algorithms to send routing
information to all nodes in an internetwork by calculating the shortest path to
each node based on a topography of the internet constructed by each node.
Each router sends that portion of the routing table (keeps track of routes to
particular network destinations) that describes the state of its own links, and it
also sends the complete routing structure (topography). The advantage of
shortest path first algorithms is that they result in smaller and more frequent
updates everywhere. They converge quickly, thus preventing problems like
routing loops and count-to-infinity (when routers continuously increment the
hop count to a particular network) which results in a stable network.

The OSPF feature enables monitoring of neighbors of a network element and

the debugging the routing information for In Band Communication (IBC). The
OSPF parameters can be configured for all embedded control channel
interfaces and for the LAN port to enable routing between these interfaces.
OSPF as a routing algorithm is used to route IP packets through the shortest
path. For this to happen, the routers need to properly establish the adjacency
and then exchange their routing database with each other.

OSPF authentication is used to avoid any malicious intentions of establishing

adjacency, thereby avoiding any malicious intentions of knowing routing
database of a network. The password configured in OSPF authentication mode
is sent in OSPF packets. This is used to establish adjacency where the same
password needs to be configured on both interfaces connected to each other.

OSPF network can be divided into sub-sections called areas. An area is a group
of OSPF networks, routers, and links that have the same area identification. It
helps in reducing the size of the router database as router only possess
information about network topology that is within the area. The default area
parameter is 0.0.0.1. Any valid IP address is an acceptable area parameter.

iISIS
iISIS stands for integrated ISIS where ISIS is the routing protocol for OSI
protocol suite. iISIS is an integration of ISIS routing protocol with IP specific
features. With iISIS as the routing protocol, OME6130 can forward OSI
packets and can send IP packets through OSI network elements cloud. This
helps the network element to integrate into an IP or OSI network environment.
The connectivity of the network element to the Element Manager can be
established either directly over IP or IP over OSI tunnel, if the network element
is in the midst of OSI network cloud. The same manual area address (MAA)
needs to be provisioned between OME6130 and the adjacent network element.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-3

Static route
For routing between routers to work efficiently in a network, routers must have
knowledge of other network IDs or it has to configure with a default route.
When enabled, the route can be advertised over, iISIS or both. This is based on
the routing settings that have been enabled on the network element. A router
with manually configured routing tables is known as a static router. A Static
route is an entry in network element routing table that specifies how to reach
an IP address through a particular gateway (network element or interface).
Static routes are used to provide static connectivity between routers, meaning
the routes do not change automatically unlike routing protocols. A static route
allows the user to access the network element from any network. The user can
do this by adding a destination network IP address and the IP address of next
hop to a network element. Thus a user can establish a link.

Proxy ARP
Proxy ARP allows a gateway network element to respond to address resolution
protocol (ARP) requests for subtending network elements that are within the
same subnetwork as the customer DCN address range. The proxy ARP feature
removes the need for customers to provision static routes on their routers and
routing protocols (OSPF) between the gateway network elements and the
customer DCN.

The OME6130 network element supports viewing and adding of proxy ARP
neighbours.

Data communication channel

Each SDH/SONET frame includes two data communication channels (DCC)
called Regenerator Section/Section DCC and Multiplex Section/Line DCC for
transporting management messages between network elements and
management systems. These in-band data communication channels enable
service providers operation support systems (OSS) to manage SDH/SONET
network elements without the need for an expensive out-of-band data
communication network.

E1/VC12 management channel can be used to transport management

communications between network elements and management systems. These
management channels enable service providers to manage SDH network
elements without the need of expensive out-of-band data communications
network.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-4 Provisioning DCN

Serial port
Serial communication is possible due to the serial port. The serial port allows
data communication between two network elements. Once the serial port has
been properly configured, the serial port can be used to send data and receive
data. There are two applications for the serial port on the OME6130 network
element. This can be used with user data channel (UDC) or PPP network. For
UDC network, overhead byte F1 is used for data communication purpose.

The OME6130 network element supports external modem connectivity to the

network element through a RS232 serial interface. The M1/F1 port interface
on the network element can be configured for modem operation. This
configuration can be done only from the craft terminal. The data
communication over serial connectivity is based on IP over PPP. The modem
facility provides a serial point-to-point connectivity using PPP protocol and is
terminated on IP.

Serial communication requires that you specify the following parameters:

• transmission baud rate
• application

Overhead tunnel
You can use this facility when a network element is used as a pass through
element. For using overhead byte for the tunnel, you must first delete it, then
recreate it with the appropriate overhead byte.

For more information on the supported applications and engineering

guidelines for DCN, refer to the Planning Guide, NT6Q92MB.

For more information on the Network interface parameters, refer to the Local
Craft Access User Guide, 323-1855-195.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-5

Chapter procedure list

Table 5-1 lists the procedures that are described in this chapter.
Table 5-1
Chapter procedure list

Action Details

Provisioning static routes Procedure 5-1

Viewing or deleting static routes Procedure 5-2

Viewing and adding the Proxy ARP neighbours Procedure 5-3

Deleting the Proxy ARP neighbours Procedure 5-4

Configuring OSPF area Procedure 5-5

Disabling OSPF Procedure 5-6

Querying or provisioning iISIS parameters Procedure 5-7

Provisioning a network interface Procedure 5-8

Querying or editing network interfaces Procedure 5-9

Deleting a network interface Procedure 5-10

Querying or provisioning serial port parameters Procedure 5-11

Querying status of overhead tunnel Procedure 5-12

Creating an overhead tunnel Procedure 5-13

Deleting an overhead tunnel Procedure 5-14

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-6 Provisioning DCN

Procedure 5-1
Provisioning static routes

Use this procedure to create static routes on the OME6130 network element.
Static route are entries in the network element routing table that specify how
to reach an IP address through a particular gateway (network element or
interface). Static routes are special routes that the network administrator
manually enters into the router database.

Note 1: The next hop IP address must be within the same network and only
one static route can be configured per destination IP address.
Note 2: When DCN byte configuration is changed from DCCR to DCCM,
the static route over the interface is not restored after configuration change.
The static route is recreated only after warm restart.
Note 3: iISIS/OSPF can be enabled on ecc interfaces. OSPF can only be
enabled on Eth, mgmt and sgre1 interfaces.

Configurable parameters
Table 5-2 lists the configurable static route parameters with their default and
acceptable values.
Table 5-2
Configurable static route parameters

Parameter Default value Acceptable value

Destination Network IP - 0 to 255.255.255.254

Address

Destination Network - 0 to 32
Address Mask length

Next hop IP Address - 0 to 255.255.255.254 (see Note 1 and

Note 2)

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-7

Table 5-2 (continued)

Configurable static route parameters

Parameter Default value Acceptable value

Advertise Route Disable • Disable

• Enable
(see Note 3)

Network Interface LAN-1-6 (eth0) • LAN-1-6 (eth0)

• STM1/OC3-1-N-1
• STM1/OC3-1-N-2
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2 (see Note 6)
where N is the slot number which can
have the value 4, 5, 6, 7, 8 or 9.
For STM-16/OC-48 capacity
• STM16/OC48-1-6-1 (ecc_6_1)
• STM16/OC48-1-7-1 (ecc_7_1)

Note 1: The Next Hop IP Address has to be specified only when the static route is
provisioned on eth0. If it is ecc interface, the Next Hop IP Address need not be
specified.
Note 2: If the address is not specified or is invalid for eth0 interface, an error
message is displayed on submit.
Note 3: When the static route with advertise option “Enable” is configured, the
routing protocol iISIS or OSPF can be enabled on the same interface.
Note 4: Any invalid static route, added on a point-to-point interface is added in the
WUI, but is not added in the Kernel routing table.
Note 5: Any invalid static route added on a broadcast interface (eth) is blocked.
Note 6: For a redundant system, only one port is available for provisioning. Hence
for STM4/OC12, redundant mode, ports STM4/OC12-1-6-2, and STM4/OC12-1-7-2
are not available for provisioning.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-8 Provisioning DCN

Procedure 5-1 (continued)

Provisioning static routes

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Static routes configuration page (step 1).
• Add a route to the reach the desired destination IP by specifying the gateway (step 4).

Expected results
• A static route is successfully created.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
A list is displayed under DCN.
3 Click Static route.
The Static routes configuration page is displayed.
4 Click Add a new Static Route.
The Creating Static Route page is displayed.
5 Enter the appropriate values against the fields. For details regarding the
configurable parameters, refer to Table 5-2 on page 5-6.
6 Click Submit.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-9

Procedure 5-2
Viewing or deleting static routes

Use this procedure to view or delete static routes on the OME6130 network
element. For details regarding the static route parameters, see Table 5-2 on
page 5-6.

CAUTION
Potential loss of communication to network element
There is a risk of loss of visibility to the network
element when you delete a static route provisioned on
the network element. You may lose connection to the
network element if you do not have any other route to
access the network element. Ensure you have another
link or route to access the network element (DCC,
direct connection, serial port).

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the view or delete Static routes page (step 1).
• Delete the desired static route entry (step 4).

Expected results
• Static routes provisioned on the network element are displayed.
• A static route is successfully deleted.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-10 Provisioning DCN

Procedure 5-2 (continued)

Viewing or deleting static routes

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
A list is displayed under DCN.
3 Click Static route.
The Static routes Configuration page is displayed. The details regarding the
provisioned static routes are displayed.
If you want to delete a static route entry continue with step 4. Otherwise, you
have completed the procedure.
4 Select the static route entry to be deleted by putting a check mark in the
delete field.
Note: If your PC and the network element is in a different subnetwork,
communication will be lost as a result of deleting the static route on the LAN
interface.
5 Click Submit.
A confirmation message is displayed.
6 Click Yes.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-11

Procedure 5-3
Viewing and adding the Proxy ARP neighbours

Use this procedure to view and add the network neighbours on the OME6130
network element. This enables the user to view only the desired nodes.

Note 1: The maximum number of Proxy Address Resolution Protocol

(ARP) neighbours in OME6130 is 14.
Note 2: As the OME6130 network element does not support gracious
ARP, in a dual GNE configuration, if one of the GNE goes down, the router
takes about 10 minutes to send the management data through the other
GNE.
Note 3: Ensure that the router ARP timers are set to less than 10 minutes
to limit the DCN outage to 10 minutes.
Configurable Parameters
Refer to Table 5-3 for the configurable parameters of Proxy ARP.
Table 5-3
Configurable Proxy ARP parameters

Parameter Default value Acceptable value

Destination Network IP - Any valid IP address of network

Address element in the same subnet that is
reachable from the Gateway network
element.

Network Interface LAN-1-6(eth0) LAN-1-6(eth0)

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-12 Provisioning DCN

Procedure 5-3 (continued)

Viewing and adding the Proxy ARP neighbours

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Network interface page (step 1).
• Add the Proxy ARP (step 4).

Expected results
• Proxy ARP is successfully added.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
A list is displayed under DCN.
3 Click Proxy ARP Neighbour.
The Proxy ARP Neighbours configuration page is displayed.
4 Click on Add a new Proxy ARP Neighbour link.
The Creating Proxy ARP Neighbour page is displayed.
5 Enter the appropriate values against the fields. Refer to Table 5-3 on
page 5-11 for acceptable values of the parameters.
6 Click Submit.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-13

Procedure 5-4
Deleting the Proxy ARP neighbours

Use this procedure to delete the network neighbours on the OME6130 network
element.

Note: Deleting Proxy Address Resolution Protocol (ARP) Neighbours

will result in loss of communication to the remote network elements in the
network in the absence of static route.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Network interface page (step 1).
• Check on the delete box of the desired Neighbour network IP address (step 4).

Expected results
• Proxy ARP is successfully added.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
A list is displayed under DCN.
3 Click Proxy ARP Neighbour.
The Proxy ARP Neighbours configuration page is displayed.
4 Check on the delete box of the desired Neighbour network IP address.
5 Click Submit.
A confirmation page is displayed.
6 Click Confirm Delete.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-14 Provisioning DCN

Procedure 5-5
Configuring OSPF area

Use this procedure to configure the Open Shortest Path First (OSPF) parameter
on the OME6130 network element.

The OME6130 uses IP for its remote management over both LAN and ECC.
The OSPF protocol is used to route the IP packets.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Configure OSPF Parameters page (step 1).
• Provision the OSPF parameter (step 4).

Expected results
• OSPF parameters are configured.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
3 Click OSPF.
The OSPF parameters configuration page is displayed.
4 Enter the appropriate value against the Area field.
Note: The default OSPF area 0.0.0.1 is the area address of the backbone.
Changing the OSPF area may cause a loss of communication to the network
element.
5 Click Submit.
A success message is displayed upon confirmation.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-15

Procedure 5-6
Disabling OSPF

Use this procedure to disable the Open Shortest Path First parameter on the
OME6130 network element.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Configure OSPF Parameters page (step 1).
• Disable the OSPF parameter (step 5).

Expected results
• OSPF parameters are configured.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
3 Click Network interface.
The Network interface configuration page is displayed.
4 Click on Edit link.
The Network interface provisioning page is displayed.
5 Select Disable option from the drop down list of the OSPF parameter.
6 Click Submit.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-16 Provisioning DCN

Procedure 5-7
Querying or provisioning iISIS parameters

Use this procedure to configure the integrated ISIS parameters on the

OME6130 network element. For details on the configurable parameters, refer
to Table 5-4.

Note 1: The iISIS parameters are displayed on the Network interface level
only when iISIS is enabled on a global level. But iISIS option can be
enabled or disabled at both the Network interface level and the global level.
Note 2: If the default static route is provisioned as 0.0.0.0 from the WUI,
then the iISIS cannot be enabled at the nodal level.
Note 3: If the iISIS is enabled at the nodal level, then default route cannot
be added from the WUI.

Configurable Parameters
Table 5-4
Configurable iISIS parameters

Parameter Default Value Acceptable Value

iISIS Enable Disable • Disable

• Enable

Intermediate System Type L1 Routing -

Manual Area Address1 490000 -

Manual Area Address2 - -

Manual Area Address3 - -

Partition Repair Disable -

Note: The Manual Area Address can be any valid hexadecimal number between 3
to 13 bytes long.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-17

Procedure 5-7 (continued)

Querying or provisioning iISIS parameters

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Edit IISIS-1 page (step 1).
• Configure the iISIS parameters (step 4).

Expected results
• iISIS parameters are configured.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
3 Click iISIS (global iISIS).
The View iISIS page is displayed.
4 Click on Edit.
The Edit IISIS-1 page is displayed.
5 Enter the appropriate values against the Area fields (refer to Table 5-4).
6 Click Submit.
The confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
Note: To view the iISIS parameters on the Network interface level, refer to
Table 5-7 on page 5-25.
8 To configure the iISIS at Network interface level, refer to step 6 on page 5-28.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-18 Provisioning DCN

Procedure 5-8
Provisioning a network interface

Use this procedure to provision embedded communication channel (ECC),

management channel or static GRE tunnel on the OME6130 network element.

This allows you to provision embedded communication channel using any of

the following bytes:

• F1
• F2
• F3
• F2F3
• DCC_M/LDCC
• DCC_R/SDCC
Note: In order to provision a static GRE tunnel, iISIS must be enabled at
the nodal level. Refer to Procedure 5-7, Querying or provisioning iISIS
parameters on page 5-16 for details.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-19

Procedure 5-8 (continued)

Provisioning a network interface

Configurable ECC Parameters

Table 5-5 lists the configurable ECC parameters.
Table 5-5
Configurable ECC parameters

Parameter Default Value Acceptable Value

Port STM1/OC3-1-N-1 • STM1/OC3-1-N-1

• STM1/OC3-1-N-2
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2 (see Note)
where N is the slot number which can
have the value 4, 5, 6, 7, 8 or 9.
For STM-16/OC-48 capacity
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1

ECC Byte Selection ecc_disable • ecc_disable

• ecc_F1
• ecc_F2
• ecc_F3
• ecc_F2F3
• ecc_DCC_R/ecc_SDCC
• ecc_DCC_M/ecc_LDCC

ECC Path - AU-n/STS-n over which ECC is carried.

Note: For a redundant system, only one port is available for provisioning. Hence for
STM4/OC-12, redundant mode, ports STM4/OC12-1-6-2, and STM4/OC12-1-7-2
are not available for provisioning.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-20 Provisioning DCN

Procedure 5-8 (continued)

Provisioning a network interface

Table 5-6 lists the configurable Static GRE Tunnel parameters.

Table 5-6
Configurable Static GRE Tunnel parameters

Parameter Default Value Acceptable Value

Remote Manual Area 490000 (see Note 1)

Address

Remote System ID 000000000000 (see Note 2)

NSAP Selector Byte 2F 2F

Note 1: The Manual Area Address can be any valid hexadecimal number between
3 and 13 bytes.
Note 2: Remote System ID is the valid MAC address of the remote network
element.
Note 3: DCC cannot use the F2/F3 bytes for DCC when an AU is provisioned on
the VC4 as the F2/F3 are not terminated.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Network interface page (step 1).
• Provision the Network interface (step 4).

Expected results
• Embedded communication channel is provisioned.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-21

Procedure 5-8 (continued)

Provisioning a network interface

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
3 Click Network interface.
The Network interface configuration page is displayed.
4 Determine your next step.
If you want to Then go to
provision ECC step 5
provision management step 13
channel
provision Static GRE Tunnel step 19

Provision ECC
5 Click Provision ECC.
The Provision ECC page is displayed.
6 Select from the pull down menu or enter the Port and the ECC byte. For
details, refer to Table 5-5 on page 5-19.
.

CAUTION
Potential loss of communication with the network
element
You may lose communication with the network element if the
ECC byte is set to ecc-disable and you do not have another
route or link to access the network element.

7 Determine your next step.

If Then go to
you have selected F2, F3, or step 8
F2F3
otherwise step 9

8 Provision the desired AU/STS for the ECC Path field.

9 Click Submit.
The Network interface provisioning page is displayed.
Note: A warm restart is required for changes to OSPF router dead interval
and hello interval changes to take place.
10 Select from the pull down menu to make any changes. For details, refer to
Table 5-7 on page 5-25.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-22 Provisioning DCN

Procedure 5-8 (continued)

Provisioning a network interface

Step Action

11 Click Submit.
A confirmatory page is displayed.
12 Click Accept Valid Modifications.
A success message is displayed. The provisioned ECC is displayed in the
Network interface configuration page.
If you want to provision management channel or static GRE tunnel, continue
with step 4. Otherwise, you have completed the procedure.
Provision management channel
13 Click Provision Management Channel-1 or Provision Management
Channel-2.
The Management channel configuration page is displayed.
14 Select the desired values for the parameters from the pull down menu. Refer
to Table 5-8 on page 5-26 for details.
Note: E1 Management channel can only be added to the first port of this
card.
15 Click Submit.
A Network interface provisioning page is displayed.
16 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 5-7 on page 5-25 for details.
17 Click Submit.
18 Click Accept Valid Modifications.
A success message is displayed.
If you want to provision ECC or static GRE tunnel, continue with step 4.
Otherwise, you have completed the procedure.
Note: The selected port parameter should be available before provisioning
the management channel. Based on the availability of the network
termination point, the operation succeeds or fails.
Provision Static GRE Tunnel
19 Click Provision Static GRE Tunnel link.
The Static GRE tunnel configuration page is displayed.
Note: The Provision Static GRE Tunnel link is displayed only when the iISIS
is enabled at the global level.
20 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 5-6 on page 5-20 for details.
21 Click Create.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-23

Procedure 5-8 (continued)

Provisioning a network interface

Step Action

22 Click Yes.
A success message is displayed.
If you want to provision management channel or ECC, continue with step 4.
Otherwise, you have completed the procedure.
Note: IBC will be established only when the same ecc bytes are enabled at
both ends and OSPF/iISIS is enabled at the ecc interface for the gateway.
OSPF/iISIS should be enabled for the corresponding ecc interface at the
remote node.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-24 Provisioning DCN

Procedure 5-9
Querying or editing network interfaces

Use this procedure to view or edit the network interfaces or the management
channel on the network element.

Note 1: An OSI/LAPD interface can be created with OSI as the Layer 3

protocol and LAPD as the Layer2 protocol. Then the default MTU size
created is 512. If the Layer 3 protocol is selected as IP with Layer 2
protocol as Standard PPP, RFC 1661, then the default MTU size is 1518
bytes. The Remote systemID, Remote MAA and Remote NSAP Selector
byte cannot be provisioned while configuring ecc interfaces for OSI/LAPD
links.
Note 2: For provisioning a Network interface to IP, change the Layer3
protocol to IP, the type field to PPP HDLC Framing or Standard PPP,
RFC1661 and the MTU size must be set to 1518. This allows you to edit
the IP parameters like Layer 2 protocol, Magic Number, OSPF, Hello
Interval, and Router Dead Interval.
Note 3: When iISIS is enabled at the nodal level, there is option for ppp
with hdlc framing as a layer 2 protocol at the interface level but the
provisioning will not be successful.
Note 4: Querying or editing of management channel is only possible when
OME6130 network element is in SDH mode.
Note 5: Ensure that the DCC interfaces are not provisioned prior to
configuring a management channel.

CAUTION
Loss of connectivity
Editing a Network interface may cause a loss of connectivity
to the network element.

This procedure allows you to edit the following parameters associated with the
Network interfaces:
• Network interface Short Name (view only)
• Association (view only)
• Layer3 Protocol
• Admin Status
• IP Address (view only)
• MTU
• Layer2 Protocol
• Magic Number

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-25

Procedure 5-9 (continued)

Querying or editing network interfaces

• OSPF Enable
• Hello Interval
• Router Dead Interval
• OSPF Authentication Mode
• OSPF Authentication Password/Key
• iISIS
• L1 Default Metric
• L2 Default Metric
• L2 Routing only

Configurable network interface parameters

Table 5-7 lists the configurable network interface parameters with their default
and acceptable values.
Table 5-7
Configurable network interface parameters

Parameter Default value Acceptable value

Admin Status up • up
• down

Layer 3

Layer 3 Protocol IP • OSI

• IP

MTU 1518 64 to 1600

Layer 2

Layer 2 Protocol Standard PPP, • Standard PPP, RFC 1661

RFC 1661 • PPP, HDLC Framing

Magic number Enable • Enable

• Disable

OSPF

OSPF Disable • Disable

• Enable

Hello Interval 10 1 to FFFF h

Router Dead Interval 40 1 to FFFF h

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-26 Provisioning DCN

Table 5-7 (continued)

Configurable network interface parameters

Parameter Default value Acceptable value

OSPF Authentication Disable • Disable Authentication

Mode Authentication • Simple Password

OSPF Authentication Blank 8 alphanumeric characters

Password/Key

iISIS

iISIS Disable • Disable

(see Note) • Enable

L1 Default Metric 4 -

L2 Default Metric 20 -

L2 Routing Only Disable • Disable

• Enable

Note: The iISIS parameters are displayed only for ECC interfaces when the iISIS is
enabled at the global level.

Table 5-8 lists the configurable management channel parameters with their
default and acceptable values.
Table 5-8
Configurable management channel parameters

Parameter Default value Acceptable value

Management channel type E1 • E1

• VC12

E1 port • E1-1-N-1
where N can take the values
4, 5, 8 or 9.

Port

STM - (In SDH mode) Valid STM

K 1 1-3

L 1 1-7

M 1 1-3

Note: Port information (STM, K, L, M) is only applicable for VC12 management

channel.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-27

Procedure 5-9 (continued)

Querying or editing network interfaces

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View Network interfaces page (step 1).
• Edit the Network interface parameters (step 5).

Expected results
• The Network interface and management channel parameters are edited.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-28 Provisioning DCN

Procedure 5-9 (continued)

Querying or editing network interfaces

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
3 Click Network interfaces.
The View Network interface configuration page is displayed.
4 Click Edit against the Network interface to be edited.
The Network interface provisioning page is displayed.
CAUTION
Loss of connectivity
Editing a Network interface may cause a loss of
connectivity to the network element.

5 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 5-7 for details.
Note: To enable the iISIS protocol at a global level, refer to “Querying or
provisioning iISIS parameters” on page 5-16.
6 The user can now enable or disable the iISIS option at the Network interface
level. For details, refer to Table 5-7.
Note: For a network interface, the user can enable either iISIS or OSPF
protocol, but not both.
7 Click Submit.
A confirmation page is displayed.
8 Click Accept Valid Modifications.
A success message is displayed.
Note 1: If management channel 1 (mgmt1) is successfully edited, a
cross-connect is provisioned between the E1 or the VC12 channel and
MGT-1-2-27. If management channel 2 (mgmt2) is successfully edited, a
cross-connect is created between E1 or the VC12 channel and MGT-1-2-28.
Note 2: The Network interface corresponding to mgmt1 (Management
channel 1) and mgmt2 (Management channel 2) interfaces shall be created.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-29

Procedure 5-10
Deleting a network interface

Use this procedure to delete the network interface.

Note 1: This operation is applicable to all the management channel, ecc

and static GRE interfaces.
Note 2: If any of the network element link goes down, the static route will
be pulled down and will not be seen in the user interface.
Note 3: If a LAPD interface is deleted, while having OSPF configured on
another interface, that results in a OSPF restart and the network element
will be unreachable temporarily for a maximum of 25 seconds.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View Network interface page (step 1).
• Delete the Network interface (step 4).

Expected results
• The Network interface is deleted.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-30 Provisioning DCN

Procedure 5-10 (continued)

Deleting a network interface

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
3 Click Network interface.
The Network interface configuration page is displayed.
4 Click on the delete option of the desired Network interface.
5 Click Submit.
The confirmation page is displayed.
6 Click Confirm Delete to delete the interface.
A success message is displayed.
Note: A network interface cannot be deleted if there is a static route
provisioned on that interface.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-31

Procedure 5-11
Querying or provisioning serial port parameters

Use this procedure to view or provision serial port parameters on the

OME6130 network element.

Note 1: In the serial port provisioning, the Application and the Admin
status fields cannot be changed simultaneously. First application and the
corresponding parameter has to be selected. For the application to come
into effect the admin status of the serial port must be set to up.
Note 2: If F1-UDC needs to be used for serial port application, then F1
byte cannot be used for ECC byte communication.
This procedure allows you to edit the following parameters associated with a
serial port:

• Application
• Baud Rate
• Admin Status
CAUTION
Risk of loss of association
Changing the serial port settings may cause a loss of
association to a network element connected via modem or F1
user byte. Ensure that alternate comms is provisioned before
changing the provisioning for the serial port.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-32 Provisioning DCN

Procedure 5-11 (continued)

Querying or provisioning serial port parameters

Configurable parameters
Table 5-9 lists the configurable serial port parameters with their default and
acceptable values.
Table 5-9
Configurable serial port parameters

Parameter Default value Acceptable value

Application Unprovision Application • Unprovision Application

• ppp
• udc

Baud Rate 9600 • 9600

• 19200
• 38400
• 57600
• Not applicable

Admin Status If_admin_down • If_admin_up

• If_admin_down

For PPP application user needs to set the following PPP parameters:
• IP address
• Max Receive unit
• Max transmit unit
Table 5-10 lists the configurable PPP (Point-to-Point Protocol) application
parameters with default and acceptable values.
Table 5-10
Configurable PPP parameters
Parameter Default value Acceptable value

IP Address IP address of the network User can configure any IP address

element

Max Receive unit 1500 128 -1500

Max Transmit unit 1280 1280 - 1500

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-33

Procedure 5-11 (continued)

Querying or provisioning serial port parameters

For UDC application user needs to set the following UDC parameters:
• Overhead byte
• STM Port
Table 5-11 lists the configurable UDC parameters with acceptable and default
values.
Table 5-11
Configurable UDC parameters

Parameter Default value Acceptable value

Overhead byte F1 F1
F2

STM Port STM1-1-N-1/OC3-1-3-1 • STM1/OC3-1-N-1

• STM1/OC3-1-N-2
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2 (see Note 2)
where N is the slot number which
can have the value 4, 5, 6, 7, 8 or
9.
For STM-16/OC-48 capacity
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1

AUG AUG/STS3-1-6-1-1 • AUG/STS3-1-6-1-1/

• AUG/STS3-1-6-1-2
• AUG/STS3-1-6-1-3
• AUG/STS3-1-6-1-4 (see Note 3)
For STM-16/OC-48 Capacity
AUG/STS3-1-6-1-1 to
AUG/STS3-1-6-1-16

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-34 Provisioning DCN

Table 5-11 (continued)

Configurable UDC parameters

Parameter Default value Acceptable value

AU AUG/STS3-1-6-1-1-1 • AUG/STS3-1-6-1-1-1
• AUG/STS3-1-6-1-2-1
• AUG-/STS31-6-1-3-1
• AUG-/STS31-6-1-4-1
• AUG/STS3-6-1-3-1
• AUG/STS3-1-6-1-4-1 (see Note
3)
For STM-16/OC-48 Capacity
AUG/STS3-1-6-1-1 to
AUG/STS3-1-6-1-16

Note 1: The AUG and AU fields are editable only if the F2 byte is selected for the
Overhead byte.
Note 2: For a redundant system, only one port is available for provisioning. Hence
for STM4/OC12, redundant mode, ports STM4/OC12-1-6-2, and STM4/OC12-1-7-2
are not available for provisioning.
Note 3: AUG/STS3-1-6-1-2-1, AUG/STS3-1-6-1-3-1, AUG/STS3-1-6-1-4-1 are
available only if the network element is working with STM4 capacity.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-35

Procedure 5-11 (continued)

Querying or provisioning serial port parameters

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the View Serial Port page (step 1).
• Provision the desired parameters in the Provision Serial Port page (step 5).

Expected results
• The serial port parameters are successfully provisioned.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-36 Provisioning DCN

Procedure 5-11 (continued)

Querying or provisioning serial port parameters

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click DCN.
3 Click Serial port.
The Serial port configuration page is displayed. The details regarding the
serial ports are displayed.
Note 1: Check that the ECC byte for IBC is not set as F1 on the same
STM-1/4/OC-3/12 port or STM-16/OC-48 port used for UDC application.
Note 2: F1 User Data Channel is not supported originating from the 2x155M
circuit pack.
If you want to provision the serial port parameters, then continue with step 4.
Otherwise you have completed the procedure.
4 Click edit against the appropriate port.
The corresponding Serial port configuration page is displayed.
5 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 5-9 on page 5-32 and Table 5-10 on page 5-32 for
details.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
8 Again click edit against the same port.
the corresponding configuration serial port page is displayed.
9 Set admin status to up and click submit.
A confirmation message is displayed.
10 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-37

Procedure 5-12
Querying status of overhead tunnel

Use this procedure to view the overhead tunnel provisioned on the OME6130
network element.

Note: If the ECC_bytes are enabled on the STM-1/4/OC-3/12 and

STM-16/OC-48 port, the corresponding bytes cannot be used for
tunneling.

This procedure allows you to view the following parameters associated with an
overhead tunnel:
• Tunnel Name
• Source Port
• Destination Port
• Overhead Byte

Before you start

• Log into the network element user interface with the appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Configure overhead tunnels page (step 1).

Expected results
• The details of the overhead tunnel provisioned on the network element are displayed.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Overhead tunnel.
The Configure overhead tunnels page is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-38 Provisioning DCN

Procedure 5-13
Creating an overhead tunnel

Use this procedure to create an overhead tunnel on the OME6130 network

element.

Note: You must ensure that STM-1/4/OC-3/12 or STM-16/OC-48 is not

already provisioned for ECC channel on the required overhead byte, before
creating overhead tunnel.

Configurable overhead tunnel parameters

Table 5-12 lists the configurable overhead tunnel parameters with their default
and acceptable values.
Table 5-12
Configurable overhead tunnel parameters

Parameter Default value Acceptable value

Source Port Name STM1/OC3-1-N-1 • STM1/OC3-1-N-1

• STM1/OC3-1-N-2
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2 (see Note)
where N is the slot number
which can have the value 4, 5,
6, 7, 8 or 9.
For STM-16/OC-48 capacity
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1

Destination Port STM1/OC3-1-N-1 • STM1/OC3-1-N-1

Name • STM1/OC3-1-N-2
• STM4/OC12-1-6-1
• STM4/OC12-1-6-2
• STM4/OC12-1-7-1
• STM4/OC12-1-7-2 (see Note)
where N is the slot number
which can have the value 4, 5,
6, 7, 8 or 9.
For STM-16/OC-48 capacity
• STM16/OC48-1-6-1
• STM16/OC48-1-7-1

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-39

Table 5-12 (continued)

Configurable overhead tunnel parameters

Parameter Default value Acceptable value

Overhead Byte E1 • E1
• E2
• F1
• DCC_R/SDCC
• DCC_M/LDCC

Note: For a redundant system, only one port is available for provisioning. Hence for
STM-4/OC-12 redundant mode, ports STM4/OC12-1-6-2 and STM4/OC12-1-7-2
are not available for provisioning.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Create overhead tunnel page (step 1).
• Configure desired values for the parameters in the Add overhead tunnel page (step 4).

Expected results
• An overhead tunnel is created on the network element.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-40 Provisioning DCN

Procedure 5-13 (continued)

Creating an overhead tunnel

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Overhead tunnel.
The Configure overhead tunnels page is displayed. The details regarding the
Overhead tunnels are displayed.
3 Click Create Overhead tunnel.
The Add Overhead tunnel page is displayed.
4 Select the appropriate values against the fields. Refer to Table 5-12 on
page 5-38 for details.
5 Click Submit.
A confirmation page is displayed.
6 Click Yes.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Provisioning DCN 5-41

Procedure 5-14
Deleting an overhead tunnel

Use this procedure to delete an Overhead tunnel created on the OME6130

network element.

CAUTION
Risk of communication failure
Deletion of overhead tunnel may cause a loss of
communication.

Before you start

• Log into the network element user interface with the appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Configure overhead tunnels page (step 1).
• Delete the desired overhead tunnel (step 3).

Expected results
• The desired overhead tunnel is deleted.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click Overhead tunnel.
The Configure Overhead tunnels page is displayed. The details regarding the
Overhead Tunnels are displayed.
3 Check the delete check box for the Overhead tunnel to be deleted.
4 Click Submit.
A confirmation page is displayed.
5 Click Confirm Delete.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
5-42 Provisioning DCN

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
6-1

Equipment provisioning 6-

This chapter contains procedures for provisioning and operating the OME6130
network element, which includes configuring:
• the network element data
• the time settings
• the circuit packs
The OME6130 has 3 types of aggregate card:

• Aggregate card 1x155/622MAgg which can be used when the system is

configured in the STM-1/OC-3 or STM-4/OC-12 redundant mode.
• Aggregate card 2x155/622M which can be used when the system is
configured in STM-1/OC-3 or STM-4/OC-12 non-redundant mode.
• Aggregate card 1x2G5 which can be used when the system is configured
in STM-16/OC-48 redundant mode.
The three aggregate cards are described as follows:

• A circuit pack with two STM-1/4/OC-3/12 ports, cross-connect fabric,

timing/synchronization and control processor subsystems. This is intended
for the non-redundant equipment application used as STM-1/4/OC-3/12
ADM or 1+1 protected or unprotected terminal multiplexer.
• A circuit pack with one STM1/4/OC-3/12 port, cross-connect fabric, and
timing/synchronization and control processor subsystems. This is intended
for redundant equipment protection application using two circuit packs
providing redundant cross-connect fabric, timing/synchronization
subsystem and control processor complex. The aggregate ports being on
different circuit packs also provide equipment redundancy of the facility
(aggregate ports).
• The 1x2G5Agg circuit pack only has one port variant and hence an
STM-16/OC-48 ADM or protected TMUX would have equipment
redundancy.
Note: Operating the system with 155/622MAgg and 1x2G5Agg card is
not a valid combination.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-2 Equipment provisioning

The OME6130 network element supports:

• 28xE1DS1 circuit pack, which provides 28 E1 interfaces.
• 28xE1DS1 circuit pack, which provides 28 DS1 interfaces.
• 3xE3DS3 circuit pack, which provides 3 E3 interfaces.
• 3xE3DS3 circuit pack, which provides 3 DS3 interfaces.
• PSU which is the power supply unit of the OME6130 network element.
• OAM circuit pack, which provides interfaces to
— Modem/F1
— External synchronisation interface
— Alarm In
— Alarm Out
— Craft
— LAN
• 2x155/622M which is the processor of the OME6130. The 2x155/622M
processes the requests sent to the network element. This functions as a
cross-connect circuit pack and supports two optical STM-1/4/OC-3/12
interfaces with Non-redundant mode.
• 1x155/622MAgg which is the processor of the OME6130. The
1x155/622MAgg processes the requests sent to the network element. This
functions as a cross-connect circuit pack and supports one optical
STM-1/4/OC-3/12 interfaces with redundant mode.
• 1x2G5Agg which is the processor of the OME6130. The 1x2G5Agg
processes the requests sent to the network element. This functions as a
cross-connect circuit pack and supports one optical STM-16/OC-48
interfaces with redundant mode.
• 2x155M circuit pack, which provides two optical STM-1/OC-3 interfaces
to be used as tributary service interfaces.
• 2xGE supports 2 Gig Ethernet port with 622M worth of uplink WAN
mapping capability. Also supports VCAT/LCAS based L1 point-to-point
transport capability. It supports
— 2xGE
— 2 Gig Ethernet port with 622M worth of uplink WAN mapping
capability
— VCAT/LCAS based L1 point to point transport capability
• 8xETH which is the 10/100BaseT Ethernet Private Line circuit pack of
OME6130. 8xETH circuit pack provides line interfaces to eight 10/100
Mbps Ethernet interfaces.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-3

• 4x10/100BT + 4x100FX L1 circuit pack which provides four 10/100 BT

Ethernet interfaces and four Fast Ethernet interfaces.
• 2xGE/FX + 8x10/100BT L2 622M circuit pack is the Layer 2 Packet
Aggregation circuit pack. This circuit pack will support 2 optical ports
which can be configured for GE or Fast Ethernet interfaces, as well as 8
10/100BT Ethernet interfaces. This circuit pack supports Layer 2
switching capabilities.
• FAN module.
1+1 equipment protection is provided for the aggregate cards. Aggregate card
will automatically switch if a hardware failure is encountered for the primary
card. Once any card becomes a primary, it remains primary unless a cold reset
or forced switch is applied to the primary card. The user can initiate aggregate
card switching by issuing a forced switch command.

The date and time settings include setting the date and time of the network
element. The time zone settings enable you to set the appropriate time zone
relevant to the location of the network element.

Chapter procedure list

Table 6-1 lists the procedures that are described in this chapter.

Table 6-1
Chapter procedure list

Action Details

Querying network element data Procedure 6-1

Editing network element data Procedure 6-2

Editing the time settings for the network element Procedure 6-3

Querying circuit packs Procedure 6-4

Deleting a circuit pack Procedure 6-5

Editing the alarm and performance monitoring mode Procedure 6-6

Provisioning E1/T1 ports Procedure 6-7

Provisioning E3/DS3 ports Procedure 6-8

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-4 Equipment provisioning

Procedure 6-1
Querying network element data

Use this procedure to view basic data on the OME6130 network element. This
procedure allows you to view the following basic network element parameters:
• Name
• Node Configuration (view only)
• Node Product Code (view only)
• AU Mode (view only)
• Router ID
• Ethernet IP
• Contact
• Location
• Software Version (view only)
• SDH/SONET Mode (view only)
• Node Capability
• Node Redundancy Mode (view only)

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the NE information page (step 1).

Expected results
• The basic network element data is presented.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-5

Procedure 6-1 (continued)

Querying network element data

Step Action

1 Click NE information in Navigation menu.

The NE information page is displayed.
Note: The basic network element data is displayed in the Input/Output area
of the Node Manager.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-6 Equipment provisioning

Procedure 6-2
Editing network element data

Use this procedure to edit the network element data on the OME6130 network
element.

Configurable network element parameters

Table 6-2 lists the editable network element parameters, their default values
and acceptable values.
Table 6-2
Configurable network element parameters

Parameter Default value Acceptable value

Name Default 0-20 character string

(see Note)

Router ID 192.168.1.254 xxx.xxx.xxx.xxx

Ethernet IP 192.168.1.254/24 xxx.xxx.xxx.xxx

Contact - 0-255 character string

(see Note)

Location - 0-255 character string

(see Note)

Note: The character string can include all alphanumeric and special characters.
However, it is recommended not to use the ‘&’ character in the Name field to avoid
XML parsing error.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-7

Procedure 6-2 (continued)

Editing network element data

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the NE information page (step 1).
• Edit the basic network element data (step 2).

Expected results
• The basic network element parameters are edited.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click NE information in Navigation menu.

The NE information page is displayed.
2 Enter the appropriate values against the relevant fields. Refer to Table 6-2 on
page 6-6.
3 Click Submit.
A confirmation page is displayed.
4 Click Accept Valid Modifications.
A success message is displayed.

CAUTION
Network element reboot
Editing the Router Id and the Ethernet IP of the network
element initiates a warm restart without affecting the
commissioned traffic. Connectivity to the network
element is lost for five minutes during the warm restart.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-8 Equipment provisioning

Procedure 6-3
Editing the time settings for the network element

Use this procedure to edit the date, time, time zone and time server settings of
the OME6130 network element.

Note: Up to five time servers can be provisioned on the network element

to synchronize.

Configurable time settings parameters

Table 6-3 lists the editable date and time settings parameters of the OME6130
network element.
Table 6-3
Configurable time settings parameters

Parameter Default value Acceptable value

Date and Time Current date and time, valid date and time in the following
relevant to the configured format:
time zone. • Month—January to December
• Date—1 to 31
• Year—2001 to 2036
• Hour—00 to 23
• Minutes—00 to 59
• Seconds—00 to 59

Table 6-4 lists the editable other time zone setting parameters of the OME6130
network element.
Table 6-4
Configurable Other time zone parameters

Parameter Default value Acceptable value

Zone America, NewYork Any time zone available in the time

zones list.

Offset Hours -5 -12 to 11

Offset Minutes 30 0 to 59

Daylight saving Disable • Enable

• Disable

DST String - The time zone string during DST

period (see Note 2).

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-9

Table 6-4 (continued)

Configurable Other time zone parameters

Parameter Default value Acceptable value

DST Start Valid date and time in the following

(Month: Week: format:
Day: Hour: • Month—January to December
Minute) • Week—1st Week to 4rth Week, Last
week
• Day—Sunday to Saturday
• Hour—0 to 23
• Minutes—0 to 59
(see Note 2)

DST Stop Valid date and time in the following

(Month: Week: format:
Day: Hour: • Month—January to December
Minute) • Week—1st Week to 4rth Week, Last
week
• Day—Sunday to Saturday
• Hour—0 to 23
• Minutes—0 to 59
(see Note 2)

Note 1: By default the DST will be set to its default value, the DST start and stop
time are displayed only when DST is set to Enable.
Note 2: The DST String, DST Start and DST Stop parameters can be provisioned
only if Daylight savings is enabled.

Table 6-5 lists the DST start and DST end time for various time zones for the
year 2007.
Table 6-5
DST start and end time for the year 2007

Time Zone DST Start DST End

Eastern Standard Time March 11 at 02:00:00 November 4 at 02:00:00

Central Standard Time March 11 at 02:00:00 November 4 at 02:00:00

Mountain Standard Time March 11 at 02:00:00 November 4 at 02:00:00

Pacific Standard Time March 11 at 02:00:00 November 4 at 02:00:00

Atlantic Standard Time March 11 at 02:00:00 November 4 at 02:00:00

Hawaiian Standard Time Not applicable Not applicable

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-10 Equipment provisioning

Table 6-5 (continued)

DST start and end time for the year 2007

Time Zone DST Start DST End

Greenwitch Mean Time Not applicable Not applicable

Indian Standard Time Not applicable Not applicable

Chile Summer Time October 14 at 00:00:00 March 11 at 00:00:00 (DST

(DST will end in March started in October 2006)
2008)

Easter Island October 13 at 22:00:00 March 10 at 22:00:00 (DST

SummerTime (DST will end in March started in October 2006)
2008)

Australian Eastern October 28 at 02:00:00 March 25 at 03:00:00 (DST

Standard Time (DST will end in March started in October 2006)
2008)

Central Australian October 28 at 02:00:00 March 25 at 03:00:00 (DST

Standard Time (DST will end in March started in October 2006)
2008)

Western Australian October 28 at 02:00:00 March 25 at 03:00:00 (DST

Standard Time (DST will end in March started in October 2006)
2008)

Korean Standard Time Not applicable Not applicable

Table 6-6 lists the editable time server setting parameters of the OME6130
network element.
Table 6-6
Configurable time server settings

Parameter Default value Acceptable value

NTP client Enabled Disable • Enable

• Disable

NTP Server-0 - IP address of the first server

NTP Server-1 - IP address of the second server

NTP Server-2 - IP address of the third server

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-11

Table 6-6 (continued)

Configurable time server settings

Parameter Default value Acceptable value

NTP Server-3 - IP address of the fourth server

NTP Server-4 - IP address of the fifth server

Synchronization interval 1024 seconds • 16

• 32
• 64
• 128
• 256
• 512
• 1024
• 2048
• 4096
• 8192
• 16384

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-12 Equipment provisioning

Procedure 6-3 (continued)

Editing the time settings for the network element

Note 1: If OMEA is used to manage the OME6130 network element, the

first NTP server (NTP Server-0) is automatically provisioned. All other
timing servers are provisioned against the remaining NTP servers.
Note 2: The timing server nominated must have stratum level of 14 or less
than 14. The network element will not synchronize if the stratum level is
out of range.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Set Node Time page (step 3).
• Edit the network element date and time (step 4).
• Reach the Set Time Zone page (step 6).
• Set the desired time zone or define an offset from the GMT (step 7).
• Reach the Set Time Server page (step 12).
• Set the IP of the timing server for the network element (step 13).

Expected results
• The time settings of the network element are edited.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-13

Procedure 6-3 (continued)

Editing the time settings for the network element

Action
Step Action

1 Click System Time in Navigation menu.

2 Determine your next step.
If you want to edit the Then go to
network element date and time step 3
Time Zone settings step 6
Time Server settings step 12

3 Click Set time.

The Set Node Time page is displayed.
4 Select the appropriate node date and time. For details, refer to Table 6-3 on
page 6-8.
5 Click Submit.
A success message is displayed.
If you want to edit other time setting of the network element go to step 2.
Otherwise, you have completed this procedure.
6 Click Set time zone.
The Set Time Zone page is displayed.
7 Select the desired time zone or define an offset form the GMT.
If you want Then
select the desired time zone select the desired time zone from the
pull-down menu of the Zone field. Go
to step 10.
define an offset from the GMT select Other Time Zone. Go to
step 8.

8 Click Submit.
The Other Time Zone page is displayed.
9 Enter the appropriate values against the other time zones fields. Refer to
Table 6-4 on page 6-8 for details.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-14 Equipment provisioning

Procedure 6-3 (continued)

Editing the time settings for the network element

Step Action

10 Click Submit.
A success message is displayed.
11 If you want to edit other time settings, go to step 2, otherwise you have
completed this procedure.
CAUTION
Node restart
Changing the time zone of an network element requires
a warm restart of the network element for the changes
to take effect.

12 Click Set time server.

The Set Time Server page is displayed.
13 Enter the IP address of the network element or the timing server to which the
network element is to be referenced against the NTP Server-x field,
where
x identifies the priority assigned to the servers
referenced, 0 being the highest priority.

Note 1: The IP address referenced must be reachable by the network

element.
Note 2: If OMEA is used to manage the OME6130 network element, the first
NTP servers (NTP Server-0) is automatically provisioned. Provision all other
time servers against remaining NTP servers.
14 Enter the appropriate values against the fields. Refer to Table 6-6 on
page 6-10 for details.
15 Click Submit.
A success message is displayed.
16 If you want to edit other time setting of the network element go to step 2,
otherwise you have completed this procedure.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-15

Procedure 6-4
Querying circuit packs

Use this procedure to retrieve the node inventory or to view the details
associated with a particular circuit pack or module.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Node Inventory page (step 1).
• Select the desired circuit pack to view the details (step 2).

Expected results
• The details associated with the selected circuit pack is displayed in the input/output area.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Inventory in the Navigation menu.

2 Click Node inventory.
The Node inventory page is displayed.The circuit pack population details
along with the status of each of them is displayed.
Note: Querying or editing the circuit packs can be done in the Node slot view
area.
3 To view the desired circuit, you need to click on that particular slot.
The Corresponding circuit pack page is displayed.
Note: The Node Inventory page displays the SFPs inserted in the network
element.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-16 Equipment provisioning

Procedure 6-5
Deleting a circuit pack

Use this procedure to delete the configuration details of circuit packs that are
removed from the network element.

The network element retains the configuration details of circuit packs even
after they are removed from the equipment shelf. In such cases, the Node
Inventory page reflects the Oper Status as Down and the Is present field as
Not present for the relevant circuit packs.

Note 1: In order to delete the equipment entity of a circuit pack, the circuit
pack must first be physically removed from the OME6130 network
element.
Note 2: Before deleting the circuit pack, ensure you delete cross-connects
provisioned on ports of the circuit pack. For more information, refer to
Bandwidth data services guide, 323-1855-320.
Note 3: Before deleting the circuit pack, ensure you delete nominated
timing references which are sourced by ports on the circuit pack. For more
information, refer to Procedure 4-5, Deleting external synchronization
sources.
Note 4: Before deleting the circuit pack, ensure you disable any DCC
channels provisioned on facilities of the circuit pack. For more
information, refer to appropriate procedures in Provisioning interfaces or
Provisioning DCN chapters.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-17

Procedure 6-5 (continued)

Deleting a circuit pack

Before you start

• Log into the network element user interface at the default view level.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
• Ensure you physically remove the circuit pack before deleting the equipment. Refer to Trouble Clearing and
Module Replacement Procedures, 323-1855-543 for more details.
• In order to delete the circuit pack, you have to delete any provisioning that is set for ports on that circuit pack,
such as cross-connects, port timing from a facility on the circuit pack, DCC using one the facilities on the
circuit pack.

Procedure tasks
• Reach the Node inventory page (step 1).
• Delete the desired circuit pack (step 3).

Expected results
• The circuit pack is deleted.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Inventory in the Navigation menu.

2 Click Node inventory.
The Node inventory page is displayed.
3 Click Delete Cards.
The View/Delete Cards page is displayed.
A list of circuit packs whose configuration details are retained after the circuit
packs are removed is displayed.
4 Select the circuit packs that are to be deleted against the Delete field.
5 Click Submit.
A success message is displayed.
Note 1: Only circuit packs that are physically removed from the chassis will
be listed in the “Delete cards” page.
Note 2: For the network element to recognize a circuit pack in a particular
slot, you must delete any pre-existing circuit pack configuration on that slot.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-18 Equipment provisioning

Procedure 6-6
Editing the alarm and performance monitoring mode

Use this procedure to edit the alarm and performance monitoring mode of the
28xE1DS1 circuit pack.

For 3xE3DS3 circuit pack, both alarm and performance monitoring is enabled
by default.

Configurable alarm and performance monitoring mode parameters

Table 6-7 lists the editable date and time settings parameters of the OME6130
network element.
Table 6-7
Configurable alarm and performance monitoring mode parameters

Parameter Default value Acceptable value

PDH Path No Monitoring • No Monitoring

Monitoring • Alarm Monitoring
Option
• Alarm And Performance Monitoring

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Alarm and Performance Monitoring Mode page (step 1).
• Select the desired PDH path monitoring mode (step 5).

Expected results
• The desired PDH path monitoring mode is selected.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-19

Procedure 6-6 (continued)

Editing the alarm and performance monitoring mode

Action
Step Action

1 Click Inventory in the Navigation menu.

2 Click SHELF-1.
3 Click 28xE1DS1.
The Corresponding E1/T1 Tributary card page is displayed.
4 Click on Select Alarm and Performance Monitoring Mode for Ports.
The Alarm and Performance Monitoring Mode page is displayed.
For details on performance monitoring and alarms, refer to Trouble Clearing
and Module Replacement Procedures, 323-1855-543.
Note: Alarm and Performance monitoring mode can be enabled only when
framing mode for the port is chosen.
5 Select the desired value against the PDH Path Monitoring Option field. For
details, refer to Table 6-7 on page 6-18.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-20 Equipment provisioning

Procedure 6-7
Provisioning E1/T1 ports

Use this procedure to configure the 28xE1/DS1 circuit pack to provide only E1
interfaces or only DS1 (T1) interfaces.

Note 1: The same circuit pack cannot simultaneously provide both E1

interfaces and DS1 interfaces.
Note 2: If an E1/DS1 port is part of cross-connect or a nominated timing
source or has a loop back active, the change of circuit pack type (E1 to DS1
and vice versa) is denied. However, any port specific parameter (like admin
up/down, or LBO enable/disable) does not prevent the change from one
type to another.
Note 3: To delete the circuit pack and for changing the configuration from
E1 to DS1 or vice-versa, you need to delete all the provisioned
cross-connects and IBCs on it.
t.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the E1/T1 ports configuration page (step 1).
• Select the desired port configuration (step 5).

Expected results
• The desired port is configured on the circuit pack.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-21

Procedure 6-7 (continued)

Provisioning E1/T1 ports

Action
Step Action

1 Click Inventory in the Navigation menu.

2 Click SHELF-1.
3 Click 28xE1DS1.
The E1/T1 Tributary card page is displayed.
4 Click Configure E1/T1 mode.
The T1/E1 ports configuration page is displayed.
5 Select E1/DS1 from the pull down menu for the Port configuration menu.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
Note: Wait approximately 1 minute for the proper provisioning changes to
take effect. A refresh of the WUI session may be required in order to get an
updated view of the facilities.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-22 Equipment provisioning

Procedure 6-8
Provisioning E3/DS3 ports

Use this procedure to configure the ports on the 3xE3/DS3 circuit pack
independently to behave as E3 or DS3 interfaces.

If an E3/DS3 port is part of cross-connect or has a loop back active, the change
of circuit pack type (E3 to DS3 and vice versa) is denied. However, any port
specific parameter (like admin up/down) does not prevent the change from one
type to another.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the E3/DS3 ports configuration page (step 1).
• Select the desired port configuration (step 5).

Expected results
• The desired port is configured on the circuit pack.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Equipment provisioning 6-23

Procedure 6-8 (continued)

Provisioning E3/DS3 ports

Action
Step Action

1 Click Inventory in the Navigation menu.

2 Click SHELF-1.
3 Click 3xE3DS3.
The E3/DS3 Tributary card page is displayed.
4 Click Configure E3/DS3 port.
The E3/DS3 ports configuration page is displayed.
5 Select E3 or DS3 from the pull-down menu for the Port Configuration field.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A confirmation page is displayed.
Note: Wait approximately 1 minute for the proper provisioning changes to
take effect. A refresh of the WUI session may be required in order to get an
updated view of the facilities.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
6-24 Equipment provisioning

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 323-1855-310
7-1

Maintenance operations 7-

This chapter contains procedures for maintenance operations that can be

performed on the OME6130 network element.

Loopbacks
Loopback enables you to carry out maintenance operation to detect the exact
location of failure. You can perform facility and terminal loopbacks to test the
electrical (E1/DS1/E3/DS3) and optical (STM-1/4/OC-3/12 ports) or
(STM-16/OC-48 ports) connectivity of the OME6130 network element. When
a facility loopback is operated on E1/DS1 and optical ports, AIS is sent
downstream.

Facility loopback tests traffic connections to and from E1/DS1/E3/DS3 port

connections on the OME6130 and are generally performed on site. Facility
loopback can be configured on STM-1/4/OC-3/12 interfaces on
1x155/622MAgg card or STM-16/OC-48 interface on 1x2G5Agg card.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-2 Maintenance operations

Figure 7-1 shows an example of facility loopback that tests the

E1/DS1/E3/DS3 port connections to and from 2x155/622M cards at network
elements 1 and 2. The same concept is applicable to all other aggregate cards.
Figure 7-1
Facility Loopback

OME6130
OME6130
network element
network element
1
2
2x155/
622M
2x155/
Test set 1 622M
Test Set 2
E1
E1
STM-1 STM-1
Interface E1
Interface
E1

Terminal loopback tests the E1/DS1/E3/DS3 and STM-1/4/OC-3/12 port or

STM-16/OC-48 port connections. Terminal loopback is supported on the
Ethernet interfaces, but AIS is not sent downstream. Terminal loopback can be
configured on STM-1/4/OC-3/12 interfaces on 1x155/622MAgg card or
STM-16/OC-48 interface on 1x2G5Agg card.

Figure 7-2 shows an example of terminal loopback that tests a E1/DS1/E3/DS3

connection to and from the 2x155/622M modules. The same concept is
applicable to all other aggregate cards. You must connect the test equipment to
the E1/DS1/E3/DS3 ports on the OME6130 and operate a facility loopback on
the aggregate card.
Figure 7-2
Terminal Loopback

OME6130
OME6130
network element
network element
1
2

2x155/
622M 2x155/
Test Set 1 622M
E1 E1
Interface STM-1/4 STM-1/4 E1
Interface
E1

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-3

When loopback testing is completed and the loopback operation is released,

the loopback information is cleared from the aggregate circuit pack.
CAUTION
Traffic affecting process
Facility loopback and terminal loopback are traffic
affecting.

CAUTION
Traffic affecting process
Application of facility or terminal loopback on the near
end port (with respect to OMEA server) of a remotely
managed node will result in loss of connectivity with
the node and the downstream network. Hence, while
applying loopbacks, the node should be provided with
IBC protection or should have a personal placed at the
site of the node to avoid loss of connectivity.

Figure 7-3 shows the connectivity of the nodes to the OMEA server. Facility
or terminal loopbacks can be created at the near end ports of Node A without
loss of connectivity due to presence of Ethernet connectivity. But, provisioning
loopbacks at the near end ports of Node B and Node C will lead to loss of
connectivity in the downstream network. Provisioning loopbacks at the far end
elements will not affect connectivity.
Figure 7-3
Terminal Loopback

Node A Node B Node C

OMEA Near Far Near Far Near Far

end end
Server Ethernet end end end end
Connectivity

Remotely
Downstream Network Managed Nodes

Maintenance operations include the following:

• loopback operations on ports
• diagnostic operations

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-4 Maintenance operations

Diagnostics
In OME6130, the user has the facility to view the system diagnostics, the
OSPF related information and the routing information. This is available in the
Diagnostics menu in the user interface.

There are three options available, they are:

• OSPF monitor
• Systems Diagnostics
• iISIS monitor
SNMP traps
Simple Network Management Protocol (SNMP) is a set of protocols for
managing complex networks. SNMP is an application-layer protocol that
allows network devices to exchange management information. SNMP allows
network administrator to find and interpret network problems and plan
network growth. The OME6130 uses SNMP to provide asynchronous event
notification to a network management system (NMS). SNMP trap is an SNMP
application that uses the SNMP trap operation to send information to a network
manager. Traps are sent when errors or specific events occur on the network.

Configuration management
The OME6130 network element supports configuration backup and FTP it to
the selected server.

Backup configuration can be used for saving the configuration from the
network element. This command copies the existing snapshot of the
configuration and FTPs it to the server mentioned. In case of failure, a backup
operation failure alarm is raised.

Restore configuration can be used for restoring the configuration to the

network element. This command obtains the configuration, through FTP from
a remote server, performs checks and accepts the configuration if applicable to
the network element. In case of failure, a restore failure alarm is raised.

Restoring the configuration can be done by either restoring from remote

machine via FTP, or from the local machine using HTTP.

The OME6130 network element gives an explicit error message for the cause
of the failure. The messages may be for one of the following reasons:
• The username, password authentication failure
• Unable to reach the server IP address.
• Incorrect permissions to transfer the file.
The OME6130 network element can recover from restoration operation
failures due to network availability by using FTP timeout of 15 seconds.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-5

The OME6130 network element verifies the validity of the restored

configuration. The activation of restored configuration shall be non-service
affecting for the unaffected configuration. If the verification fails, the restored
configuration is rejected and configuration restore failure alarm is raised.

The OME6130 network element raises an alarm on detection of a

configuration corruption or a version mismatch but this does not affect traffic.

Note: It is recommended to perform a network element database backup

on a daily basis.

Upgrade operation
The OME6130 allows software, firmware, and documentation download. The
network element allows users with ADMIN privileges to perform software and
firmware download operations.

The software download is based on FTP. The network element initiates the
download through an FTP client from an FTP server. However, the network
element can run the FTP server thereby enabling a host workstation without
FTP server to achieve the upgrade. The software download and activation is
non-service affecting. During the software download operation all other
functionality of the network element remains unaffected.

A firmware upgrade involves the upgrade of boot loader and operating system.
The firmware bundle is checked for checksum and the version. The firmware
download is non-service affecting and requires a warm restart to take effect.

During a documentation upgrade, the documentation bundle is checked for

checksum and the version.

Note: For details on the supported upgrade CAP procedures, refer to

Planning Guide, NT6Q92MB.

Chapter procedure list

Table 7-1 lists the procedures that are described in this chapter.
Table 7-1
Chapter procedure list

Action Details

Provisioning loopback on STM/OCn ports Procedure 7-1

Provisioning loopback on PDH/DSn ports Procedure 7-2

Provisioning loopback on Ethernet ports Procedure 7-3

Backing up the network element configuration data Procedure 7-4

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-6 Maintenance operations

Table 7-1
Chapter procedure list

Action Details

Restoring the network element configuration data Procedure 7-5

Restoring the factory defaults Procedure 7-6

Provisioning system settings Procedure 7-7

Provisioning SNMP trap destination IP addresses Procedure 7-8

Viewing the diagnostics information Procedure 7-9

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-7

Procedure 7-1
Provisioning loopback on STM/OCn ports

Use this procedure to issue a loopback on the STM/OCn ports provisioned on

the OME6130 network element.

This procedure allows you to provide:

• Normal Operation
• Facility Loopback
• Terminal Loopback
Note: Loopback is a traffic affecting operation.

Configurable loopback parameters

Table 7-2 lists the configurable loopback mode parameters with their default
and acceptable values.
Table 7-2
Configurable loopback parameters

Parameter Default value Acceptable value

LoopBack Mode Normal • Normal Operation

Operation • Facility LoopBack
• Terminal LoopBack

Note: A downstream alarm indication signal (AIS) is not transmitted for

the facility loopback.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-8 Maintenance operations

Procedure 7-1 (continued)

Provisioning loopback on STM/OCn ports

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the corresponding loopback page (step 1).
• Configure the desired loopback mode for the port (step 4).

Expected results
• An alarm is raised indicating that a loopback mode is configured on the corresponding port.
• The port remains out of service until the loopback mode is configured to normal operation.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click Loop-Backs.
3 Click STM/OCn.
The STM/OCn Port loopback page is displayed.
4 Click the desired STM/OCn port.
The corresponding port maintenance page is displayed.
5 Select appropriate value against the LoopBack Mode field. Refer to Table
7-2 on page 7-7 for details regarding the configurable parameters.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-9

Procedure 7-2
Provisioning loopback on PDH/DSn ports

Use this procedure to issue a loopback on the PDH/DSn ports provisioned on

the OME6130 network element.

This allows you to provide:

• Normal Operation
• Facility Loopback
• Terminal Loopback
Note: Loopback is a traffic affecting operation.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the corresponding loopback page (step 1).
• Configure the desired loopback mode for the port (step 4).

Expected results
• An alarm is raised indicating the loopback mode configured on the corresponding port.
• The port remains out of service until the loopback mode is configured to normal operation.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-10 Maintenance operations

Procedure 7-2 (continued)

Provisioning loopback on PDH/DSn ports

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click Loop-Backs.
3 Click PDH.
The PDH port loopback page is displayed.
4 Click the desired E1/DS1/E3/DS3 port.
The corresponding port maintenance page is displayed.
5 Select appropriate value against the LoopBack Mode field. Refer to Table
7-2 on page 7-7 for details.
Note: Downstream AIS is not sent for facility loopback on E3/DS3 ports.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-11

Procedure 7-3
Provisioning loopback on Ethernet ports

Use this procedure to issue a terminal loopback on the Ethernet ports

provisioned on the OME6130 network element.

This allows you to provide:

• Normal Operation
• Terminal Loopback
Note 1: Facility loopback is not supported on Ethernet ports.
Note 2: Loopback is a traffic affecting operation.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the corresponding loopback page (step 1).
• Configure the desired loopback mode for the port (step 4).

Expected results
• An alarm is raised indicating the loopback mode is configured on the corresponding port.
• The port remains out of service until the loopback mode is configured to normal operation.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-12 Maintenance operations

Procedure 7-3 (continued)

Provisioning loopback on Ethernet ports

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click Loop-Backs.
Note: Loopback is a traffic affecting operation.
3 Click Ethernet.
The Ethernet port loopback page is displayed.
4 Click the desired Ethernet port.
The corresponding port maintenance page is displayed.
Note: Facility loopback is not supported for Ethernet ports.
5 Select Terminal loopback/Normal operations against the LoopBack Mode
field. Refer to Table 7-2 on page 7-7 for details regarding the configurable
parameters.
6 Click Submit.
A confirmation page is displayed.
7 Click Accept Valid Modifications.
A success message is displayed.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-13

Procedure 7-4
Backing up the network element configuration data

Use this procedure to view or configure the backup configuration parameters

on the OME6130 network element. This is used to save the network element
configuration files to a server located at the specified URL.

This procedure allows you to configure the following parameters:

• Username of the PC where you want to store the back up configuration
data.
• Password for the above mentioned Username.
• IP Address of the PC where you want to store the back up configuration
data.
• FTP port (Optional).
• Directory, name of the directory in the PC where you want to store the back
up configuration data.
Refer to Local Craft Access User Guide, 323-1855-195 for description of
parameters on the Backup configuration page.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
• Ensure that FTP server is running on your PC or workstation.

Procedure tasks
• Reach the Backup configuration page (step 1).
• Enter the desired values against the corresponding fields (step 4).

Expected results
• It provides backup of network element configuration.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-14 Maintenance operations

Procedure 7-4 (continued)

Backing up the network element configuration data

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click Configuration management.
3 Click Backup configuration.
The Backup configuration page is displayed.
Note: Ensure that FTP server is running on your PC or workstation.
4 Enter appropriate values against the fields. For details, refer to Local Craft
Access User Guide, 323-1855-195.
5 Click Submit.
Configuration backup command accepted message is displayed.
In Status/Alarm area, Configuration backup: Successful message is
displayed against Configuration donwload operation last executed field.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-15

Procedure 7-5
Restoring the network element configuration data

Use this procedure to restore data (including that backed-up from circuit
packs) on the OME6130 network element from the server located at the
specified URL. The restore performs some basic checks on the integrity of the
restored data and compares the software release listed in the backup data with
the current software release running on the network element. If the software
releases are not the same, the restoration fails. A successful restoration is
completed with a cold restart of the network element during the commit
configuration step.

CAUTION
Risk of service interruption
During the commit configuration step of the restoration, the
network element will cold restart. Traffic on existing
cross-connects that are not common to those in the restored
configuration are affected.

CAUTION
Loss of comms data
During the cold restart, connectivity to the network element
will be impacted for up to 7 minutes. Activation of the restored
backup may overwrite the IP address and comms settings of the
network element. Ensure you have the comms provisioning
data of the backup file prior to the network element restore.

This procedure allows you to configure the following parameters:

• Configuration
• Username
• Password
• IP Address
• FTP port (optional)
• Directory

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-16 Maintenance operations

Procedure 7-5 (continued)

Restoring the network element configuration data

Configurable restore configuration parameters

Table 7-3 lists the configurable restore configurable parameters.
Table 7-3
Configurable restore configuration parameters

Parameter Default value Acceptable value

Configuration Operation Restore • Restore configuration from local

configuration machine (browse the file only by
from remote clicking the browse option)
machine • Restore configuration from remote
machine (give the Username,
password, IP address and the
directory of the machine from where
you are taking the data)

Refer to Local Craft Access User Guide, 323-1855-195 for description of other
parameters on the Restore configuration page.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Launch the Restore configuration page (step 1).
• Select the type of restoration (step 4).
• Enter the restoration settings (step 5).
• Commit the configuration (step 8).
• Wait for the cold restart to complete and log back into the network element (step 10).

Expected results
• The desired data is successfully restored.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-17

Procedure 7-5 (continued)

Restoring the network element configuration data

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click Configuration management.
3 Click Restore configuration.
The Restore configuration page is displayed.
4 Select the type of configuration.
If you want to restore Then select
the data from
remote machine Restore configuration from remote machine
local machine Restore configuration from local machine

Note: An FTP server is required while restoring from remote machine.

5 Enter appropriate values against the fields. For details, refer to Local Craft
Access User Guide, 323-1855-195.
6 Click Submit.
A confirmation page is displayed.
Note: Wait until a system message appears in the bottom frame of the Node
configuration page displays “successful“.
7 Click again on Restore configuration.
The Commit configuration page is displayed.
8 To restore configuration data, choose commit configuration for the
Configuration Operation field. To cancel the restore operation, select
cancel configuration.
9 Click Submit.
On successful restoring, the network element cold restarts without displaying
any message.
On successful cancel configuration, the Cancel configuration page is
displayed.
CAUTION
Cold restart
Restoring the network element configuration data leads to cold
restart of the network element.

Note 1: The commit configuration operation is only available when the

configuration download operation is successful. Refer the Node configuration
state on the same page.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-18 Maintenance operations

Procedure 7-5 (continued)

Restoring the network element configuration data

Step Action

Note 2: If the selected configuration is different from that of the desired

network element, the network element does not accept the commit
configuration option and displays an error message. To commit it forcefully,
you need to select the Forcefully commit option and Submit.
Note 3: After a forced restore, the node takes on the DCN of the node and
the backup originally came from. If you wish to change it, you must log on to
the node to do so after the forced restore is complete.
Note 4: Ensure to either commit or cancel the restored network element
configuration before initializing the network element.
10 Wait up to seven minutes for the network element to complete the cold restart
and log back into the network element with the new configuration.
The network element restore procedure is complete.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-19

Procedure 7-6
Restoring the factory defaults

This operation on the network element leads to the uninitialized mode by

removing all the provisioning and configuration from it. The user can perform
this operation when the network element needs to be in the default settings.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.
• Ensure that FTP server is running on your PC or workstation.

Procedure tasks
• Reach the Restore factory defaults page (step 1).
• Restore the factory defaults (step 4).

Expected results
• The factory default settings are restored.
• If the expected results do not occur, contact your next level of support.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-20 Maintenance operations

Procedure 7-6 (continued)

Restoring the factory defaults

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click Configuration management.
3 Click Restore factory defaults.
The Restore factory defaults page is displayed.
Note: The page displays a note; All configuration information, event history
and performance data will be deleted. This action will bring down existing
traffic. Please attempt the action only if the network element needs to be re
initialized. A power cycle is necessary after this action is performed.
4 Click Restore Factory Default.
5 Click on Proceed with Restoration.
Note 1: This operation will ask for the power cycle of the node. The node will
reboot and will go to the uninitialized mode. The factory defaults will be
restored.
Note 2: Restoring the factory defaults in the OME6130 network element
does not restore the default users.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-21

Procedure 7-7
Provisioning system settings

Use this procedure to configure the system settings on the OME6130 network
element.

This procedure allows you to configure the Performance day bin rollover
timezone.
Refer to Local Craft Access User Guide, 323-1855-195 for description of
parameters on the System setting page.

Before you start

• Log into the network element user interface at the default view level with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the System setting (step 1).
• Enter the desired time zone against the corresponding field (step 3).

Expected results
• Performance day bin rollover timezone is configured to the required time zone.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click System settings.
The System setting page is displayed.
3 Select from the pull down menu Local/GMT against the field.
4 Click Submit.
A confirmation page is displayed.
5 Click Accept Valid Modifications.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-22 Maintenance operations

Procedure 7-8
Provisioning SNMP trap destination IP addresses

Use this procedure to provision the Sub-Network Management Protocol

(SNMP) trap destination IP addresses.

Refer to Local Craft Access User Guide, 323-1855-195 for the description of
parameters on the provisioning SNMP trap destination IP address page.

This allows you to configure the following SNMP trap parameters:

• IP Address
• Port
• SNMP Version

Configurable SNMP trap destination parameters

Table 7-4 lists the configurable SNMP trap destination IP address parameters
with their default and acceptable values.
Table 7-4
Configurable SNMP trap destination parameters

Parameter Default value Acceptable value

IP Address - SNMP trap destination IP

address

Port 162 Port of the SNMP trap

destination address

SNMP Version SNMP_V1 SNMP_V1

SNMP_V2

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-23

Procedure 7-8 (continued)

Provisioning SNMP trap destination IP addresses

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the SNMP trap destination IP address page (step 1).
• Enter the desired values against the corresponding field (step 3).

Expected results
• SNMP trap destination IP address is successfully configured.
• If the expected results do not occur, contact your next level of support.

Action
Step Action

1 Click Configuration in the Navigation menu.

2 Click SNMP trap.
The SNMP trap destination IP addresses page is displayed.
3 Select from the pull down menu or enter the appropriate values against the
fields. Refer to Table 7-4 on page 7-22 for details regarding the configurable
parameters.
4 Click Submit.
A success message is displayed.
—end—

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-24 Maintenance operations

Procedure 7-9
Viewing the diagnostics information

Use this procedure to view all the system related information. The diagnostics
feature enables the user to view the following system related information, they
are:
• OSPF monitor
• System diagnostics
• iISIS monitor
The OSPF monitor has all the OSPF related information. System diagnostics
enables the user to collect the debug data and the iISIS monitor provides the
iISIS routing information.

Note: The iISIS monitor information is only available if iISIS was enabled
at nodal level.

Before you start

• Log into the network element user interface with appropriate user access privileges.
• Be familiar with the OME6130 network element user interface as described in Local Craft Access User
Guide, 323-1855-195.

Procedure tasks
• Reach the Diagnostics option (step 1).
• View the desired Diagnostic feature (step 3).

Expected results
• The diagnostic information has been viewed.
• If the expected results do not occur, contact your next level of support.

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
 Maintenance operations 7-25

Procedure 7-9 (continued)

Viewing the diagnostics information

Action
Step Action

1 Click Maintenance in the Navigation menu.

2 Click Diagnostics.
3 Determine your next step:
If you want to view Then go to
OSPF related information step 4
System related information step 6
iISIS related routing information step 13

4 Click OSPF monitor.

The OSPF monitor page has all the OSPF related information.
5 Click on the desired parameter to view the details. The procedure is
completed.
Refer to Local Craft Access User Guide, 323-1855-195 for the description on
the parameters.
If you want to view other diagnostics information, go to step 3. Otherwise, you
have completed the procedure.
6 Click System diagnostic.
The Collect Debug Data page is displayed.
Note: This page is displayed when the user collects the data for the first time.
Else it will directly display the overwrite data and Clean Up Data options.
7 Click on Collect Data.
8 Determine your next step:
If you want to Then go to
download the debug data step 9
overwrite the existing data step 10
clean the old data and download the step 11
recent debug data

9 Click on Download Debug Data link.

The data can be downloaded and saved in your local system.
If you want to overwrite the downloaded data, continue with step 10.
Otherwise, you have completed the procedure.
10 Click OverWrite Data.
The recent debug data will be automatically overwritten on the existing data.

Provisioning and Protection Switching Procedures 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
7-26 Maintenance operations

Procedure 7-9 (continued)

Viewing the diagnostics information

If you want to remove the previously downloaded data, continue with step 11.
Otherwise, you have completed the procedure.
11 Click Clean Up Data.
The Collect Debug Data page is displayed.
12 Click Collect Data.
The recent data can be saved in your local system.
If you want to view other diagnostics information, go to step 3. Otherwise, you
have completed the procedure.
13 Click iISIS monitor.
The information can be either be saved in your local system or just viewed
with an editor like wordpad.
—end—

Optical Multiservice Edge 6130 323-1855-310 Standard Rel 2.0 Iss 1 Jun 2007
Nortel

Optical Multiservice Edge 6130

Provisioning and Protection Switching Procedures

Copyright © 2006-2007 Nortel Networks, All Rights Reserved

This document is protected by copyright laws and international treaties. All

information, copyrights and any other intellectual property rights contained in this
document are the property of Nortel Networks. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information
contained herein and this document shall not be published, copied, produced or
reproduced, modified, translated, compiled, distributed, displayed or transmitted, in
whole or part, in any form or media.

The information is provided “as is” and Nortel Networks does not make or provide
any warranty of any kind, expressed or implied, including any implied warranties of
merchantability, non-infringement of third party intellectual property rights, and
fitness for a particular purpose.

Nortel, the Nortel logo and the Globemark are trademarks of Nortel Networks.
Internet Explorer is a trademark of Microsoft Corporation.
Netscape is a trademark of Netscape Communications Corporation.

323-1855-310
Standard Rel 2.0 Issue 1
June 2007
Printed in Canada