Cisco Transport Manager Installation Guide, 9.1
Chapter 1: System Requirements
Download this chapter
Chapter 1: System RequirementsChapter 1: System Requirements
Download the complete book
Book-length PDFBook-length PDF (PDF - 2 MB)
 Feedback

Table Of Contents

System Requirements

1.1  CTM Server Requirements

1.1.1  Additional Prerequisites

1.1.2  Solaris SFTP Packages for MGX NEs

1.1.3  Server Specifications

1.1.4  Disk Space Specifications

1.1.5  Partition Specifications

1.1.6  Important Note About MGX Debug Levels and Log Files

1.2  CTM Client Requirements

1.2.1  Using Remote Application Software with the CTM R9.1 Client

1.2.2  Java Heap Sizes

1.3  Oracle Licensing for CTM

1.3.1  Oracle Enterprise Edition

1.3.2  Oracle Standard Edition

1.4  Overview of Sudo Commands

1.4.1  Explanation of the ctms-start Command

1.4.2  Explanation of the ctms-stop Command

1.4.3  Explanation of the ctms-abort Command

1.4.4  Explanation of the showctm Command

1.4.5  Explanation of the ctms-stop-service Command


System Requirements

This chapter describes what is required to install CTM. It contains the following sections:

•CTM Server Requirements

•CTM Client Requirements

•Oracle Licensing for CTM

•Overview of Sudo Commands

Note•CiscoView is an optional package and is not provided with CTM R9.1. Contact your Cisco account representative for information on how to license and install CiscoView.

•Although Cisco makes every attempt to ensure the availability of third-party hardware and software platforms specified for CTM, Cisco reserves the right to change or modify system requirements due to third-party vendor product availability or changes that are beyond Cisco's control.

1.1  CTM Server Requirements

The CTM server runs on any of the following specifications:

•Sun Solaris 10, release 05/09, on a Sun SPARC-based server

•Sun Solaris 10, release 05/09, on a Sun T2 processor

Cisco tests certain simulated network configurations, which are listed in Table 1-2 and Table 1-3. Your setup and performance might vary depending on the size of your network and the usage pattern of management tasks.

Note•The CTM server must run on a dedicated workstation. Any application that is not explicitly listed in this chapter as being required or supported by CTM cannot be installed on the dedicated CTM server workstation.

•CTM is not validated against required file systems (/oracle, /db01, /db02, /db03, /db04, /db05) of the Network File System (NFS) type.

•CTM R9.1 does not support local or global Solaris zones.

•When Solaris 10 is installed, it also installs the International Input Method Server (IIMS), which uses the CTM internal port 9010. Port 9010 is used by an MGX process called eventd. If the eventd process cannot start, internal CTM alarms appear continuously in the Alarm Browser, indicating that CTM is restarting the eventd process automatically. The IIMS is required only for non-English input methods; it is not required in CTM. Enter the Solaris command ps -eaf | grep 9010 to show the process that is using port 9010. If the IIMS process is using port 9010, run the script /etc/init.d/IIim stop to free up that port. Alternately, stop the IIMS process and make port 9010 available for the MGX eventd process.

•When Solaris 10 is installed, it also installs its new Windows manager, Java Desktop System (JDS). JDS gives a new look and feel to the GUI. The first time you start Solaris 10, you are prompted with a message to choose Common Desktop Environment (CDE), the legacy desktop system, or JDS. Choose JDS if you prefer the newer look and feel. If you access the CTM server through the CTM client installed on a Solaris 10 workstation, the GUI has a new look and feel.

Table 1-1 lists the items required to install the CTM server.

Table 1-1 Items Required to Install the CTM Server 

Requirement
Notes

CTM installation CDs

The CTM server CDs are the "S" CDs. If you are installing the CTM client on Windows or Solaris, you will need the client "C" CD.

Solaris Operating System 10 5/09 Media Kit

•Product is available on CD or DVD.

•Solaris 10 can be installed only on a 64-bit workstation.

•During the Solaris 10 installation, you are prompted to select software to install. (The default is End User System Support—769 MB.) 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 CTM server. Choose Include Solaris 64-bit support.

Sun Solaris patches 118666-18, 118667-22, 119059-47, 119090-32, 119213-19, 119254-65, 119313-26, 119757-15, 119783-10, 119900-08, 120272-24, 120410-31, 120543-14, 121118-16, 121308-17, 122212-33, 122911-16, 123938-02, 125332-06, 125539-06, 125555-05, 125719-21, 125731-04, 125952-19, 126363-07, 126868-02, 136882-02, 137080-03, 138866-03, 138874-03, 139099-02, 139555-08, 139604-05, 139606-02, 139608-04, 139656-02, 139966-02, 139967-01, 139969-02, 139982-02, 139986-01, 139991-02, 140074-08, 140165-01, 140171-02, 140391-02, 140397-06, 140559-01, 140562-02, 140563-01, 140796-01, 140899-01, 140917-02, 141020-01, 141414-07, 141733-04, 141742-03, and 141930-01 or later

