Planning Guide

450-3121-601
Nortel Networks
Optical Manager Element Adapter 3.0

Planning Guide
Standard Issue 2 January 2005
Whats inside...
Optical Manager Element Adapter description Optical Manager Element Adapter applications Computing platform requirements Compatibilities Engineering considerations Ordering information
Copyright 2003 - 2005 Nortel Networks, All Rights Reserved

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. This 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 Networks, the Nortel Networks logo, and the Globemark are trademarks of Nortel Networks.
Printed in Canada or in the United Kingdom
iii
Contents
About this document Optical Manager Element Adapter description
OMEA architecture 1-1 Network management layers 1-1 OMEA domains and server groups 1-3 OMEA integration with AP 1-3 OMEA Desktop 1-3 AP network management 1-4 Fault management 1-5 Navigation and network element auto-discovery 1-5 Reach through to network elements and OMEA 1-5 Optional applications 1-5
v 1-1
Optical Manager Element Adapter applications

New features and functionality 2-1 OMEA Desktop introduction 2-2 OMEA applications and commands 2-3 Context for applications 2-5 OMEA Desktop window 2-5 Navigator 2-8 Network tree 2-9 Navigator alarm column 2-9 Find button 2-10 Object menus 2-10 OMEA Applications window 2-10 OMEA Applications window management 2-11 Navigating among applications 2-11 NE Properties 2-13 Performance applications 2-14 Performance measurement collection 2-14 Historical PM Archive Browser 2-14 Security applications 2-15 Event Browser and Audit Trail 2-16 Global Settings 2-16 Users and groups 2-17 User access privileges and permissions 2-18 Password policy 2-18
2-1
Planning Guide 450-3121-601
iv Contents Account activity information 2-18 Network Element Backup and Restore 2-19 Considerations for redundant server configurations 2-20 NE Backup and Restore user interface 2-20
Computing platform requirements

OMEA server requirements 3-1 Hardware specifications 3-2 OMEA server software requirements 3-4 Solaris OS requirements 3-5 Solaris OS Patches required for OMEA 3-6 Configuring the default router 3-7 Partitioning information 3-7 hostname requirement 3-7 Kernel parameters 3-8 Modify system files to enable remote root access (optional) 3-8 OMEA client specifications 3-9
3-1
Compatibilities
Optical Manager Element Adapter release 3.0 compatibility 4-1 Supported upgrade paths 4-4
4-1
Engineering considerations
Deployment rules 5-2 Applications Platform 5-2 15-minute PM collection 5-2 OMEA and network elements 5-2 Disk space requirements 5-3 Base data 5-4 Network Element data 5-4 Bandwidth requirements 5-5 OMEA capabilities 5-6 Firewall considerations 5-8
5-1
Ordering information
Software and documentation packages 6-1
6-1
Optical Manager Element Adapter 3.0 Jan 2005 Standard
About this document

This planning guide describes the applications and functionality provided by Optical Manager Element Adapter (OMEA).
Audience
This document is for the following members of the operating company: strategic and current network planners provisioners transmission and standards engineers network administrators system lineup and testing (SLAT) personnel
Technical support and information

Nortel Networks provides technical support for customers of Optical products. This support consists of emergency and regular technical support and a suite of additional support services. Refer to Contacting Optical products Technical Support on page vii for contact information specific to your location.
Emergency technical support
You can reach emergency technical support personnel outside of the regular technical support hours through an automatic paging system. Nortel Networks provides emergency technical support for customers who have purchased an optional, value-added service package. For the period covered by the service package, technical support for critical issues is provided outside of regular business hours. Note: For the period covered by the service package, access to regular technical support for all issues defined in the service package is also available.
vi About this document
Issues considered critical include: issues that are now having an effect on, or have the potential to immediately have an effect on, services carried by the managed nodes issues causing the loss of network visibility or loss of fault management functionality to one or more of the managed nodes
Regular technical support
Nortel Networks provides regular technical support for customers who have purchased an optional, value-added service package. Use the regular technical support to report and receive help for issues covered by the product warranty, as described in your purchase agreement with Nortel Networks. You can be charged a standard rate for service requests that Nortel Networks considers to be outside the scope or period covered by the product warranty. You can purchase extended warranty coverage and additional support services. These optional, value-added service packages are part of the Optical Product Services suite.
Optical Product Services
A full suite of optional, value-added services and service packages is available for purchase through the Optical Product Services suite. The services include: extended product warranty support advanced technical support installation planning and support on-site installation technical training software upgrades network planning and integration consultation Network Management System Audits and Performance Reports Contact your Nortel Networks representative for more information about the Optical Product Services suite.
About this document vii
Contacting Optical products Technical Support You can reach Optical products technical support by telephone through Nortel Networks technical support. Use the same telephone number for both emergency and non-emergency support. Telephone numbers are provided for several large regions and for individual countries outside of those regions. You can find these numbers on the Nortel Networks internet site at the following address:
http://www.nortelnetworks.com/help/contact/global
Technical support telephone numbers supporting large regions are listed below.
Region Telephone number You require an express routing code (ERC). To determine the ERC, see our corporate Web site at www.nortelnetworks.com. Place your cursor over the SUPPORT & TRAINING link, then select Express Routing Codes.
North America 1-800-4NORTEL (except Mexico) (1-800-466-7835)
Continental Europe
00800-8008-9009
United Kingdom +44 (0)20-8920-4618 Africa Asia Pacific 27-11-808-4000 011-61-2-8870-8800
CE conformance There are no European Union Directives that require the fitting of the CE marking which apply to this software product.
viii About this document
1-1
Optical Manager Element Adapter description

Optical Manager Element Adapter (OMEA) enables the network management functions provided by Optical Network Management Applications Platform (AP) for the Optical Metro (OM) 5100, Optical Metro 5200, Optical Multiservice Edge (OME) 6500, OME 6110, and the Common Photonic Layer (CPL) network elements. For more information on network elements supported by OMEA, see Compatibilities on page 4-1. For more information on the network management functions provided by AP, see Applications Platform Introduction, 450-3101-100. OMEA also provides element management applications specific to the NE type being managed. These applications are available through the OMEA Desktop. More detailed descriptions of element management applications, and procedures for using them, are described in the OMEA Standard Operations Guide, 450-3121-301 documentation. This section describes the OMEA architecture and AP network management. For a list of NEs and for associated OMEA features that this release of OMEA supports see Compatibilities on page 4-1 for more information.
1-
OMEA architecture
This section covers the following topics: Network management layers on page 1-1 OMEA domains and server groups on page 1-3 OMEA integration with AP on page 1-3 Network management layers The Nortel Networks management solution consists of three layers: the network element (NE) layer, the mediation layer, and the application layer. The NE layer consists of the Optical series NEs being managed. Each managed NE is assigned an IP address via which it is added to the OMEA server.
1-2 Optical Manager Element Adapter description
The mediation layer consists of a stand-alone OMEA server or two OMEA servers configured in an active-active redundant mode. These two dual active servers manage the NEs and feed the NE data into AP. Note: While both servers are active and collect data from the NEs, only one server feeds data to AP. From the AP view, only one server is active. The application layer uses the Application Platform either in standalone mode or in a federation. The OMEA servers are added to AP as controllers, following which NEs being managed by OMEA are auto-discovered on AP.
Figure 1-1 Network management layers
Optical Manager Element Adapter description 1-3
OMEA domains and server groups An OMEA domain is a logical entity which, at the lowest level of deployment, consists of an OMEA server and the network elements (NEs) managed by that server. An OMEA server and the NEs managed by that server is referred to as a group. You have the option to deploy an additional OMEA server to create a redundant pair configuration. These redundant servers may be geographically separated. OMEA does not support multiple groups per domain. When two OMEA servers are deployed in a redundant pair configuration, one server is designated the master and the other server is designated the slave. Synchronization of data on the two servers takes place automatically, with the master writing to the slave. If the master server fails, you can manually force the slave server to assume the master status (for details of redundancy refer to the OMEA Installation and Configuration Guide, 450-3121-201). OMEA integration with AP Integration with AP provides reach-through capability from the Applications Platform (AP) to the network elements through the OMEA. In this configuration, the network elements are displayed on AP, which manages the NEs via the OMEA. OMEA in a redundant configuration consists of two active servers on Sun Solaris servers. This configuration uses an Ethernet transmission control protocol/Internet protocol (TCP/IP) local area network (LAN) or a wide area network (WAN) connection to the network elements. Refer to the OMEA Installation and Configuration Guide, 450-3121-201 for details and procedures on integrating OMEA with AP. AP users can view the network, retrieve alarms, and reach through to the network elements through OMEA. For information about the reach through procedures, refer to the OMEA Standard Operations Guide, 450-3121-301. OMEA also provides element management applications specific to the NE type being managed. These applications are available through the OMEA Desktop. You can log in to the OMEA Desktop from AP. OMEA Desktop OMEA 3.0 introduces a new desktop that can be installed on a PC or a Sun workstation. Once the desktop is installed on a PC or a Sun workstation, a low bandwidth and secured (RADIUS) connection can be made to OMEA servers. In a redundant configuration, the OMEA desktop user can connect to either server of a redundant pair; a user connected to an OMEA server will access the same information as a user connected to the peer OMEA server or as the AP reachthrough user.
In a redundant configuration, there is no discrepancy between OMEA desktops as there is a real-time peer-to-peer synchronization performed between the servers. Any change made on a server is automatically updated on the other server.
Figure 1-2 OMEA Desktop access
AP network management
Optical Manager Element Adapter functions as a mediation device that provides a link into AP. AP provides the following capabilities: Fault management on page 1-5 Navigation and network element auto-discovery on page 1-5 Reach through to network elements and OMEA on page 1-5 Optional applications on page 1-5
Optical Manager Element Adapter description 1-5
Fault management AP provides the following fault management capabilities: retrieve alarms raise notification clear notification acknowledgement of alarms
Network Summary Alarm Banner
The Network Summary Alarm Banner in the AP displays a summary of all active alarms in the current view, including alarms raised by optical network elements. The Network Banner highlights the severity of new alarms using color indicators. For more information on AP Fault Management, refer to AP Alarm Management User Guide, 450-3101-014. Navigation and network element auto-discovery Once the OMEA is added to AP using the Graphical Network Editor (GNE), AP automatically discovers the network elements and enrolls them. You can use tools within APs GNE to lay out the network elements. The Graphical Network Browser (GNB) displays network elements as icons and provides a launch point for AP applications. For features and tools supported from AP, refer to the AP user guides. Reach through to network elements and OMEA From AP, you can select a network element and log in to it. You can launch the NE craft interface or a TL1 session. You can also log in to the OMEA server. You can launch the OMEA Desktop or open a command line window to the OMEA server Unix operating system. Optional applications The following value-added applications can be ordered separately. However it is important to note that these applications are only supported on certain network element types (see Compatibilities on page 4-1).
Historical Fault Browser
The Historical Fault Browser (HFB) application provides historical alarm event support for all network elements managed by AP. The HFB application provides centralized storage and retrieval of network alarm events. The HFB application also provides filtering of alarm events and report generation capabilities. The HFB application stores alarm event information in a relational database management system (RDBMS), which
allows you to generate historical information about the alarms that occurred in the network. For more information, see the Historical Fault Browser User Guide, 450-3101-041.
Fault management contract interfaces
The Fault management contract interface application provides a CORBA interface for exporting alarm information to other compliant software systems. For more information, see the Alarm Management CORBA Open Interface Specification, 450-3101-802.
External alarm interface
The External alarm interface (EAI) application resides on the AP workstation and allows the AP to communicate with an external computer system. The EAI and the external computer system communicate through a transmission control protocol/Internet protocol (TCP/IP) connection. The EAI feature allows the external computer system to receive real-time alarm surveillance information. The EAI communicates with the relevant internal subsystems of the AP to retrieve and format the messages into ASCII strings. For more information on EAI, see the Alarm Management: External Alarm Interface User Guide, 450-3101-820. Note: This function requires an option key. For more details on AP, refer to AP Release Planning Guide, 450-3101-601.
Trail Management
Trail Management provides an end-to-end connection and bandwidth management capability for broadband networks. Enhanced scalability and distribution permits support for large networks and geographic separation of the Trail Management graphical user interface (GUI). For more information, see the Trail Management Planning Guide, 450-3101-608.
TMF814 interface support
AP Release 10 forms the basis for the evolution of the Optical Management solution for Nortel Networks Optical products. A key component is the evolution of CORBA northbound interfaces to TMF814. See the AP Release 10 documentation for more information.
Centralized connection management
Optical Connection Management (OCM) enables the provisioning of end-to-end connections across network elements from a central position.
2-1
Optical Manager Element Adapter applications

