Home | About | Contact

Dell 8 Release Note

Download Release note of Dell PowerEdge M1000e Desktop, Network Card for Free or View it Online on All-Guides.com. This version of Dell PowerEdge M1000e Manual compatible with such list of devices, as: PowerEdge M600, PowerEdge M610x, PowerEdge M710HD, POWEREDGE M905, PowerEdge M910

Dell PowerEdge M1000e Release note - Page 1
1
Dell PowerEdge M1000e Release note - Page 2
2
Dell PowerEdge M1000e Release note - Page 3
3
Dell PowerEdge M1000e Release note - Page 4
4
Dell PowerEdge M1000e Release note - Page 5
5
Dell PowerEdge M1000e Release note - Page 6
6
Dell PowerEdge M1000e Release note - Page 7
7
Dell PowerEdge M1000e Release note - Page 8
8
Dell PowerEdge M1000e Release note - Page 9
9
Dell PowerEdge M1000e Release note - Page 10
10
Dell PowerEdge M1000e Release note - Page 11
11
Dell PowerEdge M1000e Release note - Page 12
12
Dell PowerEdge M1000e Release note - Page 13
13
Dell PowerEdge M1000e Release note - Page 14
14
Dell PowerEdge M1000e Release note - Page 15
15
Dell PowerEdge M1000e Release note - Page 16
16
Dell PowerEdge M1000e Release note - Page 17
17
Dell PowerEdge M1000e Release note - Page 18
18
Dell PowerEdge M1000e Release note - Page 19
19
Dell PowerEdge M1000e Release note - Page 20
20
Dell PowerEdge M1000e Release note - Page 21
21
Dell PowerEdge M1000e Release note - Page 22
22
Dell PowerEdge M1000e Release note - Page 23
23
Dell PowerEdge M1000e Release note - Page 24
24
Dell PowerEdge M1000e Release note - Page 25
25
Dell PowerEdge M1000e Release note - Page 26
26
Dell PowerEdge M1000e Release note - Page 27
27
Dell PowerEdge M1000e Release note - Page 28
28
Dell PowerEdge M1000e Release note - Page 29
29
Dell PowerEdge M1000e Release note - Page 30
30
Dell PowerEdge M1000e Release note - Page 31
31
Dell PowerEdge M1000e Release note - Page 32
32
Dell PowerEdge M1000e Release note - Page 33
33
Dell PowerEdge M1000e Release note - Page 34
34
Dell PowerEdge M1000e Release note - Page 35
35
Dell PowerEdge M1000e Release note - Page 36
36
Dell PowerEdge M1000e Release note - Page 37
37
Dell PowerEdge M1000e Release note - Page 38
38
Dell PowerEdge M1000e Release note - Page 39
39
Dell PowerEdge M1000e Release note - Page 40
40
Dell PowerEdge M1000e Release note - Page 41
41
Dell PowerEdge M1000e Release note - Page 42
42
Dell PowerEdge M1000e Release note - Page 43
43
Dell PowerEdge M1000e Release note - Page 44
44
Dell PowerEdge M1000e Release note - Page 45
45
Dell PowerEdge M1000e Release note - Page 46
46
Dell PowerEdge M1000e Release note - Page 47
47
Dell PowerEdge M1000e Release note - Page 48
48
Dell PowerEdge M1000e Release note - Page 49
49
Dell PowerEdge M1000e Release note - Page 50
50
Dell PowerEdge M1000e Release note - Page 51
51
Dell PowerEdge M1000e Release note - Page 52
52
Dell PowerEdge M1000e Release note - Page 53
53
Dell PowerEdge M1000e Release note - Page 54
54
Dell PowerEdge M1000e Release note - Page 55
55
Dell PowerEdge M1000e Release note - Page 56
56
Dell PowerEdge M1000e Release note - Page 57
57
Dell PowerEdge M1000e Release note - Page 58
58
Dell PowerEdge M1000e Release note - Page 59
59
Dell PowerEdge M1000e Release note - Page 60
60
Dell PowerEdge M1000e Release note - Page 61
61
Dell PowerEdge M1000e Release note - Page 62
62
Fabric OS v6.4.1 Release Notes v1.0 Page 27 of 62
BES/FS8-18 Encryption Group. Please refer to the Encryption Admin Guide for configuration
information.
The RKM Appliance A1.6, SW v2.7 is supported. The procedure for setting up the RKM Appliance
with BES or a DCX/DCX-4S with FS8-18 blades is located in the Encryption Admin Guide.
Support for registering a 2nd RKM Appliance on BES/FS8-18 is blocked. If the RKM Appliances
are clustered, then the virtual IP address hosted by a 3rd party IP load balancer for the RKM
Cluster must be registered on BES/FS8-18 in the primary slot for Key Vault IP.
With Windows and Veritas Volume Manager/Veritas Dynamic Multipathing, when LUN sizes less
than 400MB are presented to BES for encryption, a host panic may occur and this configuration is
not supported in the FOS v6.3.1 or later release.
HCL from FOS v6.3.x to v6.4 is supported. Cryptographic operations and I/O will be disrupted but
other layer 2 traffic will not.
Relative to the BES and a DCX with FS8-18, all nodes in the Encryption Group must be at the
same firmware level of FOS v6.2 or later before starting a rekey or First Time Encryption operation.
Make sure that existing rekey or First Time Encryption operations complete before upgrading any
of the encryption products in the Encryption Group. Also, make sure that the upgrade of all nodes
in the Encryption Group completes before starting a rekey or First Time Encryption operation.
To clean up the stale rekey information for the LUN, follow one of the following two methods:
Method 1:
Method 1:Method 1:
Method 1:
1.
1.1.
1. First, modify the LUN policy from “encrypt” to “cleartext” and commit. The LUN will
become disabled.
2.
2.2.
2. Enable the LUN using “cryptocfg --enable –LUN”. Modify the LUN policy from “clear-
text” to “encrypt” with “enable_encexistingdata” to enable the first time encryption
and do commit. This will clear the stale rekey metadata on the LUN and the LUN can
be used again for encryption.
Method 2:
Method 2:Method 2:
Method 2:
1.
1.1.
1. Remove the LUN from Crypto Target Container and commit.
2.
2.2.
2. Add the LUN back to the Crypto Target Container with LUN State=”clear-text”,
policy=”encrypt” and “enable_encexistingdata” set for enabling the First Time
Encryption and commit. This will clear the stale rekey metadata on the LUN and the
LUN can be used again for encryption.
TEMS key vault support troubleshooting tips:
o Regarding TEMS key vault (KV) communication with a Brocade encryption group, the
default communication port setting for the TEMS KV is 37208, however, the Brocade
encryption members and leader use 9000 so this needs to be reset on NCKA.
Additionally, the following is a checklist of things to review if the initial attempt to connect
to the KV fails:
Check physical and logical connection via a ping on port 9000, this should be the
first check.
For the group leader node, the kac client cert and the kv cert files are to be
identical.
For group member nodes the kv file is to be the same as the kv file on the group
leader node.
Crosscheck to ensure the private key file corresponds to the kac public cert file
on any node.