•These Solaris patches might be superseded by more recent patches. Visit Sun's website for the most up-to-date patch information.

•While 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.

•Enter the showrev -p | grep <patch_number> command to verify that the required Solaris patches are installed.

•Always install Solaris patches in single-user mode.

Sun Microsystems Java Development Kit (JDK) Standard Edition version 1.5.0_20

JDK is installed automatically for the CTM server and CTM GateWay/CORBA, and bundled with the CTM client.

Oracle 10g software plus the following patches:

•p4898608_10203_GENERIC.zip

•p5201883_10203_SOLARIS64.zip

•p5337014_10203_SOLARIS64.zip

•p5605370_10203_SOLARIS64.zip

•p5752399_10203_SOLARIS64.zip (required if you are using Veritas as a disk management system)

•p6113507_10203_SOLARIS64.zip (only for New Zealand Daylight Saving Time)

•p6235161_10203_SOLARIS64.zip

•p6864068_10203_SOLARIS64.zip

•The Oracle 10g product is available on CD or in .cpio file format.

•Oracle patches are available in .zip file format.

Oracle 10g licenses for Sun Solaris

Oracle licenses can be purchased either for the server processor or for named users. For more information on Oracle 10g named users, see Oracle Licensing for CTM.

Available swap space

—

CD-ROM drive

—


1.1.1  Additional Prerequisites

Before installing the CTM server and the Oracle 10g database on your Sun Solaris 10 server, verify the following:

•The ping command is included in your path environment variable.

•Your /ctm_backup directory (the disk directory for the backed-up database and configuration files) is at least as big as the total size of your database data files.

•Solaris Secure File Transfer Protocol (SFTP) packages have been installed (if your managed network contains MGX NEs). See Solaris SFTP Packages for MGX NEs.

•You have identified nonroot users and related UNIX groups to run CTM UNIX commands. See Overview of Sudo Commands.

1.1.2  Solaris SFTP Packages for MGX NEs

If your managed network contains MGX NEs, you must download and install Solaris packages to enable SFTP support with those MGX NEs. You can install the SFTP packages in any order. Complete the following steps, which apply to both SPARC-based and T2 servers:

Step 1 Go to http://ftp.sunfreeware.com/ftp/pub/freeware/sparc/5.10/ and download the latest version of the libraries shown in the following table.

Package Name
Package Name in Solaris

libiconv-1.11

SMCliconv

libgcc-3.4.6

SMClgcc346

libgcrypt-1.2.4

SMCgcrypt

libgpgerror-1.5

SMClgpger

zlib-1.2.3

SUNWzlib


Step 2 Unzip the library packages that you downloaded in Step 1.

Step 3 Verify that the /usr/local directory exists on your CTM server.

Step 4 Enter the following command to install the library packages: 

pkgadd -d <absolute_path_of_the_unzipped_library>

For example, enter: 

pkgadd -d /tmp/libgcc-3.4.6-sol10-sparc-local

Step 5 As the installation option, choose All.

Step 6 In the console window, verify the progress of the installation.

1.1.3  Server Specifications

Table 1-2 and Table 1-3 show recommended optical and MGX hardware specifications for installing the CTM server, and the resulting maximum number of NEs the server manages for each configuration. The tables also show samples of configurations in which the CTM server and Oracle 10g database are installed on the same workstation. The CTM server can run on any platform that supports Sun Solaris 10.

If the CTM server and Oracle database are installed on separate workstations, both workstations must meet the hardware requirements shown in Table 1-2 and Table 1-3.

Note•The processor requirements for UltraSPARC IV apply also to UltraSPARC IV+. CTM R9.1 requires the same number of processors regardless of whether you use UltraSPARC IV or UltraSPARC IV+.

•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 1-2 Recommended Specifications for the CTM Server Installation—Optical 

Network Size
Oracle Database Type
Processor
CPU Speed
RAM
No. of Network Partitions
Max. No. of Optical NEs1

Small

Standard Edition

T2 processor with 4 cores

1.2 GHz

8 GB

1

200

2 x UltraSPARC III or 2 x IIIi CPU

Medium

Enterprise Edition

T2 processor with 4 cores

1.2 GHz

16 GB

1

500

4 x UltraSPARC III or 2 x UltraSPARC IV CPU

Large

Enterprise Edition

T2 processor with 4 cores

1.2 GHz

32 GB

4

2000

8 x UltraSPARC III or 4 x UltraSPARC IV CPU

High end

Enterprise Edition

T2 processor with 8 cores

1.4 GHz

64 GB

8

4000

8 x UltraSPARC IV CPU with fiber-channel disk array

1.2 GHz

1 These numbers assume you are using fully equipped ONS 15454 MSPP nodes (for example, 12 OC-48, 2 TCC, and 1 XC10G with up to 2 SDCC links and 48 SONET cross-connections per node). Note that these numbers should be used as a guideline, and will vary depending on the software and hardware configuration of your NEs.


Table 1-3 Recommended Specifications for the CTM Server Installation—MGX 

Network Size
Oracle Database Type
Processor
CPU Speed
RAM1
No. of Network Partitions
Max. No. of MGX NEs

