NetApp System Manager 2.0 Public Beta

System Manager 2.0 enables you to manage multiple storage systems and storage elements such as disks, volumes, and aggregates. It provides a Web-based graphical management interface to manage common storage system functions from a Web browser.

You can perform tasks such as:

- Configure and manage storage elements such as disks, aggregates, volumes, LUNs, qtrees, and quotas.
- Configure protocols such as CIFS and NFS and provision file sharing.
- Configure protocols such as FC and iSCSI for block access.
- Create vFiler units and manage them.- Set up SnapMirror relationships and manage SnapMirror tasks.- Manage HA configurations and perform takeover and giveback.
- Monitor and manage your storage systems.

Note: The Public Beta program is open to all existing NetApp customers. The Beta version of NetApp System Manager 2.0 software has to be installed only on non-production environments. Beta has a limited support on NetApp communities only.

http://communities.netapp.com/groups/netapp-system-manager-20-public-beta

NetApp System Manager 2.0 Tutorials
http://communities.netapp.com/docs/DOC-10703

Disk drive in BYP (disk bypass) status

What are Drive Bypass Events?

fcal link_stats report BYP status.

Example:
localhost> fcstat device_map
Loop Map for channel 4a:
Translated Map: Port Count 28
7 29 27 26 25 24 23 22 21 20 19 18 17 16 45 44
43 42 41 40 39 38 37 36 35 34 33 32
Shelf mapping:
Shelf 1: 29 BYP 27 26 25 24 23 22 21 20 19 18 17 16
Shelf 2: 45 44 43 42 41 40 39 38 37 36 35 34 33 32

This means that the disk id 28 has been bypassed.

Drive bypass events are situations which cause the ESH to bypass a drive port thus making it inaccessible by the host and isolating the drive from the loop. There are primarily two different kinds of drive Bypass Events:
Threshold Bypasses - Situations where the ESH detects that a certain kind of error is occurring for a specific period of time and the determination is made to bypass the port because of accumulated errors over time or over the amount of data flowing through the loop.
Policy Bypasses - Situations where the ESH detects a critical problem and bypasses a drive in order to maintain the integrity of the loop. This might be a "situational" problem which later clears, but once a drive is bypassed, it will remain bypassed until manually cleared by removing and reseating the drive, or by power cycling of the shelf.
Self Bypasses - The hard drive electronics determine that the internal circuitry cannot function properly anymore. Thus the drive itself calls to be removed from the loop.

EMC VNX/ Isilon Spec Sheet

VNXe series -- http://www.emc.com/products/series/vnxe-series.htm#/1

VNX series -- http://www.emc.com/products/series/vnx-series.htm#/1

VNX Gateway -- http://www.emc.com/products/series/vnx-series-gateways.htm#/1

Isilon S-series -- http://www.isilon.com/s-series

Isilon X-series -- http://www.isilon.com/x-series

Isilon NL-series -- http://www.isilon.com/nl-series

General Availability of Data ONTAP 8.0.1 7-Mode

Supported Platforms

Data ONTAP 8.0.1 7-Mode GA release is supported on the following platforms:

FAS/V62x0

FAS/V60x0

FAS/V32x0

FAS/V31x0

FAS/V3070

FAS/V3040

FAS2040

SA series

https://now.netapp.com/NOW/products/cpc/cpc1101-04.shtml
 

NetApp - Changing Gateway Settings

1. SSH to controller 1.
2. Type 'rdfile /etc/rc'
3. Copy the contents of the /etc/rc output to notepad. (Might want to save this to a file for safe keeping)
   1. Example
        1.hostname bob
           ifconfig e0a `hostname`-e0a mediatype auto flowcontrol full netmask 255.255.255.0 partner e0a
           ifconfig e0b `hostname`-e0b mediatype auto flowcontrol full partner e0b
           ifconfig e0c `hostname`-e0c mediatype auto flowcontrol full partner e0c
           route add default 1.1.1.1 1
           routed on
           options dns.domainname bob.local
           options dns.enable on
           options nis.enable off
           savecore
 
4. Change the notepad contents for the default route statement.
     1. Example
            1.hostname bob
           ifconfig e0a `hostname`-e0a mediatype auto flowcontrol full netmask 255.255.255.0 partner e0a
           ifconfig e0b `hostname`-e0b mediatype auto flowcontrol full partner e0b
           ifconfig e0c `hostname`-e0c mediatype auto flowcontrol full partner e0c
           route add default 2.2.2.2 1
           routed on
           options dns.domainname bob.local
           options dns.enable on
           options nis.enable off
           savecore
5. Make sure you get this right or your system won't boot. Copy the contents of the modified file to your clipboard.
6. In the SSH session type 'wrfile /etc/rc'
7. Paste the contents of your buffer into the SSH session.
8. Press Ctrl+C to quit the editor.
9. Verify, type 'rdfile /etc/rc' and make sure there are no extra line breaks or truncations.
10. Type 'route delete default'
11. Type 'route add default 2.2.2.2 1'
12. SSH to controller 2.
13. Repeat steps abvove

Netapp Snapvault : Transfer aborted: destination qtree is not coalesced

