![HP Fabric OS v7.0.1 Administrator'S Manual Download Page 372](http://html.mh-extra.com/html/hp/fabric-os-v7-0-1/fabric-os-v7-0-1_administrators-manual_165056372.webp)
334
Fabric OS Administrator’s Guide
53-1002446-01
Configuration upload and download considerations for FA-PWWN
16
Configuration upload and download considerations for FA-PWWN
The configuration upload and download utilities can be used to import and export the FA-PWWN
configuration.
ATTENTION
Brocade recommends you delete all FA-PWWNs from the switch with the configuration being
replaced before you upload or download a modified configuration. This is to ensure no duplicate
FA-PWWNs in the fabric.
Firmware upgrade and downgrade considerations for FA-PWWN
Firmware downgrade is blocked if the FA-PWWN feature is enabled on the switch. All FA-PWWN
configurations are lost if firmware is downgraded, followed by an upgrade back to Fabric OS v7.0.0.
This is done to ensure that the FA-PWWN configurations are not tampered with when the switch is
running an earlier version of the firmware.
You must also consider zone configuration, security configuration, and target ACLs when
downgrading from Fabric OS 7.0.0. If any of these (zone configuration, security configuration, and
target ACLs) have FA-PWWNs configured, the SAN network may not function properly, or at all.
Security considerations for FA-PWWN
The FA-PWWN feature can be enabled only by authorized administrators. Thus, existing user-level
authentication and authorization mechanisms should be used to ensure only authorized users can
configure this feature.
If you are concerned about security for FA-PWWN, you should configure device authentication. You
can use authentication at the device level to ensure security between the switch and the server.
Refer to
“Device authentication policy”
on page 146 for information about configuring device
authentication.
You can also use the Device Connection Control (DCC) policy to ensure that only an authorized
physical server can connect to a specific switch port.
NOTE
When creating the DCC policy, use the physical device WWN and not the FA-PWWN.
If you use DCC, a policy check is done on the physical PWWN on the servers. In the case of an HBA,
the FA-PWWN is assigned to the HBA only
after
the DCC check is successful.
Refer to
“DCC policy behavior with Fabric-Assigned PWWNs”
on page 141 for additional
information.
Summary of Contents for Fabric OS v7.0.1
Page 1: ...53 1002446 01 15 December 2011 Fabric OS Administrator s Guide Supporting Fabric OS v7 0 1 ...
Page 22: ...xxii Fabric OS Administrator s Guide 53 1002446 01 ...
Page 26: ...xxvi Fabric OS Administrator s Guide 53 1002446 01 ...
Page 30: ...xxx Fabric OS Administrator s Guide 53 1002446 01 ...
Page 38: ...xl Fabric OS Administrator s Guide 53 1002446 01 ...
Page 40: ...2 Fabric OS Administrator s Guide 53 1002446 01 ...
Page 214: ...176 Fabric OS Administrator s Guide 53 1002446 01 Management interface security 7 ...
Page 228: ...190 Fabric OS Administrator s Guide 53 1002446 01 Brocade configuration form 8 ...
Page 248: ...210 Fabric OS Administrator s Guide 53 1002446 01 Validating a firmware download 9 ...
Page 334: ...296 Fabric OS Administrator s Guide 53 1002446 01 Setting up TI over FCR sample procedure 12 ...
Page 360: ...322 Fabric OS Administrator s Guide 53 1002446 01 Encryption and compression example 14 ...
Page 404: ...366 Fabric OS Administrator s Guide 53 1002446 01 ...
Page 430: ...392 Fabric OS Administrator s Guide 53 1002446 01 Ports on Demand 18 ...
Page 502: ...464 Fabric OS Administrator s Guide 53 1002446 01 Buffer credit recovery 23 ...
Page 572: ...534 Fabric OS Administrator s Guide 53 1002446 01 Hexadecimal overview D ...
Page 584: ...546 Fabric OS Administrator s Guide 53 1002446 01 ...