Routed VPLS supported functionality and restrictions for network mode are specified as follows:
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.
In network mode, both static routing and dynamic routing protocols are supported.
Whenever a VPLS FIB entry is removed because of 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, R-VPLS is supported in both the base routing instance (IES) and VPRN services. IPv4 addressing is supported for IES and VPRN IP interfaces associated with an R-VPLS service.
IPv6 addressing support is not available for IES interfaces associated with an R-VPLS service.
In both network modes, multiple SAPs configured on the same port cannot be part of the same R-VPLS Service. That is, a single service can only be configured with a single SAP on a specific 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 untagged packets. Tagged packets received are dropped.
In network mode, MPLS protocols (For example: RSVP, LDP) cannot be enabled on R-VPLS IP interface
In network mode, MPLS-TP cannot use R-VPLS, IES, and IP interface.
In network mode, R-VPLS SAPS can be configured on a MC-LAG LAG.
The discard-unknown feature is not supported in the VPLS service associated with R-VPLS (only on 7210 SAS-R6 and 7210 SAS-R12).
In the saved configuration file, for the R-VPLS service, the R-VPLS service instance appears twice; one appearance for service creation and one with all the other configuration parameters. This is required to resolve references to the R-VPLS service and to execute the configuration without any errors.
Service-based SHGs are not supported in an R-VPLS service.