Brocade TurboIron 24X Series Configuration Guide - Manual (Page 65)

Brocade TurboIron 24X Series Configuration Guide 31
53-1003053-01
Configuring basic system parameters
New start and end dates for US daylight saving time
NOTE
This feature applies to US time zones only.
Starting in 2007, the system will automatically change the system clock to Daylight Saving Time
(DST), in compliance with the new federally mandated start of daylight saving time, which is
extended one month beginning in 2007. The DST will start at 2:00am on the second Sunday in
March and will end at 2:00am on the first Sunday in November.
The DST feature is automatic, but to trigger the device to the correct time, the device must be
configured to the US time zone, not the GMT offset. To configure your device to use the US time
zone, enter the following command.
TurboIron(config)#clock timezone us pacific
Syntax: [no] clock timezone us <timezone-type>
Enter pacific, eastern, central, or mountain for <timezone-type>.
This command must be configured on every device that follows the US DST.
To verify the change, run a show clock command.
TurboIron#show clock
Limiting broadcast, multicast, and unknown unicast traffic
TurboIron X Series devices can forward all flooded traffic at wire speed within a VLAN. However,
some third-party networking devices cannot handle high rates of broadcast, multicast, or
unknown-unicast traffic. If high rates of traffic are being received by the device on a given port of
that VLAN, you can limit the number of broadcast, multicast, or unknown-unicast packets or bytes
received each second on that port. This can help to control the number of such packets or bytes
that are flooded on the VLAN to other devices.
Byte-based limiting for broadcast, multicast, and unknown unicast traffic provides the ability to rate
limit traffic based on byte count instead of packet count. When the byte mode is enabled, packets
will be received on a port as long as the number of bytes received per second is less than the
corresponding limit. Once the limit is reached, further packets will be dropped.
TurboIron X Seriesdevices do not support packet-based and byte-based limiting simultaneously on
the same port. For example, if you configure packet-based limiting for broadcast traffic, you must
also configure packet-based limiting for multicast and unknown unicast traffic. Likewise, if you
configure byte-based limiting for broadcast traffic, you must also configure byte-based limiting for
multicast and unknown unicast traffic.
Command syntax for packet-based limiting
To enable broadcast limiting on a group of ports by counting the number of packets received, enter
commands such as the following.
TurboIron(config)#interface ethernet 1 to 8
TurboIron(config-mif-e10000-1-8)#broadcast limit 65536
These commands configure packet-based broadcast limiting on ports 1 – 8. On each port, the
maximum number of broadcast packets per second cannot exceed 65,536 packets per second.