•ConfiguringVirtual Switches as SeparateRouting Instances on page 40
ConfiguringVirtual Switches as Separate RoutingInstances
Youcan configure twovirtual switches as separate routing instances on an MX Series
routerwith bridge domains and VLANs.
Beforeyoubegin, you should havealready configured a basic bridge domain environment.
Fora general description of a basic bridge domain environment, see “Layer2 Features
fora Bridging Environment” on page 21. For an example of a basic bridgedomain
configuration,see “ExampleRoadmap: Configuring a Basic Bridge Domain Environment”
onpage 22. More detailed examples arealso provided for the four features generally
requiredin a Layer 2 environment:
•Interfacesand VLAN tags required.
•Bridgedomains required by the topology.
•Spanningtree protocols required by the topology.
•Integratedbridging and routing required bythe topology.
Atthe end of this configuration, you createtwo virtual switches as separate routing
instancesto separate the VLANs and broadcastdomains. Because the same VLAN ID
canbe used in multiple switched networks,virtual switches can keep each VLAN and
broadcastdomain logically separated.
Toconfigure twovirtual switches as separate routing instances:
1. Thefollowing statements configurethe first virtual switch in a routing instance.
[edit]
routing-instances{
virtual-switch-1{
instance-typevirtual-switch;
...virtual-switch-1configurationwith one STP/VLAN ID set...
}
}
2. Thefollowing statement configurethe second virtual switch in a different routing
instance.
[edit]
routing-instances{
virtual-switch-2{
instance-typevirtual-switch;
...virtual-switch-2configurationwith another STP/VLAN ID set...
}
}
Thisis not a complete configuration.
Formore information about configuring virtual switches, see the Junos OS Layer2
ConfigurationGuide.
Copyright© 2010, Juniper Networks,Inc.40
Junos10.4 MX Series Ethernet ServicesRouters Solutions Guide