HP 4400 HP StorageWorks Fabric OS 6.4.0c Release Notes (5697-0703, September 2 - Page 32

FC FastWrite, Native connectivity, FCAP, FICON, Additional considerations for FICON environments

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

Page 32 highlights

FC FastWrite When an FC FastWrite Initiator is moved to a port that does not have FC FastWrite enabled, I/O recovers and reverts to the slow path route (non-FC FastWrite). This change was introduced with Fabric OS 6.3. Native connectivity Fabric OS-based platforms operating in interopmode 2 or 3 should never be deployed in a fabric without at least one M-series switch. Fabric OS 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) after 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. This can occur when you power cycle the M-series switch while it was participating in a fabric with Frame Redirection zoning, a capability used for Fabric OS-based application or encryption services. If the switch is still participating in the fabric with Frame Redirection, issue the cfgsave command from a Brocade Fabric OS-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 the 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 a hafailover operation. • The pkicert (1.06) utility may cause evm errors, so each new switch should be isolated from the fabric in non-VF mode to install new certificates. FICON • For the DC SAN Backbone Director, FICON is not allowed with a 48-port blade in the Default Logical Switch. All ports on a 48-port blade must be assigned to a user-defined Logical Switch to use them in a FICON enabled switch. • The DC04 SAN Director is not supported for FICON Cascading in interopmode 2 or 3 for use in mixed fabrics with M-EOS platforms. NOTE: For information about specific versions of Fabric OS support for FICON, see the B-series FICON Connectivity Stream. Additional considerations for FICON environments This section provides supplemental information for users deploying Fabric OS-based platforms in FICON environments: • The HP StorageWorks DC04 SAN Director is supported for FICON only in Brocade Native Mode (interopmode 0), and therefore is not supported for interoperability with M-EOS platforms. 32

  • 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
FC FastWrite
When an FC FastWrite Initiator is moved to a port that does not have FC FastWrite enabled, I/O
recovers and reverts to the slow path route (non-FC FastWrite). This change was introduced with
Fabric OS 6.3.
Native connectivity
Fabric OS-based platforms operating in interopmode 2 or 3 should never be deployed in a fabric
without at least one M-series switch. Fabric OS 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) after 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
. This can occur when you power cycle the M-series switch
while it was participating in a fabric with Frame Redirection zoning, a capability used for Fabric
OS-based application or encryption services. If the switch is still participating in the fabric with Frame
Redirection, issue the
cfgsave
command from a Brocade Fabric OS-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 the
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 a
hafailover
operation.
•
The pkicert (1.06) utility may cause
evm
errors, so each new switch should be isolated from the
fabric in non-VF mode to install new certificates.
FICON
•
For the DC SAN Backbone Director, FICON is not allowed with a 48-port blade in the Default
Logical Switch. All ports on a 48
–
port blade must be assigned to a user-defined Logical Switch
to use them in a FICON enabled switch.
•
The DC04 SAN Director is not supported for FICON Cascading in interopmode 2 or 3 for use in
mixed fabrics with M-EOS platforms.
NOTE:
For information about specific versions of Fabric OS support for FICON, see the B-series FICON
Connectivity Stream.
Additional considerations for FICON environments
This section provides supplemental information for users deploying Fabric OS-based platforms in
FICON environments:
•
The HP StorageWorks DC04 SAN Director is supported for FICON only in Brocade Native Mode
(interopmode 0), and therefore is not supported for interoperability with M-EOS platforms.
32