How to add a new disk shelf to a Netapp filer ??

Assumption:- Filer has already one disk shelf connected this is the new one which has to be added and cabled.

Cables required:- Two SAS cables , Two ACP (CAT6 ETHERNET ) cables if any

1. Rack the shelf

2. Connect power cables & turn the shelf on (wait about 30 seconds)

3. On the front of the shelf, change the shelf id to something unique. (try and keep it sequential with the shelf that's already there)  DO NOT USE "00"

4. Wait about 45 seconds and then restart the shelf and make sure the new shelf ID came up.

4. SSH into both filers and do "options disk.auto_assign off"

5. Do a "storage show disk -p" on both controllers and copy the contents into a txt file and save it. (run this command again and make sure all your disks are still there)

6. Do a "options autosupport.doit "before shelf add"" on both controllers since i'm scared your doing this via community forums. ("before shelf add" is in quotes on the command)

5. Now for the fun part, take a SAS cable and plug one end into the TOP circle of the OLD shelf and plug it in the BOTTOM square of the NEW shelf

6. Now take another SAS cable and plug one end into the BOTTOM circle of the OLD shelf and plug it into the TOP square of the new shelf

7. assign your disks and don't forget to turn back on disk auto assign when you're done.

8. Run "storage show disk -p" and make sure all of your old disks are there.

(shelves at the end of a stack are always reversed, this is a special circumstance and you will not cable all shelves like this in the future.

Understanding LUN Usage in Netapp

Early today i have seen some volumes shown threshold reached 70 % but in my windows box showing plenty  of free space available. I was wondered what is happening to my storage and i found the reason why .
If you delete a load of data from the client-side (eg NTFS) the client marks the blocks as free, as opposed to physically zero'ing out the data, right?  Down at the storage level WAFL has no way to know these blocks have been deleted, so when you write more data to the LUN it will consume new blocks in the volume.  Typically, as a LUN ages, you will find the NetApp side will show the LUN at, or close to 100% full, but the clients filesystem may still have plenty of space.  This is by design, and often not a problem - although it looks a bit odd at first.  Check out Snapdrive's Space Reclaimer feature if using Windows - this will reclaim those free blocks at the WAFL end if required.

What is Netapp DS4243 ??

(DS = Disk Shelf, 4= 4U high, 24= number of disks, 3= 3GB SAS (although it has 4 in the SAS matrix making 12GB)) is a SAS only shelf, so these use SAS cables rather than FC.

Cluster Take over and Giveback in Netapp

NetApp commands such as Take over and Give back in Active/Active Cluster mode configuration.

Active /Active cluster means; you should require 2 controllers and these two controllers should communicate each other.

We had requirement that we need to take offline of controller 2 ( which is our development LUN’s and CIFS volumes are connected)

We can use below commands to do the cluster failover before we take Controller2 offline . Here is the command

First we need to check the status of the cluster (is it enabled or disabled)

FAS01> cf status
Cluster enabled, Controller2 is up.

FAS01 > cf  takeover

This command will take over the Controller2 resource entirely and will work continuously without any affect. User wouldn't know this take over. Once you give this command you will log off from the controller2 session and it will be hand over to controller 1 entirely.

Now controller 2 is running and using the resource of controller 1 and the performance you can decrease little bit. And the controller 1 console prompt will change to take over mode and lots of logs will come to the console.

Once your work is over you can return back by using below command

Controller1 (takeover) > cf giveback

Always better to disconnect any user or application before you take offline of any controller.

What is iSCSI in detail ??

http://tools.ietf.org/html/rfc3720

Usage of Port 445 In windows

Port no : 445 (TCP) being used for Active Directory, Windows shares & SMB file sharing which is mandatory for windows servers

NETBACKUP OPSCENTER "Error occurred while connecting to the OpsCenter Server. Please ensure that the server is running"

1) Update hosts file with the server's short and FQDN name

2) Stop OpsCenter services:

<install_path>\OpsCenter\server\bin>opsadmin stop
Stopping the OpsCenter Web Console Service...
Stopping the OpsCenter Server...
Stopping the OpsCenter database...

3) Start OpsCenter services:

 <install_path>\OpsCenter\server\bin>opsadmin start
Starting the OpsCenter Database...
The Symantec OpsCenter Database Server service is starting.
The Symantec OpsCenter Database Server service was started successfully.

