February 5, 2012

You are here: Home / Uncategorized

NetApp Setup Guide

October 5, 2010 By 1 Comment

I’ve had this posted for awhile on my NetApp Reference Page at the top but I wanted to move it into a post for the permalink to this, hence the post.

Setup Guide for NetApp Installs

Pre-Install: Infrastructure

  • Ensure physical cabling done (Verified the appropriate amount of ethernet/FC switch ports are available and the cables have been run to the location the NetApp will reside)
    • Ethernet
      • Management port cable run (1 per head)
      • IP address to use for management port(s)
      • Ethernet port(s) cable(s) run (varies per configuration)
      • Document all IP addresses that will be assigned to interfaces
      • Ethernet switches configured properly and relevant information sent to implementation engineer
        • Jumbo frames if required
        • EtherChannel configuration if required
        • Necessary vlans configured
    • Fibre Channel
      • Cables run (varies per configuration)
      • Appropriate zoning done on switches
    • Power available

Pre-Install: Administrative

  • Document contact info for all parties involved (technical resources, project managers, etc)
  • Document address for where the NetApp controller(s) will be located
  • Document licenses for all protocols
  • Document hostname(s) to use for NetApp controller(s)
  • Document the following information and verify compatibility with support matrix
    • For all hosts connecting to the NetApp via a FC/iSCSI connection
      • OS Version (eg Windows Server 2003 R2 Standard x86)
      • HBA Models
        • Current driver version
        • Current firmware version
      • MPIO version
      • Host Utilities Kit version
      • SnapDrive version
    • FC Switches
      • Switch model(s)
      • Firmware version
    • ONTAP version

Install: Administrative

  • Register customer info on NOW site
  • Obtain, document and install all software licenses

Install: Upgrade to Latest Versions

  • Upgrade ONTAP to latest
  • Upgrade RLM/BMC to latest
  • Upgrade system firmware to latest
  • Upgrade disk firmware to latest
  • Upgrade shelf firmware to latest

Install: Initial Setup Best Practices

  • Configure RLM/BMC
  • Configure SSH
options ssh.access "host=host1,host2 AND if=e0"
  • Disable telnet
  • Configure SSL
  • Disable HTTP
  • Configure AutoSupport
  • Configure NTP/timed
options timed.log on
options timed.proto ntp
options timed.servers 0.us.pool.ntp.org,1.us.pool.ntp.org,2.us.pool.ntp.org
options timed.sched 1h
options timed.window 5m
options timed.max_skew 3h
options timed.log off
  • Adjust aggregate snap reserve (if necessary)
snap reserve -A aggr0 0
  • Set RAID group size appropriately
  • Assign odd disks to 1st head and even disks to 2nd head
    • Ensure appropriate spare disks are kept
  • Resize vol0
    • Set to 20g for smaller filers and 50g for larger filers
  • Set ucode options on vol0 (new volumes will inherit this option)
vol options vol0 create_ucode on
vol options vol0 convert_ucode on
  • Set appropriate security style for vol0 (unix or ntfs)

options wafl.default_security_style unix (or ntfs)

Install: Protocol Configuration

Configure NFS:

  • Disable auto export of NFS volumes
options nfs.export.auto-update off

Configure iSCSI:

  • Disable iSCSI on unused interfaces/vifs
iscsi interface disable vif1
  • Disable protocols on ethernet ports if required (7.3 and later)
options interface.blocked.cifs e5b
options interface.blocked.nfs e1a,e1b
options interface.blocked.iscsi e5b
options interface.blocked.cifs "" (undoes the previous restriction)
  • Disable WINS on unnecessary interfaces (-wins on ifconfig)

Configure CIFS:

  • Make sure snapshots are visible from CIFS clients
options cifs.show_snapshot on
  • Make sure the previous versions tab is integrated
options cifs.ms_snapshot_mode xp
  • Disable default home share

Install: Add on Software Configuration

Installing SnapDrive

  • Install necessary patches
  • Install .NET
  • Install Host Utilities Kit

