Professional Documents
Culture Documents
450-3201-001 (OneControl R5.0 Fundamentals) 11.01
450-3201-001 (OneControl R5.0 Fundamentals) 11.01
450-3201-001 (OneControl R5.0 Fundamentals) 11.01
Fundamentals
Release 5.0
What’s inside...
New in this release
Overview
GUI basics
Compatibilities
Publication history 0
August 2015
Issue 11.01 of the OneControl Unified Management System 5.0
Fundamentals
January 2015
Issue 10.01 of OneControl Unified Management System 4.2 Fundamentals
September 2014
Issue 09.02 of OneControl Unified Management System 4.1 Fundamentals
August 2014
Issue 09.01 of OneControl Unified Management System 4.1 Fundamentals
April 2014
Issue 08.01 of OneControl Unified Management System 4.0 Fundamentals
December 2013
Issue 07.01 of OneControl Unified Management System 3.2 Fundamentals
July 2013
Issue 06.01 of OneControl Unified Management System 3.1 Fundamentals
April 2013
• Issue 05.02 of OneControl Unified Management System 3.0
Fundamentals
• Issue 05.01 of OneControl Unified Management System 3.0
Fundamentals
September 2012
Issue 04.01 of OneControl Unified Management System 2.2 Fundamentals
August 2012
Issue 03.01 of OneControl Unified Management System 2.1 Fundamentals
January 2012
Issue 02.01 of OneControl Unified Management System 2.0 Fundamentals
Contents 0
Overview 2-1
The OneControl Unified Management System 2-1
OneControl and support for Ethernet Services Manager (ESM) 2-5
About ESM 2-5
Deployment basics 2-5
Geographical redundancy 2-6
Licensing 2-7
High-level features 2-8
Dashboard display 2-8
Consolidated Network Map 2-8
For more information about the network map and its components, see “The
Network Map” on page 3-5.Alarm browser 2-9
Audit log 2-9
Compatibilities 4-1
Supported network elements 4-1
Supported by Management of CoreStream, Management of 4200, and
Management of CoreDirector and 5400 4-1
Supported by Manager for 6k, OM5k and CPL 4-2
Supported by Ethernet Services Manager (ESM) 4-5
Equipment supported by Packet Service Management 4-7
Equipment supported by Wavelength Service Management 4-7
Network element software 4-7
10G 4-9
40G 4-15
100G 4-18
Equipment supported for OTN 4-23
5400 equipment supported for OTN 4-39
ATTENTION
Check for updated versions of this document on the Ciena portal. For
download instructions, see “Documentation download” on page ix.
Documentation download
You can download OneControl documents and other related documents from
the Ciena portal.
Command strings
Command strings that you enter in a terminal window appear in bold face
courier font as in the following example:
cd /tmp
Note: You must enter the command string exactly as shown, including
spaces, and press Enter.
Keyboard keys
Keyboard key names appear in bold face as in the following example:
Press Enter.
ATTENTION
Within this document, the term “OneControl Manager for 6k, OM5k and CPL”
should be interpreted to mean OneControl Manager for the following network
elements: ActivFlex 6110 Multiservice Optical Platform (ActivFlex 6110),
ActivFlex 6130 Multiservice Optical Platform (ActivFlex 6130), Optical
Multiservice Edge 6150 (OME6150), 6200 Packet-Optical Platform (6200),
6500 Packet-Optical Platform (6500), 565/5100/5200 Advanced Services
Platform (565/5100/5200), and Common Photonic Layer (CPL). The
OneControl Manager for 6k, OM5k, and CPL represents the evolution of the
Optical Manager Element Adapter (OMEA).
This chapter describes the new features in Release 5.0 of the OneControl
Unified Management System, referred to hereafter as OneControl.
New Devices
The following device is newly supported in OneControl Release 5.0.
• SLM stitching 1+8 MOTR and 2x10G OTR XCON to 5400 Control Plane
Layer 1
• Port alarm display for broadband cards
• Port state display for broadband card at service endpoints
• Filtering connections on intermediate nodes/ports
• Transport provisioning enabled by WSM license
• Navigation to PWSM tab to view supporting wavelengths
• 6200 1.1 SONET/SDH service management in OSP
• OVPNid support for 6500 Link and SNC for 6500 10.0
• 6500 ODU4 connection on 100G OCI (NTK529AC) and 100G Hybrid
XCIF (NTK656AA) (6500 10.1)
• “Retain home path” support for 6500 10.0
MTOSI enhancements
New features in Release 5.0 of OneControl Unified Management System
Gateway Multi-Technology Operations System Interface (MTOSI) include:
• Physical port traffic loopback
• Reporting of Power Supply and Fan Check status
• Provisioning of unpoliced traffic services
• System timing frequency distribution (BITS and SyncE)
• Link Aggregation Group (LAG) management
• MTOSI single gateway license
• Parity support
Basically, when traffic is policed, traffic on the port that exceeds the traffic
parameter boundaries is dropped.
System timing is the recovery of timing from external sources and the
distribution of timing to external sources, more specifically to:
• Allow the input of BITS and SyncE timing data on UNI/NNI ports and RJ45
ports, respectively.
• Allow the output of SyncE data on UNI/NNI ports.
The MTOSI LAG Management feature is only supported for SAOS 6.x.
Create a LAG
The new MTOSI createFloatingTerminationPoint operation and its notification
are introduced in this release.
This operation is used to support the creation of WAN link aggregation groups
on CESD devices supporting the LAG function. This operation also supports
the “tpDataToModifyList” as input. A PTP object representing each physical
port that is to be aggregated must exist; the list cannot be empty. A client side
CTP is re-created and associated to each port that is aggregated. Any
services and/or management VLANs present on either port to be aggregated
move to the FTP representing the LAG.
Delete a LAG
The new MTOSI deleteFloatingTerminationPoint operation and its notification
are introduced in this release.
This operation is used to support the deletion of WAN link aggregation groups
on CESD devices supporting the LAG function. Any services and/or
management VLANs present on a LAG move to the primary (distribution) port
of the LAG.
Previously, all five MTOSI feature licenses had their own expiry dates but
changes have been made and one MTOSI gateway license is used in place of
the five feature licenses. The MtosiLicenseService checks each license to see
if it has expired and sets the “isEnabled” property to true or false. To ensure
the feature licenses expire when the gateway license expires, the
MtosiLicenseService sets all feature licenses as enabled when the gateway
license is valid and otherwise when the gateway license expires.
Parity support
In this release, MTOSI supports parity of:
• 8700 SAOS release 8.3 to the functionality supported by MTOSI for 8700
SAOS release 8.2. This parity does not include testing of flow domain
fragments (FDFR).
• 6500 release 10.2 to the functionality supported by MTOSI for 6500
release 10.1.
• 6500 200G circuit pack with parity to existing MTOSI functionality for Fault,
Performance, physical and logical Inventory, and Provisioning (OTN
services).
Overview 2-
Figure 2-1 shows the relationship between the components of the OneControl
system.
Figure 2-1
The OneControl system
map, network element list, alarm counts and detailed alarms list. Users
have access to real-time events and the CoreStream NE inventory,
connection provisioning, the CoreStream circuit ID summary, span
configuration, EMS summary, NE security configuration, historical analog
performance monitoring, and an external point viewer.
• Management of 4200: when this license and associated software are
present, OneControl enables a series of menu selections for the
management of Ciena’s 2300 and the 4200 family of network elements.
Relate features use the main OneControl GUI as well as extended
OneControl GUI windows. Provisioned 4200 NEs and the links in which
they participate are fully reflected in the OneControl network map, NE list,
alarm counts and detailed alarms list. This includes the ESOM
Association Summary, management of optical channel connections,
provisioning for the 2150 NE and its port associations, the protected circuit
summary, real-time performance monitoring graphs, trap viewer, and G10
management. The 4200 management license also enables management
of O-APS and FlexSelect 40G devices.
• Management of 5400 and CoreDirector: when this license and
associated software are present, OneControl enables a series of menu
selections for the management of Ciena’s 5400 and CoreDirector Switch
products for optical switching equipment. These features use the main
OneControl GUI as well as extended OneControl GUI windows.
CoreDirector and 5400 NEs and the links in which they participate are fully
reflected in the OneControl network map, NE list, alarm counts and
detailed alarms list. Supported features include the Ethernet cross-
connect and ring summary, USR aggregate node management, and a
historical PM and Ethernet PM viewer.
• OneControl Service Layer Manager: OneControl’s Service Layer
Manager software works with other components of OneControl to provide
an end-to-end, service-oriented view of diversely managed network
connections. Service Layer Manager tools build a logical model of
SONET/SDH control-plane services traversing the network, identify
customers associated with those services, and correlate faults on
individual nodes and links with the overall services they support. The
Service Layer Manager is opened from the OneControl GUI, and opens in
an extended GUI of Service Layer Manager windows.
• OneControl Universal OSS Gateway: when this license is present,
OneControl enables access to northbound interfaces, and the ability to
create, edit, and delete northbound interfaces users through OneControl’s
the NBI Administration menu.
• Manager for 6k, OM5k and CPL: when this license and associated
software are present, OneControl’s Manager for 6k, OM5k and CPL offers
a comprehensive and scalable management system including the
following features:
Deployment basics
The OneControl software employs a client/server architecture.
• the OneControl server software resides on a physical server running the
Solaris or Linux operating system. OneControl can run on Solaris 10 (64-
bit) T2, T3, and T4 servers, Oracle Linux 5.6 or 5.8, or RedHat Linux 5.6
or 5.8 servers.
• the OneControl client application is available for Windows, Linux, and
Solaris. Windows support includes Windows XP, Windows 7 (32-bit and
64-bit) and Windows Citrix 2008 (64-bit).
Geographical redundancy
OneControl can be deployed in a Geographical Redundancy (GR)
configuration in which two fully functioning OneControl systems in distant
locations replicate data over a communications network. In the event of a local
disaster affecting one system, the unaffected system can take over the
responsibility for managing the network and OneControl client connections.
For more information about deployment options and system requirements for
OneControl, see OneControl Installation, 450-3311-201, and the OneControl
Engineering Guide, 450-3201-010.
Licensing
Ciena grants access to OneControl and many of its capabilities using feature-
specific licenses.
Users with appropriate security privileges can use the Manage EMS
Configuration tab to add and extend feature licenses. For quantity-based
licenses, users can also configure alarms that warn when resource
consumption exceeds threshold percentages.
Also, when a license has exceeded 100% usage, each OneControl client
logged in to the sever displays a popup dialog reminding the user that their
licenses have been exceeded. Clicking the OK button will close the warning
dialog. However, the dialog will display again every 30 minutes at the :00 and
:30 points of every hour, and will continue to do so until the license usage no
longer exceeds 100%.
Optional Major and Minor EMS alarms indicating “License Threshold Usage
Exceeded” can also be raised at user-configurable percentage thresholds,
although for each license OneControl will raise only the single highest alarm
that is warranted. A user with the administrator role can set these two
threshold values using the License section of OneControl’s Administration
GUI. Unlike the Critical license alarm, these Major and Minor alarms can be
cleared manually, and no dialog is displayed to users regarding these alarms.
High-level features
This section describes the main features of OneControl, including its inter-
operation with supported EMSes.
Dashboard display
The OneControl Dashboard provides a single space that summarizes user
data and network data:
• a Resources area displays the user’s recent activities, watch list,
bookmarks, and knowledge learning links.
• a Summaries area displays data regarding network health, EMS health,
and a current and historical fault summary. This information updates at a
configurable interval.
This display consolidates information from all NEs in the managed network,
mediated by the supported EMSes.
For more information about the Dashboard and its components, see “The
Dashboard” on page 3-3.
The network map displays all NEs and physical links, whether discovered by
software or created manually by users. Fault status is displayed for individual
NEs and links, as well as alarm summaries for the network as a whole.
Note: The 61XX series of nodes is an exception; only links involving 6110
and 6130 nodes are displayed on the network map. Links on 6150 nodes
are not displayed.
Like the Dashboard, the network map consolidates information from all NEs
in the managed network, mediated by the supported EMSes.
For more information about the network map and its components, see “The Network
Map” on page 3-5.Alarm browser
The OneControl GUI allows users to view both active and historical network
alarms on a single tab within the GUI. From the Alarms browser, a user can:
• acknowledge and un-acknowledge alarms
• manually clear alarms for OneControl itself
• sort the list of alarms by displayed properties
• view a count of all active alarms by severity
• filter the alarm list, and save, modify, delete, import, and export alarm
filters
• add, delete, and modify annotations for individual alarms
From a given OneControl alarm, a user can also directly open the
corresponding trouble clearing procedure in the online help.
OneControl also allows users to export and save any list of alarms to a
separate file.
Security alarms are browsed using a separate alarm browser, accessed from
a different area of the OneControl menu and requiring security privileges to
access.
Audit log
The OneControl Audit Log maintains a chronological record of user-initiated
operations and user-related security events, enabling an operator to
determine which user performed a given action, when, and from what IP
address. The log also records the result of the action as reported by the server
in response to the client request.
The audit logs tracks all security and configuration-related requests that are
specifically tied to a client, and which require more than read-only permission
levels. For example:
• security events: users logging in and out, and changes to administrative
security settings such as password duration and syntax
• enrolling or unenrolling a subordinate instance of ESM or an integrated
instance of Manager for 6k, OM5k and CPL.
• configuring data retention periods
• fault acknowledgment and clearing
• Threshold Crossing Alert (TCA) management activities
• creating or modifying links and groups
Note: Logs of any modifications made to OSRP links that were performed
using the OSRP Link Summary application are instead captured in
OneControl’s “Legacy Historical Audit Logs”.
The audit log keeps a record of all login and logout attempts received by the
server, regardless of user permissions or the result.
The Health Monitor displays the key, currently executing applications and
processes, and an indication of when critical application parameters exceed
high-end tolerances. In this way, the Health Monitor allows users and support
engineers to identify potential performance issues, and provides critical
environment data in the event of deficiencies in application performance or
behavior.
• other tabs display detailed data for individual managed services and
configured threshold crossing alerts.
Security: shared credentials
OneControl includes an option to provide a centralized security infrastructure.
When installed in this configuration, OneControl provides a single point from
which to administer user accounts and access control permissions for
OneControl and supported EMSes.
End-to-end service and service infrastructure paths are deduced from the
series of supporting nodal cross-connects and links. Once a user has
searched for and selected a service using the Service Query feature,
OneControl displays the path of the selected service on the network map.
OneControl also supports the creation of LSP tunnels (and other elements of
MPLS infrastructure) using MPLS Manager. Like Ring Manager, this
application is available for use with CES devices that are managed by
OneControl in conjunction with ESM.
End-to-end services are deduced from the series of supporting nodal cross-
connects and links. Once a user has searched for and selected a service
using the Service Query feature, OneControl displays the path of the selected
service on the network map.
• The Power Overlay feature enables you to view optical power levels,
including: the per fiber power level, the per channel wavelength power
level, and OSC powers on wavelength services and/or selected photonic
links.
• The Power Graph feature provides a view of the power data traversing a
photonic path. The Power Graph also provides details about the cards
participating in the selected wavelength service.
• Layer 0 (photonic) link alarms provide a visual alarm indicator (link
highlights) on the network map using alarm colors to reflect the highest
severity port alarm conditions of the ports at either side (source and
destination) of the photonic link.
The supported releases of these managed NEs vary based on whether the
network is made up solely of one type of NE, or includes multiple NE types,
and whether the NEs support OTN or OSRP as described in the OneControl
Service Management Guide, 450-3201-302.
For more information about OTN and SONET/SDH service management, see
the OneControl Service Management Guide, 450-3201-302.
GUI basics 3-
This chapter describes the basic components of the client GUI for the
OneControl Unified Management System (hereafter OneControl), including
the primary windows that form the starting point for most operations and the
structure of the menus used to access software features. The chapter also
includes procedures for opening and exiting the OneControl GUI on both
Windows and Solaris workstations.
Note: You can launch more than one instance of the OneControl client on
a single workstation; but only one client per workstation can log into a
given OneControl server.
This allows users to, for example, open different instances of the
OneControl client on the same workstation and log simultaneously into
both OneControl servers of a geographically redundant pair.
This chapter includes the following sections:
• “The OneControl client application” on page 3-1
• “The Dashboard” on page 3-3
• “The Network Map” on page 3-5
• “Data grids” on page 3-10
• “Configuring and saving GUI preferences” on page 3-11
The application title bar displays the OneControl server name. The current
user and connection status are displayed in the status bar.
Figure 3-1
The OneControl client GUI (showing Dashboard)
• Title Bar: The title bar displays the application name and the host name
of the server to which the client is connected.
• Menu Bar: The menu bar allows a user to open new views within the
OneControl GUI. For a breakdown of menu items and their effect when
selected, see “Configuring and saving GUI preferences” on page 3-11.
• Display Tabs: As the user opens new views in the OneControl GUI (for
example the Network Map, NE List, or Network Alarms view), most appear
as new tabs in the client GUI window. Some views (particularly all Security
windows and any subordinate EMS or Craft interfaces) open in separate
windows.
• Status Bar: The status bar displays the name of the user currently logged
into the OneControl client, as well as the status of the connection between
the client and the server. The network date and time are also displayed on
the right-hand side of the status bar.
The Dashboard
The OneControl Dashboard provides a single-glance summary of the network
statistics and details relevant to day-to-day network administration tasks. The
Dashboard is a central point from which to launch supported EMS
applications.
The Dashboard can be configured to display as a tab within the main GUI, or
as a separate window. By default the Dashboard displays when the client first
opens. For information about configuring the Dashboard, see “Configuring
and saving GUI preferences” on page 3-11.
Figure 3-2
The Dashboard
The Dashboard consists of two main areas: the Resources area and the
Summaries area.
The Resources area displays the user’s recent activities, watch list,
bookmarks, and access to product documentation and Ciena support.
• The Recent Activities list displays the activity log for the currently user,
such as alarm acknowledgments and client launches.
• The Watch List area display notifications whenever certain user-selected
events occur (such as alarms meeting certain criteria, or the provisioning
or management of Layer 1 connections).
• My Bookmarks provide one-click shortcuts to user-selected features; a
user can add bookmarks by simply dragging a menu item and dropping it
onto the Bookmarks area, then optionally associating a filter to narrow
down the associated display.
• The Support Center section includes links to Ciena web pages providing
product information and customer support, and to open the customer
documentation integrated into OneControl.
The Summaries area displays at a single glance key data pertaining to
network status, divided into the Network Overview, Connection Management
Overview, EMS Overview, and a current and historical alarm summary.
Individual charts summarize network status, and allow users to drill down to
find additional detail regarding the displayed data.
• The Network Overview displays NE alarm counts, a status summary,
alarm history, and graphs for Ethernet alarms, fiber status, and
provisioning limitations for Layer 0 connections.
• The Connection Management Overview displays two charts: one counting
in-service Layer 1 connections routed on their preferred, “home” route,
and another counting Layer 1 connections in each of the following states:
Down, Down Disabled, Troubled, Troubled Disabled, and Normal
Disabled. Both charts distinguish between connections in service and
those in provisioning.
• The EMS Overview displays information on the status of associated
element management systems, either Ethernet Services Manager (ESM),
or the integrated Manager for 6k, OM5k and CPL. Individual charts show
EMS status, the name and type of associated servers hosting the ESM or
Manager for 6k, OM5k and CPL software, and EMS threshold crossing
alerts.
• The Network and EMS Alarm Summary displays alarm counts, divided
into severity, for the entire managed network. Tools allow a user to view
alarm counts for different, recent time intervals to convey alarm trends,
and to enable or disable updates to the displayed information.
Note: The 61XX series of nodes is an exception; only links involving 6110
and 6130 nodes are displayed on the network map. Links on 6150 nodes
are not displayed.
In addition to displaying NEs and links, the network map represents a group
of related NEs as a single group. Using the network map, users can manually
add, move, or delete NEs, groups, and the links between groups.
Users can also change the background map over which the Network Map
topological display is superimposed.
Figure 3-3
The Network Map
• Graphical Map Area: shows NEs, groups, and links that constitute the
managed network in their topological relationship.
• View/Edit Options: allow the user to change selection tools, zoom and
scale the map view, edit the layout of NEs, groups, and links, refresh the
displayed data, and save updated layouts.
• Link Layer Display Selection: allows the user to individually enable or
disable the display of the following layers on the Network Map: Photonic,
SONET/SDH, SONET/SDH OSRP, OTN, Ethernet, and Unknown. For
user-created links, the user can specify the associated layer. When the
map is first opened, all layers will be selected by default.
• Search Tool: allows the user to search for an NE, group, or link on the
Network Map by name. Clicking the ellipsis button opens the NE list tab.
• Network Navigator Area: lists all groups on the network map. This
includes the name of the group and the aggregate alarm counts for all
member NEs. Alarm symbols are color-coded as described in “Alarm
indicators” on page 3-9.
• Network-wide Alarm Banner: displays a summary of all alarms of each
severity (critical, major, minor, and warning) for the entire network. The
display further breaks alarms into two groups: New unacknowledged
alarms, and Outstanding alarms (both acknowledged and
unacknowledged).
On the Network Map display, right-clicking an NE, link, or group opens a pop-
up menu from which the user can choose actions with reference to the
selected object. For example, choosing Manage NE List or View Current
Alarms opens the respective displays filtered to show only results pertaining
to the selected NE or group. The same pop-up menu includes an option to
open an NE Manager interface appropriate for the selected NE.
For more information about these service management panels, see the
OneControl Service Management Guide, 450-3201-302.
Table 3-1
NE Icon Types
AMP Transport
Multifunctional Group
Table 3-2
Additional Icon Types (node status, packet service port types)
The following port icons appear on the network map panel that appears as part
of the Packet Service Management tab.
Links
Links signify connections between NEs or groups. For automatically
discovered links, the link details are displayed on the link. You can also hover
over a discovered link to see the link details in a popup. Manually drawn links
do not include additional link information.
Whenever there are a configurable number of links between two endpoints (by
default, two or more), those links are automatically collected together into a
“link group”. A Link Group appears on the map as a thicker line than a single
link, and are common between group icons. Clicking a link group opens a
selection list containing all the links in that group.
Layer-0 and layer-2 links on the Network Map are shaded with the color of the
highest-severity alarm currently affecting either end port.
Layer-0 link alarms are summarized on a link group by highlighting the link
group the color of the highest severity link alarm of a link contained within the
link group. If you click the link group to view the contained links, each
contained link is highlighted with the color of its highest severity Layer-0 link
alarm. Right-click a link and select View Current Alarms or View Historical
Alarms to open the Alarms tab and examine the alarms.
Alarm indicators
On the network map, the NE icon color indicates alarm severities. The icon
background color is that of the highest severity unacknowledged alarm; if
there are no unacknowledged alarms, the icon is green. The icon border color
is that of the highest severity acknowledged or unacknowledged alarm. If an
NE is not the subject of any alarm, both the background and the border are
green in color.
The icon also reports the sum of the counts of the highest severity
acknowledged and unacknowledged alarms, with a plus sign to indicate that
there are also less severe alarms (either acknowledged or unacknowledged).
Groups
Groups are user-created objects that help organize NEs in the network map.
Groups can contain other groups. A group is represented on the map by a
distinctive group icon, and in the tree list by a folder icon. A user gives a group
a unique name upon creation.
A group tool tip reports the group name and a set of alarm severity counts
resembling those shown for NEs, except that the group counts are aggregates
of the alarm counts for all of the NEs within the group.
Information pop-ups
A popup appears when hovering over an object on the network map, and stays
visible as long as the mouse is over either the object or the popup.
Annotations
A user can use a pop-up menu to add annotations for a node and group. If an
object has an annotation, a small word balloon icon is displayed on the object.
Data grids
The OneControl GUI includes several tabs (Alarms, the NE List, and others)
which display data in tables. These tables have several common features
designed to assist users in manipulating and exporting data.
Note: Disabled columns are still present in the underlying data, but are
simply not displayed. As a result, sorting based on a given column still
applies even if that column is subsequently disabled; and if then re-
enabled, the sort identifier will still be displayed in the restored column
header.
This configuration of displayed columns, along with column order and width,
are saved to the OneControl server as a user preference associated with the
current user’s login, and are applied to future instances (but not other currently
open instances) of the same table.
User configuration is stored on the server and associated with a user login. As
a result, user preferences will be reflected in the GUI configuration regardless
of the workstation on which the user launches the client.
For the procedure to configure preferences in the OneControl client, see the
“General OneControl concepts” chapter of the OneControl Standard
Operations Guide, 450-3201-301.
Compatibilities 4-
CoreDirector and 6.1.4, 6.1.4.1, 6.2, 6.2.1, 6.2.1.1, 6.2.1.2, 6.2.2, 6.3
CoreDirector CI
5410 TDM 2.1, 2.1.1, 2.2, 2.2.1, 2.2.1.1, 3.0, 3.0.1, 3.0.2, 3.0.3,
4.0 (see Note 1)
5430 2.1, 2.1.1, 2.2, 2.2.1, 2.2.1.1, 3.0, 3.0.1, 3.0.2, 3.0.3,
4.0 (see Note 1)
CoreStream 9.1
O-APS 1.2.2
2300 3.4.2
Table 4-1
Nodes supported by Managers of CoreStream/4200/CoreDirector and 5400
2130 2.3.1
Note 1: Specifically, for 5400 2.2, 2.2.1, and 2.2.1.1, OneControl supports 10GBe
VCAT over SONET and 100GbE VCAT on OSLM-1. Other features unique to 5400
2.2, 2.2.1, and 2.2.1.1 are not supported.
Note 2: 5400 nodes tolerate OC-768/STM-256 client services on OSLM-3 and
TSLM-3 cards.
Table 4-2
Supported network elements for Manager for 6k, OM5k and CPL
Table 4-2
Supported network elements for Manager for 6k, OM5k and CPL (continued)
6500 (a) (See Note 14) 9.0.x Yes Note 10 T Note 9 T Note 9 T Note 10
6500 (a) (See Note 14) 9.1.x Yes Note 10 T Note 9 T Note 9 T Note 10
Table 4-2
Supported network elements for Manager for 6k, OM5k and CPL (continued)
Legend:
Yes: Fully supported
(Yes): Supported with limitations
T: Tolerated only (see notes for details)
- : Not supported
Note 1: These NEs display as “5000” in the Manager for 6k, OM5k and CPL GUI.
Note 2: Connection management such as retrieval of PTP and CTP from TMF is not supported.
Note 3: On the 6110 5.0, connection management is not available for Transmux and EoPDH cards.
Note 4: OSP Release 8.1 and later do not support MS-SPRing on 6130 NEs. On the 6110 5.0 NE,
connection management is not available for the Transmux and EoPDH cards.
Note 5: On the 6110 5.0, connection management is not available for the Transmux and EoPDH cards.
Note 6: 6150 SONET-mode NEs are not supported in OSP. OSP will display the 6150 NE name in NE
list, but will not retrieve ports and a user is not able to create, edit, or delete connections. OSP support
is provided for Release 1.x cards, but not for Release 2.x cards or configurations. Also, links on 6150
NEs do not display on the OneControl network map.
Note 7: 6150 SONET-mode NEs are not supported in NSV. NSV will display the 6150 NE name in NE
list, but will not retrieve ports or connections. NSV support is provided for Release 1.x cards, but not
for Release 2.x cards. Also, links on 6150 NEs do not display on the OneControl network map.
Note 8: 4F BLSR configurations are not supported but are tolerated.
Note 9: Can be used with 6500 Releases 8.0, 8.1, 9.0, 9.1, 9.2, 9.3, and 9.3.1. However,
configurations that are newly introduced in those releases may not be recognized, and as a result some
services may not be visualized and/or provisioned correctly.
Note 10: Tolerates 6500 Releases 8.0, 8.1, 9.0, 9.1, 9.2, 9.3, and 9.3.1. That is, can be used with 6500
Network Elements running those software versions. However, configurations that are newly introduced
in those releases may not be recognized, and as a result some connection-related information reported
from TMF may not be accurate. Fault, inventory and PMs are supported.
Note 11: 6500 support for specific connection types is indicated as follows:
(a): includes support for O-shelf.
(b): includes support for SONET/SDH control plane connections.
(c): includes support for OTN non-control plane connections.
(d): includes support for OTN control-plane connections.
Table 4-2
Supported network elements for Manager for 6k, OM5k and CPL (continued)
Note 12: Starting with 6500 10.05, OneControl adds the following Member Shelf Gateway capabilities
for 6500 management:
• Ability to manage a 6500 TIDc where GNEs can be configured on TIDc Member Shelves, or on the
Primary Shelf, or both.
• Support of Asymmetric RNE list for Private IP DCN.
• Support for in-service editing of GNE Span-Of-Control list.
Note 13: Support for CLI Session to 6500 via the GNE in a Private IP setup
Note 14: The Packet Service Management features of OneControl support the following cards on the
6500: L2MOTR, eMOTR, and OTN Packet Fabric cards, including packet cards (4x10G and 48xGE
PKT I/F) and OTN/hybrid based cards (10x10 Hybrid I/F and 100G hybrid XCIF).
3902 Yes - - - - - - - -
3903 - - - Yes - - - - -
3904 - - - Yes - - - - -
3905 - - - Yes - - - - -
3911 Yes - - - - - - - -
Table 4-3
Supported network elements for Ethernet Services Manager (ESM) (continued)
3920 Yes - - - - - - - -
3938 - - - Yes - - - - -
3942 - - - Yes - - - - -
5305 - - - - Yes - - - -
5410 - - - - - Yes - - -
8500 - - - - - - Yes - -
8700 - - - - - - - Yes -
LE-311v - - - - - - - - Yes
Note 1: OneControl is able to enrol and synchronize with the 8500, and displays alarm data
for the node. However no service provisioning is supported for the 8500 in this release of
OneControl.
Note 2: ISM 5.1.2 supports 8700 nodes only to SAOS 8.2.
Table 4-4
Network element software releases supported by WSM
Note 1: DOC is disabled on SLTE nodes. Only visualization and troubleshooting are supported.
Note 2: If DOC is disabled on SLTE nodes, only visualization and troubleshooting are supported. If
DOC is enabled on SLTE nodes, visualization, troubleshooting, provisioning and restoration are
supported.
10G
This section describes the 10G equipment and facility options supported by
WSM:
• “6500 10G broadband regen-capable” on page 4-9
• “6500 10G broadband line-to-line” on page 4-10
• “6500 10G POTS line-to-line” on page 4-14
• “5400 10G line-to-line” on page 4-15
Table 4-5
6500 10G broadband regen-capable equipment supported by WSM
Broadband Equipment XFP Equipment Client Facility
Table 4-6
6500 10G broadband line-to-line equipment supported by WSM
Broadband Equipment DWDM Equipment Line Facility
Table 4-6
6500 10G broadband line-to-line equipment supported by WSM (continued)
Broadband Equipment DWDM Equipment Line Facility
OTM2 1-8
Table 4-6
6500 10G broadband line-to-line equipment supported by WSM (continued)
Broadband Equipment DWDM Equipment Line Facility
OTM2 1-8
Table 4-6
6500 10G broadband line-to-line equipment supported by WSM (continued)
Broadband Equipment DWDM Equipment Line Facility
STM64 1-4
OTM2 1-4
Table 4-7
6500 10G POTS line-to-line equipment supported by WSM
POTS Equipment DWDM Equipment Line Facility
Table 4-8
5400 10G broadband equipment supported by WSM
Card Part # XFP Support Line ports Port Group Modes Pluggables
40G
This section describes the 40G equipment and facility options supported by
WSM:
• “6500 40G broadband” on page 4-16
• “6500 40G POTS line-to-line” on page 4-17
• “5400 40G line-to-line” on page 4-18
Table 4-9
6500 40G broadband equipment supported by WSM
OCLD Equipment Broadband Equipment Client Facility Access
Path
Type PEC Type PEC Type Port OTU Mapping FEA REGEN
Rate
Table 4-10
6500 40G POTS line-to-line equipment supported by WSM
OCLD Equipment Broadband Equipment Client Facility Access
Path
Type PEC Type PEC Type Port OTU Mapping FEA REGEN
Rate
E40GOCLD Only NO
Colored:
NTK539PA
NTK539PB
NTK539PC
NTK539PD
NTK539PE/
Submarine
NTK539PF
Colored &
Colorless:
NTK539RA
NTK539RB
NTK539RC
NTK539RD
NTK539RE/
Submarine
E40G Only NO
UOCLD Colored
NTK539XA
NTK539XE/
Submarine
Table 4-11
5400 40G line-to-line equipment supported by WSM
Card Part # XFP Support Line ports Port Group Modes Pluggables
100G
This section describes the 100G equipment and facility options supported by
WSM:
• “6500 100G broadband” on page 4-19
• “6500 100G POTS line-to-line” on page 4-20
• “5400 100G line-to-line” on page 4-21
Table 4-12
6500 100G broadband equipment supported by WSM
OCLD Equipment XFP Equipment Line Facility Access
Path
Type PEC Type PEC Type Port OTU Mapping FEA REGEN
Rate
Table 4-12
6500 100G broadband equipment supported by WSM (continued)
OCLD Equipment XFP Equipment Line Facility Access
Path
Type PEC Type PEC Type Port OTU Mapping FEA REGEN
Rate
Table 4-13
6500 100G POTS line-to-line equipment supported by WSM
OCLD Equipment XFP Equipment Line Facility Access
Path
Type PEC Type PEC Type Port OTU Mapping FEA REGEN
Rate
Table 4-13
6500 100G POTS line-to-line equipment supported by WSM (continued)
OCLD Equipment XFP Equipment Line Facility Access
Path
Type PEC Type PEC Type Port OTU Mapping FEA REGEN
Rate
Table 4-14
5400 100G broadband equipment supported by WSM
Card Part # XFP Support Line ports Port Group Modes Pluggables
Table 4-14
5400 100G broadband equipment supported by WSM (continued)
Card Part # XFP Support Line ports Port Group Modes Pluggables
Table 4-15
6500 10G - Equipment and facilities supported for OTN
P10GSOEL OC192 2
Table 4-15
6500 10G - Equipment and facilities supported for OTN (continued)
OC192 2
OC192 2
OTM2 2 10G709
OC192 2
Table 4-15
6500 10G - Equipment and facilities supported for OTN (continued)
OC192 2
OTM2 2 10G709
Table 4-16
6500 40G - Equipment and facilities supported for OTN
ETH40G 1 44G5
OTM3 1 43G018
Table 4-16
6500 40G - Equipment and facilities supported for OTN (continued)
Table 4-16
6500 40G - Equipment and facilities supported for OTN (continued)
Table 4-17
6500 100G - Equipment and facilities supported for OTN
Table 4-17
6500 100G - Equipment and facilities supported for OTN (continued)
Table 4-18
6500 OTSC - Equipment and facilities supported for OTN
OC192 1-4
OC192 1-4
Table 4-18
6500 OTSC - Equipment and facilities supported for OTN (continued)
OC192 1-4
OC192 1-4
OC192 1-4
Table 4-18
6500 OTSC - Equipment and facilities supported for OTN (continued)
OC192 1-4
OC192 5-8
Table 4-18
6500 OTSC - Equipment and facilities supported for OTN (continued)
OC192 1-8
OC192 1-8
OC192 1-8
Table 4-19
6500 MOTR and OTNFLEX - Equipment and facilities supported for OTN
Table 4-19
6500 MOTR and OTNFLEX - Equipment and facilities supported for OTN (continued)
Table 4-19
6500 MOTR and OTNFLEX - Equipment and facilities supported for OTN (continued)
Table 4-19
6500 MOTR and OTNFLEX - Equipment and facilities supported for OTN (continued)
The following 6500 OPS, TPT, and 40G configurations are supported.
Table 4-20
6500 OPS, TPT, and 40G - Equipment and facilities supporting OTN
Table 4-21
OneControl OTN support for 5400 Modules
ESLM
MSLM
OSLM
TSLM
TSLM-2D - - - - - - Yes
TSLM-12D - - - - - - Yes
Release 5.0
Publication: 450-3201-001
Document status: Standard
Issue 11.01
Document release date: August 2015
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena
web site at www.ciena.com