Addendum

applied on the egress interface, which must not cause the IGMP queries to be transmitted out of the
interface.
• The following note applies to the Configuring a VLT VLAN or LAG in a PVLAN section of this
Addendum document:
When you configure VLT nodes in a PVLAN, you must create the PVLAN after you configure a VLT
domain. If you configure the PVLAN before you set up the VLT domain, you must delete and
reconfigure the VLANs to enable the VLT interconnect (VLTi) or ICL membership to be correctly
added. Otherwise, the ICL is not properly tagged with the PVLAN.
• The following note applies to the Microsoft Network Load Balancing overview topic of this Addendum
document:
The flow processor (FP) entry that is used for Microsoft NLB is not redefined after a reload of the
system if the interface that is used for NLB was shut down before the system reload. This problem
occurs because the arp ip-address multicast-mac-address command that you configure to
associate an IP address with a multicast MAC address retrieves an interface port and slot from the
interface list specified using the Layer 2 multicast command of
mac-address-table static
command. As a result, the interface configured in static ARP is mapped with that of the L2 multicast
configuration and matched with the associated VLAN ID.
When you shut down an interface and reload a system, all ARP entries are reset and the interface FP
entry is removed. After the system comes up, no IFP entry is associated with the static NLB ARP. This
behavior occurs because the interface is in shutdown state and hence no active ARP entry is
maintained by the ARP application. Therefore, you must always associate the NLB configuration with
one of the active or enabled interfaces.
• The following note applies to the Priority-Based Flow Control section of the DCB chapter of I/O
Aggregator Configuration Guide:
On an I/O Aggregator, PFC is enabled by default with a priority value of 4 if you enable automatic
detection of DCB with PFC turned off. This behavior occurs if you perform a reload of the switch with
the dcb enable auto-detect on-next-reload command configured. The output of the show
interface
interface-type slot/port pfc details command displays the priority list as 4.
• The following note is additional information to the Configuring PFC section of the DCB chapter of all
of the platforms' Configuration Guides:
When you apply or remove a DCB input policy from an interface, one or two CRC errors are expected
to be noticed on the ingress ports for each removal or attachment of the policy. This behavior occurs
because the port is brought down when PFC is configured. When a DCB input policy with PFC profile
is configured or unconfigured on an interface or a range of interfaces not receiving any traffic,
interfaces with PFC settings and that receive appropriate PFC-enabled traffic (unicast, mixed-frame-
size traffic) display incremented values in the "CRC" and "Discards" counters. (These ingress interfaces
receiving pfc-enabled traffic have an egress interface that has a compatible PFC configuration).
• The following note applies to the CAM Profiles section of the Content Addressable Memory (CAM)
chapter of the MXL, S4810/4820T, Z9000 configuration guides:
If you define a CAM profile in which the CAM block size for IPv4 is specified as zero on a VLT peer,
duplicate multicast data packets are obtained by the receivers. This condition occurs owing to a
missing egress mask entry that is not installed in the hardware table because of the IPv4 table size
being zero.
• The following note applies to the Private VLAN Concepts section of the PVLAN chapter of all
platforms' Configuration Guides:
PVLAN uses VLAN translation tables. This mechanism does not enable movement of stations to be
detected if the shift of the station occurs in a single PVLAN domain. It is detected correctly only with a
top-of-rack (ToR) node.
274
Documentation Updates