This section provides an overview of the applications provided by Optical Manager Element Adapter (OMEA). These applications are grouped under the following categories: New features and functionality OMEA Desktop introduction OMEA applications and commands OMEA Desktop window Navigator Navigating among applications NE Properties Performance applications Security applications Network Element Backup and Restore
2-
New features and functionality

OMEA 3.0 introduces new network element types to its portfolio:
Common Photonic Layer (CPL) Release 1.0 Note: OMEA support for CPL has been formally verified with OMEA 3.0 and CPL 1.0. The following functions are currently supported: fault management, NE discovery, and OMEA Backup and Restore. Note that Craft Launch is not currently supported from either Applications Platform or OMEA. A separate browser application must be used and the NE IP address available from the OMEA CPL NE Properties tab may be used to initiate a craft login. Optical Multiservice Edge (OME) 6110 Release 1.0 (formally known as COE)
2-2 Optical Manager Element Adapter applications OMEA 3.0 supports the following new release for existing network elements:
Optical Multiservice Edge (OME) 6500 Release 1.1 New OMEA Desktop GUI accessible from a PC, Sun workstation, and AP From a PC or a Sun workstation, OMEA Desktop GUI can access either server in a redundant pair (that is, GUI load sharing), Active-Active OMEA servers OMEA Active Alarm Manager and Active Alarm Banner User Session Monitoring Enhanced OMEA security (configurable User and Resource Groups) PM data format has changed to CSV format (therefore, data can be exported to external viewers). Also, the data retrieval performance is improved. Craft launch from the OMEA Desktop GUI Enhanced OMEA Administration Increased OME 6500 support for OMEA applications: NE Backup and Restore, Centralized Security (RADIUS) and TL1 Time Synchronization. Retrieval of all Optical Power measurements from OM5000. Trail Management support for OME 6500
OMEA 3.0 new features:
OMEA 3.0 supports additional features for existing network elements:
OMEA 3.0 Application Platform (AP) related features:
OMEA Desktop introduction

OMEA 3.0 introduces a new desktop that can be installed on a PC or a Sun workstation. Once the desktop is installed on a PC or a Sun workstation, a low bandwidth and secured (RADIUS) connection can be made to OMEA server. The OMEA desktop offers generic base functionality similar to AP, such as displaying a Navigation Tree containing the NEs under management, presenting the user with a login screen, and more. For more information, see OMEA Standard Operations Guide, 450-3121-301. OMEA PC or a Sun desktop provide the same GUI and functions as the AP reachthrough. Note: Network element reach though (craft launch) from the OMEA Desktop is only supported for a PC client, it is not supported on Solaris or AP reachthrough.
Optical Manager Element Adapter applications 2-3
OMEA applications and commands

OMEA applications and commands are accessible from two principal windows (shown in Figure 2-1), depending on the application: the Optical Manager Element Adapter - Desktop (OMEA Desktop) window, or, the OMEA Applications window Note: The OMEA Applications window is disconnected from the OMEA Desktop window (the OMEA Applications window is not contained within the OMEA Desktop window).
Figure 2-1 OMEA Desktop and OMEA Applications windows OMEA Desktop window: displays standard applications and commands (for example, the Alarm Manager) OMEA Applications window: displays administrative applications and commands (for example, NE Properties)
OMEA applications consist of the following: standard applications and commands administrative applications and commands
2-4 Optical Manager Element Adapter applications
Standard applications and commands are generally applicable to all network element types, and refer to basic monitoring functions (carried out by a network user) that do not directly affect the operation of the managed network elements. These applications and commands are accessible from the menu bar in the main OMEA Desktop window, which appears upon successful login. Figure 2-2 displays the items in the OMEA Desktop window menu bar.
Figure 2-2 Menu bar in the OMEA Desktop window (for accessing standard applications and commands)
Note: Not all commands displayed in the Help menu are supported. Administrative applications and commands are applicable to network elements and provide access to common functions that must be carried out by a network administrator. These applications are displayed in the OMEA Applications window. To open the OMEA Applications window, right-click on the active server icon from the Navigator, then select OMEA Desktop > Show. Figure 2-3 displays the items in the OMEA Applications window menu bar.
Optical Manager Element Adapter applications 2-5 Figure 2-3 Menu bar in the OMEA Applications window (for accessing administrative applications and commands)
Context for applications Applications accessed from the OMEA Applications window do not support context launching. Only applications accessed from the OMEA Desktop window (such as the Alarm Manager application) support context launching. To launch an application with a specific context, you select the required resource from the Navigator before launching the application.
OMEA Desktop window

The OMEA Desktop window appears on successful login and is the base window for the OMEA applications. The Desktop window consists of the following elements (see Figure 2-4): a menu bar from which standard OMEA applications are launched a display area a status bar that provides (from left to right): NE/server/domain loss of association indicator alarm counts area that displays the total number of active alarms, by severity, for all NEs being managed messages area that displays the status of actions the OMEA is performing Figure 2-4 also shows the Navigator, a window that appears when the main OMEA Desktop window is opened. See Navigator on page 2-8.
2-6 Optical Manager Element Adapter applications Figure 2-4 OMEA Desktop window Title bar Menu bar
Display area
Status bar Messages area Alarm counts area Loss of association indicator
Main menu bar
The menu bar that appears in the OMEA Desktop window provides access to standard applications and commands. Some applications require a context, which you can select in the Navigator. Note: The ability to launch certain applications depends on your access privileges. If you do not have sufficient access privileges, the corresponding menu item appears greyed out.
The menu bar in the OMEA Desktop window also provides access to window management commands, from the Window menu, for organizing and displaying OMEA windows.
Display area
The OMEA display area contains the standard applications that are launched from the menu bar in the OMEA Desktop window. For example, when you launch the Alarm Manager, this application opens and is contained within the display area. Note: Administrative applications are not contained within the display area, but are contained within a separate OMEA Applications window.
Loss of association (LOA) indicator
An icon in the bottom left corner of the OMEA Desktop window provides a high-level indication of the communications between OMEA and the network elements in its group. The normal icon is a question mark in a gray box. If there is a loss of association, with any managed network element, the box turns blue. The Navigator indicates more precisely which NE is affected. Figure 2-5 displays the loss of association indicators.
Figure 2-5 Loss of association indicators
Normal communications (background is grey) NE LOA (background is blue) Server LOA Domain LOA
Alarm counts area
The alarm counts area displays the total number of active alarms by severity, for all NEs, for all servers, being managed. A field is displayed for each of the alarm severity levels.
Messages area
The status bar along the bottom of the OMEA Desktop window includes a messages area. Status messages are available for certain actions only. For supported actions, status messages summarize the command executed and application launched from the OMEA. The status messages indicate if an action is still processing, and whether the action was successful. The messages area can be expanded to display the previous 20 status messages, by clicking the arrow at its right edge.
Navigator
The Navigator is a tool that provides the following important functions (see Figure 2-6): displays the network as a hierarchy of resources that can be viewed individually or as a group displays current alarm status for resources supports object (right-click) menus that provide access to nodal applications relevant to the selected resource provides context for applications launched from the OMEA Desktop window menu bar The Navigator opens with initial login. You can minimize or close the navigator, and re-open it by selecting the Show Navigator command from the Window menu in the OMEA Desktop window. The Navigator consists of the following components within the Resources tab: Network tree on page 2-9 Navigator alarm column on page 2-9 Find button on page 2-10 Object menus on page 2-10
Figure 2-6 Navigator
Network tree Alarm count Alarm severity count Other severities Domain Server Group Server Network Elements
Alarm color
Find tool
Network tree The Network tree displays the hierarchy of resources in your network, on the right side of the Navigator. The hierarchy consists of the following levels: Network - a single instance representing the entire managed network Domain - OMEA Desktop server (you can log in to multiple OMEA Desktop servers) Server Group - a container for OMEA servers (standalone or redundant pair) Server - an OMEA that manages one or more network elements Folder - a device for automatically grouping network elements of the same type Sub-folder - sub-folder level for OM5000 only. OM5000 supports the following two sub-folder levels: the OM5000 network name sub-folder and the Site identifier sub-folder Network elements - managed resources Note 1: A blue icon with a question mark indicates that OMEA has lost communication with, or has not yet discovered, the associated network resource. Note 2: Multiple logged in servers are displayed in the Navigator in alphanumerical order (from top to bottom). Objects in the hierarchy are expanded and collapsed by clicking on the plus and minus boxes to their left. Right-clicking on an item presents its object menu, from which applicable applications can be started with a context of the selected item. Objects in the Navigator are managed using applications opened from the Administration menu, which is available in the OMEA Applications window. Navigator alarm column Alarm information displayed in the left column of the Navigator applies to adjacent items in the Network tree. The alarm information consists of the following objects, within a rectangle: a color that indicates the highest severity alarms a number, indicating the number of highest severity alarms associated with the adjacent object a letter, indicating the highest severity of alarm A plus sign, if present, indicates that additional alarms of lower severity also exist for the associated object.
Alarm severity letters and colors are as follows: C - critical - red M - major - red m - minor - orange w - warning - yellow For unexpanded groups containing subgroups, the alarm information is a total for all subgroups contained by the group. Expanding the group distributes alarm counts to the individual members of the expanded group. If an expanded group contains further unexpanded subgroups, the alarm information beside the unexpanded subgroups is a total for all items in the subgroup. The alarm information is distributed to members in the subgroup when it is expanded. This behavior applies to any further levels of grouping in the hierarchy. Find button If you do not know the location of a network resource in the hierarchy, click the Find button in the Navigator to open the Find dialog. Use the Find dialog to search for the resource. You can also use the Find dialog to open the hierarchy in the Navigator to reveal the found resource. Note: To specify a partial search string, use a wildcard character in the string you enter in the Containing text field. For more information, see OMEA Standard Operations Guide, 450-3121-301. Object menus The object menu is displayed when you right-click on an object. If you attempt to use an application that is not available, OMEA presents information messages to indicate the reason.
OMEA Applications window

