VLAN Configuration for VPLS and Bridge Domains

[Contents] [Prev] [Next] [Index] [Report an Error]

This chapter provides configuration and operational information to help you manipulate virtual local area networks (VLANs) within a bridge domain or a virtual private LAN service (VPLS) instance. The VPLS configuration is not covered in this chapter. For more information about configuring Ethernet pseudowires as part of VPLS, see the JUNOS Software Feature Guide.

Note: This chapter is not intended as a troubleshooting guide. However, you can use it with a broader troubleshooting strategy to identify MX-series router network problems.

The manipulation of VLANs within a bridge domain or a VPLS instance can be done in several ways:

By using the vlan-map statements at the [edit interfaces] hierarchy level. This chapter does not use vlan-map. For more information about VLAN maps, see the JUNOS Interfaces Configuration Guide.
By using vlan-id statements within a bridge domain or VPLS instance hierarchy. This method is used in the configuration in this chapter.

The vlan-id and vlan-tags statements under the bridge domain or VPLS routing instance are used to:

Translate (normalize) received VLAN tags, or
Implicitly create multiple learning domains, each with a “learn” VLAN.

The use of a VLAN map or a normalized VLAN is optional.

Note: You cannot use vlan-map when configuring a normalized VLAN.

This chapter discusses the following topics:

[Contents] [Prev] [Next] [Index] [Report an Error]