Hot swapping of a failed disk is fairly straight procedure if the disks are regular SCSI disks, but for the Fibre Channel (FC) disks we should follow different procedure for hot swaping.
Below specific procedure should be used when replacing one of the internal disks in a system with internal fibre drives (Sun Fire 280R, Sun Fire V480, Sun Fire V490, Sun Fire V880, Sun Fire V890), especially if the disk is under Veritas Volume Manager (VxVM) control.
1) When the “boot net – install” command is issued at the ok prompt, the JumpStart client looks for a Jumpstart boot server.
2) The boot server responds to the rarp request via the “rarpd” daemon (in.rarpd). Using the information in the /etc/ethers file, the server can obtain the client’s IP address and communicate it to the client.
3) A JumpStart server, on the local subnet, receives the RARP request (Reverse Address Resolution Protocol), and maps it to an IP address, using its /etc/ethers and /etc/hosts files. A name service, such as NIS or NIS+, could also be used to map the address.
4) With the IP address known, the JumpStart server generates a RARP reply to the JumpStart client.
5) The JumpStart server responding to the client’s RARP request maps the client’s ethernet address to its IP address and host name, returning this data to the client.
Second Level Boot Process
1) The JumpStart client downloads a minimal kernel(miniroot) from the JumpStart server, into the JumpStart client’s memory. This comes by way of a TFTP request, issued by the Jumpstart client.
2) When the JumpStart server receives the TFTP request, it searches for a matching IP address and architecture, in the “/tftpboot” directory.
3) Once the JumpStart client is booted from the miniroot, it locates the “rules.ok” file. The entry is checked, to make sure it matches that of the JumpStart client.
4) When the match is found, the actions specified are executed. First, the “begin” scripts(if any) are executed. Then the specified profile is installed, and finally the “finish” scripts(if any) are executed.
With the release of Solaris 10 Operating System (OS), the configuration of Storage Area Network (SAN), Serial Attached SCSI (SAS) attached devices, and turning on STMS/MPXIO has changed. This Post details the new ways devices are brought into the operating system, and their configuration files.
The default way Solaris 10 handles SAN/SAS attached devices is to auto-configure them. All devices seen on a Host Bus Adapter(HBA)/Attachment point in the SAN/SAS are automatically configured. Full Story