Routed VPLS
Page 302 7210 SAS M Services Guide
QoS Support for VPLS SAPs and IP interface in a Routed VPLS service
• SAP ingress classification (IPv4 and MAC criteria) is supported for SAPs configured in
the service. SAP ingress policies cannot be associated with IES IP interface.
• Egress Port based queuing and shaping are available. It is shared among all the SAPs on
the port.
• Port based Egress Marking is supported for both routed packets and bridged packets. The
existing access egress QoS policy can be used for Dot1p marking.
• IES IP interface bound to routed VPLS services, IES IP interface on access SAPs and IES
IP interface on Access-Uplink SAPs are designed for use with inband management of the
node. Consequently, they share a common set of queues for CPU bound management
traffic. All CPU bound traffic is policed to pre-defined rates before being queued into
CPU queues for application processing. The system uses meters per application or a set of
applications. It does not allocate meters per IP interface. The possibility of CPU
overloading has been reduced by use of these mechanisms. Users must use appropriate
security policies either on the node or in the network to ensure that this does not happen.
Routed VPLS Supported Routing Related Protocols
The following lists the support available for routing protocols on IP interfaces bound to a VPLS
service
• Static-routing is supported
• BGP is not supported
• OSPF is not supported
• ISIS is not supported
• BFD is not supported
• VRRP is not supported
• ARP is supported
• DHCP Relay is not supported
Spanning Tree and Split Horizon
A routed VPLS context supports all spanning tree and port-based split horizon capabilities that a
non-routed VPLS service supports.
To Next Page
Loading...
Need help?
General
