|
|
Table Of Contents
Release Notes for Cisco TransportPlanner 8.5
Software and Hardware Requirements
Supported Java Runtime Environment
Caveats in Cisco TransportPlanner 8.5
Open Caveats in Cisco TransportPlanner- Release 8.5
Resolved Caveats in Cisco TransportPlanner- Release 8.5
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco TransportPlanner 8.5
Revised: October 12, 2007, OL-11722-01
Note
Effective from Release 8.5, Cisco MetroPlanner has been renamed as Cisco TransportPlanner.
Release notes address closed (maintenance) issues, caveats, and new features for the Cisco TransportPlanner - Release 8.5 Network Design Tool. For detailed information about the features and capabilities introduced with this release, refer to the Cisco TransportPlanner DWDM Operations Guide, Release8.5, available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/ong/15400/r85docs/index.htm
Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, visit the following URL:
http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl
Contents
•
•
•
Changes to Release Notes
This section documents supplemental changes that have been added to the Release Notes for Cisco TransportPlanner - Release 8.5. No changes have been added to the Release Notes for Release 8.5.
Software and Hardware Requirements
Before you begin to install Cisco TransportPlanner 8.5, you must check if your system meets the minimum software and hardware requirements. This section describes the software and hardware requirements for Cisco TransportPlanner 8.5
•
•
Operating System Requirements
Cisco TransportPlanner 8.5 runs on systems with following Operating Systems:
•
•
Supported Java Runtime Environment
Cisco TransportPlanner 8.5 requires that you install Java Runtime Environment Version 1.5.x. You can download it from the following URL:
http://java.sun.com/j2se/1.5.0/download.jspHardware Requirements
Cisco TransportPlanner 8.5 runs on systems with following hardware configurations:
Customizing Memory Usage for JVM
Cisco TransportPlanner Release 8.5 allows you to customize the maximum amount of memory to be used by the Java Virtual Machine (JVM). The default value of 512MB is appropriate for use with Recommended HW (1GB of RAM).
For hardware having less physical memory, it is recommended that you reduce the maximum amount of memory to be used by the JVM. This helps you prevent the system starting using System Virtual Memory, which results in reduced system performances.
If you reduce the amount of memory dedicated to JVM Cisco TransportPlanner may generate Out of Memory error in case of complex design, typically when Any-to-Any with a big number of Nodes is required. In such cases, it is recommended that you increase the memory.
Allowing JVM to use too much memory compared with available RAM can instead result in very low system performances due to the use of Virtual Memory. Refer to table below for details about recommended settings.
256MB
128M
200M
170M
512MB
256M
450M
350M
1GB
512M
900M
800M
2GB
1024M
1800M
1600M
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 (512M) with the appropriate one from the Suggested JVM memory column of the table above. Save the file and restart Cisco TransportPlanner for the changes to take effect.
Caveats in Cisco TransportPlanner 8.5
Review the notes listed below before using TransportPlanner. Caveats with tracking numbers are known system limitations that are scheduled to be addressed in a subsequent release. Caveats without tracking numbers are provided to point out procedural or situational considerations when deploying the product.
Open Caveats in Cisco TransportPlanner- Release 8.5
This section contains the open caveats in the following components in Cisco TransportPlanner Release 8.5:
•
•
•
DCU
•
Optical Results table shows green results for faulty connections in the following scenarios:
–
–
–
This will be resolved in a future release.
•
After the analysis of a network, AMP-C are placed in booster position with low gain and not DCU. The workaround is to force booster positions to none or BST. This will be resolved in a future release.
GUI Reports
•
There is no option to exclude optical patch-cord to or from TXT or Line Card. The BoM stores information about the patch-cord to or from TXT or line cards for every network. This will be resolved in a future release.
•
The ANS (xml) file that Cisco TransportPlanner generates to pre-provision the MSTP units in the shelf does not pre-provision the Port Pluggable Module (PPM). This will be resolved in a future release.
•
A Null pointer exception is reported during the analysis when the network design includes or more Line+ sites. Workaround is to set the functionality of the Line+ sites to "ROADM" or "Hub." This will be resolved in a future release.
•
The Diff Report on the Internal Connections report between a network in "Design Analyzed" and "Install Analyzed" status may report a false difference in the Dispersion Compensation units required in a node. This problem will be resolved in a future release.
Card Layout
•
If you upgrade or move a network design that contains a Linear Aggregated Ethernet demand and two cascaded XPonder units at the either edges of the chain to Install mode, the layout will be modified even if it is not unlocked. This will be resolved in a future release.
•
Cisco TransportPlanner could include the Line Cards supporting a P-Ring demand in two different shelves of the same Node. Line Cards supporting a P-Ring demand must be in the same shelf so that the user can rearrange the node layout appropriately to get the required Node / Site configuration. This issue will be resolved in a future release.
•
When you create a Y-cable protected traffic demand and force the tool to use the 1RU FlexLayer Y-cable module, you cannot move the DWDM units to a different position of the Node layout. This will be resolved in a future release.
•
When you create an AggregatedEthernet demand that is terminated in a node configured to use the Separate Shelf layout, the XPonder (XP) unit is placed in a new shelf even if there is room available in other shelves in the Node. The User shall manually change the position of the XP unit to optimize the layout of the Node and adjust the BoM. This will be resolved in a future release.
•
When you upgrade and analyze a network designed Cisco MetroPlanner 7.0 or later, by unlocking all the site layouts, you get two air-ramps next to each other. This will be resolved in a future release.
•
When the Muxponder units supporting Y-cable clients are moved in the node layout, it generates wrong BoM, wrong internal connections report, or inability to move. There is no workaround to this problem. This will be resolved in a future release.
•
When you move a node that includes WXC, WSS, MUX or DMX units to a different shelf, the patch panels cabled to the node are not moved. This may result in including MPO-LC cables that do not exist as Product IDs (15454-MPO-LC-x=) in the BoM. Workaround is to avoid moving the units to a different shelf or make sure the patch panel are installed close to the shelf. This will be resolved in a future release.
•
When you move a node that includes OPT-PRE or OPT-AMP-C and DCU units to a different rack, the DCU unit cabled with the amplifier is not moved. Workaround is to avoid moving units to the different rack or make sure the DCU is installed close to the shelf. This will be resolved in a future release.
•
You could move non-OSCM units in slot #8 and slot #10. Cisco TransportPlanner does not support this operation and should not be performed even if it allows you to do this. This will be resolved in a future release.
•
You cannot move an OSCM unit from slot #8 to slot #10 or from slot #10 to slot #8 in the node layout. This will be resolved in a future release.
•
When you upgrade a network that has been analyzed, you cannot move the units in the node layout after you unlock and analyze the node layout. Workaround is to close and re-open the Node Layout report. This will be resolved in a future release.
DWDM Cards
•
Cisco TransportPlanner does not consider that each Line Card features four DWDM Trunk interfaces. As a result, the number of 4-10GE-ITU and 4OC192-ITU CRS-1 DWDM Line Cards is wrongly calculated. You need to modify the BoM manually to remove the unneeded units. This will be resolved in a future release.
•
Cisco TransportPlanner does not use OPT-BST-E unit(s) for C band design even if this might help solve the OSNR problems related to the use of OPT-BST unit(s) in some cases. You need to force the use of OPT-BST-E manually instead of OPT-BST and force an high per-channel Output power (for example: 4dBm/ch for 40chs designs or 5dBm/ch for 32chs designs). This will be resolved in a future release.
•
Wavelength Routing report indicates the Optical Bypass channels in an Anti-ASE location as passing in Express. This will be resolved in a future release.
•
When you type a word or phrase in the Find field of the Search tab and press Enter, the Online Help does not display any warning message if there are no matching results. This will be resolved in a future release.
•
The Network Wizard displays all the available fibres instead of showing only fibres that are compatible to the selected design rule. This will be resolved in a future release.
Core
•
In network sections with average span loss of up to 24 dB, high per channel power (thus resulting in total power launched into fibre ~20 dBm), and sequence of 3~4 OLA nodes w/o equalizations (DGE or ROADM node), the per-channel power of lambdas in the lower part of the spectrum may result to be lower then the one of lambdas in the higher part of the spectrum. Because of this, some channels may have an OSNR that is less than the expected value.
The difference between expected and actual OSNR value for these lambdas is due to an intra-band stimulated Raman scattering that occurs when the total power into fibre is > 17~18 dBm. To avoid this type of situations, the user should manually force the use of OPT-BST-E or OPT-AMP-C in the Booster position of the impacted sites and the Output Power of these amplifiers shall be manually forced at -0.5dB. This setpoint must be modified only in the amplifiers transmitting into spans described in the above scenario. This will be resolved in a future release.
•
You cannot use the ANSI file generated through the NE Update procedure to provision the OIC nodes in a network design that contains multi-degree nodes. The file has to be manually edited to divide the single Network Element assumed by Cisco TransportPlanner in the proper number of different Network Elements.
In addition to this, the Drop Power included in the Installation Parameters report for the OIC nodes is not correctly reported. Because of this, the BoM for the OIC locations does not include the required fixed attenuators if the 32DMX-O is not used.
Workaround to determine the type and number of fixed attenuators to be used on the Drop side of the OIC node is to look at the Installation Parameters report and calculate the required attenuation as follows:
–
–
This will be resolved in a future release.
Network Model Connection
•
When you analyze a network that has at least one Multi-Degree for node which both the Structure and the Type properties are set to Auto, but a Demux unit is forced, you get an error. This will be resolved in a future release.
Other
•
When designing a network using the L-band units, the Internal Connections report for ROADM Nodes uses both the PP-64-LC and PP2-64-LC Patch Panel C-band wavelength labels instead of L-band ones. This will be resolved in a future release.
Resolved Caveats in Cisco TransportPlanner- Release 8.5
This section contains the resolved caveats in the following components in Cisco TransportPlanner Release 8.5:
•
Core
•
Wrong equalization of channel power in asymmetric node. This problem has been resolved.
GUI Reports
•
Cisco MetroPlanner allowed you to use unsupported characters in network and site names. This problem has been resolved.
DWDM Cards
•
Cisco MetroPlanner allows the user to set the Output Power on OPT-BST-E unit to -1dBm even if the unit does not support. This results in an error when loading the ANS (xml) file in the Node. This problem has been resolved.
•
In the Wavelength Routing report, the user cannot resize column width to see complete Node name if that is not completely visible. This problem has been resolved.
•
Express connections between the innermost OADM cards in an Anti-ASE Node are included in the Internal Connections report. This problem has been resolved.
•
In a network design that has P-Ring traffic demand using ONS 15454 ITU Line Cards, if you select Multi-Shelf / Separated-Shelf option for a Node (OSMINE compliant units placement not selected), the Node layout places ITU Line Cards in separated shelves. This problem has been resolved.
•
Cisco MetroPlanner shows duplicate entries for cables PID in the Side/Side cable drop-down menu inside the Node property. This problem has been resolved.
•
When you run a design in Upgrade mode, channel power thresholds change even if the node is locked. This problem has been resolved.
•
When you run a design in Upgrade mode, the output setpoint of a 32-DMX card is changed even if it is locked. This problem has been resolved.
•
OSC-CSM channel threshold wrongly triggered BST placement. This problem has been resolved.
•
Internal Connection report contains wrong cabling information in the SW Prov. view for Nodes configured to use Multi-Shelf Management and Separate Shelf layout. This problem has been resolved.
•
Internal Connection report contains wrong cabling information in the SW Prov. view for Nodes configured to use Multi-Shelf Management and Same Shelf layout. This problem has been resolved.
•
Cisco MetroPlanner allowed you to use Y-cable protection option in point to point requests with traffic type ISC-Peer 2R. This problem has been resolved.
•
When the Protected clients and Separated Shelves option was flagged on, Cisco MetroPlanner R7.0.3 added supplementary shelves in the first rack in the optical shelves instead of using the free slots in the second rack to deploy protected clients. This problem has been resolved.
•
Adding new services to an analyzed network results in the DWDM units to be added to a new shelf even if there are available slots in the existing shelves. This problem has been resolved.
•
You cannot delete a Node in a network if it is a copy or an upgrade or another network with a P-Ring defined. This cannot be done even if the P-Ring demand has been already removed. This problem has been resolved.
•
In the Internal Connections report, the connections between the 32DMX-O and the DWDM units are not included in the SW Prov. section. This problem has been resolved.
•
Unneeded connections between two patch Panel. This problem has been resolved.
•
When doing a design with 2G-FICON service using the 2.5G Data Muxponder (MXP_MR_2.5G) unit, the 200-SM-LC-L (ONS-SE-G2F-LX=) item is duplicated. This problem has been resolved.
Related Documentation
Release-Specific Documents
•
•
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
This document is to be used in conjunction with the documents listed in the Obtaining Documentation, Obtaining Support, and Security Guidelines section.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0705R)
Release Notes for Cisco TransportPlanner 8.5
Copyright © 2007, Cisco Systems, Inc.
All rights reserved
Posted: Tue Oct 16 23:22:44 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
