Clustered ontap…8.2RC1 is here!

NetApp has posted 8.2RC1 which as a lot of new interesting features, one of which I am very eager to try, QoS for storage!  You can limit iOPs and such by volume.

But first, we are going to look at the upgrade steps.  Page 33 of the 8.2RC1 Documentation lists the 3 different states the software can be within your cluster:

1.  Download but not install

2.  Install a previously downloaded image

3.  Download & install in 1 step.

As we look at our current images:

kitt::system node image> show
Is Is Install
Node Image Default Current Version Date
——– ——- ——- ——- ————————- ——————-
kitt-01
image1 false false 8.0.2P4 9/17/2012 04:31:04
image2 true true 8.1.2 1/12/2013 07:54:56
kitt-02
image1 true true 8.1.2 12/3/2012 02:39:30
image2 false false 8.0.2P4D7 11/18/2012 04:00:00

We are in an interesting, but education state with a different version of the backup image than each other.

Now we will download + install the image to both nodes:

 

kitt::system node image> update -node -package http://10.3.3.44/DOT/82RC1_q_image.tgz -replace-package true

Error: Missing value for -node.

kitt::system node image> update -node * -package http://10.3.3.44/DOT/82RC1_q_image.tgz -replace-package true
Software update started on node kitt-01. Updating image1 package: http://10.3.3.44/DOT/82RC1_q_image.tgz current image: image2
Downloading package. This may take up to 10 minutes.
96% downloaded
Download complete.
Listing package contents.
Decompressing package contents.
Invoking script (validation phase).
INSTALL running in check only mode
Mode of operation is UPDATE
Current image is image2
Alternate image is image1
Package MD5 checksums pass
Versions are compatible
Available space on boot device is 753 MB
Required space on boot device is 290 MB
Kernel binary matches install machine type
Invoking script (install phase). This may take up to 30 minutes.
Mode of operation is UPDATE
Current image is image2
Alternate image is image1
Package MD5 checksums pass
Versions are compatible
Available space on boot device is 753 MB
Required space on boot device is 290 MB
Kernel binary matches install machine type
Getting ready to install image
Syncing device…
Extracting to /cfcard/x86_64/freebsd/image1…
x BUILD
x CHECKSUM
x COMPAT.TXT
x INSTALL
x VERSION
x cap.xml
x fw.tgz
x kernel
x metadata.xml
x perl.tgz
x platform.ko
x platfs.img
Installed MD5 checksums pass
Installing diagnostic and firmware files
Firmware MD5 checksums pass
Installation complete. image1 updated on node kitt-01.

Software update started on node kitt-02. Updating image2 package: http://10.3.3.44/DOT/82RC1_q_image.tgz current image: image1
Downloading package. This may take up to 10 minutes.
96% downloaded
Download complete.
Listing package contents.
Decompressing package contents.
Invoking script (validation phase).
INSTALL running in check only mode
Mode of operation is UPDATE
Current image is image1
Alternate image is image2
Package MD5 checksums pass
Versions are compatible
Available space on boot device is 753 MB
Required space on boot device is 290 MB
Kernel binary matches install machine type
Invoking script (install phase). This may take up to 30 minutes.
Mode of operation is UPDATE
Current image is image1
Alternate image is image2
Package MD5 checksums pass
Versions are compatible
Available space on boot device is 753 MB
Required space on boot device is 290 MB
Kernel binary matches install machine type
Getting ready to install image
Syncing device…
Extracting to /cfcard/x86_64/freebsd/image2…
x BUILD
x CHECKSUM
x COMPAT.TXT
x INSTALL
x VERSION
x cap.xml
x fw.tgz
x kernel
x metadata.xml
x perl.tgz
x platform.ko
x platfs.img
x rootfs.img
Installed MD5 checksums pass
Installing diagnostic and firmware files
Firmware MD5 checksums pass
Installation complete. image2 updated on node kitt-02.

2 entries were acted on.

kitt::system node image>

Image installed, now we verify:

kitt::system node image> system node image show-update-progress -node *
There is no update/install in progress
Status of most recent operation:
Run Status: Exited
Exit Status: Success
Phase: Run Script
Exit Message: Installation complete. image1 updated on node kitt-01.
There is no update/install in progress
Status of most recent operation:
Run Status: Exited
Exit Status: Success
Phase: Run Script
Exit Message: Installation complete. image2 updated on node kitt-02.
2 entries were acted on.

