san_host ‑add

Creates a SAN host entry on the Oracle FS System.

SYNOPSIS

san_host ‑add 
   ‑name sanhost‑name
   [{‑hpuxCompatibility | ‑noHpuxCompatibility}]
   [{‑iscsiAccessControl | ‑noIscsiAccessControl}
    { ‑iscsiAuthentication
      ‑chapName chap‑name
    | ‑noIscsiAuthentication
    }]
   [‑fcInitiatorPort fcinitiatorport‑wwn[/fcinitiatorport‑alias]
                     [, fcinitiatorport‑wwn[/fcinitiatorport‑alias] ]... ]
   [‑iscsiInitiatorPort iscsi‑initiator‑name[/iscsi‑initiatorport‑alias]
                     [, iscsi‑initiator‑name[/iscsi‑initiatorport‑alias] ]...  ]
   [{‑reconcileMappings | ‑noReconcileMappings}]
   [‑associateGroup host‑group‑id‑or‑fqn]

   [{‑sessionKey | ‑u admin‑user ‑oracleFS oracle‑fs‑system}]
   [{‑outputformat | ‑o} { text | xml }]
   [{‑timeout timeout‑in‑seconds | ‑verify | ‑usage | ‑example | ‑help}]

DESCRIPTION

Use the san_host ‑add command to create an associated host entry by associating one or more initiators on a host to a named host entry. An initiator is the World Wide Name (WWN) of an FC HBA port or the name of an iSCSI initiator. When you create a host entry, you can configure authentication between the iSCSI Controller ports and the hosts.

For systems that use the HP-UX operating system, you can set an option to use the HP-UX LUN numbering scheme. You can optionally specify that the system reconcile any future conflicts with existing host LUN mappings.

If the host is running Oracle FS Path Manager (FSPM) then FSPM automatically creates a host entry for the host when FSPM first connects to the Pilot on theOracle FS System. For host systems that use FSPM, you might not need to use the san_host ‑add command. Refer to the Oracle FS Path Manager Installation Guide for details on how to add FSPM host entries on the Oracle FS System.

Note: Only administrators with primary administrator, admin1, or admin2 roles are authorized to run the san_host ‑add command.

OPTIONS

‑associateGroup

Specifies the ID or the fully qualified name (FQN) of the host group with which to associate the SAN host.

‑chapName

Identifies the CHAP name to use during iSCSI authentication.

Note: The system prompts you twice for the CHAP secret. The second prompt ensures the correctness of the secret.

‑fcInitiatorPort

Specifies the Fibre Channel (FC) HBA ports on the SAN host that can connect to the Oracle FS System. The system recognizes the following two formats for specifying HBA ports:

Required: 16 hexadecimal digits that are separated by colons, as in xx:xx:xx:xx:xx:xx:xx:xx, where each xx is a hexadecimal number.
Note: The colons are optional.
Optional: an alias for the port consisting of a slash character ( / ) that is followed by the text of the alias.

‑hpuxCompatibility

Identifies the host as using the HP-UX addressing mode for LUNs.

‑iscsiAccessControl

Enables access control for an iSCSI session.

‑iscsiAuthentication

Enables the Challenge Handshake Authentication Protocol (CHAP) authentication to restrict access to the Oracle FS System from the host.

The ‑iscsiAuthentication option is valid only when the ‑iscsiAccessControl option is also specified.
If the ‑iscsiAuthentication option is omitted and the ‑iscsiAccessControl option is specified, SAN hosts do not need to provide CHAP names and passwords when accessing the Oracle FS System.

‑iscsiInitiatorPort

Specifies one or more iSCSI initiator names that are used by the SAN host. Each iSCSI initiator name should be specified as the name that is configured on the SAN host and optionally followed by a slash character ( / ) and an alias for the name.

‑name

Specifies the name of a SAN host entry that you are creating on the Oracle FS System. After the Oracle FS System updates the internal host table, the name that you provide is used to create the fully qualified name (FQN). Use double quotation marks around names containing spaces or dashes to ensure that the Oracle FS CLI software that is running on the Pilot includes the spaces or dashes in the name; otherwise, the software will generate a parsing error.

‑noHpuxCompatibility

Disables the HP-UX LUN addressing mode for the SAN host.

‑noIscsiAccessControl

Disables access control for iSCSI. When you disable iSCSI access control, all of the required CHAP authentication options are also disabled. If you want to re-enable iSCSI access control in the future, you will need to specify a new CHAP name and password.

‑noIscsiAuthentication

Disables authentication that is based on the Challenge Handshake Authentication Protocol (CHAP). This property applies to iSCSI hosts that attempt to access the Oracle FS System.

‑noReconcileMappings

Disables the automatic fixing of any LUN mappings for this host that cause mapping conflicts.

‑reconcileMappings

Specifies that any subsequent LUN mappings for this host that cause a conflict are automatically fixed. If this option is omitted, ‑noReconcileMappings is the default.

EXAMPLE

Task

Create a SAN Host entry on the Oracle FS System.

Parameters

The name of a SAN host entry: sanhost_1
The Fibre Channel (FC) HBA port on the SAN host that can connect to the Oracle FS System: 2001000B08000520/fcport-alias_1

$ fscli san_host ‑add ‑name sanhost_1 ‑fcInitiatorPort 2001000B08000520/⁠fcport-alias_1