Table of Contents
Release Notes for the Cisco ME 3800X, ME 3600X and ME 3600X-24CX Switch, Cisco IOS Release 15.2(4)S and Later Releases
- Cisco IOS Release 15.2(4)S
- Cisco IOS Release 15.2(4)S1
- Cisco IOS Release 15.2(4)S2
- Cisco IOS Release 15.2(4)S3
- Cisco IOS Release 15.2(4)S4
- Cisco IOS Release 15.2(4)S6
- If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
- If your switch is on, use the show version privileged EXEC command. See the “Finding the Software Version and Feature Set” section.
- If you are upgrading to a new release or a different image, see the software upgrade filename for the software version. See the “Deciding Which Files to Use” section.
For the complete list of Cisco ME 3800X, ME 3600X and ME 3600X-24CX switch documentation, see the “Related Documentation” section.
- “Hardware Supported” section
- “Software Licenses and Features” section
- “Upgrading the Switch Software” section
- “Installation Notes” section
- “New Software Features” section
- “Important Note” section
- “Open and Resolved Caveats” section
- “Related Documentation” section
- “Obtaining Documentation, Obtaining Support, and Security Guidelines” section
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.
- Metro IP access is the universal image.
- Advanced Metro IP access license.
- 10 Gigabit Ethernet upgrade license—enables 10 Gigabit Ethernet on the SFP+ uplink ports.
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.
- Metro Ethernet services is the universal license.
- Metro IP services license.
- Metro Aggregation services license.
- Scaled license for any of the above licenses.
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.
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.
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.
- “Finding the Software Version and Feature Set” section
- “Deciding Which Files to Use” section
- “Installing Software Images and Licenses” section
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.
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.
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.
Step 1 Use Table 7 to identify the file that you want to download.
- For // location , specify the IP address of the TFTP server.
- For / directory / image-name .tar , specify the directory (optional) and the image to download. Directory and image names are case sensitive.
- The /overwrite option overwrites the software image in flash memory with the downloaded one.
- The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
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.
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.
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
The 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 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:
- 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
- Open Caveats for Cisco Release 15.2(4)S4
- 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
- Resolved Caveats for Cisco Release 15.2(4)S4
- Resolved Caveats for Cisco Release 15.2(4)S6
Conditions: This issue is observed when CE-facing interface is EVC BD with split-horizon group as 0 or 2. For split-horizon group 1, traffic flows fine. The issue with CE-facing as group 0, cannot be fixed because of hardware limitation.
Conditions: This issue occurs when L2 specific functionality is enabled on a L3 box. This is more of an unsupported and undesired configuration as the L3 box is capable of building the MCAST database on its own.
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.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 29A47C0z
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).
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 traceback messages. Memory leaks are also observed.
– The (S,G) is not hardware programmed for an MSDP created entry (the source is on a VRF1 on N1 and the receiver is on a S1-S2 switch). Core replication is happening but VRF replication is not working properly.
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.
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.
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: 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).
On the Loopback interface used for BGP neighbor establishment, deleting the ip pim sparse-mode and adding back ip pim sparse-mode results in traceback messages. Memory leaks are also observed after this.
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 message is thrown with decode pointing to L2 Multicast MET.
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 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.
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.
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: 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).Mar 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 0x2C5ECD0z
Conditions: This issue occurs when there is traffic over the Core VCs (as they are `up') 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.
Conditions: This issue occurs when IGMP snooping has to be enabled, and SVI has to be acting as a MROUTER. When this MROUTER is shut, traffic should still flow, because L2 connectivity is up. But an outage is observed.
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.
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.
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: 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.
When changing a QoS policy for classification, such as altering a class-map or changing an associated ACL, while the policy is attached to an interface, the classification stops working and remarks traffic in a strange way.
On the Cisco ME3600X/3800X switch, RIP packets are not punted to CPU from routing TCAM. This is because the CPU is not attached to the TCAM. This results in all the control plane using Multicast RR entry to go down.
Conditions: This issue occurs when the egress policy class is hit by the traffic stream should have marking along with policer configured while the ingress policy class hit should have ingress marking.
- For initial configuration information, see the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware installation guide.
- For upgrading information, see the “Downloading Software” section in the release notes.
- Cisco ME 3800X and ME 3600X Switch Software Configuration Guide
- Cisco ME 3800X and ME 3600X Switch Command Reference
- Cisco ME 3800X and ME 3600X System Message Guide
- Cisco ME 3800X and ME 3600X Switch Hardware Installation Guide
- Cisco ME 3800X and ME 3600X Switch Getting Started Guide
- Installation Notes for the Cisco ME 3800X and ME 3600X Switch Power-Supply and Fan Modules
- Regulatory Compliance and Safety Information for the Cisco ME 3800X and ME 3600X Switches
- Cisco ME 3600X-24CX Switch Hardware Installation Guide
- Cisco ME 3600X-24CX Switch Getting Started Guide
- Installation Notes for the Cisco ME 3600X-24CX Switch Power-Supply and Fan Modules
- Regulatory Compliance and Safety Information for the Cisco ME 3600X-24CX Switch
- Cisco Small Form-Factor Pluggable Modules Installation Notes
- Cisco 10-Gigabit XFP Transceiver Modules Install Note
- Cisco CWDM GBIC and CWDM SFP Installation Notes
- Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix
- Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix
- Cisco CWDM SFP Transceiver Compatibility Matrix
- Cisco Small Form-Factor Pluggable Modules Compatibility Matrix
- 10-Gigabit Ethernet Transceiver Modules Compatibility Matrix
- Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules
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:
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)