EasyManua.ls Logo

Dasan V5808 - Displaying Mcfdb Information; IGMP Snooping Basic

Dasan V5808
814 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
UMN:CLI User Manual
V5808
414
no ip mcfdb aging-time
Deletes the specified aging time for forwarding entries.
To specify the maximum number of forwarding entries on the McFDB, use the following
command.
Command
Mode
Description
ip mcfdb aging-limit
<256-65535>
Global
Specifies the maximum number of forwarding entries
on the McFDB.
256-65535: number of entries (default: 5000)
no ip mcfdb aging-limit
Deletes the specified maximum number of forwarding
entries.
9.2.1.3 Displaying McFDB Information
To display McFDB information, use the following command.
Command
Mode
Description
show ip mcfdb
Enable
Global
Bridge
Shows the current aging time and maximum number of
forwarding entries.
show ip mcfdb aging-entry [vlan
VLAN | group A.B.C.D] [mac-
based | detail]
Shows the current forwarding entries.
VLAN: VLAN ID (1-4094)
A.B.C.D: ipv4 multicast group address
X:X::X:X: ipv6 multicast group address
mac-based: lists entries on a MAC address basis
To clear multicast forwarding entries, use the following command.
Command
Mode
Description
clear ip mcfdb [* | vlan VLAN]
Enable
Global
Clears multicast forwarding entries.
*: all forwarding entries
VLAN: VLAN ID (1-4094)
clear ip mcfdb vlan VLAN group
A.B.C.D source A.B.C.D
Clears a specified forwarding entry.
group A.B.C.D: multicast group address
source A.B.C.D: multicast source address
9.2.2 IGMP Snooping Basic
Layer 2 switches normally flood multicast traffic within the broadcast domain, since it has
no entry in the Layer 2 forwarding table for the destination address. Multicast addresses
never appear as source addresses, therefore the switch cannot dynamically learn
multicast addresses. This multicast flooding causes unnecessary bandwidth usage and
discarding unwanted frames on those nodes which did not want to receive the multicast
transmission. To avoid such flooding, IGMP snooping feature has been developed.
The purpose of IGMP snooping is to constrain the flooding of multicast traffic at Layer 2.
IGMP snooping, as implied by the name, allows a switch to snoop the IGMP transaction
between hosts and routers, and maintains the multicast forwarding table which contains
the information acquired by the snooping. When the switch receives a join request from a

Table of Contents