Routed Vlan Interface - Juniper JUNOS OS 10.3 - SOFTWARE Manual

For ex series ethernet switches
Hide thumbs Also See for JUNOS OS 10.3 - SOFTWARE:
Table of Contents

Advertisement

Complete Software Guide for Junos

Routed VLAN Interface

1288
®
OS for EX Series Ethernet Switches, Release 10.3
The VLAN registration information sent by MVRP and GVRP includes the current VLANs
membership—that is, which switches are members of which VLANs—and which switch
interfaces are in which VLAN. GVRP and MVRP share all VLAN information configured
on a local switch.
MVRP can also be used to dynamically create VLANs, which are VLANs created on one
switch and propagated to other switches as part of the MVRP message exchange process.
As part of ensuring that VLAN membership information is current, GVRP and MVRP
remove switches and interfaces from the VLAN information when those switches and
interfaces become unavailable. Pruning VLAN information has these benefits:
Limits the network VLAN configuration to active participants only, reducing network
overhead.
Targets the scope of broadcast, unknown unicast, and multicast (BUM) traffic to
interested devices only.
In a traditional network, broadcast domains consist of either physical interfaces connected
to a single switch or logical interfaces connected to one or more switches through VLAN
configurations. Switches send traffic to hosts that are part of the same broadcast domain,
but routers are needed to route traffic from one broadcast domain to another and to
perform other Layer 3 functions such as traffic engineering. EX Series switches use a
Layer 3 routed VLAN interface (RVI) named
using it to route data to other Layer 3 interfaces. The RVI functions as a logical router,
eliminating the need for having both a switch and a router.
The RVI (the
interface) must be configured as part of a broadcast domain or virtual
vlan
private LAN service (VPLS) routing instance for Layer 3 traffic to be routed out of it. The
RVI supports IPv4, IPv6, MPLS, and IS-IS traffic. At least one Layer 2 logical interface
must be operational for the RVI to be operational. You must configure a broadcast domain
or VPLS routing instance for the RVI just as you would configure a VLAN on the switch.
Multicast data, broadcast data, or unicast data is switched between ports within the
same RVI broadcast domain or VPLS routing instance. The RVI routes data that is destined
for the switch's media access control (MAC) address.
Jumbo frames of up to 9216 bytes are supported on an RVI. To route jumbo data packets
on the RVI, you must configure the jumbo MTU size on the member physical interfaces
of the RVI and not on the RVI itself (the
packets—for example, to ping the RVI with a packet size of 6000 bytes or more—you
must explicitly configure the jumbo MTU size on the interface named
CAUTION: Setting or deleting the jumbo MTU size on the RVI (the
interface) while the switch is transmitting packets might result in dropped
packets.
See "Configuring Routed VLAN Interfaces (CLI Procedure)" on page 1379.
vlan
to perform these routing functions,
vlan
interface). However, for jumbo control
Copyright © 2010, Juniper Networks, Inc.
(the RVI).
vlan
vlan

Advertisement

Table of Contents
loading

Table of Contents