Other vlan features, Hardware, Allocating memory – Brocade BigIron RX Series Configuration Guide User Manual
Page 397: For more vlans or virtual routing interfaces
BigIron RX Series Configuration Guide
319
53-1002484-04
Other VLAN features
11
Other VLAN features
Allocating memory for more VLANs or virtual routing
interfaces
By default, you can configure up to 512 VLANs and virtual routing interfaces on the device.
Although this is the default maximum, the device can support up to 4089 VLANs and 4095 virtual
routing interfaces. (VLAN IDs 0, 4090, 4091, 4092 and 4095 are reserved.)
NOTE
If many of your VLANs will have an identical configuration, you might want to configure VLAN groups.
If you need to configure more than 512 VLANs, enter commands such as the following at the global
CONFIG level of the CLI.
BigIron RX(config)# system-max vlan 2048
BigIron RX(config)# write memory
BigIron RX(config)# end
BigIron RX# reload
Syntax: [no] system-max vlan <num>
The <num> parameter specifies the maximum number of VLANs that can be configured. Enter 1 –
4089, but IDs 4091 – 4094 are reserved.
Hardware flooding for Layer 2 multicast and broadcast
packets
Broadcast and multicast packets do not have a specific recipient. In order for these "special"
packets to reach their intended recipient, they needed to be sent on all ports of the VLAN (or
"flooded" across the VLAN).
By default, the device performs hardware flooding for Layer 2 multicast and broadcast packets.
(Layer 2 multicast packets have a multicast address in the destination MAC address field.)
However, if uplink VLANs or protocol-based VLANs are configured, this default behavior is
overridden and software flooding is enabled.
You can disable hardware flooding for Layer 2 multicast and broadcast packets on a per-VLAN
basis. For example:
BigIron RX(config)#
BigIron RX(config)# vlan 2
BigIron RX(config-vlan-2)# no multicast-flooding
Syntax: [no] multicast-flooding
NOTE:
•
This feature is supported on the 10 Gigabit Ethernet module.
•
This feature cannot be enabled on an empty VLAN; the VLAN must already have ports
assigned to it prior to enabling this feature.
•
This feature is not supported on Layer 3 protocol-based VLANs.
•
This feature is not supported on private VLANs.