Commands to troubleshoot any issue with NetApp, Server, HBA etc.
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
Posted by Patel Ketan at 9:14 PM
0 comments:


NetApp :-How to configure SnapMirror
You cannot do Snapmirror from 2 volumes on source to 1 volume on destination.

Snapmirror is configured on volume level and it is 1 to 1 relationship.

Also SnapMirrored volume must be as large or larger than the source volume.
Although it is possible to configure a SnapMirrored volume with a different
configuration than that of the source volume. eg. different size RAID groups or
disk geometries, it can result in sub- optimal mirroring performance


ON Source Filer:-

1) ENABLE SNAPMIRROR
fas3070-ca*> options snapmirror.enablesnapmirror.enable on

2) ADD IP OF SOURCE AND DESTINATION FILER IN /etc/hosts file:-fas3070-ca*> wrfile /etc/hosts127.0.0.1 localhost10.41.71.150 fas3070-ca fas3070-ca-e0a # SOURCE (localhost)10.64.20.115 fas3070-ams fas3070-ams-e0a # DESTINATION

3) CHANGE SNAPMIRROR.ACCESS OPTIONS FROM LEGACY TO host=
fas3070-ca*> options snapmirror.accesssnapmirror.access legacy
fas3070-ca*> options snapmirror.access host=10.64.20.115

fas3070-ca*> options snapmirror.accesssnapmirror.access host=10.64.20.115

4) CREATE VOLUME:-
fas3070-ca*> vol create src_vol kaggr 1gCreation of volume 'src_vol' with size 1g on containing aggregate'kaggr' has completed.

5) WRITE SOME DATA IN VOLUME:-
fas3070-ca*> wrfile /vol/src_vol/vol_status
ABC
6) MAKE SURE DESTINATION FILER IS REACHABLE:-
fas3070-ca*> ping 10.64.20.11510.64.20.115 is alive

ON Destination Filer:-

1) ENABLE SNAPMIRROR AND LOG.:-
fas3070-ams*> options snapmirror.enablesnapmirror.enable on
fas3070-ams*> options snapmirror.logsnapmirror.log.enable on

2) ADD IP AND HOST NAME OF SOURCE FILER:-
fas3070-ams*> wrfile /etc/hosts127.0.0.1 localhost10.64.20.115 fas3070-ams fas3070-ams-e0a # DEST. FILER (localhost)10.41.71.150 fas3070-ca fas3070-ca-e0a #SOURCE FILER

3) CREATE VOLUME SAME SIZE AS SOURCE:-
fas3070-ams*> vol create dst_vol aggr1 1g
4) RESTRICT VOLUME:-
fas3070-ams*> vol restrict dst_vol
fas3070-ams*> vol status Volume State Status Options dst_vol restricted raid_dp, flex

5) INITIALIZE SNAPMIRROR:-
fas3070-ams*> snapmirror initialize -S 10.41.71.150:src_vol fas3070-ams:dst_volTransfer started.Monitor progress with 'snapmirror status' or the snapmirror log.


6) VERIFY SNAPMIRROR STATUS:-
fas3070-ca*> snapmirror statusSnapmirror is on.Source Destination State Lag Statusfas3070-ca:src_vol fas3070-ams:dst_vol Source - Transferring (88 KB done)

fas3070-ca*> snapmirror statusSnapmirror is on.Source Destination State Lag Statusfas3070-ca:src_vol fas3070-ams:dst_vol Source 00:00:15 Idle
Posted by Patel Ketan at 8:27 PM


How & When to do netboot NetApp
Not all NetApp is supported netboot. Only FAS2000 series, FAS6000
series and FAS3040/3070 are supported.

Netbooting is required if your compactflash card is corrupted and
you can't boot the NetApp storage. Reason for using this is that
FAS2000/6000 series and 3040/3070 don't boot from floppy or disk
as they boot from compactflash card.

Also when you install or upgrade ONTAP, the download command
copies a boot kernel to the compactflash card, not from a boot block
on disk as in prior NetApp series such as FAS270/940 etc.

In order to netboot you need http or tftp server available and
boot image on the server. Boot image can be downloaded from
http://now.netapp.com/ or from /etc/boot/ directory.

1) Configure NIC with static IP or dhcp.