Starting the OpsCenter Server...
The Symantec OpsCenter Server Service service is starting.
The Symantec OpsCenter Server Service service was started successfully.

Starting OpsCenter Web Console Service...
The Symantec OpsCenter WebServer Service service is starting.
The Symantec OpsCenter WebServer Service service was started successfully.

How to update permanent license instead of expired demo key without system reboot ??

1）Input permanent license
# vxlicinst -k <license_key>

2）Check license files，delete or remove demo license files
# cd /etc/vx/licenses/lic
# ls -l
# rm <old_demo_key_file>
or
# mv <old_demo_key_file> <other_directory>

3）Update license using commands
# hasys -updatelic -all
<<<<<<  update system level licensing on all running systems in the cluster at one time.

or
# hasys -updatelic -sys <sysname>
<<<<<<  update the licensing on a specific node.

then
# haclus -updatelic
<<<<<<  update licensing at the cluster level.
<<<<<<  NOTE: Before running haclus -updatelic, make sure that system level licensing is updated by running hasys -updatelic on all of the nodes in the cluster.

# vxdctl license init
<<<<<<  request that vxconfigd reread any persistently stored license information. this command forces vxconfigd to rescan the licenses, and to make the new licenses available.

# vxenablef -e full
<<<<<< enable licensed VxFS features

How to check the SERIAL NUMBER of a WINDOWS MACHINE ??

c:\> wmic bios get serialnumber -- > This command gives the serial number

SerialNumber
4ABDEBC

What are the different shells available in Data ONTAP 8 cluster mode and what are their uses?

There are 3 different shells available within Data ONTAP 8 cluster mode operating system.

clustershell
This is the default shell that is started when a user logs into the system. This shell was called NG shell and could be started by running 'ngsh' from BSD prompt of the system.

nodeshell
This is the shell that can be started by running the command 'system node run'. Commands can be run in node shell from clustershell by using the following syntax : 'node run <nodename> <command>'.
Node shell for any node in the cluster can be accessed from any other node. Nodeshell was known as dblade in Data ONTAP GX.

Systemshell
This is the low level shell used for advanced, diagnostic and troubleshooting purposes. Under normal circumstances systemshell should not be used without directions from NetApp Support. Systemshell is specific to a node. You may access a remote system which is in the cluster from a different node by specifying the node name. Systemshell was known as BSD shell in Data ONTAP GX and was started when root logged into the node. In order to unlock the systemshell for the diag user.

How to view and add NetBackup License keys using the command line and GUI ??

The "bpminlicense" utility manages a NetBackup license file. The preferred method to manage NetBackup licenses is to use the Help > License Keys panel in the NetBackup Administration Console.

Windows command location: %install_path%\VERITAS\NetBackup\bin\admincmd
UNIX command location: /usr/openv/netbackup/bin/admincmd

Options:
bpminlicense -add_keys
bpminlicense -delete_keys
bpminlicense -find_keys -verbose
bpminlicense -list_keys -verbose

-list_keys - Lists the keys in the NetBackup license file.

-verbose - Displays additional information to standard output.

-add_keys | -delete_keys | -find_keys keystring1 .. keystringn - Respectively, these options find and list, add, or delete one or more specified keystrings in the NetBackup license file.

GUI MODE:-

Go to Help in the Netbackup Administration Console and select option 

Add License Keys 

Note:- After applying the license key start and stop the Netbackup services and also stop the NETBACKUP DATABASE ( dbsrv11.exe)

C:\> programfiles\Veritas\Netbackup\bin> bpdown ----->  To stop the NBU services

Now go to TASK MANAGERà Processà find “dbsrv11.exe “ à End process

After this now again start the services

C:\> programfiles\Veritas\Netbackup\bin> bpup  ----->  To start the Netbackup services

Expiring Tapes in Netbackup

I have come across this error when i tried expiring my tapes 

bpexpdate  -m 000001 -d 0 

 it has thrown error  "requested media id is not assigned to this host in the emm database"

If we get this error then we need to use the below command and have HOST and MEDIA SERVER name added on to the same command.

bpexpdate -m 000001 -d 0 -host mediaservername

What is cifs.max_mpx on Netapp ??

The multiplex ID (Mid) is used along with the Pid to allow multiplexing the single client and server connection among the client's multiple processes, threads, and requests per thread. Clients may have many outstanding requests (up to the negotiated number, MaxMpxCount) at one time.Servers MAY respond to requests in any order, but a response message MUST always contain the same Mid and Pid values as the corresponding request message. The client MUST NOT have multiple outstanding requests to a server with the same Mid and Pid.

