Release Notes for Cisco CPT– CTC and Documentation Release 9.5.3.6 and Cisco IOS Release 15.2(1)SD6a
Available Languages
Contents
First Published: September 06, 2013
Last Updated: August 08, 2014
Text Part Number: OL-30501-04
Cisco Carrier Packet Transport Release Notes
The release notes contains the enhancements for the CPT platform. CPT is now support SSHv2 and SNMPv3 also. For detailed information regarding features, capabilities, hardware, and software introduced with this release, see Cisco CPT Configuration Guide. For the latest version of the Release Notes for the Cisco Carrier Packet Transport, visit the following URL:
http://www.cisco.com/en/US/products/ps11348/prod_release_notes_list.html
Note
The terms "Cisco CPT" and "CPT" are used interchangeably.
Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, visit the following URL:
https://tools.cisco.com/bugsearch/search
This chapter includes the following topics:
Critical Bug Fixes
Critical Bug Fixes in Release 9.5.1.2
It is recommended to use Release 9.5.1.2 that is the latest release of Cisco CPT.
Release 9.5.1.2 addresses the following critical fix over Release 9.5.1.1:
Critical Bug Fixes in Release 9.5.1.1
Release 9.5.1.1 addresses the following critical fixes over Release 9.5.1:
CSCub52947: CFM was not working for pseudowires with the following encapsulation type:
CSCub18341: Ethernet frame Delay Measurement (ETH-DM) in Y.1731 performance monitoring was not working for pseudowires with the following encapsulation types:
encapsulation untagged
encapsulation untagged list, range
encapsulation double tagged with single outer VLAN and multiple inner VLANs
Note
ITU-T Y.1731 is enhanced in Release 9.5.1.1 to support untagged frames.
CSCub64669: Hierarchical Ingress service policy was not working for the incoming encapsulation type as encap dot1q <id> second-dot1q <range>.
CSCub09721: CTC allowed the BW value of MPLS-TP tunnels to be edited in the Partial state.
CSCua90740: CTC did not allow the MPLS-TP tunnels to be deleted in the Partial state.
CSCub23598: CTC did not send update events to the Cisco Prime Optical (CPO) when a channel group was created or the Port name was modified.
CSCub41943: TNC crashed when upgraded from version 9.5.0 to 9.5.1.
CSCua86053: CTC and Cisco IOS displayed invalid BW value when the following steps were performed:
CSCub95953: Database loss occurred when the following steps were performed:
Opened a card and provisioned a port on the Provisioning > Pluggable Port Modules tabs.
Configured L2PT Config settings on the Provisioning > Ether Ports > Ethernet tabs.
Deleted the port. This led to database corruption.
In CPT 200 chassis, reset the uplink card.
In CPT 600 chassis, reset both the active and standby uplink cards.
For information on other bugs fixed in this release, use the Bug ToolKit.
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.
New Features and Functionality
This section highlights new features and functionality for Release 9.5.1. For detailed documentation for the configuration as well as limitations of each of these features, see the Cisco CPT Configuration Guide.
Y.1731 Fault Management and Performance Monitoring
Y.1731 is an extension of the Connectivity Fault Management (CFM). The ITU-T Y.1731 feature provides operations, administration, and maintenance (OAM) functions for fault management and performance monitoring to serve the needs of service providers in a large network.
CPT supports Ethernet Alarm Indication Signal (ETH-AIS), Ethernet Remote Defect Indication (ETH-RDI), and Ethernet Locked Signal (ETH-LCK) functionality for fault detection and isolation.
Y.1731 Performance Monitoring (PM) provides a standard Ethernet PM function that includes measurement of Ethernet frame delay, frame delay variation, frame loss, and frame throughput measurements specified by the ITU-T Y-1731 standard. To measure Service Level Agreement (SLA) parameters such as frame delay or frame delay variation, a small number of synthetic frames are transmitted along with the service to the maintenance end point (MEP).
CPT supports only two–way Ethernet frame Delay Measurement (ETH-DM) in Y.1731 performance monitoring. The CPT system sends, receives, and processes PM frames in intervals of 100 ms (10 frames per second) and 1 second.
Note
CFM must be enabled in the network for Y.1731 to become operational.
Span
Span is a technique of replicating the ingress or egress frames in a specific port to a specified list of destination ports. It is a monitoring feature used to monitor the traffic that is coming in and out of a port, channel group, or an Ethernet Flow Point (EFP). The monitored traffic can be used to debug the network and can also be used by law enforcement agencies.
The span can be configured to monitor ingress traffic, egress traffic, or both. The span source can be a physical port, channel group, or an EFP. The span destination can be a physical port or a channel group.
CPT supports two span modes:
Port Span—In this configuration, the ingress or egress traffic on all the Ethernet Virtual Circuits (EVCs) in the source port or channel group is captured on the destination port or channel group. The pseudowire or tunnel port is not supported as a span destination.
EFP Span—In this configuration, the ingress or egress traffic on the specified EFPs on a particular port or channel group is captured on the destination port or channel group. All types of services such as Multiprotocol Label Switching (MPLS), Virtual Private LAN Service (VPLS), Virtual Private Wire Service (VPWS), xconnect can be monitored. The pseudowire or tunnel port is not supported as a span destination.
Interlink QoS
Traffic from 1 GE ports of CPT 50 to CPT 200 or CPT 600 can be prioritized when there is congestion on the 10 GE interlink ports. CPT provides strict priority queuing mode. In this mode, the qos-group 7 and qos-group 3 share the same and highest priority than the remaining six queues. These two queues are scheduled on a round-robin basis if there is traffic on both these queues. The remaining six queues are configured in strict priority scheduling mode in the following order: Qos-group 6, 5, 4, 2, 1, 0.
Support for MSTP Cards
The following MSTP cards are supported in the CPT 200 and CPT 600 chassis:
15454-40-SMR2-C=
15454-40-SMR1-C=
15454-AR-XP=
15454-AR-XP-LIC=
15454-AR-MXP=
15454-AR-MXP-LIC=
15454-OTU2-XP=
15454-ADM-10G=
15454-OPT-AMP-17C=
15454-OPT-AMP-C=
15216-MD-40-ODD=
15216-MD-40-EVEN=
15216-FLD-4-30.3=
15216-FLD-4-33.4=
15216-FLD-4-36.6=
15216-FLD-4-39.7=
15216-FLD-4-42.9=
15216-FLD-4-46.1=
15216-FLD-4-49.3=
15216-FLD-4-52.5=
15216-FLD-4-55.7=
15216-FLD-4-58.9=
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.
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).
Related Documentation
Mapping of CPT and IOS Releases
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 © 2014, Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)