The simple answer is yes they are as follows:
The available adapters are:
FCS0 is from the first VIO with the partner adapter FCS2 from the second VIO
The adapter plus children are as follows:
The adapter from the other VIO server:
Dear all
I have a SCO server with a mapping to a NFS share on a linux server. The Linux server went down and the mapping on the SCO server failed. Now when I run the df -k command on the SCO server, the NFS mapping is showing the following error:
df: cannot statfs... (5 Replies)
Hello guys,
It would be so nice of you if someone can provide me with these informations.
1) My SAN group assigned 51G of LUN space to the VIO server.I ran cfgdev to discover the newly added LUN. Unfortunately most of the disks that are in VIO server is 51G. How would I know which is the newly... (3 Replies)
Is anyone here using NPIV with AIX? If you are, what type of switch are you connected to? Also, please share some impressions of NPIV over traditional port-to-port LUN assignments. We are looking to move to NPIV and need some convincing argume... I mean information. (2 Replies)
Hi All,
I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV.
My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They... (2 Replies)
Hi All..
On to a new implementation with AIX 7.1 san boot from EMC disks (Using NPIV). Anyone played with this recently?
Wondering if we need PowerPath on the AIX clients or has native MPIO matured to replace it. Thoughts?
Thanks
Mr B (6 Replies)
Hi,
I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers?
Thanks,
Ronald (2 Replies)
Hello,
I am using fgltty connection (which is actually qputty) to my AIX 6.1 server.
The problem is that PageUp and PageDown keys are not working and i cannot find a way to do the correct mapping for this issue. I read and tried many things that i saw in the web but nothing worked. Well... (2 Replies)
Hello,
I do not know if this is the right title to use. I have a large dictionary database which has the following structure:
where a b c d e are in English and p q r s t are in a target language., the two separated by the delimiter =.
What I am looking for is a perl script which will take... (5 Replies)
Hi All :)
i would like to know if i can customize the WWN of the new VFC (NPIV).
Or, if i must move the LPAR on another server with another FCS, i have to change the zoning??
Thanks in advance.
Mario
---------- Post updated 09-21-12 at 02:51 AM ---------- Previous update was 09-20-12 at... (1 Reply)
Please forgive me here as I don't fully understand what I am talking about here so if I use the wrong terminology please overlook me.
We have multiple AIX LPARs on the managed system with two VIO Servers. A Co-Worker and I are trying to set up a new LPAR client (The guy that knows this is out)... (14 Replies)
Discussion started by: juredd1
14 Replies
LEARN ABOUT HPUX
vxsplitlines
vxsplitlines(1M)vxsplitlines(1M)NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster
SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname]
DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk
group.
If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config-
uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot
import a disk group in this state unless you specify which disk's configuration copy to use.
You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information
together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid.
The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies.
The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import.
OPTIONS -c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name.
Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have
recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not
match.
-g diskgroup
Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the
vxdg(1M) manual page.
EXAMPLES
Display the disks on each side of the split in the disk group newdg:
vxsplitlines -g newdg
Display the SSB IDs stored in the configuration copy on disk c2t4d0:
vxsplitlines -g newdg -c c2t4d0
NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups.
The version number of the disk group must be 110 or greater.
SEE ALSO vxdg(1M)
Veritas Volume Manager Administrator's Guide
VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)