Small

Standard Edition

T2 processor with 4 cores

1.2 GHz

8 GB

1

6

2 x UltraSPARC III or 2 x IIIi CPU

Medium

Enterprise Edition

T2 processor with 4 cores

1.2 GHz

16 GB

1

20

4 x UltraSPARC III or 2 x UltraSPARC IV CPU

Large

Enterprise Edition

T2 processor with 4 cores

1.2 GHz

32 GB

1

50

8 x UltraSPARC III or 4 x UltraSPARC IV CPU

High end

Enterprise Edition

T2 processor with 8 cores

1.4 GHz

64 GB

1

100

8 x UltraSPARC IV CPU with fiber-channel disk array

1.2 GHz

1 The memory required for the maximum number of NEs is for a single NE type. A network with multiple NE types might require additional memory.


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 is increased from the size shown in Table 1-2 and Table 1-3, more resources are reserved for the higher number of NEs to be managed.

•Oracle Database Type—Standard Edition is allowed only in small configurations. In a small configuration, performance is identical whether Standard Edition or Enterprise Edition is used. In medium or larger networks, Oracle Enterprise Edition is required.

•Processor—The server can manage more NEs as the number of processors increases above what is shown in Table 1-2 and Table 1-3. The server can manage fewer NEs as the number of processors decreases.

•RAM—The server can manage more NEs if the RAM increases above what is shown in Table 1-2 and Table 1-3. 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.

1.1.4  Disk Space Specifications

Note To calculate the disk space required for multiple NE types, add the specified disk space required for each NE type. For example, in a small network without PM data collection, if you are adding optical NEs (which requires 62 GB of disk space, according to Table 1-4) and MGX NEs (which requires 62 GB of disk space, according to Table 1-5), you will require 124 GB disk space total.

Table 1-4 to Table 1-5 show disk space requirements for optical and MGX NEs based on network size and PM data collection status when you are installing the CTM server and Oracle 10g database on the same workstation. The disk space shown does not include the /ctm_backup directory.

Table 1-4 Disk Space Requirements for Installing the CTM Server and Oracle 10g on the Same Workstation—Optical

Network Size
Maximum No. of NEs
Total Disk Space Without PM Collection, Without Optional Partitions
Total Disk Space Without PM Collection, with Optional Partitions1
Total Disk Space with PM Collection, Without Optional Partitions
Total Disk Space with PM Collection, with Optional Partitions

Small

200

62 GB

64 GB

123 GB

125 GB

Medium

500

94 GB

98 GB

240 GB

244 GB

Large

2000

144 GB

150 GB

448 GB

454 GB

High end

4000

236 GB

244 GB

858 GB

866 GB

1 The optional partitions are /db01_rd and /db02_rd.


Table 1-5 Disk Space Requirements for Installing the CTM Server and Oracle 10g on the Same Workstation—MGX 

Network Size
Maximum No. of NEs
Total Disk Space Without PM Collection, Without Optional Partitions
Total Disk Space Without PM Collection, with Optional Partitions1
Total Disk Space with PM Collection, Without Optional Partitions
Total Disk Space with PM Collection, with Optional Partitions

Small

6

62 GB

64 GB

123 GB

125 GB

Medium

20

94 GB

98 GB

240 GB

244 GB

Large

50

144 GB

150 GB

448 GB

454 GB

High end

100

306 GB

314 GB

952 GB

960 GB

1 The optional partitions are /db01_rd and /db02_rd.


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 optical 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 400 optical 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 optical 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 4000 optical NEs, assuming an average of 100 interfaces per NE, up to a maximum of 400,000 interfaces (includes logical and physical interfaces).

1.1.4.1  Understanding the ctm_backup Directory

As shown in Table 2-1 on page 2-2, the ctm_backup directory is a repository used by the oracle user to back up the following main categories of information:

•CTM 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).

Note•The final /ctm_backup size is also related to the ARCHIVELOG files.

•The /ctm_backup directory can be a symbolic link to a user-defined directory and must have read/write permissions.

1.1.5  Partition Specifications

Note•It is recommended that you use the partition sizes described in this section. CTM performance will degrade if you do not use the recommended partition sizes.

•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.

•CTM is a high-transaction application, which causes high I/O throughput for Oracle redo logs. It is recommended 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 CTM shutdown.

Table 1-6, Part 1 shows partition specifications for installing the CTM server and Oracle 10g on the same workstation when PM data collection is enabled.

Table 1-6, Part 1 Partition Sizing for Installing the CTM Server and Oracle 10g on the Same Workstation—PM Collection Enabled 

Network Size
/
swap1
/cisco
/oracle
/db01
/db01_rd2
/db02
/db02_rd
/db03
/db04
/db05
/ctm_backup

Small

12 GB

12 GB

10 GB

5 GB

5 GB

1 GB

6 GB

1 GB

40 GB

30 GB

8 GB

96 GB

Medium

12 GB

24 GB

10 GB

5 GB

8 GB

2 GB

16 GB

2 GB

90 GB

70 GB

10 GB

203 GB

