Friday, May 30, 2008

Solaris Netapps add new filesystem

The following volume options should be configured:
Nosnap No automatic scheduled Snapshot™ duplications
Minra Minimal read ahead
Nvfail NVRAM check and behavior
sapfiler1> vol options sapdata nosnap on
sapfiler1> vol options sapdata minra on
sapfiler1> vol options sapdata nvfail on
sapfiler1> vol options saplog nosnap on
sapfiler1> vol options saplog minra on
sapfiler1> vol options saplog nvfail on
sapfiler1> qtree create /vol/sapdata/sapdata_lun
sapfiler1> qtree create /vol/saplog/saplog_lun
sapfiler1> qtree create /vol/saplog/sapmnt_lun
sapfiler1> qtree create /vol/saplog/sapusr_lun
sapfiler1> qtree create /vol/saplog/trans_lun
Create the LUNs
sapfiler1> lun create -s 30g -t solaris /vol/sapdata/sapdata_lun/sapdata
sapfiler1> lun create -s 5g -t solaris /vol/saplog/saplog_lun/saplog
sapfiler1> lun create -s 500m -t solaris /vol/saplog/sapmnt_lun/sapmnt
sapfiler1> lun create -s 500m -t solaris /vol/saplog/sapusr_lun/sapusr
sapfiler1> lun create -s 200m -t solaris /vol/saplog/trans_lun/trans
Define the initiator group
To create the initiator group you need to know the WWPN of the host, which will use these LUNs. The
WWPN can be obtained with the sanlun command on the host.
bash-2.03# sanlun fcp show adapter
lpfc0 WWPN:10000000c92d55f3
sapfiler1> igroup create -f -t solaris pp400 10:00:00:00:c9:2d:55:f3
Map the LUNs to the initiator group
sapfiler1> lun map /vol/sapdata/sapdata_lun/sapdata pp400 0
sapfiler1> lun map /vol/saplog/saplog_lun/saplog pp400 6
sapfiler1> lun map /vol/saplog/sapusr_lun/sapusr pp400 7
sapfiler1> lun map /vol/saplog/sapmnt_lun/sapmnt pp400 8
sapfiler1> lun map /vol/saplog/trans_lun/trans pp400 9

Configure persistent binding
Persistent binding is configured with the tool /usr/sbin/lpfc/lputil . To configure persistent
binding you need to know the WWNN of the filer. The WWNN can be obtained with the sysconfig
command at the filer console.
sapfiler1> sysconfig –v
…………
…………
slot 3: Fibre Channel Target Host Adapter 3a
(Dual-channel, QLogic 2312 (2342) rev. 2, 64-bit, )
Firmware rev: 3.1.15
Host Port Addr: 011000
Cacheline size: 8
SRAM parity: Yes
FC Nodename: 50:a9:80:00:02:00:88:f7 (50a98000020088f7)
FC Portname: 50:a9:80:03:02:00:88:f7 (50a98003020088f7)
Connection: PTP, Fabric
After using lputil command the lpfc.conf file has the following entry.
File /kernel/drv/lpfc.conf
…………
…………
# BEGIN: LPUTIL-managed Persistent Bindings
fcp-bind-WWNN="50a98000020088f7:lpfc0t1";
Network Appliance Inc. Proprietary
7
TECHNICAL REPORT
File /kernel/drv/lpfc.conf
…………
…………
# BEGIN: LPUTIL-managed Persistent Bindings
fcp-bind-WWNN="50a98000020088f7:lpfc0t1";
Edit entries in /kernel/drv/sd.conf
The LUN IDs that were used when mapping the LUNs to the initiator groups and the SCSI ID that was
used with the lputil command have to be used in the entries in /kernel/drv/sd.conf.
…………
…………
name="sd" parent="lpfc" target=1 lun=0;
name="sd" parent="lpfc" target=1 lun=1;
name="sd" parent="lpfc" target=1 lun=2;
name="sd" parent="lpfc" target=1 lun=3;
name="sd" parent="lpfc" target=1 lun=4;
name="sd" parent="lpfc" target=1 lun=5;
name="sd" parent="lpfc" target=1 lun=6;
name="sd" parent="lpfc" target=1 lun=7;
name="sd" parent="lpfc" target=1 lun=8;
name="sd" parent="lpfc" target=1 lun=9;

Reboot with reconfigure
After the new entries in /kernel/drv/sd.conf are edited, the host needs to be rebooted with the
reconfigure option. reboot -- -r

Configure new disks with format command
The new disks can now be configured with the format command.