The OMEA Applications window provides access to administrative applications and commands for network elements. You can launch the OMEA Applications window from the object menu for a logged in server as follows: right-click on the active server icon from the Navigator, then select OMEA Desktop > Show. Only one OMEA Applications window can be open at a time. To open OMEA applications for network elements in a specific domain (if you are logged in to servers from multiple domains), you must select the logged in server in the required domain when launching the OMEA Applications window. The OMEA Applications menu commands allow you to launch OMEA applications, depending on your access privileges. For more information, see OMEA Security Administration Guide, 450-3121-351. Menus are organized to support the user roles. For example, the contents of the Security menu will normally be used in the OMEA Administrator role.
The use of specific menu commands is described in the procedures of the OMEA documentation. However, the best way to become familiar with menu contents is to explore them on the system. OMEA Applications window management The enhanced navigation and window management features supported for the OMEA Applications window allows you to optimize and customize interaction with the OMEA user interface. You can use the following methods to view and navigate OMEA administrative applications: Within a single OMEA Applications window, you can open multiple applications for NEs in a single domain. Each open application is represented by a tab in the window. To switch between applications displayed in a single OMEA Applications window, click on the tab for the application you want to view. You can view an administrative application in a window separate from the OMEA Applications window. To do so, click on the tab for the application, and drag the tab to an area outside the OMEA Applications window. The application appears in a separate window (undocked from the OMEA Applications window). The title bar of the new window identifies the application, and also contains a separate menu bar. You can then return the application back to the OMEA Applications window by selecting Return to main window from the Window menu that appears in the application window. When applications are undocked from the OMEA Applications window (as described in the previous item), you can easily toggle between the application window and the OMEA Applications window using the Window menu that appears in both windows. You can return all undocked applications to the OMEA Applications window by selecting Return all windows from the Window menu that appears in the OMEA Applications Window.
Navigating among applications

There are many ways to open the applications or refresh the content of an open application. Use the following general actions to navigate among element management applications: Use menus to select a command. Menus are provided in the OMEA Desktop window, OMEA Applications window, and some application windows. Click the menu and select the desired command. The commands clearly state the action they perform, or the action becomes clear when the command is selected. If you select a command that could affect performance, OMEA allows you to cancel the operation before proceeding.
Note: Some applications provide buttons that duplicate the function of a menu command. The procedures refer to the buttons because they provide the quickest access. Click an object. This action performs a function that is the normal next step you want to take. For example, clicking on an alarm in the Alarm Manager displays details for that alarm. Application windows (for applications launched from the OMEA Desktop window) may display information for objects you have pre-selected. For example, the Alarm Manager application displays an object pre-selected in the Navigator. Note: For supported applications, if multiple objects are selectable, use Control-click to select additional objects or shift-click to select a range of objects. Click a column header in a table to sort rows in the table by that column. Advanced sorting is also supported: to sort the rows in a table by multiple columns (sort within a sorted list), hold the Control key (for applications in the OMEA Applications window) or the Shift key (for the Alarm Manager) and then click the column headers in the required order (click the column header to use as the primary sort criteria, then click the column header to use as the secondary sort criteria, and so on).
NE Properties
The NE Properties application displays detailed information for a network element (see Figure 2-7). From this application, you can also edit the user ID, password, or AP NE ID; manage or delete a network element; and rediscover a network element. For a description of field values, see the OMEA Standard Operations Guide, 450-3121-301.
Figure 2-7 NE Properties window
Performance applications
Performance Monitoring refers to the continuous collection, analysis and reporting of the performance data of a managed network element. This analysis allows early detection of service degradations and facilitates preventive maintenance without interruption of service. Note: Performance Monitoring is supported on certain network elements (see Compatibilities on page 4-1). Performance measurement collection Network elements managed by OMEA collect a wide range of performance measurements (PM). These PMs are collected by OMEA and displayed in the OMEA performance monitoring applications. PMs are collected on a daily basis and you can also enable collection on a 15-minute basis. Note that instantaneous power measures (equipment PMs) from OM5000 NE are not stored in bins on the NE. They are referred to as unbinned measurements. Unbinned PMs are a snapshot of the instantaneous power readings and are taken every time PMs are collected. Thus if 15-minute PM collection is disabled, unbinned PMs are only taken daily. The Configure 15 Min PM Collection window allows you to enable or disable 15-minute PM collection by network element. Historical PM Archive Browser PMs are archived on the OMEA for seven days by default. However it is configurable from 1 to 31 days. The storage interval is dependent on the disk space available (see Engineering considerations on page 5-1). The Historical PM Archive Browser (Figure 2-8) lets you search for and examine collected PMs, on a per 15 minute, per day, or unbinned basis. The PM archive is fully available to users with read, or read/write/admin permissions, from the Performance menu on the OMEA Applications window. You can use the search criteria in the Browser to locate the specific PMs. Once you have retrieved the required historical PMs, you can save them to a file for further analysis.
Optical Manager Element Adapter applications 2-15 Figure 2-8 PM Archive Browser application
Security applications
Security policy involves the selection of actions for the system to take upon detection of a security situation, and the establishment of thresholds for the system to detect security situations. For example, you may select that after three unsuccessful login attempts, a user account is disabled for one minute. Security policy applies to users who access the OMEA Desktop and to users who access some managed network elements through the craft or TL1 interfaces. Changes to security policy are made at OMEA and are distributed to applicable network elements for application to craft interface users. RADIUS authentication can be enabled for certain network element types (see Compatibilities on page 4-1). The availability of menu commands and the appearance of resources in lists depends on user privileges. For more details on security applications and features, refer to the OMEA Security Administration Guide, 450-3121-351.
Event Browser and Audit Trail The Event Browser application provides access to logs for the OMEA server. All service-affecting actions are captured and stored on the OMEA server. The Event Browser application then allows users to query and view logs based on criteria such as event type, whether the logs are for the server or the NE, and date and time interval. By default, 7 days of logs and events are stored on the server. This value is configurable up to 31 days. The storage interval is dependent on the disk space available (see Engineering considerations on page 5-1). Logs viewed in the browser can then be stored in a file in CSV (comma separate variable) format in order to generate or print reports. The Audit Trail functionality in OMEAs security application runs a daily audit. Logs generated during the audit can then be viewed by users using the Event Browser application. Audits identify and disable dormant accounts, and synchronize user profile information on managed network elements. After the network element is commissioned, the audit synchronizes user profile data on that network element with OMEA security data. Only users with Security Administration application privileges can view security logs. Logs which are generated and stored in the OMEA server cannot be deleted by any user. Log records which are generated include information such as date and time for the event, user identification, description of the action, and resource accessed. Global Settings Global settings apply to all instances of affected objects and are used by OMEA to detect security violations or to affect the object in violation in a certain way or for a certain time. Global settings are divided into several groups (see Figure 2-9). Each group is edited by selecting a different tab in the Global Settings editing dialog (See the OMEA Security Administration Guide, 450-3121-351 for details).
Optical Manager Element Adapter applications 2-17 Figure 2-9 Global Settings window
Some global settings are distributed to network elements within the OMEA span of control. See the OMEA Security Administration Guide, 450-3121-351 for details. Note: Global Settings are supported on certain network elements (see Compatibilities on page 4-1). Users and groups User accounts are used to log in to OMEA and use applications to manage network elements. Membership in user groups determine the permissions and privileges of a user. Level of access to network element types and to OMEA applications is defined for each user group. To provide the appropriate permissions to an individual user, you must perform the following tasks: Create a user account for the user. Add the user account to one or more user groups that provide the access to the required OMEA applications and network element types.
For more information, see the OMEA Security Administration Guide, 450-3121-351. User access privileges and permissions To access OMEA, a user must possess a user account and password. Each user account is a member of a user group. Each user group is assigned access privileges. Privileges are determined by security level and scope. Security levels include the following: read read/write read/write/admin Each application limits action based on security level. These limits are defined in the OMEA Security Administration Guide, 450-3121-351. A user gains resource access permissions by being a member of one or more user groups. Resources include server groups and network elements. Privileges are assigned by a security administrator (see OMEA Security Administration Guide, 450-3121-351 for further information). Password policy To maintain security, passwords must be closely guarded. Passwords stored in the OMEA server are encrypted. The following measures apply to passwords: Password must conform to requirements such as minimum length, and a number of alphabetic, numeric, and special characters all of which are defined by the administrator. Your password expires after a prescribed time which is defined by the administrator. Users must change their password before it expires. The administrator provides users with the specific requirements. OMEA indicates the reason when a new password is not accepted. OMEA also reminds users when they need to change their passwords. The Change Password application is available to all users from the Security menu in the OMEA Desktop window. Account activity information Activity information is collected on each user account for the purpose of alerting users if any inappropriate activity has occurred with their account. When a user successfully logs in, a warning message is displayed that indicates whether an unauthorized login attempt has been made using that users account.
The following information is displayed in the warning message: date, time, and location identifier (where available) of the last successful access to the network element or OMEA using this account number of unsuccessful attempts to gain system access to the network element or OMEA since the last successful access by this user account network-wide account activity information, pertaining to the last login anywhere in that network by this user account
Network Element Backup and Restore

