08-02-2012
Yes, it meets all the requirements for npiv. We have been configuring servers for the past year with the same processes.
I am getting the mksysb from our primary nim 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
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
5. 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
6. AIX
VIO Server is managing both AIX Clients and Linux Clients. For AIX Clients, we could do a disk mapping from slot numbers to VIO and also uname -L to determine the lparid and serial number frame its running on.
From a Linux Client,
How do I know which IBM frame its running on? Any command to... (4 Replies)
Discussion started by: rpangulu
4 Replies
7. 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
8. 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
9. AIX
Hi All,
I've been trying to create a new LPAR for some days now but I can't get the VIO server to recognize the new LPAR. This is what I did:
On HMC create new LPAR
On HMC create new virtual scsi adapter for LPAR in VIO profile
On HMC add new virtual scsi adapter for LPAR with DLPAR... (6 Replies)
Discussion started by: petervg
6 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
LEARN ABOUT LINUX
ntptrace
NTPTRACE(1) General Commands Manual NTPTRACE(1)
NAME
ntptrace - trace a chain of NTP servers back to the primary source
SYNOPSIS
ntptrace [ -n ] [ server ]
DESCRIPTION
ntptrace determines where a given Network Time Protocol (NTP) server gets its time from, and follows the chain of NTP servers back to their
master time source. If given no arguments, it starts with localhost. Here is an example of the output from ntptrace:
% ntptrace
localhost: stratum 4, offset 0.0019529, synch distance 0.144135
server2ozo.com: stratum 2, offset 0.0124263, synch distance 0.115784
usndh.edu: stratum 1, offset 0.0019298, synch distance 0.011993, refid 'WWVB'
On each line, the fields are (left to right): the host name, the host stratum, the time offset between that host and the local host (as
measured by ntptrace; this is why it is not always zero for "localhost"), the host synchronization distance, and (only for stratum-1
servers) the reference clock ID. All times are given in seconds. Note that the stratum is the server hop count to the primary source, while
the synchronization distance is the estimated error relative to the primary source. These terms are precisely defined in RFC-1305.
OPTIONS
-d Turns on some debugging output.
-n Turns off the printing of host names; instead, host IP addresses are given. This may be useful if a nameserver is down.
-r retries
Sets the number of retransmission attempts for each host (default = 5).
-t timeout
Sets the retransmission timeout (in seconds) (default = 2).
-v Prints verbose information about the NTP servers.
BUGS
This program makes no attempt to improve accuracy by doing multiple samples.
Network Time Protocol October 7, 2006 NTPTRACE(1)