Following are the prerequisites to create a
Pilot image on the replacement SAS HDD if the software version of the Oracle FS system is below 6.2.5.
-
Enable secure shell (SSH) on the active Pilot and log in to the active Pilot.
-
HTTP and DHCP servers: dnsmasq is used as the HTTP and DHCP server. Configuration files for dnsmasq are located at /var/lib/axiom/dnsmasq_svc.conf. The lease file for dnsmasq is located at /var/lib/axiom/dnsmasq_svc.leases.
-
NET-2 port to enable Guided Maintenance on the alternate Pilot: Using the NET-2 port allows the Oracle FS System to be operational, while GM is performed on the Pilot on which the SAS HDD is replaced.
- Unplug the cable attached to the NET-2 port at the back of the Pilot where the SAS HDD must be replaced. Also, unplug the cable from the NET MGT port and plug it into the NET-2.
- On the active Pilot, flush the DHCP lease file located at /var/lib/axiom/dnsmasq_svc.leases and restart the service.
[root@pilot1 /]# echo “” > /var/lib/axiom/dnsmasq_svc.leases
- Restart the dnsmasq service.
[root@pilot1 /]# service dnsmasq_svc restart
Note: The dnsmasq is the DHCP server and must be restarted after the DHCP lease file is flushed, so that the Pilot to be repaired can acquire a fresh IP address that will be used for the kick-start installation.
- Power on the Pilot with the replacement SAS HDD by connecting the power cords.
Note: When the Pilot with the replacement SAS HDD is powered on, the NET–2 port boots up and starts downloading all the necessary RPM packages and files from the active Pilot, and enables the Pilot to restart automatically and join the Oracle FS System.
- Wait for 20 minutes and then ping the external IP address of the Pilot that contains the replacement drive.
A ping reply indicates that thePilot OS has been installed successfully on the SAS HDD.
- Reconnect the cabling that had been disconnected from the Pilot as follows:
- Repeat steps 2 and 3 to flush the DHCP lease files and restart the DHCP server.