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: PowerEdge M600, PowerEdge M605, PowerEdge M610, PowerEdge M710, 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 29 of 62
Users who want to utilize Access Gateway’s Device-based mapping feature in the ESX
environments are encouraged to refer to the SAN TechNote GA-TN-276-00 for best
implementation practices. Please follow these instructions to access this technote:
o Log in to http://my.brocade.com
o Go to Documentation > Tech Notes.
o Look for the Tech Note on Access Gateway Device-Based Mapping in VMware ESX Server.
Bottleneck Detection
Due to memory constraints, when using Bottleneck Detection on the Brocade 48000, a maximum
of 100 ports should be configured and enabled for monitoring at any time.
FCR
IPFC over FCR is now disabled by default. Switches that are upgraded to FOS v6.3 will retain their
configuration settings for IPFC over FCR. The change to the default configuration only applies to
new units shipping with FOS v6.3 or units running v6.3 that are reset to a default configuration.
Use fcrbcast - - enable to explicitly enable IPFC over FCR.
Broadcast frame forwarding is not supported in an FCR fabric with a Brocade 8000. By default,
broadcast frame forwarding is disabled on the FC router. If your edge fabric includes a Brocade
8000, do not enable broadcast frame forwarding on the FC router because this can degrade FCR
performance when there is excessive broadcast traffic.
With FC8 blades, the switch must be disabled to change the backbone fabric ID.
With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the IDs
unique.
When using FC Routing in a backbone to edge configuration with an Mi10K in the edge fabric,
users may experience slow throughput for hosts attached to the Mi10K. Users may encounter
this following a bounced IFL connection between the backbone and edge fabric. This slowdown
can be resolved by disabling/enabling the Mi10K ports for the hosts that are impacted.
Mi10K Directors operating with firmware prior to M-EOSn v9.9.5 may experience repeated system
faults when attached as an FCR edge switch to a Brocade 7800 EX Port. To avoid this, ensure
that the Mi10K is operating with M-EOSn v9.9.5 or later when in an edge fabric that will be
attached to a Brocade 7800 FCR Backbone.
VEX edge to VEX edge device sharing will not be supported.
FC FastWrite
When an FC FastWrite Initiator is moved to a port that doesn't have FC FastWrite enabled, I/O will
recover and revert to the slow path route (non FC FastWrite). This is a behavioral change from
FOS v6.2.x.
Traffic Isolation over FCR
All switches and Fibre Channel Routers both in edge and backbone fabrics must be running FOS
v6.1.0 or later in order to support this feature.
In order for Traffic Isolation over FCR to function properly, the associated TI zones in each fabric
(both edge fabrics and backbone fabric) need to have failover ENABLED.
TI over FCR is only supported in edge-to-edge configurations. There is no support for TI in
backbone to edge routing configurations.