Take a look on first lpar, we can see the virtual fiber, it comes from VIOS and routed to physical FC of Power machine.
Take a look on second lpar, it's not virtual. I wonder if it is actual physical FC from Power Machine assigned directly to lpar. --- Post updated at 09:27 AM ---
I wonder where those physical FC come from? As virtual FC comes from VIOS.
Moderator's Comments:
edit by bakunin: see my post below, please use CODE-tags. Thank you.
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)
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)
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)
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)
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)
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)
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)
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)
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 NETBSD
isp
ISP(4) BSD Kernel Interfaces Manual ISP(4)NAME
isp -- Qlogic based SCSI and FibreChannel SCSI Host Adapters
SYNOPSIS
isp* at pci? dev? function? (PCI)
isp* at sbus? slot ? offset ? (SBus)
scsibus* at isp?
DESCRIPTION
This driver provides access to SCSI or FibreChannel devices.
SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, and LVD (for the ISP1080 and ISP1280),
Fibre Channel support uses FCP SCSI profile for FibreChannel. and uses Class 3 connections only. Support is available for Public and Pri-
vate loops. Command tagging is supported for all (in fact, FibreChannel requires tagging).
CONFIGURATION
An optional flags 0x80 appended to the above isp* declarations will disable the download of driver firmware, which means you use whatever
firmware is running on the card. If no firmware is running on the card, the driver cannot operate the card.
An optional flags 0x40 appended to the above isp* declarations (can be OR'd in with the other config flags option) will keep the driver from
looking at device or bus NVRAM settings (this is in case NVRAM is just wrong and you have the card in a platform where it is inconvenient to
change NVRAM settings on the card).
HARDWARE
Supported cards include:
ISP1000
SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards.
PTI SBS440
Performance Technology ISP1000 variants.
ISP1020
Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards.
ISP1040
Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards.
PTI SBS450
Performance Technology ISP1040 variants.
Qlogic 1240
Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards.
Qlogic 1080
Qlogic 1280 LVD Ultra2 Wide PCI cards.
Qlogic 1280
Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards.
Qlogic 2100
Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop
Qlogic 2102
Qlogic Dual Loop 2100A Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2200
Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2202
Qlogic 2200 Dual Bus Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2204
Qlogic 2200 Quad Bus Optical Fibre Channel Arbitrated Loop PCI cards.
Qlogic 2300
Qlogic 2300 2-Gigabit Optical Fibre Channel PCI cards.
Qlogic 2312
Qlogic 2300 2-Gigabit Dual Channel Optical Fibre Channel PCI cards.
PTI SBS470
Performance Technology ISP2100 variants.
Antares P-0033
Antares Microsystems ISP2100 variants.
Qlogic 2400
Qlogic 2400 4-Gigabit Optical Fibre Channel PCI cards.
Qlogic 2500
Qlogic 2500 8-Gigabit Optical Fibre Channel PCI cards.
SEE ALSO cd(4), intro(4), scsi(4), sd(4), st(4)AUTHORS
The isp driver was written by Matthew Jacob for NASA/Ames Research Center.
BUGS
The driver currently ignores some NVRAM settings.
The driver currently doesn't do error recovery for timed out commands very gracefully.
Sometimes, when booting, the driver gets stuck waiting for the Fibre Channel firmware to tell it that the loop port database is ready. In
this case you'll see an announcement that the loop state has a value of 0x1. To unwedge the system, unplug and replug the fibre channel con-
nection, or otherwise cause a LIP (Loop Initialization Primitive sequence) - this will kick the firmware into getting unstuck.
BSD June 24, 2009 BSD