OMEA performs daily backups for each NE supported by the application. The NE backup and restore application is also used to schedule a one-time backup, schedule the frequency of backups, or perform an immediate backup of NE data, and to restore data to an NE from a previous manual or automatic backup. A data backup involves the transfer of various information from the NE to a database in OMEA. The type and amount of data included in the backup varies with NE type. Note: Backup and Restore is supported on certain network elements (see Compatibilities on page 4-1). OMEA maintains data backups for each NE. You can configure the number of backup files that are maintained (the configurable range is from 3 to 31, the default is 5). When the maximum number of backups is surpassed, the oldest unlocked backup file is deleted automatically in order to store the most recent backup. Note: You can lock one backup file. A locked backup file is maintained on the server and is not deleted automatically when the maximum number of backups is surpassed. If you want the locked backup file to be deleted automatically, you must first unlock it. You can restore any of the available backups. You can backup and restore data for one or more NEs. NE backups are taken: automatically, within one hour after enrollment on OMEA automatically, depending on the configured frequency (the default is daily) manually, at a user defined time Backup files for a network element are retained when the NE is de-enrolled from OMEA.
Considerations for redundant server configurations If you have deployed a redundant pair of OMEA servers, manual backups are stored only on the server from which the backup was initiated. Manual backups are not copied to the other server in the redundant pair. Automatic backups are performed independently on each server in the redundant pair, according to the automatic backup schedule. NE Backup and Restore user interface The NE Backup and Restore application (see Figure 2-10) is used to find and select a target for a data backup or restore schedule automatic backups or perform a one-time backup
Figure 2-10 NE Backup and Restore application
3-1
Computing platform requirements

This chapter provides information on products compatible with Optical Manager Element Adapter (OMEA).
3-
OMEA server requirements

The OMEA server consists of the hardware platform and the software packages. The hardware platform supports and provides the resources for the software packages, from the OS to the OMEA server software. The hardware platform provides the physical link that underlies the data communications network and the means of access either locally or remotely. The system software provides the interface between the OMEA applications and the hardware platform. The system software provides platform management, monitoring functionality, and allows the OMEA applications to use the resources from the hardware platform. WARNING The engineering limits were calculated using a specific workstation / server type detailed within this section. If a higher performance workstation / server is used to exceed the stated engineering limits for the number of NEs per workstation, Nortel Networks does not accept responsibility, or provide support for, any performance-related issues which may arise as a result. Nortel Networks agrees only to provide support for problems that are non-performance related when the engineering limits are exceeded. Customers should also be aware that surpassing these prescribed limits may lead to behavior which may not be initially perceived to be performance related i.e. corruption, core dumps, etc. In summary, responsibility for any performance-related issues which arise as a result of surpassing the prescribed engineering limits must be understood and accepted by the customer.
3-2 Computing platform requirements
Hardware specifications This section presents the hardware requirements that are valid for OMEA workstations / servers. The hardware is divided into recommended systems, which should be acquired for all new deployments, and supported legacy systems, which include all previously recommended systems that are still supported.
Recommended platforms
The supported hardware platforms for OMEA are: Sun Fire V880, minimum 1.2Ghz, 8 CPUs, minimum 32 Gbyte RAM (memory), minimum 6x 73 Gbyte SCSI (disk space) Sun Fire V440 or Netra 440, minimum 1.28Ghz, 4 CPUs, minimum 16 Gbyte RAM (memory), minimum 4x 73 Gbyte SCSI (disk space) Sun Fire V240 or Netra 240, minimum 2 CPUs at a minimum of 1.28Ghz, minimum 8 Gbyte of RAM (memory), 2 x 73 Gbyte SCSI (disk space) Sun Fire 280R, minimum 2 CPUs at a minimum of 1.2Ghz, minimum 8 Gbyte of RAM (memory), 2 x 73 Gbyte SCSI (disk space) Note 1: The disk space indicated above is recommended as OMEA may use more disk space in a future release. Even if 18 Gbyte SCSI (disk space) is the minimum disk space required (36 Gbyte is the minimum disk size offered by Sun for a V240, 73 Gbyte is the minimum disk size offered by Sun for a V440 and V880), more disk space may be required depending on the configuration setting for PMs, Logs and event storage. For more information, refer to Disk space requirements on page 5-3. Note 2: Some hardware (for example, 280R CPU at 750Mhz) may have been discontinued by the manufacturer; legacy support for hardware exists only while Sun continues to provide hardware or software support for that particular hardware. Note 3: A Sun Fire V880 can be equipped with the minimum recommendation of a Sun Fire V440, to be ready for future expansion on the server. If you do so, the Sun Fire V880 is considered as a Sun Fire V440 for OMEA Compatibilities and Engineering considerations. Also, a Sun Fire V880 can be equipped with the minimum recommendation of a Sun Fire V240, to be ready for future expansion on the server. If you do so, the Sun Fire V880 is considered as a Sun Fire V240 for OMEA Compatibilities and Engineering considerations. Note 4: A Sun Fire V440 can be equipped with the minimum recommendation of a Sun Fire V240, to be ready for future expansion on the server. If you do so, the Sun Fire V440 is considered as a Sun Fire V240 for OMEA Compatibilities and Engineering considerations.
Computing platform requirements 3-3 Supported legacy platforms
The supported hardware platforms for OMEA are: Sun Fire V240, minimum 2 CPUs at a minimum of 1Ghz, minimum 4 Gbyte of RAM (memory), 2 x 73 Gbyte SCSI (disk space) Sun Fire 280R, minimum 2 CPUs at a minimum of 750Mhz, minimum 2 Gbyte of RAM (memory), 2 x 73 Gbyte SCSI (disk space) Note 1: The disk space indicated above is recommended as OMEA may use more disk space in a future release. Even if 18 Gbyte SCSI (disk space) is the minimum disk space required (36 Gbyte is the minimum disk size offered by Sun for a V240), more disk space may be required depending on the configuration setting for PMs, Logs and event storage. For more information, refer to Disk space requirements on page 5-3. Note 2: Some hardware (for example, 280R CPU at 750Mhz) may have been discontinued by the manufacturer; legacy support for hardware exists only while Sun continues to provide hardware or software support for that particular hardware.
Supported legacy platforms for OM5000 networks only
For OM5000 networks, there are other platforms that are supported for OMEA These platforms are: Sparc Ultra 80, 450Mhz, 2 CPUs, minimum 2 Gbyte RAM (memory), minimum 18 Gbyte SCSI (disk space) Sparc Ultra 60, 450Mhz, 2 CPUs, minimum 2 Gbyte RAM (memory), minimum 18 Gbyte SCSI (disk space). Note 1: Some of these platforms have been discontinued by the manufacturer; legacy support for hardware exists only while Sun continues to provide hardware or software support for that particular platform. Note 2: The OMEA software includes additional value-added Java-based desktop applications such as enhanced PM collection and viewing as well as enhanced security applications. These applications are more CPU and memory intensive than the standard mediation / AP device adaptation functions. As a result, OMEA operations (for example, server start-up (including NE discovery), desktop launch, PM collection and retrieval, event retrieval) performed using the supported legacy platforms (Sparc Ultra 60 / 80) have longer response times compared with the Sun Fire 280R or a Sun Fire V240 platform. Therefore, although OMEA desktop functions can be performed using the Sparc Ultra 60 / 80 supported legacy systems, these platforms are best suited for the day-to-day use of OMEA mediation functions such as AP Fault / Trail and craft reach through operations on smaller networks (110 NEs per platform). For optimal overall performance, including optimal performance of day-to-day OMEA desktop operations, a Sun Fire 280R or a Sun Fire V240 platform is recommended.
Note 3: 18 Gbyte SCSI (disk space) is the minimum disk space required. More disk space may be required depending on the configuration setting for PMs, Logs and event storage. For more information refer to Disk space requirements on page 5-3. Note 4: Refer to Engineering considerations on page 5-1 for the engineering limits associated with the different capacities. For more information, refer to the Sun Microsystems Web site at http://www.sun.com/documentation.
OMEA server software requirements

