Upgrade and revert cautions
If you are upgrading to this Data ONTAP release or reverting from this
release to an earlier release, you should review these issues, and if any apply
in your environment, take appropriate action.
For more information about procedures and planning, see the Data ONTAP 8.0
7-Mode Upgrade and Revert/Downgrade Guide.
v “CIFS startup might take several minutes after cluster failover giveback”
v “Change in nondisruptive upgrade procedure” on page 68
v “Upgrade process changes with Data ONTAP 7-Mode software images” on
page 69
v “iSCSI traffic not supported on e0M and e0P interfaces” on page 70
v “New FlexVol volume space requirements when upgrading from a release
earlier than Data ONTAP 7.3” on page 70
– “Determining system capacity and space guarantees before upgrading to
Data ONTAP 7.3 or later” on page 70
v “If your root FlexVol volume does not meet the new size requirements” on
page 71
v “Nondisruptive upgrades on systems with VMware ESX Server hosts” on
page 71
v “Requirements for nondisruptive upgrades on systems with deduplicated
volumes” on page 72
v “New reversion and downgrade procedures” on page 72
CIFS startup might take several minutes after cluster failover giveback
After a cluster failover giveback, the CIFS protocol might take several minutes
to start up. If vFiler units are present, they might not be initialized for the
duration of the CIFS startup time. The delay in CIFS startup is typically due
to network infrastructure issues related to domain controllers and LDAP
servers.
About this task
To ensure that the domain controllers, DNS servers, and LDAP servers are
accessible, it is recommended that you run the following tests on the partner
node for which giveback is to be initiated before initiating a giveback.
Note: If the storage system contains vFiler units, you must complete the
procedure on all vFiler units running CIFS.
Procedure
1. Test domain controller connectivity and responsiveness by entering the
following command: cifs testdc
Important cautions 67