Layer 2 Virtual Switch Instances
Understanding Layer 2 Virtual Switches Instances
Benefit of Using Layer 2 Virtual Switch Instances:
Splitting Layer 2 traffic using virtual switch instances allows you to more logically organize your Layer 2 traffic into multiple “virtual” Layer 2 networks.
At Layer 2, you can group one or more VLANs into a single routing instance to form a virtual switch instance. A virtual switch instance is composed of VLANs. The virtual switch instance isolates a LAN segment and contains most Layer 2 functions, such as spanning-tree protocol instances and VLAN ID spaces, into it’s own smaller, logical network. Splitting Layer 2 traffic using virtual switch instances allows you to more logically organize your Layer 2 traffic into multiple “virtual” Layer 2 networks.
A default virtual switch, called default-switch, is automatically created when a virtual switch is configured. All Layer 2 traffic not assigned to a VLAN in a virtual switch automatically becomes part of the default virtual switch.
You can configure a virtual switch to participate only in Layer 2 bridging and optionally to perform Layer 3 routing. In addition, you can configure spanning-tree protocols (STPs) within the virtual switch to prevent forwarding loops. For more information about how to configure Layer 2 logical ports on an interface, see the Junos OS Network Interfaces Library for Routing Devices.
You can associate one or more logical interfaces configured as trunk interfaces with a virtual switch. A trunk interface, or Layer 2 trunk port, enables you to configure a logical interface to represent multiple VLANs on the physical interface. For more information about how to configure trunk interfaces, see the Junos OS Network Interfaces Library for Routing Devices.
You can also configure Layer 2 forwarding and learning properties for the virtual switch.
Configuring a Layer 2 Virtual Switch on an EX Series Switch
A Layer 2 virtual switch, which isolates a LAN segment with its spanning-tree protocol instance and separates its VLAN ID space, filters and forwards traffic only at the data link layer. Each VLAN consists of a set of logical ports that participate in Layer 2 learning and forwarding. A virtual switch represents a Layer 2 network.
Two main types of interfaces are used in virtual switch hierarchies:
Layer 2 logical interface—This type of interface uses the VLAN-ID as a virtual circuit identifier and the scope of the VLAN-ID is local to the interface port. This type of interface is often used in service-provider-centric applications.
Access or trunk interface—This type of interface uses a VLAN-ID with global significance. The access or trunk interface is implicitly associated with VLANs based on VLAN membership. Access or trunk interfaces are typically used in enterprise-centric applications.
Note:The difference between access interfaces and trunk interfaces is that access interfaces can be part of one VLAN only and the interface is normally attached to an end-user device (packets are implicitly associated with the configured VLAN). In contrast, trunk interfaces multiplex traffic from multiple VLANs and usually interconnect switches.
To configure a Layer 2 virtual switch, include the following statements:
[edit] routing-instances { routing-instance-name ( instance-type virtual-switch; vlans vlan-name{ vlan-id (all | none | number); [...configure optional VLAN parameters] } } }
To enable a virtual switch, you must specify virtual-switch
as the instance-type
.
The VLANs that are specified with the vlan-id
statement
are included in the virtual switch.
You can configure other optional VLAN parameters in the virtual switch.
Configuring a Layer 2 Virtual Switch with a Layer 2 Trunk Port
You can associate one or more Layer 2 trunk interfaces with a virtual switch.
A virtual switch configured with a Layer 2 trunk port also
supports IRB within a VLAN. IRB provides simultaneous support for
Layer 2 bridging and Layer 3 IP routing on the same interface.
Only an interface configured with the interface-mode (access
| trunk)
statement can be associated with a virtual switch.
An access interface enables you to accept packets with no VLAN identifier.
In addition, you can configure Layer 2 learning and forwarding properties for the virtual switch.
To configure a virtual switch with a Layer 2 trunk interface, include the following statements:
[edit] routing-instances { routing-instance-name { instance-type virtual-switch; interface interface-name; vlans name{ vlan-id (all | none | number); [...configure optional VLAN parameters] } } }