Networking And Security Protocols Enhancements; Ability To Block Data Traffic On The E0M Interface - IBM N Series Manual

Networking and Security protocols enhancements

This Data ONTAP release includes a number of new features and
enhancements for networking and security protocol enhancements. This
section provides an overview of these features and enhancements.
For more information about these features, see the Data ONTAP 8.0 7-Mode
Network Management Guide.
v "Ability to block data traffic on the e0M interface"
v "Support for the SMB 2.0 protocol" on page 35
v "Support for CDP" on page 35
v "Port-based load-balancing option for multimode interface groups" on page
35
v "TSO in NICs" on page 35
v "64-bit SNMP object identifiers (OIDs) are supported" on page 36
v "Configuration for receiving untagged traffic on VLAN tagged interfaces"
on page 36
v "Vifs are now known as interface groups" on page 36

Ability to block data traffic on the e0M interface

In Data ONTAP 8.0.2 and later releases, you can block certain types of traffic
from the e0M interface, including SnapMirror transfers, SnapVault transfers,
and data transfers that use the CIFS, NFS, and NDMP protocols. This feature
enables you to optimize system performance.
Data ONTAP 8.0.2 introduces a new option
interface.blocked.mgmt_data_traffic to control the blocking of data transfer
on the e0M interface. New systems that ship with Data ONTAP 8.0.2 and later
releases have the default value of this option set to on, which prevents data
transfer on the e0M interface. Systems upgraded to Data ONTAP 8.0.2, 7.3.6,
and later releases have the default value of the option set to off, which allows
data transfer on the e0M interface.
Note: Data transfers that use the iSCSI protocol are always blocked on
systems upgraded to Data ONTAP 8.0 and later. The data transfers are not
affected by the option interface.blocked.mgmt_data_traffic option setting.
The e0M port is a low-bandwidth interface that should be used only for
management traffic that uses SSH and other management protocols.
Configuring e0M to serve data traffic can cause performance degradation and
routing problems. Therefore, e0M should be configured on a dedicated
management LAN or it should be configured down. If an e0M interface is
serving management traffic, it should be partnered with another e0M
interface.
34
IBM System Storage N series: Data ONTAP 8.0.4 7-Mode Release Notes