Large

12 GB

48 GB

10 GB

5 GB

10 GB

3 GB

26 GB

3 GB

190 GB

140 GB

12 GB

389 GB

High end3

12 GB

96 GB

10 GB

5 GB

12 GB

4 GB

50 GB

4 GB

360 GB

300 GB

18 GB

753 GB

1 Use swap when creating the partition. Do not use /swap.

2 The /db01_rd and /db02_rd partitions are optional.

3 If your managed network contains MGX NEs, the minimum recommendation is the high-end configuration. Any additional disk space can be distributed across partitions.


Table 1-6, Part 2 shows partition specifications for installing the CTM server and Oracle 10g on the same workstation when PM data collection is disabled.

Table 1-6, Part 2 Partition Sizing for Installing the CTM Server and Oracle 10g on the Same Workstation—PM Collection Disabled 

Network Size
/
swap1
/cisco
/oracle
/db01
/db01_rd2
/db02
/db02_rd
/db03
/db04
/db05
/ctm_backup

Small

12 GB

12 GB

10 GB

5 GB

5 GB

1 GB

6 GB

1 GB

5 GB

4 GB

8 GB

35 GB

Medium

12 GB

24 GB

10 GB

5 GB

8 GB

2 GB

16 GB

2 GB

8 GB

6 GB

10 GB

57 GB

Large

12 GB

48 GB

10 GB

5 GB

10 GB

3 GB

26 GB

3 GB

14 GB

12 GB

12 GB

85 GB

High end3

12 GB

96 GB

10 GB

5 GB

12 GB

4 GB

50 GB

4 GB

20 GB

18 GB

18 GB

131 GB

1 Use swap when creating the partition. Do not use /swap.

2 The /db01_rd and /db02_rd partitions are optional.

3 If your managed network contains MGX NEs, the minimum recommendation is the high-end configuration. Any additional disk space can be distributed across partitions.


Table 1-7, Part 1 shows the partition specifications for the CTM server when installing the CTM server and Oracle 10g on separate workstations.

Table 1-7, Part 1 Partition Sizing for the CTM Server when Installing the CTM Server and Oracle 10g on Separate Workstations 

Network Size
/
swap1
/cisco
/oracle
/db01
/db02
/db03
/db04
/db05
/ctm_backup

Small

12 GB

12 GB

10 GB

5 GB

—

—

—

—

—

—

Medium

12 GB

24 GB

10 GB

5 GB

—

—

—

—

—

—

Large

12 GB

48 GB

10 GB

5 GB

—

—

—

—

—

—

High end

12 GB

96 GB

10 GB

5 GB

—

—

—

—

—

—

1 Use swap when creating the partition. Do not use /swap.


Table 1-7, Part 2 shows the partition specifications for the Oracle 10g database server when installing the CTM server and Oracle 10g on separate workstations with PM collection enabled.

Table 1-7, Part 2 Partition Sizing for the Oracle 10g Database Server when Installing the CTM Server and Oracle 10g on Separate Workstations—PM Collection Enabled 

Network Size
/
swap1
/oracle
/db01
/db01_rd2
/db02
/db02_rd
/db03
/db04
/db05
/ctm_backup

Small

10 GB

4 GB

5 GB

5 GB

1 GB

6 GB

1 GB

40 GB

30 GB

8 GB

96 GB

Medium

10 GB

6 GB

5 GB

8 GB

2 GB

16 GB

2 GB

90 GB

70 GB

10 GB

203 GB

Large

10 GB

12 GB

5 GB

10 GB

3 GB

26 GB

3 GB

190 GB

140 GB

12 GB

389 GB

High end3

10 GB

12 GB

5 GB

12 GB

4 GB

50 GB

4 GB

360 GB

300 GB

18 GB

753 GB

1 Use swap when creating the partition. Do not use /swap.

2 The /db01_rd and /db02_rd partitions are optional.

3 If your managed network contains MGX NEs, the minimum recommendation is the high-end configuration. Any additional disk space can be distributed across partitions.


Table 1-7, Part 3 shows the partition specifications for the Oracle 10g database server when installing the CTM server and Oracle 10g on separate workstations with PM collection disabled.

Table 1-7, Part 3 Partition Sizing for the Oracle 10g Database Server when Installing the CTM Server and Oracle 10g on Separate Workstations—PM Collection Disabled 

Network Size
/
swap1
/oracle
/db01
/db01_rd2
/db02
/db02_rd
/db03
/db04
/db05
/ctm_backup

Small

10 GB

4 GB

5 GB

5 GB

1 GB

6 GB

1 GB

5 GB

4 GB

8 GB

35 GB

Medium

10 GB

6 GB

5 GB

8 GB

2 GB

16 GB

2 GB

8 GB

6 GB

10 GB

57 GB

Large

10 GB

12 GB

5 GB

10 GB

3 GB

26 GB

3 GB

14 GB

12 GB

12 GB

85 GB

High end3

10 GB

12 GB

5 GB

12 GB

4 GB

50 GB

4 GB

20 GB

18 GB

18 GB

131 GB

