Release Notes for Cisco IOS Release 15.6(1)M
Image Information and Supported Platforms
Add 5Mbps and 100Mbps to the 5921
Performance Improvements on the 5921
The Cisco 5921 ESR has the following limitation:
Obtaining Documentation and Submitting a Service Request
The following release notes support Cisco IOS Releases 15.6(1)M and higher releases. These releases support the Cisco 5900 Embedded Services Routers (ESR) platforms. These release notes are updated to describe new features, limitations, troubleshooting, recommended configurations, caveats, and how to obtain support and documentation.
Note You must have a Cisco.com account to download the software.
Cisco IOS Release 15.6(1)M includes the following Cisco IOS images:
The following documentation is available:
http://www.cisco.com/c/en/us/td/docs/solutions/GGSG-Engineering/15-4-3M/config-guide/Configuration-Guide.html
http://www.cisco.com/c/dam/en/us/td/docs/solutions/GGSG-Engineering/Cisco_5921/Cisco_5921_ESR_Integration.pdf
http://www.cisco.com/c/en/us/products/ios-nx-os-software/ios-software-releases-listing.html
The following new features are supported with release 15.6(1)M.
There are two new licenses that support additional throughput speeds on the 5921. The c5921 universalk9 and entbasek9 images now support the 5Mbps and the 100Mbps PIDs shown in the following table.
The 50% CPU usage restriction on fast path thread has been removed. The IOS scheduler thread avoids going to sleep when it has a job, and improves the performance of c5921. This was previously tracked as bug #CSCuv60913 in the Closed Caveats section.
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:
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:
Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or closed (resolved).
Minor performance improvement on the CPU utilization on the c5921.
Fast path thread goes to sleep when it utilize more then 50% of CPU.
Physical interface configured under a certain VRF, breaks DLEP adjacency with radio device.
Need to be able to change OSPFv3 metric OC
Router-dynamic cost for OSPFv3 = OC + (S1) + (S2) + (S3) + (S4)
Requests to be able to adjust the OC value
OC is derived from the Maximum Data Rate (MDR). It would be much more meaningful to derive OC from the Current Data Rate and zero the remaining components of the metric calculation for MANET use here.
On the 5921 a memory leak over dlep session occurred when OSPF changed to EIGRP
While connecting with MANET infra server we will get a new virtual-access interface created every time for the same connection. The old virtual-access will still be there until you brought your router down or reboot.
When running DLEPv1.5, OSPF route cost was not being calculated as expected
When modem sends destination up message with the default link metrics value, the Route Cost doesn't change for new MANET neighbor.
On the 5915 series router running 15.2(4)GC2 IOS version, OSPFv3 is leaking memory.
IPv4 and IPV6 Multicast traffic does not pass through VMI interfaces. This happens only when Multicast traffic has to be forwarded over VMI interfaces.
Physical interface configured under a certain VRF, breaks DLEP adjacency with radio device.
On the 5930, accurate accounting of CPU usage was not available.
On the 5930, a crash leaded by BADSHARE messages occurred 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
-Traceback= 58D6348z 4203E28z 4048508z 402CA64z 42409ACz 4019D24z 4019D24z 4240A68z 4225890z 4225890z 422C6F4z
*Feb 9 14:10:59.743: %SYS-2-BADSHARE: Bad refcount in datagram_done, ptr=12494B08, count=0
The c5921 is unable to read the VLAN tags from Linux kernel-2.6.32-504.23.4.el6.i686 and later, with one exception: using latest e1000 driver, 8.0.35-NAPI, with 2.6.36 kernel and dot1q works as expected.
No known workaround after kernel-2.6.32-504.23.4.el6.i686.
kernel-2.6.32-504.16.2.el6.i686 and Linux kernel 2.6.36 is working.
The 5940 needs to be able to limit the number of simultaneous login sessions per user. This applies to management connections via the VTY lines.
CPU Utilization reaches 100% while running DLEPv1.7
May hit the problem when running the combination of DLEPv1.7, R2CP and PPPOE
Packet loss observed during oversubscription of QOS in c5921
More packet loss is observed in all the queue on sending traffic using IXnetwork for QOS configuration
On oversubscribing a particular queue for example Q1
DLEP cost not same on uut & neighbor router, after neighbors are brought up
After the DLEP client session is established, Configure OSPF and bring up the neighbors on uut and neighbor router. Once the VMI state changes to FULL on both sides, check the cost on both routers. The cost is not same on uut and neighbor router. It shows 1 on uut and 251 on peer router.
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 at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.