Sponsored Content
Operating Systems Solaris Netapp filer LUN Resize. Commands to run on Solaris afterwards. Post 302222770 by cheetobandito on Thursday 7th of August 2008 01:28:51 PM
Old 08-07-2008
Do you have the netapp host services running on the Solaris server or are you just mounting over the network??
 

9 More Discussions You Might Find Interesting

1. Solaris

Connect Solaris 10 to NetApp filer using Emulex single port HBAs.

Hi, I'm connecting a Solaris 10 server to a Netapp filer with two single port Emulex (Sun StorageTek PCI-X Enterprise 4GB FC HBA) HBAs. After physically installing both these HBAs what do I ned to do within Solaris 10 to enable them and configure them with persistent bindings. Do I need... (6 Replies)
Discussion started by: gwhelan
6 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. AIX

Dynamic LUN resize

Anyone know how to resize a LUN (if SAN disk array has increased the LUN size) and have AIX LVM know about it? Or is it automatic? Equivalent vxvm command is something like: vxdisk resize size= (3 Replies)
Discussion started by: apra143
3 Replies

4. AIX

Resize Lun

Good afternoon! Help with a solution I have AIX 7.1 works through vios I expanded Lun that it is necessary to make that aix saw this change and to expand the section lvm Sorry for my English (1 Reply)
Discussion started by: iformats
1 Replies

5. 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

6. Red Hat

How to resize filesystem by resizing the LUN without impact to applications.?

Is it possible to resize a filesystem by resizing the LUN on RHEL 6.4 64-bit with LVM and no impact to running applications? The research I have done so far seems to take the approach of adding a new LUN and then expaning the volume group to the new LUN. I'm looking for an approach that avoids a... (7 Replies)
Discussion started by: aenagy
7 Replies

7. Solaris

Netapp filer details - command?

What command can I use to find out details about a netapp filer. I have a directory that is a filer i would like to know details about the source host/folder that it points to. Thanks. (2 Replies)
Discussion started by: jjohnson
2 Replies

8. Solaris

Restore of Netapp FC lun targets used as the disks for a zpool with exported zfs file systems

So, We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 Replies

9. Linux

Identify newly attached LUN from NetApp

Hi I need to identify a newly attached LUN from NetApp on a linuxserver running uname -o GNU/Linux I have first run the df -h and got the following: df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_outsystemdb-lv_root 50G 2.7G 45G ... (3 Replies)
Discussion started by: fretagi
3 Replies
ypset(1M)																 ypset(1M)

NAME
ypset - bind to particular Network Information Service server SYNOPSIS
host] domain] server Remarks The Network Information Service (NIS) was formerly known as Yellow Pages (YP). Although the name has changed, the functionality of the service remains the same. DESCRIPTION
tells to get Network Information Service (NIS) services for the specified domain from the process running on server (see ypserv(1M) and ypbind(1M)). server is the NIS server that the NIS client binds to, and is specified as either a host name or an IP address. If server is down or is not running this is not discovered until a local NIS client process tries to obtain a binding for the domain. The daemon then tests the binding set by If the binding cannot be made to the requested server, attempts to rebind to another server in the same domain present in the ypservers file. NOTE: In order to run must be initiated with the or options. For more information on how to initiate see ypbind(1M). The command is useful for binding a client node that is not on a broadcast network. If a client node exists on a broadcast network which has no NIS server running, and if there is a network with one running that is available via a gateway, can establish a binding through that gateway. It is also useful for debugging NIS client applications such as when a NIS map exists only at a single NIS server. In cases where several hosts on the local net are supplying NIS services, it is possible for to rebind to another host, even while you attempt to find out if the operation succeeded. For example, typing followed by and receiving the reply may be confusing. It could occur when host1 does not respond to because its process is not running or is overloaded, and host2, running gets the binding. The server is the NIS server to bind to, specified as either a host name or an IP address. Refer to ypfiles(4) and ypserv(1M) for an overview of the Network Information Service. Options recognizes the following options and command-line arguments: Bind server for the Version 2 NIS protocol. Set the binding on host instead of locally. host can be specified as a host name or an IP address. Use domain instead of the default domain returned by (see domainname(1)). DIAGNOSTICS
The user is not root, or ypbind was run without the flags. See ypserv(1M) for explanations of the flags. The user is not root, or ypbind was run without one of the flags. See ypserv(1M) for explanations of the flags. WARNINGS
Starting with ONCplus version B.11.31.02, the NIS Version 1 protocol is no longer available. AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
domainname(1), ypwhich(1), ypserv(1M), ypfiles(4). ypset(1M)
All times are GMT -4. The time now is 02:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy