Q. What are the major enhancements for Cisco Transport Manager 9.2?
A. Table 1 lists new features for Cisco Transport Manager 9.2.
Table 1. New Features in Cisco Transport Manager 9.2
Ability to export the entire equipment inventory table
You have the option to export the entire equipment inventory table to a text file.
Ability to configure Cisco Transport Manager server ports used for Cisco Transport Manager GateWay/CORBA from the Cisco Transport Manager client
A new Port Configuration tab is available from the Cisco Transport Manager GateWay/CORBA Service pane. The Port Configuration tab allows you to configure the following Cisco Transport Manager server port values:
• Name service
• Notification service
• Element management system (EMS) session
• Event notification port range
• Server-to-client port range
Automatic software version check for network element (NE) activation
Cisco Transport Manager automatically checks and lists any unsupported software versions when activating software or reverting software to an earlier version on an NE.
New NE Type column in the NE software table
For ONS 15454 NEs, the NE type values are:
• DWDM: For ONS 15454 MSTP R9.2 or later NEs
• TDM: For ONS 15454 MSPP R9.2 or later NEs
• Not Available: For all other NE versions
Ability to configure a SOCKS v5 proxy server to manage connectivity through network firewalls
In many networks, the Cisco Transport Manager server is installed on a host behind a firewall, while the Cisco Transport Manager client is installed on a host outside a firewall.
The firewall is the gateway for all of the TCP/IP connections to a private network. The firewall filters all connections using a set of configurable policies that determine whether a connection can be established with hosts behind the firewall, with the private network's hosts, and with hosts outside the firewall.
You can configure a SOCKS v5 proxy server. The SOCKS protocol tunnels the following connections to a firewall in a controlled manner:
• All random CORBA ports
• The default JMOCO port (27613)
• The JDBC connection port (1521)
In the Control Panel > Recovery Properties pane, you can associate each Cisco Transport Manager server with a SOCKS host.
Discovery of dense wavelength-division multiplexing (DWDM) pluggable line insertion modules (PLIMs) on Cisco Carrier Routing System 1 (CRS-1) 3.9.0 and 3.9.1
Cisco Transport Manager 9.2 supports the discovery of DWDM PLIMs on CRS-1 3.9.0 and CRS-1 3.9.1. Cisco Transport Manager discovers the CRS-1 DWDM PLIMs through ONS 15454 NEs.
Ability to manually discover NEs and add them to specific network partitions
In Cisco Transport Manager 9.2, you can choose the mode of discovery for undiscovered NEs. In earlier Cisco Transport Manager releases, the discovery mode was limited to automatic. Using this feature, you can manually discover the NEs when needed, control the details retrieved during the discovery process, and add them to the desired network partitions.
Q. Is the Gateway/CORBA northbound interface available for all network element types?
A. Cisco Transport Manager 9.2 supports fault and inventory through the CORBA interface for all network element types. In addition the CORBA interface can be used for equipment and circuit provisioning on the Cisco ONS 15305, ONS 15327, ONS 15310-CL, ONS 15310-MA, ONS 15454 SONET, ONS 15454 SDH, ONS 15600 SONET, and ONS 15600 SDH. The CORBA interface can be used for performance monitoring for the Cisco ONS 15302, ONS 15305, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15600 SONET, and ONS 15600 SDH.
For further details on coverage, refer to the Cisco Transport Manager Gateway/CORBA Release 9.2 User Guide and Programmer Manual, available at http://cisco.com/en/US/products/sw/opticsw/ps2204/tsd_products_support_series_home.html.
Q. Is the Gateway/CORBA interface based on an industry standard?
A. Yes, Gateway/CORBA is based on and compliant with TMF 814 (Version 3.0) as published by the TeleManagement Forum.
Q. Does Cisco Transport Manager provide a Simple Network Management Protocol (SNMP) northbound API?
A. Yes, Cisco Transport Manager forwards traps from network elements that use SNMP to send traps northbound. Cisco Transport Manager also includes support for Reliable Transfer Mode (RTM) SNMP northbound interface for MGX® Voice Gateways. This northbound alarm interface provides a mechanism to forward and filter MGX alarms and events in a reliable (Cisco RTM) or nonreliable (standard User Datagram Protocol [UDP]) format.
Q. Can Cisco Transport Manager 9.2 support a network with mixed releases of the same network element?
A. Yes, it can.
See the Cisco Transport Manager Release Notes for an updated list of network elements and releases supported by Cisco Transport Manger 9.2.
Q. Does the Cisco Transport Manager product include the required hardware?
A. No. Cisco Transport Manager is a software-only application product that is based on industry-standard, off-the-shelf Sun and PC hardware platforms.
Q. Are there different configurations for the Cisco Transport Manager server?
A. Yes, the Cisco Transport Manager server can be installed in different configurations depending on the number of nodes managed and the hardware configuration available. The Cisco Transport Manager server can be installed in small, medium, large, and high-end configurations. For further details refer to the Installation Guide for Cisco Transport Manager 9.2 at http://cisco.com/en/US/products/sw/opticsw/ps2204/prod_installation_guides_list.html.
Additionally, during the upgrade, users can change the configuration size to the next available (that is, medium to large and large to high end; upgrade from the small configuration to the medium configuration is not supported).
Q. Does Cisco Transport Manager 9.2 support a high availability configuration?
Q. Can I download Cisco Transport Manager 9.2 from Cisco.com?
A. No, you must order the software, which is delivered on CD. Documentation is available for download through Cisco.com.
Q. Is Cisco Transport Manager 9.2 demonstration software available?
A. Yes, you can obtain Cisco Transport Manager 9.2 for evaluation from your Cisco sales representative.
Q. Is Cisco Transport Manager 9.2 compatible with earlier versions of the Cisco Transport Manager client, such as Release 6.0 or Release 7.2?
A. No, all Cisco Transport Manager clients must be upgraded to the new Cisco Transport Manager 9.2 client.
Q. Can the same Cisco Transport Manager client and network element right-to-use (RTU) licenses obtained for use with earlier versions of Cisco Transport Manager be used with Release 9.2?
A. If a valid Cisco Transport Manager 9.2 application upgrade is purchased, all network element and client RTU licenses that have been purchased in the past are still valid for Cisco Transport Manager 9.2 with no additional upgrade charge. Application (Server and Client), CORBA, and High Availability licenses must be upgraded.
Q. What warranty is included with Cisco Transport Manager 9.2?
A. Cisco Transport Manager 9.2 includes a standard software warranty from Cisco that warrants for 90 days from the date of delivery to you that (a) the media on which the software is furnished will be free of defects in materials and workmanship under normal use; and (b) the software substantially conforms to its published specifications.
Q. Is there a service contract available for Cisco Transport Manager 9.2?
A. Yes, you must purchase a Cisco Software Application Support (SAS) contract to receive access to technical assistance through the Cisco Technical Assistance Center (TAC) or Cisco.com. Cisco SAS also provides you with Cisco Transport Manager software updates (maintenance, minor) as they are made available for the duration of your contract. Current Cisco Software Application Support plus Upgrades (SASU) service contracts, which are no longer available for Cisco Transport Manager 9.2, will be valid until their expiration.
Q. Does Cisco Transport Manager 9.2 support all the configuration and provisioning features provided in the Cisco Transport Controller for the Cisco ONS Family?
A. No, there are some feature differences between Cisco Transport Manager 9.2 and Cisco Transport Controller for the Cisco ONS 15305, ONS 15310-CL, ONS 15310-MA, ONS 15327, ONS 15454 SONET, ONS 15454 SDH, ONS 15600 SONET, and ONS 15600 SDH. These differences are identified in the Cisco Transport Manager 9.2 User Guide.
Q. What TCP and SNMP ports does Cisco Transport Manager use?
Q. Does Cisco Transport Manager 9.2 Client support Windows 7?
High Availability Solution for Cisco Transport Manager
Q. Is there a high availability version of Cisco Transport Manager 9.2?
A. The Cisco Transport Manager 9.2 software used in the standalone version and in the High Availability Solution is the same. For the Cisco Transport Manager High Availability Agent 3.0, both Veritas high availability clustering software and third-party hardware are needed to set up a high availability environment.
Q. Where can I obtain the Cisco Transport Manager High Availability Agent 3.0?
A. It is included on the installation CD with Cisco Transport Manager 9.2 and also available for evaluation from your Cisco sales representative. The product part numbers are CTM-9.2-HA and CTM-9.2-HA-UPG.
Q. Is there a migration mechanism for standalone Cisco Transport Manager 8.x customers to migrate to Cisco Transport Manager 9.2 in a high availability configuration?
A. You can migrate your current standalone Cisco Transport Manager to the standalone Cisco Transport Manager 9.2, provided you follow the correct migration steps outlined in the installation guide. It is not possible to migrate from a standalone to a high availability configuration.
Q. What is the virtual IP address?
A. The virtual IP address hides or masks the physical IP addresses normally assigned to the Sun server Ethernet ports. By masking the physical IP address, all network elements, clients, and OSSs target the virtual IP address. In the event of a hardware failover, the standby UNIX server assumes this virtual IP address. Only the active UNIX server has the virtual IP address, so all entities are communicating with the same IP address.
Q. Does a high availability design affect the functionality of the Cisco Transport Manager clients, network-element access, or OSS?
A. All services and features are designed to operate identically to a standalone configuration.
Q. Can the High Availability Solution be installed on an existing standalone server?
A. No. There is no migration path from a standalone Cisco Transport Manager configuration to a high availability configuration. The Veritas File System and Volume Manager software technologies (included in Veritas Database Edition/High Availability for Oracle) need to be installed immediately after the Solaris 10 operating system is installed.
Q. What licenses will I need with Cisco Transport Manager in a high availability environment?
A. You will need to purchase the Cisco Transport Manager High Availability Agent 3.0 RTU license. When the license is purchased, all high availability documentation will be shipped to you on a CD. Please refer to Cisco.com to download the latest electronic copy of the Cisco Transport Manager release notes.
Q. Is any other Cisco software necessary, other than Cisco Transport Manager 9.2 and the Cisco Transport Manager High Availability Agent 3.0?
Q. Is there any customization needed in the high availability environment?
A. You may wish to modify specific aspects of the high availability configuration to fit your environment, such as adding more Ethernet modules, not mirroring internal disks, or modifying steps that are documented in the Cisco Transport Manager High Availability Installation Guide.
Q. What does the Cisco Transport Manager High Availability Agent do?
A. It is a software module that monitors processes and assesses the status of the primary server to help ensure that Cisco Transport Manager is operating correctly.
Q. Will Cisco provide information on how to back up Cisco Transport Manager in a high availability environment?
A. Cisco provides an application note similar to the one provided for the Cisco Transport Manager standalone servers.
Q. What information is included in the Cisco Transport Manager High Availability Installation Guide?
A. The document discusses all the reference hardware, part numbers, diagrams, and the references to the installation instructions for all the software (Solaris, all hardware and software patches, Veritas, Oracle, Cisco Transport Manager 9.2, and Cisco Transport Manager High Availability Agent 3.0).
Q. Where can I find other documentation about the Cisco Transport Manager and High Availability Agent?
A. The complete High Availability Solution package - all documentation on the Cisco Transport Manager High Availability Agent - is available on Cisco.com at a password-protected location. After you have purchased a license to operate the Cisco Transport Manager High Availability Agent, you will receive a complete printed copy of all High Availability Solution documents and a password to access Cisco.com. This website also contains the most up-to-date Cisco Transport Manager release notes.
Installation and Support
Q. What maintenance contracts are required for a high availability configuration?
A. The maintenance contracts required are:
• External high availability support from third-party vendors (consists of support for Sun servers, Veritas software, and Oracle).
• Annual Cisco Transport Manager maintenance contract from Cisco
• Disk array support (EMC, Hitachi, and so on)
• Tape or system backup support
Q. What are the options for external high availability support?
A. You can obtain support from the individual third-party vendors mentioned previously, through joint support alliances, or you can rely on your own in-house expertise.
Q. Does the annual Cisco Transport Manager maintenance contract differ for installation on high availability servers versus standalone servers?
A. Yes. For installation on high availability servers, you need to purchase the standard Cisco Software Application Support (SAS) contract for Cisco Transport Manager, along with a high availability SAS. The minimum baseline joint support alliance contract is also required, but you can purchase higher levels of support - such as 2-hour hardware replacement, fly-to-site, priority queuing, and more - from each vendor.
Q. Because the Cisco Transport Manager High Availability Solution consists of two Sun servers, does this require the purchase of two copies of Cisco Transport Manager and two maintenance contracts?
A. No. Only the Cisco Transport Manager software and a single maintenance contract are required.
Q. Why has Cisco chosen to recommend outsourced support for my high availability infrastructure?
A. Because timely resolution of critical problems is best managed by those with the expertise to assist with these third-party products.
Third-Party Hardware and Software
Q. Can I deviate from the specified Sun Solaris and Oracle releases with Cisco Transport Manager in a high availability environment?
A. No. Cisco Transport Manager 9.2 has been validated on specific Solaris 10 and Oracle 10g releases, as specified in the installation guide. Deviation from the specified Solaris or Oracle release in the standalone or high availability architecture may cause problems that the Cisco TAC team would be unable to reproduce.
Q. What hardware release of Solaris is used in the high availability and standalone Cisco Transport Manager configurations?
A. Both have been validated with Solaris 10 10/09 OS.
Q. What software is required to run on the high availability configuration?
A. The software requirements for the high availability configurations are as follows:
• Solaris 10 10/09 OS
• Cisco Transport Manager 9.2
• Cisco Transport Manager High Availability Agent 3.0
• Oracle Enterprise Database Edition 9i Release 2 64-bit production (Oracle10g) for Sun Solaris 10
• Veritas Storage Foundation High Availability 5.0 for Oracle on Solaris
For geographic redundancy, add:
• Veritas Volume Replicator 5.0 MP3
• Veritas Cluster Server VVR Agent 5.0 MP3
• Veritas Global Cluster Manager 5.0 (with data-replication option) MP3
In addition, all software patches for Solaris, Veritas, PCI adapters, and Oracle are required.
Q. How many licenses are required?
A. Table 2 lists the required software licenses for the Cisco Transport Manager High Availability Solution.
Table 2. Software Licenses for the Cisco Transport Manager High Availability Solution
Number of Required Licenses
Cisco Transport Manager 9.2
Cisco Transport Manager High Availability Agent 3.0
Oracle Database 10g
See vendor for options
Veritas Storage Foundation High Availability 5.0 for Oracle on Solaris
1 license per server
Veritas Volume Replicator 5.0 MP3
1 license per server
Veritas Cluster Server VVR Agent 5.0 MP3
1 license per server
Veritas Global Cluster Manager 5.0 MP3
1 license (with data-replication option) per site
Please contact your Veritas sales representative for more details on configurations and pricing of the Veritas Global Clustering solutions.
Q. What are the options for Oracle licenses?
A. You can pay Oracle based on the number of CPUs installed in your system or based on the number of named users. The Cisco Transport Manager 9.2 Standalone Installation Guide provides detailed information on the number of named users required. Full Oracle licensing is required for the primary Sun server; no additional Oracle licenses are required for the secondary Sun server. An Oracle sales representative can offer the best advice on exact licensing fees, based on your hardware configuration.
Q. Are extra Oracle named users or licenses required with the data-replication option in the High Availability Solution?
A. As specified earlier, the Cisco Transport Manager 9.2 software used in the High Availability Solution is identical to the standalone Cisco Transport Manager 9.2 software. There are no extra named users or licenses needed to operate in a high availability configuration.
Q. What does Veritas Storage Foundation High Availability 5.0 MP3 for Oracle on Solaris consist of?
A. Veritas Storage Foundation High Availability 5.0 MP3 for Oracle on Solaris comprises the following:
• Veritas Volume Manager (VxVM) 5.0 MP3
• Veritas File System (VxFS) 5.0 MP3
• Veritas Cluster Server (VCS) 5.0 MP3
• Veritas Cluster Server Oracle Agent 5.0 MP3
Q. Will the Cisco Transport Manager High Availability Agent work with any Sun hardware?
Q. Is Sun Cluster Server or Oracle Parallel Server part of the High Availability Solution?
A. No. There are a variety of ways that high availability can be deployed using a multitude of vendor software and hardware. The goal is to provide customers with an architecture that has been tested using Cisco Transport Manager High Availability Agent 3.0. Veritas was selected because it is a leading software high availability solution integrator and uses best-in-class Sun hardware and Oracle Relational Database Management System (RDBMS).
Q. What causes the secondary server to assume the role of the primary server?
A. The secondary server assumes the load of the primary server in the event of primary server failure. Essentially, a number of criteria must be met for the high availability setup to determine that the primary server has failed. When the high availability setup has detected a failure, the primary system is shut down in an orderly sequence (assuming no system failures on the CPU, motherboard, and so on), and the secondary server activates all appropriate daemons, launches Oracle, activates the virtual IP, and restarts Cisco Transport Manager.
Q. What is the impact on the network in the case of a primary server failure?
A. Any alarms sent to the primary server when the systems are switching to the secondary server will be lost until Cisco Transport Manager resynchronizes with the network element and receives an updated alarm status. When the secondary Cisco Transport Manager server comes online, Cisco Transport Manager can synchronize either manually or automatically to every network element to obtain the latest alarm status.
Q. Will the secondary server toggle back to the primary server if the Cisco Transport Manager High Availability Agent detects a failure in the secondary server?
A. No. This requires a platform manager intervention and prevents the systems from toggling back and forth until someone investigates what caused the initial failover situation.