Follow these instructions if you add, remove, or replace a SAN initiator identifier in the host.
Changes to Fibre Channel (FC) HBAs installed in the host, and changes to iSCSI initiator names used by the host, effect how the Oracle FS System recognizes connections from the host. When the SAN initiators used by the host are changed, the Oracle FS System definition of the host must be updated to match, and any LUN mappings to the host must be adjusted. Oracle FS Path Manager (FSPM) does most of this automatically when you follow these steps.
- Make the changes to the configuration.
FSPM tries to ensure that the changes are automatically passed to the
Oracle FS System when the
FSPM daemon is restarted.
If you replaced all the FC HBAs in the host, you must make a LUN on the Oracle FS System system visible to at least one of the new ports on the host. This LUN can be unmapped or mapped to one of the host ports. If you map the LUN to one of the ports, it maps to all ports on the host after the FSPM daemon is restarted. If you decide that this LUN is temporary, delete it after you restart the daemon.
- Choose one of:
- Reboot the host as part of reconfiguring the HBAs and after setting up the mapping described earlier, if necessary.
No further action is needed.
- Do not reboot the host as part of the reconfiguration (for example, if you use a “hot plug” method to change HBAs).
Restart the FSPM software after the reconfiguration is completed and after setting up the mapping described earlier, if necessary. To restart the FSPM, review the information on starting and stopping the FSPM software as described in this document.
The FSPM daemon discovers the change when it starts up after the system reboot or after being explicitly restarted. The FSPM daemon updates the Oracle FS System management software. The LUN mappings to the host are automatically adjusted to match the new SAN connections from the host.