1 Use swap when creating the partition. Do not use /swap.

2 The /db01_rd and /db02_rd partitions are optional.

3 If your managed network contains MGX NEs, the minimum recommendation is the high-end configuration. Any additional disk space can be distributed across partitions.


1.1.6  Important Note About MGX Debug Levels and Log Files

By default, the MGX debug levels and the number of log files to retain are kept low to save disk space. During the first few installations or upgrades, it is recommended (but not mandatory) that you increase the debug level of some MGX processes to assist in debugging any issues that might arise.

It is recommended that you increase the debug level for the following processes:

•topod (debug level 5)

•ILMITopoc (debug level 5)

•ooemc (debug level 7; retain up to 50 log files)

•nts (debug level 5; retain up to 20 log files)

•snmpcomm (debug level 5)

•NMServer (debug level 5; retain up to 20 log files)

For information about changing the debug level for these processes, see the Cisco Transport Manager Release 9.1 User Guide, Chapter 9, section "Setting Debug Options."

After running the system for several weeks without any problems, you can reduce the debug levels to save disk space.

1.2  CTM Client Requirements

To install the CTM client, it is recommended that you have a Sun Solaris workstation or Microsoft Windows PC configured as shown in Table 1-8.

Table 1-8 Minimum Requirements for the CTM Client 

Platform
Network Size
RAM1 ,2 ,3
CPUs
CPU Speed
Disk Space Without CEC4
Disk Space with CEC
Other

Sun workstation

Small

512 MB

1

333 MHz

640 MB

710 MB

•Sun Solaris 10 release 05/09 with CDE, with graphics support for 16-bit color or higher, or Java Desktop System (JDS)

•Mozilla 1.7 (the version integrated in Solaris 10 release 05/09)

Medium

512 MB

Large

1 GB

High end

2 GB

Pentium 4 class PC

Small

512 MB

1

450 MHz

630 MB

700 MB

•Microsoft 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 6.0 or Mozilla 1.7.13, with JavaScript enabled

•Microsoft Windows XP and Windows 2003 patch number KB928388 is available for the revised Daylight Saving Time in 2007

Medium

512 MB

Large

512 MB

High end

512 MB

1 If you are running multiple CTM client sessions on a single client workstation, add 256 MB of RAM for each additional CTM client.

2 If you are running more than two simultaneous Cisco Transport Controller (CTC) sessions on a single client workstation, add 64 MB of RAM for each CTC client.

3 It is recommended that you set the client virtual memory to two times the size of the physical memory (two times the amount of RAM).

4 Disk space requirements are for CTM and Cisco Edge Craft (CEC) client software only.


It is strongly recommended that you install the CTM client on a workstation separate from the CTM server. Installing the CTM client and server on the same workstation consumes server resources and causes performance degradation.

Table 1-9 shows the maximum number of simultaneous CTM client sessions supported in a network of optical devices versus a network of MGX devices.

Table 1-9 Maximum Number of Simultaneous CTM Client Sessions 

Network Size
Max. No. of CTM Client Sessions in an Optical Network
Max. No. of CTM Client Sessions in an MGX Network

Small

30

30

Medium

60

50

Large

100

50

High end

100

100


1.2.1  Using Remote Application Software with the CTM R9.1 Client

Client launch and operation are supported by the following remote application software:

•Windows Server 2003 Enterprise Edition with Terminal Services

•Citrix Presentation Server 4.0

•Secure Global Desktop Enterprise Edition 4.0 (previously known as Tarantella Enterprise)

Note If you are using Secure Global Desktop, enable full-duplex autodetection on the GUI server interface to prevent performance slowdown.

The hardware requirements for the remote application depend on the number of clients that the system must export, calculated with the following formula:

Target RAM = base RAM + (delta RAM x number of clients)

Target CPU = base CPU + (delta CPU x number of clients)

where:

•base RAM—Amount of RAM required by the remote application software.

•base CPU—Amount of CPU required by the remote application software.

•delta RAM—Amount of RAM required for each additional client.

•delta CPU—Amount of CPU required for each additional client.

1.2.1.1  Citrix and Windows Server 2003 Terminal Services

The following figure shows the environment for a remote Citrix Presentation Server or Windows Server 2003 Terminal Server. In this example, the GUI application server and the presentation server reside on the same workstation.

Figure 1-1 Remote Citrix or Windows Server 2003 Terminal Server Environment

The following table shows requirements for a remote Citrix or Windows Server 2003 Enterprise Edition Terminal Server.

Table 1-10 Requirements for Citrix and Windows Server 2003 Enterprise Edition with Terminal Services 

Remote Application Software
Base RAM
Delta RAM
Base CPU
Delta CPU

Windows Server 2003 Enterprise Edition with Terminal Services

512 MB

300 MB

450 MHz

240 MHz

Citrix Presentation Server 4.0

512 MB

300 MB

450 MHz

240 MHz


In this example, the hardware requirements for 10 clients are:

•CPU = 450 MHz + (240 MHz x 10) = 2850 MHz

•RAM = 512 MB + (300 MB x 10) = 3512 MB