Install: Verify Configuration

Post Install: Test Plan

  • Verify data is still accessible after the following hardware failures
    • Shelf
    • Path (fcadmin offline 0a)
    • Switch
    • ESH
    • Controller
  • Verify MPHA
storage show disk -p
  • Perform a cf takeover and giveback and ensure no issues
  • Test AutoSupport and ensure configured users are receiving email
  • Ensure all vif interfaces have a partner interface (cf-config-check.cgi will detect this)
  • ifconfig -a and ensure all necessary interfaces are up, speed/duplex settings are correct

Popularity: 43% [?]

Filed Under: Featured, NetApp, ONTAP, Uncategorized

Configuring ASDM on Cisco PIX 515

June 6, 2010 By 2 Comments

Not being a day to day Cisco guy I thought I’d throw this up on my blog, mostly for my future reference.  I currently am running PIX OS 7.0(1) and wanted to run ASDM to make configuring my client VPN access easier.

The steps for installing ASDM are pretty easy:

PRD-FW1# copy tftp flash

Enter your tftp server and asdm file name

PRD-FW1(config)# asdm image flash:/asdm-524.bin

PRD-FW1(config)# wr mem

Then to allow the http access:

PRD-FW1(config)# http server enable

PRD-FW1(config)# http 0 0 inside

I initially installed ASDM version 5.24, it copied to flash fine but when I tried to run the following command it gave me an error:

PRD-FW1(config)# asdm image flash:asdm-524.bin

It returned an error saying “Device Manager image set, but not a valid image file flash:asdm-524.bin” If I ran a show run it did show the asdm image, and I did get the webpage to sucessfully load when accessing it from internally but nothing would happen.  My next step was to take the MS approach to troubleshooting and try a reload before pulling my hair out but that didn’t solve anything.

At this point I thought maybe I had an issue with the asdm-524.bin file and I decided to try asdm-512.bin which gave me the same exact problem.  After some searching I realized the ASDM version is apparently tied to the PIX OS version and I needed to use a version like asdm-502.bin

Now I was able to sucessfully run the “asdm image flash:asdm-502.bin” command, but my next problem was that the ASDM Launcher wouldn’t do anything after I logged in and the webpage would just sit at a screen that said “Do not close this window”.

To fix that I found I needed to have a much older version of Java, I needed version 6 update 7 x86 version After I only had that version on my laptop I was able to connect to ASDM successfully.

Popularity: 12% [?]

Filed Under: Home Lab, Networking, Uncategorized Tagged With: , ,

option lun.partner_unreachable.default-partner.behavior: Value must be ‘drop’, ‘error’, or ‘start’ logged periodically to the console

January 13, 2010 By Leave a Comment

You may see this options logged to the system console, the cause of this message is that the value for ‘options lun.partner_unreachable.default-partner.behavior‘ is set to ‘unknown‘ in the /etc/registry.local file.

This file is read by ONTAP at certain times which will cause this error to be repeated. Run ”options lun.partner_unreachable.default-partner.behavior drop‘ to resolve this issue.

NetApp Bug Link (NOW Account Required)

Popularity: 7% [?]

Filed Under: Uncategorized Tagged With: , ,

NetApp 64 bit Aggregates in ONTAP 8.0

January 6, 2010 By 1 Comment

Some notes from some ONTAP 8 training I went to:

One of the features in the new version of Data ONTAP 8.0 is the ability to use 64 bit aggregates, prior to this all aggregates were 32 bit.  The main reason to use a 64bit aggregate is to break the 16TB aggregate limit found in 32 aggregates.

ONTAP 7.3 helped with this in that it changed the way the 16TB was calculated, it no longer counted the parity drives in the 16TB which gave you an extra ~20% usable space in your aggregates (actual savings varied based on disk size).  As mentioned before, to expand beyond the 16TB a 64 bit addressing scheme needed to be used, the following shows the limit of either aggregate type:

