bridge vpls rd

Syntax

bridge vplsName vpls rd routeDistinguisher

no bridge vplsName vpls rd

Release Information

Command introduced in JUNOSe Release 7.1.0.

Description

Specifies the unique two-part route distinguisher for a VPLS instance that uses BGP as the signaling protocol. Because you cannot change or remove the route distinguisher for a VPLS instance after you set it, issuing the no version fails, and causes the router to display an error message.

The following rules apply when you configure the route distinguisher for a VPLS instance:

• After you set the route distinguisher for a VPLS instance, you cannot change it for that VPLS instance. To change the route distinguisher, you must either remove the transport virtual router configuration from the VPLS instance or delete the VPLS instance from the router. You can then reconfigure the VPLS instance with a new route distinguisher.
• Multiple VPLS instances that use the same transport virtual router cannot have the same route distinguisher. Conversely, multiple VPLS instances that use different transport virtual routers can have the same route distinguisher.

The bridge vpls rd command is not valid for a VPLS instance that uses LDP as the signaling protocol. To configure a VPLS instance with LDP signaling, use the mpls ldp vpls vpls-id command and the mpls ldp vpls neighbor command.

Note: The bridge vpls rd command is available for a VPLS instance only after you issue the bridge vpls transport-virtual-router command, which creates the VPLS instance and configures the transport virtual router.

Options

• vplsName—Name of a VPLS instance created with the bridge vpls transport-virtual-router command
• routeDistinguisher—Unique two-part identifier in the format number1:number2, where:
  • number1—Autonomous system (AS) number or an IP address
  • number2—Unique integer; 32 bits if number1 is an AS number; 16 bits if number1 is an IP address

Global Configuration

Related Topics

• Configuring VPLS Instances with BGP Signaling in the JUNOSe BGP and MPLS Configuration Guide

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.