Release Notes for Cisco IOS Release 15.5(3)M on the Cisco 5900 Embedded Services Routers (ESR) platforms.

---

---

5921 Enterprise Based Image

Starting with the 15.5(3)M release, a new Enterprise Based image will be available for the 5921 ESR. The feature set provides core routing functionality but removes the advanced IP Security features (IPSec, VPN), Unified Call Manager, WAAS, and IP Mobility from the 5921 Advanced feature set. It will support three throughputs with Smart Licensing mode including 10, 25, and 50MB.

The image label is c5921i86-entbasek9-tar.SPA.155-3.M.

---

Note The CSL license is not supported in 15.5(3)M enterprise based image. The enterprise based image supports both node-lock-machine and node-lock-storage license schemes.

DLEP Version 7

The 5900 series Embedded Routers support Dynamic Link Exchange Protocol (DLEP) version7 with Cisco IOS Release 15.5(3)M. Understanding and Configuring DLEP information can be found here:

http://www.cisco.com/c/en/us/td/docs/solutions/GGSG-Engineering/15-4-3M/config-guide/Configuration-Guide/DLEP.html

Background information about DLEP can be found here:

http://www.cisco.com/web/strategy/docs/gov/aag_dlep.pdf

End User Interface

The CLI has some differences noted below:

• The default UDP port is 55555 and the default TCP port is 55556
• The default value for version is 0 (DLEP1.0)
• TCP port applies only for DLEPv1.5 or v1.7
• Interface can be configured either for DLEPv1.0, DLEPv1.5, or DLEPv1.7

• This CLI is not applicable for DLEPv1.5 or DLEPv1.7
• The default heartbeat threshold value for DLEPv1.5 and DLEPv1.7 is 2 seconds

Commands common to DLEPv5 and DLEPv7:

[no] ip dlep neighbor-down-ack-timeout <nnnn>

[no] ip dlep peer-terminate-ack-timeout <nnnn>

show dlep client [interface]

show dlep neighbor [interface]

show dlep counters [interface]

show dlep config [interface]

clear dlep client [interface] [<peer ID>]

clear dlep neighbor [interface] [<session ID>]

clear dlep counters [<Interface>]

Cisco Application Visibility and Control (AVC)

The Cisco Application Visibility and Control (AVC) solution is a suite of services in Cisco network devices that provides application-level classification, monitoring, and traffic control, to:

• Improve business-critical application performance
• Support capacity management and planning
• Reduce network operating costs

Detailed information on AVC can be found at the following links:

AVC Home:

http://www.cisco.com/c/en/us/products/routers/avc_control.html

AVC User Guide:

http://www.cisco.com/c/en/us/td/docs/ios/solutions_docs/avc/guide/avc-user-guide.html

The Cisco 5921 ESR has the following limitation:

With the 5921 ESR, several situations have been encountered in which the e1000e Ethernet driver strips VLAN tags before a frame reaches the 5921. This will result in dot1q trunking not performing properly (the 5921 will receive frames with no VLAN tag, even though it is configured to expect VLAN tags). In IOS, you will notice this by seeing ARP or ping failures.
If you see such behavior, please issue the following debug command from IOS:

# debug arp

Now, try the ping again. If the VLAN tag stripping issue is present, you will see a "wrong cable" message similar to the following:

Now switch to the Linux command line and see if the e1000e driver is being used by issuing the following command (using eth0 as an example):

From the Linux command line, verify the VLAN mode of the device:

If the VLAN mode is enabled, this indicates that the driver is stripping the VLAN tags.

To remedy this using CentOS, please upgrade to the latest e1000e driver by following these steps from the Linux command line:

If the process ends with the following message, ignore it:

From the Linux command line, verify that the new driver has been activated:

 

Cisco IOS Release 15.5(3)M

The following sections list caveats for Cisco IOS Release 15.5(3)M:

Closed Caveats

• CSCuu35625

Crash leaded by BADSHARE messages when shaping traffic

1. Apply a shaper on LAN interface that is oversubscribed by traffic coming in on a DMVPN tunnel

2. The following error messages may be seen

3. The device crashes. In some circumstances the device may not crash and an output queue wedge occurs

• CSCuu68111

On the c5940, the " show proc cpu " shows Total CPU less than interrupt CPU.

• CSCut23386

Symptom :

IPv4 and IPV6 Multicast traffic does not pass through VMI interfaces.

Conditions :

This happens only when Multicast traffic has to be forwarded over VMI interfaces.

• CSCut50780

On the C2800 Series Integrated Services Routers, when running DLEP, the router crashes at bma_soutput.

• CSCur99197

EIGRP Internal routes do not get a route-tag appended when using a distribute-list with a route-map. If these are EIGRP External routes they do not have this problem and the route-tag is set as per the route-map.

• CSCur15562

In a c5940 which registers hardware SEC Engine as a valid hardware entropy source, the crypto packets shall be depleted after 256 attempts of entropy collection (roughly 10 days). This could hinder the crypto services that needs the crypto packets.

• CSCut59448

Routes pointing to Null0 do not appear in Routing Table.

• CSCut23407

Incomplete ESP entries cause high CPU load.

Symptom :

When you have incoming traffic on the outside interface, the CPU will go to a very high load (70% +) with little traffic.

Open Caveats

• CSCuv01746

DLEP VRF aware support request

Symptom :

Physical interface configured under a certain VRF, breaks DLEP adjacency with radio device.

Example:

Conditions :

VRF configured under a physical interface which we intend to use for DLEP adjacency.

Workaround :

Do not configure a physical interface intended to be used for DLEP under any VRF.

Further Problem Description :

VMI interface used by DLEP is going down and neighbor getting deleted when physical interfaces is configured under a VRF (not in Global Routing table).

 

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

 

© 2012-2015 Cisco Systems, Inc. All rights reserved.

Printed in the USA on recycled paper containing 10% postconsumer waste.