Recommended value is1124 if you use any of the following products towards CIFS shares on a filer:

• Microsoft SQL Server (before SQL 2000)


• Microsoft Exchange (before Exchange 2000)

The memory allocation on every CIFS clients will increase, however, experience shows that setting this option is completely safe.
You need to restart CIFS on the filer.

Netbackup Error 13

Error :- Error bprm (Pid - 3104) From client SERVER12 ERR_unable to backup system state or shadow copy, please check the state of VSS and associated writes

ERR - unable to backup system state or shadow copy . please check the state of VSS and associated writes INF estimate

WRN- Cant open object : shadow copy components failure occurs accessing the backup component

Media manager exited with status 90 : Media manager received no data file read failed (13)

Resolution:-  please check the state of VSS and associated Writers

vssadmin list providers --> This will show Microsoft VSS and ACRONIS ( If any THIRD PARTY VSS Found on Server )

vssadmin list writers

If found delete the registry entry of THIRD PARTY VSS

Delete the registry key with the coresponding VSS GUID value

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\

Backup

What is the DEFAULT ip address of BROCADE SWITCHES ??

Default IP Address for switches: 10.77.77.77

 Default Netmask: 255.255.255.0

Netbackup Error Code 71

Status 71 is due to none of the file exist and this can happen is different circumstances

1> If the file doesn't exist and you are trying to backup that file. Eg. If you are backing up c:\temp\nbu.txt in the backup and if the file nbu.txt is removed from that folder you will get status 71

2> If you are running a job with multi streaming on

K:\mssqldumps

Q:\Mssqldumps

And if for that server q doesn't exist it will give you that error message.

3>As you are backing up CIFS through AD server, what credentials NBU client using on AD server ?

Make sure NBU client service on AD server should be started with the credentials that has access to the cifs share. If it doesn't have access that will give you status 71

How to backup Network Drive in Netbackup ??

Requirements for backing up network shares on Windows:

1. Select 'Backup network drives' in policy attributes

2. Specify UNC path in Backup Selection

3. Change the NetBackup Client Service Logon account to a domain user with read and write permissions on the share.

Netbackup Error code 58

Best possible troubleshooting tool for status 58 is NBU bptestbpcd command.

It test port connectivity as well as forward and reverse name lookup.

Please do the following:

Create bpcd log folder on client under netbackup/logs.

Next, test from master as well as all media servers that can backup this client:

bptestbpcd -client <client-name> -verbose -debug

Output of command will prove port connectivity to client as well as forward name lookup.

bpcd log file on client will show client's attempt to resolve server's IP address to hostname, followed by comparison of resolved hostname with SERVER entries.
Next, bpcd log will show attempt back to server on either vnetd (13724) or PBX (1556), depending on NBU version.

What is ZONING ??

A zone is a specified group of fabric-connected devices, also called zone
members.

Any device, or zone member, connected to the fabric can be included in
one or more zones.

Devices can communicate only with devices that are in the same zone.
 After zoning has been enabled, if a device is not explicitly defined in a
zone that device is considered not to exist.

Devices that attach to the fabric need to be added to a new or existing
zone before their ability to communicate is enabled.

After the zone members are grouped into zones, zones are grouped into
a zone configuration and the zone configuration can then be enabled.

When enabled, the zone configuration is distributed to all switches in
the fabric and an RSCN is delivered by each switch to its local nodes.

What is the Difference between Netapp WAFL_Check and wafliron ?

WAFL_check and wafliron are both diagnostic tools used to check WAFL file systems.

If WAFL_check is run the administrator can choose whether or not to commit changes.
Wafliron will make changes as it runs and reports these changes. The administrator has no choice over which changes wafliron will commit.

wafliron can be run while the filer online and serving data from
Volume/aggregates not being checked

WAFL_check , however must be run from the Special Boot Menu
 and the storage appliance will not be serving data until WAFL_Check
completes and the administrator chooses to commit changes.

Netapp Support should be consulted before running either wafliron or WAFL_check

Note :- WAFL_Check can take long time to run and the storage appliance will not serve
any data during this time. It will remain unavailable from the network and only
be accessible from a console connection.

Troubleshooting Secure Channel Issue in WINDOWS 2008

Following is the summary of the troubleshooting and the steps taken to resolve the secure channel issue.

