User guide

DataDirect Networks SFA™ OS 2.2.1.3 Release Notes Revision A1 | 10
o If the ULA field has the value "0000000000000000", continue to wait and
not issue any CLI commands besides "SHOW CONTROLLER".
Below is an example output of the condition where you would want to wait:
$ show controller
*************************
* Controller(s) *
*************************
| Up Time | |Encl| |
…
Idx|Name |Mastership|Locality| D: H: M: S|RP| ID |Idx | ULA |
…
-----------------------------------------------------------------------------------------------
…
0 A PRIMARY LOCAL 0000:20:24:34 1 0001ff0900180000 0 00000001ff0800ac
…
1 B SECONDARY REMOTE 0000:00:00:05 1 0001ff09002d0000 0 0000000000000000
…
Total Controllers: 2
o When the ULA number has something other than all zeros for the remote
controller, it is now safe to issue CLI commands and avoid the
communication problems.
• There is an issue when enabling DIRECTPROTECT of DATA_INTEGRITY_FIELD for
a pool that is already doing an initialization.
When DATA_INTEGRITY_FIELD is enabled after an initialization has already started,
that initialization is stopped and restarted from the beginning as a Non-Destructive
Initialization to fill in the DATA_INTEGRITY_FIELD blocks. If, for any reason other
than a shutdown, the master controller were to restart during the transition from a
DIRECTPROTECT of non-DATA_INTEGRITY_FIELD to DATA_INTEGRITY_FIELD
the Initialization fence may not get set back to zero. If this were to happen the Non-
Destructive Initialization would not properly fill out the DATA_INTEGRITY_FIELD
blocks below the previous Initialization fence. This is a very small window while the
controller is in the process of transitioning to the new DIRECTPROTECT value.
Work Arounds:
o When creating the pool, specify the DIRECTPROTECT value on the
command line itself. CREATE POOL [options needed]
DIRECTPROTECT=DATA_INTEGRITY_FIELD.
o Wait for the original initialization to complete prior to setting
DIRECTPROTECT to DATA_INTEGRITY_FIELD.
[DE14609]
5.2 SFA12KXE and SFA12K-20E
• On E-platforms, downgrading SFA OS 2.2.0 to earlier SFA OS versions is not
supported if there are more than 128 VDs presented to any stack.
• If Installing Older DDN Solutions on SFA12K-20E, Potential Network Ordering Issues
May Arise.