Release Notes for the Cisco ME 3800X, ME 3600X

Release Notes for the Cisco ME 3800X, ME 3600X
Release Notes for the Cisco ME 3800X, ME 3600X
and ME 3600X-24CX Switches,
Cisco IOS Release 15.3(2)S and Later Releases
August 16, 2013
May 24, 2016
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.3(2)S
•
Cisco IOS Release 15.3(2)S1
•
Cisco IOS Release 15.3(2)S2
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:
•
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 on page 9.
•
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 on page 10.
For the complete list of Cisco ME 3800X, ME 3600X and ME 3600X-24CX switch documentation, see
the “Related Documentation” section on page 41.
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/software/navigator.html?a=ahttp://www.cisco.com/cisco/web/download/in
dex.htmli=rpm
Contents
•
“Hardware Support” section on page 2
Cisco Systems, Inc.
www.cisco.com
•
“Software Licenses and Features” section on page 4
•
“Upgrading the Switch Software” section on page 9
•
“Installation Notes” section on page 12
•
“New Software Features” section on page 13
•
“Important Notes” section on page 15
•
“Open Caveats” section on page 15
•
“Resolved Caveats” section on page 24
•
“Related Documentation” section on page 41
•
“Obtaining Documentation, Obtaining Support, and Security Guidelines” section on page 42
Hardware Support
Table 1
Supported Hardware
Device
Description
Cisco ME-3800X-24FS-M
24 Gigabit Ethernet SFP downlink ports and 2 SFP+ (10 Gigabit) uplink ports; supports
removable, hot-swappable AC- and DC-input power supplies and fan modules.
Cisco ME-3600X-24FS-M
24 Gigabit Ethernet SFP downlink ports and 2 SFP+ (10 Gigabit) uplink ports; supports
removable, hot-swappable AC- and DC-input power supplies. and fan modules
Cisco ME-3600X-24TS-M
24 10/100/1000BASE-T copper downlink ports and 2 SFP+ (10 Gigabit) uplink ports;
supports removable, hot-swappable AC- and DC-input power supplies and fan modules.
Cisco ME-3600X-24CX-M
Note
The OC3/STM1 interface is not currently enabled by software.
IO mode 1
16 Gigabit Ethernet SFP downlink ports, 8 SFP/copper downlink ports and 2 XFP (10
Gigabit) uplink ports;16 T1/E1 interfaces; supports removable, hot-swappable AC and DC
input power supply and fan modules.
IO mode 2
8 SFP/copper downlink ports and 4 XFP (10 Gigabit) uplink ports;16 T1/E1 interfaces;
supports removable, hot-swappable AC and DC input power supply and fan modules.
IO mode 3
16 GigabitEthernet SFP downlink ports and 3 XFP (10 Gigabit) uplink ports; 16 T1/E1
interfaces; supports removable, hot-swappable AC and DC input power supply and fan
modules.
2
OL-29319-03
Table 1
Supported Hardware (Continued)
Device
Description
SFP+ modules
SFP-10G-SR, SFP-10G-LR, SFP-10G-ER, SFP-10G-ZR, SFP-10G-LRM,
SFP-H10GB-CUxM, DWDM-SFP10G-61.41, DWDM-SFP10G-60.61,
DWDM-SFP10G-59.79, DWDM-SFP10G-58.98, DWDM-SFP10G-58.17,
DWDM-SFP10G-57.36, DWDM-SFP10G-56.55, DWDM-SFP10G-55.75,
DWDM-SFP10G-54.94, DWDM-SFP10G-54.13, DWDM-SFP10G-53.33,
DWDM-SFP10G-52.52, DWDM-SFP10G-51.72, DWDM-SFP10G-50.92,
DWDM-SFP10G-50.12, DWDM-SFP10G-49.32, DWDM-SFP10G-48.51,
DWDM-SFP10G-47.72, DWDM-SFP10G-46.92, DWDM-SFP10G-46.12,
DWDM-SFP10G-45.32, DWDM-SFP10G-44.53, DWDM-SFP10G-43.73,
DWDM-SFP10G-42.94, DWDM-SFP10G-42.14, DWDM-SFP10G-41.35,
DWDM-SFP10G-40.56, DWDM-SFP10G-39.77, DWDM-SFP10G-38.98,
DWDM-SFP10G-38.19, DWDM-SFP10G-37.40, DWDM-SFP10G-36.61,
DWDM-SFP10G-35.82, DWDM-SFP10G-35.04, DWDM-SFP10G-34.25,
DWDM-SFP10G-33.47, DWDM-SFP10G-32.68, DWDM-SFP10G-31.90,
DWDM-SFP10G-31.12, DWDM-SFP10G-30.33
SFP modules
GLC-FE-100FX, GLC-FE-100EX, GLC-FE-100ZX, GLC-FE-100LX, GLC-FE-100BX-U,
GLC-FE-100BX-D, GLC-LH-SM, GLC-SX-MM, GLC-SX-MMD, GLC-LH-SMD,
GLC-ZX-SM, GLC-EX-SMD, GLC-T, GLC-BX-U (CPN 10-2094-02), GLC-BX-D (CPN
10-2093-02), GLC-BX-U, GLC-BX-D, SFP-GE-L, SFP-GE-S, SFP-GE-T,
CAB-SFP-50CM, CWDM-SFP-1470, CWDM-SFP-1490, CWDM-SFP-1510,
CWDM-SFP-1530, CWDM-SFP-1550, CWDM-SFP-1570, CWDM-SFP-1590,
CWDM-SFP-1610, DWDM-SFP-6061, DWDM-SFP-5979, DWDM-SFP-5898,
DWDM-SFP-5817, DWDM-SFP-5736, DWDM-SFP-5655, DWDM-SFP-5575,
DWDM-SFP-5413, DWDM-SFP-5494, DWDM-SFP-5332, DWDM-SFP-5252,
DWDM-SFP-5172, DWDM-SFP-5092, DWDM-SFP-5012, DWDM-SFP-4931,
DWDM-SFP-4851, DWDM-SFP-4772, DWDM-SFP-4692, DWDM-SFP-4612,
DWDM-SFP-4532, DWDM-SFP-4453, DWDM-SFP-4373, DWDM-SFP-4294,
DWDM-SFP-4214, DWDM-SFP-4134, DWDM-SFP-4056, DWDM-SFP-3977,
DWDM-SFP-3898, DWDM-SFP-3819, DWDM-SFP-3739, DWDM-SFP-3661,
DWDM-SFP-3582, DWDM-SFP-3504, DWDM-SFP-3425, DWDM-SFP-3346,
DWDM-SFP-3268, DWDM-SFP-3190, DWDM-SFP-3112, DWDM-SFP-3033,
DWDM-SFP-6141
OL-29319-03
3
Table 1
Supported Hardware (Continued)
Device
Description
SFP modules supported on the
Cisco ME-3600X-24CX
SFP-GE-L, SFP-GE-S, SFP-GE-Z, GLC-LH-SM, GLC-SX-MM, GLC-SX-MMD,
GLC-LH-SMD, GLC-T, SFP-GE-T, GLC-FE-100FX-RGD, GLC-FE-100LX-RGD,
GLC-LX-SM-RGD, GLC-SX-MM-RGD, GLC-ZX-SM, GLC-ZX-SM-RGD, GLC-BX-U
(CPN 10-2094-02), GLC-BX-D (CPN 10-2093-02), and GLC-EX-SMD, GLC-FE-100FX,
GLC-FE-100EX, GLC-FE-100ZX, GLC-FE-100LX, GLC-FE-100BX-U,
GLC-FE-100BX-D, CWDM-SFP-1470, CWDM-SFP-1490, CWDM-SFP-1510,
CWDM-SFP-1530, CWDM-SFP-1550, CWDM-SFP-1570, CWDM-SFP-1590,
CWDM-SFP-1610, DWDM-SFP-6061, DWDM-SFP-5979, DWDM-SFP-5898,
DWDM-SFP-5817, DWDM-SFP-5736, DWDM-SFP-5655, DWDM-SFP-5575,
DWDM-SFP-5413, DWDM-SFP-5494, DWDM-SFP-5332, DWDM-SFP-5252,
DWDM-SFP-5172, DWDM-SFP-5092, DWDM-SFP-5012, DWDM-SFP-4931,
DWDM-SFP-4851, DWDM-SFP-4772, DWDM-SFP-4692, DWDM-SFP-4612,
DWDM-SFP-4532, DWDM-SFP-4453, DWDM-SFP-4373, DWDM-SFP-4294,
DWDM-SFP-4214, DWDM-SFP-4134, DWDM-SFP-4056, DWDM-SFP-3977,
DWDM-SFP-3898, DWDM-SFP-3819, DWDM-SFP-3739, DWDM-SFP-3661,
DWDM-SFP-3582, DWDM-SFP-3504, DWDM-SFP-3425, DWDM-SFP-3346,
DWDM-SFP-3268, DWDM-SFP-3190, DWDM-SFP-3112, DWDM-SFP-3033,
DWDM-SFP-6141
XFP modules supported on the
Cisco ME-3600X-24CX
XFP-10G-MM-SR, XFP10GLR192SR-RGD, XFP10GER192IR-RGD,
XFP-10GER-192IR+, XFP-10GER-192LR+, XFP-10GER-192LR,
XFP10GZR192LR-RGD, XFP10GLR-192SR-L, XFP10GER-192IR-L,
XFP-10GZR-OC192LR, DWDM-XFP-C
Cables
SFP interconnect cable (50 cm)
1-meter, 3-meter, and 5-meter copper SFP+ cables
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:
•
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.
For differences in feature support for each license, see Table 2 and Table 3 on page 6.
The ME3600X-24CX supports the above licences including the following:
4
•
10G license
•
1588BC license
•
T1/E1 counted license
OL-29319-03
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.
•
Metro Ethernet services is the universal image.
•
Metro IP services license.
•
Metro Aggregation services license.
•
Scaled license for any of the above licenses.
For differences in feature support for each license, see Table 4 and Table 5 on page 8.
To install a software image, see the “Upgrading the Switch Software” section on page 9 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:
Switch# configure terminal
Switch(conf)# license boot level <MetroEthServices|MetroIPServices|MetroAggrServices>
Note
Only MetroAggrServices is supported during evaluation. Accept the EULA.
Switch(conf)# exit
Switch# write memory
Switch# reload
Note: This evaluation license will be validated only after reload.
Enabling evaluation license on an ME 3600X:
Switch# configure terminal
Switch(conf)# license boot level <MetroIPAccess|AdvancedMetroIPAccess>
Note
Only AdvancedMetroIPAccess is supported during evaluation. Accept the EULA.
Switch(conf)# exit
Switch# write memory
Switch# reload
Note: 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
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 automatically updates to the new license type. You do not
need to clear the evaluation license.
OL-29319-03
5
Table 2
ME 3600X Supported Features per License
Metro IP Access (Universal Image)
Advanced Metro IP Access license
•
Basic Layer 2 features (including 802.1Q)
•
All features in the Metro IP Access image
•
Ethernet Virtual Circuits (EVCs)
•
Multiprotocol label switching (MPLS)
•
IPv4 routing—RIP, OSFP, EIGRP, IS-IS, and BGP
•
MPLS traffic engineering and Fast Reroute
•
Bidirectional Forwarding Detection (BFD)
•
MPLS OAM
•
Multicast routing —PIM, DM, SSM, and SSM mapping
•
MPLS VPN
•
Ethernet Operations, Administration, and Maintenance
(OAM)—802.1ag, 802.3ah, and E-LMI
•
Ethernet over MPLS (EoMPLS)
•
Pseudowire redundancy
•
Multiple Spanning Tree Protocol (MSTP), Resilient Ethernet
Protocol (REP), and Flex Links
•
Virtual Private Lan Service (VPLS)
•
Synchronous Ethernet with Ethernet Synchronization
Messaging Channel (ESMC)
•
Multi VRF-CE (VRF-Lite) with service awareness (ARP,
ping, SNMP, syslog, traceroute, FTP and TFTP)
•
Switch Database Management (SDM) templates
•
Quality of Service (QoS)
Table 3
ME 3600X and ME 3600X-24CX License Scaling and Template
Supported feature
Metro IP Access
Advanced Metro IP Access
SDM Templates
Default
IPv4
Default
IPv4
Application
template1
MAC addresses
8K
8k
16 K
16 K
16 K
IPv4 routes
20 K
24K
20 K
24 K
12 K
IPv6 routes
5K
4K
6K
3K
4K
Layer 2 Multicast groups
1K
1K
1K
1K
1K
Layer 3 Multicast groups
1K
1K
1K
1K
1K
Bridge domains
4K
4K
4K
4K
4K
Maximum Pseudowire (EoMPLS or VPLS)
—
—
512
512
512
MPLS VPN
—
—
128
128
128
VRF Lite
128
128
128
128
128
VPLS Instances
0
—
26
26
26
ACL entries
2K
2K
2K
2K
IPv4: 2 K
IPv6: 1 K
Queues
4K
4K
4K
4K
4K
Queues per ASIC
2K
2K
2K
2K
2K
IPv4 QoS classification
4K
4K
4K
4K
1K
Policers
2K
2K
2K
2K
2K
6
OL-29319-03
Table 3
ME 3600X and ME 3600X-24CX License Scaling and Template (Continued)
Supported feature
Metro IP Access
Advanced Metro IP Access
EFP
3990
3990
3990
3990
3990
EFPs per Port
3990
3990
3990
3990
3990
STP Instances
128
128
128
128
128
Etherchannel Groups
26
26
26
26
26
Interfaces per Etherchannel Groups
8
8
8
8
8
HSRP/VRRP
128
128
128
128
128
FRR/TE Headend
—
—
512
512
512
FRR/TE Midpoints
—
—
5K
5K
5K
BFD Sessions @ 50 msec
50
50
50
50
50
Number of SVI for Layer 3
128
128
128
128
128
PBR Entries
—
—
—
—
250
BGP Session
100
100
100
100
100
mVPN-MDT
—
—
—
—
250
1. Application Template is applied to both ME3600x -24TS/FS and ME3600x-24CX to enable mVPN, PRB, IGMP-Snooping, IPv6, and IPv6-ACL.
Table 4
ME 3800X Supported Features per License
Metro Ethernet Services (Universal
Image)
Metro IP Services license
Metro Aggregation Services license
•
Basic Layer 2 features (including
802.1d and 802.1Q)
•
All features in the Metro Ethernet
Services image
•
All features in the Metro IP
Services license
•
EVCs
•
•
MPLS
•
Ethernet OAM—802.1ag,
802.3ah, and E-LMI
IPv4 routing—RIP, OSFP, EIGRP,
IS-IS, and BGP
•
•
BFD
MPLS traffic engineering and Fast
Reroute
•
MST, REP, Flex Links
•
•
MPLS OAM
•
Synchronous Ethernet with
Ethernet Synchronization
Messaging Channel (ESMC)
Multicast routing—PIM, DM, SSM, and
SSM mapping
•
MPLS VPN
•
Multi VRF-CE with service awareness
(ARP, ping, SNMP, syslog, traceroute,
FTP and TFTP)
•
EoMPLS
•
Pseudowire redundancy
•
Virtual Private Network (VPLS)
OL-29319-03
7
Table 5
ME 3800X License Scaling
Metro IP
Services
Scaled
Metro IP
Services
Metro
Aggregati
on
Services Scaled Metro Aggregation Services
Default
Default
Default
Default
Default
VPNv4
VPNv4+
IPV6
Video
Template
64 K
128 K
32 K
64 K
128 K
256 K
256 K
256 K
256 K
IPv4 routes
1K
1K
42 K
80 K
24 K
32 K
80 K
80 K
80 K
Layer 3
Multicast
Groups
0
0
2K
4K
2K
4K
8K
2K
10 K
IPv6 routes
0.5 K
0.5 K
21 K
40 K
12 K
16 K
8K
40 K
8K
Layer 2
Multicast
Groups
2K
4K
2K
2K
2K
4K
4K
2K
10 K
Bridge
domains
4K
4K
2K
2K
4K
8K
4K
8K
4K
ACL entries
4K
8K
4K
8K
4K
16 K
4K
4K
4K
IPv4 QoS
classification
16 K
24 K
16 K
24 K
16 K
24 K
12 K
12 K
12 K
EoMPLS PW 0
(Cisco IOS
Release
15.1(2)EY
and later
0
0
0
4K
8K
8K
8K
1K
MPLS VPN
0
0
0
0
2K
2K
2K
2K
2K
VRF Lite
0
0
2K
2K
2K
2K
2K
2K
2K
VPLS
Instances
0
0
0
0
1K
4K
4K
4K
4K
Queues
16 K
32 K
16 K
32 K
16 K
32 K
32 K
32 K
32 K
Queues per
ASIC
8K
16 K
8K
16 K
8K
16 K
16 K
16 K
16 K
Policers
8K
16 K
8K
16 K
8K
16 K
16 K
16 K
16 K
EFP
3990
15990
3990
3990
3990
15990
3990
3990
3990
Maximum
3990
EFPs per Port
3990
3990
3990
3990
3990
3990
3990
3990
STP
Instances
128
128
128
128
128
128
128
128
128
Maximum
Etherchannel
Groups
26
26
26
26
26
26
26
26
26
Metro
Services
Scaled
Metro
Services
Default
MAC table
addresses
Supported
Feature
8
OL-29319-03
Table 5
ME 3800X License Scaling (Continued)
Metro IP
Services
Scaled
Metro IP
Services
Metro
Aggregati
on
Services Scaled Metro Aggregation Services
Default
Default
Default
Default
Default
VPNv4
VPNv4+
IPV6
Video
Template
Interfaces per 8
Etherchannel
Group
8
8
8
8
8
8
8
8
HSRP/VRRP
256
256
256
256
256
256
256
256
256
FRR/TE
Headend
—
—
—
—
1K
1K
1K
1K
1K
FRR/TE
Midpoints
—
—
—
—
7K
7K
7K
7K
7K
Number of
SVI for
Layer 3
1K
4K
1K
4K
1K
4K
4K
4K
4K
PBR Entries
—
2K
—
2K
—
2K
2K
2K
2K
BGP Session
100
100
100
100
100
100
100
100
100
mVPN-MDT
—
1K
—
1K
1K
1K
1K
1K
1K
Supported
Feature
Metro
Services
Scaled
Metro
Services
Default
Upgrading the Switch Software
•
“Finding the Software Version and Feature Set” section on page 9
•
“Deciding Which Files to Use” section on page 10
•
“Installing Software Images and Licenses” section on page 10
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
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.
OL-29319-03
9
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.
Table 6
Cisco IOS Software Image Files
Filename
Description
me380x-universal-tar.153-2.S.tar
Cisco ME 3800X universal image.
me380x-universal-tar.153-2.S1.tar
me380x-universal-tar.153-2.S2.tar
me380x-universalk9-tar.153-2.S.tar
me380x-universalk9-tar.153-2.S1.tar
Cisco ME 3800X universal cryptographic image. This image has
the Metro Ethernet features plus Kerberos and SSH.
me380x-universalk9-tar.153-2.S2.tar
me360x-universal-tar.153-2.S.tar
Cisco ME 3600X universal images.
me360x-universal-tar.153-2.S1.tar
me360x-universal-tar.153-2.S2.tar
me360x-universalk9-tar.153-2.S.tar
me360x-universalk9-tar.153-2.S1.tar
Cisco ME 3600X universal cryptographic image. This image has
the Metro IP access features plus Kerberos and SSH.
me360x-universalk9-tar.153-2.S2.tar
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:
http://www.cisco.com/en/US/partner/docs/ios-xml/ios/fundamentals/command/Cisco_IOS_Configurati
on_Fundamentals_Command_Reference.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.
10
OL-29319-03
To download software, follow these steps:
Step 1
Use Table 6 on page 10 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://www.cisco.com/cisco/software/navigator.html?a=ahttp://www.cisco.com/cisco/web/downloa
d/index.htmli=rpm
b.
For ME 3800X, navigate to Switches > Service Provider Switches - Ethernet Aggregation.
For ME 3600X, navigate to Switches > Service Provider Switches - Ethernet Access.
Note
Step 3
c.
Navigate to your switch model.
d.
Click IOS Software, then select the latest IOS release.
When you select a crypto image, you must also accept the terms and conditions of using crypto images.
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:
Switch# ping tftp-server-address
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:
Switch# archive download-sw tftp:[[//location]/directory]/image-name.tar
•
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.
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:
Switch# archive download-sw /overwrite tftp://192.0.2.1/image-name.tar
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 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.
OL-29319-03
11
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.
Switch# show boot
BOOT path-list
:
flash:/me380x-universal-mz.153-2.S/me380x-universal-mz.153-2.S.bin
Config file
:
flash:/config.text
Private Config file : flash:/private-config.text
Manual Boot
: no
HELPER path-list
:
Step 8
Save the configuration and reload the switch.
Switch# reload
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 the command to install the license:
Switch# license install flash:LICENSE_FILENAME
or
Switch# license install tftp://location/LICENSE_FILENAME
Step 3
Enter these commands to boot from the new license:
Switch# config t
Switch(config)# license boot level license_name
Step 4
If you have a a scaled license, install the scaled license
Switch# license install flash:SCALED_LICENSE_FILENAME
or
Switch# license install tftp://location/SCALED_LICENSE_FILENAME
Note
Step 5
To revert to a non-scaled license, enter the license clear scaled_license_name privileged EXEC
command.
Reload the switch for new license to take effect.
Switch# reload
Installation Notes
You can assign IP information to your switch by using these methods:
12
•
The CLI-based setup program, as described in the switch hardware installation guide.
•
The DHCP-based autoconfiguration, as described in the switch software configuration guide.
•
Manually assigning an IP address, as described in the switch software configuration guide.
OL-29319-03
New Software Features
The following sections provide information on new software features:
OL-29319-03
•
Cisco IOS Release15.3(2)S, page 14
•
Cisco IOS Release15.3(2)S1, page 15
•
Important Notes, page 15
13
Cisco IOS Release15.3(2)S
The following new software features are introduced in Cisco IOS Release 15.3(2)S.
IPv4 Loop-Free Alternate (LFA) Fast Reroute (FRR)—When a link or a switch fails, distributed routing
algorithms compute new routes that take the failure into account. The time taken for computation is
called routing transition. Until the transition is completed and all switches are converged on a common
view of the network, the connectivity between the source and destination pairs is interrupted. You can
use the IPv4 Loop-Free Alternate (LFA) Fast Reroute (FRR) feature to reduce the routing transition time
to less than 50 milliseconds using a precomputed alternate next hop. For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swiprout.html
RMON—Remote Monitoring (RMON) is a standard monitoring specification that enables various
network monitors and console systems to exchange network monitoring data. RMON provides network
administrators with more freedom in selecting network monitoring probes and consoles with features
that meet their particular networking needs. For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swrmon.html
DOSFS support for Secure Digital Cards—This feature provides DOSFS support for Secure Digital
Cards on the Cisco ME 3600X and ME 3800X platforms. For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swsdflash.html
Support for MPLS labels with PTP traffic (PTPoMPLS)—This feature provides support for time
stamping and processing of MPLS labelled PTP traffic. The following encapsulation types are
supported:
•
VPN
•
BGP IPv4
•
LDP
•
FRR
For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/chassis/
configuration/guide/swclocking.html
QoS Support for Dataplane Loopback—This feature provides support for dataplane loopback for EFP in
the presence of QoS policies. For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swedpl.html
L2VPN Protocol Based CLI—This feature provides L2VPN protocol base CLI support for the following
functional areas: L2TPv3, CESoUDP and mLACP. For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swl2vpn_prot_based.html
VPLS BGP Signaling—This feature enables you to use BGP as the control plane protocol for both
autodiscovery and signaling, in accordance with RFC 4761. For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swmpls.html
14
OL-29319-03
EVC Local Connect—This feature is a Layer 2 point-to-point service that provides the ability to
transparently transmit packets between two service instances which reside on the same device. This
feature is different from traditional Layer 2 bridging. Local connect provides a point-to-point connection
which connects the two service instances (end points). Packets are not forwarded based on MAC
addresses. For more details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swevc.html
Cisco IOS Release15.3(2)S1
The following new software feature is introduced in Cisco IOS Release 15.3(2)S1.
Multi-level Priority Queues (MPQ)—This feature allows you to configure multiple priority queues for
multiple traffic classes by specifying a different priority level for each of the traffic classes in a single
service policy map. For details about this feature, see:
http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/15.3_2_S/configu
ration/guide/swmultilevel_pq.html
Important Notes
•
Use the following commands to adjust the channel on a DMDM-XFP-C tunable SFP, proceed as
follows:
Switch(config)#int te0/1
Switch(config-if)#itu channel 23
Switch(config-if)#end
Note
Based on the ITU grid, the channel number can vary.
Open Caveats
The following sections provide information about open caveats:
•
Open Caveats in Cisco Release 15.3(2)S, page 15
•
Open Caveats in Cisco Release 15.3(2)S1, page 19
•
Open Caveats in Cisco Release 15.3(2)S2, page 23
Open Caveats in Cisco Release 15.3(2)S
•
CSCub11348
Symptom: Broadcast traffic flows over the standby spoke VC and then gets punted.
Conditions: The traffic comes over the core VCs since they are up, and it flows over the standby
spoke VC from the hub to the spoke. In the spoke, that traffic received from the spoke VC gets
punted to the CPU (software forwarded).
Workaround: There is no workaround.
OL-29319-03
15
•
CSCub24496
Symptom: 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 action.
Conditions: Observed in the following scenarios:
– Cisco ME3600X is running Cisco IOS Release XE37.
– Multicast stream can be received on any type of interface (Layer 2 and Layer 3).
Workaround: There is no workaround.
•
CSCud61539
Symptom: IGMP snooping does not work with H-VPLS.
Conditions: When the interworking type for H-VPLS is VLAN, IGMP snooping is not occurring on
H-VPLS.
Workaround: Change the interworking to ethernet.
•
CSCud72912
Symptom: The switch hangs during core dump through TFTP/FTP.
Conditions: Configuring exception dump.
Workaround: Use the SD Flash memory for core dump instead of TFTP/FTP, using the following
command: exception flash all sdflash.
•
CSCue11706
Symptom: Traceback messages appear, related to CPU hogs on reload. Also observed on shut or no
shut of interfaces.
Conditions: Creating a large number of EFPs (1k or more) on a single interface leads to a CPU
overload.
Workaround: There is no workaround.
•
CSCue18541
Symptom: ARP does not pass for tunneled (QinQ) VLANs when DAI is enabled on C-VLAN.
Conditions: IP ARP inspection is enabled on the switch where dot1q tunnel is configured.
Workaround: Disable ARP inspection.
•
CSCue25840
Symptom: The QoS policy gets detached from the interface.
Conditions: Observed with a scaled egress service-policy when the policy is removed from one
interface and there is flapping on the other interface.
Workaround: There is no workaround.
•
CSCue30168
Symptom: Ping failure upon path switchover from EVC to routed pseudowire.
Conditions: When MAC move occurs from EVC to routed pseudowire.
Workaround: Clear the MAC address table.
•
CSCue30311
Symptom: The switch crashes on configuring a VLAN first and reconfiguring the policy-map.
16
OL-29319-03
Conditions: When the QoS policy-map applied on the switchport interface is reconfigured or
modified after the addition of a VLAN globally.
Workaround: Wait to configure the VLAN until the CPU is normal and then modify the policy-map.
•
CSCue38489
Symptom: ICMP replies are being duplicated on the Cisco ME 3600X switch.
Conditions: Create service instances on port channel interfaces on a Cisco ME 3600X switch, in a
topology as follows:
IXIA---7600(Te2/1-2)====(PO1)====(Te0/1-2)ME3600(Gi0/4-5)====(PO2)====(Gi1/0/25-26)
SW3750------IXIA
Workaround: There is no workaround.
•
CSCue47516
Symptom: More than 50 ms convergence is observed.
Conditions: Observed upon reloading or test crashing the peer device.
Workaround: There is no workaround.
•
CSCue52744
Symptom: The VRF dual stack is not working.
Conditions: Observed when there are 15 VRFs with dual stack and 15 VRFs for IPv4 only.
Workaround: Maintain all VRFs with dual stack.
•
CSCue67712
Symptom: Error messages appear after flapping the connected interface on adjacent switches or
when reloading switches.
Conditions: Floods the console for some time and does not affect data traffic.
Workaround: There is no workaround.
•
CSCue67759
Symptom: DMR, SLR, LTM, LTR, LBM and LBR are single tagged when the core facing interface
is a switch port.
Conditions: Observed when the UP MEP and core facing interface are configured as switch port
trunk.
Workaround: There is no workaround.
•
CSCue89385
Symptom: Traffic from routed VPLS does not trigger ARP.
Conditions: Observed under the following conditions:
– A routed VPLS network that has multiple CE routers connected to the PE router
– A local CE router is connected to the PE router through an EVC
– 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.
•
CSCue94397
Symptom: Trust port configuration is invalid on DHCP snooping over EVC. The DHCP discover
request cannot be snooped correctly and is dropped on EVC in a layer 2 flat environment.
OL-29319-03
17
Conditions: When configuring in new interface regarding BD of trust port or when reloading after
saving configuration.
Workaround: There is no workaround.
•
CSCuf01449
Symptom: Traffic is not forwarded from the service instance.
Conditions: Normally observed after a reload, but may be observed with other negative triggers,
such as clear ip mro *, shut no shut of port, and so on.
Workaround: Perform a shut or no shut on the link.
•
CSCuf15906
Symptom: Intermittent REP flaps observed.
Conditions: Fast hellos (denoting the lowest timer that can be enabled on an REP) are enabled on a
scaled node.
Workaround: Remove the fast hellos.
•
CSCuf21331
Symptom: Incorrect programming occurs when MPLS IP is removed globally.
Conditions: The traffic flow is affected as the incorrect FID is programmed for some of the VCs.
Workaround: There is no workaround. But try running the clear xconnect all and clear mpls ldp ne
* commands to see if the issue gets resolved.
•
CSCuf25555
Symptom: Policy-based routing stops working after reloading the switch.
Conditions: Observed when next-hops configured for a different sequence number of a route-map
were reachable through the same physical interface.
Workaround: Remove and reconfigure the route-map.
•
CSCuf30192
Symptom: Multicast traffic stops getting forwarded when a MROUTER (SVI) VLAN is shut. The
incoming interface and outgoing interface are on same VLAN.
Conditions: 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.
Workaround: Enable and disable IGMP snooping.
•
CSCuf43673
Symptom: On the Cisco ME 3600X switch, the system crashes and traceback messages appear.
Conditions: Observed after changing route-map on route-reflecter that establishes the Cisco ME
3600X. The Cisco ME 3600X is route-reflecter-client. The route-map setting that you change on the
route-reflecter is the output route-map for the other route-reflecter-client, not for the Cisco ME
3600X.
Workaround: There is no workaround.
•
CSCuf48322
Symptom: Traffic drops in a VPLS scenario.
Conditions: A port-channel with SVI is in the core. Traffic is not sent out of the Cisco ME 3600X
ME 3800X towards the core.
18
OL-29319-03
Workaround: Have the main interface towards the core.
•
CSCuf61563
Symptom: Static MAC address configuration does not drop traffic from the specific MAC.
Conditions: None.
Workaround: There is no workaround.
•
CSCuf85278
Symptom: Memory leak observed with IP FRR.
Conditions: Continuous flap of BFD triggered IGP/interface or with ECMP paths for IP FRR.
Workaround: Avoid ECMP paths or stabilize the network with higher BFD timers in case of BFD
triggering IGP flaps.
Open Caveats in Cisco Release 15.3(2)S1
•
CSCub24496
Symptom: On the loopback interface used for Border Gateway Protocol (BGP) neighbor
establishment, deleting the ip pim sparse-mode command and adding back the ip pim
sparse-mode command, results in traceback messages. Memory leaks are also observed after this
action.
Conditions: Observed in the following scenarios:
– When the Cisco ME3600X Switch running Cisco IOS-XE Release 3.7.
– When the multicast stream are received on any type of interface (Layer 2 and Layer 3).
Workaround: There is no workaround.
•
CSCud43017
Symptom: On removing the registered loopback interface for master-slave, the PTP session does not
start.
Conditions: This issue occurs when the loopback interface (used in PTP configuration) is deleted
and added back after the PTP is configured.
Workaround: First add the loopback interface and then reconfigure the PTP session.
•
CSCue11706
Symptom: Traceback messages related to CPU hogs are observed upon reload. Traceback messages
are also observed during shut or no shut of interfaces.
Conditions: This issue occurs when a large number of EFPs (1k or more) are created on a single
interface. This leads to a CPU overload.
Workaround: There is no workaround.
•
CSCue18801
Symptom: Elastic Load Balancing (ELB) does not work on a flapping core interface that is
configured as a Tunnel.
Conditions: This issue occurs when the internal/terminal loopback is configured and the traffic on
the remote end of the x-connect is flapped (stopped and started).
Workaround: Stop the loopback session and then start the session again.
•
OL-29319-03
CSCue30168
19
Symptom: A path switchover from Ethernet Virtual Connection (EVC) to routed pseudowire results
in ping failure.
Conditions: This issue occurs when a MAC move occurs from EVC to a routed pseudowire.
Workaround: Clear the MAC address table.
•
CSCue30311
Symptom: The Cisco ME3600X Switch does not respond when a VLAN is configured first and then
policy-map is reconfigured.
Conditions: This issue occurs when QoS policy-map applied on the switchport interface is
reconfigured or modified after adding the VLAN at the global level.
Workaround: Configure the VLAN wait until the CPU is normal, and then modify the policy-map.
•
CSCue67759
Symptom: Delay Measurement Reply (DMR), Session Level Redundancy (SLR), Linktrace
Message (LTM), Linktrace Reply (LTR), Loopback Message (LBM), and Loopback Reply (LBR)
are single tagged when the core-facing interface is a switch port.
Conditions: This issue is observed when the UP MEP and core facing interface are configured as
switch port trunk.
Workaround: There is no workaround.
•
CSCue72574
Symptom: Y1731 DMM/SLM/1DM does not work if core and access interfaces have q-in-q
configuration and rewrite ingress tag operations.
Conditions: This issue occurs when CFM UP MEPs configured at core and access interfaces have
q-in-q configuration and rewrite ingress tag operations.
Workaround: There is no workaround.
•
CSCue80192
Symptom: Error messages are displayed on the console.
Conditions: This issue occurs when the PTP functionality does not work after approximately 50 PTP
configurations and unconfigurations.
Workaround: Reload the device.
•
CSCue94397
Symptom: Trust port configuration is invalid on Dynamic Host Configuration Protocol (DHCP)
snooping over EVC. The DHCP discover request cannot be snooped correctly and the request is
dropped on EVC in a Layer 2 flat environment.
Conditions: This issue occurs when configuring new interface regarding BD of trust port or when
reloading after saving the configuration.
Workaround: There is no workaround.
•
CSCuf56070
Symptom: MAC flaps are observed with Resilient Ethernet Protocol (REP).
Conditions: This issue occurs when there is traffic.
Workaround: There is no workaround.
•
CSCuf73865
Symptom: Packet corruption is observed with Virtual Private LAN Services (VPLS) VC type 4.
20
OL-29319-03
Conditions: This issue occurs when egressing on VPLS VC type 4 from a Cisco ME3600X Switch
or a Cisco ME3800X Switch.
Workaround: There is no workaround.
•
CSCuf85278
Symptom: Memory leak is observed with IP Fast Reroute (FRR).
Conditions: This issue occurs when there is continuous flap of Bidirectional Forwarding Detection
(BFD) triggered IGP/interface or with Equal Cost Multipath (ECMP) paths for IP FRR.
Workaround: Avoid ECMP paths or stabilize the network with higher BFD timers in case of BFD
triggering Interior Gateway Protocol (IGP) flaps.
•
CSCuf85418
Symptom: Netflow and BFD configurations on the same interface (Layer 3 port, portchannel, and
so on) make BFD unresponsive and BFD stays in the "AdminDown" state.
Conditions: This issue occurs if there is an interface (individual Layer 3 port, portchannel)
configured with Netflow and BFD. This issue can occur on the Cisco ME3600X and on Cisco
ME3800X Switches.
Workaround: Disable the ip flow ingress command from the interface configured with BFD.
Netflow is not supported on the Cisco ME3600X and on Cisco ME3800X platforms.
•
CSCuf87407
Symptom: BFD session flaps intermittently on the Cisco ME3800X Switch.
Conditions: This issue occurs when aggressive timers (for example, 50 ms) are configured.
Workaround: Increase the timer value to about 150 ms.
•
CSCug16730
Symptom: Control traffic loops back when ELB is configured.
Conditions: This issue occurs when the ELB configuration matches the control traffic.
Workaround: There is no workaround.
•
CSCug29132
Symptom: Measurements are not done when the active flex link port is down and the standby takes
over as the active port on the Cisco ME3600X or Cisco ME3800X Switch.
Conditions: This issue occurs on the Cisco ME3600X or Cisco ME3800X Switch running Cisco IOS
Release 15.2(4)S1, 15.3(1)S, or 15.3(2)S with:
– UP MEP configured
– Flex link configured on uplink ports
– Y1731 SLM active on flex link
Workaround: There is no workaround.
•
CSCug33146
Symptom: Open Shortest Path First (OSPF)/ Label Distribution Protocol (LDP) packets are not
punted to CPU, despite enabling IP on the VLAN.
Conditions: This issue occurs when the VLAN UP trigger to multicast is missed.
Workaround: Perform a shut or no shut of VLAN.
•
OL-29319-03
CSCug33345
21
Symptom: Address Resolution Protocol (ARP) resolution fails when Dynamic ARP Inspection
(DAI) is enabled.
Conditions: This issue occurs after enabling DAI on another VLAN.
Workaround: Enable DAI on the relevant VLAN.
•
CSCug33828
Symptom: After the reload of Cisco ME3600X Switch, a part of the configuration disappears. As a
result, a portion of the network does not work until those commands are added back to the
configuration.
Conditions: This issue occurs after a reload.
Workaround: There is no workaround.
•
CSCug49343
Symptom: Unable to delete pseudowire interface after its creation.
Conditions: This issue occurs when a pseudowire interface defined with only one value is deleted.
Workaround: Define the pseudowire with two numbers. Note the second number as it is not
displayed in the running configuration.
•
CSCug50156
Symptom: Traceback messages are observed when the interface is removed and added back quickly.
Conditions: This issue occurs when the interface is removed or configuration is replaced such that
a port is removed and added back quickly.
Workaround: There is no workaround.
•
CSCug50399
Symptom: Broadcast traffic sent through span destination port forwards traffic, and other ports of
the Cisco ME3800X Switch receives it.
Conditions: This issue occurs under normal conditions.
Workaround: There is no workaround.
•
CSCug52804
Symptom: Multicast traffic drops as it hits the signal-to-noise Ternary Content Addressable Memory
(TCAM) entries.
Conditions: This issue occurs when signal-to-noise entry matches the source IP address of the
multicast packet.
Workaround: There is no workaround.
•
CSCug57173
Symptom: Traceback messages are displayed when the backup TE FRR interface flaps.
Conditions: This issue occurs where there is:
– a reload of the PEER router
– an interface flap
– a topology change
Workaround: There is no workaround.
•
CSCug58425
Symptom: MAC flaps seen in VPLS hub-spoke model.
22
OL-29319-03
Conditions: This issue occurs when the first VC that comes up is a spoke VC.
Workaround: Reconfigure Layer 2 VFI or flap the VLAN interface.
•
CSCug69579
Symptom: MAC learning takes place for BPDUs.
Conditions: This issue occurs when MAC learning happens for BPDUs.
Workaround: There is no workaround.
•
CSCug73982
Symptom: Static MAC address configured on the same VLAN disappears after reload.
Conditions: This issue occurs when the static MAC address is configured on the same VLAN.
Workaround: There is no workaround.
•
CSCug88920
Symptom: The configuration disappears after a switch reload when the speed is configured with a
value equal to 1000 and duplex is configured as “full”.
Conditions: This issue occurs after a switch reload.
Workaround: Perform a reconfiguration.
•
CSCug89751
Symptom: The egress traffic across a few gigabit ports on the Cisco ME3600-24CX-M Switch stops.
Conditions: This issue occurs when Cisco ME3600-24CX-M Switch is configured in the IO Mode
3, and the Maximum Transmission Unit (MTU) is greater than 2600 bytes.
Workaround: There is no workaround.
•
CSCue29941
Symptom: Classification on qos-group does not work in the egress policy-map.
Conditions: This issue occurs when the ingress policy-map marks both discard class and qos-group.
Workaround: Use either discard class or qos-group in the ingress policy-map.
Open Caveats in Cisco Release 15.3(2)S2
•
CSCuf61563
Symptom: Static MAC address configuration does not drop traffic from the specific MAC.
Conditions: This issue occurs under normal conditions.
Workaround: There is no workaround.
•
CSCug01382
Symptom: Active path does not come-up.
Conditions: This issue occurs with MPLS TP in the core traffic not switching to Active path on
unshutting the Active path.
Workaround: Perform a shut or no shut of the SVI on mid point, and observe if the working LSP
comes-up.
•
CSCug33146
Symptom: OSPF/LDP packets are not punted to the CPU despite having IP enabled on the VLAN.
OL-29319-03
23
Conditions: This issue occurs when VLAN up-trigger to multicast is missed. This is a very rare case.
This happens in an environment where VLAN up and down is common.
Workaround: Perform a shut or no shut on the VLAN.
•
CSCug33345
Symptom: Address Resolution Protocol (ARP) resolution fails when Dynamic ARP Inspection
(DAI) is enabled.
Conditions: This issue occurs after enabling the DAI on another VLAN.
Workaround: Enable DAI on the relevant VLAN.
•
CSCug58425
Symptom: MAC flaps seen in VPLS hub-spoke model.
Conditions: This issue occurs when the first VC that comes up is a spoke VC.
Workaround: Reconfigure Layer 2 VFI or flap the VLAN interface.
•
CSCuh24470
Symptom: Missing packets and jitterbuffer underrun counters are incrementing on a Cisco
ME3600CX node where E1 pseudowire (SATOP) is created between a Cisco ME7600 and the Cisco
ME3600CX over the MPLS cloud.
Conditions: This issue occurs when the trigger for this issue is to add "mpls ldp explicit null" on PE
switches.
Workaround: There is no workaround.
•
CSCuh25375
Symptom: ISIS neighbor ship goes down between the Cisco ME3600X nodes after a reload or a
power cycle.
Conditions: This issue occurs after the router is reloaded or is power cycled.
Workaround: There are two workarounds to fix this issue. One is to execute the clear isis *
command, and the other is to configure "mpls ldp igp sync holddown 60000".
•
CSCuh79802
Symptom: Unable to disable the MAC-learning for VLAN on Cisco ME3600X/ME3800X switches.
Conditions: This issue occurs when a VLAN is not part of the EVC or BD.
Workaround: There is no workaround.
Resolved Caveats
The following section provides information about resolved caveats:
24
•
Resolved Caveats in Cisco Release 15.3(2)S, page 25
•
Resolved Caveats in Cisco Release 15.3(2)S1, page 31
•
Resolved Caveats in Cisco Release 15.3(2)S2, page 37
OL-29319-03
Resolved Caveats in Cisco Release 15.3(2)S
•
CSCty51088
Symptom: On a Cisco ME 3600X or Cisco ME 3800X, when traffic for a group (S2,G) is sent to an
interface that is already acting as the source for another group (S1,G), it does not receive any traffic
since no (S2,G) entry is formed.
Conditions: Observed when the receiver interface is already a source interface for another multicast
stream.
Workaround: There is no workaround.
•
CSCty79284
Symptom: Source connected to dual home node is not forwarded to receivers in the PIM SSM mode.
The issue was due to the PIM joins not reaching the source node.
Conditions: Observed with dual home PIM SSM node with traffic source.
Workaround: Add a static group to forward the traffic to the next hop router.
•
CSCtz17977
Symptom: Unable to ping HSRP VIP address over routed VPLS.
Conditions: Two Cisco ME 3600X switches are connected together through VPLS. When the Cisco
ME 3600X-1 is configured with HSRP under VLAN50, the R1 is able to ping. The R2 and Cisco
ME 3600X-2 are unable to ping the VIP (HSRP) address. The R2 and Cisco ME 3600X-2 are able
to physically ping the IP address of R1 and the Cisco ME 3600X-1. There is an ARP entry for the
VIP address on all routers.
Workaround: There is no workaround.
•
CSCtz58189
Symptom: The Cisco ME 3600X crashes when using the config replace command with certain QoS
parameters configured on the switch.
Conditions: Observed when certain QoS are configured on the switch are replaced with the
configuration that is removing the configurations.
Workaround: There is no workaround.
•
CSCtz58391
Symptom: Ingress QoS TCAMs (Ternary Content Addressable Memory) are not cleared after certain
dynamic changes.
Conditions: Observed 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.
•
CSCtz60398
Symptom: Continuous platform assert failure traceback messages are observed with CFM over
cross connect on the switch.
Conditions: CFM over cross connect with MPLS TE in core. Flap the core facing link.
Workaround: There is no workaround.
•
CSCtz74604
Symptom: With a scaled 6PE and 6VPE configuration, a crash is observed.
OL-29319-03
25
Conditions: Observed on flapping the interfaces, and defaulting the configurations with a scaled 6PE
and 6VPE configuration.
Workaround: There is no workaround.
•
CSCua40973
Symptom: Ping channel CV is not working. This is a new channel ID for MPLS TP. When using this
option, the ping fails.
Conditions: None.
Workaround: There is no workaround.
•
CSCua98421
Symptom: RMEPs from a Cisco ASR 9000 are not learned on a Cisco ME 3800X with CFM running
over cross connect. The Cisco ASR 9000 does learn the RMEPs from the Cisco ME 3800X.
Conditions: Observed when QoS is enabled on the Cisco ME 3800X prior to enabling CFM.
Workaround: Apply the CFM configuration before QoS or reload the switch with both QoS and
CFM enabled in the configuration.
•
CSCua98805
Symptom: Traceback messages are seen at adjmgr_free_met.
Conditions: Observed upon defaulting an attachment interface having an L2PT configuration and
used for VPLS.
Workaround: There is no workaround.
•
CSCub18997
Symptom: The Cisco ME 3800X running Cisco IOS release 15.2(2)S1 may crash under certain
scenarios due to a stack overflow.
Conditions: Observed when QoS is configured.
Workaround: There is no workaround.
•
CSCub34595
Symptom: Enabling Dynamic ARP Resolution (DAI) on a VLAN may cause ARP resolution to fail
for hosts in other VLANs.
Conditions: Observed when enabling DAI on a VLAN.
Workaround: Enable DAI for the failing VLAN with the ip arp inspection vlan x command.
Configure an ARP ACL to permit traffic for valid IP source + MAC source pair with the arp
access-list acl_name command. Configure DAI filter and associate with the ARP ACL with the ip
arp inspection filter acl_name vlan x command. Configure DAI trust on egress port with the ip arp
inspection trust command.
•
CSCub41914
Symptom: Traceback message occurs upon shutting down and bringing up Switch Virtual Interface
(SVI) on core interfaces.
Conditions: ECMP paths, with MPLS over SVI on core.
Workaround: There is no workaround.
•
CSCub60422
Symptom: The Cisco ME 3600X-24CX switch crashes.
Conditions: Observed upon executing the command diagnostic start test all.
26
OL-29319-03
Workaround: There is no workaround.
•
CSCub62897
Symptom: The SVI does not come-up for a long time even though there are active ports in the
VLAN.
Conditions: Observed with flex link with preemption and VLAN load balance configuration.
Workaround: There is no workaround.
•
CSCub71958
Symptom: Cross connect traffic is failing to flow.
Conditions: Observed upon reloading the peer device or upon clearing MPLS LDP neighborship.
Workaround: Reload the switch.
•
CSCub89229
Symptom: The 10 gigabit ethernet port fails to come up.
Conditions: Observed upon soaking the box without any XFP in the concerned 10 gigabit ethernet
ports for more than 12 hours.
Workaround: Reload the switch with the XFP intact.
•
CSCub93654
Symptom: On the Cisco ME 3600X or Cisco ME 3800X, an ACL applied on an SVI affects l2
switched traffic.
Conditions: None.
Workaround: Explicitly add an ACL entry to allow intra-VLAN traffic.
•
CSCuc08306
Symptom: The CoS-inner value is not preserved in the case of POP2.
Conditions: Observed when traffic is flowing from the service instance with POP2 configured to
another service instance with POP2, which has a marking with CoS. The CoS-inner value also gets
affected with the QoS policy-map. Without QoS, the current behavior is POP2 -> POP2. The outer
VLAN CoS value gets copied to both the inner and outer CoS value of the egress VLAN tag.
Workaround: There is no workaround.
•
CSCuc11090
Symptom: When the Cisco ME 3600X or ME 3800X is the encapsulation box in MVPN, if the
packet size if greater than the default MTU, packets will not flow out of the box.
Conditions: Observed when MVPN is configured on the Cisco ME 3600X or ME 3800X switch. The
switch should be a core encapsulation switch and traffic should be going on the tunnel to hit this
situation. Only packets beyond the default MTU will not go out and get dropped.
Workaround: Send packets of a smaller size from the source so that after encapsulating with 24 bytes
of the outer IP of the MDT tunnel, it does not go beyond the size of the egressing interface MTU.
•
CSCuc13364
Symptom: The egress service policy on EFP drops all traffic in egress. The offered rate equals the
drop rate. The interface output rate is zero, and output drop increases.
Conditions: Observed with the Cisco ME 3600X or ME 3800X running Cisco IOS release 15.2(2)S.
Workaround: There is no workaround.
•
OL-29319-03
CSCuc15656
27
Symptom: REP occasionally fails when a peer device that is running REP on the same segment is
reloaded.
Conditions: Observed when a remote device is reloaded. The REP state machines on both devices
can get stuck.
Workaround: Flap the link of the unit which did not go into the REP wait state. This brings up the
REP state machines at both ends.
•
CSCuc44555
Symptom: Multicast traffic is not forwarded to downstream, even when the groups show up in the
group list.
Conditions: Observed only when the traffic comes on RPF fail interface, and the downstream port
is blocked due to STP or a similar protocol.
Workaround: Disable IGMP snooping.
•
CSCuc47879
Symptom: Removing the channel group configuration on a CEM controller causes the device to
hang in a particular scenario.
Conditions: Observed when the following steps are performed:
a. Configure the CEM group (CESoPSN or SAToP) on a controller.
b. Configure the channel group on this controller with same time slots used in (a) for the CEM
group.
c. Remove the channel group configured in step (b).
Workaround: Perform a hard reboot of the device.
•
CSCuc52506
Symptom: 6PE and 6VPE traffic drops on shutting the ECMP link.
Conditions: Observed after configuring the 6PE/6VPE between UPE-2 and UPE-1 with ECMP paths
between both nodes and then shutting the ECMP link.
Workaround: There is no workaround.
•
CSCuc59049
Symptom: Crash information generation is incomplete.
Conditions: Observed when a crash occurs.
Workaround: There is no workaround.
•
CSCuc59105
Symptom: The Cisco ME 3600X or ME 3800X may crash.
Conditions: Observed only when issuing the show platform qos policer cpu x x command through
an SSH session.
Workaround: Execute the command through telnet or through the console.
•
CSCuc59765
Symptom: The Cisco ME 3600X and ME 3800X fail to trigger a watchdog crash in certain scenarios.
Conditions: Observed when soaking over a prolonged period of time.
Workaround: There is no workaround.
•
28
CSCuc64719
OL-29319-03
Symptom: A Cisco ME 3600X HSRP failover is observed in VPLS.
Conditions: Observed when HSRP state changes from active to standby. The MAC address on the
active switch is not flushed.
Workaround: Clear the MAC table on the HSRP active switch.
•
CSCuc76515
Symptom: Cross connect fails to negotiate to the correct VC type upon reload.
Conditions: Observed in vc-type4 sessions.
Workaround: Clear the cross connect peer.
•
CSCuc79161
Symptom: Memory leak observed.
Conditions: Observed after flapping the interface, keeping the setup idle, and executing the
command clear xconnect.
Workaround: There is no workaround.
•
CSCuc90061
Symptom: Attaching the QoS policy on EFP with rewrite action as ingress rewrite push was not
supported previously. Now, policy with only class-default can be attached to these EFPs.
Conditions: Observed only for EFPs with rewrite action configured as ingress rewrite push.
Workaround: There is no workaround.
•
CSCuc93135
Symptom: The PTP processor boot failure may lead to file descriptor leakage.
Conditions: Observed when the PTP processor is enabled.
Workaround: There is no workaround.
•
CSCuc94983
Symptom: The ConPE node crashes.
Conditions: Observed with rigorous flapping of the core.
Workaround: Have a stable core network.
•
CSCuc98469
Symptom: The Cisco ME 3800X hangs and crashes several times after receiving corrupted frames
with CRC errors on the 10GE interface.
Conditions: Occurs due to a bad quality optical link.
Workaround: Fix the link to remove line injected errors.
•
CSCud09627
Symptom: The following error message is seen on the console:
npm_intfman_get_el3idc_vlan_index:interface el3id handle is NULL
Conditions: Observed under the following conditions:
– no mpls traffic-eng tunnels
– mpls traffic-eng tunnels
– clear ip bgp *
or
OL-29319-03
29
– upon doing IM OIR on peer end
Workaround: There is no workaround.
•
CSCud11453
Symptom: The following traceback message appears in the console:
:39:23.127: %IPV6_ROUTING-3-RIB: ipv6_is_addr_ours called for link-local address with
wrong tableid -Process= "NCEF ADJ Refresh bg process", ipl= 0, pid= 84 -Traceback=
6FAF20z 10C1A44z BA391Cz 2AF5C04z 2BFFC6Cz 2C566CCz 2C519B8z
Conditions: Observed when enabling IPv6.
Workaround: There is no workaround. No functional impact.
•
CSCud16693
Symptom: The Cisco ME 3600X and ME 3800X switches crash as soon as you apply a policy-map
referencing table-map.
Conditions: Observed when applying a service policy that has an unsupported combination of police
action with table-map and without table-map.
Workaround: Configure a service policy that does not have the combination of police action with
table-map and without table-map.
•
CSCud17448
Symptom: The CoS-inner value is getting copied to CoS in case of Q-in-Q configuration on EVC
bridge-domain.
Conditions: Observed with EVC bridge-domain with Q-in-Q and no rewrite configuration.
Workaround: There is no workaround.
•
CSCud29000
Symptom: Traffic with the wrong tag is sent upon dynamically modifying the rewrite tag.
Conditions: Observed upon dynamically changing the tag to be pushed. The device sends traffic with
the previously configured tag.
Workaround: Remove the service instance and reconfigure with a new rewrite tag to be pushed.
•
CSCud33887
Symptom: 6VPE packets get punted and policed.
Conditions: Observed when an ESP header is enabled.
Workaround: There is no workaround.
•
CSCud48017
Symptom: The forwarding ASIC is locked up with enqueue back-pressure. No traffic is received or
sent out on this ASIC.
Conditions: Occurs only when the hardware entry is corrupted.
Workaround: There is no workaround.
•
CSCud61469
Symptom: Crash observed while configuring a service instance under port channel 2.
Conditions: Configure a service instance under port channel 2.
Workaround: There is no workaround.
30
OL-29319-03
Resolved Caveats in Cisco Release 15.3(2)S1
•
CSCuc65374
Symptom: Chunk leaks are observed with MPLS IP and IP FRR configuration.
Conditions: This issue occurs when there are some triggers like flapping and clearing MPLS LDP.
Workaround: There is no workaround.
•
CSCuc83137
Symptom: The value of the output packet counter is twice that of the input with Ethernet Virtual
Connection (EVC) local connect.
Conditions: This issue occurs after changing the encapsulation on EVC.
Workaround: There is no workaround.
•
CSCud37614
Symptom: Service policy in EVC cannot be reattached after changing pop to push rewrite
operations.
Conditions: This issue occurs when a service-policy is configured on EVC. This issue also occurs
when rewrite ingress tag is changed, and configured on the service-policy on EVC.
Workaround: Before changing the rewrite ingress tag, remove service-policy on EVC.
•
CSCud53234
Symptom: File copy from SD flash to SD flash stops working properly.
Conditions: This issue occurs when the destination file size is less than the file size of the source
file after coping the first file. This makes SD flash data unusable.
Workaround: Format the directory sdflash:/.
•
CSCud72912
Symptom: The Cisco ME3600X-ME3800X switch stops responding after a core dump through
TFTP/FTP.
Conditions: This issue occurs while configuring the exception dump.
Workaround: Use SD Flash for core dump instead of TFTP/FTP, and run the following command:
exception flash all sdflash: .
•
CSCue07657
Symptom: IP SLA goes unstable in a single link scenario when CFM is working under EVC BD
configuration on CE6 and CE7 uplink port.
Conditions: This issue occurs when flex link is configured on uplink ports, and when CFM remote
MEPs do not come up.
Workaround: Perform a manual switchover of flex link ports until platform forwarding vlist is not
empty. This causes CC packets to be sent correctly, and remote MEPs come up.
•
CSCue18541
Symptom: Address Resolution Protocol (ARP) does not pass for tunneled (QinQ) VLANs when DAI
is enabled on C-VLAN.
Conditions: This issue occurs when the IP ARP inspection is enabled on the
Cisco ME3600X-ME3800X switch where dot1q tunnel is configured.
Workaround: Disable the ARP inspection.
OL-29319-03
31
•
CSCue32065
Symptom: Memory leaks are observed with “nile_add_rep_entry”.
Conditions: This issue occurs when rep admin vlan is configured at the global level.
Workaround: There is no workaround.
•
CSCue33091
Symptom: Pings to Switch Virtual Interface (SVI) are successful when the MAC address table is
cleared, but fails later.
Conditions: This issue occurs while pinging the SVI interface.
Workaround: There is no workaround.
•
CSCue38489
Symptom: Multicast packets (both data and control) are duplicated when they egress out of the port
channel with ten gigabit interface members.
Conditions: This issue occurs when multicast packets have duplicate service instance or EFPs. This
issue happens when:
- The port channel has only ten gigabit interfaces as members.
- Multicast, unlearnt unicast or broadcast packets egress out on the port channel interface.
However, after reloading the switch with the given configurations, the issue persists only when the
admin shut or no shut is performed at least once on the port channel interface.
Workaround: There is no workaround.
•
CSCue49656
Symptom: Continuous flap of T1/E1/OC3 Serial intf.
Conditions: This issue occurs with oversubscribed traffic.
Workaround: There is no workaround.
•
CSCue51982
Symptom: Traceback messages are observed with archive download.
Conditions: This issue occurs when an archived version of the tar image is downloaded.
Workaround: There is no workaround.
•
CSCue52471
Symptom: CFM transparency fails over EFP local connect.
Conditions: This issue occurs when CFM is enabled globally.
Workaround: There is no workaround.
•
CSCue52744
Symptom: The VPN routing/forward (VRF) dual stack is not working.
Conditions: This issue occurs when there are 15 VRFs with dual stack and 15 VRFs for IPv4 only.
Workaround: Maintain all VRFs with dual stack.
•
CSCue58716
Symptom: REP flaps are seen in the switch when there are high subscriber STP Bridge Protocol Data
Unit (BPDU) that are L2PT forwarded from a different interface.
32
OL-29319-03
Conditions: This issue occurs when both REP Link Status Layer (LSL) packets and STP BPDU are
using the same CPU receive queue.
Workaround: There is no workaround.
•
CSCue65592
Symptom: Peer-end interface shows link status as ‘up’.
Conditions: This issue occurs when the interface on the Cisco ME3600X-24CX-M switch is
administratively down and the switch is reloaded.
Workaround: Perform a shut or no shut on the Cisco ME3600X-24CX-M interface.
•
CSCue68487
Symptom: The Cisco ME3600X-24CX-M switch stops responding after a channel and a CEM are
configured.
Conditions: This issue is observed when the following steps are performed:
a. Configure channel group on a controller (tug-2 1 t1 1 ch 0 ti 1-24)
b. Configure CEM group on same controller (tug-2 2 t1 1 cem 1 ti 1-24)
c. Unconfigure CEM group (no tug-2 2 t1 1 cem 1)
d. Configure the same CEM group on the same controller (tug-2 2 t1 1 cem 1 ti 1-24)
e. Unconfigure channel group (no tug-2 1 t1 1 ch 0)
Workaround: There is no workaround.
•
CSCue83505
Symptom: Memory leak is observed with ELB with QoS configuration.
Conditions: This issue occurs when the ME3600X-24CX-M box is loaded with ELB and QoS
configuration.
Workaround: There is no workaround.
•
CSCue85729
Symptom: Error occurs on connection manager when interfaces with local connect are defaulted.
Conditions: This issue occurs when the interface has EFP configured with local connect.
Workaround: There is no workaround.
•
CSCue89385
Symptom: Traffic from routed VPLS does not trigger ARP.
Conditions: This issue is observed under the following conditions:
– A routed VPLS network that has multiple CE routers is connected to a PE router.
– A local CE router is connected to the PE router through an EVC.
– 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.
•
CSCue92754
Symptom: Console messages display status of internal ports.
Conditions: Reload the device.
Workaround: There is no workaround.
•
OL-29319-03
CSCue96478
33
Symptom: Ping drops on controller interface GigabitEthernet0. Receive stall in the ETSEC driver.
Conditions: This issue occurs under normal conditions.
Workaround: Perform a shut or no shut on the GigabitEthernet0 interface.
•
CSCue97277
Symptom: VRF ping does not work after deleting and recreating the VRF.
Conditions: This issue occurs when VRF is deleted and added back multiple times.
Workaround: There is no workaround.
•
CSCuf01449
Symptom: Traffic is not forwarded from the service instance.
Conditions: This issue occurs after a reload, however this issue may also occur with other negative
triggers, such as clear ip mro *, shut no shut of port, and so on.
Workaround: Perform a shut or no shut on the link.
•
CSCuf01706
Symptom: Node crashes when Layer 3 and Layer 2 services are reloaded. This terminates the peer
end nodes.
Conditions: This issue occurs when a reload or flap of MPLS interface is enabled at the peer end.
Workaround: There is no workaround.
•
CSCuf04476
Symptom: Traffic is observed after applying the policy-map under 10G interface on the Cisco ME
3600X Switch.
Conditions: This issue occurs when the interface is configured as Layer 3 with VRF under the 10G
interface, without VRF or Layer 2.
Workaround: Perform a shut or no shut after adding or removing policy map.
•
CSCuf16072
Symptom: The Cisco ME 3600X Switch fails to execute archive upload-sw command while
uploading an image. This failure leads to unsuccessful creation of the temporary directory
ramfs:update.
Conditions: This issue occurs under normal conditions.
Workaround: Use copy flash: tftp: instead of archive upload-sw command.
•
CSCuf25555
Symptom: Policy-based routing stops working after reloading the Cisco ME3600X-ME3800X
switch.
Conditions: This issue is observed when next-hops configured for a different sequence number of a
route-map is reachable through the same physical interface.
Workaround: Remove and reconfigure the route-map.
•
CSCuf30192
Symptom: Multicast traffic is not forwarded when an MROUTER (SVI) VLAN is shut. This
happens when the incoming and outgoing interfaces are on the same VLAN.
Conditions: This issue occurs when IGMP snooping is enabled and SVI is acting as an MROUTER.
Outage occurs when the MROUTER is shut. However, traffic flow should be smooth because the
Layer 2 connectivity is up.
34
OL-29319-03
Workaround: First enable and then disable IGMP snooping.
•
CSCuf30461
Symptom: Traffic is not forwarded from Cisco ME3600X Switch, when routed over the EFP that
has double VLAN tag.
Conditions: This issue occurs when the Cisco IOS image is upgraded to Cisco IOS Release
15.3(1)S1.
Workaround: Upgrade to 15.3(1)S2.
•
CSCuf73923
Symptom: The command to get PHY information without interface option is rejected.
Conditions: This issue occurs when the PHY information CLI command is executed without
interface option.
Workaround: Specify the interface option to get the PHY information.
•
CSCug21366
Symptom: Traffic fails when there is a switchover from Ethernet Flow Point (EFP) to Pseudowire
(PW).
Conditions: This issue occurs due of traffic congestion.
Workaround: There is no workaround.
•
CSCug22139
Symptom: Traceback messages are seen when policy-map is applied on the interface.
Conditions: This issue occurs when the ACL with following range command is used in QoS:
– permit udp any host x.x.x.x range 1024 65535
– permit udp host x.x.x.x range 1024 65535 any
Workaround: Apply ACL with the following modification:
– permit udp any host x.x.x.x range 1024 65534
– permit udp host x.x.x.x range 1024 65534 any
•
CSCug23635
Symptom: Ingress drop counters are not incremented when the show policy-map command is
issued.
Conditions: This issue occurs when ELB is enabled on an EFP port.
Workaround: There is no workaround.
•
CSCug31322
Symptom: The Cisco ME3600X-ME3800X switch does not respond after writing into the crashinfo
file.
Conditions: This issue occurs when additional check is added for extended crash dump.
Workaround: There is no workaround.
•
CSCug32786
Symptom: The following SFP+ do not perform optimally for the Cisco ME3600X Switch, where
fiber spans close to their maximum distances are supported:
– ZR
– DWDM
OL-29319-03
35
– CX1
Conditions: This issue occurs under normal operating deployments.
Workaround: There is no workaround.
•
CSCug34597
Symptom: Ternary Content Addressable Memory (TCAM) cleanup is not operating properly. A
service policy cannot be applied after TCAM has exhausted. This continues even after TCAM
resources are removed.
Conditions: This issue occurs when the TCAM resources are not freed after the configuration are
removed, which causes the TCAM to be exhausted.
Workaround: Reload the switch.
•
CSCug37229
Symptom: Ping does not work from Provider Edge (PE) to PE over RPW, and
PM-4-BAD_VLAN_ID traceback messages are observed.
Conditions: This issue occurs with SVI based Multiprotocol Label Switching (MPLS) link.
Workaround: Configure the core facing interface with default values, and apply the configurations
back.
•
CSCug39331
Symptom: Changes are not updated in the policy-map when QoS policy is changed for
classification. For example, altering class-map or changing associated ACL. This happens when the
policy is attached to an interface.
Conditions: This issue occurs when change is made to match the statement on the class-map or in
the access-list.
Workaround: Remove the policy from the interface and reattach it.
•
CSCug45188
Symptom: Internet Control Message Protocol (ICMP) Layer 4-type is not accepted in QoS ACL
configuration.
Conditions: This issue occurs under normal conditions.
Workaround: There is no workaround.
•
CSCug51414
Symptom: Unable to run Ethernet Loopback (ELB) commands on service instances when the
physical port is down.
Conditions: This issue occurs when the service provider does the loopback testing of EVCs on a port
that is down.
Workaround: There is no workaround.
•
CSCug53728
Symptom: Egress classification on port-channel member link is not working for per-hop behavior
(PHB) based policies on EC member links.
Conditions: This issue occurs when egress classification does not work for PHB policies on EC
member links.
Workaround: Apply non-PHB policies.
•
36
CSCug56651
OL-29319-03
Symptom: Traffic fails when packets flow out of access interface with MPLS tag.
Conditions: This issue occurs when the outgoing packet size is large.
Workaround: There is no workaround.
•
CSCug59338
Symptom: Unable to save license related information in secondary storage device (for example,
flash).
Conditions: This issue occurs under normal conditions.
Workaround: There is no workaround.
•
CSCug60599
Symptom: Access-list counter for denied packets do not work on the Cisco ME3600X Switch.
Conditions: This issue occurs when the ACE specifies a “deny” action with the logging option
enabled.
Workaround: There is no workaround.
Resolved Caveats in Cisco Release 15.3(2)S2
•
CSCue52131
Symptom: Traceback messages are seen when policy-map is applied to EFP in ELB mode.
Conditions: This issue occurs when the facility loopback is configured on the interface, and then,
ingress QoS policy-map with the policer is applied.
Workaround: There is no workaround.
•
CSCue67759
Symptom: Delay Measurement Reply (DMR), Session Level Redundancy (SLR), Linktrace
Message (LTM), Linktrace Reply (LTR), Loopback Message (LBM), and Loopback Reply (LBR)
are single tagged when the core-facing interface is a switch port.
Conditions: This issue is observed when the UP MEP and core facing interface are configured as
switch port trunk.
Workaround: There is no workaround.
•
CSCue92617
Symptom: Traffic leaks are observed when removing the traffic engineering fast reroute command
from the tunnel interface using the command no tunnel mpls traffic-eng fast-reroute.
Conditions: This issue occurs when an MPLS tunnel is configured with the IP FRR.
Workaround: There is no workaround.
•
CSCue94397
Symptom: Trust port configuration is invalid on DHCP snooping over EVC. The DHCP discover
request cannot be snooped correctly and is dropped on the EVC in layer 2 flat environment.
Conditions: This issue occurs when configuring a new interface regarding BD of trust port, or when
reloading after saving the configuration.
Workaround: There is no workaround.
•
OL-29319-03
CSCuf73865
37
Symptom: Packet corruption is observed with Virtual Private LAN Services (VPLS) VC type 4.
Conditions: This issue occurs when egressing on VPLS VC type 4 from a Cisco ME3600X Switch
or a Cisco ME3800X Switch.
Workaround: There is no workaround.
•
CSCug26600
Symptom: Traffic fails when the case is switched from Unicast to Flood.
Conditions: This issue occurs when traffic switches from Unicast over EFP to Flood over EFP and
PW does not happen.
Workaround: There is no workaround.
•
CSCug33828
Symptom: After the reload of Cisco ME3600X Switch, a part of the configuration disappears. As a
result, a portion of the network does not work until those commands are added back to the
configuration.
Conditions: This issue occurs after a reload.
Workaround: There is no workaround.
•
CSCug34124
Symptom: Traceback messages are observed upon removing an EVC due to bad magic number in
chunk header.
Conditions: This issue occurs when ScEoMPLS pseudowire is configured on the EVC on Cisco
ME3600X.
Workaround: There is no workaround.
•
CSCug37434
Symptom: Sector and I/O errors are observed while archive download.
Conditions: This issue occurs during archive download of tar image.
Workaround: Reload the console and archive download again.
•
CSCug49343
Symptom: Unable to delete pseudowire interface after its creation.
Conditions: This issue occurs when a pseudowire interface defined with only one value is deleted.
Workaround: Define the pseudowire with two numbers. Note the second number as it is not
displayed in the running configuration.
•
CSCug50156
Symptom: Traceback messages are observed when the interface is removed and added back quickly.
Conditions: This issue occurs when the interface is removed or the configuration is replaced such
that a port is removed and added back quickly.
Workaround: There is no workaround.
•
CSCug50399
Symptom: Broadcast traffic sent through span destination port forwards traffic, and other ports of
the Cisco ME3800X Switch receives it.
Conditions: This issue occurs under normal conditions.
Workaround: There is no workaround.
38
OL-29319-03
•
CSCug52804
Symptom: Multicast traffic drops as it hits the signal-to-noise Ternary Content Addressable Memory
(TCAM) entries.
Conditions: This issue occurs when signal-to-noise entry matches the source IP address of the
multicast packet.
Workaround: There is no workaround.
•
CSCug73982
Symptom: Static MAC address configured on the same VLAN disappears after reload.
Conditions: This issue occurs when the static MAC address is configured on the same VLAN.
Workaround: There is no workaround.
•
CSCug74906
Symptom: Wrong threshold warning messages are displayed for several SFPs.
Conditions: This issue occurs only for the BX_U and the BX_D SFPs.
Workaround: There is no workaround.
•
CSCug77016
Symptom: Memory leaks are observed on flapping the core facing interface.
Conditions: This issue occurs on flapping the core facing MPLS interface carrying MPLS services
for example, L2VPN.
Workaround: There is no workaround.
•
CSCug86770
Symptom: Traceback messages are seen when the port with EFP cross connect is defaulted.
Conditions: This issue occurs while defaulting ports with EFP cross connect.
Workaround: There is no workaround.
•
CSCug88920
Symptom: The configuration disappears after a switch reload when the speed is configured with a
value equal to 1000 and duplex is configured as “full”.
Conditions: This issue occurs after a switch reload.
Workaround: Perform a reconfiguration.
•
CSCug89751
Symptom: The egress traffic across a few gigabit ports on the Cisco ME3600-24CX-M Switch stops.
Conditions: This issue occurs when Cisco ME3600-24CX-M Switch is configured in the IO Mode
3, and the Maximum Transmission Unit (MTU) is greater than 2600 bytes.
Workaround: There is no workaround.
•
CSCug99066
Symptom: IGMP Snooping is not functional on adding new interface.
Conditions: This issue occurs when IGMP Snooping is enabled, and when TCN is disabled.
Workaround: There is no workaround.
•
OL-29319-03
CSCuh04222
39
Symptom: Serial interfaces (either PPP/HDLC) does not come-up on re-create, on Cisco ME3600X
switch.
Conditions: This issue occurs when a serial interface is re-created with other channel-group number
instead of the previously used channel-group number.
Workaround: Reload the switch.
•
CSCuh09508
Symptom: Traffic is not looped back for EFP with double tag configured for data plane loopback
with cos as the filter criteria for loopback.
Conditions: Traffic to be looped back is having Q-in-Q tags and different outer cos and inner cos
specified. Loopback is configured with cos match criteria.
Workaround: Traffic to be looped back should have both outer and inner cos as same value and this
cos value should be used in the data plane loopback configuration.
•
CSCuh19921
Symptom: Peer router OSPF session is brought-down.
Conditions: This issue occurs when BFD is configured for LFA FRR client. On flap of a link in the
ring, OSPF is brought-down on peer client.
Workaround: Have BFD configured for OSPF client as well.
•
CSCuh23923
Symptom: The crashinfo file is not dumped to the SD flash memory.
Conditions: This issue occurs when a crashinfo file is configured to be dumped into the SD flash
memory.
Workaround: There is no workaround.
•
CSCuh27485
Symptom: Policer command in percentage does not work on the Cisco ME3600X/ME3800X
platforms.
Conditions: This issue occurs when QoS policy is configured on EFP which has ELB enabled
‘police cir percent’ does not work.
Workaround: Configure the policer with absolute value instead of percentage value.
•
CSCuh71576
Symptom: EVC filtering fails, as the wrong traffic egresses EVC.
Conditions: This issue occurs due to the dynamic modification of encapsulation with etype
IPv6/IPv4 configured under service instance.
Workaround: Perform a shut or no shut of BD or SVI interface.
•
CSCuh80249
Symptom: The Cisco ME3600X crashes if VRF configuration is removed from routed PW VLAN
interface.
Conditions: This issue occurs when routed PW VLAN interface is configured with the secondary IP
address.
Workaround: There is no workaround as there is no support for secondary IP address on routed PW
VLAN interface.
•
40
CSCuh82969
OL-29319-03
"Receive Power Threshold(++,+,-,--)" is not displayed by the command show interface transceiver.
Conditions: This issue occurs on the Cisco ME-3800X-24FS-M device running 15.3(2)S1.
Workaround: There is no workaround.
•
CSCui27900
Symptom: CRC errors are observed on sending traffic greater than 1G on 10G WAN links. Packet
drops are also seen.
Conditions: This issue occurs when 10G links are configured on WAN mode, and traffic rate is more
than 1 Gbps.
Workaround: There is no workaround.
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.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:
•
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
These compatibility matrix documents are available from this Cisco.com site:
OL-29319-03
41
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
•
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
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.
42
OL-29319-03
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement