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
PCI_CREATE_SLOT(9)						Hardware Interfaces						PCI_CREATE_SLOT(9)

NAME
pci_create_slot - create or increment refcount for physical PCI slot SYNOPSIS
struct pci_slot * pci_create_slot(struct pci_bus * parent, int slot_nr, const char * name, struct hotplug_slot * hotplug); ARGUMENTS
parent struct pci_bus of parent bridge slot_nr PCI_SLOT(pci_dev->devfn) or -1 for placeholder name user visible string presented in /sys/bus/pci/slots/<name> hotplug set if caller is hotplug driver, NULL otherwise DESCRIPTION
PCI slots have first class attributes such as address, speed, width, and a struct pci_slot is used to manage them. This interface will either return a new struct pci_slot to the caller, or if the pci_slot already exists, its refcount will be incremented. Slots are uniquely identified by a pci_bus, slot_nr tuple. There are known platforms with broken firmware that assign the same name to multiple slots. Workaround these broken platforms by renaming the slots on behalf of the caller. If firmware assigns name N to MULTIPLE SLOTS
The first slot is assigned N The second slot is assigned N-1 The third slot is assigned N-2 etc. PLACEHOLDER SLOTS
In most cases, pci_bus, slot_nr will be sufficient to uniquely identify a slot. There is one notable exception - pSeries (rpaphp), where the slot_nr cannot be determined until a device is actually inserted into the slot. In this scenario, the caller may pass -1 for slot_nr. The following semantics are imposed when the caller passes slot_nr == -1. First, we no longer check for an existing struct pci_slot, as there may be many slots with slot_nr of -1. The other change in semantics is user-visible, which is the 'address' parameter presented in sysfs will CONSIST SOLELY OF A DDDD
bb tuple, where dddd is the PCI domain of the struct pci_bus and bb is the bus number. In other words, the devfn of the 'placeholder' slot will not be displayed. COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 PCI_CREATE_SLOT(9)
All times are GMT -4. The time now is 09:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy