Table Of Contents
Cisco Prime Optical 9.6 Quick Start Guide
Preface
Assumptions and Limitations of This Guide
Related Documentation
Obtaining Documentation and Submitting a Service Request
Installation Requirements
System Requirements
Server Requirements
Disk Space and Partition Requirements
VMware Support
Ports and Protocols
Southbound Ports
Client-Server Communication Protocols
Client Requirements
Preparing for Installation
Enabling SSH on the Prime Optical Server and Database Workstation
Preparing the Environment for a Single-Server Installation
Before You Begin
Installing Prime Optical
Preparing the Server for Prime Optical Installation
Installing Prime Optical on the Server
Verifying the Installation
Uninstalling Prime Optical
Next Steps
Launching the Client
Password Complexity Rules
Configuring a SOCKS Server
Getting Started with Prime Optical
Creating a SuperUser Account
Configuring a User for Server-to-NE Connection
(Optional) Configuring Automatic Alarm Acknowledgement
Enabling Automatic NE Backup
Verifying NE Automatic Backup
Verifying NE Support
Quick Start Guide
Cisco Prime Optical 9.6 Quick Start Guide
Revised: August 10, 2012, OL-27183-01
1 Preface
This guide will get you quickly up and running with Prime Optical 9.6.
Assumptions and Limitations of This Guide
If your Prime Optical deployment differs from what is described in these assumptions, see the Cisco Prime Optical 9.6 Installation Guide or contact your Cisco account representative for assistance with planning and installation of Prime Optical.
The guide assumes the following:
•
This is a new Prime Optical installation, not an upgrade from a previous version.
•The Prime Optical server and database will be installed on one workstation.
•The Prime Optical embedded database (Oracle 11g 11.2.0.1.0), not an external database, will be used.
•You are familiar with the following products and topics:
–Basic internetworking terminology and concepts
–Network topology and protocols
–Microsoft Windows 7 and Windows XP
–Red Hat Enterprise Linux administration
–UNIX environment
–Oracle database administration
–Telecommunications Management Network (TMN) architecture model
This guide does not cover the following:
•Integration
•Customization
•Package download
•Advanced configuration (for example, polling)
•High availability
•External database
•GateWay/CORBA installation
Related Documentation
See the Cisco Prime Optical 9.6 Documentation Overview for a list of Prime Optical guides.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
2 Installation Requirements
Review the prerequisites and recommendations for the hardware and software you need to support your Prime Optical deployment. These recommendations are based on the assumptions and target setup for this guide, as described in System Requirements. If your network setup is not covered by this guide, see the Cisco Prime Optical 9.6 Installation Guide.
The following topics are covered:
•System Requirements
•Server Requirements
•Ports and Protocols
•Client Requirements
System Requirements
Table 1 lists the platforms that are supported in Prime Optical.
Note The Prime Optical server must run on a dedicated workstation. Any application that is not explicitly listed in Table 1 as being required or supported by Prime Optical cannot be installed on the dedicated Prime Optical server workstation.
Table 1 Supported Platforms and Operating Systems
Platform
|
Operating System
|
Sun UltraSPARC-based server1
|
Sun Solaris 10, release 10/09 or later
|
Sun UltraSPARC T Series
|
Cisco UCS B series
|
One of the following:
•Red Hat Enterprise Linux (RHEL) 5.5 server 64-bit
•RHEL 5.6 or 5.7 server 64-bit (with or without VMware ESXi version 4.1 or 5.0)
|
Cisco UCS C series
|
Note the following:
•Prime Optical is not validated against required file systems (/oracle, /db01, /db02, /db03, /db04, /db05) of the Network File System (NFS) type.
•Prime Optical does not support local Solaris zones.
•If you are installing Prime Optical with Prime Central, Domain Name System (DNS) must be enabled on the Prime Optical server.
Table 2 lists the items required to install the Prime Optical server.
Table 2 Items Required to Install the Prime Optical Server
Requirement
|
Notes
|
Prime Optical installation DVDs
|
—
|
One of the following:
•Solaris Operating System 10 Media Kit, 64-bit
•Red Hat Enterprise Linux (RHEL) 5.5, 5.6, or 5.7, 64-bit
|
•During Solaris 10 installation, you are prompted to select software to install. Choose Entire Distribution plus OEM support—5641 MB.
•Make sure that your file systems are configured to allow large files. If this configuration is not applied, no single file can be larger than 2 GB, which can be problematic for large database installations of the Prime Optical server. Choose Include Solaris 64-bit support.
Note Enable the IPV6 networking option to install Linux.
|
Latest Solaris patch
|
•Visit the Oracle website for the most up-to-date patch information.
•When installing Solaris patches, you might receive a message saying, "This patch is obsoleted by patch number, which has already been applied to this system." This message indicates that an updated version of the patch is already installed, and no action is required.
•Always install Solaris patches in single-user mode.
•The setup program generates a warning if the following OS packages are missing:
–SUNWi1cs
–SUNWi15cs
|
Sun Microsystems Java Development Kit (JDK) Standard Edition version 1.6.0_33
|
•JDK is installed automatically for the Prime Optical server and Prime Optical GateWay/CORBA.
•Java Runtime Engine (JRE) 1.6 must be installed on the machine. If the client does not start, check that Java Web Start is associated to the browser with the correct javaws.
|
Oracle 11g software
For Solaris and Linux: 10404530
|
The Oracle product is available on CD or in .cpio file format.
|
Oracle 11g licenses
|
Oracle licenses can be purchased either for the server processor or for named users. For more information on Oracle named users, see the Cisco Prime Optical 9.6 Installation Guide.
|
GNU tar
|
Prime Optical uses GNU tar to extract files from archives. GNU must be installed on the Prime Optical server workstation.
|
Server Requirements
The following tables list hardware requirements for installing the Prime Optical server.
Table 3 lists the minimum processor requirements.
Note It is possible to use and configure disk arrays for database storage with any type of RAID layout. You can do so only if the disk throughput is equal to or higher than the throughput calculated for internal disks.
Table 3 Minimum Processor Requirements
Network Size
|
|
|
Small
|
1 x 4 cores
|
2 x Intel Xeon 5620
|
Medium
|
1 x 4 cores
|
2 x Intel Xeon 5620
|
Large
|
1 x 4 cores
|
2 x Intel Xeon 5620
|
High end
|
1 x 8 cores
|
2 x Intel Xeon 5640
|
Cisco tests the simulated network configurations using the Enterprise Edition Oracle database type listed in Table 4. Your setup and performance might vary depending on the size of your network and the usage pattern of management tasks.
Table 4 Recommended Specifications for the Prime Optical Server Installation
Network Size
|
RAM—Solaris (Sun Workstation)
|
RAM—Linux (UCS System)
|
RAM—Linux (VM)
|
No. of Network Partitions 1 ,2
|
|
Small
|
8 GB
|
24 GB
|
8 GB
|
1
|
200
|
Medium
|
16 GB
|
24 GB
|
16 GB
|
1
|
500
|
Large
|
32 GB
|
48 GB
|
32 GB
|
4
|
2000
|
High end
|
64 GB
|
96 GB
|
64 GB
|
8
|
5000
|
The following list describes the server configuration parameters and the effect of changes in each parameter on the maximum number of NEs the server can manage:
•Network Size—If the network size increases, more resources are reserved for the higher number of NEs to be managed.
•RAM—The server can manage more NEs as the RAM increases. The server can manage fewer NEs as the RAM decreases.
•Number of Network Partitions—For each network partition, the server reserves resources for the higher number of NEs to be managed. The server can manage more NEs as the number of network partitions increases. The server can manage fewer NEs as the number of network partitions decreases.
Disk Space and Partition Requirements
Table 5 and Table 6 show disk space and partition requirements for NEs based on network size and PM data collection status:
•The minimum disk space is the total space required for ,/swap, /cisco, /oracle, /db01, /db02, /db03, /db04, and /db05. (The minimum disk space does not include /ctm_backup or the optional partitions /db01_rd and /db02_rd.)
•The maximum disk space is the total space required for ,/swap, /cisco, /oracle, /db01, /db02, /db03, /db04, /db05, /db01_rd, /db02_rd, and /ctm_backup.
Caution Prime Optical
performance degrades if you do not use the recommended partition sizes. We recommend that you use the partition sizes described here.
•To improve database performance and maximize data input/output, configure a dedicated disk array with the following setup:
–Dynamic multipathing (DMP) to parallelize the file system access.
–Raid 0 (striping) to optimize the disk input data.
•Prime Optical is a high-transaction application that causes high I/O throughput for Oracle redo logs. We recommend that you reserve dedicated system controllers for file systems—including the optional /db01_rd and /db02_rd file systems—that manage redo logs.
Caution For large and high-end networks, if you do not follow the preceding disk striping recommendations, the I/O might create a critical bottleneck and cause an unexpected Prime Optical
shutdown.
Table 5 Disk Space and Partition Requirements—PM Collection Enabled
Network Size
|
Disk Space
|
/
|
|
|
/oracle
|
/db01
|
/db02
|
/db03
|
/db04
|
/db05
|
/db01_rd (optional)
|
/db02_rd (optional)
|
/ctm_ backup
|
Small
|
133 GB (min)
|
12 GB
|
12 GB
|
20 GB
|
10 GB
|
5 GB
|
6 GB
|
40 GB
|
30 GB
|
8 GB
|
1 GB
|
1 GB
|
101 GB
|
236 GB (max)
|
Medium
|
250 GB (min)
|
12 GB
|
24 GB
|
20 GB
|
10 GB
|
8 GB
|
16 GB
|
90 GB
|
70 GB
|
10 GB
|
2 GB
|
2 GB
|
208 GB
|
462 GB (max)
|
Large
|
458 GB (min)
|
12 GB
|
48 GB
|
20 GB
|
10 GB
|
10 GB
|
26 GB
|
190 GB
|
140 GB
|
12 GB
|
3 GB
|
3 GB
|
394 GB
|
858 GB (max)
|
High end
|
868 GB (min)
|
12 GB
|
96 GB
|
20 GB
|
10 GB
|
12 GB
|
50 GB
|
360 GB
|
300 GB
|
18 GB
|
4 GB
|
4 GB
|
758 GB
|
1634 GB (max)
|
Table 6 Disk Space and Partition Requirements—PM Collection Disabled
Network Size
|
Disk Space
|
/
|
|
|
/oracle
|
/db01
|
/db02
|
/db03
|
/db04
|
/db05
|
/db01_rd (optional)
|
/db02_rd (optional)
|
/ctm_ backup
|
Small
|
72 GB (min)
|
12 GB
|
12 GB
|
20 GB
|
10 GB
|
5 GB
|
6 GB
|
8 GB
|
7 GB
|
8 GB
|
1 GB
|
1 GB
|
40 GB
|
114 GB (max)
|
Medium
|
104 GB (min)
|
12 GB
|
24 GB
|
20 GB
|
10 GB
|
8 GB
|
16 GB
|
12 GB
|
10 GB
|
10 GB
|
2 GB
|
2 GB
|
62 GB
|
170 GB (max)
|
Large
|
154 GB (min)
|
12 GB
|
48 GB
|
20 GB
|
10 GB
|
10 GB
|
26 GB
|
20 GB
|
18 GB
|
12 GB
|
3 GB
|
3 GB
|
90 GB
|
250 GB (max)
|
High end
|
246 GB (min)
|
12 GB
|
96 GB
|
20 GB
|
10 GB
|
12 GB
|
50 GB
|
28 GB
|
24 GB
|
18 GB
|
4 GB
|
4 GB
|
136 GB
|
390 GB (max)
|
Note the following PM assumptions for optical NEs:
•In a small network, PM data collection assumes 30 days of storage for PM data collected across 200 NEs, assuming an average of 200 interfaces per NE, up to a maximum of 40,000 interfaces (includes logical and physical interfaces).
•In a medium network, PM data collection assumes 30 days of storage for PM data collected across 500 NEs, assuming an average of 100 interfaces per NE, up to a maximum of 40,000 interfaces (includes logical and physical interfaces).
•In a large network, PM data collection assumes 30 days of storage for PM data collected across 2000 NEs, assuming an average of 100 interfaces per NE, up to a maximum of 200,000 interfaces (includes logical and physical interfaces).
•In a high-end network, PM data collection assumes 30 days of storage for PM data collected across 5000 NEs, assuming an average of 100 interfaces per NE, up to a maximum of 500,000 interfaces (includes logical and physical interfaces).
ctm_backup Directory Size
The ctm_backup directory is a repository used by the oracle user to back up the following main categories of information:
•Prime Optical database backup and export dump
•Configuration files
•Database ARCHIVELOG files
The oracle user must have read/write permissions or the database backup will fail. The database should be blocked if the ARCHIVELOG files cannot be moved to the /ctm_backup directory.
It is recommended that the /ctm_backup size be equivalent to the sum of the single database partitions (that is, the sum of /oracle, /db01, /db02, /db03, /db04, /db05, and—if configured—/db01_rd and /db02_rd).
The /ctm_backup directory can be a symbolic link to a user-defined directory and must have read/write permissions.
VMware Support
Prime Optical 9.6 can run on a virtual machine (VM) on VMware vSphere version 4.1 or 5.0. VM RAM, disk, and partitioning requirements must comply with the same requirements for a nonvirtualized setup based on system size.
To configure VMware:
Step 1 Assign RAM as listed in Table 4, "Recommended Specifications for the Prime Optical Server Installation".
Step 2 Comply with the disk space and partition requirements as listed in Disk Space and Partition Requirements.
Step 3 Configure VM vCPU settings. Refer to VMware VSphere performance guidelines for information on vCPU settings.
A general guideline is to configure 2vCPU for every 500nodes. This is based on a UCS C210 M2 machine, with a dual-socket, multicore, 2.93-GHz processor in a medium-sized network, Prime Optical setup during Cisco internal validation.
Step 4 Confirm that the /etc/hosts file exists inside the guest OS of the VM and that the hostname (with and without a domain) is associated to the proper IP address and not to the loopback IP 127.0.0.0.
In the following examples, the hostname vm-rh-01 is associated to the loopback address 127.0.0.1.
Example of a correct entry in the /etc/hosts file:
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
10.58.65.195 vm-rh-01 vm-rh-01.cisco.com
Example of an incorrect entry in the /etc/hosts file:
127.0.0.1 vm-rh-01 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
Note The /etc/hosts file might contain the wrong information if the VM OS was installed without network connectivity.
Ports and Protocols
Prime Optical uses the ports and protocols listed in the following topics:
•Southbound Ports
•Client-Server Communication Protocols
Southbound Ports
Prime Optical uses the following ports to communicate with NEs:
•Inbound ports—For operations initiated by the node and then directed to the Prime Optical server.
•Outbound ports—For operations initiated by the Prime Optical server and then directed to the node.
Table 7 lists the ports that Prime Optical uses to communicate with ONS 15216 NEs.
Table 7 Port Information for ONS 15216 NEs
Port
|
ONS 15216 NE
|
Inbound or Outbound?
|
TL1 Telnet
|
3083
|
Outbound
|
CLI
|
23, 8023
|
Outbound
|
Prime Optical GateWay/SNMP set/trap
Note Prime Optical GateWay/SNMP uses port 162 as an internal port.
|
161, 162
|
Outbound
|
TFTP
|
69
|
Inbound
|
Table 8 lists the ports that Prime Optical uses to communicate with ONS 15305 NEs.
Table 8 Port Information for the ONS 15305 NEs
Port
|
ONS 15305
|
CLI
|
23
|
Prime Optical GateWay/SNMP
Note Prime Optical GateWay/SNMP uses port 162 as an internal port.
|
161
|
Table 9 lists the ports that Prime Optical and CTC use to communicate with CTC-based NEs.
Table 9 Port Information for CTC-Based NEs
Port
|
NE
|
CORBA listener port on the Timing Communications and Control Card (TCC+/TCC2) (NE)
|
Configurable with:
•TCC+/TCC2 fixed (57790, outbound).
•Standard Internet Inter-ORB Protocol (IIOP) port (683, outbound).
•User-defined constant.
Note After Prime Optical is installed, you can configure the port in the NE Explorer (Network > Address subtab). For more information, see the topic on viewing and changing the network address for CTC-based NEs in the Cisco Prime Optical user guide.
|
CORBA listener port on Prime Optical server (callback)
|
Dynamic (current functionality).
Note To make the port static, see the topic on CTC IIOP Port Configuration in the Cisco Prime Optical user guide.
|
HTTP
|
From any CTC or Prime Optical port to HTTP port 80 (outbound) on the NE.
|
HTTPS
|
Port 443, active if configured on the NE. This port is available only in NE release 6.0 and later. Prime Optical tries to communicate on this port regardless of whether or not the NE supports HTTPS. If this port is blocked, it could cause long NE initialization times.
|
TL1 port on TCC+/TCC2 (NE)
|
From any CTC or Prime Optical port to TCP port 3082, 2361 (outbound), or port 4083 (secure).
|
CTC launched from Prime Optical Domain Explorer
|
•From any CTC port to the IIOP port on the NE.
•From any NE port to the IIOP port on CTC.
•From any CTC port to HTTP port 80 (outbound) on the NE.
•Either port is configurable in the CTC.INI (Windows) or .ctcrc (UNIX):
–Dynamic (default).
–Standard IIOP port (683, outbound).
–User-defined constant.
|
L2 Service Resync and Cisco IOS CLI ports
|
From any port on Prime Optical to ports 20xx and 40xx on the NE, where xx is the ML-series card slot number.
Note Ports 40xx are required only if shell access is set to Secure.
|
Prime Optical GateWay/SNMP
Note Prime Optical GateWay/SNMP uses port 162 as an internal port.
|
From any NE port to SNMP trap port 162 (inbound) on the Prime Optical server.
|
Table 10 lists the ports that Prime Optical uses to communicate with ONS 155xx NEs.
Table 10 Port Information for the ONS 155xx
Port
|
ONS 155xx
|
Inbound or Outbound?
|
HTTP
|
80/81
|
Outbound
|
TL1
|
TCP 3082, 3083
|
Outbound
|
Cisco IOS CLI
|
TCP 23 (Telnet)
|
Outbound
|
Software download, backup, restore
|
69 (TFTP server)
|
Inbound
|
Prime Optical GateWay/SNMP requests
Note Prime Optical GateWay/SNMP uses port 162 as an internal port.
|
UDP 161
|
Outbound
|
SNMP traps
|
UDP 162
|
Inbound
|
Client-Server Communication Protocols
Prime Optical uses the following protocols for client-server communication:
•Common Object Request Broker Architecture (CORBA)—Object Management Group's open, vendor-independent architecture and infrastructure that computer applications use to work together over networks.
•Java Management Object and Configuration Object (JMOCO)—Cisco-proprietary, TCP/IP-based request/response protocol.
•Telnet—A standard internet protocol that provides terminal emulation using the TCP/IP protocols.
•Java Database Connectivity (JDBC)—The industry standard for database-independent connectivity between Java programming languages and databases. The Prime Optical client uses JDBC to communicate directly with the Prime Optical database, independently from the Prime Optical server.
•Inbound ports are for operations initiated by the Prime Optical client and then directed to the Prime Optical server.
•Outbound ports are for operations initiated by the Prime Optical server and then directed to the Prime Optical client.
Table 11 lists the ports used for communication between the Prime Optical server host and the Prime Optical client host.
Table 11 Prime Optical Server-to-Prime Optical Client Ports
Port
|
Inbound or Outbound
|
Protocol
|
Application Protocol
|
Service
|
Notes
|
80 (configurable)
|
Inbound
|
TCP
|
HTTP
|
Web server
|
Apache HTTP port
|
443 (configurable)
|
Inbound
|
TCP
|
HTTPS
|
Web server
|
Apache HTTP port
|
61616 (configurable)
|
Inbound
|
TCP
|
JMS
|
JMS Broker
|
ActiveMQBroker port
|
27613 (configurable)
|
Inbound
|
TCP
|
Proprietary
|
Prime Optical server
|
JMOCO port
|
20000 (configurable)
|
Inbound
|
TCP
|
CORBA
|
CORBA ImR
|
CORBA Implementation Repository port
|
30000
|
Inbound
|
TCP
|
CORBA
|
SM service
|
Service Manager port
|
CORBA IIOP listener port
|
Inbound
|
TCP
|
CORBA
|
CTC-based network services
|
Dynamic: Ports are selected randomly
|
22
|
Inbound
|
TCP
|
SSH
|
Prime Optical server host
|
Standard SSH port for secure login
|
1521
|
Inbound
|
TCP
|
JDBC
|
Oracle listener
|
Database listener port
|
10023-10086
|
Inbound
|
TCP
|
Telnet
|
Telnet relay ports
|
Telnet port
|
3000-3200
|
Outbound
|
UDP
|
SNMP
|
ONS 1530x
|
ONS 1530x SNMP trap forwarding to CEC
|
Table 12 lists the ports used for communication between the Prime Optical server workstation and the NEs.
Table 12 Prime Optical Server-to-NE Ports
Port
|
Inbound or Outbound
|
Protocol
|
Application Protocol
|
Service
|
Notes
|
161
|
Outbound
|
UDP
|
SNMP
|
Base service
|
—
|
162
|
Inbound
|
UDP
|
SNMP
|
Base service
|
—
|
4500-4510
|
Inbound
|
TCP
|
Proprietary
|
ONS 15305 R3.0 (CTC-based)
|
—
|
12345
|
Outbound
|
TCP
|
Proprietary
|
ONS 15305 R3.0 (CTC-based)
|
—
|
17476
|
Inbound
|
TCP
|
Proprietary
|
ONS 15305 R3.0 (CTC-based)
|
—
|
80
|
Outbound
|
TCP
|
HTTP
|
ONS 15305 R3.0 (CTC-based)
|
—
|
23
|
Outbound
|
TCP
|
Telnet
|
ONS 15305
|
—
|
4500-4510
|
Inbound
|
TCP
|
Proprietary
|
ONS 15305
|
—
|
23
|
Outbound
|
TCP
|
Telnet
|
ONS 15305
|
—
|
161
|
Outbound
|
UDP
|
SNMP
|
ONS 15305 R3.0 (CTC-based)
|
—
|
161
|
Outbound
|
UDP
|
SNMP
|
ONS 15305
|
—
|
3083
|
Outbound
|
TCP
|
TL1
|
ONS 15216
|
—
|
23
|
Outbound
|
TCP
|
Telnet
|
ONS 15216
|
—
|
8023
|
Outbound
|
TCP
|
Telnet
|
ONS 15216
|
—
|
69
|
Inbound
|
TCP
|
TFTP
|
ONS 15216
|
—
|
161
|
Outbound
|
UDP
|
SNMP
|
ONS 15216
|
—
|
161
|
Outbound
|
UDP
|
SNMP
|
CTC-based
|
ML cards.
|
7200
|
Inbound
|
UDP
|
SNMP
|
CTC-based
|
ML cards.
|
7209
|
Outbound
|
UDP
|
SNMP
|
CTC-based
|
ML cards.
|
7210
|
Inbound
|
UDP
|
SNMP
|
CTC-based
|
ML cards.
|
CORBA listener port on the TCC+/TCC2 card (NE)
|
Outbound
|
TCP
|
CORBA
|
CTC-based
|
The port is configurable with:
•TCC+/TCC2 fixed (57790, outbound).
•Standard Internet Inter-ORB Protocol (IIOP) port (683, outbound).
•User-defined constant.
|
CORBA listener port on the Prime Optical server (callback)
|
Inbound
|
TCP
|
CORBA
|
CTC-based
|
Dynamic.
|
80
|
Outbound
|
TCP
|
HTTP
|
CTC-based
|
—
|
3082
|
Outbound
|
TCP
|
TL1
|
CTC-based
|
TL1 port on TCC+/TCC2 (NE).
|
2361
|
Outbound
|
TCP
|
TL1
|
CTC-based
|
TL1 port on TCC+/TCC2 (NE).
|
4083
|
Outbound
|
TCP
|
TL1
|
CTC-based
|
TL1 port on TCC+/TCC2 (NE), secure.
|
20xx
|
Outbound
|
TCP
|
Telnet
|
CTC-based
|
ML cards: L2 Service Resync port. From any port on Prime Optical to port 20xx on the NE, where xx is the ML card slot number.
|
40xx
|
Outbound
|
TCP
|
Telnet
|
CTC-based
|
ML cards: L2 Service Resync port when the shell access is set to secure. From any port on Prime Optical to port 40xx on the NE, where xx is the ML card slot number.
|
3082, 3083
|
Outbound
|
TCP
|
TL1
|
ONS 155xx
|
—
|
161
|
Outbound
|
UDP
|
SNMP
|
ONS 155xx
|
—
|
80, 81
|
Outbound
|
TCP
|
HTTP
|
ONS 155xx
|
—
|
23
|
Outbound
|
TCP
|
Telnet
|
ONS 155xx
|
—
|
69
|
Inbound
|
TCP
|
TFTP
|
ONS 155xx
|
—
|
Table 13 lists the ports used for communication between the Prime Optical client workstation and the NEs.
Table 13 Prime Optical Client-to-NE Ports
Port
|
Inbound or Outbound
|
Protocol
|
Application Protocol
|
Cross-Launched Application
|
Notes
|
161
|
Outbound
|
UDP
|
SNMP
|
CEC
|
—
|
4500-4510
|
Inbound
|
TCP
|
Proprietary
|
CEC
|
—
|
161
|
Outbound
|
UDP
|
SNMP
|
CTC
|
—
|
4500-4510
|
Inbound
|
TCP
|
Proprietary
|
CTC
|
—
|
12345
|
Outbound
|
TCP
|
Proprietary
|
CTC
|
—
|
17476
|
Inbound
|
TCP
|
Proprietary
|
CTC
|
—
|
69
|
Inbound
|
UDP
|
TFTP
|
CTC
|
—
|
23
|
Outbound
|
TCP
|
Telnet
|
CTC
|
—
|
80
|
Outbound
|
TCP
|
HTTP
|
CTC
|
—
|
CORBA listener port on the TCC+/TCC2 card (NE)
|
Outbound
|
TCP
|
CORBA
|
CTC
|
The port is configurable with:
TCC+/TCC2 fixed (57790, outbound)
Standard Internet Inter-ORB Protocol (IIOP) port (683, outbound)
User-defined constant
|
CORBA listener port on the Prime Optical server (callback)
|
Inbound
|
TCP
|
CORBA
|
CTC
|
Dynamic: The port range can be configured
|
80
|
Outbound
|
TCP
|
HTTP
|
CTC
|
—
|
Table 14 lists the TCP ports to use in a SOCKS proxy server configuration. This information is helpful when setting up a firewall routing table.
Table 14 TCP Ports to Open in a SOCKS Proxy Server Configuration
Port
|
Inbound or Outbound
|
Protocol
|
Application Protocol
|
Notes
|
1080
|
Inbound on firewall/SOCKS proxy host
|
TCP
|
SOCKS v5
|
The port is configurable and is used for the connection between the Prime Optical client host and the firewall host.
|
10023-10086
|
Inbound (Prime Optical server host)
|
TCP
|
Telnet
|
Used for the connection between the Prime Optical client host and the Prime Optical server host.
|
80
|
Inbound (Prime Optical server host)
|
TCP
|
HTTP
|
Used for the connection between the Prime Optical client host and the Prime Optical server host.
|
All CTC ports, for CTC cross-launch
|
Inbound on the NE that CTC is connected to
|
TCP
|
—
|
Used for the connection between the Prime Optical client host and the subnetwork that contains the NE that CTC is trying to reach.
|
Client Requirements
To install the Prime Optical client, you must have a Linux or Solaris workstation or Windows PC. Memory, CPU, and disk requirements are listed in Table 15.
The delta RAM and delta CPU must be counted for each additional launched client.
Table 15 Minimum Requirements for the Prime Optical Client
Platform
|
|
Delta CPU Speed
|
|
Disk Space with CEC
|
|
Sun workstation
|
512 MB
|
240 MHz
|
640 MB
|
710 MB
|
Sun Solaris 10 release 10/09 or higher with CDE, with graphics support for 16-bit color or higher, or Java Desktop System (JDS)
Mozilla Firefox 3.6
|
Linux workstation
|
512 MB
|
240 MHz
|
730 MB
|
760 MB
|
—
|
Pentium 4 class PC
|
512 MB
|
240 MHz
|
630 MB
|
700 MB
|
Microsoft Windows 7 (32- and 64-bit), Windows Vista, Windows 2000 Professional with Service Pack 4, Windows XP Professional with Service Pack 2, or Windows Server 2003 Enterprise Edition with Terminal Services, each with graphics support for 16-bit color or higher
Microsoft Internet Explorer 8.0, 9.0, or Mozilla Firefox 3.6, 9.0, with Java Script enabled
Microsoft Windows XP and Windows 2003 patch number KB928388 for the 2007 Daylight Saving Time
|
Caution Installing the Prime Optical
client and server on the same workstation consumes server resources and could degrade performance. We strongly recommend that you install the Prime Optical
client on a workstation separate from the Prime Optical
server.
Table 16 shows the maximum number of simultaneous Prime Optical client sessions by network size.
Table 16 Maximum Number of Simultaneous Prime Optical Client Sessions by Network Size
Network Size
|
Max. No. of Prime Optical Client Sessions
|
Small
|
30
|
Medium
|
60
|
Large
|
100
|
High end
|
100
|
3 Preparing for Installation
Before installing Prime Optical, you must perform the following preinstallation tasks:
•Enabling SSH on the Prime Optical Server and Database Workstation
•Preparing the Environment for a Single-Server Installation
Enabling SSH on the Prime Optical Server and Database Workstation
To enable you to install Prime Optical, the Prime Optical server must be able to use secure shell (SSH).
To enable SSH:
Step 1 As the root user, enter the following command to start the SSH service:
On Solaris:
On Linux:
Step 2 Edit the /etc/ssh/sshd_config file on the Prime Optical workstation and change the PermitRootLogin value to yes.
Step 3 Enter the following command on the Prime Optical workstation to make the changes take effect:
On Solaris:
On Linux:
Preparing the Environment for a Single-Server Installation
You must prepare the environment for Prime Optical server and Oracle database installation on the same server.
Before You Begin
Verify the following:
•The ping command is included in your path environment variable.
•You have identified users and related UNIX groups to run Prime Optical UNIX commands.
Note This feature is available only if you choose root user instead of optusr as the Prime Optical user during installation.
Step 1 Log in as the root user.
(For Solaris only) The C shell (csh) is recommended. To start the C shell, enter the following command:
Step 2 Enter the following command to verify that the disk directories shown in Table 17 exist:
Table 17 Disk Directories
Directory
|
Contents
|
/opt
|
For the Prime Optical installation, including .jar files, executable shell scripts, and so on
|
/db01
|
For the system tablespace used by Oracle
|
/db01_rd1
|
Optional partition for the redo logs
|
/db02
|
For the basedata tablespace, alarmdata tablespace, and eventdata tablespace that Prime Optical uses
|
/db02_rd1
|
Optional partition for the redo logs
|
/db03
|
For the data tablespace that Prime Optical uses
|
/db04
|
For the index tablespace that Prime Optical uses
|
/db05
|
For the archived and undo tablespace that Prime Optical uses
|
/ctm_backup2
|
For the backed-up database and configuration files
Note The /ctm_backup partition is required for backups.
|
/oracle
|
For the Oracle software
|
/tftpboot
|
For the TFTP directory
Note Disk partitioning is not required for /tftpboot, but the directory is required.
|
4 Installing Prime Optical
Installing Prime Optical on a single-server with an embedded database is a two-part process:
1. Prepare the server for installation.
2. Install Prime Optical
Preparing the Server for Prime Optical Installation
Before you install Prime Optical, you must first connect to the server and, if using X server, verify the display settings.
To prepare the server for Prime Optical installation:
Step 1 (For Solaris only) As the root user, launch a terminal on the server where you want to install Prime Optical. (If you logged in as a nonroot user, enter the su - command to become the root user.)
The C shell (csh) is recommended. To start the C shell, enter the following command:
Step 2 Enter the following command to set the DISPLAY variable:
setenv DISPLAY hostname-or-IP-address:0.0
Step 3 Enter the following command to verify that the display is set correctly:
In the command output, you should see:
hostname-or-IP-address:0.0
Step 4 If you are using an xterm window or a remote host, enter the following command to enable the xterm connection from the clients:
The default path is one of the following:
•(Solaris) /usr/openwin/bin
•(Linux) /usr/bin
Step 5 (For Solaris only; not applicable to Linux) Verify that the STTY command is not used in the shell configuration file; for example, in the .login, .cshrc, and .profile files.
Installing Prime Optical on the Server
As part of your Prime Optical installation, you will install the Prime Optical server and Oracle 11g database on the same Sun Solaris or Red Hat Linux server.
To install Prime Optical:
Step 1 Insert the Cisco Prime Optical Server installation DVD into the DVD drive and enter the following commands:
cd /DVD-mount-point/Disk1
ls -laR
If no list of files is returned, or if you get an error message, see the Sun Solaris or Linux documentation for mounting the DVD-ROM.
Step 2 Enter the following commands and click Next.
cd /
DVD-mount-point/Disk1/setup.sh
Step 3 At the License Agreement screen, read the license agreement, click the I accept the terms of the license agreement radio button, and click Next.
Step 4 At the Installation Options screen, choose New installation; then, click Next.
Step 5 At the Server Configuration screen, do the following:
a. Under Server Installation Type, select an installation mode. (For field descriptions, see Table 18.)
b. Under Oracle Installation Type, click Oracle Embedded; then, click Next.
Step 6 At the Main Options screen, check the following check boxes; then, click Next:
•Create Prime Optical database
•Install Prime Optical server
Step 7 At the Operating System User screen, select a user type; then, click Next. (For field descriptions, see Table 18.)
Step 8 At the Oracle Information screen, click Next. If a previous version of Oracle is detected on your system, click Continue to delete it and continue the installation.
Step 9 Review the preinstallation checks; then, click Next.
A warning message appears during the preinstallation checks. If the installation continues, you can ignore the message; if the installation quits, see the topic on downloading and installing Oracle packages in the Cisco Prime Optical 9.6 Installation Guide.
If a message tells you that an NIS/NIS+ configuration has been detected, cancel the installation, unconfigure NIS/NIS+, and relaunch the installation.
Step 10 At the Select Network Configuration screen, specify the size of your network; then, click Next.
Step 11 (For root users only) At the Prime Optical Group Information & Sudo Installation screen, enter the required information; then, click Next. (If you already installed and configured sudo with rules in a file other than /etc/sudoers, copy the rules from /etc/sudoers to /user/local/etc/sudoers at the end of the installation.)
Step 12 At the FTP Information screen, enter the required information; then, click Next. (For field descriptions, see Table 18.)
Step 13 At the Server IP Address screen, verify that the correct hostname or IP address is shown for the Prime Optical server; then, click Next.
Step 14 (Optional, for Solaris only) To enable TFTP, enter the required information; then click Next.
Step 15 At the Database Information screen, click Next; then, click Next again.
Step 16 At the Destination Folder screen, specify where you want to install the Prime Optical server; then, click Next.
Caution Do not specify a mount point as the target installation directory for the Prime Optical
server installation, or the installation data will be lost when the workstation restarts. You must create a dedicated Prime Optical
subdirectory. For example, if /cisco is the mount point for the disk partition /dev/dsk/c0t0d0s5, you cannot specify /cisco as the Prime Optical
installation directory. Instead, specify a dedicated subdirectory such as/cisco/PrimeOpticalServer.
Note Do not delete any instances of /opt/CiscoTransportManagerServer from your Prime Optical file structure. Prime Optical checks for the /opt/CiscoTransportManagerServer directory or a symbolic link to it. If Prime Optical cannot find either, it automatically creates a symbolic link.
Step 17 In the Pre-Installation Summary screen, click Install. If you get a message telling you that SSH is not configured, verify that PermitRootLogin is set to Yes in the /etc/ssh/sshd_config file; then, click Continue.
Step 18 Enter the root password and follow the prompts to configure the SSH connection and continue the installation.
Step 19 In the Web Server Installation Summary screen, click Next; then, in the Install Complete screen, click Done.
Step 20 As the root user, enter the following command to reboot the system and automatically start the Prime Optical server:
After the server reboot, it might take up to 20 minutes for the Prime Optical server to come up.
Explanations of Fields in the Installation Wizard
Table 18 describes the required information for your Prime Optical embedded database installation.
Table 18 Fields in the Installation Wizard
Screen
|
Field Description
|
Server Installation Type
|
•Standalone—Installs Prime Optical without Prime Central integration. For more information about the Prime Central portal, see http://www.cisco.com/en/US/products/ps11754/tsd_products_support_series_home.html.
•Suite—Installs Prime Optical with Prime Central. After Prime Optical is integrated with the suite, it cannot be reverted to standalone mode.
Caution If you are installing Prime Optical with Prime Central, DNS must be enabled on the machine where Prime Optical is being installed. If the machine cannot resolve hostnames into IP addresses through DNS, Prime Optical registration will fail.
|
Operating System User
|
•root—Default option. Allows only the root user to operate Prime Optical.
•optusr—Allows a user other than root to operate Prime Optical. If this option is selected, the following rules apply:
–Only the optusr can start or stop the Prime Optical server.
–The root user will still be the only user who can install and uninstall Prime Optical.
–The following processes will still be executed by root: Web Apache Server and SNMPTrapService.
Note The password for optusr is Ctm123!. You can change the password later using the passwd -u optusr command.
|
FTP Information
|
Create new FTP account—If checked, the install script will automatically create the FTP user on the Prime Optical server workstation. If unchecked, it is assumed that an FTP user already exists on the Prime Optical server workstation.
Note The FTP user is created in the locked state. Execute the following command to unlock the FTP user:
passwd -u username
where username is the FTP username that you specified during installation.
|
Verifying the Installation
To verify that Prime Optical was installed correctly:
Step 1 Enter the opticalctl status command after the server reboots to verify that the server is running.
The opticalctl status command displays the Prime Optical server version running as 9.6, followed by the build number. In the command output, you should see two instances of "Prime Optical Server," "SnmpTrapService," "SMService," "Apache Web Server," "TOMCAT," and "OrchestrationService." This indicates that the server is running.
Step 2 Verify that the client launches. See Launching the Client.
5 Uninstalling Prime Optical
To uninstall the Prime Optical server and the embedded database:
Step 1 Enter the following command to set the display on your terminal:
setenv DISPLAY hostname-or-IP-address:0.0
Step 2 Enter the following command to verify that the display is set correctly:
In the output, you should see:
hostname-or-IP-address:0.0
Step 3 Log into the Prime Optical server as the root user and enter the following command:
/opt/CiscoTransportManagerServer9.6/UninstallerData/IAUninstaller.sh
Step 4 When prompted to confirm the uninstallation, be sure to type your response in all capital letters, or the installer will quit. Enter YES.
6 Next Steps
Launching the Client
The Prime Optical client uses Java Web Start technology. When the Prime Optical administrator updates or patches the server, the client is updated automatically.
To launch the Prime Optical client:
Step 1 Open a Prime Optical-supported web browser and enter the following URL:
https://server-hostname
where server-hostname is the hostname of Prime Optical.
Step 2 Accept the self-signed, untrusted security certificates. (If your browser is Internet Explorer, place the security certificates in the trusted certificate store; otherwise, they will reappear upon subsequent logins.)
Step 3 The first time you log in, enter the case-sensitive username and password defaults:
•Username: SysAdmin
•Password: Ctm123!
Step 4 When prompted, change the password; then, click OK. (For password complexity rules, see Password Complexity Rules.)
Step 5 From the Prime Optical Home page menu, choose Start and select a Domain Explorer.
If you choose the SOCKS option, you must configure a SOCKS v5 proxy server address and port value. If a SOCKS server is not configured, you will connect to the Prime Optical server directly. See Configuring a SOCKS Server for information on how to configure a SOCKS server.
Note When Prime Optical is installed with Prime Central, you can launch the Domain Explorer from the Prime Central portal only.
Step 6 Click OK at the advisory message.
After the Java Web Start window appears and downloads the Domain Explorer, one of the following may occur:
•If you are using Internet Explorer, the Prime Optical client is installed automatically.
•If you are using Mozilla Firefox, you are prompted to open the PrimeOptical.jnlp file or save it to your desktop. After you open and run the .jnlp file, the Prime Optical client is installed automatically.
If the client does not start, check that Java Runtime Engine (JRE) 1.6 is installed on the machine, and that Java Web Start is associated to the browser with the correct javaws.
Password Complexity Rules
Password complexity is configurable through the Prime Optical UI (Control Panel > Security Properties pane). By default, the password must:
•Contain at least six characters, but not more than 15 characters.
•Contain at least two alphabetic characters (A-Z, a-z). Of the alphabetic characters, at least one must be uppercase and one must be lowercase.
•Contain at least one numeric character (0-9).
•Contain at least one special character (+ # % , . ; & !). The default special character set is TL1+UNIX.
•Allow a special character as the first or last character.
•Allow a numeric character as the first or last character.
•Not contain the username or any circular shift of the username. An uppercase letter and its corresponding lowercase letter are considered equivalent. For example, if the username is Arthur, the password cannot contain the string arthur, rthura, thurar, hurart, urarth, or rarthu.
•Differ from the old password by at least three characters. For example, if the old password is MikeBrady5!, the new password cannot be mikebrady5% because only the last character is different. However, the new password MikeBrady2!99 is acceptable because it differs from MikeBrady5! by three characters.
Configuring a SOCKS Server
To configure a SOCKS v5 proxy server address and port value to manage connectivity through network firewalls:
Step 1 From the Home page, choose Administration > SOCKS Table.
Step 2 Click Add Row; then, for the SOCKS host, enter the hostname or IP address and the TCP port number.
Step 3 Click Save.
Step 4 Click the radio button next to the row with the SOCKS server settings you want to use the next time you log in, and click Save as Default. (Each user must select a default SOCKS server.)
Getting Started with Prime Optical
These procedures will get you started quickly with using Prime Optical. These procedures are high-level and do not include field descriptions.
Table 19 lists high-level tasks and the related topic in the Cisco Prime Optical 9.6 user guide where you can find more information.
Creating a SuperUser Account
Note This functionality is disabled when Prime Optical is installed as part of Prime Central.
You must create a SuperUser account to start Prime Optical configuration.
To create a SuperUser account:
Step 1 In the Domain Explorer window, choose Administration > Users.
Step 2 In the Prime Optical Users table, choose Edit > Create.
Step 3 In the Create New User wizard, fill in the appropriate fields.
Step 4 Click Next. When you are finished adding a new SuperUser, click Finish.
Configuring a User for Server-to-NE Connection
To configure a user for the Prime Optical server to use to connect with NEs:
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 Click Security Properties and set the appropriate parameters. (If many tabs are displayed in the properties pane, click the arrow or Show List icons to view all available tabs.)
Step 3 Click Save.
(Optional) Configuring Automatic Alarm Acknowledgement
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click UI Properties to open the UI Properties pane.
Step 3 After making your selections, click Save.
Enabling Automatic NE Backup
Automatic backup is not available for all NEs.
To enable NE automatic backup:
Step 1 In the Domain Explorer window, choose Administration > Control Panel.
Step 2 In the Control Panel window, click NE Service to open the NE Service pane.
Step 3 Click the NE Auto Backup tab.
Step 4 Enter the following information:
•Select Modify Mode
•NE Model
•Enable Auto Backup
•Number of Backup Copies Retained
•Backup Time
•Backup Data (available only if ONS 15600 SONET or ONS 15600 SDH is selected as the NE model)
Step 5 Click Save.
Changes take effect immediately; however, the backup already scheduled for the next 24 hours remains in effect. A backup with the new parameters will occur after the previously scheduled backup runs.
Verifying NE Automatic Backup
To verify that Prime Optical is automatically backing up the NE, go to the Job Monitor table (Administration > Job Monitor), verify that the task is listed, and check its status.
If automatic backup for an NE failed, the task status will be "Failed." This failure is logged in the Audit Log, and an alarm is generated.
Verifying NE Support
To verify that an NE software version exists in the Supported Devices table, from the client, choose Domain Explorer > Administration > Supported NE table.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved.
Feedback