1.2.1.2  Secure Global Desktop Enterprise Edition 4.0

The following figure shows the environment for a remote client via the Secure Global Desktop server. In this example, the GUI application server and the Secure Global Desktop server reside on different workstations. The application server can be a Windows Server 2003 Enterprise Edition with Terminal Services or a Solaris workstation.

Figure 1-2 Remote Secure Global Desktop Environment

The following table shows requirements for a remote Secure Global Desktop server on a Solaris workstation and a GUI application server on a Windows PC.

Table 1-11 Requirements for Secure Global Desktop Server and GUI Application Server on Separate Solaris and Windows Workstations  

Server and Platform
Base RAM
Delta RAM
Base CPU
Delta CPU

Secure Global Desktop server on Solaris

256 MB

7 MB

100 MHz

7 MHz

GUI application server on Windows Server 2003 Enterprise Edition with Terminal Services

512 MB

300 MB

450 MHz

240 MHz


In this example, the hardware requirements for 10 clients are:

•Secure Global Desktop server CPU = 100 MHz + (7 MHz x 10) = 170 MHz

•Secure Global Desktop server RAM = 256 MB + (7 MB x 10) = 326 MB

•Application server CPU = 450 MHz + (240 MHz x 10) = 2850 MHz

•Application server RAM = 512 MB + (300 MB x 10) = 3512 MB

The following table shows requirements for a remote Secure Global Desktop server on a Solaris workstation and a GUI application server on another Solaris workstation.

Table 1-12 Requirements for Secure Global Desktop Server and GUI Application Server on Separate Solaris Workstations   

Server and Platform
Base RAM
Delta RAM
Base CPU
Delta CPU

Secure Global Desktop server on Solaris

256 MB

40 MB

100 MHz

30 MHz

GUI application server on Solaris

512 MB

200 MB

333 MHz

110 MHz


In this example, the hardware requirements for 10 clients are:

•Secure Global Desktop server CPU = 100 MHz + (30 MHz x 10) = 400 MHz

•Secure Global Desktop server RAM = 256 MB + (40 MB x 10) = 656 MB

•Application server CPU = 333 MHz + (110 MHz x 10) = 1433 MHz

•Application server RAM = 512 MB + (200 MB x 10) = 2512 MB

1.2.2  Java Heap Sizes

The CTM client startup script provides small and high-end memory allocation and identifies the maximum heap allocation for the client Java Virtual Machine (JVM) process. The CTM client launches with the appropriate minimum and maximum Java heap sizes based on the server configuration (small, medium, large, or high end). The following table shows the Java heap memory values.

Table 1-13 Java Heap Sizes 

Network Size
Initial Heap Size
Maximum Heap Size

Small

100 MB

192 MB

Medium

128 MB

256 MB

Large

192 MB

512 MB

High end

256 MB

1024 MB


Caution The client memory type should match (or exceed) the server memory type. If a client configured for a small network logs into a medium, large, or high-end server, the small client could crash due to memory limitations. Therefore, a warning dialog box appears if a client configured for a small network logs into a medium, large, or high-end server.

1.3  Oracle Licensing for CTM

This section explains how to calculate the total number of Oracle Named User Plus licenses required for your CTM R9.1 server and client installations. This section describes with examples the following Oracle database editions:

•Oracle Enterprise Edition

•Oracle Standard Edition

Note See the Oracle website for detailed information about Oracle licensing definitions and requirements.

Oracle's technology products, including the Oracle database required for use with CTM, are licensed using one of two possible metrics. Which metric to use normally depends on which will result in a lower price for the database. If for some reason the number of database users cannot be counted, the Processor metric must be used. However, in a CTM environment, database users normally can be counted:

•Processor—This metric is defined as the number of processors on the server on which the Oracle database is installed or running. This option must be used in environments in which software users cannot easily be identified or counted (not normally the case in a CTM environment).

Note For the purpose of counting the number of processors, a multicore chip with n cores is determined by multiplying n cores by a core processor licensing factor of 0.75. All cores on all multicore chips for each licensed program for each core processor licensing factor listed above are aggregated, before multiplying by the appropriate core processor licensing factor. All fractions of a number are rounded up to the next whole number. When licensing Standard Edition programs on servers with a maximum of one processor with one or two cores, only one processor is counted.

•Named User Plus—This metric is used in environments in which users can be identified and counted. Named User Plus includes both human-operated and automated devices. All human-operated and automated devices that access the program must be licensed. A Named User Plus license may access the program on any instances on which it is deployed, provided that the minimum license requirement on each server is met.

In the context of a CTM environment, human-operated device means any device operated by a user who has direct or indirect access to CTM. Direct access is gained through a user account on CTM that allows access through the CTM client GUI. Indirect access is possible through a user account on a higher-layer OSS, which in turn communicates with CTM through CTM GateWay/CORBA. Automated users include the NEs managed by CTM and the CTM server itself.

Oracle database editions have the following differences:

