 Feedback
|
Table Of Contents
Software Licenses and Features
Finding the Software Version and Feature Set
Installing Software Images and Licenses
Open Caveats for Cisco Release 15.2(4)S
Open Caveats for Cisco Release 15.2(4)S1
Open Caveats for Cisco Release 15.2(4)S2
Open Caveats for Cisco Release 15.2(4)S3
Resolved Caveats for Cisco Release 15.2(4)S1
Resolved Caveats for Cisco Release 15.2(4)S2
Resolved Caveats for Cisco Release 15.2(4)S3
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Cisco ME 3800X, ME 3600X and ME 3600X-24CX Switch, Cisco IOS Release 15.2(4)S and Later Releases
April 23, 2013
These release notes include important information about the following Cisco IOS releases that run on the Cisco ME 3800X, ME 3600X and ME 3600X-24CX switches:
•
Cisco IOS Release 15.2(4)S
•
•
•
These release notes also include the limitations, restrictions, and caveats that apply to these releases.
You can verify that these release notes apply to your switch as follows:
•
•
•
For the complete list of Cisco ME 3800X, ME 3600X and ME 3600X-24CX switch documentation, see the "Related Documentation" section.
You can download the switch software from this site (registered Cisco.com users with a login password):
Contents
•
•
•
•
•
•
Hardware Supported
Software Licenses and Features
If you have a service support contract and order a software license or if you order a switch, you receive the universal software image, available in crypto and noncrypto versions. If you do not have a service support contract, such as a SMARTnet contract, download the image from Cisco.com.
The ME 3600X supports these licenses:
•
•
•
For differences in feature support for each license, see Table 2 and Table 3.
The ME3600X-24CX supports the above licences plus:
•
•
•
The ME 3800X supports these licenses plus a scaled license that can be installed with any of these licenses to increase the supported values for that license, for example, more MAC addresses, VLANs, IPv4 routes, and so on.
•
•
•
•
For differences in feature support for each license, see Table 4 and Table 5.
To install a software image, see the "Upgrading the Switch Software" section and the "Working with the Cisco IOS File System, Configuration Files, and Software Images" chapter in the software configuration guide.
To install a software license, see the "Cisco IOS Software Activation Tasks and Commands" chapter in the Cisco IOS Software Activation Configuration Guide:
http://www.cisco.com/en/US/partner/docs/ios/csa/configuration/guide/csa_commands.html
An emergency evaluation license is embedded in the software image and does not require the installation of a license file. Specify which evaluation license to enable by using the license boot level command.
Enabling evaluation license on an ME 3800X:
ME3800X# configure terminalME3800X(conf)# license boot level <MetroEthServices|MetroIPServices|MetroAggrServices>
Note
ME3800X(conf)# exitME3800X# write memoryME3800X# reloadNote: This evaluation license will be validated only after reload.Enabling evaluation license on an ME 3600X:
ME3600X# configure terminalME3600X(conf)# license boot level <MetroIPAccess|AdvancedMetroIPAccess>
Note
ME3600X(conf)# exitME3600X# write memoryME3600X# reloadNote: This evaluation license will be validated only after a reload.After entering the license boot level command, you are prompted to accept the End-User Licensing Agreement (EULA). After accepting the EULA, exiting configuration mode, and saving the running configuration to memory, reload the switch to apply the evaluation license.
Note
Upon installation of a license file, the license automatically updates to the new license type. There is no need to clear the evaluation license.
Upgrading the Switch Software
•
•
•
Finding the Software Version and Feature Set
The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. The image is stored on the system board flash device (flash:).
Note
You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.
Deciding Which Files to Use
The software installation procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.
Installing Software Images and Licenses
The switch is shipped with the latest software image installed. Follow the instructions in this section if you need to reinstall or upgrade the software image.
Before installing your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See End of Sale and End of Life Products at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/prod_category_end_of_life.html
You can copy the software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command. You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference at this URL:
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
To download software, follow these steps:
Step 1
Step 2
a.
b.
For ME 3600X, navigate to Switches > Service Provider Switches - Ethernet Access.
c.
d.
Note
Step 3
For more information, refer to Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, refer to the software configuration guide for this release.
Step 6
Switch# archive download-sw tftp:[[//location]/directory]/image-name.tar•
•
•
•
This example shows how to download an image from a TFTP server at 198.51.100.1 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.51.100.1/image-name.tarYou can also download the image file from the TFTP server to the switch and keep the current image by using the /leave-old-sw option instead of the /overwrite option.
Note
The installation process extracts the tar file with all the files and the IOS image, and sets the BOOT directory to the created directory in flash memory. The process takes approximately 5 to 10 minutes, and at some stages might appear to have stopped.
Step 7
Switch# show bootBOOT path-list :flash:/me380x-universal-mz.151-2.EY/me380x-universal-mz.151-2.EY.binConfig file : flash:/config.textPrivate Config file : flash:/private-config.textManual Boot : noHELPER path-list :
Step 8
Switch# reloadAfter the installation, the switch is running the universal image. Follow these steps to install a purchased license with increased capabilities. To purchase a license, contact Cisco.
Step 1
Step 2
Switch# license install flash:LICENSE_FILENAMEorSwitch# license install tftp://location/LICENSE_FILENAMEStep 3
Switch# config tSwitch(config)# license boot level license_nameStep 4
Switch# license install flash:SCALED_LICENSE_FILENAMEorSwitch# license install tftp://location/SCALED_LICENSE_FILENAME
Note
Step 5
Switch# reload
Installation Notes
You can assign IP information to your switch by using these methods:
•
•
•
New Software Features
The following sections provides information on new software features:
Cisco IOS Release15.2(4)S
The following new software features are introduced in Cisco IOS Release 15.2(4)S.
MPLS-TP Support—The Multiprotocol Label Switching (MPLS) Transport Profile (TP) feature enables you to create tunnels that provide the transport network service layer over which IP and MPLS traffic traverse. MPLS-TP tunnels enable a transition from Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy (SDH) time-division multiplexing (TDM) technologies to packet switching to support services with high bandwidth requirements, such as video. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/chassis/configuration/guide/swmp_transport_profile.html
6PE Support—The IPv6 Provider Edge (6PE) feature facilitates provisioning of IPv6 services for the Cisco ME3600X and ME3800X switches. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/sw6vpe.html
IPv6 VPN over MPLS (6VPE)—IPv6 VPN Provider Edge (6VPE) feature provides support for IPv6 VPN services over MPLS core networks. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/sw6vpe.html
Synthetic Frame Loss Measurement (ETH-SLM)—The Synthetic Frame Loss Measurement (ETH-SLM) feature measures frame loss using synthetic frames, rather than data traffic. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swy1731pm.html
IPSLA Support for ETH-SLM (Ethernet Synthetic Loss Measurement in Y1731)—This feature provides IPSLA Support for ETH-SLM (Ethernet Synthetic Loss Measurement in Y1731). For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swy1731pm.html
BGP 4 bytes ASN—The BGP Support for 4-byte autonomous system numbers (ASN) feature provides support for 4 byte AS numbers in BGP per RFC 4893. For details about this feature see: http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_bgp/configuration/15-1sg/irg-4byte-asn.html
BGP Per neighbor graceful restart configuration—The BGP Per neighbor graceful restart configuration feature allows for enabling and disabling Graceful Restart Per BGP Neighbor. For details about this feature see: http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_bgp/configuration/15-1sg/irg-grace-restart-neighbor.html
BGP Support for Dual AS Configuration for Network AS Migration—This feature provides BGP Support for Dual AS Configuration for Network AS Migrations. For details about this feature see: http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_bgp/configuration/15-1sg/irg-dual-as.html
Table Map QoS—Table Map QoS functionality-Enhancement to existing feature. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swqos.html
VRRP MIB - RFC2787—This feature provides support for RFC2787: "Definitions of Managed Objects for the Virtual Router Redundancy Protocol". For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swvrrp.html
BFD-BFD Hardware Offload Support—BFD-BFD Hardware Offload Support-This feature provides support of BFD sessions in ME3600X-24CX hardware supporting offloading of BFD sessions. For details about this feature, see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/chassis/configuration/guide/swbfd.html
Circuit Emulation over Packet Switched Network—The feature provides support for Circuit Emulation over Packet Switched Network feature on Cisco ME3600x-24CX switch. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/chassis/configuration/guide/swpseudowire.html
DAI—DAI (Dynamic ARP Inspection)-DAI is used to verify the sanity of IP to MAC address mappings specified in ARP packets sent by connected hosts or neighboring switches. This prevents man in the middle attacks that can be carried out by poisoning ARP with the help of ARP packets containing invalid IP to MAC address mappings. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swdynarp.html
T1/E1 Support—T1/E1 support on ME-3600-24CX-This feature provides support for T1/E1 ports on ME3600C-24CX switch. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_2_S/chassis/configuration/guide/sw_T1-E1.html
PBR—Policy based routing (PBR) provides a flexible means of routing packets by allowing the user to configure a defined policy for traffic flows. This lessens reliance on routes derived from routing protocols. PBR gives you more control over routing by extending and complementing the existing mechanisms provided by routing protocols. PBR allows you to set the IP precedence. It also allows you to specify a path for certain traffic, such as priority traffic over a high-cost link.
For Cisco ME 3600X, the PBR feature is supported with the application SDM template. For Cisco ME 3800X, the this feature is supported with the scaled license. For details about this feature see:
OSPF TTL Security Check—The OSPF TTL Security Check feature allows the addition of an extra layer of protection to OSPF by setting and checking TTL values. Neighbors will send packets with a TTL of 255 and we will only accept OSPF packets with a 254 TTL. For details about this feature see: http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.2_4_S/configuration/guide/swospf_ttl.html
EVC MIBThe EVC MIB is a Cisco proprietary Simple Network Management Protocol (SNMP) MIB for managing an Ethernet infrastructure. SNMP versions 1 and 2c are supported. The EVC MIB consists of 18 tables and three notifications. The command-line interface (CLI) commands snmp-server enable traps ethernet evc and snmp-server host traps evc are implemented for enabling or disabling notifications. Notifications are disabled by default.
Support for service instances such as Layer 2 VLAN interfaces was added in Cisco IOS Release 12.2(33)SRD1. Service instances are represented as subinterfaces in the IF-MIB and associated with an ifIndex. Four commands support this feature: debug if-mgr trace efp-ext, debug if-mgr errors efp-ext, snmp ifindex, and snmp trap link-status. The snmp commands are supported under service instance configuration mode (config-if-srv). Changes to configurations and existing commands are not required.
To use the EVC MIB, the Ethernet Infrastructure module must be present in the Cisco IOS software image, and Metro Ethernet Infrastructure High Availability must be in place. SET operations are not supported on any object in Cisco IOS Releases 12.2(33)SRD and 12.2(33)SRD1.
For detailed information about EVC MIB-related commands, see the Cisco IOS Carrier Ethernet Command Reference, found here: http://www.cisco.com/en/US/partner/docs/ios-xml/ios/cether/command/ce-cr-book.html
For detailed information about SNMP commands, see both the Cisco IOS Network Management Command Reference, found here: http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_book.html and the Cisco IOS Interface and Hardware Component Command Reference, found here: http://www.cisco.com/en/US/docs/ios/interface/command/reference/ir_book.html
For detailed information about the EVC MIB, and to locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use the Cisco MIB Locator, found here: http://tools.cisco.com/ITDIT/MIBS/servlet/index
Cisco IOS Release15.2(4)S2
Cisco ME 3600X 24CX 1588-2008 Boundary Clock—The Cisco ME 3600X 24CX Series Switch supports the Precision Time Protocol (PTP) as defined by the IEEE 1588-2008 standard. PTP provides accurate time synchronization over packet-switched networks. For details abut this feature see:
Important Note
Switch Port Analyzer (SPAN) is not supported due to a hardware limitation.
Open and Resolved Caveats
The following section provides information on open and resolved caveats:
•
•
•
•
•
•
•
Open Caveats for Cisco Release 15.2(4)S
•
EVC BD split-horizon group 0 and 2 breaks traffic over VPLS.
EVC BD split-horizon group 0 and 2 breaks traffic over VPLS. Group 1 forwards traffic over the PW.
When SH is enabled, SH group 0 and group2 match on the lowest 1 or 2 bits. The L2 logical ID for ARP packets injected use id 31 (all 1s). Therefore, it matches on the lowest bits and is SH'ed out, and ARP never resolves.
Workaround: None.
•
W2 crashes with PIM Snooping enabled and mcast traffic running.
Workaround: None.
•
Crash observed on enabling scaled 6PE configuration.
Workaround: None.
•
Multicast traffic may not be forwarded correctly when traffic is received on a layer 2 port-channel.
The PIM DR forwards traffic onto the layer 2 port-channel, while the other node only has a *,G entry. In this situation, the traffic is not forwarded out of the layer 2 port with receivers.
Conditions: This issue is observed in a setup with two Cisco ME 3600X with layer 2 port-channel in between and mVPN. This issue is observed only on port-channel 1.
Workaround: Avoid port-channel 1 by creating a dummy port-channel 1 and start using from port-channel 2 until port-channel 126.
•
IPv6 Traffic forwarded to wrong VRF when address is same on both VRFs.
When traffic is sent from the VRF1 interface of UPE-1 to 5000::1, the traffic is forwarded over the VRF2 interface of UPE-2. It should be sent over the VRF1 interface on UPE-2.
Workaround: None.
•
ME3800 is corrupting the VLAN information in the packet.
The ME3800 acts as an nPE, sending the wrong VLAN tag for a VLAN in the egress direction towards spoke.
Workaround: None.
•
OSPF Flaps with RPW.
OSPF flaps appear at intervals of around 30 minutes.
Workaround: None.
•
Multicast streams stop being forwarded with message MET FULL ERR.
Some multicast streams may be stopped being forwarded or new multicast streams cannot be joined. When this happens, a MET FULL ERR message appears.
Conditions: This issue is observed on a Cisco ME 3600X running IOS 15.2(2)S1.
Workaround: None. A reboot is required to temporarily clear the situation.
Open Caveats for Cisco Release 15.2(4)S1
•
Portchannel is in a suspended state, with the peer throwing messages that LACP is not enabled on the remote node.
Conditions: This issue is observed upon reload.
Workaround: Remove/add the untagged service instance which has L2peer STP and LACP configured.
•
BGP VPNV4 flaps after reload if BGP peer route is learned via TE.
Upon reloading the Cisco ME 3600X 24CX, its BGP peership with the Cisco ME 3800X comes up, but the peer PE Cisco ME 3800X does not learn any routes from the Cisco ME 3600X 24CX after reloading. Upon expiry of the hold timer on the Cisco ME 3800X, the BGP goes down and comes back up. Again, no routes are learned on the Cisco ME 3800X and the BGP goes down. This happens continually. The same behavior is observed upon reloading the Cisco ME 3800X.
Conditions: All PE (Cisco ME 3600X, Cisco ME 3800X, and Cisco ME 3600X 24CX) have TE tunnels starting from each PE to all other PE. Autoroute announce is configured on all PEs, so PEs are reachable to each other via a TE tunnel. Each PE has VPNV4 peership with all other PEs.
Workaround: Disable the TE tunnel, then after the first flap, the routes are learned and BGP comes up. Then enable TE and BGP remains up. Upon setting IP "ip tcp mss adjust 1200" BGP comes up.
•
Tracebacks seen at n13mmpd_adjmgr_13m_update_port_mcast_nh
The following traceback appears:
platform assert failure: l3m_port_met->efp.ge_allocated == TRUE: ../src/src-asic/adjmgr_l3m.c: 6110: del_l3m_efp_met-Traceback= 642CF0z 1F2A084z 2062840z 20659F8z 20668A0z 294866Cz 2948D18z 294D780z 29A9300z 29A47C0zConditions: Specific configuration is loaded and traffic is started.
Workaround: None.
•
MPLS LSP ping does not work when the PE-to-PE TE tunnel is down.
Conditions: The PE-to-PE tunnel is down, and the next hop to PE1 has TE tunnel to remote PE2, and PE1 is ME3600.
Workaround: None.
•
The Cisco ME 3600X crashes when using the config replace command with certain QoS configurations.
Conditions: When you try to replace the configuration on the router with the configuration that removes the configurations, the router crash occurs.
Workaround: None.
•
Cisco ME 3600X: Ingress QoS tcams are not cleared after certain dynamic changes.
Conditions: Upon removing the encapsulation from the service instance and then deleting the service instance, QoS tcams are not cleared.
Workaround: Instead of deleting the encapsulation first, delete the service instance.
•
Continuous platform asserts failure tracebacks with CFM over Xconnect on the box.
Conditions: This issue occurs with CFM over Xconnect with MPLS TE in core. Flap the core facing link.
Workaround: None.
•
Xconnect traffic is routed if the MTU exceeds the core MTU, in case of MPLS over SVI.
An IP lookup is done on the xconnect traffic, which should not happen.
Conditions: LS is configured on SVI and the MTU exceeds the core MTU.
Workaround: MPLS over SVI is not supported in the 15.2(4)S releases.
•
The Cisco ME 3600X and Cisco ME 3800X unicast met shows multiple ReplicationContextQueueEntry and traffic is flooded to all ports in the VLAN.
Conditions: This issue is observed when an access port is in the same VLAN as the rep segment and a rep flap is seen.
Workaround: Clear mac-address table fixes the CQE entries.
•
Broadcast traffic flows over Standby Spoke VC and then gets punted.
Conditions: The traffic comes over the Core VCs and then flows over the Standby Spoke VC from Hub to Spoke. In the Spoke, the traffic received from the Spoke VC gets punted to the CPU (Software Forwarded).
Workaround: None.
•
Native mcast traffic is not forwarded over the Cisco ME 3600X after a core INTF shut/no shut operation.
After the repetitive trigger on mVPN setup on the router (such as core INTF shut/no shut), one of the native multicast streams of terrain is not flowing as expected.
Workaround: None.
•
On the Loopback interface used for BGP neighbor establishment, deleting the "ip pim sparse-mode" and adding back the "ip pim sparse-mode" results in tracebacks. Memory leaks are also observed.
Conditions: This issue has been observed under the following conditions:
–
–
Workaround: None.
•
VRF replication is not occurring with the Cisco ME 3600X or Cisco ME 3800X as the VRF RP.
Conditions: This issue has been observed under the following conditions:
–
–
–
Workaround: None.
•
Traffic is not flowing out of the GE port on the Cisco ME 3600X.
The egress service policy on EFP is dropping all traffic in egress. The offered rate equals the drop rate. the interface output rate is zero, and the output drop is increasing.
Conditions: This issue is observed on a Cisco ME 3600X running 15.2(2)S.
•
Enabling Dynamic ARP Resolution (DAI) on a VLAN may cause ARP resolution to fail for hosts in other VLANs.
Workaround: Enable DAI for the failing VLAN with IP ARP inspection trust. For example:
ip arp inspection vlan 30int gi 0/10ip arp inspection trustint gi 0/11ip arp inspection trust•
CFM over Xconnect remote MEPs are not learned.
Conditions: Have CFM over Xconnect on the Cisco ME 3600X and TE tunnels in the core. Core link is mapped to the forwarding ASIC.
Workaround: Remove the TE tunnels in the core or have the core link on the forwarding ASIC.
•
Traffic drop is observed on egress direction of L2VPN when cos filtering is configured on EVC.
Conditions: Egress cos filtering with L2VPN drops packets.
Workaround: Attach pseudowire-class with interworking type as ethernet VLAN.
Open Caveats for Cisco Release 15.2(4)S2
•
DHCP snooping binding is not established on an EVC BD trusted port.
Conditions: When DHCP snooping is enabled on one or more VLANs and EVC BD is configured on a trusted port that is connected towards the SP network/DHCP server, the client does not receive the IP address and DHCP snooping binding is not established.
Workaround: None. Only the switchport can be configured as a trusted port for now.
•
Policy-map gets accepted at port-level even if the sum of the child bandwidth is more than the parent shaper value.
Conditions: Policy-map on the service instance is added first and then the port-shaper value is added.
Workaround: Design the QoS policy-map so that the parent shaper value is equal to or more than the sum of the child bandwidths.
•
MAC withdrawal does not occur.
Conditions: This issue is observed upon shutting the VFI's VLAN on NPE. Failure of the spoke VC works as expected.
Workaround: Fail only the spoke VC without affecting the VFI and core VCs on NPE1.
•
The portchannel is in a suspended state, with the peer throwing messages that LACP is not enabled on the remote node.
Conditions: This issue is observed upon reload.
Workaround: Remove/add the untagged service instance that has l2peer STP and LACP configured.
•
When DHCP requests are sent to renew the allocated IP address, and DHCP host tracking is enabled on the switch, the CPU utilization periodically reaches 100%.
Conditions: DHCP snooping is enabled on one or more VLANs on the Cisco ME 3600X and ME 3800X running IOS 15.2(2)S or a higher version. DHCP snooping host tracking is configured. A DHCP renew request is sent from a DHCP client.
Workaround: Disable DHCP snooping host track CLI.
•
Confirm and Exceed action counters in the show policy-map interface are not getting cleared with scale configs upon executing the clear counters command.
Conditions: Observed when executing the clear counters command.
Workaround: Remove the policy-map and add it back.
•
Traceback observed upon creating a TE tunnel with 6PE/6VPE configuration. No functionality impact.
Conditions: Configure 6PE/6VPE and create a TE tunnel with autoroute announce.
Workaround: None.
•
Multicast traffic may not be forwarded correctly when traffic is received on a layer 2 port-channel.
Conditions: This issue is observed with a pair of Cisco ME switches with layer 2 port-channel in between, with layer 2 access port on the non DR PIM neighbor.
Workaround: Create a dummy portchannel1 (poch1) and start using from portchannel2 until portchannel26. Do not use the dummy portchannel1.
•
Nuclear Header Error Message is observed.
Conditions: These messages are observed only if more that one OSPF neighbors is established with more than one RoutedPseudowire enabled interface and OSPF flaps.
•
1PPS configuration is rejected while changing router roles from master to slave or slave to master with 1PPS configuration.
Conditions: The configurations input 1pps 0/0 on the master and output 1pps 0/0 on the slave are not deleted when PTP is unconfigured.
Workaround: Unconfigure input 1pps 0/0 or output 1pps 0/0 before unconfiguring PTP.
•
In a 1:1 (one active and one standby) scenario, when the hot standby converges to active, the port-channel does not come down, but the REP is re-converging. The fast-switch over happens in nearly 1 second.
Conditions: This issue is observed in a 1:1(one active and one-standby) scenario, when the hot standby converges to active.
Workaround: None.
•
Broadcast traffic flows over the Standby Spoke VC and then gets punted.
Conditions: The traffic comes over the Core VCs (as they are up) and the flows over the Standby Spoke VC from Hub to Spoke. In the Spoke, the traffic received from the Spoke VC gets punted to the CPU (Software Forwarded).
Workaround: None.
•
On the Loopback interface used for BGP neighbor establishment, deleting the ip pim sparse-mode and adding back ip pim sparse-mode results in tracebacks. Memory leaks are also observed after this.
Conditions: This issue is observed under the following conditions:
–
–
Workaround: None.
•
On the Cisco ME 3600X and ME 3800X, running IOS 15.2S or earlier, when EVC BD is configured on more than 1 port and modification of encapsulation and BD are done on the ports, an assert accompanied with traceback is thrown with decode pointing to L2 Multicast MET.
Conditions: This issue is observed only with the following sequence of steps, even when IGMP snooping is disabled by default:
1.
2.
3.
4.
Workaround: The above issue does not occur when steps 3 and 4 (above) are reversed; in other words, when EVC BD is modified on the second port followed by the first port. The issue also does not occur for EVC BD configuration on multiple ports with different BD on each port.
•
The Cisco ME 3800X stops forwarding traffic and crashes.
Conditions: This issue is observed when a QoS policy applied to a EFP on a 10G interface is removed.
Workaround: None.
•
With the ME3600/ME3800 connected back to back with GIG 0/16, the Multicast traffic does not flow.
Conditions: This issue is observed under the following conditions:
–
–
Workaround: None.
•
The PXE client network boot is failing when a Cisco ME 3600X running 15.2(4)S is the DHCP relay agent.
The Cisco ME 3600X is changing the option 54 'DHCP Server Identifier' address to it's own ip address in the DHCP Offer received from the PXE DHCP server, causing the client to send his PXE boot request (port 4011) to the Cisco ME 3600X instead of to the PXE server.
Workaround: Downgrade the Cisco ME 3600X to the latest 15.1(2)EY release.
•
DWDM SFP+ are supported in Cisco ME 3600X switches, but when inserted, this switch is not recognizing those DWDM in the SNMP ENTITY-MIB.
Conditions: When a DWDM SFP+ is present on the Cisco ME 3600X switch.
Workaround: None.
•
The Cisco ME 3800X and ME 3600X fails to trigger a watchdog crash in certain scenarios.
Conditions: This issue is observed with soaking over a prolonged period of time.
Workaround: None.
•
Table-map marking is not getting removed after deleting the class-default.
Conditions: Packets continue to get marked as per previous table-map config, even when the configuration is deleted.
Workaround: Detach and re-attach the policymap.
•
With scale EVC Xconnect configuration and same policy-map applied on all of the EVCs, deleting and adding a user-defined class-map results in assert messages on the forwarding ASIC.
Conditions: This issue is observed upon adding and deleting the user-defined class-map.
Workaround: Remove the policy-map and make the dynamic modification on the policy-map. Or, there has to be a delay in the removal and addition of the class-map.
•
The Cisco ME 3800X and a Cisco 7600 are working as PE devices, and they have multiple core connections between them. If we bounce one of the core interfaces between the Cisco ME 3800X and the Cisco 7600 and the attachment circuit (AC) simultaneously on the Cisco ME 3800X, we see that the VPLS status on the Cisco ME 3800X shows as up but it shows as down on the Cisco 7600.
Conditions: There should be multiple connection between core devices.
Workaround: Bounce the attachment circuit on the Cisco 7600 to resolve the issue.
•
6VPE packets get punted and policed.
Conditions: ESP header is enabled.
Workaround: None.
•
Traffic forwarding on EFPs fails after removing mac-security.
Conditions: When removing mac-security with the deny option from EFP, traffic fails to be forwarded on that EFP.
Workaround: Remove and re-add the service instance.
•
On the Cisco ME 3600X, need support for dot1dBasePortIfIndex OID.
Conditions: SNMP walk OID dot1dBasePortIfIndex (.1.3.6.1.2.1.17.1.4.1.2) does not work.
Workaround: None.
•
A CPU hog, followed by a crash, is observed.
Conditions: Peer device flap or network instability can cause this issue.
Workaround: This issue does not occur on a stable network.
•
Y1731PM is not working in the following situations:
–
–
Conditions:
The core facing interface is configured as rewrite ingress tag pop 1 symmetric, as follows:
interface GigabitEthernet0/9switchport trunk allowed vlan noneswitchport mode trunkservice instance 1 ethernet testencapsulation dot1q 151rewrite ingress tag pop 1 symmetricbridge-domain 151!endThe Q-inQ interface is configured as follows:
interface GigabitEthernet0/1switchport trunk allowed vlan noneswitchport mode trunkservice instance 1 ethernet testencapsulation dot1q 151 second-dot1q 110bridge-domain 151cfm mep domain l7 mpid 555cos 1!Workaround: None.
•
With two separate XFPs installed in ports Te0/1 and Te0/2, the optic types reported by the show interface status, show interface TeX/X capabilities, and the show interfaces tenGigabitEthernet X/X transceiver properties commands are not accurate.
Conditions: This issue is observed upon inserting two different types of XFPs in a Cisco ME 3600X running 15.2(4)S1.
Workaround: To verify that XFP is installed, run one of the following commands: show controllers ethernet-controller tenGigabitEthernet 0/1 phy or show inventory.
Open Caveats for Cisco Release 15.2(4)S3
•
Broadcast traffic flows over standby spoke VC and then gets punted.
Conditions: The traffic comes over the core VCs as they are up and then flows over the standby spoke VC from hub to spoke. In the spoke, that traffic received from the spoke VC gets punted to the CPU (software forwarded).
Workaround: There is no known workaround.
•
The following messages are output, and system crash occurs on an ME3600X node:
Mar 15 05:01:40.999 JST: %PLATFORM_NCEF-3-ADJ: NULL OCE handle for fib 10.239.145.114/32 Tbl:1-Traceback= 641BB8z 2C198D4z 2C2BF44z 2C32DB4z 2C2F564z 2C2BCFCz 2C27640z 2C63810z 2C5ECD0zMar 15 05:01:42.539 JST: %SYS-2-CHUNKBADROOTCHUNKPTR: Bad root chunk pointer in chunk header, chunk 0x12B8C3FC data 0x12B81318 root chunk ptr 0x0-Process= "Check heaps", ipl= 0, pid= 5 -Traceback= 641BB8z 17CA67Cz 17CB1DCz 17F1BFCz 2C63810z 2C5ECD0zMar 15 05:01:44.519 JST: %SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (13/10),process = Check heaps.-Traceback= 0x2491838z 0x2492390z 0x20BFDECz 0x20C14D0z 0x20BE958z 0x17ED274z 0x17CB860z 0x17CA68Cz 0x17CB1DCz 0x17F1BFCz 0x2C63810z 0x2C5ECD0zConditions: System crash occurs on an ME3600X node after changing route-map on route-reflector that establishes ME3600X.
ME3600X is route-reflector-client. The route-map setting that you change on route-reflector is output route-map for another route-reflector-client, not for ME3600X.
Workaround: None.
•
ARP resolution gets failed for a vlan after enabling DAI on another VLAN.
Conditions: This issue is seen after enabling DAI on another VLAN.
Workaround: Enable DAI on VLAN of interest.
Resolved Caveats for Cisco Release 15.2(4)S1
•
SVI link up delay issue on flexlink with VLB and Preemption.
SVI is not coming up for a long time, even though there are active ports in that VLAN. This issue occurs with flexlink + preemption + VLAN load balance configuration.
Conditions: Flexlink with preemption and VLAN load balance.
Workaround: None.
•
Cisco ME 3600X QoS: Cos-inner value has to be preserved in the case of POP2.
In an EVC POP1 - POP2 scenario, the egress set cos command previously wrote cos of both outer VLAN and VLAN-inner. Now the egress set cos command writes cos of only the outer VLAN.
Workaround: None.
•
The Cisco ME 3800X crashes during an interface flap.
CPU hog errors may also be seen at the time of the crash (such as SYS-3-CPUHOG). The task is running for (186028) msecs, more than (2000) msecs (1/0), process = Non-Qos Events Process.
Conditions: IGMP and SVI are configured.
Workaround: None.
Resolved Caveats for Cisco Release 15.2(4)S2
•
Cisco ME 3600X: Ingress QoS tcams are not cleared after certain dynamic changes.
Conditions: Upon removing the encapsulation from the service instance and then deleting the service instance, QoS tcams are not cleared.
Workaround: Instead of deleting the encapsulation first, delete the service instance.
•
Native mcast traffic is not forwarded over the forwarding ASIC after a core INTF shut/no shut operation.
After the repetitive trigger on mVPN setup on the router (such as core INTF shut/no shut), one of the native multicast streams of terrain is not flowing as expected.
Workaround: Perform one of the following commands:
clear ip mroute <mcast_group>clear ip route *•
Enabling Dynamic ARP Resolution (DAI) on a VLAN may cause ARP resolution to fail for hosts in other VLANs.
Workaround: Enable DAI for the failing VLAN with IP ARP inspection trust. For example:
ip arp inspection vlan 30int gi 0/10ip arp inspection trustint gi 0/11ip arp inspection trust•
CFM over Xconnect remote MEPs are not learned.
Conditions: Have CFM over Xconnect on the Cisco ME 3600X and TE tunnels in the core. Core link is mapped to the forwarding ASIC.
Workaround: Remove the TE tunnels in the core or have the core link on the forwarding ASIC.
•
Upon executing the sh inv command when SFP-10G-LR SFP-10G-SR is present in a Cisco ME 3800X or ME 3600X, the description is missing.
Conditions: SFP-10G-LR SFP-10G-SR should be present in 10G ports.
Workaround: None.
•
The Cisco ME 3600X-24CX switch crashes.
Conditions: An exception is observed when an unsupported 3rd party SFP with invalid EEPROM content is inserted and replaced with a Cisco supported SFP when the interface is in an error-disabled state.
Workaround: Use a supported SFP.
Resolved Caveats for Cisco Release 15.2(4)S3
•
Confirm and Exceed action counters in the show policy-map interface are not getting cleared with scale configs upon executing the clear counters command.
Conditions: Observed when executing the clear counters command.
Workaround: Remove the policy-map and add it back.
•
Continuous platform asserts failure tracebacks with CFM over Xconnect on the box.
Conditions: This issue occurs with CFM over Xconnect with MPLS TE in core. Flap the core facing link.
Workaround: None.
•
Multicast traffic may not be forwarded correctly when traffic is received on a layer 2 port-channel.
The PIM DR forwards traffic onto the layer 2 port-channel, while the other node only has a *,G entry. In this situation, the traffic is not forwarded out of the layer 2 port with receivers.
Conditions: This issue is observed in a setup with two Cisco ME 3600X with layer 2 port-channel in between and mVPN. This issue is observed only on port-channel 1.
Workaround: Avoid port-channel 1 by creating a dummy port-channel 1 and start using from port-channel 2 until port-channel 126.
•
1PPS configuration is rejected while changing router roles from master to slave or slave to master with 1PPS configuration.
Conditions: The configurations input 1pps 0/0 on the master and output 1pps 0/0 on the slave are not deleted when PTP is unconfigured.
Workaround: Unconfigure input 1pps 0/0 or output 1pps 0/0 before unconfiguring PTP.
•
The Cisco ME 3800X stops forwarding traffic and crashes.
Conditions: This issue is observed when a QoS policy applied to a EFP on a 10G interface is removed.
Workaround: None.
•
DWDM SFP+ are supported in Cisco ME 3600X switches, but when inserted, this switch is not recognizing those DWDM in the SNMP ENTITY-MIB.
Conditions: When a DWDM SFP+ is present on the Cisco ME 3600X switch.
Workaround: None.
•
ME3600X: Unexpected deferred is counted in certain conditions.
Conditions: Unexpected deferred is counted on egress interface in MPLS network, although the duplex setting is full.
Workaround: None.
•
The Cisco ME 3800X and ME 3600X fails to trigger a watchdog crash in certain scenarios.
Conditions: This issue is observed with soaking over a prolonged period of time.
Workaround: None.
•
The following DWDM SFPs do not work on a GE or 10GE port on ME3600:
–
–
–
–
–
–
–
The same SPF works on a ME3400. When insert one of the DWDM SFPs above into a GE or 10GE port on ME3600 or ME3800, the switch logs the following error messages:
%PHY-4-SFP_NOT_SUPPORTED: The SFP in Gi0/3 is not supported%PM-4-ERR_DISABLE: gbic-invalid error detected on Gi0/3, putting Gi0/3 in err-disable stateConditions: This issue applies to ME3600 and ME3800. The problem is verified in 15.2(4)S1.
Workaround: None.
•
When MAC security is configured on a EFP port, traffic received on this EFP and designated to one mac address learned on the same EFP is bounced back on the EFP.
Conditions: The traffic is not bounced back during one of the following conditions:
–
or
–
or
–
Workaround: None.
•
The Cisco ME3600/ME3800 causes traffic loss or intermittent end-to-end ping drops.
Conditions: This symptom is observed when excess of ICMP redirects in network comprising of Cisco ME3600/ME3800.
Workaround: None.
•
The MAC flaps in the network happen on the reload of the device.
Conditions: The MAC flaps occur because multicast BPDUs are being sent back into the VPLS core after they reach the destination. This behavior causes MAC flaps on every device that is on the path through which the BPDU traverses.
Workaround: Apply split horizon at the bridge-domain where the MAC flaps happen.
•
Cannot configure max mtu when channel-port deleted and re-added.
Conditions: When the port-channel is deleted and created again, the max MTU cannot be set up.
Workaround: Reload the device.
•
CPU errors are seen with (*, G/M) entries on ACL.
Conditions: This symptom is seen on ME3600CX boxes operating in Mode 3 or Mode 4.
Workaround: Operate the ME3600CX boxes in Mode 2.
•
During archive download to upgrade a software version, an old image present in the board does not get deleted or displayed.
Conditions: This symptom occurs during an archive download.
Workaround: None.
•
CFM is working under EVC BD configuration on CE6 and CE7 uplink port. But ip sla is unstable in single link scenario. The network is enhanced to a dual link path connection with ME3600. We need to enable Flex-link feature at CE6 and CE7 (ME3600) for dual link scenario and found that the CFM cannot formed by peer.
Since Flex-link is not supported on EFP interface, uplink port was changed to a switchport setting at CE6 and CE7. The CFM remote maintenance-points were not formed on the CE (ME3600) at the peering end.
Conditions: On IOS 15.2(4)S, with flexlink configured on uplink ports, CFM remote MEPs do not come up.
Workaround: Manual switchover of flexlink ports until platform forwarding vlist is not empty. This causes CC packets to be sent correctly and remote MEPs come up.
•
L3 traffic failure.
Conditions: This issue occurs when configuring 4n+1th EFP in a bridge-domain where n=1,2, an so forth.
Workaround: Clear mac-address table.
•
Packet loss are seen over pseudowire and high CPU.
Conditions: This symptom is observed when IPv6 site-local multicast MAC traffic is sent over SVI EoMPLS. The traffic is looped between the PE of the EoMPLS.
Workaround: None.
•
Ingress classification based on numbered IP ACL does not work correctly.
Conditions: If an ingress QoS policy contains match based on numbered ACL, classification does not work, and the actions do not take effect.
Workaround: Use a named ACL instead of numbered ACL for the match.
•
ME3600 Traffic from routed VPLS not triggering ARP.
Conditions: This symptom is observed in a routed VPLS network that has multiple CE routers connected to the PE router. The issue occurs when a local CE router is connected to the PE router via an EVC and when a ping is sent from a local CE router to the remote CE router.
Workaround: Ping the first interface VLAN of the EVC to resolve the ARP.
•
ACL configured on switchport denies all VRF forwarded traffic in hardware.
Conditions: This issue occurs with VRF forwarded traffic.
Workaround: None.
•
When trying to upload an image by using archive upload-sw, however, the temp dir "ramfs:update" was not created, and the upload failed.
Conditions: None.
Workaround: Use copy flash: tftp: instead.
•
Policy-based routing stops working after the router reloads.
Conditions: This symptom occurs when multiple next-hops configured on the same route map are reachable through the same interface.
Workaround: Remove and reconfigure the route-map.
Related Documentation
These documents provide complete information about the switch and are available from these Cisco.com sites:
ME 3800X switch:
http://www.cisco.com/en/US/products/ps10965/tsd_products_support_series_home.htmlME 3600X and ME 3600X-24CXswitch:
http://www.cisco.com/en/US/products/ps10956/tsd_products_support_series_home.html
Note
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
These compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
•
•
•
•
•
•
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 "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)
© 2011—2013 Cisco Systems, Inc. All rights reserved.
