Multicast Router Ports; Gvrp - Avaya 2330 Manual

Layer 2 fundamentals
If fast-leave processing is not enabled, when a device receives a "leave group" message for
a group that has members on the host interface, the device sends group-specific queries to
the host for the group being left. The group-specific queries have a maximum response time
set to a "last member query" interval. If no "join" reports are received within the maximum
response time, the device assumes there are no local members in this group and sends a
"leave" report to the multicast router (if available).
When a device receives a "leave group" message with fast-leave processing enabled, the
device does not send group-specific queries to the host. The device immediately updates its
own database and sends a "leave report" to the multicast router if there are no other members
for the group. Fast-leave processing helps stop the multicast traffic flow to the host after
receiving a "leave report".

Multicast router ports

Any Layer 2 port of a Secure Router 2330/4134 can become a multicast router (mrouter) port.
When a port receives an IGMP v1/v2 general query, that port is marked as an mrouter port. If
the Secure Router 2330/4134 stops receiving queries for a specific period of time, the
dynamically-learned mrouter port is removed. This period of time varies based on the
configured IGMP Snooping "query interval" and "maximum response time" settings.
You can also specify that an mrouter port be static. The static mrouter port configuration
overrides a dynamic entry.

GVRP

Generic Attribute Registration Protocol (GARP) VLAN Registration Protocol (GVRP) is an
application defined in the IEEE 802.1Q standard that allows routers to exchange VLAN
information in a network.
GVRP:
• runs only on 802.1Q trunk links
• prunes trunk links so that only active VLANs will be sent across trunk connections. GVRP
ports run in various modes to control how they will prune VLANs.
• expects to hear join messages from the routers or switches before it will add a VLAN to
the trunk
• updates and hold timers can be altered
• can be configured to dynamically add and manage VLANs to the VLAN database for
trunking purposes
42 Configuration — Layer 2 Ethernet
Comments? infodev@avaya.com
July 2013