Release Notes for Cisco CPT– CTC and Documentation Release 9.5.3.5 and Cisco IOS Release 15.2(1)SD6
Available Languages
Contents
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
- Software and Hardware Requirements
- New Features and Functionality
- Cisco Bug Search Tool
- Export to Spreadsheet
- Related Documentation
- Mapping of CPT and IOS Releases
- Obtaining Documentation and Submitting a Service Request
Critical Bug Fixes
Critical Bug Fixes in Release 9.5.3.5
It is recommended to use Release 9.5.3.5 that is the latest release of Cisco CPT.
Release 9.5.3.5 addresses the following critical fixes over Release 9.5.3.3:
- CSCun27465 : Database loss observed when the two mid points were configured for the same tunnel.
- CSCuo18699 : During the upgrade from 9.5.3 to 9.5.3.1, static label range set to default range.
- CSCty37470 : CTC displayed PTS error when the command line interface was failed for pseudowire or VPLS configuration.
- CSCun99897 : PTF card manager was unable to handle any error that received due to invalid slot provisioning from TNC.
- CSCui88443 : Protected LSP didn't come up when the working LSP was down.
- CSCuj71143: Provisionable Patchcord (PPC) deleted when the ENE was reset.
- CSCul15766 : VLAN 4093 tagged frame was unsuccessful with the Virtual Private LAN Services (VPLS).
- CSCul73841 : Invalid MAC entries added in the MAC table when the VPLS service was deleted.
- CSCul75163 : Duplicate in-label assigned for MPLS-TP tunnel after a new node was inserted in the circuit.
- CSCum35193 : Node state changed to unknown state after the PTF card was hard reset.
- CSCuo11382 : Telnet to the loopback IP was not allowed without credentials.
- CSCul20741 : SVP class ID did not allocate when the following steps were performed:
- CSCuf26409: Layer 2 Protocol Tunneling (L2PT) did not configure on the devices where Cisco Discovery Protocol (CDP) was disabled globally.
- CSCuo43884 : Bidirectional Fault Detection (BFD) flap was generated when the working or protected LSP was deleted.
- CSCul17416: QoS did not work when it was applied over VPLS service with VLAN range as encapsulation.
- CSCuh89020: A node controller did not accept incoming connections and reset.
- CSCtw63026 : Rewrite encap tag was changeable for the services where bridge-domain was already configured.
- CSCtw92316 : Error displayed when the following tasks were performed:
- CSCuj47981 : Error displayed when a protected LSP with 6 or more spans, was added to the MPLS-TP tunnel.
- CSCtz46945: Simultaneous addition of more than one node was not working properly for the virtual forwarding instance (VFI).
- CSCud59250 : MPLS–TP Tunnel did not create when the Create PW Class Automatically option was checked.
- CSCue48184 : Pseudowire with non-default MTU value went down when a new node was added to the existing VPLS circuit.
- CSCuf85491 : Configure/Edit L2TP link under the Provisioning > Ether Ports > Ethernet tab did not work when the L2PT Config column position was changed.
- CSCui68634 : License was missed from the PTF and the CPT 50 was down after an upgrade from 9.5.2 to 9.5.3.
- CSCuj25196 : Debug message displayed on the PTF when the pluggable port module (PPM) was deleted from CTC.
- CSCuj62997 : MTU value of a pseudowire did not modify when the pseudowire was created on the port-channels.
- CSCul42890 : UNC words displayed with CWDM pluggables when the node was shut or unshut.
- CSCum52787 : Single tagged packet received when the double tagged packet was sent through the VPLS with the single tagged encap and pop 1 rewrite operation.
- CSCul55620 :Telnet to the loopback IP was not allowed without credentials.
- CSCum93550 : EVC packets with different destination mac address dropped at the tunnel port where the OSPF was configured.
- CSCul46450 : MAC learning was not consistent between the nodes of the VPLS.
- CSCun15139 : Memory leak observed for some errors of the MPLS.
- CSCuo03159 : CPU utilization was high when 1 G port went down.
- CSCuo06934 : Default port TPID did not reset even when an EFP was created with default encap on the same port after deleting the EFP with dot1ad TPID.
Critical Bug Fixes in Release 9.5.3.3
Release 9.5.3.3 addresses the following critical fixes over Release 9.5.3:
- CSCud23500: CTC did not allow the user to create a protected pseudowire over MPLS-TP Tunnel with same physical link.
- CSCud83025 : CTC hanged when the Card View > Performance > Elec PM tab was clicked.
- CSCuj38620 : CTC did not allow the user to add a protected LSP on an unprotected MPLS-TP tunnel for the large protected span.
- CSCul02287 : CTC did not allow the user to edit the next hop IP address for an MPLS-TP link number.
- CSCuh98856: Connection between TNC card and PTM or CPT 50 card was lost due to Etsec RX or TX buffer full.
- CSCub57948 : Proper alarm was not getting generated for fan-out port connectivity failure.
- CSCul34323 : EQPT- FAIL alarm was not getting cleared for parity errors, after recovery.
- CSCul32735 : SAT-COMM-FAIL alarm was getting cleared automatically on CTC after reboot of TNC card.
- CSCuj87233 : Sometimes pseudowire ping and traceroute operations were not working.
- CSCul38618 : OSPF LSDB was showing invalid link metrics values.
- CSCui53677 : Error messages displayed in UL or Trib console when the following steps were performed:
- CSCui18866 : DCMSDK error displayed on the PTF card.
- CSCul73277 : During the upgrade from 9.51 to 9.53, CPT 50 became unreachable.
- CSCul01575: Database loss occurred when the pseudowire and Label Distribution Protocol (LDP) was configured on the same port.
- CSCui99137 : Database loss occurred when the MPLS-TE and REP was configured on the same interface.
- CSCui99626 : Database loss occurred when the pseudowire class used in a pseudowire on which CFM was configured, modified.
- CSCuj21906: Database loss occurred when the Label Distribution Protocol (LDP) was configured on the Link Aggregation (LAG) member port.
- CSCuj03949 : Database loss occurred when the MPLS-TE link attribute was configured on the AC port.
- CSCum97353 : Database loss occurred when the policy map mapped to the interface, was deleted.
- CSCuj00746 : After an upgrade from 9.512 to 9.523, pseudowire was down due to label allocation.
- CSCuo06503 : After an upgrade from 9.53 to 9.535, traffic loss was observed.
- CSCuj93899 : During the upgrade from 9.5.2.1 to 9.5.3.5, database loss occurred.
- CSCul76233 : CTC did not respond when the VPWS or VPLS services were modified.
- CSCum17440 : CTC did not allow the user to configure more than 8 Connectivity Fault Management (CFM) with the same level.
- CSCug15096 : CTC did not allow the user to login into IOS mode.
- CSCuo70319 : CTC did not allow the user to configure the pluggable port module (PPM) for the pluggables inserted in the MSTP card.
- CSCuo54065 : CTC did not support Generic Communications Channels (GCC) configuration for OTU2XP card.
- CSCul32735: SAT-COMM-FAIL alarm cleared automatically on CTC after reboot of TNC card.
- CSCug97315 : BKPMEM and EQPT- FAIL alarm raised.
- CSCuo24486 : PROT-CONFIG-MISMATCH alarm generated on the stand-by PTF card and database loss occurred when the PTF card was rebooted.
- CSCul71651 : Bit error displayed on the TDM pluggable when the following steps were performed:
- CSCud97155 : TNC crashed when tNetTask performed.
- CSCug97348 : TNC reloaded due to FIN attack.
- CSCum50368 :TNC crashed when the database was restored.
- CSCug97416 :TNC reset with tCORBA exception.
- CSCum23868 : PTM card status was not updated after reload.
- CSCun30867 : PTF card was unable to communicate with TNC.
Critical Bug Fixes in Release 9.5.3
Release 9.5.3 addresses the following critical fixes over Release 9.5.2.3:
- CSCuh32113: When TNC was activated after the system upgrade from 9.5.2 to 9.5.3, TNC rebooted continuously and could not be recovered.
- CSCui67091: After an upgrade from 9.5.2 to 9.5.3, state of all the MPLS-TP tunnels and pseudowires were changed to PARTIAL.
- CSCuc18985: After an upgrade from 9.5.1, database loss occurred when the uplink card was reset or database was reloaded with 128 members virtual forwarding instance (VFI).
- CSCug91371: An upgrade to 9.5.1.3 failed because the active PTF card failed in between the upgrade process.
- CSCue38018: After an upgrade from 9.5.1.2 to 9.5.2, database loss occurred if EVC was created on the same interface as that of pseudowire AC endpoints.
- CSCub41943: During the upgrade from 9.5.0 to 9.5.1, Transport Node Controller (TNC) card crashed when the channel-group data was fetched.
- CSCug47083: After an upgrade from 9.5.1 to 9.5.2.1, the EVPL circuits stopped forwarding traffic.
- CSCug29140: A pseudowire with a name containing a space at the beginning and the end disappeared when the CPT system was upgraded from 9.5.2.1 to 9.5.3.
- CSCuh15144: After an upgrade from 9.5.1 to 9.5.2.1, the SAT-COM-FAIL alarm was observed with the severity as minor.
- CSCug40521: Database loss occurred when the PTF was reset after deleting the interface on which an MPLS-TP tunnel was configured.
- CSCud90557: Database loss occurred when the user performed the following steps:
- CSCui04191: Database loss occurred when the user performed the following steps:
- CSCui22484: Database loss occurred when the user performed the following steps:
- CSCui12072: Database loss occurred when the user performed the following steps:
- CSCue26633: Database loss occurred when the user performed the following steps:
- CSCud66930: Database loss occurred when the user performed the following steps:
- CSCuh19362: Database loss occurred when the user performed the following steps:
- CSCuc42069: Database loss occurred when a pseudowire class (associated to a VPLS) was provisioned with the following values:
- CSCui09652: Database loss occurred when the pseudowire and destination port of a span were configured on the same port where a channel-group was already configured.
- CSCuh71428: Database loss occurred when the Pluggable Port Module (PPM) was deleted where the table-map was already configured.
- CSCui11280: Database loss occurred when an MPLS-TP link was configured the port which was destination port of a span.
- CSCui58996: Database loss occurred when the Label Distribution Protocol (LDP) was configured on the port where a Resilient Ethernet Protocol (REP) was already configured.
- CSCui60106: Database loss occurred when the Label Distribution Protocol (LDP) was configured on the port where an EVC was already configured.
- CSCug92219: The ONS-SC-E1-T1-CES and ONS-SC-E3-T3 SFPs did not work with CPT 50. The traffic did not flow and certain invalid parameters were observed during the provisioning.
- CSCuh51631: DS3 traffic did not resume after the PTF card was reset multiple times.
- CSCuc84965: The traffic was not flowing on 1 G CPT 50 when the user performed the following steps:
- CSCud70712: Traffic flow was not observed for the static pseudowires when the following steps were performed:
- CSCuh29838: Traffic flow was not observed for certain pseudowires when the following steps were performed:
- CSCub94383: TNC crashed on retrieving the equipment entity parameters when the CPU usage was high.
- CSCui45278: PTF crashed when Connectivity Fault Management (CFM) was configured and the CPU usage was high.
- CSCui39559: Standby PTF card reset when more than 1532 point–to–point (P2P) EVCs with Ethernet type dot1q were created.
- CSCuh76534: The table-map did not synched with the PTF card when more than one table-maps were configured on the port and the table-map used with the port was not first configured table-map.
- CSCui33079: PTM card crashed when the policy-map configuration was changed.
- CSCuc64508: The hostname of the PTF card changed to an IP address after a switchover was performed.
- CSCuf17323: The PTF card reset on a CPT 50 port when the following tasks were performed simultaneously on the port:
- CSCui50097: The standby PTF card reset due to non-default label mismatch which was configured before Stateful Switchover (SSO).
- CSCui01457: The PTF card crashed when the following tasks were performed:
- CSCue27382: Keepalive failures were observed at TNC when the line card was deleted using CTC. The PTF cards did not receive the boot-up response from TNC even after these were hard booted.
- CSCtz32511: CTC did not allow the user to create Generic Communications Channels (GCC) for GCC rates 192k and 400k.
- CSCua75095: CTC did not allow to delete a protected MPLS-TP tunnel if the lockout was enabled on one of its LSPs. The state of MPLS-TP tunnel changed to PARTIAL in CTC, but it remained as UP in Cisco IOS.
- CSCug47241: CTC did not allow to create a pseudowire between two nodes from releases 9.5.1 and 9.5.2.2 respectively.
- CSCuh96531: CTC allowed the user to create an EVC circuit or a pseudowire with Ethernet type dot1ad on the port where Ethernet type dot1q was already configured.
- CSCui19292: CTC allowed the user to enable MVR on the point–to–multipoint (P2MP) Bridge where Ethernet type dot1q was already configured.
- CSCug65485: When editing the policy-map using CTC QOS policy removed the policer and added it again even when no parameter was changed. This impacted services that were provisioned for the EVC.
- CSCuh97941: CTC displayed 0 as VLB Preempt Delay on the Open Packet Transport View > Provisioning > REP > Segment tab when a segment was created with VLB Preempt Delay enabled and with some valid preempt delay value.
- CSCuh12243: CTC displayed an error message when the user selected and deselected the queuing options for creating a table-map under the Provisioning > QoS > Policy Map > Create Policy Map > Action > Queuing tab.
- CSCug15096: The user was not able to login into Cisco IOS of the PTF card using CTC.
- CSCuf16842: The SNMP agent was getting stuck on the CPT 600 or CPT 200 chassis. This was observed for multiple versions of SNMP.
- CSCue84243: Remote Fault alarm was observed even the ports were up and running.
- CSCug18181: A CPT 50 console did not ask for credentials when accessed from any other CPT 50 device.
- CSCud34373: Channel groups were not listed in the Available Ports drop-down list of the EFP Configuration Preview screen when creating an EVC circuit using CTC.
- CSCug92060: Bidirectional Fault Detection (BFD) was flapping when it was configured over the unprotected tunnel midpoints.
- CSCua07169: A pseudowire continued to forward the traffic even when the pseudowire state was changed to DOWN using CTC.
- CSCua88616: If an endpoint PW neighbor was deleted from a mesh VPLS circuit containing EFPs, the VPLS circuit moved to Partial and UP state. When the VPLS circuit was cleared and re-queried, the circuits did not merge and two VPLS circuits were observed. One was in Discovered and UP state and another was in Partial and DOWN state.
- CSCuh69954: Error message displayed when the following steps were performed on the EFP port with VLAN range or list multiple times:
- CSCui12192: Policy class actions changed to 0 after it was edited for a class-map.
- CSCui46465: Y.1731 Delay Measurements was not working on Xconnect where MPLS-TP Tunnel and Attachment Circuit (AC ) were configured.
Critical Bug Fixes in Release 9.5.2.3
Release 9.5.2.3 addresses the following critical fix over Release 9.5.2.2:
- CSCue73365: CTC did not allow the user to create a pseudowire, VPLS or EVC on the port where the MPLS TP link was already configured and vice versa.
- CSCug47241: CTC did not allow to create a pseudowire between two nodes belonging to 9.5.1 and 9.5.2.2 respectively.
- CSCud70712: Some pseudowires did not come up when the following steps were performed:
- CSCug01617: The client port was wrongly counting the bandwidth of the protected pseudowire while creating the protected pseudowire circuit.
- CSCuh56656: The out link number of the forward and the reverse LSPs were getting swapped when the following steps were performed:
- CSCue14896: PTF cards were resetting automatically at regular intervals due to loss of communication between TNC and PTF.
- CSCug10545: The Performance Monitoring (PM) parameters of the OTN ports in the Extended Forward Error Correction (EFEC) mode was higher than the Standard Forward Error Correction (SFEC) mode.
- CSCub47224: The snmpgetbulk query was returning timeout without any response.
- CSCuf16842: The SNMP agent was getting stuck on the CPT 600 and CPT 200 chassis. This was observed for multiple SNMP versions.
- CSCuf35431: After an upgrade from release 9.5.2 to 9.5.2.1, the pseudowires with spaces in the pseudowire name were not available on the CTC.
- CSCug47083: After an upgrade from release 9.5.1 to release 9.5.2.1, the Ethernet Virtual Circuits (EVC) configurations were not found in the CPT 50 panels that were connected to the PTF card.
- CSCug40521: Database loss was observed when the following steps were performed:
- CSCuh19362: Database loss was observed when the following steps were performed:
- CSCuh29838: Traffic flow was not observed for certain pseudowires when the following steps were performed:
- CSCuc84965: Traffic flow was not observed for the 1 G CPT 50 when the following steps were performed:
Critical Bug Fixes in Release 9.5.2.2
Release 9.5.2.2 addresses the following critical fix over Release 9.5.2.1:
Critical Bug Fixes in Release 9.5.2.1
Release 9.5.2.1 addresses the following critical bug fixes over 9.5.2.
- CSCue94077: CTC did not allow to enter VLAN range when creating a class map.
- CSCue73421: When the show running-config command was executed through a telnet session for a large configuration file, the contents of the configuration file was displayed as garbled.
- CSCue73365: CTC and Cisco IOS allowed to configure an MPLS-TP link on the same interface on which a pseudowire, and Ethernet Virtual Circuit (EVC) was already configured. Similarly, CTC and Cisco IOS allowed to configure a pseudowire and EVC on the same interface on which an MPLS-TP lin was already configured.
- CSCue54833: CTC did not allow spaces in the PW Name field when creating a new pseudowire.
- CSCue66419: CTC did not allow the user to create a multisegment pseudowire.
- CSCue91711: The bandwidth value of a pseudowire changes to 0 when any modification is made on the Edit Circuit > General tab.
Critical Bug Fixes in Release 9.5.2
Release 9.5.2 addresses the following critical fixes over Release 9.5.1.2:
- CSCtw96586: Egress Quality of Service (QoS) was not working on point-to-multipoint (P2MP) EVC after a node power cycle.
- CSCtx24528: Egress QoS was not working when power cycling the node with Virtual Private LAN Services (VPLS) and a port-channel on a CPT 50 panel that was fanned out from a trib card.
- CSCuc01160: Traffic flow rate on Ethernet Flow Points (EFPs) dropped when an ingress QoS service policy was applied on an EFP when the encapsulation is double VLAN tagged and inner tag was VLAN range.
- CSCtx00536: Committed information rate (CIR) was not working for SFP+1 and SFP+2 ports in UL at the interface level.
- CSCub23788: ITU-T Y.1731 delay measurement was not working on a port-channel interface when the maintenance association profile was configured on a pseudowire and an EVC where the pseudowire was configured first followed by the EVC.
- CSCub36186: Layer 2 virtual forwarding interface (VFI) became partial when the existing endpoint psuedowire neighbor is deleted in a mesh VPLS circuit containing EFPs.
- CSCtx05374: High traffic switch time was observed during interconnect (IC) link switchover.
- CSCtz80539: Ethernet Connectivity Fault Management (CFM) UP maintenance endpoints (MEPs) did not learn the remote MEPs after 512 entries.
- CSCud05137: CTC always displayed the bandwidth (BW) value of an MPLS-TP tunnel as a rounded numerical value. For example, if 1500 Mbps was entered as the BW value when creating an MPLS-TP tunnel, CTC displayed it as 1 Gbps instead of 1.5 Gbps when the MPLS-TP tunnel was successfully created.
- CSCud95214: If unknown nodes existed in the network, CTC did not display some of the PPC spans in the route of the MPLS-TP tunnel that was displayed in the TP Tunnel Circuit Routing Constraints screen.
- CSCto67716: CTC displayed the default values of the optics PM parameters such as laser bias, receive optical power, and transmit optical power instead of NA on the Performance > Optics PM > Current Values tab for the SFPs that are not supported in CPT. These SFPs are ONS-SI-100-FX, ONS-SI-100-LX10, and ONS_SI_GE_LX.
- CSCua91006: CTC displayed -40dBm instead of NA in all the columns on the Performance > Optics PM > Current Values tab when a copper SFP was inserted into a CPT 50 slot.
- CSCub60793: CTC and Cisco IOS allowed Resilient Ethernet Protocol (REP) to be configured on the main port-channel interface.
- CSCuc57227: CTC allowed a port to be configured as a destination port when that port was a part of source port-channel in a span session.
- CSCuc31758: CTC allowed the interworking and protocol of a pseudowire class associated with a VPLS to be edited.
- CSCub50449: CTC displayed an error and did not reflect the required configuration when the following steps were performed:
- CSCua49867: Port state (10 GE and 1GE) of a CPT 50 panel that was displayed in CTC was different from the port state displayed in Cisco IOS.
- CSCtz68644: Packet Transport Fabric (PTF) card reset continuously due to a communication failure between the Transport Node Controller (TNC) and the PTF card.
- CSCua26265: Error burst was observed in DS1/DS3 traffic after the TNC card was reset.
- CSCub33820: The management connectivity of the CPT 200 or CPT 600 shelves running TNC or TSC cards was lost.
- CSCuc81545: Uplink card restarted continuously when a table map was applied to an interface where an MPLS-TE tunnel was created.
- CSCty88141: Egress span was not working on multiple cards.
- CSCtz85679: A memory leak was observed when configuring an EFP span for a range of EFPs that had more than eight EFPs.
- CSCuc65212: Database loss occurred when a port (with L2PT configuration) that was provisioned on an uplink card, a CPT 50 panel or a trib card was deleted and the uplink card was reset.
- CSCua09563: Database loss occurred when CTC allowed an REP link and an MPLS-TP link to be configured on the same interface.
- CSCuc36879: Database loss occurred when the protocol and status of a pseudowire class were modified as LDP and oam respectively.
- CSCud53118: Database loss occurred when a fully loaded CPT 600 chassis was upgraded from Release 9.5.1 to Release 9.5.2.
- CSCtq67285: A traffic hit was experienced in the following scenarios: Scenario A Scenario B
Critical Bug Fixes in Release 9.5.1.2
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
No new feature or functionality is added in Releases 9.5.1.1, 9.5.1.2, 9.5.2, 9.5.2.1, 9.5.2.2, 9.5.2.3 and 9.5.3. 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.
NoteCFM 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
Use the Cisco CPT Release Notes, Release 9.5.3.5 in conjunction with the following referenced Release 9.5.x publications:
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 deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)