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::Filer(3pm) User Contributed Perl Documentation NetApp::Filer(3pm)
NAME
NetApp::Filer -- OO Class for managing NetApp Filer devices
SYNOPSIS
use NetApp::Filer;
my $filer = NetApp::Filer->new({
hostname => $hostname_of_nasfiler,
ssh_identity => "/path/to/ssh/identify/file",
});
my $filer = NetApp::Filer->new({
hostname => $hostname_of_nasfiler,
protocol => 'telnet',
telnet_password => $telnet_password,
});
DESCRIPTION
This class implements methods for communication with a NetApp Filer device. Both ssh and telnet are supported, but only ssh is really
recommended. NetApp doesn't support concurrent access via telnet, and the error checking using ssh is far more robust. Not to mention,
you can configure secure access via ssh without using passwords, but telnet access will always require a password.
METHODS
Filer Specific Methods
new( $args_ref )
This method takes a hash reference of arguments, and returns a NetApp::Filer object to be used to communicate with the specified filer.
The arguments are as follows:
NetApp::Filer->new({
# Required arguments
hostname => $hostname,
# Optional arguments
username => $username,
ssh_identify => $ssh_identity,
ssh_command => [ @ssh_command ],
protocol => 'ssh' | 'telnet',
telnet_password => $telnet_password,
telnet_timeout => $telnet_timeout,
cache_enabled => 0 || 1,
cache_expiration => $cache_expiration,
});
(required) hostname
The value of this argument is a string, which is the hostname of the filer to connect to.
(optional) username
The username to use for communication. Defaults to 'root'.
(optional) ssh_identify
The ssh identify file to use for ssh communication. If not specified then ssh will be invoked without the -i argument, and will use
whatever default identify file is setup for the current user.
In practice, this argument will almost always be required, but the code allows it to be optional.
If the specified file doesn't exist, then a fatal exception is raised.
(optional) ssh_command
An array reference representing the ssh command to be used to communication. Defaults to just ['ssh'].
Don't use this argument to specify the identity via -i. Instead, use the ssh_identify argument. If you need to specify certain ssh
options, for example StrictHostKeyChecking, then use this argument. For example:
my $filer = NetApp::Filer->new({
hostname => $somenasfiler,
ssh_command => [qw( ssh -o StrictHostKeyChecking=no )],
});
(optional) protocol
This option is a string, either 'ssh' or 'telnet'. The default, and recommended, protocol is ssh. While telnet is supported, only one
concurrent root telnet session per filer is allowed, and the error checking over telnet is far less robust than ssh.
(optional) telnet_password
This option is a string, and specified the root password to use when connecting via telnet. Note that password based ssh connectivity
is not supported, and telnet access, while supported, is not recommended. The author uses the telnet support for only one thing:
installing the ssh keys, and configuring ssh access.
(optional) cache_enabled
NOTE: The caching mechanism is considered experimental. For one thing, it depends on using a patched version of Memoize::Expire, which
is still not yet available on CPAN. Use with caution.
This option has a boolean value, and is used to disable the internal caching of the results of several API calls. By default, the
cache is disabled. If enabled, then the result of any of the following NetApp::Filer methods will be cached, using Memoize:
get_aggregate
get_volume
get_qtree
To enable caching of these API calls, set cache_enabled to a true value. The cached values will expire (see the next option), unless
the expiration value is set to 0.
(optional) cache_expiration
This option is an integer, and is the number of seconds to cache results of the above API calls. The default value is 10 seconds.
Setting this value to 0 will prevent the cached values from expiring at all.
get_version
Returns a NetApp::Filer::Version object.
get_licenses
Returns a list of NetApp::Filer::License objects, each of which represents a single licensed service on the filer. Note that if the
service is "not licensed", it is ignored. Only services with active of expired licensed are returned.
get_license( $service )
Returns a single NetApp::Filer::License object for the specified service.
add_license( $code )
Adds a license using the specified code. Returns a boolean value only.
delete_license( $service )
Deleted the license for the specified service. Returns a boolean value only.
Aggregate Specific Methods
get_aggregate_names
Returns a list of strings, each of which is the name of an aggregate on the filer.
get_aggregates
Returns a list of NetApp::Aggregate objects, each of which represents an aggregate on the filer.
get_aggregate( $name )
Returns a single NetApp::Aggregate object for the specified aggregate name.
create_aggregate( %args )
Create an aggregate using the specified arguments, and returns the NetApp::Aggregate object that represents it. The arguments are as
follows:
my $aggregate = $filer->create_aggregate(
# Required arguments
name => $name,
# Optional arguments
raidtype => 'raid0' | 'raid4' | 'raid_dp',
raidsize => $raidsize,
disktype => 'ATA' | 'FCAL' | 'LUN' | 'SAS' | 'SATA' | 'SCSI',
diskcount => $diskcount,
disksize => $disksize,
rpm => $rpm,
language => $language,
snaplock => 'Compliance' | 'Enterprise',
mirrored => 1, # -m
traditional => 1, # -v
force => 1, # -f
disks => [
# To specify a single set of disks:
'disk1', 'disk2', ....
# To specify two sets of disks:
[ 'disk1', 'disk2', .... ],
[ 'diskn', 'disktn+1', .... ],
],
);
destroy_aggregate( %args )
Destroy an aggregate using the specified arguments. The arguments are as follows:
$filer->destroy_aggregate(
# Required arguments
name => $name,
);
Volume Specific Methods
get_volume_names
Returns a list of strings, each of which is the name of a volume on the filer.
get_volumes
Returns a list of NetApp::Volume objects, each of which represents a volume on the filer.
get_volume( $name )
Returns a single NetApp::Volume object for the specified volume name.
Qtree Specific Methods
get_qtree_names
Returns a list of strings, each of which is the name of a qtree on the filer.
get_qtrees
Returns a list of NetApp::Qtree objects, each of which represents a single qtree on the filer.
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.
create_qtree( %args )
Creates a qtree on the filer. The arguments are as follows:
$filer->create_qtree(
# Required arguments
name => $name,
# Optional arguments
mode => $mode,
security => 'unix' | 'ntfs' | 'mixed',
oplocks => 0 | 1,
);
(required) name
The name of the qtree to create.
(optional) mode
The UNIX mode bits to use when creating the qtree.
(optional) security
The security of the qtree. This must be one of: unix, ntfs, or mixed.
(optional) oplocks
This option specified whether or not oplocks are to be enabled on the qtree. The value is interpreted in a boolean context, true
meaning "enabled" and false meaning "disabled".
Snapmirror Specific Methods
set_snapmirror_state( $state )
Sets the snapmirror state on the filer to the specified value, which must be either of the strings "off" or "on".
get_snapmirror_state
Returns a string, either "off" or "on", indicating whether or not snapmirror is turned off or on for this filer.
get_snapmirrors
Returns a list of NetApp::Snapmirror objecte, each of which represents a single snapmirror relationship on the filer.
Export Specific Methods
There is one general purpose method to retrieve all of the NFS exports on a filer, and 4 special purpose ones that make it easy to see the
difference between the contents of /etc/exports, and the live exports reported by "exportfs".
get_exports
Returns a list of NetApp::Filer::Export objects, each of which represents an NFS export on the filer.
get_permanent_exports
Returns a list of NetApp::Filer::Export objects, each of which represents a permanent export, which is one found in the /etc/exports file.
get_temporary_exports
Returns a list of NetApp::Filer::Export objects, each of which represents a temporary export, which is one NOT found in the /etc/exports
file. Temporary exports are ones created manually, using "exportfs -io", or by using the "exportfs -b" option to fence clients, or any
other command which creates a live NFS export that has not yet been written to /etc/exports, and which will not survive a reboot of the
filer.
get_active_exports
Returns a list of NetApp::Filer::Export objects, each of which represents a active export. Active exports are those reported by the
"exportfs" command. They can be permanent, if they are found in /etc/exports, or temporary, if created by hand.
get_inactive_exports
Returns a list of NetApp::Filer::Export objects, each of which represents a inactive export. An inactive export is a permanent export
found in /etc/exports, but which is NOT found in the list of active exports reported by "exportfs". If the options of a permanent export
are changed, but not saved to /etc/exports (eg. re-export something with "exportfs -io"), then the active, temporary export for that same
path, and the inactive, permanent export in /etc/exports can both exist concurrently.
perl v5.14.2 2008-12-09 NetApp::Filer(3pm)