Nortel Networks 3500 User Manual
Operation, administration, and maintenance (OAM) features 2-45
Planning and Ordering Guide—Part 1 of 2 NTRN10AN Rel 12.1 Standard Iss 1 Apr 2004
•
UUU is the network entity code.
The combination of these codes comprise a unique place, a unique building
and a specific entity. If lower case characters or a mixture of upper and lower
case characters are desired, the CLLI may be enclosed in quotations.
and a specific entity. If lower case characters or a mixture of upper and lower
case characters are desired, the CLLI may be enclosed in quotations.
Connection ID
Connection ID is a 40 character string used to identify specific connections
across an OPTera Metro 3000 network. This feature allows users to label
network connections in a more meaningful way to make the identification of
connections less complicated.
across an OPTera Metro 3000 network. This feature allows users to label
network connections in a more meaningful way to make the identification of
connections less complicated.
Note: The backslash (/), double quotation mark ("), and percentage sign
(%) characters are not supported in the Connection Id string.
(%) characters are not supported in the Connection Id string.
Connection ID can be added or modified through any of the following
interfaces:
interfaces:
•
TL1
•
Site Manager
•
Trail Manager
Connection ID can be added, modified, or deleted to or from an existing
SONET cross-connect while carrying traffic. A Connection ID can be
provisioned for a resilient packet ring (RPR) cross-connect type when
provisioning an end-to-end connection but it cannot be edited or deleted
afterwards. Connection ID for RPR connections require you to provision both
the east and west cross-connects first.
SONET cross-connect while carrying traffic. A Connection ID can be
provisioned for a resilient packet ring (RPR) cross-connect type when
provisioning an end-to-end connection but it cannot be edited or deleted
afterwards. Connection ID for RPR connections require you to provision both
the east and west cross-connects first.
Note: Connection ID is preserved over in-service rollover.
Connection ID is supported for all connection types on the OPTera Metro
3500. For RPR connections, Connection ID is stored on the optical interfaces
associated with the resilient packet ring (RPR) but cannot be edited after its
initial set-up.
3500. For RPR connections, Connection ID is stored on the optical interfaces
associated with the resilient packet ring (RPR) but cannot be edited after its
initial set-up.
Consolidated load
OPTera Metro 3500 Release 12.1 is a consolidated load, with support for
J-SDH (Japan Synchronous Digital Hierarchy) and SONET (Synchronous
Optical Network) payload and frame formats.
J-SDH (Japan Synchronous Digital Hierarchy) and SONET (Synchronous
Optical Network) payload and frame formats.
You can use Site Manager or the TL1 interface to switch from SONET mode
to a Superset (SONET and J-SDH) mode. You can also use these interfaces to
retrieve the current mode. Refer to the Release 12.0 Japan Specific Supplement
for more information.
to a Superset (SONET and J-SDH) mode. You can also use these interfaces to
retrieve the current mode. Refer to the Release 12.0 Japan Specific Supplement
for more information.
Note 1: You cannot switch from Superset mode to SONET mode.