-Reset secure channel using nltest and reboot the server , after which the issue did not reoccur.

-We also noticed the netlogon issue mentioned that the rpc was unavailable because of which it was not able to establish a secure session. Increased the number of DNS servers in the network adapter.

-Also found that the network card drivers were outdated (v4.x). the latest were around (7.x). Have advised to update the network card drivers.

-We forced the licensing server discovery over IP so that it does not depend on DNS in an event of a dns failure.

- For the access denied problem, we confirmed that it was a issue by design after not limiting the user to a single session.

Unable to RDP to WINDOWS 2008 Server from internal client machines and getting generic error

Following is the summary of the troubleshooting and the steps taken to resolve the RDP issue.

- Tried to RDP using admin switch to localhost.

Error: Generic error.

- Ran tasklist and netstat -ano. This is to check if 3389 port listening as Terminal Services listen on port 3389.

a. Start Registry Editor.

b. Locate the following subkey in the registry, and then click Parameters:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

c. Double-click the MaxUserPort value, type 50000 (decimal) in the Value data box,

and then click OK.

d. Locate the TcpTimedWaitDelay value under the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

e. Double-click the TcpTimedWaitDelay value, type 30 in the Value data box, and

then click OK.

f. Closed registry editor and opened command prompt

g. executed these commands

netsh int tcp set global chimney=disabled

netsh int tcp set global rss=disabled

netsh int ip set global taskoffload=disabled

netsh int tcp set global autotuninglevel=disabled

netsh int tcp set global congestionprovider=none

netsh int tcp set global ecncapability=disabled

netsh int tcp set global timestamps=disabled

i. Reboot the server.

DFM error: Java.net.SocketException: No buffer space avaliable ( maximum connection reached)

NetApp Oncommand/DFM/NMC error: Java.net.SocketException: 
No buffer space avaliable ( maximum connection reached)

Permanent Solution:-
Kernel sockets leak on a multiprocessor computer that is running 
Windows Server 2008 R2 or Windows 7

http://support.microsoft.com/kb/2577795 



Temporary Solution:-

This is the error i came across OnCommand running on windows 2008 R2 server.

The solution is to increase the connection in windows 2008 server.

1) Open the windows command line and check how many ports are opened.

C:\>netsh int ipv4 show dynamicport tcp

Protocol tcp Dynamic Port Range

---------------------------------

Start Port      : 49152

Number of Ports : 16384

2) Increase the number of ports with the command

C:\>netsh int ipv4 set dynamicportrange protocol=tcp startport=5000 numberofports=60536

3) confirm again

C:\>netsh int ipv4 show dynamicport tcp

Protocol tcp Dynamic Port Range

---------------------------------

Start Port      : 5000

Number of Ports : 60536

Ports Used for Netapp

#/vol/vol0/etc/services 
#
# Network services, Internet style
#
 
ftp-data        20/tcp
ftp             21/tcp
ssh             22/tcp
telnet          23/tcp
smtp            25/tcp
time            37/tcp           # Time Service
time            37/udp           # Time Service
domain          53/udp           # DNS
domain          53/tcp           # DNS
portmap         111/udp
portmap         111/tcp
dhcps           67/udp           # DHCP server
dhcpc           68/udp           # DHCP client
tftp            69/udp
http            80/tcp
kerberos        88/udp           # Kerberos 5 
kerberos        88/tcp           # Kerberos 5 
nntp            119/tcp         
ntp             123/tcp          # Network Time Protocol
ntp             123/udp          # Network Time Protocol
netbios-name    137/udp          # NetBIOS nameserver 
netbios-dg      138/udp          # NetBIOS datagram service 
netbios-ssn     139/tcp          # NetBIOS service session 
snmp            161/udp
ldap            389/tcp          # LDAP session
https           443/tcp          # SecureAdmin/SSL
cifs-tcp        445/tcp          # CIFS over TCP with NetBIOS framing
kpasswd         464/tcp          # Filer does not listen on this port;
                                 # used as Domain Controller destination port 
                                 # for Kerberos passwd set/change operations
shell           514/tcp
syslog          514/udp
route           520/udp
ldap-ssl        636/tcp          # LDAP over SSL
kerberos-sec    750/udp          # For compatibility with older "750" clients
kerberos-sec    750/tcp          # For compatibility with older "750" clients
nfsd            2049/udp
nfsd            2049/tcp
nrv             2050/tcp         # NetApp Remote Volume protocol, used in 
                                 # FlexCache and Restore-On-Demand.
 