The following software components are required with OMEA: Sun Solaris operating system software (defined in Solaris OS requirements on page 3-5) must be installed prior to OMEA installation. Solaris software can be ordered from Sun Microsystems or from Nortel Networks (see OMEA software and documentation packages on page 6-2). Specific Solaris operating patches are required to operate OMEA (see Solaris OS Patches required for OMEA on page 3-6). The OM5000 series System Manager Interface (SMI) software must be installed on the OMEA platform for each release of the network element software in the network. Installation of the SMI software takes place after OMEA installation. See the OMEA Installation and Configuration Guide, 450-3121-201 and the OM5000 network element documentation. The OME6500 series Site Manager (SM) craft interface software must be installed on the AP. Installation of the SM software takes place after OMEA installation. See the OME6500 network element documentation. The CPL craft interface software must be installed on the AP. Installation of the CPL craft software takes place after OMEA installation. See the CPL network element documentation. The OME6110 craft interface software must be installed on the AP. Installation of the OME6110 craft software takes place after OMEA installation. See the OME6110 network element documentation.
Computing platform requirements 3-5
Solaris OS requirements The Sun Solaris operating system (OS) is required to support the OMEA server software. OMEA software is supported on the versions of Solaris specified below. WARNING The OMEA product has been verified using the Solaris OS versions documented in this section. All feature validation, engineering characterization, and product certification performed by Nortel Networks has been performed with these OS versions. Nortel Networks supports platforms and configurations, including OS and patch levels, as specified in this document. Nortel Networks does not accept any liability related to the installation of other OS versions not tested and certified by Nortel Networks.
Recommended Solaris OS
OMEA 3.0 is baseline on Sun Solaris 9 (SUN 5.9) operating system (OS). baseline Solaris 9 Version 12/03 OMEA is moving away from a fixed OS release/version and Nortel Networks will periodically validate new Solaris OSes released by Sun Microsystems. The latest release/version of Solaris OSes supported by OMEA 3.0 can be found at the Nortel Networks Web site, as follows: Go to the Nortel Networks Web site, http://www.nortelnetworks.com. In order to view the latest release/version of Solaris OS supported by OMEA 3.0, you must be a registered user and have a valid user ID and password. Select the Support & Training link. Select the Browse product support tab. Select the Product Families link. Select the Preside family link. Find the Preside for Optical Networks Operating System heading, and select the Documentation link below it. Use the document(s) available under the Documentation tab to identify the latest release/version of Solaris OS supported by OMEA 3.0.
The link is updated periodically. Refer to the Nortel Networks Web site for the most up-to-date information.
All other software tools and drivers necessary for the basic setup of the platform are included as part of the Sun Solaris standard release English or Multilingual server media kit CD-ROMs. The documentation is supplied on a separate CD with the Sun Solaris kit and is also available at http://www.sun.com/documentation. The Solaris Advanced Installation Guide provided by Sun provides detailed procedures to install the Sun Solaris OS. During the installation, you must set certain commissioning parameters. Solaris OS Patches required for OMEA After the Solaris operating system (OS) installation, a series of Nortel Networks recommended OS patches must be applied. WARNING Sun Microsystems can be contacted to obtain the latest patch versions. However, this software has been verified against a specific set of patches. Installation of any additional patches other than the ones listed or provided is not supported, and Nortel Networks does not accept responsibility, or provide support for any related issues which may arise as a result. Customers should also be aware that installing any additional patches may lead to undesirable behavior (performance related, corruption, core dumps, etc). In summary, responsibility for any issues which arise as a result of installing additional patches besides those listed or provided must be understood and accepted by the customer.
Recommended Solaris patch bundle
Nortel Networks periodically validates new Solaris patch bundles released by Sun Microsystems. This information can be found at the Nortel Networks Web site, as follows: Go to the Nortel Networks website, http://www.nortelnetworks.com. In order to download the recommended patches you must be a registered user and have a valid user ID and password. Select the Support & Training link. Select the Browse product support tab. Select the Product Families link. Select the Preside family link. Find the Preside for Optical Networks Operating System heading, and select the Documentation link below it. Use the document(s) available under the Documentation tab to identify the name of the latest recommended software patch package that applies to Solaris OS.
Select the Software tab. A list of software available is displayed. Find the name of the software patch package you need, and the select the link. Download the software and the corresponding Readme file.
The recommended software patch package is updated periodically. Refer to the Nortel Networks Web site for the most up-to-date information. The Readme file contains the most recent details on how to apply the patches to your system. Configuring the default router You must configure the /etc/defaultrouter file with the IP address of the router interface that connects the OMEA server to the network. Log in to the workstation as a root user. Create or modify the /etc/defaultrouter file using a text editor to include a one-line entry defining the IP address of the default router. For the default router to take effect, reboot the system using the reboot command. Partitioning information The OMEA server requires the following file partitioning for the disk where OMEA software is installed:
Partition Minimum partition size (in MB) Refer to Recommended platforms for Hard Disk size
/ (root) (Slice 0) swap (Slice 1) all remaining, after allocation of Swap 4096 It is recommended that the swap size should be twice the size of total RAM installed on the server total disk space UFS Swap
File system
overlap (Slice 2)
N/A
Note: Slice 2 overlap cannot be changed, as it is the total disk space.
hostname requirement The UNIX hostname cannot be greater than 9 characters. Note: The OMEA Desktop hangs if launched against an OMEA Server that has a UNIX hostname of 10 or more characters.
Kernel parameters The OMEA server kernel parameters must have the values as stated in the following table. All other parameters that are not in the table should be configured as per the default values. The OMEA kernel parameters are set automatically during installation.
Kernel Parameter msgsys:msginfo_msgtql msgsys:msginfo_msgmnb shmsys:shminfo_shmmax shmsys:shminfo_shmmni semsys:seminfo_semmns semsys:seminfo_semmni semsys:seminfo_semmsl semsys:seminfo_semopm semsys:seminfo_semvmx rlim_fd_cur rlim_fd_max Value 1024 65536 4294967295 400 2048 126 260 100 32767 1024 1024
Modify system files to enable remote root access (optional) If you want to enable remote login access to the workstation as root, you need to modify the /etc/default/login file using a text editor. Comment out the line CONSOLE=/dev/console by placing a # symbol in front of it. If you want to enable remote file transfer protocol (FTP) access to the workstation as a root user, you need to modify the /etc/ftpusers file using a text editor. Delete the line containing the word root.
OMEA client specifications

The client desktop PC or Sun workstation must meet the following requirements: CPU 400 MHz, RAM 256 MB, Hard Disk 500 MB Ethernet/fast Ethernet NIC card with RJ-45 connection one of the following operating systems: Windows 2000 (SP4), Windows XP (SP1a), and Solaris 9 OS 12/03 or later. Graphics video/driver supporting 16-bit colors and Standard Color Monitor (256-color operation is supported, but with diminished color precision.) For the client desktop machine, it is assumed that the OMEA-compatible OS is pre-installed; the Ethernet port is properly configured with TCP/IP protocol; a Web browser (Netscape or Internet Explorer) is pre-installed; and the display colors setting is set to 256 colors or higher.
4-1
Compatibilities
This chapter provides information on products compatible with the Optical Manager Element Adapter (OMEA) release.
4-
Optical Manager Element Adapter release 3.0 compatibility

