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
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > bridge vpls route-target
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 route-target

Syntax

[ no ] bridge vplsName vpls route-target { import | export | both } extendedCommunity

Release Information

Command introduced in JunosE Release 7.1.0.

Description

Creates or adds to a list of VPN extended communities that the router uses to determine which routes are imported by a VPLS instance that uses BGP as the signaling protocol. The no version removes a route target from the specified list.

A route is imported into the BGP address family for a specified VPLS instance when both of the following conditions are met:

  • An update message with a route-target export list advertises a route.
  • That list contains at least one route target that matches a route target in the route-target import list associated with a VPLS instance.

The bridge vpls route-target 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 route-target 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
  • import—Adds the route target to the specified VPLS instance's import list; the VPLS instance accepts only routes that have at least one route target that matches a route target in the import list
  • export—Adds the route target to the specified VPLS instance's export list; all routes advertised from this VPLS instance are associated with the export list
  • both—Adds the route target to both the import list and export list of the specified VPLS instance. This is the recommended setting for a VPLS instance
  • extendedCommunity—Two-part number in the format number1:number2 that identifies an extended community of VPNs, 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

Mode

Global Configuration

 

Related Documentation

  • Configuring VPLS Instances with BGP Signaling
 

Published: 2012-03-30

 
  • About Juniper
  • The New Network
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • 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