•Oracle Standard Edition—Requires a minimum of five Named User Plus licenses or the total number of actual users, whichever number is higher. Oracle Standard Edition can be licensed only on servers that have a maximum capacity of four sockets. A blade server that meets these criteria is also eligible for licensing this program. Effective with the release of Oracle 10g, the Oracle Standard Edition product includes the Real Application Clusters database option. The Real Application Clusters option is not included with any Standard Edition versions prior to Oracle 10g. Customers who participate in Oracle's Update Subscription Service for the Standard Edition database can upgrade to the 10g version of the product for the supported licenses. Also, customers must use Oracle Cluster Ready Services as the clusterware; third-party clusterware is not supported. Customers must use Oracle Automatic Storage Management to manage all data.

•Oracle Enterprise Edition—Requires a minimum of 25 Named User Plus licenses per processor or the total number of actual users, whichever number is higher.

The following figure shows an example CTM environment to illustrate identifying the human and automated database users that must be counted.

Figure 1-3 Example CTM Environment

In the example shown in Figure 1-3 there are two independent CTM servers and Oracle database instances. There are four NEs, one of which is managed by both CTM servers. There is one direct CTM user and one indirect user. So in this example the total number of Oracle named users is as follows:

CTM servers: 2*

NEs: 4**

CTM users: 1**

Higher-layer OSS users: 1

Total Named User Plus: 8 = 2 + 4 + 1 + 1

*Because of the self-monitor feature of CTM, a CTM server itself is considered an automated user of the database and is therefore counted.

**A Named User Plus license entitles the user to access Oracle on any instances where it is deployed. So if a user has access to multiple CTM servers, only a single license is needed per user. Also, if an NE is managed by multiple CTM servers, only a single license is needed per NE.

This example explains how to count the named users, but the number of named users required is the larger of either 1) the actual count or 2) the required minimum. The required minimum will vary depending on the edition of the Oracle database (for example, standard, enterprise, and so on).

1.3.1  Oracle Enterprise Edition

Oracle Database Enterprise Edition (EE) provides improved scalability performance. The two major features in this release are:

•The Oracle partitioning option (not available in the Oracle SE)

•An increased number of maximum supported CPUs (Oracle SE supports a maximum of only four CPUs)

Note Oracle EE requires a separate license.

1.3.1.1  CTM with Oracle EE (Example A)

A service provider has 800 NEs and a data center with 10 CTM client workstations. 100 employees in the data center are authorized to use the CTM client. Some of the employees in the data center share the same CTM account (username/password). CTM is running on a Sun V880 with 8 processors, with only one core and 32 GB of RAM.

•Named User Plus: 1) Minimum = 8 processors x 25 users/processor = 200 or 2) Count = 800 licenses for NEs + 100 licenses for data center personnel + 1 CTM server = 901

Result: 901 Named User Plus licenses are required

•Processor: 8 processor licenses

If the processors are UltraSPARC IV and IV+ (dual core), the calculation for processor licensing is:

•Processor: (8 x 2) x 0.75 = 12 processor licenses

1.3.1.2  CTM with Oracle EE (Example B)

The same service provider as in the previous example decides to enable CTM GateWay/CORBA and connect to a higher-layer OSS that handles inventory management. There are 20 employees in the data center authorized to access the inventory system; 5 of them are also CTM users (that is, they are a subset of the 100 CTM users identified in the previous example). In this case, the total number of human users is:

95 CTM-only users + 15 inventory system-only users + 5 CTM/inventory system users, or 115 human named users.

As a result of adding the OSS and related users, the total number of named users required has increased from 901 to 916.

1.3.2  Oracle Standard Edition

For small CTM installations, Oracle Database Standard Edition (SE) offers a low-cost alternative. Oracle Database SE can be licensed only on servers that have a maximum capacity of four sockets.

1.3.2.1  CTM with Oracle SE (Example)

A large enterprise customer has 78 NEs and 5 CTM client workstations. 15 employees in the data center are authorized to use the CTM client. Some of the employees in the data center share the same CTM account (username/password). CTM is running on a Sun V240 with 2 processors and 8 GB RAM.

•Named User Plus: 1) Minimum = 2 processors x 5 users/processor = 10 or 2) Count = 78 licenses for NEs + 15 licenses for data center personnel + 1 CTM server = 94

Result: 94 Named User Plus licenses are required

•Processor: 2 processor licenses

If the processors are UltraSPARC IV and IV+ (dual core), the calculation for processor licensing is:

•Processor: 2 processor licenses

1.4  Overview of Sudo Commands

Sudo software (freeware) version 1.6.6 is bundled with the CTM R9.1 software. The sudo software enables nonroot UNIX users to run the following UNIX commands:

•ctms-start

•ctms-abort

•ctms-stop

•ctms-stop-service

•showctm

•getinfo.sh

•prune_auditlog.sh

•prune_errlog.sh

•prune_audittrail.sh

•prune_fm.sh

•prune_pm.sh

•prune_ne.sh

•prune_server_monitor.sh

•prune_admin_job_table.sh

•prune_ne_ipaddress.sh