kitt::system node image> system node image show
Is Is Install
Node Image Default Current Version Date
——– ——- ——- ——- ————————- ——————-
kitt-01
image1 false false 8.2RC1 4/16/2013 04:37:16
image2 true true 8.1.2 1/12/2013 07:54:56
kitt-02
image1 true true 8.1.2 12/3/2012 02:39:30
image2 false false 8.2RC1 4/16/2013 04:42:36
4 entries were displayed.

 Next we are supposed to check out snapmirror relationships and current jobs:

kitt::system node image> job show
Owning
Job ID Name Vserver Node State
—— ——————– ———- ————– ———-
1 Certificate Expiry Check
kitt – Queued
Description: Certificate Expiry Check
2 CLUSTER BACKUP AUTO 8hour
kitt – Queued
Description: Cluster Backup Job
3 CLUSTER BACKUP AUTO daily
kitt – Queued
Description: Cluster Backup Job
4 CLUSTER BACKUP AUTO weekly
kitt – Queued
Description: Cluster Backup Job
5 Vol Reaper kitt – Queued
Description: Vol Reaper Job
5 entries were displayed.

kitt::system node image> job delete *
5 entries were acted on.

kitt::system node image> job show
This table is currently empty.

 These queued jobs are expected due to the nature of this being a lab that is spun up and spun down on demand.

kitt::system node image> storage failover show -auto-giveback false -instance

Node: kitt-01
Partner Name: kitt-02
Node NVRAM ID: 118045084
Partner NVRAM ID: 118049824
Takeover Enabled: true
Takeover Possible: true
Reason Takeover not Possible: –
Interconnect Up: true
Interconnect Links: VIA Interconnect is up (link 0 down, link 1 up)
Interconnect Type: Infiniband ( Mellanox Arbel )
State: connected
Partner State: Up
Time Until Takeover: –
Reason Takeover not Possible by Partner: –
Auto Giveback Enabled: false
Auto-Abort Operations Enabled: false
Check Partner Enabled: true
Takeover Detection Time (secs): 15
Takeover on Panic Enabled: true
Takeover on Reboot Enabled: true
Delay Before Auto Giveback (secs): 600
Hardware Assist Enabled: true
Partner’s Hwassist IP: 10.3.3.102
Partner’s Hwassist Port: 4444
Hwassist Health Check Interval (secs): 180
Hwassist Retry Count: 2
Hwassist Status: active
Time Until Auto Giveback (secs): –
Local Mailbox Disks: 7a.00.0, 7a.00.1
Partner Mailbox Disks: 5c.12.0, 5c.12.1
Missing Disks on Local Node: None
Missing Disks on Partner Node: None
Auto Giveback After Takeover On Panic: true

 Some steps have been omitted, refer to the upgrade guide for more detail.

Here is what it looked like rebooting 1 of the nodes:

kitt::system node image> reboot -node kitt-01
(system node reboot)

Warning: Are you sure you want to reboot the node? {y|n}: y

login: Waiting for PIDS: 618.
Waiting for PIDS: 595.
.
Uptime: 2h35m50s
System rebooting…

Phoenix TrustedCore(tm) Server
Copyright 1985-2005 Phoenix Technologies Ltd. All Rights Reserved
Portions Copyright (c) 2005-2009 NetApp All Rights Reserved
BIOS Version: 1.9.0
CPU= AMD Opteron(tm) Processor 852 X 4
Testing RAM.
512MB RAM tested
32768MB RAM installed
Fixed Disk 0: NACF1GBJU-A11
Boot Loader version 1.8
Copyright (C) 2000-2003 Broadcom Corporation.
Portions Copyright (C) 2002-2009 NetApp

CPU Type: AMD Opteron(tm) Processor 852

Note: The system will install firmware version 1.10.0 in 5 seconds.
Type Ctrl-C now to skip firmware installation.

Updating firmware now.

Warning: Do not power off the system until the update is complete.

New BIOS Version: 1.10.0
New Loader Version: 1.9
Saving Primary Image to Secondary
Updating Secondary Boot Flash
Programming .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+ done. 2031616 bytes written
Updating Primary Boot Flash
Programming .+.+.+.+.+.+.+.+.+.+.+.+.+.+ done. 917504 bytes written

Firmware update is complete.
System rebooting…

So far so good, but we are about to find out a minor surprise…..