Addendum

does not occur if there is no Ethernet traffic and only FCoE traffic is present, or if DCB remains
disabled on the ToR switch.
• The following note applies to the Protocol Separation section of the EIS chapter of the addendum
document:
If you configure a source interface is for any EIS management application, EIS might not coexist with
that interface and the behavior is undefined in such a case. You can configure the source interface for
the following applications: FTP, ICMP (ping and traceroute utilites), NTP, RADIUS, TACACS, Telnet,
TFTP, syslog, and SNMP traps. Out of these applications, EIS can coexist with syslog and SNMP traps
only because these applications do not require a response after a packet is sent.
• The following note applies to the Config Storm Control section of Storm Control chapter of the
S6000 Configuration Guide:
When both rate policing and storm control are configured, packets are dropped and are not sent out
of the egress interface. Rate policing and storm control are mutually exclusive operations; you can
configure only one of the two functionalities at a point in time. You can configure storm control at
interface level or globally and it is restricted against the presence of the per-interface-level rate-
police or the policy-level rate-police setting.
• The following note applies to to the VLT Nodes in PVLANs section of the addendum document: ARP
entries are synchronized even when a mismatch occurs in the PVLAN mode of a VLT LAG. PR 128799
• The following note applies to the Post Configuration Script - BMP Mode section of the Configuring
BMP chapter of the Open Automation Guide:
Because the rstimer utility supports only the minute-level precision, the rstimer utility cannot be used
for the first time after the ninth minute of the execution of the script. As a result, you cannot extend
the preconfig or postconfig timer during the last minute of expiration of the timer.
• The following note applies to the Specifying an Auto-Failover Limit section of the High Availability
(HA) chapter of the S4810 and S4820T Configuration Guides:
Recovering the Switch When Auto-Failover Limit is Exceeded
When the auto-failover limit is exceeded, the switches become disabled. In such a state, you must
reboot the switches to be able to access the device again because you cannot use the preconfigured
user credentials to log in to the device until it is reset. You must use the reload command to reboot
the switches, including the management unit and the stack unit when the auto-failover limit is
exceeded.
276
Documentation Updates