BLADEOS 6.3 Application Guide
BMD00178, April 2010
27
Known Issues
This section describes known issues for BLADEOS 6.3 on the 1/10Gb Uplink Ethernet Switch
Module.
Software Upgrade Issues
Some time zones are different compared to release 6.1.2 and prior. After upgrading to release
6.3 or later, it is recommended that the administrator review the configured time zone and make
any appropriate changes. (ID:29778)
The STG port priority value is different compared to release 5.x and prior. In release 5.x and
prior, the priority value could be set to any integer from 0 to 255. In release 6.3 and later, the
range is still 0 to 255, but must be specified in increments of 4 (such as 0, 4, 8, 12, and so on).
If the specified value is not evenly divisible by 4, the value will be automatically rounded down
to the nearest valid increment whenever manually changing the priority value, when loading a
configuration from prior to release 6.3, and during the software upgrade process. If using STG
port priorities, after upgrading to release 6.3 or later, it is recommended that the administrator
review the configured values and make any appropriate changes. (ID: 38556)
Access Control Lists
When an Access Control List (ACL) is installed on two different ports, only one statistics
counter will be available. The GbESM does not support two different statistics counter for one
ACL installed on two different ports.
The ACL filters for TCP/UDP work properly only on packets that do not have IP options.
When configuring an ACL to set 802.1p priority for in-profile packets, and updating the DSCP
field using TOS bits for out-of-profile packets, the out-of-profile packets will have also the
802.1p priority set as defined in the in-profile setting.
Although the management port can be configured for port filtering option, actual port filtering
will not occur, because the system filters out the management VLAN.
IGMP Relay
When having joins from multiple VLANs, and the multicast data transmitter is on a VLAN that
did not receive any joins, multicast data is routed only if the flood option is disabled using the
/cfg/l3/igmp/adv/flood d
command.
If an IGMP v2 joins an IGMP group on the same port where an IGMP v1 join has already been
issued, the software will default to the IGMP v1 timeout value.
