Sponsored Content
Operating Systems AIX vio server ethernet to vio client ethernet(concepts confusing) Post 302591367 by kah00na on Thursday 19th of January 2012 10:21:29 AM
Old 01-19-2012
I think this is the answer you are looking for...

You have to get your HMC involved because the vio server and your client LPAR can only see their own slot numbers for their adapters. I don't think either can see the other server's slot number, maybe they can but I'm not sure how.

Here is how it can be done though. In this example, slot 11 on the VIO server connects to slot C9 on the client.

Get the slot number of the vscsi0 from the client side using "lsslot -c slot":
Code:
client_lpar:/:$ lsslot -c slot | grep vscsi0
U8205.E6B.0110000-V1-C9   Virtual I/O Slot  vscsi0
client_lpar:/:$

Assuming your managed system's name is "MANAGEDSYSTEM", query your HMC with the 'lshwres' command and grep out your client LPAR's hostname and slot number. From this command you'll see the client slot to VIO slot association (make sure to put the comma inside the double-quotes of the grep):
Code:
client_lpar:/:$ ssh -q hscroot@hmchostname lshwres -r virtualio -m MANAGEDSYSTEM --rsubtype scsi --level lpar | grep "lpar_name=client_lpar," | grep "slot_num=9,"
lpar_name=client_lpar,lpar_id=1,slot_num=9,state=1,is_required=0,adapter_type=client,remote_lpar_id=39,remote_lpar_name=vio1,remote_slot_num=11
client_lpar:/:$

You can verify the resulting VIO slot number information by looking at the 'lsmap -all' output on your VIO server:
Code:
vio1:/home/padmin:# lsmap -all | more
SVSA            Physloc                                      Client Partition ID
--------------- -------------------------------------------- ------------------
vhost0          U8205.E6B.0110000-V39-C11                    0x00000001

VTD                   client_lparhdisk0
Status                Available
LUN                   0x8100000000000000
Backing device        hdisk5
Physloc               U78AA.001.xxxxxX6-P1-C4-T1-Z10060F8020061F02-L3000000000000
Mirrored              false

 

10 More Discussions You Might Find Interesting

1. AIX

Virtual Ethernet with VIO

We're using VIO (not an HMC) to manage our LPAR's We have 3 physical adapters and 4 LPARs. Through the VIO interface we assigned 2 virtual interfaces but require a 3rd interface assigned to these LPARs. I am experiencing issues understanding exactly how to create another virtual adapter, either... (1 Reply)
Discussion started by: scottsl
1 Replies

2. AIX

Virtual Ethernet VIO HMC LPARs

Hi, I am little confused about the virtual Ethernet configuration on VIO and Client Partitions. There is alot of info on the internet but it gets more confusing.... If I have LHEA, it is very simple. Just assign LHEA (logical host ethernet adapter) to client partition -> run smitty tcpip and... (10 Replies)
Discussion started by: filosophizer
10 Replies

3. AIX

vio server and vio client

Hi, I want to know wheather partition size for installation of vio client can be specified on vio server example If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

4. AIX

rebooting vio client

Hi, I would like to reboot vio client but I am not able to access vio client(I am not able to get putty) , I am able to get putty of vio server, is there any command by using which from vio server I can reboot vio client? (3 Replies)
Discussion started by: manoj.solaris
3 Replies

5. AIX

Finding cpu information on vio client

Hi, I am having single p series blade with Single Physcial CPU with dual core, on that vio server is installed, I have created vio client allocate 0.9 each cpu , now when I am running prtconf command on vio client it is showing "2" no of processor, My query using which command it will... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

6. AIX

Unable to connect VIO client

Hi I am facing very strange issue on my vio server 5 vio clients are confgured, now I am to connect 3 vio client , i am unable to connect 2 vio client my ip address,subnet mask,gateway is correct. i have rebooted and reconfigured the ip address, but issue is persists. Kindly suggest how to... (0 Replies)
Discussion started by: manoj.solaris
0 Replies

7. AIX

how will i know if a lun has been already mapped to a vio client

Hi im logged in to the vio servers now. when i give # lspv | wc -l i get the count as 6246 how will i know if a lun has been already mapped to a vio client or it is left free without mapping to any of the vio client ? (1 Reply)
Discussion started by: newtoaixos
1 Replies

8. AIX

cdrom confusion on the vio client lpar

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

9. AIX

Chef client on VIOs? How do you manage your VIO configs?

I know the VIOs are generally to be treated as an appliance and one should never drop down to oem_setup_env. In reality however, oem is a very useful tool to get the job done. So that leads me into the question of using the Chef client on a VIO. Currently a big push to manage all our *nix... (4 Replies)
Discussion started by: RecoveryOne
4 Replies

10. AIX

Need to replace a broken PV in a VIO VG used for client LPARs (and it won't release the old one)

I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
2 Replies
rarpc(1M)																 rarpc(1M)

NAME
rarpc - Reverse Address Resolution Protocol client SYNOPSIS
count] interface_name DESCRIPTION
the Reverse Address Resolution Protocol client, implements the client portion of the Reverse Address Resolution Protocol (see It sends RARP requests for the specified interface's hardware address and waits for the response from the RARP server. can be used during boot-time ini- tialization to find the IP address of an interface. To do so, set the i] variable of interface i with in Options are: Print debugging information. Use ethernet encapsulation only. Use SNAP encapsulation only. Transmits count requests and waits for each one to time out before giving up. interface_name Identifies the interface to request information about. If a response is received, it prints the IP address to its standard output. This information can be used to configure the interface as seen in If a response is not received, the client will retransmit after 2 seconds, and then after 4 seconds. After that, retransmissions occur every 8 seconds. RETURN VALUE
Exit status is 1 if the command fails or no RARP response is received. Exit status is 0 and the IP address is printed to standard output if a response is received. LIMITATIONS
1. The client cannot be run at the same time a daemon is running on the same interface. 2. The client supports only ethernet, 100VG and FDDI network interfaces. AUTHOR
was developed by HP. SEE ALSO
rarpd(1M). R. Finlayson, T. Mann, J.C. Mogul, M. Theimer, "Reverse Address Resolution Protocol", RFC 903. rarpc(1M)
All times are GMT -4. The time now is 01:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy