02-28-2019
Quote:
Originally Posted by
Phat
In some lpars, I can see they are using virtual fiber channel to connect to DS8K storage. In search with google, I understand that it is configured with VIOS server to share the physical FC channel with NPIV method.
But the situation is, in the same managed system, there are other lpars have physical FC, the WWpN not starting with C.
So my concern is, what method these lpars use to connect to SAN? How can they can "share/use" the physical FC without VIOS virtual FC?
I am not sure if i understand your question correctly. If the folowing answer is not what you expected please clarify what exactly you want to know:
Basically they both use the same way of communicating with the SAN - a "sort-of SCSI"-protocol transported over FC. NPIV basically means that a single (physical) FC port can use several (virtual) IDs - WWPNs - to identify itself. Think of it like an IP-alias for a network interface.
You may want to replace the physical FC-adapters with virtual ones, even if you only configure one LPAR to use it: if you assign physical adapters to an LPAR this partition will never be eligible for LPM (live partition mobility) and hence also not for live update (replace even the kernel without reboot, possible since AIX 7.2). My suggestion is to assign all the physical adapters to the VIOSes and give only virtual adapters to the LPARs. Notice that you will need to change the zoning for this to work.
Every virtual FC adapter (port) has actually TWO WWPNs which should both be zoned. The reason is that for LPM you need one WWPN to hold the connection on the originating side while the other WWPN is configured on the side you migrate to during the transition.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
know how to do it. (3 Replies)
Discussion started by: rainbow_bean
3 Replies
2. AIX
Hi,
Is there a way to dynamically increase the size of virtual disk on the LPAR. The virtual disk is coming from my VIO Server. From my SAN I have allocated a disk to VIO Server and from VIO Server to my LPAR....If I increase the space of the logical SAN DISK (DS 4700 using IBM TotalStorage... (0 Replies)
Discussion started by: filosophizer
0 Replies
3. AIX
Hi,
I want to know if there is any command which will tell me if an AIX machine is a LPar or not. I am using "lparstat -i" but it does not work on all AIX machines. Is there any generic command by whose output I will come to know if it is an LPar or not?
Please help.
Thanks,
Vineet (3 Replies)
Discussion started by: vineetd
3 Replies
4. AIX
Hello, we have a wierd and urgent problem, with a few of our p595 LPARs running AIX 5.3. The LPARs ran AIX 5.3 TL 7 and booted off EMC SAN disks, using EMC Powerpath. Every boot we run "pprootdev on" and "pprootdev fix". We can issue "bosboot -a" and we can reboot the machines.
Now, on two... (2 Replies)
Discussion started by: rwesterik
2 Replies
5. Solaris
Hi All,
I recently got a connection to the SAN through a fibre channel on my solaris box:
#luxadm -e port
/devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:devctl CONNECTED
#ls -l /dev/cfg
lrwxrwxrwx 1 root root 48 Feb 23 12:31 c4 -> ../../devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:fc
I then... (2 Replies)
Discussion started by: dede
2 Replies
6. AIX
Hi Guru, my question is that can I create LPAR in AIX 5.3, 6.0, 6.1 by using smit lpar, rather than using HMC or AIX Commands? Thank you very much. Mir Alihttp://xwww.unix.com/images/icons/icon5.gif (3 Replies)
Discussion started by: Tahniet
3 Replies
7. AIX
I have login into a server, and when i launch this command uname -L.
I can see there is a LPAR.
But is there anymore commands i can use to get more information on the LPAR ?
like it is VIO ?
wat the IP address ?
etc, etc.
please help. Thank you. (7 Replies)
Discussion started by: wingcross
7 Replies
8. AIX
We are running into a problem that we thought had solved but no go...
We have multiple machine types but 1 AIX and 2 i550 (AS/400) with 4 lpar each.
Existing AIX is an old (2004 vintage) machine with 5.2 on it for historical use only.
Existing Power6 i550 running code that will used... (6 Replies)
Discussion started by: jackb_guppy
6 Replies
9. AIX
Hello,
I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior.
for example
1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert.
2) disk usage alerts
3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies
10. UNIX for Beginners Questions & Answers
We have 2 LPAR. LPAR #1 have a Application, Database Server process (ctree Server) and SAN+Physical Table. LPAR#2 has only Application.
Both Application process are connected to Database via C-tree Server Process (Running on LPAR #1..
We want to keep one Active C-tree Server and one Backup... (1 Reply)
Discussion started by: gabhanes
1 Replies
LEARN ABOUT OSF1
kseg_to_phys
KSEG_TO_PHYS(9r) KSEG_TO_PHYS(9r)
NAME
KSEG_TO_PHYS - General: Converts a kernel-unmapped virtual address to a physical address
SYNOPSIS
vm_offset_t KSEG_TO_PHYS(
vm_offset_t addr );
ARGUMENTS
Specifies the buffer virtual address to convert to a physical address.
DESCRIPTION
The KSEG_TO_PHYS routine converts a kernel-unmapped virtual address to a kernel physical address. Device drivers can use this physical
address in DMA operations. Prior to calling KSEG_TO_PHYS, device driver writers often call one of the following routines to determine
whether the address passed is a virtual address in the addressed kernel segment: IS_KSEG_VA
Determines if the specified address is located in the kernel-unmapped address space. IS_SEG0_VA
Determines if the specified address is located in the user-mapped address space. IS_SEG1_VA
Determines if the specified address is located in the kernel-mapped address space.
RETURN VALUES
Upon successful completion, KSEG_TO_PHYS returns the physical address.
EXAMPLE
The following code fragment shows a call to KSEG_TO_PHYS:
. . .
caddr_t virt_addr; [1] unsigned phys_addr; [2]
. . .
if(IS_KSEG_VA(virt_addr)) { [3]
phys_addr = KSEG_TO_PHYS(virt_addr); [4]
. . .
Declares a variable to store the user buffer's virtual address. Declares a variable to store the physical address returned by
KSEG_TO_PHYS. Before calling KSEG_TO_PHYS, calls IS_KSEG_VA to determine if the virtual address is from the kernel-unmapped address space.
If the virtual address is from the kernel-unmapped address space, then calls KSEG_TO_PHYS to convert the address to a corresponding physi-
cal address.
SEE ALSO
Routines: IS_KSEG_VA(9r), PHYS_TO_KSEG(9r)
KSEG_TO_PHYS(9r)