
The following operations are performed when you use the vlan-id all configuration:
•
The logical interfaces are configured as a trunk port that multiplexes traffic from
multiple VLANs and usually interconnects switches.
•
All the VLAN identifiers are associated with a Layer 2 trunk port. Each of the logical
interfaces, ge-1/0/0.1 , or ge-2/0/0.1, or ge-3/0/0.1, accepts packets tagged with any
VLAN ID specified in the respective vlan-id-range statements.
•
The association of the received packet to a logical interface is done by matching the
VLAN tags of the received packet with the VLAN tags configured on one of the logical
interfaces on that physical port. The vlan-id all configuration within the bridge domain
c1-vlan-v1-to-v1000 for customer-c1-virtual-switch sets the normalized VLAN value.
For a logical interface with a single VLAN tag, a learning domain implicitly created for
each normalized VLAN of the interface.
•
Bridge domain c1-vlan-v1-to-v1000 for customer-c1-virtual-switch has three logical
interfaces:
•
Logical interface ge-1/0/0.1 configured on physical port ge-1/0/0.
•
Logical interface ge-2/0/0.1configured on physical port ge-2/0/0.
•
Logical interface ge-3/0/0.1configured on physical port ge-3/0/0.
•
Packets received on logical interfaces ge-1/0/0.11 or ge-6/0/0.11 with a single VLAN
tag of 1500 in the frame are accepted.
•
Unknown source MAC addresses and unknown destination MAC addresses are learned
based on their normalized VLAN values of 1 through 1000.
•
All packets sent on the VPLS pseudowire have a normalized VLAN tag after the source
MAC address field in the encapsulated Ethernet packet.
•
Although there are only three logical interfaces in the VPLS instance called
customer-c1-virtual-switch, the same MAC address (for example, M1) can be learned
on different logical interfaces for different VLANs. For example, MAC address M1 could
be learned on logical interface ge-1/0/0.1 for VLAN 500 and also on logical interface
ge-2/0/0.1 for VLAN 600.
Related
Documentation
• Ethernet Networking
• VLANs Within a Bridge Domain or VPLS Instance on page 43
• Packet Flow Through a Bridged Network with Normalized VLANs on page 44
• Configuring Learning Domains for VLAN IDs Bound to Logical Interfaces on page 47
Copyright © 2013, Juniper Networks, Inc.62
Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide
Comentarios a estos manuales