iscsi-target    3260/tcp
 
nlockmgr        4045/tcp         # NLM
nlockmgr        4045/udp
mountd          4046/tcp         # NFS mountd protocol
mountd          4046/udp
status          4047/tcp
status          4047/udp
pcnfsd          4048/tcp         # PCNFS protocol
pcnfsd          4048/udp
rquotad         4049/udp
 
ndmp           10000/tcp
sm-ics         10565/tcp         # Snapmirror Multipath 
snapmirror     10566/tcp         
sm-sync-block  10567/tcp         # Snapmirror Sync Block Data
sm-sync-trans  10568/tcp         # Snapmirror Sync Transaction Data
sm-sync-ctrl   10569/tcp         # Snapmirror Sync Control Data
nbu-nearstore  10571/tcp         # NetBackup - Nearstore
sm-ics-test    10670/tcp         # INTERNAL USE: Snapmirror Multipath Test
ndmp-local     32243/tcp         # Internal connection inside NetApp box

Default NAS Vendors Password

NetApp 

CLI/GUI - root, no password

EMC Celerra 

CLI/GUI - nasadmin, nasadmin

BlueArc 

SMU Web Manager - admin, nasadmin

SMU CLI - manager, nasadmin

SMU - root, nasadmin

Titan Server (CLI) - supervisor, supervisor

Isilon

CLI/GUI - root, a

LSI OnStor 

CLI/GUI - root, back-door

Upgrading Netapp Data Ontap 7.3.4 to Ontap 8.1

Use My AutoSupport to improve the Fitness of your NetApp Storage Systems - http://support.netapp.com/NOW/asuphome/

Hostname: FBTFAS01 Serial No: 123456789 Model No: FAS2040 Upgrade plan generated on: 14-Feb-2013 02:27:47 GMT  Version: 5.1.6 1

1. Upgrade Advisor Plan

This upgrade plan is based on AutoSupport received on Feb 30 16:34:53 2012

1.1. Warnings for Current OS 7.3.4 to Target OS 8.1

1.2. Upgrade Plan for upgrading from Current OS 7.3.4 to Target OS 8.1 Serial No Hostname Model No 123456789 FBTFAS01 FAS2040

Related to Warnings Description

Upgrade You should run AggrSpaceCheck Tool to verify that the system has the requisite

available free space needed to upgrade successfully to 7.3 or later (without

disabling space guarantees or offlining aggregates/volumes).

Upgrade If you are running SnapDrive software on Windows hosts connected to this filer, the

following versions are supported with ONTAP 8.1:

Note: If you are using SnapDrive with SnapManager for

Exchange/SQL/Oracle/SAP/SharePoint/Domino, please check the compatibility

between your SnapDrive and SnapManager before implementing the upgrade.

Upgrade NetApp Global Services recommends running perfstat during a typical usage time to

save a performance baseline prior to an upgrade in case it is needed. This will take

about 30 mins of run time.

Upgrade For each HA pair, you should plan for approximately 30 minutes to complete

preparatory steps, 60 minutes to perform the upgrade, and 30 minutes to complete

post-upgrade steps.

Upgrade You must ensure that CPU utilization does not exceed 50% before beginning a

NDU upgrade

Upgrade Please check the risk details for your system here that might impact your upgrade.

Upgrade This system may experience the issue described in Burt 455754, 'Boot Device may

be reformatted during Data ONTAP upgrades': 455754.

Upgrade Please check the risk details for your system here that might impact your upgrade.

Downgrade If you are running SnapDrive software on Windows hosts connected to this filer, the

following versions are supported with ONTAP 8.1:

Note: If you are using SnapDrive with SnapManager for

Exchange/SQL/Oracle/SAP/SharePoint/Domino, please check the compatibility

between your SnapDrive and SnapManager before implementing the upgrade.

Downgrade This system may experience the issue described in Burt 455754, 'Boot Device may

be reformatted during Data ONTAP upgrades': 455754.

Steps Upgrade Plan

Use My AutoSupport to improve the Fitness of your NetApp Storage Systems - http://support.netapp.com/NOW/asuphome/

Hostname: FBTFAS01  Serial No: 123456789 Model No: FAS2040 Upgrade plan generated on: 14-Feb-2013 02:27:47 GMT Version: 5.1.6 2

