
5
Cisco IOS XE 3S Release Notes for the Cisco ASR 903 Router
OL-26630-08
Chapter
Limitations and Restrictions
QoS Limitations
For a description of QoS features and limitations on the Cisco ASR 903 Router in Release 3.8S, see
http://www.cisco.com/en/US/docs/routers/asr903/software/guide/chassis/Release3.8.0S/ASR903-Chas
sis-SW-38.html
Software Upgrade Limitation
•
We recommend you set the
interface-module-delay
value to 150 or greater in order to ensure
sufficient time for IM software upgrades.
Subinterfaces Limitation
•
The Cisco ASR 903 router does not support subinterface configurations except on ATM interfaces.
Note
You can configure similar functionality using multiple Ethernet Virtual Connections on an
interface. For more information, see
Configuring Ethernet Virtual Connections on the Cisco
ASR 903 Router
.
T1/E1 IM Limitations
•
Inverting data on the T1/E1 interface is not supported—Inverting the data stream using the invert
data interface command is not supported.
•
Bit error rate test (BERT) patterns have limited support—Currently, only the 2^11, 2^15,
2^20-O153, and 2^20-QRSS patterns are supported for BERT.
•
If you issue the
no card type
command on the controller, you must reload the router in order to
configure a new
card type
value.
VPLS BGP Signaling
•
TE as core interface is supported for VPLS BGP Signalling but TE as preferred path is
not
supported.
•
MAC Flushing is
not
supported in this release for VPLS BGP Signaling.
•
Templates are
not
supported in this release for VPLS BGP Signaling.
•
Support for H-VPLS is available only for the hierarchical route reflector (RR) model.
•
BGP Signaling Inter-AS Option A is supported in this release. BGP Signaling Inter-AS Option B
and Inter-AS Option C are
not
supported in this release.
•
Maximum number of supported BGP Signaling neighbors per VFI is 32.
•
When route designator (RD) is explicitly configured within the same VPLS domain, the virtual
forwarding interface (VFI)s with the same VPN ID on different PE's must have the same RD
configured (as the auto-generated RD is same for Intra AS). Thus, all the PE's within a VPLS domain
must have the same RD. See
Example: Configuring VPLS BGP Signaling with Explicit RD
Configurations:, page 5
.
For more information, see
VPLS BGP Signaling.
Example: Configuring VPLS BGP Signaling with Explicit RD Configurations:
l2vpn vfi context TEST1
vpn id 1
autodiscovery bgp signaling bgp
ve id 1
ve range 100
rd 2:1 ---> RD must be same for all the VFI's in all the PE's