2) Netboot from http or tftp server

3) From boot menu use option 4a (initialized disk with flexible root volume).

4) Configure filer with IP, netmask, gateway, domainname etc.

5) Now upgrade ONTAP with software install, download command so it
writes in compact flash.

6) Make sure to reboot storage system so it comes perfectly.


You need to configure NIC in order to netboot.

LOADER> ifconfig e0a -addr=10.41.65.120 -mask=255.255.255.0
-gw=10.41.65.1 -dns=10.41.70.91 -domain=ngslabs.netapp.com

LOADER> netboot

LOADER> http:/web.foo.com/netapp/release/7.2.4/releases/x86-64/dist/netapp-x86-64

Loading web.foo.com/netapp/release/7.2.4/releases/x86-64/dist/netapp-x86-64:0x200000/38671336 0x26e13e8/33851112 0x4729ad0/2399386 0x497376a/6 Entry at 0x00202018 Closing network.
Starting program at 0x00202018
Press CTRL-C for special boot menu
Thu May 8 19:23:42 GMT [nvram.battery.state:info]:
The NVRAM battery is currently ON.
Thu May 8 19:23:52 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0b.
Thu May 8 19:23:52 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0c.
Thu May 8 19:23:52 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0f.
Thu May 8 19:23:52 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0g.
NetApp Release 7.2.4: Fri Nov 16 04:31:47 PST 2007 Copyright (c) 1992-2007 Network Appliance, Inc.
Starting boot on Thu May 8 19:23:38 GMT 2008 Thu May 8 19:23:59 GMT [diskown.isEnabled:info]: software ownership has been enabled for this system

(1) Normal boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Initialize owned disks (14 disks are owned by this filer).
(4a) Same as option 4, but create a flexible root volume.
(5) Maintenance mode boot.

