Table of Contents
Release Notes for Cisco Transport Planner, Release 10.1
Performing Software Updates in CTP
Performing Automatic Software Updates in CTP
Performing Manual Software Updates in CTP
Performing Software Update Rollback
Software and Hardware Requirements
Supported Java Runtime Environment
Customizing Memory Usage for JVM
New Features and Functionality
AC/DC power supply and cable support
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Transport Planner, Release 10.1
Release notes contain the new features and enhancements for the Cisco Transport Planner (CTP). For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to the Release 10.1 version of the Cisco Transport Planner DWDM Operations Guide .
Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, visit the following URL:
http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
Performing Software Updates in CTP
CTP enables you to update the CTP software automatically or manually.
Performing Automatic Software Updates in CTP
This section explains how to perform an automatic software update.
Step 1 When CTP is launched, it checks for the latest software update automatically. If available, the following dialog box appears: Online Update Available, Would you like to Update CTP? Click Yes.
Step 2 The Software Update Dialog box appears listing the applicable software updates. Select the required software update and click Apply.
Step 3 The Update Successful message appears. Click OK.
Note The Update dialog box appears every time CTP is launched until the software update is applied.
Performing Manual Software Updates in CTP
The software update files have a .upz extension and can be downloaded from the CTP IWE page that is internal to Cisco. Contents of the update will also be made available in the same location: http://iwe.cisco.com/web/corbu/optical/ctp
Notification about the software update is sent through email (subscribe to the mstp_network_design@cisco.com mailer list). The file is hosted on the CTP IWE page and can be downloaded manually. Customers and Partners do not have access to the Cisco internal CTP IWE page. Please contact the Cisco Sales/Account team to get the software update files.
This section explains how to perform a manual software update.
Step 1 In the CTP Help menu, go to Help > Check updates. The update CTP dialog box appears.
Step 3 Select the .upz update file and click OK.
Step 4 The Software Update Dialog box appears listing the applicable software updates. Select the required software update and click Apply.
Performing Software Update Rollback
CTP allows rollback of software updates. A single rollback moves the CTP software to the previous state (prior to the software update). For example, if there are two updates applied one by one—Update 1 and Update 2, after the first rollback, CTP removes Update 2 and retains Update 1. Further rollback(s) are needed if multiple updates are present.
This section explains how to perform a rollback.
Step 1 Press R while CTP is launching. The CTP launch is interrupted to perform a software rollback.
Step 2 Click Yes to confirm software rollback. The rollback successful dialog box appears.
Note • Delete CTP Cache before and after applying update. Procedures about deleting cache are mentioned in the CTP Operations Guide. Take a backup of the required files (User preferences, CTP Design Files (.mpz), NeUpdate File, Alien Files, and so on) before deleting CTP cache.
- Automatic Update can be performed only when you are connected to the Cisco network. If you are not on a Cisco network, try to connect to Cisco VPN first. Otherwise, the software update file should be manually provided by a Cisco representative and manually updated.
- Changes caused by the software update is applicable even if the CTP Cache is deleted after the update. To remove an update, follow the rollback procedure mentioned in the previous section.
- Multiple rollbacks are not supported in this release. Re-install CTP if required.
- In the Java Control Panel, set the Java security to medium and mention the CTP installation directory in the Exception Site List (if there are issues with the rollback). If the screen is unresponsive, end CTP process and restart CTP.
- For MAC, force quit the process and restart CTP (if there are issues with the rollback).
- After uninstallation, delete all the files under the directory where CTP is installed manually.
– Default location on Windows OS: C:\Program Files\Cisco\CTP10.1.
Software and Hardware Requirements
Before you begin to install CTP Release 10.1 , you must check if your system meets the minimum software and hardware requirements. This section describes the software and hardware requirements for CTP Release 10.1.
Operating System Requirements
CTP Release 10.1 runs on systems with the following operating systems:
- Microsoft Windows 2000 Professional
- Microsoft Windows XP Professional
- Microsoft Vista Business
- Microsoft Windows 7 Professional
- Linux
- Apple MacBook (up to Maverick). Use the following command to set the Java path to 1.6:
export JAVA_HOME=`/usr/libexec/java_home -v '1.6*'`
Note Microsoft Windows XP Professional is the preferred operating system for CTP Release 10.1.
Supported Java Runtime Environment
CTP Release 10.1 requires that you install Java Runtime Environment Version 1.6 or Version 1.7.
You can download it from this URL:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Customizing Memory Usage for JVM
CTP Release 10.1 allows you to customize the maximum amount of memory to be used by the Java Virtual Machine (JVM). The default value of 1024 MB is appropriate for use with the recommended hardware (1GB of RAM).
For hardware using less physical memory, it is recommended that you reduce the maximum amount of memory to be used by the JVM. This reduction prevents the system from using system virtual memory, which results in poorer system performance.
If you reduce the amount of memory dedicated to JVM, Cisco Transport Planner may generate an Out of Memory error in the case of a complex design, typically when designing an any-to-any traffic design with a large number of nodes. In such cases, it is recommended that you increase the memory size.
Allowing JVM to use too much memory compared to the available RAM can instead result in very low system performances due to the use of virtual memory. The following table lists the recommended settings:
To change the maximum amount of memory to be used by the JVM, you need to edit the Startup.properties file, which is available in the directory where you saved the ctp.jar file during installation. Replace the default value (1024 MB) with the appropriate one from the Suggested JVM Memory column of the preceding table. Save the file and restart the Cisco Transport Planner for the changes to take effect.
Note The suggested memory values are for a system with fairly less load. If there are many processes running on your system, changing to the suggested memory value may not launch CTP. In such cases, reduce the JVM memory appropriately (you may reduce the memory in granularity of 100 MB) by editing the Startup.properties file.
Using the Bug ToolKit
Use the Bug ToolKit to view the list of outstanding and resolved bugs in CTP Release 10.1. This section explains how to use the Bug ToolKit.
Step 1 Go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs .
You will be prompted to log into Cisco.com. After you login, the Bug Toolkit page opens.
Step 2 To search for a specific bug, enter the bug ID in the Search for Bug ID field and click Go in the Search Bugs tab.
To search for all the bugs in a specified release, enter the following search criteria in the Search Bugs tab:
- Select Product Category—Select Optical Networking .
- Select Products—Select Cisco DWDM Design Tool from the list.
- Software Version—Select 10.1 to view the list of outstanding and resolved bugs in CTP, Release 10.1.
- Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.
- Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, select Use custom settings for severity, status, and others and provide the following information:
– Severity—Check the check box for the severity level.
– Status—Check the check box corresponding to Open , Fixed , or Terminated .
Select Open to view all the open bugs. To filter the open bugs, uncheck the Open check box and select the appropriate sub-options that appear below the Open check box. The sub-options are Assigned, Forwarded, Held, Information Required, More, New, Open, Postponed, Submitted, and Waiting. For example, select New if you want to view only new bugs in CTP Release 10.1.
Select Fixed to view fixed bugs. To filter fixed bugs, uncheck the Fixed check box and select the appropriate sub-options that appear below the Fixed check box. The sub-options are Resolved and Verified .
Select Terminated to view terminated bugs. To filter terminated bugs, uncheck the Terminated check box and select the appropriate sub-options that appear below the Terminated check box. The sub-options are Closed , Junked , and Unreproducible .
You can select multiple options as required.
– Advanced—Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds. Check the Include only bugs available to customers check box to view only those bugs that are customer facing.
– Modified Date—Use this option to filter bugs based on the time duration within which the bugs were last modified. Select the appropriate option from the drop-down list.
– Results Displayed Per Page—Select the appropriate option from the drop-down list to restrict the number of results that appear per page.
Step 3 Click Search . The Bug Toolkit displays the list of bugs based on the specified search criteria.
Export to Spreadsheet
The Bug ToolKit provides the following options to export bugs to a spreadsheet:
- Click Export All to Spreadsheet link in the Search Results page under the Search Bugs tab. Specify the file name and folder name to save the spreadsheet. All the bugs retrieved by the search will be exported.
- Click Export All to Spreadsheet link in the My Notifications tab. Specify the file name and folder name to save the spreadsheet. All the saved bugs in all the groups will be exported.
If you are unable to export the spreadsheet, log into the Technical Support Website at http://www.cisco.com/cisco/web/support/index.html for more information, or call Cisco TAC (1-800-553-2447).
New Features and Functionality
This section highlights new features and functionality supported by CTP Release 10.1. For detailed documentation of each of these features, refer to the Cisco Transport Planner DWDM Operations Guide .
AC/DC power supply and cable support
Support for AC2 data center power cable and DC40 power. From release 10.1 onwards, DC40 is the default power supply.
Split ROADM
CTP supports Node Splitting (from release 10.1 onwards). The ROADM node can be configured to have separate Network Elements for different Line Sides (Per-side NE).
The following limitations apply to Split ROADM for this release:
– Multi-degree -> OXC -> 80WXC MESH-PP-4
– Multi-degree -> OXC -> 80WXC MESH-PP-8
- No support for splitting of site having omnidirectional sides and/or colorless ports.
- No support for creating OCH-CC circuits for Ethernet aggregate and TDM aggregate demands. Creating OCH-NC circuits is recommended.
- No support for creating OCH-CC circuits with alien/line/pluggable cards. Creating OCH-NC circuits is recommended.
- No support for exporting PSM-OCH protected circuits in NeUpdate XML.
- No support for circuit regenerating on a split node. Delete such circuits before splitting the node to avoid invalid reports.
- No support for circuit having optical bypass on a split node. Delete such circuits before splitting the node to avoid invalid reports.
- Information related to PPC and virtual PP-MESH is available only in NeUpdate XML file.
- PPM port types are not available in NeUpdate XML for the following cards. Creating OCH-NC circuits is recommended.
- Virtual PP-MESH Unit IDs are not editable.
- Merging two side NEs is not recommended.
- All circuits originating or terminating from the same transponder/muxponder cards should be OCH-NC or OCH-CC or OCH-NCDCN.
- Circuits are exported in NeUpdate XML only if at least one of the nodes is split and the circuit is originating/terminating or expressing through the split node.
Software Features
The new software features of Cisco Transport Planner, Release 10.1 are listed in Table 1 .
Table 1 New Features in Cisco Transport Planner, Release 10.1
Related Documentation
Cisco Transport Planner DWDM Operations Guide, Release 10.1 .
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 a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
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)