Ethernet Switching on EX Series Switches - Juniper Networks

<strong>Ethernet</strong> <strong>Switching</strong> on EX Series Switches
Table 3: Tracking RVI Usage (continued)
Switch
EX8200
EX2200, EX3300, EX4500, EX6200
Input (ingress)
Configurable
–
Output (Egress)
Automatic
You can view RVI input (ingress) and output (egress) totals with the command show
interfaces vlan extensive. Look at the input and output values in the field Logical Unit
Transit Statistics for RVI activity values.
RVI Functions and Other Technologies
Related
Documentation
RVIs are similar to IRBs, SVIs, and BVIs. They can also be combined with other functions:
• RVIs are similar to integrated routing and bridging (IRB) interfaces supported on Juniper
routers and switch virtual interfaces (SVIs) and bridge-group virtual interfaces (BVIs)
supported on other vendors’ devices.
• VRF is often used in conjunction with Layer 3 subinterfaces, allowing traffic on a single
physical interface to be differentiated and associated with multiple virtual routers. For
more information about VRF, see “Understanding Virtual Routing Instances on EX
Series Switches” on page 26.
• For redundancy, you can combine an RVI with implementations of the Virtual Router
•
Redundancy Protocol (VRRP) in both bridging and virtual private LAN service (VPLS)
environments. For more information about VRRP, see Understanding VRRP on EX
Series Switches.
Understanding Bridging and VLANs on EX Series Switches on page 3
• Configuring Routed VLAN Interfaces (CLI Procedure) on page 157
Understanding Private VLANs on EX Series Switches
14
VLANs limit broadcasts to specified users. Private VLANs (PVLANs) take this concept a
step further by limiting communication within the VLAN. PVLANs accomplish this
limitation by restricting traffic flows through their member switch ports (which are called
“private ports”) so that these ports communicate only with a specified uplink trunk port
or with specified ports within the same VLAN. The uplink trunk port (or link aggregation
group or LAG) is usually connected to a router, firewall, server, or provider network. Each
PVLAN typically contains many private ports that communicate only with a single uplink,
thereby preventing the ports from communicating with each other. PVLANs provide Layer
2 isolation between ports within the same VLAN, splitting a broadcast domain into
multiple isolated broadcast subdomains and essentially putting secondary VLANs inside
another primary VLAN.
Just like regular VLANs, PVLANs are isolated on Layer 2 and require that a Layer 3 device
be used to route traffic among them. PVLANs are useful for restricting the flow of
broadcast and unknown unicast traffic and for limiting the communication between
–
Copyright © 2012, Juniper Networks, Inc.