| 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.1 Solaris 8 OS |
The procedure to add PCI cards to a new redundant system on a Solaris 8 OS system is explained with examples for the multipath software below.
-Multipath Disk Control (MPHD)
- GR Multipath Driver (GRMPD)
If other multipath software is being used, see the manual of each product.
This is an example where an disk array device at target=3, lun=0-2 is pre-defined.
Extension using PCI Hot Plug is impossible without definition, so definition must be done before the system goes into operation.
[ If you use Solaris OS:sd ]
If this is the first time to pre-define a disk array device, begin with procedure 1.a. If this is not the first time to pre-define a disk array device, go to step 2.
Ensure target=3,lun=0 target=3,lun=1 target=3,lun=3 are defined in /kernel/drv/sd.conf.
If they are not defined or commented, modify /kernel/drv/sd.conf.
| # vi /kernel/drv/sd.conf <Return> : name="sd" class="scsi" target=0 lun=0; : name="sd" class="scsi" target=3 lun=0; name="sd" class="scsi" target=3 lun=1; name="sd" class="scsi" target=3 lun=2;: |
| # touch /reconfigure <Return> # /usr/sbin/shutdown -y -i6 -g0 <Return> |
[ If you use hddv ]
If this is the first time to pre-define a disk array device, begin with procedure 1.a. If this is not the first time to pre-define a disk array device, begin with procedure 1.e.
Check if /kernel/drv/hddv.conf exists. If it exists, the hard disk driver is being installed, so start from procedure 1.c. If it does not exist, the system is being operated with none-active extension procedures, so start from procedure 1.b.
| Not exist(new install) [ to procedure 1.c.] # ls /kernel/drv/hddv.conf <Return> /kernel/drv/hddv.conf: No such file or directory Exists(operation with non-active extension procedures) [ to procedure 1.b.] # ls /kernel/drv/hddv.conf <Return> /kernel/drv/hddv.conf |
| # hddvadm -i <Return> # ls /kernel/drv/hddv.conf <Return> /kernel/drv/hddv.conf: No such file or directory |
| New installation [ to procedure 1.e.] # hddvadm -M <Return> Operation with non-active extension procedures [ to procedure 1.d.] # hddvadm -M <Return> already ID= 1 exists. /devices/pci@1d,2000/fibre-channel@1/sd@1,0:a,raw : GR720 |
The following example shows the case that target=1 is repeated.
| # vi /kernel/drv/sd.conf <Return> : name="sd" class="scsi" target=0 lun=0; : #name="sd" class="scsi" target=1 lun=0; #name="sd" class="scsi" Delete or comment out target=1 lun=1; conflicting definition parts in sd/hddv #name="sd" class="scsi" target=1 lun=2; : |
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.
If the target number of each disk array controller of a redundant system differs, add definition for each target number.
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> /kernel/drv/hddv.conf # vi /kernel/drv/hddv.conf <Return> : #name="hddv" class="scsi" target=0 lun=0; : #name="hddv" class="scsi" target=0 lun=7; : name="hddv" class="scsi" target=1 lun=0; name="hddv" class="scsi" target=1 lun=1; Remove comments of the LUN in use name="hddv" class="scsi" target=1 lun=2; : name="hddv" class="scsi" target=3 lun=0; name="hddv" class="scsi" target=3 lun=1; Remove comments of extended LUN name="hddv" class="scsi" target=3 lun=2; #name="hddv" class="scsi" target=3 lun=3; : |
The message example for "Check NG" means that target=3 is defined in both files,
and the procedures must be performed again from procedure 1.d.
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 1.g.] # /opt/FJSVhddv/bin/hddvchk_conf <Return> /kernel/drv/sd.conf and /kernel/drv/hddv.conf seems to be correct Check NG [ to procedure 1.d.] # /opt/FJSVhddv/bin/hddvchk_conf <Return> NG ID = [ 3 ] |
| # touch /reconfigure <Return> # /usr/sbin/shutdown -y -i6 -g0 <Return> |
Use the following command to stop the hardware disorder 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 5.
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 4061 |
[ 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> pcipsy18:R0B01-PCI#slot02 unknown empty unconfigured unknown |
| # cfgadm -x led=fault,mode=blink pcipsy18:R0B01-PCI#slot02 <Return> |
| # cfgadm pcipsy18:R0B01-PCI#slot02 <Return> Ap_Id Type Receptacle Occupant Condition pcipsy18:R0B01-PCI#slot02 unknown disconnected unconfigured unknown |
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> # cfgadm pcipsy18:R0B01-PCI#slot02 <Return> Ap_Id Type Receptacle Occupant Condition pcipsy18:R0B01-PCI#slot02 mult/hp connected configured ok |
The daemons will be started.
| # /etc/rc2.d/S99ElxRMSrv start <Return> # /etc/rc2.d/S99ElxDiscSrv start <Return> |
Execute the following commands to update hardware configuration information of machine administration and to restart the hardware monitoring daemon.
| # /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 9.a.1. and 9.a.2. [except fcp-bind-target setting] are necessary.
Moreover, begin from procedure 9.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 9.
[ for Fibre Channel Card (PW028FC3*/PW028FC4*/PW028FC5*)]:
No procedure is necessary. Go to step 9.
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 the configuration of driver according to the following operation.
As for file related drivers, additional configuration of the PCI card driver and the device driver is needed.
[ SCSI driver(Solaris OS: glm , FUJITSU PCI SCSI Adapter Driver) ]
Configuration is not required.
[ Fibre Channel driver (PW008FC2U/ W008FC2X/GP7B8FC1U/GP7B8FC1X) ]
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> # diff /tmp/prtpicl.pre /tmp/prtpicl.pfca | more <Return> : > :status okay > :devfs-path /pci@8d,2000/fibre-channel@1 > :driver-name fjpfca > :binding-name pci10cf,105c > :bus-addr 1 > :instance 1 > :_class obp-device > :name fibre-channel : # /usr/sbin/FJSVpfca/fc_adm -l fjpfca1 <Return> |
port (topology classification , link speed)
Define this property when PCI cards using Fabric connection are added.
This definition is not needed with FC-AL connection.
fcp-bind-target(connection of target ID and WWN)
Define this property when disk array equipment using Fabric connections are added.
This definition is not needed with FC-AL connection.
max-throttle(number of maximum SCSI command issue)
This property is defined for restriction on simultaneous issue of SCSI commands.
The necessity and value of this definition depends on the specification of the disk array device, so refer to the user's manual of each equipment.
The following example shows the definition of a fjpfca1 PCI card (instance number : 1) and disk array equipment( target = 3) being added.
| # vi /kernel/drv/fjpfca.conf <Return> : port= "fjpfca0:nport", "fjpfca1:nport:sp1"; <- added fcp-bind-target= "fjpfca0t0:0x50000e1000002501", "fjpfca1t3:0x50000e1000002ab0"; <- added max-throttle= "fjpfca0t0:128", "fjpfca1t3:240"; <- added : |
| # /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 4.b and find the instance number of the added card.
Add device driver configuration with the following procedures according to the I/O device type.
[ Disk/Tape devices(Solaris OS : sd/st) ]
This example is a case where a disk device of target=2, lun=0 is pre-defined in procedure 1. and added in procedure 5. If the device is a tape device, re-read "sd" as "st" in this procedure and perform the same operation.
| # /usr/sbin/devfsadm <Return> |
In the following example, "c2t2d0" is the logical path name of the disk device added.
| # prtpicl -v > /tmp/prtpicl.post <Return> Disk device # diff /tmp/prtpicl.pre /tmp/prtpicl.post | grep devfs-path | grep sd <Return> > :devfs-path /pci@89,4000/scsi@2/sd@2,0 # ls -l /dev/dsk | grep /pci@89,4000/scsi@2/sd@2,0 <Return> lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s0 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:a lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s1 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:b lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s2 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:c lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s3 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:d lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s4 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:e lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s5 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:f lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s6 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:g lrwxrwxrwx 1 root root 41 Sep 20 22:53 c2t2d0s7 -> ../../devices/pci@89,4000/scsi@2/sd@2,0:h Tape device # diff /tmp/prtpicl.pre /tmp/prtpicl.post | grep devfs-path | grep st <Return> > :devfs-path /pci@89,4000/scsi@2/st@5,0 # ls -l /dev/rmt | grep /pci@89,4000/scsi@2/st@5,0 <Return> lrwxrwxrwx 1 root root 41 Sep 20 22:53 1 -> ../../devices/pci@89,4000/scsi@2/st@5,0: lrwxrwxrwx 1 root root 41 Sep 20 22:53 1b -> ../../devices/pci@89,4000/scsi@2/st@5,0:b lrwxrwxrwx 1 root root 41 Sep 20 22:53 1bn -> ../../devices/pci@89,4000/scsi@2/st@5,0:bn lrwxrwxrwx 1 root root 41 Sep 20 22:53 1c -> ../../devices/pci@89,4000/scsi@2/st@5,0:c lrwxrwxrwx 1 root root 41 Sep 20 22:53 1cb -> ../../devices/pci@89,4000/scsi@2/st@5,0:cb lrwxrwxrwx 1 root root 41 Sep 20 22:53 1cbn -> ../../devices/pci@89,4000/scsi@2/st@5,0:cbn lrwxrwxrwx 1 root root 41 Sep 20 22:53 1cn -> ../../devices/pci@89,4000/scsi@2/st@5,0:cn lrwxrwxrwx 1 root root 41 Sep 20 22:53 1h -> ../../devices/pci@89,4000/scsi@2/st@5,0:h lrwxrwxrwx 1 root root 41 Sep 20 22:53 1hb -> ../../devices/pci@89,4000/scsi@2/st@5,0:hb lrwxrwxrwx 1 root root 41 Sep 20 22:53 1hbn -> ../../devices/pci@89,4000/scsi@2/st@5,0:hbn lrwxrwxrwx 1 root root 41 Sep 20 22:53 1hn -> ../../devices/pci@89,4000/scsi@2/st@5,0:hn |
If the device is a tape device, this procedure is not needed.
[ Disk array device (hard disk driver : hddv) ]
This example is a case where a disk array device of target=3, lun=0-2 is pre-defined in procedure 1. and added in procedure 5.
| Check OK [ to procedure 9.b.2.] # /opt/FJSVhddv/bin/hddvchk_conf <Return> /kernel/drv/sd.conf and /kernel/drv/hddv.conf seems to be correct Check NG [ to procedure 1.e.] # /opt/FJSVhddv/bin/hddvchk_conf <Return> NG ID = [ 3 ] |
| # /usr/sbin/hddvadmdr <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> # diff /tmp/prtpicl.pre /tmp/prtpicl.post | grep devfs-path | grep hddv <Return> > :devfs-path /pci@89,2000/fibre-channel@1/hddv@3,0 > :devfs-path /pci@89,2000/fibre-channel@1/hddv@3,1 > :devfs-path /pci@89,2000/fibre-channel@1/hddv@3,2 # ls -l /dev/dsk | grep /pci@89,2000/fibre-channel@1/hddv@3,0 <Return> lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s0 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:a lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s1 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:b lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s2 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:c lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s3 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:d lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s4 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:e lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s5 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:f lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s6 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:g lrwxrwxrwx 1 root root 41 Sep 20 22:53 c3t3d0s7 -> ../../devices/pci@89,2000/fibre-channel@1/hddv@3,0:h |
[ SCSI driver(Solaris OS: glm , FUJITSU PCI SCSI Adapter Driver) ]
No procedure is necessary. Go to step 10.
[ Fibre Channel driver (PW008FC2U/ W008FC2X/GP7B8FC1U/GP7B8FC1X) ]
No procedure is necessary. Go to step 10.
[ 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> LightPulse Common Utility for Solaris/SPARC. Version 1.6a8 (03/03/2004). Copyright (c) 2003, Emulex Network Systems, Inc. Emulex Fibre Channel Host Adapters Detected: 2 Host Adapter 0 (lpfc11) is an LP9802 (Ready Mode) Host Adapter 1 (lpfc9) is an LP9802 (Ready Mode) MAIN MENU 1. List Adapters 2. Adapter Information 3. Firmware Maintenance 4. Reset Adapter 5. Persistent Bindings 0. Exit Enter choice => 5 <Return> PERSISTENT BINDINGS MENU 1. Display Current Bindings 2. Display All Nodes 3. Duplicate Adapter Bindings 4. Bind Target Manually 5. Bind Automapped Targets 6. Delete Binding(s) 0. Return to Main Menu Enter choice => 5 <Return> 0. lpfc11 1. lpfc9 Select an adapter => 0 <Return> Automapped FCP Nodes: Node Target WWPN WWNN ---- ------ --------- -------- Automapped FCP Node 0 50-06-0e-80-00-10-04-92 50-06-0e-80-00-10-04-92 Automapped FCP Node 1 50-06-0e-80-00-10-04-90 50-06-0e-80-00-10-04-90 Press the Enter or Return key to continue: Bind all auto-mapped targets? (Y/N) => Y <Return> Select Binding Method: 1. By Node Name 2. By Port Name 3. By D_ID 0. Cancel Enter Choice => 2 <Return> : |
Execute the following commands to create a new redundant system.
The following procedure is described for MPHD/GRMPHD. If you use the redundancy software other than MPHD/GRMPHD, 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 9.b.3 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 # /usr/opt/FJSViomp/bin/iompadm -c mphd new /dev/rdsk/c3t3d0s2 /dev/rdsk/c4t3d0s2 <Return> IOMP: /dev/FJSVmphd/fiomp/adm2 Node: /dev/FJSVmphd/rdsk/mphd2s0 /dev/FJSVmphd/rdsk/mphd2s1 /dev/FJSVmphd/rdsk/mphd2s2 /dev/FJSVmphd/rdsk/mphd2s3 /dev/FJSVmphd/rdsk/mphd2s4 /dev/FJSVmphd/rdsk/mphd2s5 /dev/FJSVmphd/rdsk/mphd2s6 /dev/FJSVmphd/rdsk/mphd2s7 GRMPD # /usr/sbin/mplbconfig -nv <Return> *** Phase 1: checking /dev/rdsk *** *** Phase 2: checking multi path *** *** Phase 3: analyzing path *** Path : Action : Element path : LUN : Storage : Zone mplb0 : exist : c1t4d0s2 c2t3d0s2 : 0 : GR720464f-12340001 : : mplb8 : new : c3t3d0s2 c4t3d0s2 : 0 : GR8404550- 000213 : : # /usr/sbin/mplbconfig -av <Return> : IOMP: /dev/FJSVmplb/fiomp/adm8 Node: /dev/FJSVmplb/rdsk/mplb8s0 /dev/FJSVmplb/rdsk/mplb8s1 /dev/FJSVmplb/rdsk/mplb8s2 /dev/FJSVmplb/rdsk/mplb8s3 /dev/FJSVmplb/rdsk/mplb8s4 /dev/FJSVmplb/rdsk/mplb8s5 /dev/FJSVmplb/rdsk/mplb8s6 /dev/FJSVmplb/rdsk/mplb8s7 : |
Add configuration for the application using the logical path name determined in 9.
[ filesystem operation ]
Create file system.
To mount at system start, add an entry in the /etc/vfstab file.
| # newfs /dev/FJSVmphd/rdsk/mphd2s6 <Return> # vi /etc/vfstab <Return> : /dev/FJSVmphd/dsk/mphd2s6 /dev/FJSVmphd/rdsk/mphd2s6 /mnt ufs 1 yes - : |
[ 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> # vi /etc/vfstab <Return> : /dev/FJSVmphd/dsk/mphd2s4 - - swap - no - : # swap -l <Return> swapfile dev swaplo blocks free : /dev/FJSVmphd/dsk/mphd2s4 32,164 16 788384 683680 |
Use the logical path name determined in 9. 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
|