WindowsAdminGuru BLOG

Following is example for Solaris. 1) Download the ASL from symantec site. VxVM 4.x(Solaris) http://seer.entsupport.symantec.com/docs/290145.htm For VxVM 5.0 (Solaris) http://seer.entsupport.symantec.com/docs/292417.htm 2) install the NTAPasl package. gunzip tar pkgadd 3) Verify that the installation was successful. pkginfo -l NTAPasl. fcpblade100-ams2{root}: pkginfo -l NTAPasl PKGINST: NTAPasl NAME: Network Appliance VxVM 4.x Array Support Library CATEGORY: system ARCH: sparc VERSION: 4.0.2,REV=02.15.2006.14.28 BASEDIR: /etc/vx VENDOR: VERITAS Software DESC: Network Appliance VxVM 4.x Array Support Library PSTAMP: VERSION-4.0.2:15-Feb-2006 INSTDATE: Jan 26 2007 15:12 STATUS: completely installed FILES: 5 installed pathnames 3 shared pathnames 3 directories 2 executables 47 blocks used (approx) 4) After the ASL package is installed, run following command to claim the disk array as NetApp device: # vxdctl enable If the host is connected to the st

Brocade:- Steps to do perform before adding new brocade switch in existing fabric. How to clear configuration before installing brocade switch, configure switch and reboot switch 1) disable the switch > switchdisable 2) clear any existing configuration on the switch > cfgclear 3) Disable the configuration >cfgdisable 4) Save the configuration >cfgsave 5) Ensure that the switch is configured with default setting >configdefault 6) Set the switch parameters >configure

LUN cloning allows the user to create a copy of a LUN, which was initially created to be backed by a LUN or a file in a snapshot (i.e. using lun clone create ). LUN cloning creates a complete copy of the LUN and frees the snapshot, which can then be deleted. The lun clone create command creates a lun on the local filer that is a clone of a "backing" lun. A clone is a lun that is a writable snapshot of another lun. Initially, the clone and its parent share the same storage; more storage space is consumed only as one lun or the other changes. The parent_snap is locked in the parent volume, preventing its deletion until the clone is either destroyed or split from the parent using the lun clone split start command. The lun clone create command fails if the chosen parent_lunpath is currently involved in a lun clone split operation. lun clone split start lun_path This command begins separating clone lun_path from its underlying parent. New storage is allocated

Persistent Name Binding support is available for target devices. This support is provided for users to associate a specified device World Wide Port Name (WWPN) to a specified SCSI target ID. For driver version earlier than 4.15, it is implemented through both the /kernel/drv/sd.conf and /kernel/drv/qla2300.conf files. The matching between the target device port, the SCSI target ID, and the adapter driver instance happens inside /kernel/drv/qla2300.conf. For driver versions 4.15 and later, the driver dynamically discovers targets, so no entries in the sd.conf or st.conf files are required. Note that if you disable dynamic discovery of devices (via the hbaX-disable-dynamic-device-support parameter), you must populate the sd.conf and st.conf files as noted above for pre-4.15 drivers. The Persistent Name Binding support for target devices associates a SCSI target ID to a specified device World Wide Port Name or port ID. If port ID binding is specified it takes precedent over World Wi

World Wide Name (WWN) are unique 8 byte (64-bit) identifiers in SCSI or fibre channel similar to that of MAC Addresses on a Network Interface Card (NIC). Talking about the WWN names, there are also World Wide port Name (WWpN), a WWN assigned to a port on a Fabric which is what you would be looking for most of the time. World Wide node Name (WWnN), a WWN assigned to a node/device on a Fibre Channel fabric. To find the WWN numbers of your HBA card in Sun Solaris, you can use one the following procedures Using fcinfo (Solaris 10 only) This is probably the easiest way to find the WWN numbers on your HBA card. Here you can see the HBA Port WWN (WWpN) and the Node WWN (WWnN) of the two ports on the installed Qlogic HAB card. This is also useful in finding the Model number, Firmwar version FCode, supported and current speeds and the port status of the HBA card/port. root@ sunserver:/root# fcinfo hba-port grep WWN root@ sunserver:/root# scli -i egrep “Node NamePort Name” root@

For Linux servers:- # uname -a # cat /etc/redhat-release # df -T # cat /etc/qla2300.conf # cat /etc/module.conf # cat /proc/scsi/qla2300/0 & 1 (qlogic HBA) # scli (utility for qlogic card, need seperate rpm) For Solaris :- #uname -a # cat /etc/release # modinfo # cat /kernel/drv/lpfc.conf (Emulex HBA) # cat /kernel/drv/sd.conf (Emulex HBA) # /usr/sbin/lpfc/lputil (utility will provide more info about Emulex HBA). # scli (utility for qlogic card, need seperate package) From Netapp Filer:- # version # fcp show cfmode # fcp status # lun show # lun show -m # lun show -v # fcp show nodename # fcp show adapters # fcp show initiators # igroup show # sysconfig # sysconfig -v

Will be updated soon