HP 1606 HP B-series Fabric OS 6.4.1b Release Notes (5697-0886, March 2011-incl - Page 29

Bottleneck detection, FCR backbone fabric ID changes, Traffic Isolation over FCR - reset network settings

Get HP 1606 PDF manuals and user guides View all HP 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

VMware ESX Server Environments for best implementation practices. This document can be downloaded from the following HP website: http://www.hp.com/support/manuals Under storage, select Storage networking, and then select the appropriate switch under B-series Switches. Bottleneck detection Due to memory constraints, when using Bottleneck Detection on the 4/256 SAN Director, a maximum of 100 ports should be configured and enabled for monitoring at any time. FCR backbone fabric ID changes • With 8Gb director 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. Traffic Isolation over FCR • All switches and Fibre Channel routers, both in edge and backbone fabrics, must be running Fabric OS 6.1.0 or later in order to support this feature. • In order for TI over FCR to function properly, the associated TI zones in each fabric (edge and backbone) must have failover enabled. • TI over FCR is supported only in edge-to-edge configurations. There is no support for TI in backbone-to-edge routing configurations. IP over Fibre Channel (IPFC)/FCR IPFC over FCR is now disabled by default. Switches that are upgraded to Fabric OS 6.3.x or later retain their configuration settings for IPFC over FCR. The change to the default configuration applies only to new units shipping with Fabric OS 6.3.1a or later or units running Fabric OS 6.3.x that are reset to a default configuration. Use fcrbcast --enable to explicitly enable IPFC over FCR. Broadcast frame forwarding in FCR fabric Broadcast frame forwarding is not supported in an FCR fabric with a 2408 FCoE Converged Network Switch. By default, broadcast frame forwarding is disabled on the FC router. If your edge fabric includes a 2408 FCoE Converged Network Switch, do not enable broadcast frame forwarding on the FC router, which can degrade FCR performance when there is excessive broadcast traffic. FC Routing with Mi10K Using FC routing in a backbone-to-edge configuration with an Mi10k in the edge fabric can result in slow throughput for hosts attached to the Mi10K following a bounced IFL connection between the backbone and edge fabric. To resolve this slowdown, disable and then re-enable the Mi10K ports for the affected hosts. Mi10k directors operating with firmware earlier than MEOS 9.9.5 may experience repeated system faults when attached as an FCR edge switch to a 1606 Extension SAN Switch EX_Port. To avoid this, ensure that the Mi10k is operating with MEOS 9.9.5 or later for this configuration. Important notes and recommendations 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
VMware ESX Server Environments
for best implementation practices. This document can be
downloaded from the following HP website:
h
t
tp://w
w
w
.hp
.co
m/su
ppo
r
t/man
uals
Under
storage
, select
Storage networking
, and then select the appropriate switch under
B-series
Switches
.
Bottleneck detection
Due to memory constraints, when using Bottleneck Detection on the 4/256 SAN Director, a
maximum of 100 ports should be configured and enabled for monitoring at any time.
FCR backbone fabric ID changes
•
With 8Gb director 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.
Traffic Isolation over FCR
•
All switches and Fibre Channel routers, both in edge and backbone fabrics, must be running
Fabric OS 6.1.0 or later in order to support this feature.
•
In order for TI over FCR to function properly, the associated TI zones in each fabric (edge and
backbone) must have failover enabled.
•
TI over FCR is supported only in edge-to-edge configurations. There is no support for TI in
backbone-to-edge routing configurations.
IP over Fibre Channel (IPFC)/FCR
IPFC over FCR is now disabled by default. Switches that are upgraded to Fabric OS 6.3.x or later
retain their configuration settings for IPFC over FCR. The change to the default configuration applies
only to new units shipping with Fabric OS 6.3.1a or later or units running Fabric OS 6.3.x that
are reset to a default configuration. Use
fcrbcast
––
enable
to explicitly enable IPFC over
FCR.
Broadcast frame forwarding in FCR fabric
Broadcast frame forwarding is not supported in an FCR fabric with a 2408 FCoE Converged
Network Switch. By default, broadcast frame forwarding is disabled on the FC router. If your edge
fabric includes a 2408 FCoE Converged Network Switch, do not enable broadcast frame forwarding
on the FC router, which can degrade FCR performance when there is excessive broadcast traffic.
FC Routing with Mi10K
Using FC routing in a backbone-to-edge configuration with an Mi10k in the edge fabric can result
in slow throughput for hosts attached to the Mi10K following a bounced IFL connection between
the backbone and edge fabric. To resolve this slowdown, disable and then re-enable the Mi10K
ports for the affected hosts. Mi10k directors operating with firmware earlier than MEOS 9.9.5
may experience repeated system faults when attached as an FCR edge switch to a 1606 Extension
SAN Switch EX_Port. To avoid this, ensure that the Mi10k is operating with MEOS 9.9.5 or later
for this configuration.
Important notes and recommendations
29