You can integrate Optical Manager Element Adapter with the following systems (see Table 4-1 on page 4-2 for more detail): Applications Platform release 9.2.1, 9.2.1 SP1 and 10.1. OM 5100 and 5200 release 5.0, 6.0, 6.1 and 7.0 OME 6500 release 1.0 and 1.1 CPL release 1.0 (see note 1) OME 6110 release 1.0 OMEA support for CPL has been formally verified with OMEA 3.0 and CPL 1.0. The following functions are currently supported: fault management, NE discovery, and OMEA Backup and Restore. Note that Craft Launch is not currently supported from either Applications Platform or OMEA. A separate browser application must be used and the NE IP address available from the OMEA CPL NE Properties tab may be used to initiate a craft login. OMEA 3.0 is compatible with AP release 9.2.1, 9.2.1 SP1 and 10.1. See Table 4-1 for AP applications compatibility.
4-2 Compatibilities Table 4-1 ONM AP 9.x and 10.1 functionality available with OMEA by NE release Feature content enabled with OMEA (see Note1) ONM AP 9.2.1, 9.2.1 SP1, 10.1 OMN AP Core NE Discovery Craft and TL1 reachthrough (see Note8) Optical Manager Element Adapter (OMEA) login Fault Management Shelf-level graphics Remote Inventory Electronic Software Delivery Connection Management Facility Provisioning Performance Monitoring Traffic display OMEA Applications Global Settings Event Browser RADIUS enabled Optical applications Optical Section View Optical Power Management DWDM View OCM Trail Management Trail Manager Other Applications Back Up & Restore Software Upgrade Manager AP Historical Fault Browser Trouble Ticketing Federated View Manager No Yes Yes Yes Available via craft and OMEA No Yes Yes Yes
continued
NE Releases OM5000 5.0, 6.0, 6.1, 7.0 Yes Yes Yes Yes OME6500 1.0, 1.1 Yes Yes Yes Yes CPL 1.0 OME 6110 1.0
Yes Yes Yes Yes No
Yes Yes Yes Yes Available via craft
Available via craft
Available via craft Available via craft Available via craft Available via craft Available via craft and OMEA No No No No No No
Yes (see Note2) Yes (See Note3) Yes (See Note4) Yes (See Note4) Yes Yes (see Note2) No No No No Yes Yes No No No No No Yes (see Note7) Yes Yes No No No No No Yes No No No No No No Available via craft No Yes Yes Yes No Yes Yes Yes
Optical Connection Manager (OCM)
Compatibilities 4-3 Table 4-1 (Continued) ONM AP 9.x and 10.1 functionality available with OMEA by NE release Feature content enabled with OMEA (see Note1) ONM AP 9.2.1, 9.2.1 SP1, 10.1 North Bound Interfaces External Alarm Interface Fault Management Building Block (FMBB) Remote Management Building Block (RMBB) (see Note5) Performance Management Building Block (PMBB) Trail Management Building Block (TMBB) Corba TMF814 Yes Yes No Yes Yes No Yes Yes No Yes Yes No OM5000 5.0, 6.0, 6.1, 7.0 NE Releases OME6500 1.0, 1.1 CPL 1.0 OME 6110 1.0
No No Yes (see Note6)
No No No
No No No
No No No
Note 1: Some applications are available via AP reachthrough to craft and/or via AP reachthrough to OMEA. This is indicated in the table. Note 2: Available only with OM5000 release 6.1 and 7.0. RADIUS is not supported on OM5000 release 5.0 and 6.0, therefore the following associated RADIUS Global Settings are not distributed to these elements.
Login attempts Lockout period Inactivity period Warning message lines (example: Login failed due to password expiration) Challenge response secret
Note 3: RADIUS is not supported by the OME6500 release 1.0 NE. Therefore the associated RADIUS Global Settings are not supported for this element. Global Settings are only applicable to OMEA users. Note 4: The Warning Message is not supported for this element type. Note 5: Even though RMBB is not supported, OMEA 3.0 supports the NE discover subset of RMBB for the use of Historical Fault Browser. Note 6: Available only with AP 10.1, CORBA TMF814 subset supported are fault, GUI cut-through and logical inventory. Note 7: Trail Management 4.2.x is not supported for OME 6500 releases 1.0 and 1.1.Trail Management in only available for OME6500 release 1.1, not supported by the OME6500 release 1.0. For OME6500 release 1.1, low-order SONET provisioning is not supported by Trail Management. Note 8: Network element reach through not supported from OMEA Sun desktop.
4-4 Compatibilities
Supported upgrade paths Upgrade to OMEA is supported from Network Element Adapter (NEA) release 1.x configured as standalone or redundant pair. Also, OMEA upgrades from release 2.0 /2.2 to 3.0 are supported. Contact your Nortel Networks representative for information and procedures. The supported upgrade paths for are: Upgrade from a non-resilient NEA R1.2 to OMEA 3.0 Upgrade from a non-resilient with forklift platform NEA R1.2 to OMEA 3.0 Upgrade from a resilient NEA R1.2 to OMEA 3.0 Upgrade from a non-resilient OMEA 2.0 / 2.2 to OMEA 3.0 Upgrade from a non-resilient with forklift platform OMEA 2.0 / 2.2 to OMEA 3.0 Upgrade from a resilient OMEA 2.0 / 2.2 to OMEA 3.0
5-1
Engineering considerations
Specific rules must be followed when engineering and installing an OMEA network. These rules cover: OMEA deployment rules bandwidth requirements OMEA capabilities Note: OMEA support for CPL has been formally verified with OMEA 3.0 and CPL 1.0. The following functions are currently supported: fault management, NE discovery, and OMEA Backup and Restore. Note that Craft Launch is not currently supported from either Applications Platform or OMEA. A separate browser application must be used and the NE IP address available from the OMEA CPL NE Properties tab may be used to initiate a craft login. WARNING The engineering limits were calculated using a specific workstation type detailed in the tables provided within this section. If a higher performance workstation/server is used to exceed the stated engineering limits for the number of NEs per workstation, Nortel Networks will not accept responsibility, or provide support for, any performance related issues which may arise as a result. Nortel Networks agrees only to provide support for problems that are non-performance related when the engineering limits are exceeded. Customers should also be aware that surpassing these prescribed limits may lead to behavior which may not be initially perceived to be performance related i.e. corruption, core dumps, etc. In summary, responsibility for any performance-related issues which arise as a result of surpassing the prescribed engineering limits must be understood and accepted by the customer.
5-
5-2 Engineering considerations
Deployment rules
The following provides the engineering rules related to software requirements when you install OMEA in integrated and standalone configurations. These rules cover the Applications Platform as well as the Sun/Solaris workstations: When you deploy OMEA, the following engineering rules apply: OMEA servers (in dual active mode) act as mediation servers into AP OMEA requires a dedicated server and cannot be installed co-resident with other Nortel Networks network management applications For OMEA installation procedures, refer to the OMEA Installation and Administration Guide, 450-3121-201. Applications Platform Before you install OMEA, ensure that the workstation for the Applications Platform has the required/supported software (see Compatibilities on page 4-1). For a complete list of the software and hardware requirements for the Applications Platform, refer to the Applications Platform Planning Guide.
15-minute PM collection
The maximum number of NEs for which 15-minute PM collection can be enabled on the SunFire 280R/V240/V440/V880 is 25% of the maximum number of network elements. It is recommended that 15-minute PM collection is enabled on no more than 50 NEs on the Sparc Ultra 60 / 80 legacy supported platforms. OMEA and network elements Table 5-1 lists the supported capacities as a maximum number units for the OMEA server types. Table 5-2 describe the equivalency unit for each NE. OMEA can manage a combination of NE types per server and cannot exceed the maximum equivalency unit from Table 5-1.
Table 5-1 Maximum number of units supported per OMEA server type Maximum number of Units Server platform Sun Fire V880 Sun Fire V440 Sun Fire 280R and V240 SPARC Ultra 60 / Ultra 80 See: Table 5-2 for unit description 600 600 400 110 (OM5000 only)
Engineering considerations 5-3 Table 5-2 Network Element equivalency Unit for the OMEA servers NE release NE Equivalency Units OM5000 5.0 / 6.0 / 6.1/ 7.0 1.0 OME 6500 1.1 Full VT No VT manage- management ment 2 8 2 1.0 1.0 CPL 1.0 OME 6100 1.0
when 25% of 15-min PM collection is enabled
1.0
Full PM collection
1.0 (see Note1)
16
N/A
N/A
Note 1: For OM5000 Release 7:

on V240, no more than 50 NEs out of 400 should have 15-min PM collection enabled on Ultra 60/80, no more than 28 NEs out of 110 should have 15-min PM collection enabled
For example, an OMEA running on a SunFire 280R will support up to 125 X OM5000 Release 6.0, 150 X OM5000 Release 6.1, 50 X OME6500 Release 1.0 (unit value of 2) and 75 X CPL Release 1.0
Disk space requirements

