![](http://pdfasset.owneriq.net/8/48/8487ffbe-39e2-4a92-9bcd-73b9dbfe021c/8487ffbe-39e2-4a92-9bcd-73b9dbfe021c-bg37.png)
domain-type bridge;
vlan-id 200;
interface ge-3/3/3.200;
interface ae1.200;
interface ae3.200;
}
}
3.
Configure a bridge domain on Router 3:
[edit]
bridge-domains {
vlan100 {
domain-type bridge;
vlan-id 100;
interface ge-2/2/2.100;
interface ae3.100;
}
vlan200 {
domain-type bridge;
vlan-id 200;
interface ge-3/3/3.200;
interface ae3.200;
}
vlan201 {
domain-type bridge;
vlan-id 201;
}
vlan202 {
domain-type bridge;
vlan-id 202;
}
vlan203 {
domain-type bridge;
vlan-id 203;
}
vlan204 {
domain-type bridge;
vlan-id 204;
}
vlan205 {
domain-type bridge;
vlan-id 205;
}
}
Related
Documentation
MX Series Ethernet Services Routers Solutions Page•
• Layer 2 Features for a Bridging Environment on page 21
• Example Roadmap: Configuring a Basic Bridge Domain Environment on page 22
• Example Step: Configuring Interfaces and VLAN Tags on page 24
• Example Step: Configuring Spanning Tree Protocols on page 32
• Example Step: Configuring Integrated Bridging and Routing on page 34
31Copyright © 2010, Juniper Networks, Inc.
Chapter 2: Basic Layer 2 Features on MX Series Routers