Selection (1-5)?4a
.........................................................................................................................................................................................................................................................................................................................................................................................................Thu May 8 20:52:23 GMT [raid.disk.zero.done:notice]: Disk 0e.22 Shelf ? Bay ? [NETAPP X262_MSABR250SSX BEG2] S/N [L5A52PTG] : disk zeroing complete
.....Thu May 8 20:52:24 GMT [raid.disk.zero.done:notice]:
........................................................................................................................................................................................................................................................................................................................................................................................................Thu May 8 20:54:54 GMT [raid.disk.zero.done:notice]: Disk 0e.20 Shelf ? Bay ? [NETAPP X262_MSABR250SSX BEG2] S/N [L5A9QLJG] : disk zeroing complete
Thu May 8 20:54:54 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr0/plex0/rg0/0e.18 Shelf 1 Bay 2 [NETAPP X262_MSABR250SSX BEG2] S/N [L5A9QLFG] to aggregate aggr0 has completed successfully
Thu May 8 20:54:54 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr0/plex0/rg0/0e.17 Shelf 1 Bay 1 [NETAPP X262_MSABR250SSX BEG2] S/N [L5A9QHKG] to aggregate aggr0 has completed successfully
Thu May 8 20:54:54 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr0/plex0/rg0/0e.16 Shelf 1 Bay 0 [NETAPP X262_MSABR250SSX BEG2] S/N [L5AE02SG] to aggregate aggr0 has completed successfully
Thu May 8 20:54:56 GMT [wafl.vol.add:notice]: Aggregate aggr0 has been added to the system.
Thu May 8 20:54:56 GMT [fmmbx_instanceWorke:info]: no mailbox instance on local side Thu May 8 20:54:57 GMT [fmmb.current.lock.disk:info]: Disk 0e.18 is a local HA mailbox disk.
Thu May 8 20:54:57 GMT [fmmb.current.lock.disk:info]: Disk 0e.17 is a local HA mailbox disk.
Thu May 8 20:54:58 GMT [fmmbx_instanceWorke:info]: normal mailbox instance on local side ifconfig e0a mediatype auto Configuring onboard ethernet e0a.
Contacting DHCP server.
Ctrl-C to skip DHCP search ...
Thu May 8 20:54:58 GMT [rc:info]: Contacting DHCP server Thu May 8 20:55:02 GMT [ltm_services:info]: Ethernet e0a: Link up Thu May 8 20:57:02 GMT [rc:info]: DHCP config failed Configuring e0a using DHCP failed.
NetApp Release 7.2.4: Fri Nov 16 04:31:47 PST 2007
System ID: 0118049243 ()
System Serial Number: 1083586 ()
System Rev: B0
slot 0: System Board
Processors: 1
Memory Size: 16384 MB
Memory Attributes: Node Interleaving
Bank Interleaving
Hoisting
Chipkill ECC
slot 0: BGE 10/100/1000 Ethernet Controller
e0a MAC Address: 00:a0:98:08:46:3c (auto-1000t-fd-up)
e0b MAC Address: 00:a0:98:08:46:3d (auto-unknown-cfg_down)
e0c MAC Address: 00:a0:98:08:46:3e (auto-unknown-cfg_down)
e0d MAC Address: 00:a0:98:08:46:3f (auto-unknown-cfg_down)
e0e MAC Address: 00:a0:98:08:46:40 (auto-unknown-cfg_down)
e0f MAC Address: 00:a0:98:08:46:41 (auto-unknown-cfg_down)
slot 0: FC Host Adapter 0a
14 Disks: 2959.2GB
1 shelf with AT-FCX
slot 0: FC Host Adapter 0b
slot 0: FC Host Adapter 0c
slot 0: Fibre Channel Target Host Adapter 0d
slot 0: FC Host Adapter 0e
14 Disks: 2959.2GB
1 shelf with AT-FCX
slot 0: FC Host Adapter 0f
slot 0: FC Host Adapter 0g
slot 0: Fibre Channel Target Host Adapter 0h
slot 0: NetApp ATA/IDE Adapter 0i (0x00000000000001f0)
0i.0 977MB
slot 2: NVRAM
Memory Size: 512 MB
Please enter the new hostname []: fas6040-ca
Do you want to configure virtual network interfaces? [n]:
Please enter the IP address for Network Interface e0a []: 10.41.65.120
Please enter the netmask for Network Interface e0a [255.0.0.0]: 255.255.255.0
Please enter media type for e0a {100tx-fd, tp-fd, 100tx, tp, auto (10/100/1000)} [auto]:
Please enter flow control for e0a {none, receive, send, full} [full]:
Do you want e0a to support jumbo frames? [n]:
Please enter the IP address for Network Interface e0b []:
Please enter the IP address for Network Interface e0c []:
Please enter the IP address for Network Interface e0d []:
Please enter the IP address for Network Interface e0e []:
Please enter the IP address for Network Interface e0f []:
Would you like to continue setup through the web interface? [n]:
Please enter the name or IP address of the default gateway: 10.41.65.1
The administration host is given root access to the filer's
/etc files for system administration.
To allow /etc root access
to all NFS clients enter RETURN below.
Please enter the name or IP address of the administration host: 10.41.70.192
Where is the filer located? []: sunnyvale,ca
Do you want to run DNS resolver? [n]: y
Please enter DNS domain name []: ngslabs.netapp.com
You may enter up to 3 nameservers
Please enter the IP address for first nameserver []: 10.41.70.91
Do you want another nameserver? [n]: y
Please enter the IP address for alternate nameserver []: 10.41.70.112
Do you want another nameserver? [n]:
Do you want to run NIS client? [n]:
This system will send event messages and weekly reports to Network Appliance Technical Support.
To disable this feature, enter "options autosupport.support.enable off" within 24 hours.

Enabling Autosupport can significantly speed problem determination and resolution should a problem occur on your system. For further information on Autosupport, please see: http://now.netapp.com/autosupport/
Press the return key to continue.

The Remote LAN Module (RLM) provides remote management capabilities
including console redirection, logging and power control.
It also extends autosupport by sending
additional system event alerts. Your autosupport settings are used
for sending these alerts via email over the RLM LAN interface.
Would you like to configure the RLM LAN interface [y]:
Would you like to enable DHCP on the RLM LAN interface [y]: n
Please enter the IP address for the RLM []: 10.41.70.3
Please enter the netmask for the RLM []: 255.255.255.0
Please enter the IP address for the RLM gateway []: 10.41.70.1
The mail host is required by your system to send RLM
alerts and local autosupport email.
Please enter the name or IP address of the mail host [mailhost]:

You may use the autosupport options to configure alert destinations.
The initial aggregate currently contains 3 disks; you may add more
disks to it later using the "aggr add" command.
Now apply the appropriate licenses to the system and install
the system files (supplied on the Data ONTAP CD-ROM or downloaded
from the NOW site) from a UNIX or Windows host. When you are
finished, type "download" to install the boot image and
"reboot" to start using the system.
Thu May 8 21:03:31 GMT [init_java:warning]: Java disabled: Missing /etc/java/rt131.jar.
Thu May 8 21:03:31 GMT [dfu.firmwareUpToDate:info]: Firmware is up-to-date on all disk drives Thu May 8 21:03:31 GMT [sfu.firmwareUpToDate:info]: Firmware is up-to-date on all disk shelves.
Thu May 8 21:03:35 GMT [ltm_services:info]: Ethernet e0a: Link up add net default: gateway 10.41.65.1 Thu May 8 21:03:37 GMT [httpd_servlet:warning]: Java Virtual Machine not accessible There are 11 spare disks; you may want to use the vol or aggr command to create new volumes or aggregates or add disks to the existing aggregate.
Thu May 8 21:03:37 GMT [mgr.boot.disk_done:info]: NetApp Release 7.2.4 boot complete. Last disk update written at Thu Jan 1 00:00:00 GMT 1970 Thu May 8 21:03:37 GMT [mgr.boot.reason_ok:notice]: System rebooted.
Thu May 8 21:03:37 GMT [asup.config.minimal.unavailable:warning]: Minimal Autosupports unavailable. Could not read /etc/asup_content.conf

fas6040-ca> Thu May 8 21:03:38 GMT [console_login_mgr:info]: root
fas6040-ca> logged in from console
fas6040-ca>
fas6040-ca>
fas6040-ca> version
NetApp Release 7.2.4: Fri Nov 16 04:31:47 PST 2007
fas6040-ca>


fas6040-ca> software list73RC1_setup_q.exe73RC1_sysfiles_q.tar

fas6040-ca>
fas6040-ca> software install 73RC1_setup_q.exe



fas6040-ca> download

download: You can cancel this operation by hitting Ctrl-C in the next 6 seconds.download: Depending on system load, it may take many minutesdownload: to complete this operation. Until it finishes, you willdownload: not be able to use the console.Fri May 9 19:41:45 GMT [download.request:notice]: Operator requested download initiated

download: Downloading boot devicedownload: GRUB needs updating.download: Updating Partition layout and Loader.............................................................download: Downloading boot device (Service Area).............................

fas6040-ca> Fri May 9 19:49:09 GMT [download.requestDone:notice]: Operator requested download completedFri May 9 19:50:00 GMT [mgr.stack.openFail:warning]: Unable to open function name/address mapping file /etc/boot/mapfile_7.2.4.2: No such file or directory

How to reduce disk in a aggregate(aggr)
When you want to reduce aggr size if all disks are allocated to just 1 aggregate.

To make it easy, build a new aggregate first with three disks. If you have disks available.

If not, you will have to shutdown the system and zero the disks.

Here is the procedure if you have disks available.


1. aggr create aggr_new 3

2. vol create vol0_new aggr_new 60g

3. ndmpcopy /vol/vol0 /vol/vol0_new

4. vol rename vol0 vol_old

5. vol rename vol0_new vol0

6. vol options vol0 root

7. reboot system

8. aggr offline aggr0

9. aggr destroy aggr0

10. aggr rename aggr_new aggr0

11. disk zero spares
Posted by Patel Ketan at 7:13 AM



Tuesday, April 29, 2008
How to do LUN cloning
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 for the clone lun that is distinct from the parent.
This process may take some time and proceeds in the background.

Use the lun clone split status command to view the command's progress.
Both clone and parent luns remain available during this process of splitting them apart.
Upon completion, the snapshot on which the clone was based will be unlocked in the parent vol.


EXAMPLE:-

I want to clone a LUN (/vol/sanboot/pc113lun) in sanboot volume.

1) Check volume status
fas940-ca> vol status
Volume State Status Options
vol0 online raid_dp, flex root
sanboot online raid_dp, flex