The requisite disk space requirement is dependent on two factors: Base data and the Network Element data. To determine the required disk space, use the following calculation: Disk Space Requirement = Base data + Network Element data
Base data The base data requirement for the Sun server is the cumulative requirement of the system (OS and swap) and the OMEA (application, database, logs and events).
Table 5-3 Base data requirement per server RAM (memory) size Cumulative requirement Server RAM size 2 GByte 4 GByte 8 GByte 16 GByte 32 GByte Reserved swap size 4 GByte 8 GByte 16 GByte 32 GByte 64 GByte Base data size 14 GByte 14 GByte 14 GByte 14 GByte 14 GByte 18 GByte 22 GByte 30 GByte 46 GByte 68 GByte Total base size
Network Element data The disk space requirement is dependent on the type and number of network elements managed by the OMEA server.
Table 5-4 NE Data Space requirement per network element NE type OM5000 Release 5.0/6.0/6.1 OM5000 Release 7.0 OME6500 Release 1.0 OME6500 Release 1.1 CPL OME6110 26 Mbyte 41 Mbyte N/A N/A N/A 82 Mbyte N/A N/A 20 Mbyte N/A PM NE data size per day 5 Mbyte With VT management N/A
For example, OMEA running on a V240 platform, with 4GB RAM, managing 100 OM5000 Release 5, 100 OM5000 Release 6.0, 100 OM5000 Release 6.1 and 100 OM5000 Release 7.0 for 1 days. The disk space requirement would be (14 + 3.6) = 17.6 GByte.
Engineering considerations 5-5
Bandwidth requirements
TCP/IP connections between all workstations and network elements are required. The OMEA graphical user interface client requires IP connectivity through the DCN of the customer. The following table lists the recommended bandwidth for connections
Table 5-5 OMEA bandwidth requirement. Communications channel OMEA OM5000 Release 5.0 - 7.0 CPL Release 1.0 OME6500 Release 1.0 OME6500 Release 1.1 with 15 PM with PM enabled OM6110 Release 1.0 OMEA OMEA PC client Applications Platform Recommended bandwidth 128 kbits/s per NE 128 kbits/s per NE 150 kbits/s per NE 200 kbits/s per NE 128 kbits/s per NE 256 kbits/s per client 1.5 Mbits/s per OMEA GUI\craft session [maximum of 100Mbps] OMEA Between Resilient Pairs 1.544 Mbit/s
Note: When operating with a low bandwidth connection and using Xterminal emulator (as Exceed) onto AP, delays in windows refreshed/redrawn could occur. See the Network requirements section in the AP Planning Guide for minimum requirements.
OMEA capabilities
The following tables list the OMEA engineering capacities, when installed on the supported platforms. Table 5-6 lists the supported OMEA desktop capacities as a maximum number of units for the OMEA server types. Table 5-7 describes the equivalency unit for each OMEA desktop type. OMEA can manage a combination of NE types per server and cannot exceed the maximum equivalency unit from Table 5-6.
Table 5-6 OMEA Desktop Unit scalability Maximum number of Equivalent desktop sessions per server type Server platform Sun Fire Sun Fire SPARC Ultra 280R V240 60 / 80 OMEA Desktop (OM5000 only) 8 25 25
Sun Fire V440 40
Sun Fire V880 50
Table 5-7 OMEA Desktop GUI Equivalency Unit scalability Equivalency unit per OMEA desktop sessions supported on OMEA server per server type Server platform SPARC Ultra Sun Fire Sun Fire Sun Fire Sun Fire 60 / 80 280R V240 V440 V880 OMEA Desktop (OM5000 only) AP reach-through to 2 2.5 2.5 2.5 2.5 OMEA desktop PC or SUN client to 1 1 1 1 1 OMEA desktop
For example, OMEA running on SF 280R will be able to support a mix of PC Desktop clients and OMEA AP reach-through desktop.
Example: 20*PC clients + 2*AP reach-through OMEA desktop client = 25 clients
Table 5-8 lists the supported AP NE reachthrough capacities as a maximum number for each OMEA server type.
Engineering considerations 5-7 Table 5-8 AP NE reachthrough scalability Maximum number of reachthrough sessions supported per OMEA server Server platform Sun Fire Sun Fire Sun Fire SPARC Ultra 280R V240 V440 60 / 80 OMEA Desktop (OM5000 only) AP reachthrough to 8 10 10 18 OM5000 NE craft (SMI), see Note 1
Sun Fire V880 20
Note: OME 6500, OME6110 and CPL craft are installed on AP and AP reachthrough is limited by the AP. For more details, refer to AP <Release> Planning Guide, 450-3101-601 or related NE craft NTPs
Table 5-9 lists the supported OMEA NE reachthrough capacities as a maximum number for each OMEA server type.
Table 5-9 OMEA Desktop Network element reachthroughs for PC client Maximum number of reachthrough sessions supported on PC
Note: OMEA Sun desktop does not support network element reach through.
OMEA Desktop PC client
Reach through to OM5000 craft (SMI) Reach through to OME 6500 1 craft (SM) Reach through to OME 6110 OME6110 crafts have a Web-based user craft interface. The number of instances you can run on a single PC is equivalent to the number of Web browser instances you can run from that single PC and therefore is limited only by the PC system resources. Reach through to CPL craft CPL crafts have a Web-based user interface. The number of instances you can run on a single PC is equivalent to the number of Web browser instances you can run from that single PC and therefore is limited only by the PC system resources.
Maximum Number 5
Firewall considerations In order for OMEA to function correctly in a firewall environment, the ports listed in the following tables must be opened:
Table 5-10 OMEA / AP Firewall (also required between redundant OMEA servers)
Port End-point Application where port is used Both echo TCP or UDP based TCP Description
Standard echo session port. For external clients such as Exceed to determine the server availability before establishing connection.
Note: This may cause delays if the Exceed session is being established through a firewall.
20 Both FTP TCP Standard FTP data session port. For an external FTP client, using passive FTP mode, this port is not used. For an external FTP client, using active FTP mode, this port is used by the OMEA FTP server to initiate the FTP data connection. For an internal FTP client, using active FTP mode, the OMEA FTP client receives FTP data connection requests from this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. System Manager installed on OMEA uses passive FTP to the System Manager on the Optical Metro 5100/5200. TL1 upgrades, backups and restores use active FTP, with the client on the NE. 21 Both FTP TCP Standard FTP control session port. For an external FTP client, using active or passive FTP mode, the OMEA receives FTP control session requests on this port. For an internal FTP client, in active FTP mode, the OMEA initiates FTP control session requests to this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. System Manager installed on OMEA uses passive FTP to the System Manager on the Optical Metro 5100/5200. TL1 upgrades, backups and restores use active FTP, with the client on the NE. 23 Both TELNET TCP Used for technical support access to OMEA and AP. For use during NEA to OMEA upgrades, AP reachthrough to OMEA Desktop, and AP Reachthrough to SMI and Site Manager. AP provides Telnet access to OMEA from the AP Graphical Network Browser.
continued
Engineering considerations 5-9 Table 5-10 (Continued) OMEA / AP Firewall (also required between redundant OMEA servers)
Port End-point Application where port is used OMEA HTTP TCP or UDP based TCP Description
80
Used to launch System Manager. Used by OMEA Desktop to establish connection to the OMEA Server.
123
OMEA
NTP
TCP / UDP
Standard NTP port. For use on OMEA platforms to align time using NTP. In asymmetric (Peer-to-Peer) mode, two devices share NTP information and maintain state information during the exchange of time information. Both hosts use UDP port 123 for communication. When port 123 is used for both the source and destination port numbers, it signals the receiver that asynchronous mode is being used. In Symmetric (Client-Server), Clients request time from servers and the servers respond without using any state information. In this mode, a request is sent to destination port 123 on the server and a different source port is used for the client. The different port numbers indicate which device is acting as server and which as client.
162
OMEA
SNMPTRAP FTP
UDP TCP
Standard SNMP trap listening port used only by 3rd-party SNMP based management stations. When the NE acts as the FTP client in active FTP mode, a port in this range will be used to receive an FTP data connection from port 20 on an external FTP server. TL1 upgrades, backups and restores use active FTP, with the client on the NE. RADIUS requests are sent to this port by default, however the port number is provisionable. Any change to the default value would require a corresponding change to firewall settings. System Manager accesses this port for session management.
1024 to 5000 Remote
OMEA 1812 (included in 1024 to 5000 port) OMEA 1966 (included in 1024 to 5000 port) 6000-6020 14001 Both OMEA
RADIUS
UDP
Session Manager (SMI) X-Based Login TELNET
TCP
TCP TCP
For use in OMEA, SMI, & Site Manager reachthroughs from AP. TL1 port used between OMEA and AP.
continued
5-10 Engineering considerations Table 5-10 (Continued) OMEA / AP Firewall (also required between redundant OMEA servers)
Port End-point Application where port is used Both REGD TCP or UDP based TCP Description
30001
Transient port used by the REGD process within OMEA's AP gateway feature. For use after AP has successfully validated an OMEA controller. AP uses this port to send a xdr message containing a permanent TCP port number which the OMEA will use to connect to the AP. As this is a transient port, the connection is dropped after it is no longer needed.
30002
Both
REGB
TCP
Transient port used by the REGB process within OMEA's AP gateway feature. For use when AP attempts to manage an OMEA controller to validate the controller details. As this is a transient port, the connection is dropped after the controller has been validated.
30101
Both
REGE
TCP
Transient port used by the REGE process within OMEA's AP gateway feature. For use when a Trail Manager attempts to manage an OMEA controller to validate the controller details. As this is a transient port, the connection is dropped after the controller has been validated.
33359
OMEA
NDS
TCP / UDP TCP / UDP
Standard administrator port for Directory services used within OMEA. Required by both server and desktop. Standard LDAP port for Directory services used within OMEA. Required by both server and desktop.
33389
OMEA
NDS
Engineering considerations 5-11 Table 5-11 PC or SUN client desktop Firewall

Port End-point Application where port is used OMEA OMEA OMEA client PC OMEA client PC OMEA client RADIUS OMEA Desktop Tomcat Tomcat TCP or UDP based UDP TCP TCP TCP Description
1812 5433 8003 9012
RADIUS requests are sent to this port by default. Used for OMEA Desktop. This port is used from the service allowing the download of the PC client software from the OMEA server. Used for connection services between PC OMEA and OMEA server. Required for both server and PC desktop. Used for connection services between PC OMEA and OMEA server. Required for both server and PC desktop.
9014
OMEA client-OMEA server main connection service NDS
TCP
33359
PC OMEA client PC OMEA client
TCP / UDP TCP / UDP
Standard administrator port for Directory services used within OMEA. Required by both server and PC desktop. Standard LDAP port for Directory Services. Required for both server and PC desktop.
33389
NDS
5-12 Engineering considerations Table 5-12 OM5000 / OMEA Firewall

Port End-point Application where port is used Both FTP TCP or UDP based TCP Description
20
Standard FTP data session port. For an external FTP client, using passive FTP mode, this port is not used. For an external FTP client, using active FTP mode, this port is used by the OMEA FTP server initiates the FTP data connection. For an internal FTP client, using active FTP mode, the OMEA FTP client receives FTP data connection requests from this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. System Manager installed on OMEA uses passive FTP to the System Manager on the Optical Metro 5100/5200. TL1 upgrades, backups and restores use active FTP, with the client on the NE.
21
Both
FTP
TCP
Standard FTP control session port. For an external FTP client, using active or passive FTP mode, the OMEA receives FTP control session requests on this port. For an internal FTP client, in active FTP mode, the OMEA initiates FTP control session requests to this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. System Manager installed on OMEA uses passive FTP to the System Manager on the Optical Metro 5100/5200. TL1 upgrades, backups and restores use active FTP, with the client on the NE.
23
Both
Telnet
TCP
Used for technical support access to OMEA and AP. For use during NEA to OMEA upgrades, AP reachthrough to OMEA Desktop, and AP Reachthrough to SMI and Site Manager. AP provides Telnet access to OMEA from the AP Graphical Network Browser.
80
OMEA
HTTP
TCP
Used to launch System Manager. Used by OMEA Desktop to establish connection to the OMEA Server.
continued
Engineering considerations 5-13 Table 5-12 (Continued) OM5000 / OMEA Firewall

Port End-point Application where port is used OMEA NTP TCP or UDP based TCP / UDP Description
123
161
Remote
snmp
UDP
Standard SNMP access port. Used by System Manager and 3rd-party SNMP-based managers. In public-IP mode, all shelves are accessed using this port. In private-IP mode, this port is used to access the host shelf (a GNE). Ports 8001 to 8064 are used to access the remaining shelves (see below). When System Manager is used, SNMP traps are sent from this port on the NE to a random port on the System Manager workstation, determined on System Manager start-up.
162 179
OMEA Remote
snmptrap BGP
UDP TCP
Standard SNMP trap listening port used only by 3rd-party SNMP based management stations. Standard port used for BGP peer connections. Only used when BGP is provisioned as the GNE DCN gateway routing protocol. The connection may be initiated by either the Optical Metro 5100/5200 GNE or the external router. When the NE acts as the FTP client in active FTP mode, a port in this range will be used to receive an FTP data connection from port 20 on an external FTP server. TL1 upgrades, backups and restores use active FTP, with the client on the NE. RADIUS requests are sent to this port by default, however the port number is provisionable. Any change to the default value would require a corresponding change to firewall settings. System Manager accesses this port for session management.
1024 to 5000 Remote
FTP
TCP
OMEA 1812 (included in 1024 to 5000 port) OMEA 1966 (included in 1024 to 5000 port) 5566 Both
RADIUS
UDP
Session Manager (SMI) NE Upgrades
TCP
TCP
For use when upgrading NE software from OMEA platform.

continued
5-14 Engineering considerations Table 5-12 (Continued) OM5000 / OMEA Firewall

Port End-point Application where port is used Both NE Upgrades SNMP TCP or UDP based TCP UDP Description
5567
For use when upgrading NE software from OMEA platform. Used in private-IP mode only to access non-System Manager-host shelves. The specific port for a particular NE is (8000 + shelfID). Used by System Manager and 3rd-party SNMP-based managers. http For use by OMEA Mediation when gaining association with an NE. Standard debug port for TL1 terminal session.
8001 to 8064 Remote
8180 10001 10002
OMEA Both Both
HTTP OMEA Mediation TELNET
UDP TCP TCP
Engineering considerations 5-15 Table 5-13 CPL / OMEA Firewall

20
Standard FTP data session port. For an external FTP client, using passive FTP mode, this port is not used. For an external FTP client, using active FTP mode, this port is used by the OMEA FTP server to initiate the FTP data connection. For an internal FTP client, using active FTP mode, the OMEA FTP client receives FTP data connection requests from this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. TL1 upgrades, backups and restores use active FTP, with the client on the NE.
21
Both
FTP
TCP
Standard FTP control session port. For an external FTP client, using active or passive FTP mode, the OMEA receives FTP control session requests on this port. For an internal FTP client, in active FTP mode, the OMEA initiates FTP control session requests to this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. TL1 upgrades, backups and restores use active FTP, with the client on the NE.
23
Both
Telnet
TCP
80
OMEA
HTTP
TCP
Used to launch craft. Used by OMEA Desktop to establish connection to the OMEA Server.
continued
5-16 Engineering considerations Table 5-13 (Continued) CPL / OMEA Firewall

