03-21-2012
I'm sure there has to be another way. I say this because someone else created a LPAR on this system without rebooting the VIO server.
Due to circumstances I cannot ask this person how he managed to create the LPAR without rebooting the VIO server.
10 More Discussions You Might Find Interesting
1. AIX
Hi,
I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7).
I extend my vg vg000 (on the partition) and add the 2 hdisks.
I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies
2. AIX
I have a standard template I deploy for each of my AIX servers. It's in a mksysb format which I pulled via the nim server after I originally set it up.
I'm trying to restore this mksysb over the wire to a remote system. The remote system is an lpar running under vio (no HMC attached). The disk... (1 Reply)
Discussion started by: scottsl
1 Replies
3. UNIX for Dummies Questions & Answers
Can you have a Dynamic LPAR without VIO and if yes is there a benefit to having both? I am attempting to implement VIO and Resource pooling at my company and want to understand the limitations.
Also, I have been told the managing and allocation of the Logical Volumes is a time consuming task as... (0 Replies)
Discussion started by: bombers73
0 Replies
4. AIX
Hi, I've lost the root password in a virtual partition created in a IBM Vio Server. May I recover that somehow?
Thanks (2 Replies)
Discussion started by: r4mp4g3
2 Replies
5. AIX
We have a frame the uses 2 vios that assign disk storage to LPAR's. We have a LPAr with multiple disk and I want to know how do I tell which vio is serving the disk. For example the LPAr has hdisk 0, 1, 2, 3 all the same size. I want to know which vio is serving hdisk0, 1. (4 Replies)
Discussion started by: daveisme
4 Replies
6. AIX
hello Folks,
my vio:
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0 U9117.MMA.6534BE4-V2-C11 0x00000003
VTD ... (0 Replies)
Discussion started by: filosophizer
0 Replies
7. AIX
Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR.
How can I do it without rebooting the LPARS.
POWER6 with HMC
LPARS = AIX 6.1
Any info
developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ...
But... (5 Replies)
Discussion started by: filosophizer
5 Replies
8. AIX
I am wondering if there is a command I can run from **with-in** LPAR server (server01) to find out the hostname or IP address or other parameters for VIO server in charge of server01? (1 Reply)
Discussion started by: ms1232
1 Replies
9. AIX
Just a question which may seem dumb to some out there, but then again I am not a super technie so that's my excuse.
Is it possible to say provision a test AIX LPAR (has a 10gb boot lun and 20gb data) under a VIO which has connectivity to SAN Array A so it can see the disks provisioned to it,... (2 Replies)
Discussion started by: Johnny1314
2 Replies
10. AIX
Hi
In my vio server I have the below output
$ lsvopt | grep -i SAPSITGS
sapsitgs_cdrom TL12UP.iso 3182
In my vio client lpar I have the below output
root@sapsitgs:/ # lsdev -Cc cdromcd0 Available Virtual SCSI Optical Served by VIO Server
cd1... (1 Reply)
Discussion started by: newtoaixos
1 Replies
statd(1M) System Administration Commands statd(1M)
NAME
statd - network status monitor
SYNOPSIS
/usr/lib/nfs/statd
DESCRIPTION
statd is an intermediate version of the status monitor. It interacts with lockd(1M) to provide the crash and recovery functions for the
locking services on NFS. statd keeps track of the clients with processes which hold locks on a server. When the server reboots after a
crash, statd sends a message to the statd on each client indicating that the server has rebooted. The client statd processes then inform
the lockd on the client that the server has rebooted. The client lockd then attempts to reclaim the lock(s) from the server.
statd on the client host also informs the statd on the server(s) holding locks for the client when the client has rebooted. In this case,
the statd on the server informs its lockd that all locks held by the rebooting client should be released, allowing other processes to lock
those files.
lockd is started by automountd(1M), mount_nfs(1M), and share(1M) if NFS automounts are needed.
FILES
/var/statmon/sm lists hosts and network addresses to be contacted after a reboot
/var/statmon/sm.bak lists hosts and network addresses that could not be contacted after last reboot
/var/statmon/state includes a number which changes during a reboot
/usr/include/rpcsvc/sm_inter.x contains the rpcgen source code for the interface services provided by the statd daemon.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnfscu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), automountd(1M), lockd(1M), mount_nfs(1M), share(1M), svcadm(1M), attributes(5), smf(5)
System Administration Guide: IP Services
NOTES
The crash of a server is only detected upon its recovery.
The statd service is managed by the service management facility, smf(5), under the service identifier:
svc:/network/nfs/status
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
If it is disabled, it will be enabled by mount_nfs(1M), share_nfs(1M), and automountd(1M) unless its application/auto_enable prop-
erty is set to false.
SunOS 5.10 18 Nov 2004 statd(1M)