Fabric OS Administrator's Guide v7.0.0 (53-1002148-02, June 2011)

Fabric OS Administrator’s Guide 149

53-1002148-02

Authentication policy for fabric elements

Virtual Fabric considerations: Because the device authentication policy has switch and logical

switch-based parameters, each logical switch is set when Virtual Fabrics is enabled. Authentication

is enforced based on each logical switch’s policy settings.

Configuring device authentication

1. Connect to the switch and log in using an account with admin permissions, or an account with

OM permissions for the Authentication RBAC class of commands.

2. Enter the authUtil command to set the device policy mode.

Example of setting the Device policy to passive mode:

switch:admin> authutil --policy -dev passive

Warning: Activating the authentication policy requires

DH-CHAP secrets on both switch and device. Otherwise,

the F-port will be disabled during next F-port

bring-up.

ARE YOU SURE (yes, y, no, n): [no] y

Device authentication is set to PASSIVE

AUTH policy restrictions

All fabric element authentication configurations are performed on a local switch basis.

Device authentication policy supports devices that are connected to the switch in point-to-point

manner and is visible to the entire fabric. The following are not supported:

• Public loop devices

• Single private devices

• Private loop devices

• Mixed public and private devices in loop

• NPIV devices

• FICON channels

• Configupload and download will not be supported for the following AUTH attributes: auth type,

hash type, group type.

Supported adapters

The following adapters support authentication:

• Emulex LP11000 (Tested with Storport Miniport v2.0 windows driver)

• Qlogic QLA2300 (Tested with Solaris v5.04 driver)

• Brocade Fibre Channel HBA models 415, 425, 815 and 825

• Brocade HCAs BR-1741M-k, BR-1020, and BR-1007

• BR-1860 Fabric Adapter