32 bit aggregates are calculated by 2^32 * 4KB = ~16TB
64 bit aggregates are calculated by 2^64 * 4KB = ~67,108,864 (67 million petabytes)
Note: There are limits to the maximum sizes of 64 bit aggregates which are based on controller model

Those limits are currently:

FAS6080 100TB
FAS6040/FAS3170 70TB
FAS3160/FAS3070 50TB
FAS3140/FAS3040/FAS3050 40TB

A few things to note with that are that the maximum file/LUN size is still 16TB and that the maximum volume sizes for dedupe volumes remains the same.

When sizing your system keep in mind that the root aggregate must be 32 bit, it is also important to note that you cannot currently convert a 32 bit aggregate into a 64 bit aggregate (or vice versa).  The next major release of ONTAP 8 will have the ability to convert 32 bit to 64 bit non-disruptively however.

Along the same lines, you cannot perform block level transfers between aggregate types – Volume SnapMirror(VSM) between 32 bit and 64 bit aggregates will not work.  (Qtree SnapMirror(QSM) however will work as it is file based, as will NDMP)

The default type for creating new aggregates is 32 bit, for 64 bit you need to specify a -B 64 if using CLI or select the checkbox if using FilerView.  After upgrading to ONTAP 8.0 7-mode all existing aggregates will remain 32 bit (as mentioned before you cannot non-disruptively convert them yet to 64 bit)

Popularity: 38% [?]

Filed Under: Uncategorized Tagged With: , ,

SnapManager 6.0 for Exchange Released

December 22, 2009 By Leave a Comment

From NOW Site: SnapManager 6.0 for Microsoft Exchange introduces the following new capabilities:

  • Support for backup, restore, and verification for Microsoft Exchange 2010
  • SnapManager and Single Mailbox Recovery integration
  • Enhanced Exchange Business Continuance Module
  • Support for SnapDrive® 6.1 and SnapDrive® 6.2
  • Enhanced dataset and SnapVault integration

The functionality for dataset and SnapVault integration with SnapManager is available only if you are using Data ONTAP 7.3 RC2 or later. Obviously Exchange 2010 support is the biggest new feature although integrating SMBR into SME is a nice plus as well, will hopefully have a blog post with some screenshots of it soon.

Link to download (Requires NOW account)

Popularity: 10% [?]

Filed Under: NetApp, SnapManager for Exchange, Uncategorized Tagged With: , ,

Cascading SnapMirror, removing the middle NetApp

October 30, 2009 By Leave a Comment

Recently had a customer who had a SnapMirror relationship between their primary filer in their datacenter and a filer in their DR location.  The link between the two was very slow and  we were upgrading the filer in the DR site.  The customer was concerned about having to re-baseline and send all of the volume data over the WAN as it would take weeks to complete.  The other option was to bring the new filer to the production site and initialize the SnapMirror relationship and move it back to the DR site after the initial transfer.  Due to other factors this wasn’t an option either.

As it turns out, with SnapMirror this is actually a painless process.  The layout was something like this:

cascade_snapmirror

Say for example that filer1 transfers to filer2 at the top of every hour, I setup a SnapMirror between filer2 and filer3 to kick off at :30 after the hour.  The process was something like this:

snapmirror update snapvol on filer2 to send any changes since the last SnapMirror

snapmirror quiesce snapvol on filer2 to make the SnapMirror relationship idle

snapmirror update snapvol on filer3 to send the changes from filer2 to filer3

snapmirror quiesce snapvol on filer3 to make the SnapMirror relationship idle

snapmirror break snapvol on filer2

snapmirror break snapvol on filer3

Update the snapmirror.conf file on filer3 so that it is going from filer1 to filer3 now

snapmirror resync snapvol Resync the broken SnapMirror relationship with filer1 and filer3

snapmirror update snapvol Send any changes from filer1 snapvol to filer3 snapvol

Popularity: 3% [?]

Filed Under: Uncategorized Tagged With: ,