During the CTM server installation, the setup program prompts you to specify the name of the UNIX group to which you want to assign administrator privileges. By default, this group is set to the root group. If you specify a group other than root, the setup program verifies that the UNIX group exists on the system and adds entries to the /etc/sudoers file. Entries in this file reflect the commands that the specified UNIX group can run by using the sudo command.

The following entries in the /etc/sudoers file reflect the commands that can be run as nonroot: 

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_admin_job_table.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: 
/opt/CiscoTransportManagerServer/bin/prune_admin_job_table.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_server_monitor.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: 
/opt/CiscoTransportManagerServer/bin/prune_server_monitor.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_ne.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/prune_ne.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_pm.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/prune_pm.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_fm.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/prune_fm.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_audittrail.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: 
/opt/CiscoTransportManagerServer/bin/prune_audittrail.

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_errlog.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: 
/opt/CiscoTransportManagerServer/bin/prune_errlog.

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/prune_auditlog.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: 
/opt/CiscoTransportManagerServer/bin/prune_auditlog.

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/getinfo.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/getinfo.sh

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/showctm

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/showctm

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/ctms-stop-service

%CTM_UNIX_group hostname=(root) NOPASSWD: 
/opt/CiscoTransportManagerServer/bin/ctms-stop-service

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/ctms-stop

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/ctms-stop

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/ctms-abort

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/ctms-abort

%CTM_UNIX_group hostname=(root) NOPASSWD: /usr/bin/ctms-start

%CTM_UNIX_group hostname=(root) NOPASSWD: /opt/CiscoTransportManagerServer/bin/ctms-start

1.4.1  Explanation of the ctms-start Command

A complete set of administrative command scripts is added to the application during installation. One command automatically starts the CTM server processes every time the server is started. The server processes can also be started or stopped manually as necessary; the scripts are located in the /opt/CiscoTransportManagerServer/bin directory.

The ctms-start command sets the appropriate environment variables and starts the CTM server. The amount of time it takes for the CTM server to start varies based on the number of NEs in the configuration and the size of the database. Use ctms-start only when the CTM server has stopped.

Step 1 Log into the CTM server workstation as the root user.

Step 2 On the command line, enter the following command: 

ctms-start

Note It can take from 0 to 5 minutes for the server processes to start after the ctms-start command has finished execution. This is because NE services and gateway services (if enabled) are still initializing for all of the NEs that are deployed. Wait 5 minutes after entering the ctms-start command; then, enter the showctm command. The NE service corresponding to all the deployed NEs should have started.

1.4.2  Explanation of the ctms-stop Command

The ctms-stop command stops the CTM server gracefully. The stop procedure shuts down the server and cleans all memory and connections. The overall process takes approximately 5 minutes.

Step 1 Log into the CTM server workstation as the root user.

Step 2 On the command line, enter the following command: 

ctms-stop

1.4.3  Explanation of the ctms-abort Command

The ctms-abort command kills all of the running processes immediately and stops the CTM server. The overall process takes no longer than 2 to 3 minutes.

Step 1 Log into the CTM server workstation as the root user.

Step 2 On the command line, enter the following command: 

ctms-abort

1.4.4  Explanation of the showctm Command

The showctm command provides CTM version and process information.

Step 1 Log into the CTM server workstation as the root user.

Step 2 On the command line, enter the following command: 

showctm

The following is an example of the output of the showctm command, where all of the attributes (except for the process names) are variable: 

CTM Processes for Cisco Transport Manager Server Version: 9.1 Build: <build_number>

-------------------------------------------------------------------------------------

USER   PID   %CPU       %MEM          START         TIME  PROCESS

-------------------------------------------------------------------------------------

root  1545   0.0   0.111104033672     Sep_09       28:32  CTM Server

root  1522   0.0   0.098984           Sep_09        0:00  CTM Server

root  1794   0.2   0.5634096300984    Sep_09      228:04  SnmpTrapService

root  1620   0.0   0.4529248236944    Sep_09       60:44  SMService

root  2469   0.1   2.020528321316328  Sep_09      238:49  CTC-based SONET NetworkService-2

root  2589   0.0   1.720510481097776  Sep_09      264:03  CTC-based SDH NetworkService-4

root  4516   0.0   0.5498352279272    Sep_11       50:25  ONS15454/ONS15327/ONS15310CL/ONS15310MA PMService-1

root  8842   0.0   0.7882680444368    Sep_10       26:02  CORBAGWService

root  1536   0.0   0.0                Sep_09        0:34  Apache Web Server

1.4.5  Explanation of the ctms-stop-service Command

The ctms-stop-service command kills the service and starts a new instance of the service automatically.

Caution Use the ctms-stop-service command with extreme caution, because it terminates the service ungracefully. Before using this command, try to stop the service from the Control Panel window.

Step 1 Log into the CTM server workstation as the root user.

Step 2 On the command line, enter one of the following commands to stop the CTM process and automatically start a new service:

•SM service: 

ctms-stop-service SMService

•NE/PM services: 

ctms-stop-service<service_ID_number>

•CTM GateWay/CORBA service: 

ctms-stop-service -1

•SNMP trap service: 

ctms-stop-service -2