Virtual Private LAN Services
Page 760 7750 SR OS Services Guide
• max-ve-id higher than the local VE-ID but smaller than the remote VE-IDs:
– Provisioning is allowed
– A warning message will be generated stating that “Higher VE-ID values were received in the
BGP VPLS context. Related PWs will be removed.”
– The PWs associated with the higher VE-IDs will be removed locally.
– Note that this is a situation that should be corrected by the operator as the PW may be down
just at the local PE, consuming unnecessarily core bandwidth. The higher VE-IDs should be
removed or lowered.
If the max-ve-id has increased a BGP route refresh is sent to the VPLS community to get the routes
which might have been rejected earlier due to max-ve-id check. Default no max-ve-id – max-ve-id is
not configured. A max-ve-id value needs to be provisioned for BGP VPLS to be in “no shutdown”
state.
Default no max-ve-id
Parameters value — Specifies the allowed range of [1-value] for the VE-id. The configured value must be bigger
than the existing VE-ids.
Values 1-65535
ve-name
Syntax ve-name name
no ve-name
Context config>service>vpls>bgp-vpls
Description This command creates or edits a ve-name. Just one ve-name can be created per BGP VPLS instance.
The no form of the command removes the configured ve-name from the bgp vpls node. It can be used
only when the BGP VPLS status is shutdown. Command “no shutdown” cannot be used if there is no
ve-name configured.
Default no ve-name
Parameters name — A character string identifying the VPLS Edge instance.
Values 32 ASCII chars max
ve-id
Syntax ve-id ve-id-value
no ve-id
Context config>service>vpls>bgp-vpls>ve-name
Description This command configures a ve-id. Just one ve-id can be configured per BGP VPLS instance. The VE-
ID can be changed without shutting down the VPLS Instance. When the VE-ID changes, BGP is
withdrawing its own previously advertised routes and sending a route-refresh to all the peers which
To Next Page
Loading...