123
1024 to 5000 Remote
FTP
TCP
When the NE acts as the FTP client in active FTP mode, a port in this range will be used to receive an FTP data connection from port 20 on an external FTP server. TL1 upgrades, backups and restores use active FTP, with the client on the NE. RADIUS requests are sent to this port by default, however the port number is provisionable. Any change to the default value would require a corresponding change to firewall settings. For use by OMEA Mediation when gaining association with an NE. Standard debug port for TL1 terminal session.
OMEA 1812 (included in 1024 to 5000 port) 10001 10002 Both Both
RADIUS
UDP
OMEA Mediation TELNET
TCP TCP
Engineering considerations 5-17 Table 5-14 OME 6500 / OMEA Firewall

20
Standard FTP data session port. For an external FTP client, using passive FTP mode, this port is not used. For an external FTP client, using active FTP mode, this port is used by the OMEA FTP server to initiate the FTP data connection. For an internal FTP client, using active FTP mode, the OMEA FTP client receives FTP data connection requests from this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. TL1 upgrades, backups and restores use active FTP, with the client on the NE.
21
Both
FTP
TCP
Standard FTP control session port. For an external FTP client, using active or passive FTP mode, the OMEA receives FTP control session requests on this port. For an internal FTP client, in active FTP mode, the OMEA initiates FTP control session requests to this port on the external FTP server. Internal FTP client using passive FTP mode is not supported. TL1 upgrades, backups and restores use active FTP, with the client on the NE.
23
Both
Telnet
TCP
continued
5-18 Engineering considerations Table 5-14 (Continued) OME 6500 / OMEA Firewall
123
1024 to 5000 Remote
FTP
TCP
When the NE acts as the FTP client in active FTP mode, a port in this range will be used to receive an FTP data connection from port 20 on an external FTP server. TL1 upgrades, backups and restores use active FTP, with the client on the NE. RADIUS requests are sent to this port by default, however the port number is provisionable. Any change to the default value would require a corresponding change to firewall settings. For use by OMEA Mediation when gaining association with an NE. Standard debug port for TL1 terminal session.
OMEA 1812 (included in 1024 to 5000 port) 10001 10002 Both Both
RADIUS
UDP
OMEA Mediation TELNET
TCP TCP
Engineering considerations 5-19 Table 5-15 OME 6110 / OMEA Firewall

Port End-point Application where port is used Remote FTP TCP or UDP based TCP Description
20 and 21
When the NE acts as the FTP client in active FTP mode, a port in this range will be used to receive an FTP data connection from port 20 on an external FTP server. TL1 upgrades, backups and restores use active FTP, with the client on the NE. Standard NTP port. For use on OMEA platforms to align time using NTP. In asymmetric (Peer-to-Peer) mode, two devices share NTP information and maintain state information during the exchange of time information. Both hosts use UDP port 123 for communication. When port 123 is used for both the source and destination port numbers, it signals the receiver that asynchronous mode is being used. In Symmetric (Client-Server), Clients request time from servers and the servers respond without using any state information. In this mode, a request is sent to destination port 123 on the server and a different source port is used for the client. The different port numbers indicate which device is acting as server and which as client.
123
OMEA
NTP
TCP / UDP
161 873 162 2023
Remote Both OMEA Both
snmp NE snmptrap Telnet
UDP TCP / UDP UDP TCP
Standard SNMP access port. Used by craft and 3rd-party SNMP-based managers. rsync Standard SNMP trap listening port used only by 3rd-party SNMP based management stations. Used for technical support access to OMEA and AP. For use during NEA to OMEA upgrades, AP reachthrough to OMEA Desktop, and AP Reachthrough to SMI and Site Manager. AP provides Telnet access to OMEA from the AP Graphical Network Browser.
3021
Both
FTP
TCP
ftp on dual processor system.
Same as port 20 and 21

3023 Both Telnet TCP on dual processor system Same as port 2023. 10001 10002 Both Both OMEA Mediation TELNET TCP TCP For use by OMEA Mediation when gaining association with an NE. Standard debug port for TL1 terminal session.
continued
5-20 Engineering considerations Table 5-15 (Continued) OME 6110 / OMEA Firewall
Port End-point Application where port is used Both OMEA Telnet HTTP TCP TCP or UDP based Description
10059 20080
config-db, alive reporting Used to launch craft. Used by OMEA Desktop to establish connection to the OMEA Server.
20090
Telnet
TCP
debug port for an application to connect tcp port and SerialPort like rs232c
6-1
Ordering information
Software and documentation packages
This section provides the information you require to order Optical Manager Element Adapter software and related Optical Manager Element Adapter documentation. You can order the complete software and OMEA documentation package (as PDF files on CD), or paper copies of the documentation, as shown in the following table. The Sun Solaris operating system software and patches are not provided by Nortel Networks and are not part of the kits specified below; these must to be ordered separately from Sun Microsystems. See OMEA server software requirements on page 3-4. See Table 6-1 OMEA software and documentation packages for ordering PECs. ATTENTION
You must order ONE OMEA software kit (Application or upgrade) per installed server.
6-
6-2 Ordering information Table 6-1 OMEA software and documentation packages Product
Optical Manager Element Adapter 3.0 Application Kit
Description
PEC
Note: The LOC is not included.
Full OMEA software and documentation package. Includes the following items: NTNM16SE the software load on 2 CDs the OMEA documentation package with all related user guides on CD Optical Manager Element Adapter 3.0 PC Client Software CD OMEA Upgrade package Full OMEA software and documentation package. Includes NTNM16NE the following items: the software load on 2 CDs the OMEA documentation package with all related user guides on CD Optical Manager Element Adapter 3.0 PC Client Software CD OMEA Upgrade package Full OMEA software and documentation package. Includes NTNM16CE the following items: the software load on 2 CDs the OMEA documentation package with all related user guides on CD Optical Manager Element Adapter 3.0 PC Client Software CD OMEA documentation kit (bound, paper documents) NTNM16DE Optical Manager Element Adapter 3.0 Installation and Configuration User Guide Optical Manager Element Adapter 3.0 Standard Operations User Guide Optical Manager Element Adapter 3.0 Security Administration User Guide NTNM16LE
NEA to Optical Manager Element Adapter 3.0 Upgrade Kit
Note: The LOC is not included. Note 1: Upgrade PEC assumes a valid Server RTU for each server for which an upgrade is ordered (obtained by previously ordering an Application or Upgrade Kit).
Optical Manager Element Adapter 2.x Server Upgrade Kit
Optical Manager Element Adapter 3.0 Documentation Package
Optical Manager Element Adapter 3.0 Planning Guide Optical Manager Element Adapter 3.0 OMEA LOC documentation (bound, paper document) Operational Considerations (LOC) Optical Manager Element Adapter 3.0 Operational Considerations Legend: PEC = Product Engineering Code (Nortel Networks customer order code)
Nortel Networks
Optical Manager Element Adapter 3.0

Planning Guide
Copyright 2003 - 2005 Nortel Networks, All Rights Reserved The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. This 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 Networks, the Nortel Networks logo, and the Globemark are trademarks of Nortel Networks. Internet Explorer, Windows, and Windows NT are trademarks of Microsoft Corp. Netscape is a trademark of Netscape Communications Corp. Orbix is a trademark of Iona Technologies Corp. Sparc is a trademark of Sparc International, Inc. Sun, Sun Microsystems, and Solaris are trademarks of Sun Microsystems, Inc. UNIX is a trademark of X/Open Company Limited. 450-3121-601 Issue 2 January 2005 Standard Printed in Canada or in the United Kingdom

Planning Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Planning Guide

Загружено:

Авторское право:

Доступные форматы

450-3121-601

Optical Manager Element Adapter 3.0

Copyright 2003 - 2005 Nortel Networks, All Rights Reserved

Printed in Canada or in the United Kingdom

Optical Manager Element Adapter applications

Planning Guide 450-3121-601

Computing platform requirements

Optical Manager Element Adapter 3.0 Jan 2005 Standard

About this document

Technical support and information

Planning Guide 450-3121-601

vi About this document

Optical Manager Element Adapter 3.0 Jan 2005 Standard

About this document vii

North America 1-800-4NORTEL (except Mexico) (1-800-466-7835)

United Kingdom +44 (0)20-8920-4618 Africa Asia Pacific 27-11-808-4000 011-61-2-8870-8800

Planning Guide 450-3121-601

viii About this document

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter description

Planning Guide 450-3121-601

1-2 Optical Manager Element Adapter description

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter description 1-3

Planning Guide 450-3121-601

1-4 Optical Manager Element Adapter description

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter description 1-5

Planning Guide 450-3121-601

1-6 Optical Manager Element Adapter description

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter applications

New features and functionality

Planning Guide 450-3121-601

OMEA 3.0 new features:

OMEA 3.0 supports additional features for existing network elements:

OMEA 3.0 Application Platform (AP) related features:

OMEA Desktop introduction

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter applications 2-3

OMEA applications and commands

Planning Guide 450-3121-601

2-4 Optical Manager Element Adapter applications

Optical Manager Element Adapter 3.0 Jan 2005 Standard

OMEA Desktop window

Planning Guide 450-3121-601

Main menu bar

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter applications 2-7

Alarm counts area

2-8 Optical Manager Element Adapter applications

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter applications 2-9

Planning Guide 450-3121-601

2-10 Optical Manager Element Adapter applications

OMEA Applications window

Optical Manager Element Adapter applications 2-11

Navigating among applications

Planning Guide 450-3121-601

2-12 Optical Manager Element Adapter applications

Optical Manager Element Adapter 3.0 Jan 2005 Standard

Optical Manager Element Adapter applications 2-13

Planning Guide 450-3121-601

2-14 Optical Manager Element Adapter applications