1 Be sure to read the Release Notes as well as the Upgrade Guide of the Data ONTAP 8.1 for

important information and technical detail before beginning your upgrade.

Before upgrading Data ONTAP, monitor CPU and disk utilization for 30 seconds by

entering the following command at the console of each storage controller:

sysstat -c 10 -x 3

The values in the CPU and Disk Util columns are strongly recommended not to exceed

50% for all ten measurements reported. Ensure that no additional load is added to the

storage system until the upgrade completes.

Download perfstat and run it on a client as follows:

perfstat -f filername -t 4 -i 5 > perfstatname.out

Save this output file for a couple of weeks after the upgrade is complete

2 Ensure all SnapDrive for Windows clients are running one of the supported versions for 8.1:

3 Download the system files for 8.1 (81_e_image.zip) from the Support Site. Be sure to

download the system files that match your node model.

If you are performing a Data ONTAP NDU (or backout), you must perform this step on

both nodes before performing the takeover and giveback steps.

4 Verify the checksum of the image file with the value on the Support site.

5 Connect to the console of the node and trigger an AutoSupport:

FBTFAS01> options autosupport.doit "starting_NDU 8.1"

6 Contact NetApp Support and check /etc/messages for any obvious errors; e.g. disk

errors, firmware errors, etc.

Using Windows: Map C$ to the Windows Host

Browse the etc folder

Open file 'messages' using WordPad. If failed disks are found, it is recommended they

be removed before upgrading.

7 Back up the etc\hosts and etc\rc files in Windows to a temporary directory.

8 Copy the system image file (81_e_image.zip) to the /etc/software directory on the node.

From a Windows box as an Administrator:

o Map the C$ share to a Windows drive letter (for example X:).

o Copy the image file to X:\etc\software

9 Install the system file via the software command:

FBTFAS01> software update 81_e_image.zip -r

If you are performing a Data ONTAP NDU (or backout), you must perform this step on

both nodes before performing the takeover and giveback steps.

10 Check to see if the boot device has been properly updated:

FBTFAS01> version -b

The primary kernel should be 8.1.

11 Terminate CIFS on the node to be taken over ( FBTFAS02 ):

FBTFAS02> cifs terminate

Use My AutoSupport to improve the Fitness of your NetApp Storage Systems - http://support.netapp.com/NOW/asuphome/

Hostname: FBTFAS01 Serial No: 123456789 Model No: FAS2040 Upgrade plan generated on: 14-Feb-2013 02:27:47 GMT Version: 5.1.6 3

12 Takeover and giveback sequence between nodes

Terminate CIFS on the node to be taken over (FBTFAS02):

FBTFAS02> cifs terminate

From FBTFAS01:, take over the data service from the partner node FBTFAS02:

FBTFAS01> cf takeover

Wait 8 minutes before proceeding to the next step.

Doing so ensures the following conditions:

- The node that has taken over is serving data to the clients.

- Applications on the clients have recovered from the pause in I/O that occurs during

takeover.

- Load on the storage system has returned to a stable point.

- Multipathing (if deployed) has stabilized.

After FBTFAS02: reboots and displays "waiting for giveback", give back the data

service:

FBTFAS01> cf giveback

Terminate CIFS on the node to be taken over ( FBTFAS01 ):

FBTFAS01> cifs terminate

From the newly upgraded node FBTFAS02, take over the data service from

FBTFAS01:

FBTFAS02cf takeover -n

Halt, and then restart the first node:

FBTFAS01> halt

FBTFAS01> bye

Wait 8 minutes before proceeding to the next step.

Doing so ensures the following conditions:

- The node that has taken over is serving data to the clients.

- Applications on the clients have recovered from the pause in I/O that occurs during

takeover.

- Load on the storage system has returned to a stable point.

- Multipathing (if deployed) has stabilized.

After the first node reboots and displays "waiting for giveback", give back the data

service:

FBTFAS02> cf giveback

Attention: The giveback is not initiated and an error message is returned if any

conditions such as the following are detected:

- open client sessions (such as CIFS sessions)

- long-running operations

- operations that cannot be restarted (such as tape backup or SyncMirror

resynchronization)

- error conditions (such as disk connectivity mismatch between the nodes)

If giveback is not initiated, complete the following steps:

Use My AutoSupport to improve the Fitness of your NetApp Storage Systems - 

http://support.netapp.com/NOW/asuphome/

