Technical data

Page 18
• A SPAN destination port cannot be a profiled port.
• All AMPP features that were supported only on a physical interface on NOS v2.0 are now
supported on a VLAG in NOS v2.1, with the exception of FCoE sub-profile, which is not supported
in LAG/VLAG mode.
• While migrating from a legacy AMPP environment to VM Aware Network Automation, it is
recommend that you delete all manually created port profiles to facilitate smooth migration.
Security, ACLs, Authentication, Authorization
• ACLs are not supported for egress traffic flows.
• Configuring TACACS+ or RADIUS without a key is not supported. If no key is configured, the switch
uses a default key of “sharedsecret.”
• There is a possibility that locked user accounts will get unlocked after a reboot if the running-
config (before reboot) is different from the startup-config of user accounts.
• Encrypted text (taken from running-config of any user account password with encryption turned
on) should not be used as input for a clear-text password for the same user. This may result in
subsequent login failure of the user.
• There is no upper limit for the number of rules that can be added to a management access-list.
However, when the ACL is applied to a management interface, only the top 256 rules will be
applied if the ACL contains more than 256 rules.
• Access to ONLY the following Active Directory (AD) servers is supported by Brocade LDAP client:
o Windows 2000
o Windows 2003
o Windows 2008 AD
Virtual IP Address Support
• A Virtual IP address cannot be configured on a standalone node in VCS mode.
• A separate gateway cannot be configured for a Virtual IP address. The default gateway will be the
same as the gateway address for the management port of this switch.
• There is no Virtual MAC address associated with the Virtual IP address.
• For Virtual IP address to work correctly, the IPv4 address of the management port should be
assigned and functional.
Miscellaneous
• Brocade VDX switches load balance internal and external traffic based on hash functions using
standard network headers as keys. Due to this implementation, you may experience a traffic
imbalance depending on the application flow definition.
• Packet drops will be seen for a short duration due to routing changes with link flaps and/or node
failovers.
• Priority 7 is reserved for control traffic on VDX switches. User data traffic should use priorities 0
through 6.
• Brocade VDX architecture prioritizes unicast traffic over Broadcast or multicast traffic under port
congestion.
• System verification or diagnostics performed on a switch will require a reboot.
• Flow control is disabled by default on all interfaces.
• Configuration of more than one in-band management port on a single switch is not recommended.
• Even though the IGMP snooping feature is supported over VLAG, all multicast data traffic will be
forwarded only over the primary.