| PCI Hot Plug User's Guide I/O device edition - for Solaris(TM) Operating System - |
|
Contents
|
| Chapter 3 File Devices | > 3.2 Extension of PCI cards | > 3.2.2 Solaris 9 OS or later |
The procedure to add PCI cards to a new redundant system on a Solaris 9 OS or later system is explained with examples for the multipath software below.
*Multipath Disk Control (MPHD)
*GR Multipath Driver (GRMPD)
*ETERNUS Multipath Driver (ETERNUS MPD)
an example with GR multipath driver (GRMPD).
If other redundant software is used, see the manual of each product.
Use the following command to stop the hardware monitoring daemon of machine administration.
|
# /usr/sbin/FJSVmadm/prephp <Return> |
The daemons will be stopped.
|
# /etc/rc0.d/K10ElxRMSrv stop <Return> # /etc/rc0.d/K10ElxDiscSrv stop <Return> |
Add PCI cards according to the following procedure.
[ for PCI Fibre Channel(PW008FC3U/PW008FC2U/ GP7B8FC1U)]:
If you use SAN management function of Systemwalker StorageMGR/Softek SANView for ETERNUS (except for Vixel) /SP5000 SRM Facility
No procedure is necessary. Go to step 4.
If you don't use SAN management function of the above products
To add PCI cards with the following configurations, Fibre Channel switch SN200 series and disk array device ETERNUS3000/ETERNUS6000/GR700/800 series need to be reconfigured individually.
-If zone configuration by WWPN(World Wide Port Name) is done on SN200 series.
-If the Host Affinity function of ETERNUS3000/ETERNUS6000/GR700/800 series is used.
For details, see "SN200 Series Affinity User's Guide" or "ETERNUS3000/ETERNUS6000/GR700/800 series GRmgr User's Guide." If you use the Fibre Channel switch or disk array device other than described above, see the document of each product.
To perform the above reconfiguration, the WWPN(a 16-digit number) of the replacement card is needed. The WWPN of the PCI card can be known from the eight characters shown on a label on the front plate of the card. These characters represent the bottom eight digit of the WWPN in hexadecimal form. The top eight digit are fixed to 10000000 in hexadecimal form.
For example, if the following label is shown on the front plate of the card, the WWPN of the replacement card is 100000000e244061.
|
0e24 |
[ for Fibre Channel Card (PW028FC3*/PW028FC4*/PW028FC5*)]:
To replace PCI cards with the following configurations, Fibre Channel switch and disk array device need to be reconfigured individually.
-If zone configuration by WWPN (World Wide Port Name) is done on Fibre Channel switch.
-If the Host Zoning function of disk array device is used.
For details, see the document of each product.
To perform the above reconfiguration, the WWPN(a 16-digit number) of the replacement card is needed. The WWPN of the PCI card can be known from the twelve characters shown on a label on the back of the card. These characters represent the bottom twelve digit of the WWPN in hexadecimal form. The top four digit are fixed to 1000 in hexadecimal form.
For example, if the following label is shown on the back of the card, the WWPN of the replacement card is 10000000c9366037.
|
IEEE:0000c9366037 |
Note:
When changing Affinity configuration on SN200 series or other Fibre Channel switch, I/O to other devices is effected by the change, and may result in temporal errors.
I/O to disk array devices recovers normally because of retry processes, but on Fibre Channel tape devices, backup processes may end in errors. Stop backup before changing Affinity configuration.
|
# prtpicl -v > /tmp/prtpicl.pre <Return> |
The relationship of the position of a PCI card and format of "Ap_Id" is shown below.
|
Location of PCI slot |
Definition of slot |
Format of "Ap_Id" |
|---|---|---|
|
Inside chassis of PRIMEPOWER 900/1500/2500 |
Chassis No.: X System board No.: Y Physical slot No.: ZZ |
|
|
PCI/Disk BOX |
I/O Chassis No.: X PCI/Disk BOX No.: Y Physical slot No.: ZZ |
|
|
Other |
Physical slot No.: ZZ |
|
Below, an example of adding a PCI card to chassis number : 0, PCI/Disk BOX number : 1, physical slot number : 02, slot in PCI/Disk BOX(R0B01-PCI#slot02) is explained.
Check the status of the target slot is "empty unconfigured."
|
# cfgadm | grep R0B01-PCI#slot02 <Return> |
|
# cfgadm -x led=fault,mode=blink pcipsy18:R0B01-PCI#slot02 <Return> |
|
# cfgadm pcipsy18:R0B01-PCI#slot02 <Return> |
Connect the replaced PCI card using the cfgadm(1M) command with the configure option, or by pushing the button corresponding to the extension slot position. Note that the push button is only effective in multiuser mode. After the new PCI card is connected, use the cfgadm(1M) command and confirm that the slot status has changed to "connected configured."
If a large-scale configuration of I/O devices is connected to the PCI card in the target slot, command execution for status confirmation may take time.
|
# cfgadm -c configure pcipsy18:R0B01-PCI#slot02 <Return> |
The daemons will be started.
|
# /etc/rc2.d/S99ElxRMSrv start <Return> |
|
# /usr/sbin/FJSVmadm/postphp <Return> |
When the Host Affinity function is being used with Fibre Channel SN200 series, Host Affinity must be configured for the device added.
[ for PCI Fibre Channel(PW008FC3U/PW008FC2U/ GP7B8FC1U)]:
If you use SAN management function of Systemwalker StorageMGR/Softek SANView for ETERNUS (except for Vixel) /SP5000 SRM Facility
WWPN zoning of SN200 series, Host affinity of Array disk device ETERNUS3000/ETERNUS6000/GR700/800 series and binding setting for fjpfca.conf/sd.conf of host can be added from SAN management window automatically.
See "Operation guide" or "User's Manual" of each product for details.
Before using this function, the following procedure 8.a.1. and 8.a.2. [except fcp-bind-target setting] are necessary.
Moreover, begin from procedure 8.a.3. after executing this function.
If you don't use SAN management function of the above products
No procedure is necessary. Go to step 8.
[ for Fibre Channel Card (PW028FC3*/PW028FC4*/PW028FC5*)]:
No procedure is necessary. Go to step 8.
Note:
When changing Affinity configuration on SN200 series, I/O to other devices is effected by the change, and may result in temporal errors.
I/O to disk array devices recovers normally because of retry processes, but on Fibre Channel tape devices, backup processes may end in errors. Stop backup before changing Affinity configuration.
Add driver configurations with the operation below.
With file related drivers, configuration for the PCI card driver and the device driver is needed.
If you use ETERNUS MPD, settings of drivers are configured using grmpdautoconf command. If you use ETERNUS MPD, skip to the procedure "9.Setup of the redundant configuration".
[ SCSI driver(Solaris OS:glm, FUJITSU PCI SCSI Adapter Driver) ]
Configuration is not required.
[Fibre Channel driver (PW008FC3U/PW008FC2U/ GP7B8FC1U) ]
In the following example, instance number is 1, indicating that the interface name of the PCI card added is fjpfca1.
Making the LED of the PCI card blink using the fc_adm command can specify the relation between the instance number and the slot position. The relation between the WWPN and instance number of the PCI card added can be known from the "fc_info -a" command.
|
# prtpicl -v > /tmp/prtpicl.pfca <Return> |
port(type of topology, link speed)
Defined when adding PCI cards with Fabric connection.
This definition is not needed with FC-AL connection.
fcp-bind-target(connection between target ID and WWN)
Defined when adding disk array with Fabric connection.
This definition is not needed with FC-AL connection.
max-throttle(maximum issued SCSI commands)
Defined to limit the number of SCSI commands issued at the same time.
The need and value of this definition depends on the disk array device, so refer to the manuals of each disk array device. Below is an example where definitions for a PCI card at fjpfca1(instance number 1) and a disk array device at target=3 is added.
|
# vi /kernel/drv/fjpfca.conf <Return> |
|
# /usr/sbin/FJSVpfca/fc_config -v <Return> |
[ Fibre Channel driver (PW028FC3*/PW028FC4*/PW028FC5*) ]
Configuration is not required.
Compare the output of prtpicl(1M) command with the output saved at 3.b and find the instance number of the added card.
This is an example where an disk array device in redundant configuration at target=3, lun=0-2 is added in procedure 4.
If this is the first time to pre-define a disk array device, begin with procedure 8.b.1. If this is not the first time to pre-define a disk array device, begin with procedure 8.b.5.
Check if /kernel/drv/hddv.conf exists. If it exists, the hard disk driver is being installed, so start from procedure 8.b.3. If it does not exist, the system is being operated with none-active extension procedures, so start from procedure 8.b.2.
|
Not exist(new install) [ to Procedure 8.b.3.] |
|
# hddvadm -i <Return> |
|
New installation [ to procedure 8.b.5.] |
The following example shows the case that target=1 is repeated
|
# vi /kernel/drv/sd.conf <Return> |
A target number that is already used by the sd driver of the system disk or CD-ROM cannot be deleted. In this case, change the target number in hddv.conf and of the disk array device so that it does not conflict with sd.conf.
If case active extension has been performed before and the LUN definition to extend the next procedures 1.f. - 1.g. are not needed.
The following example shows target=3, lun=0~2 for pre-defined extension and disk array device GR720 (target=1) in use with non-active extension procedures being registered.
|
# ls /kernel/drv/hddv.conf <Return> |
The message example for "Check NG" means that target=3 is defined in both files, and the procedures must be performed again from procedure 8.b.4.
The followings are examples of execution of the FJSVhddv package installation to /opt. The path of the hddvchk_conf command depends on the installed directory.
|
Check OK [ to procedure 8.b.7.] |
|
# update_drv -f hddv <Return> |
In case disk array equipment currently used exists, the following messages are displayed but do not effect performance.
|
# update_drv -f hddv <Return> |
In the following example, "c3t3d0" is logical path name of added lun=0. The logical path name of lun=1,2 is set to "c3t3d1", "c3t3d2" respectively, because cXtYdZmeans X: PCI card number, Y: target number, Z: lun number
|
# prtpicl -v > /tmp/prtpicl.post <Return> |
[ SCSI driver(Solaris OS: glm , FUJITSU PCI SCSI Adapter Driver) ]
No procedure is necessary. Go to step 9.
[ Fibre Channel driver (PW008FC3U/PW008FC2U/ GP7B8FC1U) ]
No procedure is necessary. Go to step 9.
[ Fibre Channel Card (PW028FC3*/PW028FC4*/PW028FC5*)]
Bind the auto mapped target connected with the card and modify the entries of lpfc.conf to match the requirements of the extended Fibre Channel Controller. These procedures are reflected on next boot time. In the following, indicate to bind the auto mapped target with the card.
|
# /usr/sbin/lpfc/lputil<Return> |
Execute the following commands to create a new redundant system.
The following procedure is described for MPHD/GRMPD/ETERNUS MPD. If you use the redundancy software other than MPHD/GRMPD/ETERNUS MPD, see the document for each product.
In case of MPHD, the commands need to be executed for each LUN, specifying the path name determined in 8.b.8 as a parameter.
The italic letters below are the new multipath names, and the underlined letters are the path names that compose the multipath.
|
MPHD |
Add configuration for the application using the logical path name determined in 8.
[ filesystem operation ]
Create file system.
To mount at system start, add an entry in the /etc/vfstab file.
|
# newfs /dev/FJSVmphd/rdsk/mphd2s6 <Return> |
[ raw access operation ]
Configure applications.
For details, see the manual of each application.
[ swap device ]
Add swap device.
To make valid at system start, add an entry in the /etc/vfstab file.
|
# swap -a /dev/FJSVmphd/dsk/mphd2s4 <Return> |
Use the logical path name determined in 8. to start applications.
[ filesystem operation ]
Mount filesystem
|
# mount -F ufs /dev/FJSVmphd/dsk/mphd2s6 /mnt <Return> |
[ raw access operation ]
Start applications.
For details, see the manual of each application.
[ swap device ]
This procedure is not required.
|
Contents
|