Hostname: FBTFAS01 Serial No: 123456789 Model No: FAS2040 Upgrade plan generated on: 14-Feb-2013 02:27:47 GMT Version: 5.1.6 4

1.3. Backout Plan for upgrading from Current OS 7.3.4 to target OS 8.1

1. Address the condition described in the error message, ensuring that any

Identified operations are terminated gracefully.

2. Enter the cf giveback command with the -f option:

cf giveback -f

For more information about the -f option, see the cf(1) man page.

13 Verify the upgrade completed successfully to 8.1:

FBTFAS01> version

14 Upgrade FBTFAS02 (if not already done)

15 Connect to the console of the node and trigger an AutoSupport

FBTFAS01> options autosupport.doit "finishing_NDU 8.1"

Steps Backout Plan Description

1 Ensure all SnapDrive for Windows clients are running one of the supported versions for

7.3.4:

2 Download the system files for 7.3.4 (734_setup_e.exe) from the Support Site. Be sure to

download the system files that match your node model.

If you are performing a Data ONTAP NDU (or backout), you must perform this step on

both nodes before performing the takeover and giveback steps.

3 Verify the checksum of the image file with the value on the Support site.

4 Connect to the console of the node and trigger an AutoSupport using the following

command:

FBTFAS01> options autosupport.doit "Reverting to 7.3.4"

5 Contact NetApp Support and check /etc/messages for any obvious errors; e.g. disk

errors, firmware errors, etc.

Using Windows: Map C$ to the Windows Host

Browse the etc folder

Open file 'messages' using WordPad. If failed disks are found, it is recommended they

be removed before upgrading.

6 Back up the etc\hosts and etc\rc files in Windows to a temporary directory.

7 Copy the system image file (734_setup_e.exe) to the /etc/software directory on the

node. From a Windows box as an Administrator:

o Map the C$ share to a Windows drive letter (for example X:).

o Copy the image file to X:\etc\software

8 Install the system file via the software command:

FBTFAS01> software update 734_setup_e.exe -r

If you are performing a Data ONTAP NDU (or backout), you must perform this step on

both nodes before performing the takeover and giveback steps.

9 Check to see if the boot device has been properly updated:

FBTFAS01> version -b

The primary kernel should be 7.3.4.

10 Disable the data service:

FBTFAS01> cf disable

Use My AutoSupport to improve the Fitness of your NetApp Storage Systems - http://support.netapp.com/NOW/asuphome/

Hostname: FBTFAS01 Serial No: 123456789 Model No: FAS2040 Upgrade plan generated on: 14-Feb-2013 02:27:47 GMT Version: 5.1.6 5

1.4. Anomalies Plan for upgrading from Current OS 7.3.4 to target OS 8.1

11 Run the revert_to command:

FBTFAS01> revert_to 7.3.4

At the end of revert, the system will automatically halt itself and drop to a loader prompt.

Once at a loader prompt, you can issue either bye or reboot to bring the system back up

12 Reboot the node:

FBTFAS01> reboot

13 Enable the cluster (if both sides are downgraded):

FBTFAS01> cf enable

14 Verify the upgrade completed successfully to 7.3.4:

FBTFAS01> version

* Anomalies Description

1 Find the latest disk firmware for disk model X410_S15K7288A15 on Support site.

2 Find the latest disk firmware for disk model X287_HVIPC288A15 on Support site.

Netbackup Error 41 ( Network Connection Timeout )

The Error 41 is due to the below reasons


1. Network issues
2. Fragmented Drives
3. Corrupt file
4. Third-party software conflict (AntiVirus)
5. Client file system utilizing too many resources
Steps to try:

• Disable Veritas Snapshot Provider (VSP) on backup

• Disable AntiVirus

• Disable Tracker.exe

Troubleshooting

1 ) Increase the Network timeout in the client properties default value should be 300 Seconds.

2) Create 'bpbkar' directory on CLIENT and 'bptm' on MASTER SERVER.

How to check the serial number of QUANTUM SCALAR i40/i80 Tape Library

1 ) The serial number label is located on the back panel of the library. The Scalar i40 serial number is 10-digits long and starts with D0, for example D0H0029914. A Scalar i80 serial number is also 10-digits long and starts with D1.

2 ) From the local operator panel user interface, select Reports > About Library.

The serial number is located to the right of the Serial # field

3 ) From the remote web client user interface, select Reports > System Information.

The serial number is located in the Physical Library section.