Routed VPLS
Page 286 7210 SAS-X, R6 OS Services Guide
Routed VPLS support available and Caveats
Routed VPLS supported functionality and restrictions for both access-uplink and network mode is
given below. The following is applicable to both the modes, unless called out explicitly.
• Static ARP cannot be configured with an IES IP interface that is associated with an R-
VPLS, though static MAC can be configured in an R-VPLS service.
• Only Static routes are supported. No dynamic routing protocols are supported.
• Whenever a VPLS FIB entry is removed either due to user action, aging or mac-move, the
corresponding ARP entry whose MAC address matches that of the MAC in the FIB is
removed from the ARP cache.
• In network mode and access-uplink mode R-VPLS is supported only in the base routing
instance. Only IPv4 addressing support is available for IES interfaces associated with
Routed VPLS service.
• IPv6 addressing support is not available for IES interface associated with R-VPLS service.
• In network mode, R-VPLS service cannot be bound to an VPRN Service.
• In both network mode and access-uplink mode, multiple SAPs configured on the same
port cannot be part of the same R-VPLS Service. In other words, a single service can only
be configured with a single SAP on a given port.
• Service MTU configuration is not supported in the R-VPLS service.
• In network mode, in 'any' service (that is, svc-sap-type set to any), null sap accepts only
un-tagged packets. Tagged packets received are dropped.
• MPLS protocols (For example: RSVP, LDP) cannot be enabled on R-VPLS IP interface
• MPLS-TP cannot use R-VPLS, IES, and IP interface.
• Discard-unknown feature is not supported in the VPLS service associated with R-VPLS
(only on 7210 SAS-X,R6)
• In network mode, R-VPLS SAPS and IES interface can be configured on a MC-LAG
LAG.