Software Licenses and Features
Finding the Software Version and Feature Set
Installing Software Images and Licenses
Open Caveats and Resolved Caveats
Open Caveats in Cisco Release 15.4(2)S4
Resolved Caveats in Cisco Release 15.4(2)S4
Open Caveats in Cisco Release 15.4(2)S3
Resolved Caveats in Cisco Release 15.4(2)S3
Open Caveats in Cisco Release 15.4(2)S2
Resolved Caveats in Cisco Release 15.4(2)S2
Open Caveats in Cisco Release 15.4(2)S1
Resolved Caveats in Cisco Release 15.4(2)S1
Open Caveats in Cisco Release 15.4(2)S
Resolved Caveats in Cisco Release 15.4(2)S
Obtaining Documentation and Submitting a Service Request
Last Updated: November 22, 2015
This release note includes important information about Cisco IOS Release 15.4(2)S and later releases that run on the Cisco ME 3800X, ME 3600X and ME 3600X-24CX switches.
This release note also includes limitations, restrictions, and caveats that apply to the release.
You can verify the release notes in the following ways:
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):
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 including the following:
The ME 3800X supports these licenses and 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/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:
Note Only MetroAggrServices is supported during evaluation. Accept the EULA.
Enabling evaluation license on an ME 3600X:
Note Only AdvancedMetroIPAccess is supported during evaluation. Accept the EULA.
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 The evaluation period is valid for 60 days. When the 60 day evaluation period ends, the evaluation license will be unusable after the next reload.
Upon installation of a license file, the license will automatically update to the new license type. There is no need to clear the evaluation license.
Application template
1
|
|||||
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 The flash memory can store a maximum of two IOS images or tar files. If you try to copy or archive upgrade beyond the flash memory capacity, the action aborts.
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.
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.
The Cisco ME 3800X, ME 3600X and ME 3600X-24CX switches are 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:
ht tp://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_book.html
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 Use Table 6 to identify the file that you want to download.
Step 2 Locate the software image file:
a. If you are a registered customer, go to this URL and log in.
http://software.cisco.com/download/navigator.html
b. For ME 3800X, navigate to Switches > Service Provider Switches - Ethernet Aggregation.
For ME 3600X, navigate to Switches > Service Provider Switches - Ethernet Access.
c. Navigate to your switch model.
d. Click IOS Software, then select the latest IOS release.
Note When you select a crypto graphic image, you must also accept the terms and conditions of using crypto graphic images.
Step 3 Download the image to a TFTP server and make sure that the server is properly configured.
For more information, refer to Appendix B in the software configuration guide for this release.
Step 4 Log into the switch through the console port or a Telnet session.
Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command:
For more information about assigning an IP address and default gateway to the switch, refer to the software configuration guide for this release.
Step 6 Download the image file from the TFTP server to the switch by entering this privileged EXEC command:
This example shows how to download an image from a TFTP server at 192.0.2.1 and to overwrite the image on the switch:
You 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 There can be only two image directories in the flash memory.
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 The switch is configured to boot automatically, but you can enter the show boot privileged EXEC command to verify the boot path list and see if a manual boot is necessary.
Step 8 Save the configuration and reload the switch.
After 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 Copy the license file to flash or TFTP.
Step 2 Enter this command to install the license:
Step 3 Enter these commands to boot from the new license:
Step 4 If you have a a scaled license, install the scaled license
Note To revert to a non-scaled license, enter the license clear scaled_license_name privileged EXEC command.
The following sections provide information on new software features:
The following new software features are introduced in the Cisco IOS Release 15.4(2)S:
IEEE 802.1ad Provider Bridge implements standard protocol for double tagging of data and control protocol tunneling.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_2_S/configuration/guide/3800x3600xscg/sw802_one_ad.html
In the ring topology, when a device is inserted into the ring, the neighboring node interfaces require manual reconfiguration. The Auto-IP feature addresses the problem of manually reconfiguring nodes during insertion, deletion, and movement of nodes within the ring. This feature automatically provides IP addresses to the nodes inserted into the ring. Starting with Cisco IOS Release 15.4(2)S, Auto-IP is supported on SVI, Port-Channel, and VRF.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_2_S/configuration/guide/3800x3600xscg/auto_ip.html
Starting with Cisco IOS Release 15.4(2)S, the Cisco ME3600X-24CX-M Switch supports Bidirectional Forwarding Detection (BFD) in IPv4 Asynchronous and Echo mode. The Cisco ME-3600-24CX Series switch supports 511 BFD sessions. BFD Echo Mode is offloaded to hardware, which is only applicable to the ME-3600-24CX Series model.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_1_S/chassis/configuration/guide/3600x_24cxscg/swbfd.html
The Border Gateway Protocol (BGP) Accumulated IGP feature is an optional non-transitive BGP path attribute. The attribute type code for the accumulated interior gateway protocol (AIGP) attribute is assigned by the Internet Assigned Numbers Authority (IANA). The value field of the AIGP attribute is defined as a set of type, length, value (TLV) elements. The AIGP TLV contains the AIGP metric.
For more information, see http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/xe-3s/irg-xe-3s-book/bgp-accumulated-igp.html
The Border Gateway Protocol Prefix-Independent Convergence (BGP PIC) Edge feature improves BGP convergence after a network failure. This convergence is applicable to both core and edge failures, and you can use it in both IP and MPLS networks. This feature creates and stores a backup or an alternate path in the routing information base (RIB), forwarding information base (FIB), and Cisco Express Forwarding (CEF). When a failure is detected, the backup is taken or an alternate path is chosen immediately, thus enabling a fast failover.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_2_S/configuration/guide/3800x3600xscg/swiprout.html
Starting with Cisco IOS Release 15.4(2)S, the hybrid mode is supported with PTP 1588 redundancy. The hybrid mode is supported on the boundary clock and on the slave ordinary clocks.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_2_S/chassis/configuration/guide/3600x_24cxscg/swclocking.html
The ISIS Local Microloop Protection feature enables the link-state routing protocols such as the Intermediate System-to-Intermediate System (ISIS) protocol to prevent or avoid local microloops or uloops during a network convergence after a link-down event.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_2_S/configuration/guide/3800x3600xscg/swiprout.html
Accurate synchronization of the two end-point clocks is achieved through either PTP/IEEE 1588-2002 or Network Time Protocol (NTP). This function is supported across all the Cisco ME3600X and ME3800X series of switches.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_2_S/configuration/guide/3800x3600xscg/swy1731pm.html
Autonomic Networking (AN) makes network devices intelligent by introducing self-management concepts that simplify network management for the network operator. The Autonomic Networking Infrastructure feature simplifies the network bootstrap functionality by removing the need for any kind of pre-staging. This helps the network devices to join a domain securely, after which you can configure the devices.
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/metro/me3600x_3800x/software/release/15-4_2_S/configuration/guide/3800x3600xscg/autonomic_net.html
Note Based on the ITU grid, the channel number can vary.
If the operation fails, a failure message is displayed citing the cause of failure.
If the operation is successful, no message is displayed.
Note The archive download files are extracted to a temporary RAM disk. The RAM disk is deleted after the new files are populated in the flash. The "Deleting Ramdisk" informational message is displayed during this RAM filesystem format operation. If the RAM FS is not formatted successfully, the error message "Filesystem "*" not formatted” is also displayed along with this informational message.
The following sections provide information about open and resolved caveats:
ICMP destination ‘un-reachable’ messages are not generated by switch.
EFP needs to be reconfigured when VPLS is replaced with EoMPLS.
The vlanTrunkPortDynamicState OID is not available when the interface comes up.
The Y.1731 performance monitoring does not collect stats on EVC Tag X to Y transition on MPLS pseudowire.
Multicast traffic does not pass when bridge domain value is 8000.
Transceiver "no monitoring" is not maintained across reload of the switch.
CE-to-CE ping fails when VC Out-Interface is TE Tunnel and access is port channel.
Non-Cisco SFP+ (SFP-10G-ZR) not supported on the Cisco ME3800 switch.
Flex Link backup is administratively down when VLB configuration is removed.
OID displays the system temperature instead of power supply temperature value.
REP does not converge and MALLOC traceback is observed.
MAC flaps happen in VPLS setup when standby AC power supply is configured.
A crash is seen in nl3mmpd_del_mroute. The variables that are passed from nl3mmpd_handle_events point to a block of memory that is a freed chunk.
A port configured for EoMPLS goes into half-dulex even though it is configured as full duplex, after xconnect flaps.
The show ethernet service instance int stats command displays incorrect values.
MAC security on EVC causes high CPU utilization.
EVC configured in a bridge-group do not display local MAC addresses.
OSPF packets are not forwarded.
REP interface may flap frequently and randomly on the Cisco ME-3600-CX.
Removing of service policy on interface with traffic cause device to freeze. CPUHOG messages are seen in the logs which may be followed by a crash due to watchdog timeout.
The VLAN interface state is administratively up even when the physical port state is down.
IPv6 and IPv4 VRF pings fail due to incorrect VRF label programmed in the hardware.
WANPHY flag j1 transmit command availability displays inconsistent behavior with running-config and start config commands.
cbQosQueueingCfgBandwidth returns value of zero.
The system adds the VLAN configuration automatically for each VLAN created on the device.
When a class is configured with bandwidth, it shows the bandwidth percent values from cbQosQueueingCfgBandwidth.
Symptom: Routed Pseudowire (RPW) ping fails from PE to CE, when SplitHorizon Group 2 is configured in access, and if RPW is with Virtual Private LAN Service (VPLS) Virtual Circuit (VC).
Conditions: This issue occurs when the ping fails.
Workaround: Configure SH Group 1.
Symptom: The vlanTrunkPortDynamicState OID is not available when the interface goes up. The switch displays the error “No Such Instance currently exists at this OID”.
Conditions: This issue occurs under normal conditions. It was first discovered in the Cisco IOS 15.3(3)S release.
Workaround: There is no workaround.
Symptom: ICMP destination unreachable message is not generated by the device.
Conditions: This issue occurs when a packet is dropped because there is no route in the routing table
Workaround: There is no workaround.
Symptom: When the interface transceiver monitoring is disabled, the interface transceiver reappears after a reload.
Conditions: This issue occurs when the interface transceiver monitoring is disabled with the following commands:
After a reload, the commands reappear in the configuration.
Workaround: An EEM script can be applied to remove the commands from the configuration at bootup. This EEM script looks for the syslog message indicating the device was reloaded
Symptom: CE-to-CE ping fails when the TE Tunnel is "Up” on core.
Conditions: This issue occurs when the ARP is not resolved.
Workaround: Perform a shut of the tunnel interface.
Symptom: When the flexlink VLAN Load Balancing (VLB) configuration switchport backup interface interface-id prefer vlan vlan-id is removed on the Cisco ME3600X switch, the backup port is administratively down.
Also in this condition, even when active port is administratively down, backup port does not come up.
Conditions: This issue occurs under normal conditions.
Workaround: Run the following commands
Or reconfigure the backup port
Symptom: VLAN interface state and protocol is UP even when the corresponding physical interface is DOWN.
Conditions: This issue occurs under normal conditions.
Workaround: Shut/no shut the physical interface.
Symptom: IPv6 neighbor discovery (ND) fails due to an incorrect VRF label.
Conditions: This issue occurs when SVI VRF is configured on a specific sequence.
The IPv4 and IPv6 VRF pings fail due to an incorrect VRF label programmed in the hardware.
Workaround: unconfig/config the VRF definition or reload the switch.
Symptom: Targeted LDP session between Customer Edge devices flap every 3 minutes. IGP Interface LDP between CE devices run fine.
Conditions: This issue occurs when MPLS LDP packet is carried over L2VPN cloud with Control word OFF.
Workaround: Configure control word ON in L2VPN cloud.
Symptom: The license boot level tag ‘license boot level’ appears in show run command, and this
Conditions: This issue occurs under normal conditions.
Workaround: There is no workaround.
Symptom: A few transceiver related alarms are not reported in the CLI after running the
show facility-alarm status command. SNMP traps are not generated either for the same events.
Conditions: This issue occurs when the Cisco ME 3800X switch is running IOS release 15.3(3)S1.
Workaround: There is no workaround.
Symptom: The ECMP max-path can configure 1 to 16 when using MetroIPAccess.
Conditions: This issue occurs when you boot with MetroIPAccess.
Workaround: Use values 1 to 4.
Symptom: Enabling PBR breaks the EIGRP multicast.
Conditions: This issue occurs when:
1. A Route map is created for any random IP address (not necessarily related to multicast/protocol IP).
2. The PBR is enabled on an interface with EIGRP peering.
Workaround: There is no workaround.
Symptom: The Cisco ME3600-24CX does not display time source information when running PTP.
Conditions: This issue occurs when the ME3600-24CX does not display time source information when running PTP protocol. There is no functional issues noticed with PTP time synchronization. The time source field says Unknown.
Workaround: There is no workaround.
Symptom: The snmpEngineBoots integer does not increment on the Cisco ME 3600X and ME3800X after the device is reloaded. Instead, it is reinitialized.
Conditions: This issue occurs only when the device is rebooted.
Workaround: Perform a warm restart of the device to increment the snmpEngineBoots integer.
Symptom: The v6 multicast traffic is punted to host queue.
Conditions: This issue occurs on a L2 box with no multicast configuration.
Workaround: There is no workaround.
– Peer IP does not ping over layer 3 Port Channel
– Layer 3 (or upper) protocols fail to converge
Conditions: This issue occurs over layer 3 Port Channel
Workaround: Configure Static ARP.
Symptom: The runts and input errors are reported on the interface.
Conditions: This issue occurs on 100FX optics without fiber connected.
Workaround: Connect the fiber.
Symptom: BFD session fails to be administratively up.
Conditions: This issue occurs when BFD is running on Cisco IOS Release 15.4(1)S or earlier.
Workaround: Upgrade to Cisco IOS Release 15.4(2)S or later.
Symptom: Interface description is not retained in the running-config after loading the Cisco IOS Release 15.4(2)S.
Conditions: This issue occurs undernormal conditions.
Workaround: Copy the start-up configuration to the running config immediately after bootup.
Symptom: BFD Sessions flaps with Layer 3 SLA.
The Bidirectional Forwarding Detection (BFD) sessions flap with the Layer 3 Service Level Agreements (L3 SLA).
Conditions: The issue occurs while staring the SLA, which is configured with profile data of the Internet Mix (IMIX) traffic pattern.
Workaround: Use the packet profile combination of 64, 128, and 512 byte packets.
Symptom: The tagged traffic drops.
Conditions: The issue occurs under the following conditions:
– EFP is configured with dot1q/dot1ad VLAN range.
Workaround: Unconfigure and reconfigure the service instance.
Symptom: Configure an IP SLA Service Performance test by using IMIX packet size and without setting CIR or EIR. Observe that the amount of sent and received traffic is below the configured rate. This shows up in a two-way test under the IR and Rx/Tx statistics and in a Traffic Generator test in the Tx statistics.
Conditions: The issue occurs when you configure an IP SLA Service Performance Test which involves traffic generation (Traffic Generator and Two-Way modes) using packet size of IMIX and without having set CIR or EIR. This includes all non-color-aware test cases.
Workaround: Set the cir value equal to the highest configured rate step. Each traffic step meets the configured rate for the current step.
Symptom: The egress traffic on network-to-network interface (NNI) software trunk interface does not contain the expected outer 0x88a8 tag when the ingress interface is configured as S-UNI port with Ethernet Virtual Circuit (EVC).
Conditions: The issue occurs under the following conditions:
– When the ingress C-VLAN value is differed with the configured BD value of UNI-S EVC port.
– When S-UNI port is configured with “encapsulation default” and the S-UNI BD value and NNI trunk VLAN are the same.
– If the S-UNI encap default, BD=100 and NNI trunk VLAN member of 100
Workaround: Perform shut and no shut on the S-UNI interface, the traffic egress on NNI with expected VLAN ID on the dot1ad tag.
Symptom: The LACP protocol flaps between ME3600 switches on EVC service instance configurations.
Conditions: The issue occurs when a valid bridge-domain is not configured along with the service instance configurations.
Workaround: Add a bridge-domain to the service instance configuration
Symptom: The Y1731 Performance Monitoring (PM) does not collect the statistics when the EVC tag X popped on ingress traffic before transiting MPLS PW and pushed EVC tag Y at egress traffic.
Conditions: The issue occurs when you send the CFM untagged packets over a pseuduowire.
Workaround: IP SLA works fine when the cos value matches with the cfm domain level.
Symptom: After removing an xconnect from an EFP, the EFP continues to point to the same vsiid. This results in traffic flow instead traffic drop.
Conditions: The issue occurs when an xconnect configuration is removed from an EFP without removing the service instance.
Workaround: Remove the entire service instance configuration.
Symptom: Unable to access SD flash (2G 16-3932-01 (C-Temp)) plugged in to a Cisco IOS ME 3600X 24CX series router. The message "SD read failed!" is displayed when the device boots up.
Conditions: This issue occurs when a Cisco IOS ME 3600X 24CX series router is booted with SD card (2G 16-3932-01 (C-Temp)) plugged in.
Workaround: Use 2GB 16-3795-01 (I-Temp) SD cards.
Symptom: Serial interface flaps and counters of serial interface fail to increment.
Conditions: The issue occurs under the following conditions:
– When you configure a T3 SAToP on path 1 of the first oc3 port (1/0/0)
– When you configure a serial interface between W2_PE1 and W2_PE2 on OC3 port connected b2b (1/0/1)
– When the input and output of the serial interface counters fail to increment for any serial interface created and first serial interface flaps of each port.
– When the counters fail to increment after you delete and recreate the first serial interface.
– When you reload the box after you recreate the first serial interface, the first serial interface again goes down.
Workaround: Delete and recreate the serial interface.
Symptom: Multicast traffic is software forwarded.
Conditions: The issue occurs when the multicast traffic flows on CPU with RPF interface as L3 port-channel.
Workaround: Move RPF to physical interface.
Symptom: SVI EoMPLS traffic loss after moving from default template to vpnv4-v6 template.
Conditions: The issue occurs when traffic fails at disposition.
Workaround: Change the template to default template.
When a Metro switch ME600 or ME3800 is reloaded with an Ethernet service instance in administratively shutdown state, it might report MAC-flap messages between the administratively down service instance and another port if there is a loop with the service instance active.
This is only mac-flap messages since the efp learns the mac-address, but traffic is not forwarded.
The issues occurs when the mac-flap messages on the shut efp is seen only at bootup. This is seen only if there is already a loop when the service instance is made active.
Workaround: Perform shut and no shut of the service instance.
The.bin file that is extracted from tar does not have the right image name. And, when you upgrade the image from 3.10.0 to 3.10.1 by using the archive download-sw <TAR file> command, the router drops to rommon.
Conditions: The issue occurs when you extract the.bin file from.tar file and/or when you extract the.bin file by using the archive download-sw command.
There is no work around for the wrong image name. Router dropping to rommon during upgrade through the archive download-sw command can be avoided by using archive download-sw /leave-old-sw <TAR file> command.
Symptom: Layer 2 flow hits Layer 3 ACL entry.
Conditions: The issue occurs when the SVI interface is configured with "no ip unreachables".
1. Create a specific permit entry for the direction of ping (ICMP traffic) in the ACL.
2. Remove "no ip unreachables" configuration from the SVI.
Symptom: Egress classification does not work on switchport trunk interface with and without configuring allowed VLANs.
Conditions: The issue occurs when egress QoS is applied on an interface where switchport trunk interface is configured.
Workaround: There is no workaround.
Symptom: MVPN traffic is not received by the receivers when the core replication stops working properly.
Conditions: The issue occurs when a lot of scale is present or when data MDT is used with scale for mVPN.
Workaround: Use the default MDT.
Symptom: STP BPDU loss is observed when you want to tunnel or forward BPDUs across a EVC xconnect.
The issue occurs when you want to tunnel or forward BPDUs across a EVC xconnect. This issue is specific to l2pt forward or tunnel and is not seen with other forms of Xconnect.
Workaround: There is no workaround.
Symptom: ME3600X: CISCO-EVC-MIB is not available with MetroIPAccess license.
Conditions: The issue is observed only with MetroIPAccess license.
Workaround: Upgrade the license to AdvancedMetroIP license.
Symptom: Ping loss is seen for significant duration from non-directly connected VRRP device when the MAC address of the end host changes.
Conditions: The issue occurs when the end host device is changed with another device with the same IP address but different MAC address. Due to this issue, the non-directly connected devices are not able to ping to the host.
Workaround: Perform shut and no shut of the SVI on the non-directly connected devices.
Symptom: When the switch has a large number of active global VLANs active this case 500 and input policy is attached after egress policy on trunk port, console hangs for 15 minutes.
The issue occurs due to the following conditions:
1. Large number of active global VLANs this case 500.
2. Output policy in trunk port.
3. Input policy is configured after output policy attachment.
Workaround: There is no workaround.
Symptom: Targeted LDP session between CE devices may not form when ME3600CX is acting as a PE device with "no mpls ip propogate-ttl forward" configured on CE and PE device.
Conditions: This issue occurs when ME3600CX acts as PE router with "no mpls ip propogate-ttl forward" configured.
Workaround: Remove "no mpls ip propogate-ttl forward" from ME3600CX router.
Conditions: The issue occurs when more than 1k packets are passed to routing protocol queue.
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.html
ME 3600X and ME 3600X-24CX switch:
http://www.cisco.com/en/US/products/ps10956/tsd_products_support_series_home.html
Note Before installing, configuring, or upgrading the switch, see these documents:
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
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.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.