Creating an aggregate
You create an aggregate to provide disk space to one or more FlexVol volumes (or one traditional volume).
Before You Begin
Determine the name of the aggregate. Aggregate names must conform to the following requirements:
• Begin with either a letter or an underscore (_)
• Contain only letters, digits, and underscores
• Contain no more than 250 characters
Note: You can change the name of an aggregate later by using the aggr rename command.
Determine what disks will be used in the new aggregate. You can specify disks by listing their IDs, or by specifying a disk characteristic such as speed or type. You can display a list of the available spares on your storage system by using the aggr status -s command.
Enter the following command:aggr create aggr_name [-f] [-m] [-n] [-t {raid4|raid_dp}] [-r raidsize] [-T disk-type] -R rpm] [-L] disk-list
aggr_name is the name for the new aggregate.
-f overrides the default behavior that does not permit disks in a plex to belong to different disk pools. This option also allows you to mix disks with different RPM speeds even if the appropriate raid.rpm option is not off.
-m specifies the optional creation of a SyncMirror-replicated volume if you want to supplement RAID protection with SyncMirror protection. A SyncMirror license is required for this feature.
-n displays the results of the command but does not execute it. This is useful for displaying the disks that would be automatically selected prior to executing the command.
-t{raid4 | raid_dp} specifies the level of RAID protection you want to provide for this aggregate. If no RAID level is specified, the default value (raid_dp) is applied.
-r raidsize is the maximum size of the RAID groups for this aggregate. If no size is specified, the default is used.
-T disk-type specifies one of the following types of disk to be used: ATA, SATA, SAS, or FCAL. This option is only needed when creating aggregates on systems that have mixed disks. Use FCAL for FC disks, ATA for ATA disks connected via FC-AL, SATA for SAS-attached ATA disks, and SAS for SAS-attached SAS disks.
Note: FCAL and SAS disks are considered to be the same type for the purposes of creating an aggregate. Similarly, ATA and SATA disks are considered to be the same type.
-R rpm specifies the type of disk to use based on its speed. Valid values for rpm include 5400, 7200, 10000, and 15000.
-L creates a SnapLock aggregate. For more information, see the na_aggr(1) man page or the Data Protection Online Backup and Recovery Guide.
disk-list is one of the following values:
• ndisks[@disk-size]
ndisks is the number of disks to use. It must be at least 3 for RAID-DP aggregates or 2 for RAID-4 aggregates.
disk-size is the disk size to use, in gigabytes.
• -d disk_name1 disk_name2... disk_nameN
disk_name1, disk_name2, and disk_nameN are disk IDs of available disks; use a space to separate disk IDs.
Examples
The following command creates an aggregate called newaggr, with a RAID group size of 8, consisting of the disks with disk IDs 8a.16, 8a.17, 8a.18, and 8a.19:aggr create newaggr -r 8 -d 8a.16 8a.17 8a.18 8a.19
The following command creates an aggregate called newfastaggr, with 20 disks, the default RAID group size, and all disks with 15K RPM:aggr create newfastaggr -R 15000 20
The following command creates an aggregate called newFCALaggr. Note that if SAS disks are present, they might be used, because FC and SAS disks are considered to be the same type.aggr create newFCALaggr -T FCAL 15
Increasing the size of an aggregate
You can add hot spare disks to an aggregate to increase its size, so it can provide more storage space to its contained volumes. You might also want to increase the size of a specific RAID group.
Before You Begin
Make sure you understand the following concepts:
• Benefits of keeping your RAID groups homogenous for disk size and speed
• What types of disks can be used together (FCAL and SAS, SATA and ATA)
• How to add disks to aggregates from a heterogenous disk pool
• The requirement to add disks owned by the same system and pool
• Best practices for providing hot spares
• Checksum rules when zone checksum disks are present
Considerations
You can specify a RAID group to add disks to. If you do not specify a RAID group, the disks are added to the most recently created RAID group if there is room in that RAID group. Otherwise, a new RAID group is created.
To see the number and types of disks in each RAID group, you can use the aggr status -r command.
Steps
1. Verify that appropriate hot spare disks are available for you to add by entering the following command:aggr status -s
Make sure that enough of the spares listed are of the correct type, size, speed, checksum type, and disk connection architecture for the target RAID group in the aggregate to which you are adding the disks.
2. Add the disks by entering the following command:aggr add aggr_name [-f] [-n] [-g raid_group_name] disk_list
-f enables you to add disks from a different pool or of a different speed.
-n displays the results of the command but does not execute it. This is useful for displaying the disks that Data ONTAP would automatically select. You can then decide whether to accept Data ONTAP's selection or to add different disks.
If you specify the -g option, the disks are added to the raid group you specify. raid_group_name is the name that Data ONTAP gave to the group—e.g., rg0.
disk_list is one of the following parameters:
o ndisks[disk_size]
o -d disk1 [disk2...]
Examples
The following command adds four 300-GB disks to the aggr1 aggregate:aggr add aggr1 4@300
The following command adds the disks 5a.17 and 5a.26 to the rg1 RAID group of the aggr2 aggregate:aggr add aggr2 -g rg1 -d 5a.17 5a.26
The following command adds one disk to each plex of a mirrored aggregate aggr_mir:aggr add aggr_mir -d 5a.18 -d 8b.14
After You Finish
After you add disks to an aggregate, run a full reallocation job on each FlexVol volume contained in that aggregate. For information about reallocation, see your Block Access Management Guide.
• What happens when you add disks to an aggregate
By default, Data ONTAP adds new disks to the most recently created RAID group until it reaches its maximum size. Then Data ONTAP creates a new RAID group. Alternatively, you can specify a RAID group you want to add disks to.
• Forcibly adding disks to aggregates
You might want to override some of the restrictions on what disks can be added to an aggregate if you don't have disks of the right speed or enough disks in the correct pool. You use the aggr add -f command to accomplish this.
• What happens when you add disks to an aggregate that are larger than the existing disks
What Data ONTAP does when you add larger disks to an aggregate depends on the RAID level (RAID4 or RAID-DP) of the aggregate.
Taking an aggregate offline
You use the aggr offline command to take an aggregate offline to perform maintenance on the aggregate, move it, or destroy it.
Steps
1. If the aggregate you want to take offline contains FlexVol volumes, boot into maintenance mode.
Note: This step is not necessary for traditional volumes.
2. Enter the following command:aggr offline aggr_name
3. If you previously booted into maintenance mode, return to normal mode.
The aggregate is now offline. You cannot access any data in the aggregate's volumes.
Bringing an aggregate online
After you restrict an aggregate or take it offline, you can use the aggr online command to make it available to the storage system again by bringing it back online.
Enter the following command:aggr online aggr_name
If the aggregate is inconsistent, the command prompts you for confirmation.
Attention: If you bring an inconsistent aggregate online, it might suffer further file system corruption. If you have an inconsistent aggregate, contact technical support.
The aggregate is online and available for use.
Putting an aggregate into restricted state
You use the aggr restrict command to put the aggregate into a restricted state if you want the aggregate to be the target of an aggregate copy or SnapMirror replication operation.
Considerations
For information about aggregate copy and SnapMirror replication, see the Data Protection Online Backup and Recovery Guide.
Steps
1. If the aggregate you want to restrict contains FlexVol volumes, boot into maintenance mode.
Note: This step is not necessary for traditional volumes.
2. Enter the following command:aggr restrict aggr_name
3. If you previously booted into maintenance mode, return to normal mode.
The aggregate is now restricted. Data in the aggregate's volumes is unavailable to clients.
Parent topic: Managing aggregates
Determining how the space in an aggregate is being used
Not all of the disk space you add to an aggregate is available for user data. You use the aggr show_space command to display how the disk space in an aggregate is being used.
Considerations
If you specify the name of an aggregate, the command only displays information about that aggregate. Otherwise, the command displays information about all of the aggregates in the storage system.
For more information about the values returned by this command, see the na_aggr(1) man page.
Example
aggr show_space aggr1
Aggregate 'aggr1'
Total space WAFL reserve Snap reserve Usable space BSR NVLOG
33GB 3397MB 1529MB 28GB 0KB
Space allocated to volumes in the aggregate
Volume Allocated Used Guarantee
newvol 2344KB 2344KB (offline)
vol1 1024MB 1328KB volume
dest1 868KB 868KB volume
Aggregate Allocated Used Avail
Total space 1027MB 4540KB 27GB
Snap reserve 1529MB 6640KB 1522MB
WAFL reserve 3397MB 1280KB 3396MB
Destroying an aggregate
You destroy an aggregate when you no longer need the data in that aggregate or when you have copied the content of the aggregate to another location.
Before You Begin
Before you can destroy an aggregate, you must destroy all of the FlexVol volumes contained by that aggregate.
Considerations
When you destroy an aggregate, Data ONTAP converts its parity disks and all its data disks back into hot spares. You can then use the spares in other aggregates and other storage systems.
Attention: If you destroy an aggregate, the data in the aggregate is no longer accessible by normal access methods, unless you undestroy it before any of its disks are zeroed or reused in another aggregate.
Note: If you want to make the data in the aggregate inaccessible by any means, you can sanitize its disks.
Note: You cannot destroy a SnapLock Compliance aggregate until the retention periods for all data contained in it have expired. For more information about the SnapLock functionality, see the Data ONTAP Data Protection Online Backup and Recovery Guide
Steps
1. Take the aggregate offline by entering the following command:aggr offline aggr_name
2. Destroy the aggregate by entering the following command:aggr destroy aggr_name
The following message is displayed:
Are you sure you want to destroy this aggregate ?
3. Enter the following command to confirm that you want to destroy the aggregate:y
The following message is displayed:Aggregate 'aggr_name' destroyed.
hanging an aggregate's RAID level from RAID4 to RAID-DP
Before you change an aggregate’s RAID protection from RAID4 to RAID-DP, you need to ensure that enough appropriate hot spare disks are available.
Steps
1. Determine the number of RAID groups and the size of their parity disks in the aggregate in question by entering the following command:aggr status aggr_name -r
2. List the available hot spares on your system by entering the following command:aggr status -s
3. Make sure that at least one, and preferably two hot spare disks exist for each RAID group listed. If necessary, add additional hot spare disks.
4. Enter the following command:aggr options aggr_name raidtype raid_dp
When you change the RAID level of an aggregate from RAID4 to RAID-DP, Data ONTAP makes the following changes:
• Adds an additional disk to each existing RAID group from the storage system’s hot spare disk pool; assigns the new disk the dParity disk function for the RAID-DP group. A reconstruction begins for each RAID group to populate the dParity disk.
• Changes the raidsize option for the aggregate to the appropriate RAID-DP default value.
Undestroying an aggregate
If you previously destroyed an aggregate and have changed your mind, you can undestroy the aggregate if the data is still intact and the aggregate was not SnapLock-compliant.
Before You Begin
You must know the name of the aggregate you want to undestroy, because there is no Data ONTAP command available to display destroyed aggregates, nor do they appear in FilerView.
Undestroy the aggregate by entering the following command:aggr undestroy aggr_name
Example
sys1> aggr undestroy aggr1
The following message is displayed:To proceed with aggr undestroy, select one of the following options [1] abandon the command [2] undestroy aggregate aggr1 ID: 0xf8737c0-11d9c001-a000d5a3-bb320198 Selection (1-2)?
If you select 2, a message with a date and time stamp appears for each disk that is restored to the aggregate. The last line of the message says:Aggregate ‘aggr1’ undestroyed. Run wafliron to bring the aggregate online.
After You Finish
After undestroying an aggregate, you must run the wafliron program with the privilege level set to advanced. If you need assistance, contact technical support.
•
Note: You can change the raidsize option after the RAID level change is complete.
After You Finish
You can verify the new RAID level by using the aggr options command.
Changing an aggregate's RAID level from RAID-DP to RAID4
When you change an aggregate's RAID level from RAID-DP to RAID4, the extra parity disks are converted to spares. In addition, the raidsize option is changed.
Enter the following command:aggr options aggr_name raidtype raid4
When you change the RAID level of an aggregate from RAID4 to RAID-DP, Data ONTAP makes the following changes:
• In each of the aggregate’s existing RAID groups, the RAID-DP second parity disk (dParity) is removed and placed in the hot spare disk pool, thus reducing each RAID group’s size by one parity disk.
• Data ONTAP changes the setting for the aggregate’s raidsize option to the size of the largest RAID group in the aggregate, except in the following situations:
o If the aggregate’s largest RAID group is larger than the maximum RAID4 group size, then the aggregate’s raidsize option is set to the maximum.
o If the aggregate’s largest RAID group is smaller than the default RAID4 group size, then the aggregate’s raidsize option is set to the default group size.
o If the aggregate's raidsize option is already below the default value for RAID4, it is reduced by 1.
After You Finish
You can verify the new RAID level by using the aggr options command.
Physically moving an aggregate
To move an aggregate from one storage system (the source) to another (the target), you need to physically move disks, disk shelves, or entire loops or stacks. You might move an aggregate to move data to a new storage system model or remove data from an impaired storage system.
Before You Begin
Ensure that the target storage system meets the following requirements:
• It must be running a version of Data ONTAP that is the same or later than the version running on the source system.
• It must support the shelf, module, and disk types being moved.
• It must support the size of the aggregate being moved.
Considerations
The procedure described here applies to both aggregates with FlexVol volumes and to traditional volumes.
The procedure described here does not apply to V-Series systems. For information about how to physically move aggregates in V-Series systems, see the V-Series Software Setup, Installation, and Management Guide.
Steps
1. In normal mode, enter the following command at the source storage system to locate the disks that contain the aggregate:aggr status aggr_name -r
The locations of the data, parity, and dParity disks in the aggregate appear under the HA, SHELF, and BAY columns (dParity disks appear for RAID-DP aggregates only).
2. Complete the appropriate steps, depending on whether you are moving an aggregate or a traditional volume.
If you are moving... Then...
A traditional volume Take the volume offline by entering the following command:aggr offline vol_name
An aggregate a. Boot the storage system into maintenance mode.
b. Take the aggregate offline by entering the following command:aggr offline aggr_name
3. Follow the instructions in the disk shelf hardware guide to remove the disks or shelves you identified previously from the source storage system.
4. Install the disks or disk shelves in the target storage system.
When the target storage system sees the new disks, it sees the new aggregate as a foreign aggregate. Data ONTAP takes the foreign aggregate offline. If the foreign aggregate has the same name as an existing aggregate on the target storage system, Data ONTAP renames it aggr_name(1), where aggr_name is the original name of the aggregate.
5. If the target storage system uses software-based disk ownership, assign the disks that you moved to the target storage system by entering the following command for each moved disk:disk assign disk_name
6. Confirm that the foreign aggregate is complete by entering the following command:aggr status aggr_name
Attention: If the foreign aggregate is incomplete (if it has a status of partial), add all missing disks before proceeding. Do not try to add missing disks after the aggregate comes online—doing so causes them to become hot spare disks. You can identify the disks currently used by the aggregate using the aggr status -r command.
7. If the storage system renamed the foreign aggregate because of a name conflict, enter the following command to rename the aggregate:aggr rename aggr_name new_name
8. Enter the following command to bring the aggregate online in the destination storage system:aggr online aggr_name
9. Enter the following command to confirm that the added aggregate came online:aggr status aggr_name
10. Boot both source storage systems out of maintenance mode.
For more information about maintenance mode, see the Data ONTAP System Administration Guide.
Thursday, December 30, 2010
Wednesday, December 29, 2010
configuration file editing
Editing configuration files
Configuration files must be edited from clients
Data ONTAP does not include an editor. You cannot edit files by using the system console or by establishing a Telnet session to the storage system. You must use an editor from an NFS client or a CIFS client to edit system configuration files.
Enabling an NFS client to edit configuration files
For an NFS client to edit configuration files, the client must be authorized to access the root file system.
If the NFS client was specified as the administration host during setup or added as an administration host after setup was completed, it is already authorized to access the root file system.
If the NFS client is not specified as an administration host, complete the following steps to authorize access to the root file system.
Step Action
1 Mount the storage system root volume on the administration host.
2 From the administration host, edit the /etc/exports file on the root volume to grant root permission to the client.
3 Use the storage system console, a Telnet client, or the rsh command to issue the following command to the system:
exportfs
4 Mount the storage system root volume on the client.
Editing configuration files from an NFS client
To edit configuration files from an NFS client, complete the following step.
Step Action
1 From the client, use a text editor to edit the files in the /etc directory.
Editing configuration files from a CIFS client
After setup finished, the default /etc/passwd and /etc/group files on the root volume were set up to enable you to share files on the storage system as Administrator. The system root directory was shared automatically as C$. The administrator has read, write, and execute rights to the share.
Note
The C$ share is a "hidden" share; you can get to it only by specifying the path manually (for example, as \\filer\C$), rather than accessing it through the Network Neighborhood icon.
To edit configuration files from a CIFS client, complete the following steps.
Step Action
1 Connect from a CIFS client to the storage system as Administrator.
2 Display the contents of the system's C$ share, and select a file to edit.
Configuration files that require a carriage return after the last entry
Data ONTAP requires that the following configuration files be terminated with a carriage return:
• /etc/passwd
• /etc/group
• /etc/netgroup
• /etc/shadow
When you edit these files, be sure to insert a carriage return after the last entry.
Configuration files that should not be edited
When you configure Data ONTAP, it creates some files that you should not edit. The following configuration files should not be edited.
• cifsconfig.cfg
• cifssec.cfg
• lclgroups.cfg
• filesid.cfg
• sysconfigtab
• registry.*
Accessing the default directories on the storage system
Accessing the /etc directory from an NFS client
To access the /etc directory from an NFS client, complete the following steps.
Step Action
1 Mount the following path:
filer:/vol/vol0
filer is the name of your storage system.
Result:
You have access to the system root directory.
2 Change directories to the /etc directory, using the following command:
cd etc
Accessing the /etc directory from a CIFS client
To access the root directory from a CIFS client, complete the following steps.
Step Action
1 Map a drive to the following path:
\\filer\C$
filer is the name of your system.
Result:
You have access to the system root directory.
2 Double-click the /etc folder.
Accessing the home directory from an NFS client
To access the home directory from an NFS client, complete the following step.
Step Action
1 Mount the following path:
filer:/vol/vol0/home
filer is the name of your system.
Accessing the home directory from a CIFS client
To access the home directory from a CIFS client, complete the following step.
Step Action
1 Map a drive to the following path:
\\filer\HOME
filer is the name of your system.
Note
You can also browse the Network Neighborhood to locate the system and the HOME directory.
Accessing log files using HTTP
To access your log files using HTTP, complete the following step.
Step Action
1 Point your browser to the following location:
http:///na_admin/logs/
system_name is the name of your system.
CopyrigHow to move or rename the root volume on a filer
KB ID: 1010097 Version: 3.0 Published date: 11/19/2010
Description
• Change, rename or move the root volume
• Error message: servlet not initialized
• Switching the root volume from a SCSI shelf to a volume in FCAL
• Move the system files to another volume
• Decrease the RAID size of an existing root volume
Procedure
Moving the root volume
To move the root volume by creating a new volume, follow these steps:
1. Create a new volume for the new root volume (see the vol Manual Page for more options).
Traditional Volumes
1. Enter the following command to create a new traditional volume:
vol create new_volname number_of_disks
2. After the new volume is created, this message will be displayed - Bootblock update complete.
Do not run the download command afterwards, as it is unnecessary.
FlexVols
1. For flexible volumes, the following command creates a new volume:
vol create flex_volname aggrname size
2. To create a new 5GB FlexVol, inside of an aggregate called "aggr1," enter the following command:
vol create new_root aggr1 5g
Creating a FlexVol results in a message similar to the following:
Creation of volume 'new_root' with size 5g on containing aggregate 'aggr1' has completed.
Note:
Please refer to the following document for recommended root volume sizes:
Root volume size and space guarantee requirements
As minimum root size requirements may differ across versions of Data ONTAP. Refer to your documentation for the correct requirements.
2. Copy the entire /etc directory from the current root volume to the new root volume. If other data exists on the old root volume, also copy that data to the new root volume. If necessary, increase the size of the new root volume by adding disks to the new volume using the vol add command.
Note: Other data migration utilities such as SCOPY, vol copy, ndmpcopy, and so on, may be used to migrate large amounts of data to the new root volume. Additionally, snapvaults should be disabled during the migration process (See Bug 268338)
3. If desired, the vol rename command may be used to rename the old and new root volumes.
4. Flag the new root volume as the root volume with the following command:
vol options new_root root
For clusters, see the section Notes on clustered storage systems.
5. Verify that the shares and exports are updated accordingly, by running the following commands:
cifs shares
exportfs
6. Reboot the filer
To move the root volume without creating a new volume, follow these steps:
1. Validate the current root volume (usually vol0) and the new root volume:
vol status
2. Ensure that the ndmpd daemon is turned on using the ndmpd on command on the filer.
3. Copy the entire /etc directory from the current root volume to the new root volume
ndmpcopy /etc /vol/new_rootvol/etc
4. Flag the new root volume as the root volume:
vol options new_rootvol root
For clusters, see the section Notes on clustered storage systems.
5. If desired, rename the old and new root volume. The following command renames the volume :
vol rename
6. Verify that the shares and exports are updated accordingly, by running the following commands:
cifs shares
exportfs
7. Reboot the filer
8. Verify the new root volume settings:
vol status
An example output is shown below. For this example, the root is vol0. The new root volume will be vol2.
filer> vol status
Volume State Status Options
vol1 online raid_dp create_ucode=on
vol0 online raid4 root, create_ucode=on <<<<=== vol2 online raid4 raidsize=4, create_ucode=on filer> ndmpcopy /etc /vol/vol2/etc
Ndmpcopy: Starting copy [ 2 ] ...
Ndmpcopy: filer: Notify: Connection established
Ndmpcopy: filer: Notify: Connection established
Ndmpcopy: filer: Connect: Authentication successful
Ndmpcopy: filer: Connect: Authentication successful
Ndmpcopy: filer: Log: DUMP: creating "/vol/vol0/../snapshot_for_backup.4" snapshot.
Ndmpcopy: filer: Log: DUMP: Using subtree dump
Ndmpcopy: filer: Log: DUMP: Date of this level 0 dump: Mon Mar 7 10:18:18 2005.
Ndmpcopy: filer: Log: DUMP: Date of last level 0 dump: the epoch.
Ndmpcopy: filer: Log: DUMP: Dumping /etc to NDMP connection
Ndmpcopy: filer: Log: DUMP: mapping (Pass I)[regular files]
Ndmpcopy: filer: Log: DUMP: mapping (Pass II)[directories]
Ndmpcopy: filer: Log: DUMP: estimated 365193 KB.
Ndmpcopy: filer: Log: DUMP: dumping (Pass III) [directories]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:25 2005: Begin level 0 restore
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:25 2005: Reading directories from the backup
Ndmpcopy: filer: Log: DUMP: dumping (Pass IV) [regular files]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:28 2005: Creating files and directories.
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:32 2005: Writing data to files.
Ndmpcopy: filer: Log: DUMP: dumping (Pass V) [ACLs]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:19:06 2005: Restoring NT ACLs.
Ndmpcopy: filer: Log: RESTORE: RESTORE IS DONE
Ndmpcopy: filer: Notify: restore successful
Ndmpcopy: filer: Log: DUMP: 365298 KB
Ndmpcopy: filer: Log: DUMP: DUMP IS DONE
Ndmpcopy: filer: Log: DUMP: Deleting "/vol/vol0/../snapshot_for_backup.4" snapshot.
Ndmpcopy: filer: Notify: dump successful
Ndmpcopy: Transfer successful [ 49 seconds ]
Ndmpcopy: Done
filer> vol options vol2 root
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.37 removed
from primary mailbox set
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.36 removed
from primary mailbox set
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.35 is a pr
imary mailbox disk
volume vol2 will become root volume at the next boot.
filer> reboot
After rebooting, type the following:
filer> vol status
Volume State Status Options
vol1 online raid_dp create_ucode=on
vol0 online raid4 create_ucode=on
vol2 online raid4 root, raidsize=4, create_ucode=on
This shows vol2 as the new root volume.
Renaming the root volume
To rename the root volume, use the following syntax:
vol rename
When renaming the root volume, the CIFS shares and the /etc/exports file are automatically updated. Run the cifs shares and exportfs commands to verify that the rename changes have been accepted by the storage system.
Notes on clustered storage systems
With clustered storage, it is possible to issue a takeover in place of a reboot when setting a new root volume. As with all cluster takeovers, this may be disruptive depending on the protocols your storage system is serving (i.e. CIFS, FCP, iSCSI, and so on.) and associated settings.
To perform a takeover and giveback to change your root volume, complete the following steps:
1. Filer1> cf takeover
2. Filer1(takeover)> partner
3. Filer2/Filer1*> vol options new_root root
Necessary system files are not present on the volume 'newroot'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed.
Continue with set root operation (y/n)? y Volume 'new_root' will become root at the next boot.
4. Filer2/Filer1*> partner
5. Filer1(takeover)> cf giveback
Related links
1010130: How to remove disks from the root volume
Data ONTAP System Administration Guide > Understanding the Root Volume
________________________________________
If you need further assistance, post a question in the NetApp Support Community.
Obsolete when printed.
Search Knowledgebase
English
Search
My Recent Searches
how to reduce datastore of vmware
operation manager
simulator
sim
325.8g
how to decrease size of a lun ?
how to move lun
snapmirror break
how to resize lun
how to do switch zoning
Welcome senthilkumar kumar
• Logout
• ________________________________________
• My Profile
• ________________________________________
• My Subscriptions
• My Recommendations
Contact Us | How To Buy | Feedback | Careers | Subscriptions | Privacy Policy | © 2010 NetApp
ht © 1994-2006, Network Appliance, Inc. All rights reserved.
Part No. 210-01284_A0
File: 4defvol5.htm
Configuration files must be edited from clients
Data ONTAP does not include an editor. You cannot edit files by using the system console or by establishing a Telnet session to the storage system. You must use an editor from an NFS client or a CIFS client to edit system configuration files.
Enabling an NFS client to edit configuration files
For an NFS client to edit configuration files, the client must be authorized to access the root file system.
If the NFS client was specified as the administration host during setup or added as an administration host after setup was completed, it is already authorized to access the root file system.
If the NFS client is not specified as an administration host, complete the following steps to authorize access to the root file system.
Step Action
1 Mount the storage system root volume on the administration host.
2 From the administration host, edit the /etc/exports file on the root volume to grant root permission to the client.
3 Use the storage system console, a Telnet client, or the rsh command to issue the following command to the system:
exportfs
4 Mount the storage system root volume on the client.
Editing configuration files from an NFS client
To edit configuration files from an NFS client, complete the following step.
Step Action
1 From the client, use a text editor to edit the files in the /etc directory.
Editing configuration files from a CIFS client
After setup finished, the default /etc/passwd and /etc/group files on the root volume were set up to enable you to share files on the storage system as Administrator. The system root directory was shared automatically as C$. The administrator has read, write, and execute rights to the share.
Note
The C$ share is a "hidden" share; you can get to it only by specifying the path manually (for example, as \\filer\C$), rather than accessing it through the Network Neighborhood icon.
To edit configuration files from a CIFS client, complete the following steps.
Step Action
1 Connect from a CIFS client to the storage system as Administrator.
2 Display the contents of the system's C$ share, and select a file to edit.
Configuration files that require a carriage return after the last entry
Data ONTAP requires that the following configuration files be terminated with a carriage return:
• /etc/passwd
• /etc/group
• /etc/netgroup
• /etc/shadow
When you edit these files, be sure to insert a carriage return after the last entry.
Configuration files that should not be edited
When you configure Data ONTAP, it creates some files that you should not edit. The following configuration files should not be edited.
• cifsconfig.cfg
• cifssec.cfg
• lclgroups.cfg
• filesid.cfg
• sysconfigtab
• registry.*
Accessing the default directories on the storage system
Accessing the /etc directory from an NFS client
To access the /etc directory from an NFS client, complete the following steps.
Step Action
1 Mount the following path:
filer:/vol/vol0
filer is the name of your storage system.
Result:
You have access to the system root directory.
2 Change directories to the /etc directory, using the following command:
cd etc
Accessing the /etc directory from a CIFS client
To access the root directory from a CIFS client, complete the following steps.
Step Action
1 Map a drive to the following path:
\\filer\C$
filer is the name of your system.
Result:
You have access to the system root directory.
2 Double-click the /etc folder.
Accessing the home directory from an NFS client
To access the home directory from an NFS client, complete the following step.
Step Action
1 Mount the following path:
filer:/vol/vol0/home
filer is the name of your system.
Accessing the home directory from a CIFS client
To access the home directory from a CIFS client, complete the following step.
Step Action
1 Map a drive to the following path:
\\filer\HOME
filer is the name of your system.
Note
You can also browse the Network Neighborhood to locate the system and the HOME directory.
Accessing log files using HTTP
To access your log files using HTTP, complete the following step.
Step Action
1 Point your browser to the following location:
http://
system_name is the name of your system.
CopyrigHow to move or rename the root volume on a filer
KB ID: 1010097 Version: 3.0 Published date: 11/19/2010
Description
• Change, rename or move the root volume
• Error message: servlet not initialized
• Switching the root volume from a SCSI shelf to a volume in FCAL
• Move the system files to another volume
• Decrease the RAID size of an existing root volume
Procedure
Moving the root volume
To move the root volume by creating a new volume, follow these steps:
1. Create a new volume for the new root volume (see the vol Manual Page for more options).
Traditional Volumes
1. Enter the following command to create a new traditional volume:
vol create new_volname number_of_disks
2. After the new volume is created, this message will be displayed - Bootblock update complete.
Do not run the download command afterwards, as it is unnecessary.
FlexVols
1. For flexible volumes, the following command creates a new volume:
vol create flex_volname aggrname size
2. To create a new 5GB FlexVol, inside of an aggregate called "aggr1," enter the following command:
vol create new_root aggr1 5g
Creating a FlexVol results in a message similar to the following:
Creation of volume 'new_root' with size 5g on containing aggregate 'aggr1' has completed.
Note:
Please refer to the following document for recommended root volume sizes:
Root volume size and space guarantee requirements
As minimum root size requirements may differ across versions of Data ONTAP. Refer to your documentation for the correct requirements.
2. Copy the entire /etc directory from the current root volume to the new root volume. If other data exists on the old root volume, also copy that data to the new root volume. If necessary, increase the size of the new root volume by adding disks to the new volume using the vol add command.
Note: Other data migration utilities such as SCOPY, vol copy, ndmpcopy, and so on, may be used to migrate large amounts of data to the new root volume. Additionally, snapvaults should be disabled during the migration process (See Bug 268338)
3. If desired, the vol rename command may be used to rename the old and new root volumes.
4. Flag the new root volume as the root volume with the following command:
vol options new_root root
For clusters, see the section Notes on clustered storage systems.
5. Verify that the shares and exports are updated accordingly, by running the following commands:
cifs shares
exportfs
6. Reboot the filer
To move the root volume without creating a new volume, follow these steps:
1. Validate the current root volume (usually vol0) and the new root volume:
vol status
2. Ensure that the ndmpd daemon is turned on using the ndmpd on command on the filer.
3. Copy the entire /etc directory from the current root volume to the new root volume
ndmpcopy /etc /vol/new_rootvol/etc
4. Flag the new root volume as the root volume:
vol options new_rootvol root
For clusters, see the section Notes on clustered storage systems.
5. If desired, rename the old and new root volume. The following command renames the volume :
vol rename
6. Verify that the shares and exports are updated accordingly, by running the following commands:
cifs shares
exportfs
7. Reboot the filer
8. Verify the new root volume settings:
vol status
An example output is shown below. For this example, the root is vol0. The new root volume will be vol2.
filer> vol status
Volume State Status Options
vol1 online raid_dp create_ucode=on
vol0 online raid4 root, create_ucode=on <<<<=== vol2 online raid4 raidsize=4, create_ucode=on filer> ndmpcopy /etc /vol/vol2/etc
Ndmpcopy: Starting copy [ 2 ] ...
Ndmpcopy: filer: Notify: Connection established
Ndmpcopy: filer: Notify: Connection established
Ndmpcopy: filer: Connect: Authentication successful
Ndmpcopy: filer: Connect: Authentication successful
Ndmpcopy: filer: Log: DUMP: creating "/vol/vol0/../snapshot_for_backup.4" snapshot.
Ndmpcopy: filer: Log: DUMP: Using subtree dump
Ndmpcopy: filer: Log: DUMP: Date of this level 0 dump: Mon Mar 7 10:18:18 2005.
Ndmpcopy: filer: Log: DUMP: Date of last level 0 dump: the epoch.
Ndmpcopy: filer: Log: DUMP: Dumping /etc to NDMP connection
Ndmpcopy: filer: Log: DUMP: mapping (Pass I)[regular files]
Ndmpcopy: filer: Log: DUMP: mapping (Pass II)[directories]
Ndmpcopy: filer: Log: DUMP: estimated 365193 KB.
Ndmpcopy: filer: Log: DUMP: dumping (Pass III) [directories]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:25 2005: Begin level 0 restore
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:25 2005: Reading directories from the backup
Ndmpcopy: filer: Log: DUMP: dumping (Pass IV) [regular files]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:28 2005: Creating files and directories.
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:18:32 2005: Writing data to files.
Ndmpcopy: filer: Log: DUMP: dumping (Pass V) [ACLs]
Ndmpcopy: filer: Log: RESTORE: Mon Mar 7 10:19:06 2005: Restoring NT ACLs.
Ndmpcopy: filer: Log: RESTORE: RESTORE IS DONE
Ndmpcopy: filer: Notify: restore successful
Ndmpcopy: filer: Log: DUMP: 365298 KB
Ndmpcopy: filer: Log: DUMP: DUMP IS DONE
Ndmpcopy: filer: Log: DUMP: Deleting "/vol/vol0/../snapshot_for_backup.4" snapshot.
Ndmpcopy: filer: Notify: dump successful
Ndmpcopy: Transfer successful [ 49 seconds ]
Ndmpcopy: Done
filer> vol options vol2 root
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.37 removed
from primary mailbox set
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.36 removed
from primary mailbox set
Mon Mar 7 10:21:24 PST [filer: fmmbx_instanceWorke:info]: Disk 8a.35 is a pr
imary mailbox disk
volume vol2 will become root volume at the next boot.
filer> reboot
After rebooting, type the following:
filer> vol status
Volume State Status Options
vol1 online raid_dp create_ucode=on
vol0 online raid4 create_ucode=on
vol2 online raid4 root, raidsize=4, create_ucode=on
This shows vol2 as the new root volume.
Renaming the root volume
To rename the root volume, use the following syntax:
vol rename
When renaming the root volume, the CIFS shares and the /etc/exports file are automatically updated. Run the cifs shares and exportfs commands to verify that the rename changes have been accepted by the storage system.
Notes on clustered storage systems
With clustered storage, it is possible to issue a takeover in place of a reboot when setting a new root volume. As with all cluster takeovers, this may be disruptive depending on the protocols your storage system is serving (i.e. CIFS, FCP, iSCSI, and so on.) and associated settings.
To perform a takeover and giveback to change your root volume, complete the following steps:
1. Filer1> cf takeover
2. Filer1(takeover)> partner
3. Filer2/Filer1*> vol options new_root root
Necessary system files are not present on the volume 'newroot'. It is recommended that you copy system files from the current root volume to the new root volume using the steps outlined in System Administration Guide, chapter 'Understanding Root Volumes', section 'Changing Root Volume'. If you do not, after reboot, the appliance will enter setup and service will be disrupted until all the setup steps (including a reinstall of system software) have been completed.
Continue with set root operation (y/n)? y Volume 'new_root' will become root at the next boot.
4. Filer2/Filer1*> partner
5. Filer1(takeover)> cf giveback
Related links
1010130: How to remove disks from the root volume
Data ONTAP System Administration Guide > Understanding the Root Volume
________________________________________
If you need further assistance, post a question in the NetApp Support Community.
Obsolete when printed.
Search Knowledgebase
English
Search
My Recent Searches
how to reduce datastore of vmware
operation manager
simulator
sim
325.8g
how to decrease size of a lun ?
how to move lun
snapmirror break
how to resize lun
how to do switch zoning
Welcome senthilkumar kumar
• Logout
• ________________________________________
• My Profile
• ________________________________________
• My Subscriptions
• My Recommendations
Contact Us | How To Buy | Feedback | Careers | Subscriptions | Privacy Policy | © 2010 NetApp
ht © 1994-2006, Network Appliance, Inc. All rights reserved.
Part No. 210-01284_A0
File: 4defvol5.htm
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
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
Subscribe to:
Posts (Atom)