If you are working with NetApp SnapVault backups then at times  you'll experience one of the issue with "qtree is not coalesced". SnapVault update command will fail unless you poke the backup relationship with "Snapvault start " as below: (this will re-initiate the backup from its most recent checkpoint)

filer:/vol/source_vol/source_qtree dr_filer:/vol/dest_vol/dest_qtree Uninitialized - Idle with restart checkpoint (at 196 GB)


[root@cherrytop etc]# rsh dr_filer snapvault update dr_filer:/vol/dest_vol/dest_qtree 
 Transfer aborted: destination qtree is not coalesced.


[root@cherrytop etc]# rsh dr_filer snapvault start -S  filer:/vol/source_vol/source_qtree dr_filer:/vol/dest_vol/dest_qtree
Transfer started.
Monitor progress with 'snapvault status' or the snapmirror log.


filer:/vol/source_vol/source_qtree dr_filer:/vol/dest_vol/dest_qtree Uninitialized - Transferring (196 GB done)

What are the deduplication maximum volumes sizes and deduplication maximum total data limits for Data ONTAP 8.0.1?

https://kb.netapp.com/support/index?page=content&id=3010088

Bits and Bytes Calculator

I found this really useful when you have many remote sites and DR used alongside with backup solution.

http://www.speedguide.net/conversion.php

It also includes bandwidth reference table. 

When do we use the bye, halt, and reboot commands?

-- The bye command works at the ok prompt (ok>) to reboot the filer
-- The halt command works at the at filer prompt, it terminates all services (example: CIFS) and brings the filer to the ok prompt (ok>)
-- The reboot command works at the filer prompt (filer1>) to reboot the filer

Using the halt and bye command 
cherrytop#> halt
 CIFS local server is shutting down... 
CIFS local server has shut down...
Tue Aug 3 15:57:01 PDT [kern.shutdown:notice]: System shut down because : "halt".
Tue Aug 3 15:57:01 PDT [iscsi.service.shutdown:info]: iSCSI service shutdown
Program terminated
ok reboot (shows that reboot only works from the filer prompt)
reboot ?
ok bye

Intel Open Firmware by FirmWorks
Copyright 1995-2004 FirmWorks, NetApp. All Rights Reserved.
Firmware release 4.2.3_i1
Press Del to abort boot, Es

Memory size is 512 MB
Testing SIO
Testing LCD
Probing devices
Testing 512MB
256 to 320MB
Skipping further tests
Complete
Finding image...
Loading isa floppy
Floppy not first boot disk
No floppy disk found.

Booting from fcal
Loading /pci2/fcal@7/disk@10
100%
Starting Press CTRL-C for special boot menu

Using the reboot command
cherrytop#> bye (shows that bye only works at the ok prompt)bye not found. Type '?' for a list of commands cherrytop#> reboot
CIFS local server is shutting down... 
CIFS local server has shut down...
Tue Aug 3 16:46:01 PDT [kern.shutdown:notice]: System shut down because : "rebo
ot".
Tue Aug 3 16:46:01 PDT [iscsi.service.shutdown:info]: iSCSI service shutdown

Intel Open Firmware by FirmWorks
Copyright 1995-2004 FirmWorks, NetApp. All Rights Reserved.
Firmware release 4.2.3_i1
Press Del to abort boot, Esc to skip POST 
Memory size is 512 MB

Note:In a clustered configuration, running the "reboot" command on a node does not cause a CF takeover implicitly. It starts a 90 second counter that allows the rebooted node time to come back online before attempting a takeover. This timer can be monitored with "cf status" while the partner node is rebooting.

Data ONTAP 8.0.1 7-Mode and later releases - enhancements

Data ONTAP 8.0.1 7-Mode and later releases provide improved performance, resiliency, and management capabilities for storage resources.

Support for 64-bit aggregates:
In Data ONTAP 8.0 7-Mode and later releases, Data ONTAP supports a new type of aggregate, the 64-bit aggregate. 64-bit aggregates have a larger maximum size than aggregates created with earlier versions of Data ONTAP. In addition, volumes contained by 64-bit aggregates have a larger maximum size than volumes contained by aggregates created with earlier versions of Data ONTAP.

Upgrading to Data ONTAP 8.0.1 increases volume capacity after deduplication:
After you upgrade to Data ONTAP 8.0.1 and later from an earlier release of Data ONTAP, you can increase the deduplicated volume size up to 16 TB. 

Maximum simultaneous FlexClone file or FlexClone LUN operations per storage system:
Starting with Data ONTAP 8.0 7-Mode, you can simultaneously run a maximum of 500 FlexClone file or FlexClone LUN operations on a storage system.
 
File space utilization report:
The file space utilization report enables you to see the files and the amount of space that they occupy in a deduplicated volume. You can choose to either move or delete the files to reclaim the space.

Increased maximum RAID group size for SATA disks:
Starting in Data ONTAP 8.0.1, the maximum raid group size allowed for ATA, BSAS, and SATA disks has increased from 16 to 20 disks. The default size remains the same, at 14 disks.

FlexClone files and FlexClone LUNs support on MultiStore:
In Data ONTAP 7.3.3 and later releases of the 7.x release family, and in Data ONTAP 8.0.1 and later, the FlexClone files and FlexClone LUNs commands are available in the default and nondefault vfiler contexts.