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 M1000e, PowerEdge M605, PowerEdge M610, PowerEdge M710HD, POWEREDGE M905

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 32 of 62
A switch running FOS v6.4 in InteropMode 0 (Brocade Native Mode) cannot connect to an EX_Port
on an AP7420. A switch running FOS v6.4 in InteropMode 2 or InteropMode 3 can be connected
to EX ports on an AP7420.
Extended Fabrics and R_RDY Flow Control
Beginning with Fabric OS v5.1, Brocade supported the Extended Fabrics feature in conjunction with
R_RDY flow control (R_RDY flow control mode can be enabled via portCfgISLMode command). R_RDY
flow control mode that uses IDLE primitives does not support Brocade frame-based Trunking for
devices such as Time Division Multiplexor (TDM.) In order to overcome this limitation and provide
support for frame-based Trunking with Extended Fabrics, Fabric OS v6.2.0 and later has been
enhanced to support interoperability with these distance extension devices.
Fabric OS v6.3.1 allows Extended Fabrics E_Ports to operate in VC_RDY mode using either ARB or
IDLE primitives as fill words. This allows frame-based Trunking to be supported on Extended Fabrics E-
ports even when IDLE primitives are configured for these ports when operating in native VC_RDY
mode. Prior to this change, frame-based Trunking was supported only when ARB primitives were used
in VC_RDY mode. With Fabric OS v6.2 or later, frame-based Trunking is supported on Extended
Fabrics E_Ports regardless of whether IDLE or ARB primitives are used when operating in native
VC_RDY mode.
Implementation
The portcfglongdistance CLI parameter “VC Translation Link Init” is now overloaded to specify if the
long distance link should use IDLE or ARB primitives. By default, vc_init is enabled. If vc_init is
enabled, the long distance link will use ARB primitives. If vc_init is disabled, the link will use IDLE
primitives.
Note:
Buffer to Buffer Credit Recovery feature is not supported on Extended Fabrics E_Port when it is
configured to use IDLE primitives. The user must disable buffer to buffer credit recovery feature using
the command portcfgcreditrecovery and specifying the disable option; otherwise, the link will
continuously reset.
The Adaptive Networking SID/DID Traffic Prioritization QoS feature is not supported on Extended
Fabrics E_Ports when IDLE primitives are configured on these ports. This is because in this mode only
data Virtual Channels are available while QoS related virtual channels are not available.
When connecting to an extension device that does not support ARB primitives (such as some TDM
products), the following configuration must be used:
portcfgqos -disable <port>
portcfgcreditrecovery –disable <port>
portCfgLongDistance <port> <LD|LD> 0 <distance>
The fabric parameter “fabric.ops.mode.longdistance” is now deprecated and should not be used.
Miscellaneous.
When ports on a 5470 embedded switch are configured for 8G, Emulex HBAs may not
login in time and cause boot over SAN failures. Setting the port to auto-negotiate allows
these HBAs to log in correctly at 8G.
POST diagnostics for the Brocade 5100 have been modified beginning with FOS v6.3.1b
and v6.4.0 to eliminate an “INIT NOT DONE” error at the end of an ASIC diagnostic port
loopback test. This modification addresses BL-1020 Initialization errors encountered
during the POST portloopbacktest. (Defect 263200)
It is recommended that no more the 50 F_Port Top Talkers be enabled on a 48000
director in a large fabric (>4000 devices).