10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I believe this is an OS multipathing issue - Solaris 10
We have x2 Dual port 8GB Qlogic HBA's installed in our SOlaris 10 host.
HBA0 (IOU0) Port WWN's - 09f4 (pci@3,700000/SUNW,qlc@0)
09f5 (pci@3,700000/SUNW,qlc@0,1)
HBA1 (IOU1) Port WWN's... (2 Replies)
Discussion started by: jamba1
2 Replies
2. Solaris
Hi,
I have an Oracle/Sun T3-2 Server with a duel SAS controller Fujitsu DX60 array attached.
I have 2 x SAS HBA's in the T3-2. One HBA cabled to CM0 and one HBA cabled to CM1 of the array.
The array is setup with one RAID GROUP and one VOLUME and one LUN
In Solaris I can see one device... (4 Replies)
Discussion started by: general_lee
4 Replies
3. Solaris
Here is the issue:
I am building a database server using Solaris 10x86 U8.
The system is jumpstarted with mpxio enabled and booting from the san.
We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san... (2 Replies)
Discussion started by: nabru72
2 Replies
4. Solaris
Hello folks,
I have a newly installed Solaris 10 system running on a T6320 blade. I have set up LDM with the intent to move an ldom from another blade to this one. So far, so good.
I had the SAN folks make the LUNs belonging to the ldom visible to my new blade and I can see them, all 4 paths.... (4 Replies)
Discussion started by: Ranck
4 Replies
5. Solaris
Hi Kudo,
I wanna to know that how can I do mpxio device name to os native name mapping without using stmsboot -L I tried everything still not able to got the solution till I able to get these o/p
here is native disk info as well physical wat is the logical OS name of the disk
... (1 Reply)
Discussion started by: tarunn.dubeyy
1 Replies
6. Filesystems, Disks and Memory
Greetings Forumers!!
I was given a T2000 with one, dual port, HBA card. The card had one fiber connection to the SAN and the former admin enabled MPxIO.
Yesterday, I learned that the other port was connected to the same SAN. This system is in another city so I don't have physical access to... (1 Reply)
Discussion started by: bluescreen
1 Replies
7. Filesystems, Disks and Memory
:confused:
Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO.
If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies
8. Solaris
Hi,
I have a quick question.
How can I see MPXIO statistics (like errors, how many I/O|throuput per path, ....) on Solaris 10? Does maybe a ready dtrace script exist (I do not have the knowledge to write one myself)?
I would be happy if somebody knows some good documentation/links (with... (1 Reply)
Discussion started by: victorinox
1 Replies
9. Solaris
Hi All,
I have one question.
I found out that my system setting for mpxio-disable=yes. Sun recommend to change it to mpxio-disable=no and run stmsboot -e command.
But no one can tell will it affect the system or not and the system is sol-10 and using veritas volume manager and attached... (3 Replies)
Discussion started by: mailbox80
3 Replies
10. Solaris
Hi,
I'm new to solaris and just installed solaris 10. For some reason I can't resolve stuff. I installed it with the option to use dns. My routing is correct. (I can ping stuff outside my subnet).
I have a resolv.conf which looks like this:
bash-3.00# more resolv.conf
10.32.2.12
10.32.2.11... (5 Replies)
Discussion started by: barabas
5 Replies
NetApp::Volume(3pm) User Contributed Perl Documentation NetApp::Volume(3pm)
NAME
NetApp::Volume -- OO class for creating and managing NetApp filer volumes
SYNOPSIS
use NetApp::Filer;
use NetApp::Aggregate;
my $filer = NetApp::Filer->new({ .... });
my @volume_names = $filer->get_volume_names;
my @volumes = $filer->get_volumes;
my $volume = $filer->get_volume( 'volname' );
DESCRIPTION
This class encapsulates a single NetApp filer volume, and provides methods for querying information about the volume and it's sub-objects
(eg. qtrees), as well as methods for managing the volume itself.
INSTANCE METHODS
get_filer
Returns the NetApp::Filer object representing the filer on which the aggregate exists.
get_name
Returns the name of the volume as a string.
get_states, get_statuses, get_options
Each of these methods returns a list of strings, each of which represents a single state, status, or option for the volume.
NOTE: All you English grammar pluralization rules fanatics can
give up trying to convince the author to call that one method
get_stati.
get_state( $state ), get_status( $status ), get_option( $option )
Each of these methods returns the value for the specified state, status or option. If that particular key wasn't present, then this method
will return undef. This makes it easy to tell the difference between a key that doesn't exist, and one that has a false value.
set_option( $option => $value )
This method sets a single option to the specified value. It always returns true, and raises a fatal exception if it can not set the
option.
get_aggregate_name
Returns the name of the aggregate on which the volume lives. For a "traditonal" volume, this will be a false value.
get_aggregate
Returns the NetApp::Aggregate object representing the aggregate on which the volume lives. For a "traditonal" volume, this will be a false
value.
get_qtree_names
Returns a list of strings, each of which is the name of a qtree on the volume.
get_qtrees
Returns a list of NetApp::Qtree objects, each of which represents a single qtree on the volume.
get_qtree( $name )
Returns a single NetApp::Qtree object for the specified qtree name. The name must in the form of a pathname, for example:
/vol/volume_name/qtree_name
The qtree_name is optional if querying the object for a volume's qtree. This method simply returns nothing if the specified qtree doesn't
exist on the volume.
get_language
Returns a string representing the language code for the volume.
set_language( $language )
Set the language code to the specified value. Always returns a true value, or raises a fatal exception if the language code can not be
set.
get_size
Returns the size of the volume as a string.
set_size( $size )
This method sets the size of the volume to the specified value. In all cases, the $size value is of the same form accepted by the create()
method, and the underlying ONTAP CLI command:
[+|-] <number> k|m|g|t
get_maxfiles
Returns the maxfiles value for the volume.
set_maxfiles( $maxfiles )
Sets the maxfiles value for the volume.
is_clone
Returns true if the volume is a clone, false otherwise.
get_parent_name
Returns a string representing the name of the parent volume, if this volume is a clone.
get_parent
Returns a NetApp::Volume object representing the parent volume, if this volume is a clone.
get_snapshot_name
Returns a string representing the snapshot name, if the volume is a clone.
get_snapshot
NOT YET IMPLEMENTED. This will return a NetApp::Snapshot object, once the API is extended to support snapshots (RSN, I'm sure...)
get_snapmirrors
Returns a list of NetApp::Snapmirror objects, each of which represents a snapmirror relationship for this volume.
offline( %args )
Takes the volume offline. The arguments are as follows:
$volume->offline(
# Optional arguments
cifsdelaytime => $cifsdelaytime,
);
online( %args )
Bring the volume online. The arguments are as follows:
$volume->online(
# Optional arguments
force => 1,
);
rename( %args )
Renames the volume to the specified newname. Always returns a true value, and raises a fatal exception if the name can not be changed.
The arguments are as follows:
$volume->rename(
# Required arguments
newname => $newname,
);
restrict( %args )
Puts the volume into the restricted state. The arguments are as follows:
$volume->restrict(
# Optional arguments
cifsdelaytime => $cifsdelaytime,
);
Snapshot Specific Methods
get_snapshots
Returns a list of NetApp::Snapshot objects for each of the snapshots of the volume.
get_snapshot( $name )
Returns a single NetApp::Snapshot object matching the specified name, if it exists for the volume.
create_snapshot( $name )
Creates a snapshot of the volume with the specified name.
delete_snapshot( $name )
Deletes a snapshot of the volume with the specified name.
get_snapshot_deltas
Returns a list of NetApp::Snapshot::Delta objects for each snapshot delta for the volume.
get_snapshot_reserved
Returns a string representing the amount of reserved space, as a percentage. This string does NOT include the % sign.
set_snapshot_reserved( $percentage )
Sets the snapshot reserved space to the specified percentage, which should also NOT include the % sign.
get_snapshot_schedule
Returns a NetApp::Snapshot::Schedule object representing the snapshot schedule for the volume.
set_snapshot_schedule( %args )
Sets the snapshot schedule for the volume based on the arguments passed. The argument syntax is:
$volume->set_snapshot_schedule(
weekly => $weekly,
daily => $daily,
hourly => $hourly,
hourlist => [
$hour1, $hour2, $hour3, ....
],
);
enable_shapshot_autodelete
This method turns on snapshot autodelete for the volume.
disable_snapshot_autodelete
This method turns off snapshot autodelete for the volume.
reset_snapshot_autodelete
This method resets snapshot autodelete for the volume to the filer defaults.
set_snapshot_autodelete_option( $name => $value )
Sets the specified snapshot autodelete option ($name) to the specified $value.
get_snapshot_autodelete_option( $name )
Returns the value of the specified autodelete option ($name). Note that if the prefix is "(not specified)", then the value returned is the
empty string.
UNIMPLEMENTED COMMANDS
The following ONTAP vol commands are not implemented, because the same functionality and information is provided through this API via some
other means.
container
The aggregate containing the volume can be obtained using:
$volume->get_aggregate;
which will return the NetApp::Aggregate object for it.
TO BE IMPLEMENTED
All other commands will be implemented in a future release of this API. Commands for flexible volumes will most likely have preference
over traditional volumes.
autosize
It's not yet clear just how this one should be implemented, since the command does several things. It enables and disables the autosize
feature, or resets it to defaults, and it also sets the maximum and incremental sizes to autosize to.
This could be implemented a few different ways, for example:
$volume->autosize(
# Optional arguments
maximum => $maximum,
incremental => $incremental,
# Optional, but mutually exclusive:
on => 1,
off => 1,
reset => 1,
);
That seems a little clumsy, though. Perhaps a better interface would be to have methods to control the state of the feature:
$volume->enable_autosize;
$volume->disable_autosize;
$volume->reset_autosize;
and then methods to set/get the autosize values:
$volume_set_autosize(
# Required but mutually exclusive options
maximum => $maximum,
incremental => $incremental,
);
$volume->get_autosize;
perl v5.14.2 2008-11-26 NetApp::Volume(3pm)