Dell 8 Release Note

Download Release note of Dell PowerEdge M1000e Chassis, Computer Hardware for Free or View it Online on All-Guides.com. This version of Dell PowerEdge M1000e Manual compatible with such list of devices, as: 8, PowerEdge M600, PowerEdge M610, PowerEdge M710HD, 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 30 of 62
Integrated Routing
To allow Hot Code Load on a Brocade 5100 when using Integrated Routing, the edge switch
connected to the 5100 must be running Fabric OS v6.1 or later code.
Integrated Routing EX_Ports are only supported in the base switch on a switch with VF enabled.
Integrated Routing and TopTalkers (Fabric Mode) are not concurrently supported. To use
Integrated Routing, be sure to disable Fabric Mode TopTalkers prior to configuring EX_Ports first.
Native Connectivity
FOS-based platforms operating in interopmodes 2 or 3 should never be deployed in a fabric
without at least one M-series switch. FOS switches in interopmode 3 (McDATA Open Fabric Mode)
do not support configuration of zoning without an M-series switch in the fabric. When migrating
from M-series to B-series switches, all B-series switches should be configured to interopmode 0
(Brocade Native mode) once the last M-series switch has been removed from the fabric.
M-EOSc switches may exhibit a behavior where they block all attached devices with a reason
indication of “Blocked Temporarily, Internal”. Users that experience this may have power cycled
the M-series switch while it was participating in a fabric with Frame Redirection zoning, a
capability used for FOS-based application or encryption services . If the switch is still participating
in the fabric with Frame Redirection, issue the “cfgsave” command from a Brocade FOS-based
switch with the Frame Redirection zone in its defined zone database. If the M-EOS switch is no
longer attached to the fabric with Frame Redirection zoning, issue the
“Config.Zoning.deleteSplZoneSet” command via CLI to the M-EOS switch.
FCAP
If VF is enabled on a switch, HTTPS and FCAP certificates should always be imported in the Default
Switch. Certificates imported in a non-Default Switch will not be available after hafailover
operation.
The pkicert (1.06) utility may cause evm errors, so each new switch should be isolated from the
fabric and placed in non-vf mode to install new certificates.
FICON
Refer to Appendix: Additional Considerations for FICON Environments for details and notes for
deployment in FICON environments
.
FL_Port (Loop) Support
The FC8-48 and FC8-64 blade support attachment of loop devices in the DCX and DCX-4S.
Virtual Fabrics must be enabled on the chassis and loop devices may only be attached to ports on
a 48-port or 64-port blade assigned to a non-Default Logical Switch operating with the default 10-
bit addressing mode (they may not be in the default Logical Switch).
A maximum of 144 ports may be used for connectivity to loop devices in a single Logical Switch
within a chassis in 10-bit dynamic area mode on DCX-4S.
A maximum of 112 ports may be used for connectivity to loop devices in a single Logical Switch
within a chassis in 10-bit dynamic area mode on DCX.
Loop devices continue to be supported when attached to ports on the FC8-16, FC8-32, FC4-16
and FC4-32 blades with no new restrictions
.
Port Mirroring
On the Brocade 5300, the port mirroring feature has a limitation where all port mirror resources
must stay within the same ASIC port group. The resources are the configure mirror port, Source
Device, and Destination Device or ISL, if the Destination Device is located on another switch. The