2) Check LUN status
fas940-ca> lun show/vol/sanboot/pc113lun 10g (10737418240) (r/w, online, mapped)

3) Create Snapshot of sanboot volume which contain LUN I want to clone.
fas940-ca> snap create sanboot sanboot_snap

4) Verify snapshot I just created
fas940-ca> snap listVolume sanbootworking...
%/used %/total date name
---------- ---------- ------------ --------
0% ( 0%) 0% ( 0%) Apr 29 20:14 sanboot_snap
10% (10%) 0% ( 0%) Apr 29 20:00 hourly.0
fas940-ca>

5) Clone LUN using following command.
fas940-ca> lun clone create /vol/sanboot/pc113lun_clone -b /vol/sanboot/pc113lun sanboot_snap

6) Verify clone created as new LUN. In this example it is pc113lun_clone
fas940-ca> lun show/vol/sanboot/pc113lun 10g (10737418240) (r/w, online, mapped)/vol/sanboot/pc113lun_clone 10g (10737418240) (r/w, online)

7) Verify snapshot status. You will see it as a busy LUN.
fas940-ca> snap list
Volume sanbootworking...
%/used %/total date name
---------- ---------- ------------ --------
0% ( 0%) 0% ( 0%) Apr 29 20:14 sanboot_snap (busy,LUNs)
10% (10%) 0% ( 0%) Apr 29 20:00 hourly.0

8) Now Split the LUN
fas940-ca> lun clone split start /vol/sanboot/pc113lun_clone

9) Verify status of lun cloning/split.
fas940-ca> lun clone split status /vol/sanboot/pc113lun_clone
lun clone split status: Done 1534504 of 2621440 blocks (58% complete).

fas940-ca> lun clone split status /vol/sanboot/pc113lun_clone
lun clone split status: /vol/sanboot/pc113lun_clone: LUN is not a clone

10) Verify snapshot. Now you will not see snapshot as busy because we just split the LUN.
fas940-ca> snap list sanboot
Volume sanbootworking...
%/used %/total date name
---------- ---------- ------------ --------
0% ( 0%) 0% ( 0%) Apr 29 20:14 sanboot_snap
5% ( 5%) 0% ( 0%) Apr 29 20:00 hourly.0

11) Delete the snapshot.
fas940-ca> snap delete sanboot sanboot_snap

12) Verify LUN
fas940-ca> lun show
/vol/sanboot/pc113lun 10g (10737418240) (r/w, online, mapped)
/vol/sanboot/pc113lun_clone 10g (10737418240) (r/w, online)

13) Unmap the original LUN
fas940-ca> lun unmap /vol/sanboot/pc113lun pc13grp

14) Offline original LUN
fas940-ca> lun offline /vol/sanboot/pc113lun

15) Verify LUN status.
fas940-ca> lun show/vol/sanboot/pc113lun 10g (10737418240) (r/w, offline)/vol/sanboot/pc113lun_clone 10g (10737418240) (r/w, online, mapped)

16) Make a Comment on Original LUN.
fas940-ca> lun comment /vol/sanboot/pc113lun "VMWare ESX 3.5 Server Boot Golden LUN"

17) Verfiy LUN status.
fas940-ca> lun show -v /vol/sanboot/pc113lun
/vol/sanboot/pc113lun 10g (10737418240) (r/w, offline)
Comment: "VMWare ESX 3.5 Server Boot Golden
LUN"Serial#: Vqi6FJI0QEY-
Share: none
Space Reservation: enabled
Multiprotocol Type: vmware

18) Map the new LUN which is cloned
fas940-ca> lun map /vol/sanboot/pc113lun_clone pc13grp

19) Verify LUN mapping.
fas940-ca> lun show -m
LUN path Mapped to LUN ID Protocol
-----------------------------------------------------------------/vol/sanboot/pc113lun_clone pc13grp 0 FCP

fas940-ca> lun show
/vol/sanboot/pc113lun 10g (10737418240) (r/w, offline)
/vol/sanboot/pc113lun_clone 10g (10737418240) (r/w, online, mapped)

20) Now you have copy of LUN which you can use in case of disaster or to create new LUN from this for fast and easy deployment of OS.
Posted by Patel Ketan at 11:46 PM