If the rate exceeds the configured maximum allowed limit, it disables the SAP where the source MAC was last seen. When enabled in a VPLS, mac-move monitors the relearn rate of each MAC. Typically, the spanning tree protocol (STP) detects loops in the topology, but for those networks that do not run STP, the mac-move feature is an alternative way to protect the network against loops. A sustained, high relearn rate can be a sign of a loop somewhere in the VPLS topology. This command enables the context to configure MAC move attributes. The no version of this command disables appending the Agent-Circuit-Id information. In addition, any newly created SAPs bound to the VPLS will default to match the VPLS setting.Īs per the DSL Forum TR-101 April'06 specification, section 3.9.2, any PPPoE vendor-specific tag that may already be present in the received frame is replaced by the 7705 SAR client-id tag. If there is a mix of enabled and disabled SAPs bound to the VPLS instance, applying the command to the VPLS will override the mix, enabling (or disabling) pppoe-circuit-id on all the SAPs. Furthermore, pppoe-circuit-id can be applied to individual SAPs bound to that VPLS instance in order to override the VPLS setting. When applied to a VPLS instance, pppoe-circuit-id appends the Agent-Circuit-Id to all ATM SAPs bound to that VPLS instance. The pppoe-circuit-id command can be enabled or disabled for a VPLS instance or an individual ATM SAP. The ATM SAP must be configured for bridged llc-snap encapsulation. The Agent-Circuit-Id information is compliant with RFC 4679 section-3.3.1 Agent-Circuit-Id. When enabled, this command appends Agent-Circuit-Id information to PADI and PADR packets received from an ATM SAP (the subscriber) that is bound to a VPLS instance. The service cannot be deleted until all SAPs and SDPs defined within the service ID have been shut down and deleted, and the service has been shut down. The no form of this command deletes the VPLS service instance with the specified service-id. More than one VPLS service may be created for a single customer ID.īy default, no VPLS instances exist until they are explicitly created. Attempting to edit a service with the incorrect customer-id specified will result in an error. Once a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. Associate a range of VLANs with the mVPLS by using the managed-vlan-list command. To create a management VPLS, include the m-vpls keyword when creating the VPLS. To edit the customer association, the service must be deleted and recreated with a new customer association. Once a service has been created with a customer association, it is not possible to edit the customer association.
The customer-id must already exist (created using the customer command in the service context). When a service is created, the create keyword and the customer keyword and customer-id must be specified in order to associate the service with a customer. If the service-id exists, the context for editing the service is entered.Ī VPLS service connects multiple customer sites together acting like a zero-hop, Layer 2 switched domain. If the service-id does not exist, a context for the service is created. This command creates or edits a Virtual Private LAN Services (VPLS) instance.
0 kommentar(er)
