Informing the SAN Volume Controller of changes to host HBAs using the CLI

You can use the command-line interface (CLI) to inform the SAN Volume Controller of a change to a defined host object.

Because it is sometimes necessary to replace the HBA that connects the host to the SAN, you must inform the SAN Volume Controller of the new worldwide port names (WWPNs) that this HBA contains.

Ensure that your switch is zoned correctly.

Perform the following steps to inform the SAN Volume Controller of a change to a defined host object:

Issue the following CLI command to list the candidate HBA ports:
```
svcinfo lshbaportcandidate 
```
You should see a list of the HBA ports that are available for addition to host objects. One or more of these HBA ports should correspond with the one or more WWPNs that belong to the new HBA port.
Locate the host object that corresponds with the host in which you have replaced the HBA. The following CLI command lists all the defined host objects:
```
svcinfo lshost
```
Issue the following CLI command to list the WWPNs that are currently assigned to the host object:
```
svcinfo lshost hostobjectname
```
where hostobjectname is the name of the host object.
Issue the following CLI command to add the new ports to the existing host object:
```
svctask addhostport -hbawwpn one or more existing WWPNs
 separated by : hostobjectname/ID
```
where one or more existing WWPNs separated by : is the WWPNs that are currently assigned to the host object and hostobjectname/ID is the name or ID of the host object.
Issue the following CLI command to remove the old ports from the host object:
```
svctask rmhostport -hbawwpn one or more existing WWPNs
 separated by : hostobjectname/ID
```
where one or more existing WWPNs separated by : is the WWPNs that are currently assigned to the host object and hostobjectname/ID is the name or ID of the host object.

Any mappings that exist between the host object and the virtual disks (VDisks) are automatically applied to the new WWPNs. Therefore, the host sees the VDisks as the same SCSI LUNs as before.

See the IBM® System Storage® Multipath Subsystem Device Driver User's Guide or the documentation that is provided with your multipathing driver for additional information about dynamic reconfiguration.