Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > bridge vpls site-name site-id
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...
 

Related Documentation

  • Configuring VPLS Instances with BGP Signaling
 

bridge vpls site-name site-id

Syntax

[ no ] bridge vplsName vpls site-name siteName site-id siteId
[ multi-homed priority priority ]

Release Information

Command introduced in JunosE Release 7.1.0.
multi-homed priority keywords and priority variable added in JunosE Release 9.3.0.

Description

Configures a customer site name and a unique site identifier that belongs to the specified VPLS instance that uses BGP as the signaling protocol. Optionally configures the site to be multihomed. In a VPLS configuration, each customer site is represented by a customer edge (CE) device located at the edge of the customer’s network. The router (VPLS edge device, also known as VE router) communicates with the customer site by means of a bridge network interface connection to the CE device. The no version removes the site name and site identifier from the VPLS instance, or removes the multihomed configuration for the customer site and returns it to a single-homed state.

The bridge vpls site-name site-id 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 site-name site-id 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
  • siteName—Name of the site; string of up to 128 alphanumeric characters
  • siteId—Numerical identifier for the site; must be an unsigned 16-bit integer greater than zero that is unique across the VPLS domain associated with the VPLS instance
  • priority—Number that sets the priority of this VPLS instance for a multi-homed site, in the range 1–65535; priority is sent in BGP advertisements as the Local-Preference attribute and determines whether the router hosting the VPLS instance becomes the designated VE router for this multihomed site

Mode

Global Configuration

 

Related Documentation

  • Configuring VPLS Instances with BGP Signaling
 

Published: 2012-06-28

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out