Release Notes for Cisco CPT–CTC and Documentation Release 9.7.0.2 and Cisco IOS Release 15.2(02)SC2
Available Languages
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
New Features and Functionality
This section highlights new features and functionality for release 9.7.0.2. For detailed documentation for the configuration as well as limitations of each of these features, see the CPT Configuration Guide.
CTC support for Dual-Homed Ring
The CPT system provides the ability of service provisioning, retrieval and monitoring on CPT 50 in a dual-homed ring through CTC.
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
Critical Bug Fixes
Critical Bug Fixes in Release 9.7.0.2
It is recommended to use Release 9.7.0.2 that is the latest release of Cisco CPT.
Release 9.7.0.2 addresses the following critical fix over Release 9.7.0:
CSCur15517: PTF card stuck in the loading state when WRC and PRC were power cycled multiple times.
CSCur12384 : TNC card crashed when the database was restored and the CPT 50 in ring was reloaded.
CSCur41713: After TNC switchover, state of few tunnels were shown PARTIAL even after multiple query.
CSCur77961: TNC card crashed in WRC when the database was restored.
CSCur29107: TNC crashed when multiple services were created and deleted from the WRC in IOS mode.
CSCur40590: After hard reset, the PTM and PTF cards did not come up.
CSCus17095: PTF crashed when the EVC and CFM were unconfigured.
CSCuq92579: Standby PTF card with IGMP snooping with VPLS crashed when the build was reverted from dummy build.
CSCus16906: PTM card rebooted when the unmanaged VPWS circuit was deleted.
CSCus05935: After an upgrade from 9.701 to 9.702, Bidirectional Fault Detection (BFD) was getting down.
CSCur00596: After an upgrade from 9.533 to 9.535, fake TP-TUNNEL-DOWN alarm get generated.
CSCuq83541: After an upgrade from 9.701 build to 9.701 dummy build, false PRT-LSP-LDI alarm generated.
CSCun76011: After an upgrade to 9.7, the ESMC checkbox get disabled for ring ports on CTC.
CSCul75217: After an upgrade from 9.53 to 9.535, fake alarms get generated.
CSCuq34723: After an upgrade from 9.70 to 9.702, TFTP time out traces observed.
CSCur32428: During an upgrade from 9.536 to 9.701, fake PW_DP_FLT and WKG_PW_RX_FLT alarms observed.
CSCul77449: After revert from 9.533 to 9.532, PTM port was down.
CSCun53130: After an upgrade from 9.51 to 9.53 release, Improper removal alarm get disappeared.
CSCur67612: During an upgrade, active PTF card stuck in the image downloading state.
CSCuq90379: CPT 50 port got down when the pluggable was removed and inserted again in the port.
CSCuq93999: TDM traffic went down when the CPT 50 was power cycled.
CSCur25573: Traffic went down when the active PTF card was removed and inserted again in the port.
CSCur78571: MPLS-TP configuration lost from IOS when syslog was disabled from CTC.
CSCur02207 : State of some pseudowires displayed as partial when the MPLS-TP tunnel was created with different tunnel ID on end points.
CSCus21611: MSPW did not get created when no pseudowire class or incorrect pseudowire class was selected.
CSCur32908:No database was available in the dual-homed ring when the PPM was deleted and redundancy reload shelf was done.
CSCuh48132: VC went down on dynamic segment and disappeared from static segment.
CSCun00070: ENE node did not get discovered when the GNE node was reset.
CSCur54776: CTC responded very slow when the SNMP server was added..
CSCur90755 : CTC displayed Status of few tunnels as PARTIAL when it was launched.
CSCur77986: CTC was very slow when it was launched, MPLS-TP was cleared from network view and re-query.
CSCur94317: CTC allowed the user to configure REP segments on the ring ports.
CSCur94012: Change in description of service in CTC mode did not get updated in IOS mode.
CSCuq54077: In CTC, pseudowire class selection panel of VPLS wizard did not work when columns of this panel were rearranged.
CSCur09123: CTC allowed the user to delete the ring even the peer IP of WRC was changed.
CSCur29685: CTC did not allow user to upgrade 24 CPT 50's using synchronize software option.
CSCur04323: CTC did not vaidate IP address in node role tab for dual-homed ring.
CSCur04721: CTC allowed the user to edit the name and status of single-homed ring.
CSCuq49814: CTC did not display error when ring name was exceeded maximum number of characters.
CSCus31874: Change in description of service in CTC mode did not get updated in IOS mode.
CSCur54401: Some REP segments had same segment ID when configuration of WRC and PRC was mismatched.
CSCur04703: Open PTS View option should be enabled for single and dual homed ring.
CSCuq34672: SNMP Walk on ifHighSpeed and ifSpeed displayed different values on TNC and PTF card.
CSCur43998 : IPC failed and CPT 50 did not come to card ready state when the DMA assertion was failed.
CSCuq54612: TDM traffic was flowing even when the VPWS shut.
CSCur74238: Fan tray inventory information in CPT 50 was not getting updated to TNC and CTC when the fan tray was changed.
CSCur54691: Optics inventory information was missed from the TNC.
CSCur24644: For VPLS EVC's with vlan range encapsulation and push1 rewrite, packets forwarded with wrong outer vlan.
CSCtq26758: MEA alarm get generated for trib card.
CSCuq90445: Card out or card in syslogs did not get generated for PTM card in CPT 600.
CSCur92627: Some alarms did not get cleared in PRC when the WRC was come-up.
CSCuq86083: TNC crashed when PRC and WRC switchover was performed.
CSCuq95352: ESMC get disabled when rings or CPT 50s were added or deleted multiple times.
CSCur09919: Alarm agent memory leaked in CPT 50 when the FOG ports were shut and unshut.
CSCur14152: Communication between PTF and TNC card lost when the mode was changed from IOS to CTC and again to IOS.
CSCur21081: In golden mode, user was able to add CPT 50 device Identifier and description more than the supported length.
CSCur33022: Tunnel did not deleted when the LSP's were added and deleted multiple times.
CSCur54412: After migration, fake LOS-P and SYNCLOSS alarm observed.
CSCur56022: Status of few tunnels displayed as PARTIAL when TNC switchover was done.
CSCuo80270:There was a mismatch in default CDP configuration at NMS and IOS when a port provisioned using CTC.
CSCup24680: When LDP sync configured, IGP holddown time was set to infinite, irrespective of the values used to provision through CTC.
CSCup24586: User was unable to open PTS View when a SMR2 card provisioned on a CPT node.
CSCup46589: All MPLS-TP tunnel were not discovered when more than 400 MPLS-TP Tunnels queried.
CSCuo80923: When a GCC with rate 1200k/400k created on the CPT node, a PARTIAL Overhead circuit was seen in Overhead Circuit pane.
CSCuo03159: CPU utilization was high when 1 G port went down.
CSCuo24486: PROT-CONFIG-MISMATCH alarm generated on the stand-by PTF card and database loss occurred when the PTF card was rebooted.
CSCup98933: Shutting down and removing of xconnect caused spontaneous reload of CPT 50.
CSCup92528: BD showed mac-add for interfaces that were not allied with specific BD.
CSCuo06934: Default port TPID (0x8100) was not set after EFP deleted.
CSCuo18699: During an upgrade from 9.53 to 9.531, MPLS label range reset to default.
CSCuq56720: After upgrade from 9.53 to 9.70, LACP forwarding was failed.
CSCuq86066: CPT-50 went for reboot due to momentary heart beat packet was lost between CPT-50 and PTF card.
CSCun42126: Sometimes during upgrade, PTF card was unable to read inventory details of OTN pluggable.
CSCun99897: During upgrade PTF card processed invalid slot provisioning without validation.
CSCuo43884: Stale entries found in mid point after tunnel was deleted, causing BFD flaps in IOS.
CSCuo27933: If a GNE node (OSPF enabled on LAN in area 0.0.0.0) configured with OSPF range table entries for area 0.0.0.0 has a controller card reset; OSPF failed to generate all required Type 3 LSAs in area 0.0.0.0 if the range table entry subnet included the other adjacent areas node host addresses.
CSCur41495: During upgrade from 9.511 to 9.70, resource gone fake alarm observed.
CSCur41956: Sometimes CPT 600 was not accessible via CTC.
CSCus30665: CPT 50 auto reset with last reload reason as error was detected.
CSCus39951: SNMPv3 timed out due to incorrect value of SNMPEngineTime.
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
Software and Hardware Requirements
Before you begin to install CPT, you must check if your system meets the minimum software and hardware requirements. This section describes the software and hardware requirements for CPT.
Hardware—IBM-compatible PC with a Pentium IV or faster processor, CD-ROM drive, a minimum of 4 GB RAM, 20 GB hard disk with 250 MB of available hard drive space.
Operating System:
Windows 2000 Professional, Windows XP Professional, Windows Vista, or Windows 7, Windows Server 2003 or 2008.
UNIX workstation with Solaris Version 9 or 10 on an UltraSPARC-III or faster processor, with a minimum of 1 GB RAM and a minimum of 250 MB of available hard drive space.
Apple Mac OS X.
(Use the latest patch/service pack released by the OS vendor. Check with the vendor for the latest patch/service pack.)
Java Runtime Environment—Java Runtime Environment Version 1.7.
Browser for PC—Internet Explorer 6.x, 7.x, 8.x. For UNIX Workstation—Mozilla 1.7. For MacOS-X PC—Safari.
To install or upgrade CPT, see the guides listed in Related Documentation.
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
Cisco Bug Search Tool
Use the Bug Search Tool (BST) to view the list of outstanding and resolved bugs in a release.
BST, the online successor to Bug Toolkit, is designed to improve the effectiveness in network risk management and device troubleshooting. The tool allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The tool has provision to filter bugs based on credentials to provide external and internal bug views for the search input.
The BST is available at Bug Search. To search for a specific bug, go to https://tools.cisco.com/bugsearch, enter the <bugid>. For more information on BST, see Bug Search Help.
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
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 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 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).
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
Related Documentation
Use the Cisco CPT Release Notes, Release 9.7.0.2 in conjunction with the following referenced 9.7.0.2 publication:
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
Mapping of CPT and IOS Releases
Contents
First Published: March 24, 2014
Last Updated: February 16, 2015
Text Part Number: OL-30064-02
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation, at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
Copyright © , Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)