 Feedback
|
Table Of Contents
Release Notes for Cisco MWR 2941 Mobile Wireless Edge Router for Cisco IOS Release 15.1(1)MR4
Determining the Software Version
Upgrading to a New Software Release
Support for Existing Cisco MWR 2941 Software Features
New Hardware Features in Release 15.1(1)MR4
New Software Features in Release 15.1(1)MR4
New Hardware Features in Release 15.1(1)MR3
New Software Features in Release 15.1(1)MR3
New Hardware Features in Release 15.1(1)MR2
New Software Features in Release 15.1(1)MR2
New Hardware Features in Release 15.1(1)MR1
New Software Features in Release 15.1(1)MR1
New Hardware Features in Release 15.1(1)MR
New Software Features in Release 15.1(1)MR
Two-Way Active Measurement Protocol
New Hardware Features in Release 15.0(2)MR
New Software Features in Release 15.0(2)MR
New Hardware Features in Release 15.0(1)MR
New Software Features in Release 15.0(1)MR
Supported Hardware—Cisco MWR 2941-DC Router
Support for the ipSystemStatsTable and ipIfStatsTable Tables
Caveats in Cisco IOS Release 15.1(1)MR4
Caveats in Cisco IOS Release 15.1(1)MR3
Caveats in Cisco IOS Release 15.1(1)MR2
Caveats in Cisco IOS Release 15.1(1)MR1
Caveats in Cisco IOS Release 15.1(1)MR
Caveats in Cisco IOS Release 15.0(2)MR
Caveats in Cisco IOS Release 15.0(1)MR
Release Notes for Cisco MWR 2941 Mobile Wireless Edge Router for Cisco IOS Release 15.1(1)MR4
May 17, 2012
OL-24058-01
These release notes are for the Cisco MWR Mobile Wireless Edge Router for Cisco IOS Release 15.1(1)MR4. These release notes are updated as needed to describe new features, memory requirements, hardware support, software platform deferrals, and changes to the microcode.
For a list of the software caveats that apply to Cisco IOS Release 15.1(1)MR4, see the "Caveats in Cisco IOS Release 15.1(1)MR4" section.
To review all Cisco MWR 2941 release notes, including Release Notes for Cisco MWR 2941 Mobile Wireless Edge Router for Cisco IOS Release 15.1(1)MR4, go to:
http://www.cisco.com/en/US/products/ps9395/prod_release_notes_list.html
To review release notes for the Cisco IOS Software Release 15.1S, go to:
http://www.cisco.com/en/US/products/ps11280/prod_release_notes_list.html
Contents
This document contains the following sections:
Introduction
The Cisco MWR 2941 Mobile Wireless Router is a cell-site access platform specifically designed to aggregate and transport mixed-generation radio access network (RAN) traffic. The router is used at the cell site edge as a part of a 2G, 3G, or 4G radio access network (RAN). The Cisco MWR 2941 includes the following models:
•
Cisco MWR 2941-DC
•
The Cisco MWR 2941 router helps enable a variety of RAN solutions by extending IP connectivity to devices using Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Node Bs using HSPA or LTE, base transceiver stations (BTSs) using Enhanced Data Rates for GSM Evolution (EDGE), Code Division Multiple Access (CDMA), CDMA-2000, EVDO, or WiMAX, and other cell-site equipment. It transparently and efficiently transports cell-site voice, data, and signaling traffic over IP using traditional T1 and E1 circuits, as well as alternative backhaul networks such as Carrier Ethernet and DSL, Ethernet in the First Mile (EFM), and WiMAX. It also supports standards-based Internet Engineering Task Force (IETF) Internet protocols over the RAN transport network, including those standardized at the Third-Generation Partnership Project (3GPP) for IP RAN transport. Custom designed for the cell site, the Cisco MWR 2941 features a small form factor, extended operating temperature, and cell-site DC input voltages.
System Requirements
Table 1 lists the supported system configurations for the Cisco MWR 2941:
Memory Requirements
Table 1 lists the required memory for using this software.
Determining the Software Version
To determine the image and version of Cisco IOS software running on your Cisco MWR 2941 router, log in to the router and enter the show version EXEC command:
Router> show versionCisco IOS Software, 2900 Software (MWR2900-ADVIPRANK9-M), Version 15.1(1)MR4, RELEASE SOFTWARE (fc2)Upgrading to a New Software Release
Release 15.1(1)MR4 does not support the following features that were supported in Release 12.4(20)MR1:
•
•
•
•
For general information about upgrading to a new software release, refer to the Software Installation and Upgrade Procedures at:
http://www.cisco.com/en/US/products/hw/routers/ps259/products_tech_note09186a00801fc986.shtml
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco MWR 2941 router.
Support for Existing Cisco MWR 2941 Software Features
Release 15.1(1)MR4 supports the software features supported in Release 15.0(2)MR. For more information about Release 15.0(2)MR and previous releases, see http://www.cisco.com/en/US/products/ps9395/prod_release_notes_list.html.
New Hardware Features in Release 15.1(1)MR4
There are no new hardware features in Release 15.1(1)MR4.
New Software Features in Release 15.1(1)MR4
There are no new software features in Release 15.1(1)MR4.
New Hardware Features in Release 15.1(1)MR3
There are no new hardware features in Release 15.1(1)MR3.
New Software Features in Release 15.1(1)MR3
Release 15.1(1)MR3 introduces the following new software feature:
•
switch tail-drop accounting winpath/GigabitEthernet
New Hardware Features in Release 15.1(1)MR2
There are no new hardware features in Release 15.1(1)MR2.
New Software Features in Release 15.1(1)MR2
Release 15.1(1)MR2 introduces the following new software feature:
•
switch tail-drop accounting winpath.
New Hardware Features in Release 15.1(1)MR1
There are no new hardware features in Release 15.1(1)MR1.
New Software Features in Release 15.1(1)MR1
Release 15.1(1)MR1 introduces the following new software features:
•
•
switch buffer-limit—Configure global queue buffer limit.
New Hardware Features in Release 15.1(1)MR
This release introduces support for the GLC-EX-SMD SFP. For instructions on how to install this SFP, see
New Software Features in Release 15.1(1)MR
Release 15.1(1)MR introduces the following new software features:
•
Support for IPv6
Release 15.1(1)MR introduces support for IPv6. The following sections summarize the supported IPv6 features in Release 15.1(1)MR:
IPv6 Limitations
The Release 15.1(1)MR implementation of IPv6 has the following limitations:
•
•
•
•
Supported IPv6 Features
The following table summarizes the supported IPv6 features in Release 15.1(1)MR. For information about how to configure these features, see the hyperlinked section or refer to the IPv6 Configuration Guide, Cisco IOS Release 15.1S.
Supported IPv6 Commands
Table 2 summarizes the supported commands in Release 15.1(1)MR. For more information about these commands, refer to the Cisco IOS IPv6 Command Reference.
Sample IPv6 Configurations
The following sections provide sample configurations for IPv6.
•
•
•
This section displays partial configurations intended to demonstrate specific features.
Basic Connectivity
The following example shows how to enable IPv6 on the router.
ipv6 unicast-routingipv6 cefipv6 addressFor more information about configuring basic IPv6 connectivity, refer to Implementing IPv6 Addressing and Basic Connectivity.
Static Route
The following example shows how to configure an IPv6 static route on the Cisco MWR 2941.
Router# configure terminalRouter(config)# ipv6 route 2001:DB8::/64 102::2Router(config)# exitRouter#For more information about how to configure static routes for IPv6, see Implementing Static Routes for IPv6.
BFD
The following examples show how to configure BFD for IPv6.
•
•
•
•
Example: Specifying an IPv6 Static BFDv6 Neighbor
The following example specifies a fully configured IPv6 static BFDv6 neighbor. The interface is Ethernet 0/0 and the neighbor address is 2001::1.
Router(config)# ipv6 route static bfd ethernet 0/0 2001:DB8:1::1Example: Associating an IPv6 Static Route with a BFDv6 Neighbor
In this example, the IPv6 static route 2001:0DB8::/32 is associated with the BFDv6 neighbor 2001:DB8:1::1 over the Ethernet 0/0 interface:
Router(config)# ipv6 route static bfd ethernet 0/0 2001:DB8:1::1Router(config)# ipv6 route 2001:0DB8::/32 ethernet 0/0 2001:DB8:1::1Example: Displaying OSPF Interface Information about BFD
The following display shows that the OSPF interface is enabled for BFD:
Router# show ipv6 ospf interfaceSerial10/0 is up, line protocol is upLink Local Address 2001:DB8:1::1, Interface ID 42Area 1, Process ID 1, Instance ID 0, Router ID 10.0.0.1Network Type POINT_TO_POINT, Cost: 64Transmit Delay is 1 sec, State POINT_TO_POINT, BFD enabledTimer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5Hello due in 00:00:07Index 1/1/1, flood queue length 0Next 0x0(0)/0x0(0)/0x0(0)Last flood scan length is 1, maximum is 1Last flood scan time is 0 msec, maximum is 0 msecNeighbor Count is 1, Adjacent neighbor count is 1Adjacent with neighbor 10.1.0.1Suppress hello for 0 neighbor(s)For more information about how to configure BFD, refer to Implementing Bidirectional Forwarding Detection for IPv6.
Multiprotocol BGP
Example: IPv6 VPN Configuration Using IPv4 Next Hop
The following example illustrates a 6VPE next hop:
interface Loopback0ip address 192.168.2.11 255.255.255.255!router bgp 100neighbor 192.168.2.10 remote-as 100neighbor 192.168.2.10 update-source Loopback0!address-family vpnv6neighbor 192.168.2.10 activateneighbor 192.168.2.10 send-community extendedexit-address-familyBy default, the next hop advertised will be the IPv6 VPN address:
[0:0]::FFFF:192.168.2.10Note that it is a 192-bit address in the format of [RD]::FFFF:IPv4-address.
When the BGP IPv6 VPN peers share a common subnet, the MP_REACH_NLRI attribute contains a link-local address next hop in addition to the global address next hop. This situation typically occurs in an interautonomous-system topology when ASBRs are facing each other. In that case, the link-local next hop is used locally, and the global next hop is readvertised by BGP.
The BGP next hop is the keystone for building the label stack. The inner label is obtained from the BGP NLRI, and the outer label is the label distribution protocol (LDP) label to reach the IPv4 address embedded into the BGP next hop.
For more information about how to configure multiprotocol BGP, refer to Implementing Multiprotocol BGP for IPv6.
DHCP
The following examples show how to configure DHCP for IPv6:
Stateful DHCP—Server
ipv6 dhcp pool dhcp-poolprefix-delegation pool client-prefix-pool1 lifetime 1800 600dns-server 2001:0DB8:3000:3000::42domain-name example.cominterface vlan 102ipv6 address 102::2/64ipv6 dhcp server dhcp-poolipv6 local pool client-prefix-pool1 2001:0DB8:1200::/48 48Stateful DHCP—Client
interface vlan 102ipv6 dhcp client pd prefix-from-providerinterface vlan 101ipv6 address prefix-from-provider 2001:0DB8::5:0:0:0:100/64Stateless DHCP—Server
ipv6 dhcp pool dhcp-pooldns-server 2001:0DB8:3000:3000::42domain-name example.cominterface vlan 102ipv6 address 2001:0DB8:1234:42::1/64ipv6 dhcp server dhcp-poolStateless DHCP—Client
interface vlan 102ipv6 address autoconfigFor more information about how to configure DHCP, refer to Implementing DHCP for IPv6.
IS-IS
The following example shows how to configure IS-IS routing for IPv6 traffic.
interface Vlan306mtu 4470ip address 10.36.1.1 255.255.255.0no ptp enableipv6 address 2001:DB8:1::1/64ipv6 enableipv6 router isis isis-600-1mpls ipbfd interval 150 min_rx 50 multiplier 3!router isis isis-600-1net net 2001:DB8.0000.0000.0003.00bfd all-interfaces!address-family ipv6maximum-paths 3exit-address-family!For more information about how to configure IS-IS for IPv6, refer to Implementing IS-IS for IPv6.
Network Management
aaa new-modelip domain name example.comusername myusername password 0 mypasswordcrypto key generate rsaint vlan 102ipv6 address 2001:DB8::2/64For more information about how to configure network management for IPv6, refer to Implementing IPv6 for Network Management.
IPv6 over MPLS
The following example shows how to configure IPv6 over MPLS.
router bgp 100bgp router-id 192.168.1.1bgp log-neighbor-changesno bgp default route-target filterno bgp default ipv4-unicastneighbor 10.0.4.4 remote-as 100neighbor 10.0.4.4 update-source Loopback0!address-family ipv4neighbor 10.0.4.4 activateno auto-summaryexit-address-family!address-family ipv6redistribute ospf 6network 2001:DB8:0::/64network 2001:DB8:1::/64neighbor 10.0.4.4 activateneighbor 10.0.4.4 send-labelexit-address-family!For more information about how to configure IPv6 over MPLS, refer to Implementing IPv6 over MPLS.
IPv6 VPN over MPLS
The following example shows how to configure an IPv6 VPN over MPLS (6VPE).
vrf definition Brd 52:62address-family ipv4route-target export 52:62route-target import 52:62exit-address-family!address-family ipv6route-target export 52:62route-target import 52:62exit-address-family!vrf definition Crd 53:63!address-family ipv4route-target export 53:63route-target import 53:63exit-address-family!address-family ipv6route-target export 53:63route-target import 53:63exit-address-familyinterface Vlan52vrf forwarding Bipv6 address 2001:DB8:0:1/64ipv6 enable!interface Vlan53vrf forwarding Cipv6 address 2001:DB8:1:1/64ipv6 enable!router bgp 100bgp router-id 1.1.1.1bgp log-neighbor-changesno bgp default route-target filterno bgp default ipv4-unicastneighbor 10.10.4.4 remote-as 100neighbor 10.10.4.4 update-source Loopback0!address-family ipv4neighbor 10.10.4.4 activateno auto-summaryexit-address-family!address-family vpnv6neighbor 10.10.4.4 activateneighbor 10.10.4.4 send-community bothexit-address-family!address-family ipv6 vrf Bredistribute connectedredistribute staticexit-address-family!address-family ipv6 vrf Cneighbor 2001:DB8:100:1:: remote-as 104neighbor 2001:DB8:100:1:: activateexit-address-familyFor more information about how to configure IPv6 VPN over MPLS, see Implementing IPv6 VPN over MPLS.
OSPFv3
The following example shows to to configure OSPF version 3 in order to route IPv6 traffic.
!interface Vlan405ip address 192.168.1.2 255.255.255.0no ptp enableipv6 address 2001:DB8:1::2/64ipv6 ospf 600 area 200mpls ipbfd interval 250 min_rx 100 multiplier 3ipv6 router ospf 600router-id 10.0.5.6bfd all-interfacesevent-log size 5 one-shottimers throttle spf 200 500 5000timers throttle lsa 0 20 5000timers lsa arrival 15timers pacing flood 15!For more information about how to configure OSPF v3, see Implementing OSPF for IPv6.
QoS
The following partial configuration examples show how to use QoS features on a network with IPv4 and IPv6 traffic:
•
•
•
•
Applying Ingress QoS to IPv6 Traffic
The following example classifies IPv6 traffic based on DSCP value and marks the traffic with a CoS and QoS group value.
class-map match-all ipv6_llqmatch protocol ipv6match dscp af43 af41 cs6 cs7class-map match-all ipv6_premiummatch protocol ipv6match dscp af33, af13class-map match-all ipv6_hspsmatch protocol ipv6match dscp af12policy-map input-policyclass ipv6_llqset cos 5set qos-group 5class ipv6_premset qos-group 4set cos 4class ipv6_hspsset cos 3set qos-group 3interface GigabitEthernet0/4switchport access vlan 1000switchport mode accessservice-policy input input-policyApplying Ingress QoS to IPv4 Traffic
The following example classifies IPv4 traffic based on DSCP value and marks the traffic with a CoS and QoS group value.
class-map match-all ipv4_protomatch protocol ipmatch dscp af11 af23 af33 af43policy-map input-policyclass ipv4_protoset cos 5set qos-group 5interface GigabitEthernet0/4switchport access vlan 1000switchport mode accessservice-policy input input-policyApplying Ingress QoS to IPv4 and IPv6 Traffic
The following example classifies both IPv4 and IPv6 traffic based on the DSCP value and marks the traffic with a CoS and QoS group value.
class-map match-any llqmatch dscp efmatch dscp af43match dscp af41match dscp cs7match dscp cs6policy-map input-policyclass llqset cos 5set qos-group 5interface GigabitEthernet0/4switchport access vlan 1000switchport mode accessservice-policy input input-policyApplying Egress QoS to IPv4 and IPv6 Traffic
The following example performs the following QoS functions:
•
•
•
class-map match-all q0match qos-group 0class-map match-all q1match qos-group 1class-map match-all q2match qos-group 2class-map match-all q3match qos-group 3policy-map child_policy_egressclass q3priority percent 60class q2bandwidth remaining percent 50class q1bandwidth remaining percent 45class q0bandwidth remaining percent 4policy-map parent_policy_egressclass class-defaultshape average 380000000service-policy child_policy_egressinterface GigabitEthernet0/5switchport trunk allowed vlan 331switchport mode trunkservice-policy output parent_policy_egressFor more information about how to configure QoS for IPv6, see Implementing QoS for IPv6.
Support for New MIBs
Release15.1(1)MR introduces support for the following MIBs:
•
•
•
•
•
For more information about these MIBs and limitations, see IPv6 MIBs
T1 and E1 Local Switching
Release15.1(1)MR introduces support for T1 and E1 local switching. You can use the following commands to configure T1 and E1 local switching:
•
•
Note
Note
For more information about these commands, see the Cisco MWR 2941 Router Command Reference, Release 15.1(1)MR.
Configuring T1 and E1 Local Switching
Follow these steps to configure T1 and E1 local switching
Configuration Examples
The following examples show how to use T1 and E1 local switching:
•
•
•
TDM Local Switching—E1
controller E1 0/0tdm-group 0 timeslots 1-31controller E1 0/1tdm-group 0 timeslots 1-31connect st E1 0/0 0 E1 0/1 0TDM Local Switching—T1
controller T1 0/0tdm-group 0 timeslots 1-24controller T1 0/1tdm-group 0 timeslots 1-24connect stanley T1 0/0 0 T1 0/1 0Non-Channelized Local Switching
controller E1 0/0tdm-group 0 timeslots 1-31controller E1 0/1tdm-group 0 timeslots 1-31connect st1 E1 0/0 0 E1 0/1 0Channelized Local Switching
controller E1 0/0tdm-group 0 timeslots 1-10tdm-group 1 timeslots 11-20controller E1 0/1tdm-group 0 timeslots 1-10tdm-group 1 timeslots 11-20connect st1 E1 0/0 0 E1 0/1 0connect st2 E1 0/0 1 E1 0/1 1Channelized Local Switching on Multiple Channels
controller E1 0/0tdm-group 0 timeslots 1-10tdm-group 1 timeslots 11-20tdm-group 2 timeslots 21-25tdm-group 3 timeslots 26-31controller E1 0/1tdm-group 0 timeslots 1-10tdm-group 1 timeslots 11-20tdm-group 2 timeslots 21-25tdm-group 3 timeslots 26-31connect st1 E1 0/0 0 E1 0/1 0connect st2 E1 0/0 1 E1 0/1 1connect st3 E1 0/0 2 E1 0/1 2connect st4 E1 0/0 3 E1 0/1 3Channelized Local Switching with Segmented Timeslots
controller E1 0/0tdm-group 0 timeslots 1,3,20-22tdm-group 1 timeslots 24,26,29-30controller E1 0/1tdm-group 0 timeslots 1,3,20-22tdm-group 1 timeslots 24,26,29-30connect st1 E1 0/0 0 E1 0/1 0connect st2 E1 0/0 1 E1 0/1 1Ethernet Loopback
You can use per-port and per-VLAN Ethernet loopback to test connectivity at initial startup, to test throughput, and to test quality of service (QoS) in both directions.
This feature introduces the following new commands for Ethernet loopback:
•
•
•
Note
For more information about these commands, see the Cisco MWR 2941 Router Command Reference, Release 15.1(1)MR.
Configuring Ethernet Loopback
Follow these steps to use Ethernet loopback on the Cisco MWR 2941:
Caution
Caution
Two-Way Active Measurement Protocol
Two-Way Active Measurement Protocol (TWAMP) is an IETF standard that defines a flexible method for measuring round-trip IP performance between any two devices that support the standard. With TWAMP, IP performance of the underlying transport can be measured between network elements that incorporate the TWAMP standards. TWAMP functionality encompasses a Control-Client and Session Sender, and Server and Session-Reflector. Specific parts of this functionality can be co-located or distributed among various network elements. The MWR-2941 implements TWAMP function as Session-reflector and Sever which will be tested based on RFC 5357.
This feature introduces the following new commands:
•
•
•
•
•
Configuring TWAMP
The following sections describe how to configure TWAMP:
•
Configuring the TWAMP Server
The TWAMP server and reflector functionality are configured on the same device.
Note
Follow these steps to configure the TWAMP server:
Note
To disable the IP SLA TWAMP server, enter the no ip sla server twamp global configuration command. This example shows how to configure a switch as an IP SLA TWAMP server:
Router(config)# ip sla server twampRouter(config-twamp-srvr)# port 9000Router(config-twamp-srvr)# timer inactivity 300Configuring the TWAMP Reflector
The TWAMP server and reflector functionality are both configured on the same device.
Beginning in privileged EXEC mode, follow these steps to configure the TWAMP reflector:
To disable the IP SLA TWAMP reflector, enter the no ip sla responder twamp global configuration command. This example shows how to configure a device as an IP SLA TWAMP reflector:
Router(config)# ip sla responder twampRouter(config-twamp-srvr)# timeout 300New Hardware Features in Release 15.0(2)MR
There are no new hardware features in Release 15.0(2)MR.
New Software Features in Release 15.0(2)MR
Release 15.1(1)MRA introduces the following new software features:
•
Router# configure terminalRouter(config)# ptp mode boundaryRouter(config)# ptp priority1 128Router(config)# ptp priority2 128Router(config)# ptp domain 1Router(config)# interface Vlan1Router(config-if)# ip address 192.168.1.2 255.255.255.0Router(config-if)# ptp announce interval 3Router(config-if)# ptp announce timeout 2Router(config-if)# ptp sync interval -4Router(config-if)# ptp delay-req interval -4Router(config-if)# ptp boundary unicast-negotiationRouter(config-if)# ptp clock-source 192.168.1.1Router(config-if)# ptp enableFor more information about how to configure PTP boundary clock, see the Cisco MWR 2941 Mobile Wireless Edge Router Software Configuration Guide, Release 15.0(1)MR and the Cisco MWR 2941 Router Command Reference, Release 15.0(1)MR.
New Hardware Features in Release 15.0(1)MR
There are no new hardware features in Release 15.0(1)MR.
New Software Features in Release 15.0(1)MR
Release 15.0(1)MR introduces the following new software features:
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
–
–
•
The HSBY feature introduces the following commands:
–
–
–
–
–
–
–
•
Note
Release 15.0(1)MR also supports Ethernet Link Management Interface (E-LMI), which enables Customer Edge (CE) devices to receive notifications and status information for remote User Network Interfaces (UNIs) and Ethernet Virtual Connections (EVC).
This feature introduces the following new commands:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
This feature modifies the following commands:
–
–
–
•
Release 15.0(1)MR supports the following spanning tree features:
–
–
–
This feature introduces the following new commands:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
Release 15.0(1)MR introduces support for per-destination load balancing. You can configure per-destination load sharing on Ethernet ports, VLANs, MLPPP bundles, or pseudowires.
This feature introduces support for the following commands:
–
–
–
–
–
•
–
–
This feature introduces support for the following commands:
–
–
–
–
–
–
–
–
–
–
–
•
–
–
•
For more information about how to configure the router, see the Cisco MWR 2941 Mobile Wireless Edge Router Software Configuration Guide, Release 15.0(1)MR
Limitations and Restrictions
Caution
Cisco IOS Release 15.1(1)MR4 for the Cisco MWR 2941 router has the following limitations and restrictions:
•
•
•
•
•
•
•
–
–
–
–
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
–
–
Note
For more information about configuring dMLPPP, see the Cisco MWR 2941-DC Mobile Wireless Edge Router Software Configuration Guide, Release 15.1(1)MR.
•
•
–
–
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Supported Hardware—Cisco MWR 2941-DC Router
The Cisco MWR 2941 supports the following interface cards:
•
•
Note
The Cisco MWR 2941 router supports the following SFP modules:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Other hardware interfaces are not supported.
Caution
For instructions on how to install HWICs and SFPs, see the documentation included with the product. For information about how to configure HWICs and SFPs, see the Cisco MWR 2941 Mobile Wireless Edge Router Software Configuration Guide, Release 15.1(1)MR.
Supported MIBs
The Cisco MWR 2941 router supports the following MIBs:
Note
IPv6 MIBs
Release 15.1(1)MR4 provides support for the IPv6 with the IP-MIB, IP-FORWARD-MIB, CISCO-IETF-BFD-MIB, CISCO-CONFIG-MAN-MIB, and CISCO-FLASH-MIB. The following limitations apply to these MIBs:
•
–
–
–
–
Note
•
–
–
Support for the ipSystemStatsTable and ipIfStatsTable Tables
Table 3 summarizes the limitations for the ipSystemStatsTable and ipIfStatsTable tables; it indicates which objects within the table are supported and whether the counters for the object include forwarded packets, host-terminated packets, or both.
Caveats
This section documents the open and resolved caveats for the Cisco MWR 2941 router running Cisco IOS Release 15.0(1)MR and later.
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats, severity 2 caveats are less serious, and severity 3 caveats are the least serious of these three severity levels. Only select severity 3 caveats are listed.
For information on caveats in Cisco IOS Software Releases 15.0S, go to:
http://www.cisco.com/en/US/products/ps10890/prod_release_notes_list.html.
Note
The following sections document the opened and resolved caveats by Cisco IOS release:
•
•
•
•
•
•
•
Caveats in Cisco IOS Release 15.1(1)MR4
The following sections describe the caveats in Release 15.1(1)MR4.
Open Caveats
•
Symptom: Removal of class dynamically in policy-map causes MWR 2941 to crash.
Conditions: Occurs when deleting the priority class before deleting a user-defined class which is currently serviced on a multilink interface.
Workaround: Detach the policy from multilink interface and reattach the policy after the policy is modified.
•
Symptom: MWR SFP ports need shut/no shut after multiple reloads to send traffic.
Conditions: Occurs when continuous reload of MWR(20-50 times) over script.
Workaround: Shut/no shut the interface.
Closed Caveats
•
Symptom: TWAMP PI18 session table is not cleared after session is completed.
Conditions: Always occurs.
Workaround: Remove connection entries with CLI command no ip sla server twamp.
•
Symptom: The router running TWAMP crashes with memory corruption.
Conditions: Occurs when TWAMP is configured.
Workaround: None.
•
Symptom: MWR-2941 router running 12.2(33)MR software is not able to pass traffic on a GE interface which has been UP/UP but not previously used.
Conditions: Occurs on the SFP ports only.
Workaround: None.
•
Symptom: After upgrade to mwr2941-adviprank9-mz.151-1.MR3, the device runs out of memory.
Conditions: Occurs when MWR2941 is upgraded from mwr2941-adviprank9-mz.151-1.MR2 to mwr2941-adviprank9-mz.151-1.MR3.
Workaround: Fall back to mwr2941-adviprank9-mz.151-1.MR2.
•
Symptom: Slips on controller T1 increase when loopback diag is configured on the controller interface.
Conditions: Occurs when loopback diag is configured on the controller interface.
Workaround: When loopback diag is configured, clock source should be internal. If line is already set, then change the clock to internal for loopback diag to avoid T1 slip increment.
For more information, see http://www.cisco.com/en/US/docs/ios/11_1/feature/guide/pamce1t1.html#wp997882.
•
Symptom: Host buffers are exhausted due to configuration of default interface and deleting the system created interface.
Conditions: Occurs when removing existing links from Multilink and adding new links to another Multilink interface.
Workaround: Use the command no channel-group on the T1 controller to completely delete automatically created interfaces.
•
Symptom: Policy-map drop counters are not working consistently.
Conditions: Occurs when policy-map is applied on the MLPPP link.
Workaround: None.
•
Symptom: MWR2941 STATS does not increase on SFP interfaces. And the MAC CTRL0 value is showing wrong register output.
Conditions: Occurs when continuous reload with MRB6 image.
Workaround: Reload the MWR to solve the issue.
•
Symptom: LBR is not bearing the cos value as LBM.
Conditions: None.
Workaround: None.
Caveats in Cisco IOS Release 15.1(1)MR3
The following sections describe the caveats in Release 15.1(1)MR3.
Open Caveats
There are no open caveats in Release 15.1(1)MR3.
Closed Caveats
•
Symptom: When using the verify command to verify the integrity of the 12.2(33)MRX image, the command fails because it can't find the embedded hash signature.
Conditions: Occurs when MWR2941 is running 12.2(33)MRX k9 or non-k9 image.
Workaround: None.
•
Symptom: clear/reset counter anomaly on T1 for Cricket.
Conditions: When the interfaces 0/5 and 0/8 of T1 were disconnected, the interfaces S0/5:0 and S0/8:0 are down. When the counters were cleared, there were a huge number of input errors on both interfaces.
Workaround: None.
•
Symptom: Port Info is not correct for MAC addresses learned from EoMPLS.
Conditions: Occurs when the MAC addresses are learned from EoMPLS.
Workaround: None.
•
Symptom: Packet loss with 2941-2941 back to back under ATMoMPLSoGRE scenario.
Conditions: Occurs when two MWRs are back to back and under ATMoMPLSoGRE scenario.
Workaround: None.
•
Symptom: HSRP/GLBP configured on MWR is broken when used on a HWIC module, because the virtual mac address is not being learned by the HWIC.
Conditions: Occurs on MWR running 15.0(1)MR.
Workaround: Configure HSRP with the standby use-bia command, or configure learning for the relevant vlan using the mac-address-table learning vlan command.
•
A vulnerability in the Multicast Source Discovery Protocol (MSDP) implementation of Cisco IOS Software and Cisco IOS XE Software could allow a remote, unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition.
Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available. This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-msdp
•
The Secure Shell (SSH) server implementation in Cisco IOS Software and Cisco IOS XE Software contains a denial of service (DoS) vulnerability in the SSH version 2 (SSHv2) feature. An unauthenticated, remote attacker could exploit this vulnerability by attempting a reverse SSH login with a crafted username. Successful exploitation of this vulnerability could allow an attacker to create a DoS condition by causing the device to reload. Repeated exploits could create a sustained DoS condition.
The SSH server in Cisco IOS Software and Cisco IOS XE Software is an optional service, but its use is highly recommended as a security best practice for the management of Cisco IOS devices. Devices that are not configured to accept SSHv2 connections are not affected by this vulnerability.
Cisco has released free software updates that address this vulnerability. This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-ssh
•
Symptom: System crashed after checking ARP entry details.
Conditions: Occurs after checking ARP entry details.
Workaround: None.
•
A vulnerability exists in the Cisco IOS Software that may allow a remote application or device to exceed its authorization level when authentication, authorization, and accounting (AAA) authorization is used. This vulnerability requires that the HTTP or HTTPS server is enabled on the Cisco IOS device.
Products that are not running Cisco IOS Software are not vulnerable.
Cisco has released free software updates that address these vulnerabilities.
The HTTP server may be disabled as a workaround for the vulnerability described in this advisory.
This advisory is available at the following link:
http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-pai
•
Symptom: System crashed when gps/external port was set as input source.
Conditions: Occurs when gps/external port was set as input source.
Workaround: None.
•
Symptom: MWR crashed when executing the debug rep packet command.
Conditions: Occurs when using the debug rep packet command
Workaround: None.
•
Symptom: MWR 2941 does not pass vlan 4093 traffic.
Conditions: Occurs when the vlan being used is 4093.
Workaround: Use a different vlan ID.
•
Symptom: When a service-policy is applied to a multilink interface, all the QOS drops will not be show in the output of the show policy-map int multilink command.
Conditions: Occurs when service-policy is applied to an MLPP interface.
Workaround: Check the output of the show int summary | in Multilink command, in which the OQD (output queue drop) counter will reflect the QOS drops, or use the platform show command show platform hardware winpath qos Multilink statistics.
•
Symptom: When MWR 2941 is connected on the optical interfaceGi0/0 or 0/1, link is up on only one side after a fiber dropping or maintenance, or even just removing the fiber jumper on one end. When the jumper is reinserted or the fiber connection is recovered, the MWR Gi interface keeps down unless the shut/no shut operations make it recover.
Conditions: Occurs when MWR 2941 is using Gi0/0 or Gi0/1 fiber link, and either end of the fiber dropped.
Workaround: None.
•
Symptom: Intermittent ping drops when it goes through MWR2941.
Conditions: Occurs when MWR2941 is running 15.1(1)MR.
Workaround: Downgrade MWR2941 to 12.2(33)MRB.
•
Symptom: A router running TWAMP may experience a crash due to memory corruption. This may involve a bad block pointer.
Conditions: Occurs when TWAMP is configured.
Workaround: None.
•
Symptom: Remote L3 MPLS VPN PE routers are not able to reach locally connected networks in a given VRF on MWR router. Aggregate MPSL label for locally connected networks in a given VRF is missing in LFIB table after MWR reload.
Conditions: Occurs after the reload of MWR running IOS 15.1(1)MR1 or 15.1(1)MR2.
Workaround: Use vrf definition command to create vrf instead of the ip vrf command. Remove and reapply config of problematic VRF.
•
Symptom: REP failed on a segment after MWR lost the power.
Conditions: Occurs when MWR loses DC power and then power up.
Workaround: Reload the MWR.
•
Symptom: For the multilink interface, queue-limit configurations from startup-config are not in effect after reload.
Conditions: Occurs for multilink interfaces.
Workaround: Shut down the multilink interface that the policy is attached to, and reapply the queue-limit configurations to the policy.
•
Symptom: The QOS policies applied on multilink interfaces do not match the traffic on egress any more.
Conditions: Occurs when performing an upgrade from 12.4(20)MR2 to 15.1(1)MR.
Workaround: Shut/no shut of the multilink interface will reactivate the QOS policy.
•
Symptom: MWR2941 crashed while changing vtp version 2 to 3 in server mode.
Conditions: Occurs when changing vtp version 2 to 3 in server mode. It happens on the particular box only.
Workaround: None.
•
Symptom: The show interface gigabitethernet command is not displaying drop counters.
Conditions: Occurs when show hqf interface command is not used first.
Workaround: Use show hqf int | inc drop command and then use the show interface gigabitethernet command. Now drop counter will get updated in the output.
Caveats in Cisco IOS Release 15.1(1)MR2
The following sections describe the caveats in Release 15.1(1)MR2.
Open Caveats
There are no open caveats in Release 15.1(1)MR2.
Closed Caveats
•
The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:
–
–
–
All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.
Cisco has released free software updates that address these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.
•
Symptom: Add CLI to monitor internal port (to NPU) tail drop.
Conditions: L3 traffic goes through the NPU. For bursty L3 traffic, some packets might get dropped on the internal switchport that is connected to the NPU.
The new CLI is added: switch tail-drop accounting winpath.
Workaround: None.
•
Symptom: 2941 router is not responding to IPv6 ND Network Solicitation packets that are destined for its directly connected unique global IPv6 address. But it does respond to NS packets destined for the solicited multicast address.
Conditions: Occurs when MWR-2941 router is running 15.1(1)MR IOS, configured with IPv6 unique global addressing, and connected to another router, with transit traffic flowing and static routing.
Workaround: Use an IGP to mask the issue, or configure the static route to point to the link local address of next hop.
•
Symptom: Traceback on 2941 while reloading the other connected 2941.
Conditions: None.
Workaround: None.
Caveats in Cisco IOS Release 15.1(1)MR1
The following sections describe the caveats in Release 15.1(1)MR1.
Open Caveats
There are no open caveats in Release 15.1(1)MR1.
Closed Caveats
•
The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:
–
–
–
All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.
Cisco has released free software updates that address these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS Software and Cisco IOS XE Software that could allow an unauthenticated, remote attacker to cause a reload of an affected device or trigger memory leaks that may result in system instabilities. Affected devices would need to be configured to process SIP messages for these vulnerabilities to be exploitable.
Cisco has released free software updates that address these vulnerabilities. There are no workarounds for devices that must run SIP; however, mitigations are available to limit exposure to the vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-sip.shtml.
•
The Cisco IOS Software network address translation (NAT) feature contains multiple denial of service (DoS) vulnerabilities in the translation of the following protocols:
–
–
–
All the vulnerabilities described in this document are caused by packets in transit on the affected devices when those packets require application layer translation.
Cisco has released free software updates that address these vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-nat.shtml.
•
Cisco IOS Software is affected by two vulnerabilities that cause a Cisco IOS device to reload when processing IP version 6 (IPv6) packets over a Multiprotocol Label Switching (MPLS) domain. These vulnerabilities are:
–
–
Cisco has released free software updates that address these vulnerabilities.
Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-ipv6mpls.shtml.
•
Symptom: Router crashed when shutting down an MLPPP member link.
Conditions: Occurs when running 16Mbps 1500 bytes traffic over MLPPP bundle with 8 E1 members, and fragmentation is disabled on MLPPP link. If you then shut down a E1link, MWR2941 will crash.
Workaround: Enable fragmentation on the MLPPP link.
•
Description: Increase Ethernet egress Qos buffer limits for both queue level and port level to 512.
Conditions: For the GE interface, the queue level buffer limit was 60 and port level buffer limit was 200, which may cause TCP low throughput. Occurs when the buffer limit is reached and tail drop happens.
Workaround: None.
•
Symptom: MWR2941-DC in IOS 15.0(1)MR or 15.0(2)MR reports incorrect ATM PVC counter values and ATM0/IMA0 input after clear counters command is executed.
Conditions: Occurs when clear counters command is executed.
Workaround: None.
•
Description: This is an enhancement which increases the default value of system-level switch buffer limit from 350 to 420.
Conditions: None.
Workaround: None.
•
Description: Average rate on VBR-RT PVCs on ATM IMA is reset to 0 cps after E1 flap.
Conditions: Flap of E1 links that belong to ATM IMA that is configured with VBR-RT service class.
Workaround: Reapply the configuration of VBR-RT service class under PVC config mode.
•
Description: Add a new CLI to configure global buffer limit for queueing. The buffer-limit range is 350 to 450, and default value is 420. The following example shows the new CLI:
2941-7(config)# switch buffer-limit ?<350-450> total queue buffer limitConditions: None.
Workaround: None.
•
Description: MWR 2941 does not save the network-clock-select mode revert command in the startup configuration.
Conditions: Occurs when the router is reloaded, after the network-clock-select mode revert command is accepted in the running configuration, and successfully copied to the startup configuration. When the router is reloaded, the command has been changed to network-clock-select mode nonrevert.
Workaround: None.
Caveats in Cisco IOS Release 15.1(1)MR
The following sections describe the caveats in Release 15.1(1)MR.
Open Caveats
•
Symptom: An ATM/IMA interface can remain down for 30 seconds while the peer IMA interface is active; the ATM/IMA interface status is inconsistent on both sides. This can result in packet loss during the interface status transition.
Conditions: Occurs when the ATM/IMA interface status changes, due to performing a shutdown/no shutdown on the interface or removing a T1/E1 cable.
Workaround: No Workaround
•
Symptom: The MWR 2941 crashes when you disable an E1 link within an MLPPP bundle.
Conditions: Occurs under the following conditions:
–
–
–
–
Workaround: None.
•
Symptom: The MWR 2941 displays inaccurate traffic rate counters on the serial interface.
Conditions: Occurs when you display counters for the serial interface.
Workaround: None.
Closed Caveats
•
Symptom: The MWR 2941 internal Ethernet tsec interface stops sending host traffic.
Conditions: Occurs when you configure an MTU size of 4470 on a VLAN interface while OSPF routing is enabled. To verify the condition, issue the show platform hardware ethernet tsec 1 command to see if the number of interface resets increases.
Workaround: Use the default MTU size for the VLAN interface or apply the ip ospf mtu-ignore command to the VLAN interface.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS Software and Cisco IOS XE Software that could allow an unauthenticated, remote attacker to cause a reload of an affected device or trigger memory leaks that may result in system instabilities. Affected devices would need to be configured to process SIP messages for these vulnerabilities to be exploitable.
Cisco has released free software updates that address these vulnerabilities. There are no workarounds for devices that must run SIP; however, mitigations are available to limit exposure to the vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-sip.shtml.
•
Symptom: The MWR 2941 displays traceback messages and the MLPPP link can flap when the MLPPP backhaul link is overloaded.
Conditions: Occurs when the MLPPP bundle is overloaded.
Workaround: None; try to keep traffic throughput below the line rate of 32 Mbps in order to avoid traceback messages.
•
Symptom: The MWR 2941 show version output displays an incorrect configuration register value of 0x0 after a software upgrade.
Conditions: Occurs when you upgrade the router from a 12.2MR release to 15.0MR release.
Workaround: The output is incorrect; issue the test platform hardware configreg_read command and then issue the show version command again to display the correct configuration register value.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS Software and Cisco IOS XE Software that could allow an unauthenticated, remote attacker to cause a reload of an affected device or trigger memory leaks that may result in system instabilities. Affected devices would need to be configured to process SIP messages for these vulnerabilities to be exploitable.
Cisco has released free software updates that address these vulnerabilities. There are no workarounds for devices that must run SIP; however, mitigations are available to limit exposure to the vulnerabilities.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-sip.shtml.
Caveats in Cisco IOS Release 15.0(2)MR
The following sections describe the caveats in Release 15.0(2)MR.
Open Caveats
•
Symptom: The MWR 2941 internal Ethernet tsec interface stops sending host traffic.
Conditions: Occurs when you configure an MTU size of 4470 on a VLAN interface while OSPF routing is enabled. To verify the condition, issue the show platform hardware ethernet tsec 1 command to see if the number of interface resets increases.
Workaround: Use the default MTU size for the VLAN interface or apply the ip ospf mtu-ignore command to the VLAN interface.
•
Symptom: The MWR 2941 displays traceback messages and the MLPPP link can go in and out of service.
Conditions: Occurs when the MLPPP bundles is overloaded.
Workaround: Maintain a traffic load of less than 32 Mbps on the MLPPP bundle.
Closed Caveats
•
Symptom: PTP connections on the MWR 2941 operating across multiple hops are unstable.
Conditions: Occurs when the MWR 2941 is configured as a boundary clock and exchanging PTP traffic that travels more than one network hop to reach a destination device.
Workaround: None.
Caveats in Cisco IOS Release 15.0(1)MR
The following sections describe the caveats in Release 15.0(1)MR.
Open Caveats
•
Symptom: The Cisco MWR 2941 does not permit changes to a PVC configured with cell packing. The router displays the following message:
ATMCMDFAIL:Unable to Configure PVC(1) 1/40 on ATM0/IMA0.1.Possibly multiple users configuring IOS simultaneouslyFurther info about other user:Process id: 256, Process: AToM manager, TTY: 0, Location: ConsoleConditions: Occurs in the following topology:
mwr1---MPLS---mwr2---MPLS---mwr3----MPLS---7600
The error occurs under the following conditions:
–
–
–
–
Workaround: None.
•
Symptom: The internal tsec Ethernet interface remains in a reset state and does not send host traffic. A reload is required to restore service.
Conditions: Occurs when you configure a VLAN interface with an MTU of 4470 and OSPF routing is enabled. To verify the condition, use the show platform hardware ethernet tsec 1 command to see if the number of interface resets increases.
Workaround: You can use one of the following workarounds:
–
–
•
Symptom: The 1.544 GPS interface is not available when configuring an input network clocking source.
Conditions: Occurs when you configure the network synchronization automatic command. This command assigns a clock source based on clock priority and quality. This clock selection mechanism does not support 1.544 GPS interface as an input clock source.
Workaround: Remove the network synchronization automatic command and use the network-clock-select command to configure this interface as a clock source.
Note
•
Symptom: The multilink interface fails to restore proper bandwidth after a reload.
Conditions: Occurs when you apply and remove a bandwidth statement on a multilink bundle interface.
Workaround: Remove the bandwidth statement from the interface.
•
Symptom: The show mpls forwarding command displays incorrect output; the bytes label switched statistic only displays statistics for one path.
Conditions: Occurs when you use equal cost multipath with MPLS forwarding.
Workaround: Use show platform hardware winpath cef label command to display statistics for each packet flow that is routed or the show interface summary command to display the packets routed though each interface.
•
Symptom: The Cisco MWR 2941 ATM/IMA interface drops for approximately 30 seconds while the peer IMA interface recovers; this condition can result in packet loss during an interface status transition.
Conditions: Occurs when the ATM/IMA interface changes status, such as when you perform shutdown/no shutdown or connect a T1/E1 cable.
Workaround: None.
•
Symptom: Interface statistics for the Gigabit Ethernet interface such as packets/bytes are inaccurate after processing traffic for a long period of time.
Conditions: Occurs when the Gigabit Ethernet interface processes traffic for an extended period of time.
Workaround: Issue the clear counters command to reset the Gigabit Ethernet interface statistics accounting.
•
Symptom: When you upgrade from a 12.2(33) release to Release 15.0(1)MR and reload the MWR 2941, the router displays an incorrect notification that the configuration register is set to 0x0.
Conditions: Occurs when you upgrade to Release 15.0(1)MR from a 12.2(33) release.
Workaround: Use the test platform hardware configreg_read command to perform a configuration register read value reset. After you execute this command, the show version command displays the correct configuration register value.
Closed Caveats
•
Symptom: The MWR can display a traceback
error_index=195 [WP_ERR_CH_ALREADY_CREATED]after an ATM pseudowire VC flaps repeatedly.Conditions: Occurs when an ATM pseudowire flaps repeatedly due to a timing or IP routing issue.
Workaround: Ensure that the ATM pseudowire is configured properly.
•
Symptom: The MWR 2941 displays traceback messages when you change the IMA group ID on the E1 controller. The traceback messages block configuration of the IMA group on the controller.
Conditions: Occurs when you enable and disable scrambling-payload multiple times before changing the ima-group ID.
Workaround: None.
•
Symptom: The MWR 2941 displays the following traceback and error messages when you delete and reconfigure a VLAN.
Mar 24 03:18:32.203 HKT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan441, changed state to upMar 24 03:18:32.203 HKT: Error Traceback:File = ../sources/iw/classifier/wpi_iw_dfc.cFunction=WPI_IwSystemCreateEmcLine = 1485error_index=575 [WP_INVALID_IW_EMC_FLOW_EXISTS_IN_HASH]Mar 24 03:18:32.203 HKT: -Traceback= 261314C 26B0BC8 273B3B8 26FEA78 27649B4 2633520 26336B8 2633B98 2633F38 25FE1B8 25FE678 25FF538 30C36B4 3095110 3095780 30DE8A0Mar 24 03:18:32.203 HKT: Error Traceback:File = ../sources/iw/core/wpi_iw_flow_aggregation.cFunction=WP_IwFlowAggregationDeleteLine = 2790error_index=483 [WP_ERR_IW_FLOW_AGG_NOT_EMPTY]Mar 24 03:18:32.203 HKT: -Traceback= 261314C 26B0BC8 2726D70 26336F4 2633B98 2633F38 25FE1B8 25FE678 25FF538 30C36B4 3095110 3095780 30DE8A0 30DEAB8 3C69C30 2067A08Conditions: Occurs when you delete and reconfigure VLANs quickly.
Workaround: Wait a few seconds when removing and reconfiguring a VLAN.
•
Symptom: The console becomes unresponsive after a routing change while the MWR 2941 is processing a heavy traffic load. The majority of traffic is dropped and the console can remain unresponsive until the traffic load diminishes or the router is reloaded.
Conditions: Occurs when the router is processing at least 6 Megabits of traffic with small (64 byte) IP packets and the destination route drops or changes. This condition has only been observed on MLPPP backhaul interfaces when multiple links in a bundle switch to a redundant MLPPP bundle path while the router is processing up to 20 Mbps of 64-byte IP packets.
Workaround: None.
•
Symptom: The router does not process the remaining bandwidth percent command on a policy map applied to a Gigabit Ethernet interface.
Conditions: Occurs when the class has the highest remaining bandwidth percent configuration of all classes in the policy map and the rate of traffic for the class is significantly lower than the overall bandwidth allocated to the interface.
Workaround: Configure lower priority classes in the policy map with lower percentages until the desired bandwidth allocation is reached.
Troubleshooting
The following sections describe troubleshooting commands you can use with the Cisco MWR 2941.
Collecting Data for Router Issues
To collect data for reporting router issues, issue the following command:
•
Collecting Data for ROMmon Issues
To collect data for ROMmon issues, issue the following command while in EXEC mode:
•
Note
Related Documentation
Related documents for implementing the Cisco MWR 2941 mobile wireless edge router are available on Cisco.com
To access the related documentation on Cisco.com, go to:
http://www.cisco.com/en/US/products/ps9395/tsd_products_support_series_home.html
Documents related to the Cisco MWR 2941-DC mobile wireless edge router include the following guides:
•
–
–
–
–
•
•
–
–
Services and Support
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
