Technical data

Page 17
Important Notes
This section contains information that you should consider before you use this Network OS release.
This information is derived from NOS 2.1.1 release notes.
Command Line Interface (CLI)
• Some commands will not produce paginated output.
• For certain commands (including the no form with some commands), “?” will show unsupported
additional options.
• Tab completion and <ctrl>-c (cancel) does not work for some commands.
• For some commands, “switchId” and “all” options are not applicable in this NOS release but are
still shown as options. These will be applicable and supported in future NOS releases.
• Some CLI commands will generate an “Error:Access denied” message upon failure. This means
the operation failed on the switch and may not be related to permissions.
• The no command always exists for all roles, even if it is not required.
• Some no commands will execute without mandatory parameters that were originally used for
configuration.
• Some no commands may produce an incorrect error message upon error.
• An incorrect range might be displayed in the help text for some of the show commands.
MAC Learning Considerations in VCS
• The clear mac-address-table command has been enhanced to support clearing of the mac
addresses associated with vLAGs. This command can be used to sync mac address tables of the
VCS member switches.
Trunking
• Brocade trunk (BTRUNK) has a maximum throughput of 80 Mbps. Full link utilization of 8 ports in
a trunk group is achievable with larger packet size (>128 bytes).
Span
• CPU-originated packets cannot be output spanned on the VDX 2730.
• Span is supported only within a port group on the VDX 2730.
• A port cannot be spanned to multiple locations in the same direction.
• Only one port per port group can be configured as a destination port for ingress spanning.
• Only one port per port group can be configured as a destination port for egress spanning.
• An ISL port cannot be a source or destination SPAN port.
• Inter-chip port spanning is not allowed.
• Spanning of a LAG port is not supported. To span a LAG, you should individually enable spanning
on all the member ports of the LAG.
• A profiled port cannot be a span destination.
AMPP and Port Profiles
• Port profile status does not reflect the remote interface information in VCS fabric mode.
• AMPP is recommended to be enabled on ports in which end-hosts are directly connected to the
VDX 2730 cluster.
• Native VLAN support inside AMPP does not honor the global enable or disable flag.