SnapManager for SQL Scheduled Backups

September 30, 2009 By 1 Comment

One thing I have noticed about SMSQL backups scheduled through Windows scheduled tasks:

When you go through the backup wizard in SMSQL you will specify the databases you currently have that you want to be backed up and it will create a scheduled task for you (either SQL agent or Windows scheduled task).

If you add a new database to the SQL server later it will *not* be included in your existing backup sets.  If you want the backup to always include new databases you will need to modify the scheduled task.

Here is an example of a scheduled task command after running through the backup wizard:

"C:\Program Files\NetApp\SnapManager for SQL Server\SMSQLJobLauncher.exe" new-backup  –svr ‘<Server Name>’  -d  ‘<Server Name>’, ’6′, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’, ‘<Database Name>’ -RetainBackups  5 -lb -bksif -RetainSnapofSnapInfo 0 -trlog  –mgmt daily

Modify the run command so it looks like this:

"C:\Program Files\NetApp\SnapManager for SQL Server\SMSQLJobLauncher.exe" new-backup  –svr ‘<Server Name>’’  -RetainBackups  5 -lb -bksif -RetainSnapofSnapInfo 0 -trlog  –mgmt daily

Now any new database added will automatically be included the next time that backup job is executed

Popularity: 12% [?]

Filed Under: Uncategorized Tagged With: , ,

NetApp PerfStat with Mac OSX Leopard

February 9, 2009 By Leave a Comment

By default the PerfStat tool that is on the NetApp NOW site does not run under Mac OSX Leopard, and it will return an error that says: “Unsupported client OS”

I did a little searching and found that someone on the Nabble site had posted a ‘patched’ version of the script to use, but it doesn’t seem like you need to do that. I edited the existing script, found this section:

# Verify the OS platform
os=`uname -s`
case $os in
SunOS) ;;
OSF1) ;;
HP-UX) ;;
Linux) ;;
AIX) ;;
FreeBSD) ;;
OpenBSD) ;;
*)
echo “Error: Unsupported client OS: $os”
exit 1
;;
esac

And changed it to read:

# Verify the OS platform
os=`uname -s`
case $os in
SunOS) ;;
OSF1) ;;
HP-UX) ;;
Linux) ;;
AIX) ;;
FreeBSD) ;;
OpenBSD) ;;
Darwin) ;;
*)
echo “Error: Unsupported client OS: $os”
exit 1
;;
esac

After that I run the following command from terminal.app

sudo sh perfstat.sh -f toaster1 -t 30 -i 46 > perfstat.out


Adjust the settings accordingly.

Popularity: 3% [?]

Filed Under: Uncategorized Tagged With: , , ,

VMware Lab Manager – Remove Orphaned VMs

April 21, 2008 By Leave a Comment

If you use VMware Lab Manager and Virtual Center you have probably noticed a lot of orphaned virtual machines within your VI Client.

VMware has a tool you can install on your Lab Manager server to automatically clean up these orphans.

  • Download the tool from here (you will need to rename the extension to .msi) and install it on the Lab Manager server.
  • Open a command prompt and change your current working path to C:\Program Files\VMware\VMware Lab Manager Server\Tools\RemoveOrphanedVMs
  • Run the following: removeorphanedvms -h <virtualcenterserver>:<port 443 is the default> -u <username> -p <password> -t -v
    • Note the with the -t option it won’t actually remove any machines, it will print out to the screen the names of the machines it thought were orphans and the total amount it found.
  • Setup a scheduled task to have this run automatically in your environment if preferred.

Popularity: 4% [?]

Filed Under: Uncategorized Tagged With: , ,

Pass Through Authentication with the VMware VI Client

March 10, 2008 By 1 Comment

This seems to be a lesser known option, but if you want to pass through your domain credentials to the Virtual Center server add the following at the end of the VI Client shortcut.

-passthroughAuth -s


Popularity: 1% [?]

Filed Under: Uncategorized Tagged With: , , , ,
« Older Posts