Sponsored Content
Operating Systems Linux Identify newly attached LUN from NetApp Post 303002306 by fretagi on Tuesday 22nd of August 2017 02:55:21 AM
Old 08-22-2017
Hi

Please can I have help on this?
 

10 More Discussions You Might Find Interesting

1. Solaris

Netapp filer LUN Resize. Commands to run on Solaris afterwards.

Hi, I need to increase a veritas filesystem I have currently mounted on a Solaris 10 server. We can resize the LUN on the NetApp filer no problem. What I need to know is what do I do next on the Solaris 10 server I have so that it will see the increase in size. Do I run 'devfsadm' to... (3 Replies)
Discussion started by: gwhelan
3 Replies

2. Solaris

Can't see Netapp LUN on Solaris using LPFC after reboot.

Hi, I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies

3. Red Hat

Redhat 5 can't see my newly added LUN.

hi all, i have added new LUN to Redhat 5. i have already scanned LUN devices and it is confirmed that Kernel sees the newly added LUN's. i have used /proc/partitions and verified that my disks are there. However, i cannot find my disk using fdisk -l command. I am not sure what did i... (2 Replies)
Discussion started by: gisu0602
2 Replies

4. Solaris

new attached lun in solaris 10

hi, what are the steps to detect and configure a new attached lun in Solaris 10. Is there any difference between cfgadm and luxadm command ? rgds, snjksh (5 Replies)
Discussion started by: snjksh
5 Replies

5. Solaris

Can't see Newly created LUN by SAN admin

hello, i am an oracle DBA and trying to scan a newly created LUN of 200 GB on fiber channel by SAN admin.we have solaris 10 and SANtoolkit is installed.i tried following to get the new LUN at my machine. go /opt/Netapp/Santoolkit/bin and then ./sanlun lun show but i see only the existing... (12 Replies)
Discussion started by: janakors
12 Replies

6. Solaris

Solaris- How to scan newly attached NIC's

Hi folks, How can I scan newly attached network interfaces to server without reboot? Is there any command or something to scan without reboot. Thanks (5 Replies)
Discussion started by: snchaudhari2
5 Replies

7. Solaris

Swap space related issues, how to recognise the newly attached disk

hi!:) i got a problem....:wall::wall: i got several disks in my diskarray. I attached new disk to allocate it to the swap space. The problem is : how to recognise the newly attached disk? I've one more requirement -:wall:- i want to run dns service on another port number.how can i do... (2 Replies)
Discussion started by: vamshigvk475
2 Replies

8. AIX

Netapp iscsi lun

Hi, I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name. Please share me the steps to complete this requirements. Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies

9. Hardware

Formatting a newly created lun

Hi , I have created one new lun in my SAN storage and make it visible to my HP servers , but the fdisk -l output is somehow confusing. Do not know what to do next ---------- fdisk -l /dev/sdo1 Disk /dev/sdo1 (Sun disk label): 64 heads, 32 sectors, 10238 cylinders Units =... (7 Replies)
Discussion started by: mishra.sankar
7 Replies

10. Linux

Mount a newly added LUN on a GNU/Linux distro

Hi I am not familiar with the linux, but I was asked to create a file system on a LUN from the NetApp that was mapped to the linux server. The server is runing: uname -a Linux localhost.localdomain 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux and now... (6 Replies)
Discussion started by: fretagi
6 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)
All times are GMT -4. The time now is 09:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy