Thanks JohnF. I understand that SEA is a Layer 2 bridge between the physical and the virtual interface. But in this case , only ent1 has a I/P. So, without the I/p how is the trafiic send from ent0 or ent2 ?
I have had another look at the listing and now fully understand what is going on and your problem!
The VIO server is fitted with a four port ethernet card hence ent0, 1, 2, and 3 which is not listed but must be there as the first virtual connector became ent4 with ent5 as its control channel (These were created on the HMC before the etherchannel adapter was created hence the etherchannel adapter is ent6). The etherchannel was then created probably using the following command on the VIO server:
Following this the only virtual SEA was created on the VIO server using the following command:
All of this means the adapter ent1 is a physical port on the VIO server which is configured with a management / admin address (whichever your organisation uses).
As I said earlier you will need to connect the client LPARs virtual ethernet adapter to whichever VLAN id was declared when ent4 was created. To find this VLAN id you can either look at the VIO server on the HMC or run the command
which will list the VLAN id in the listing which is quite long!
Last edited by johnf; 07-26-2011 at 05:06 AM..
Reason: bad spelling!
I have a script running remotely using viosvrcmd command on hmc to back up the VIO servers. these are the steps involved
1. Mount the NFS directory on to the VIO server
2. run backupios command
3. un mount the directory
I am stuck up in the 3rd step. I am not able to unmount the nfs... (6 Replies)
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)
Hi Guys,
I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards...
... (2 Replies)
I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO.
On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes
Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hi,
I am facing an issue in vio server. When I run
bosboot -ad /dev/hdisk0
I am getting an error
trustchk: Verification of attributes failed: /usr/sbin/bootinfo
: accessauths
regards,
vjm
Please use code tags next time for your code and data. (8 Replies)
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
We've got two datacenters and in every datacenter 2 VIOs.
The VIO manages the I/O of the LPARs. So: Is it possible to reboot the VIO without shuting down an LPAR:wall: (4 Replies)
Hi Team,
My new build configuration always looking for the files from the build where i copied from.
please help me to resolve this.
I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development
I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
LEARN ABOUT HPUX
vxdiskadd
vxdiskadd(1M)vxdiskadd(1M)NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager
SYNOPSIS
vxdiskadd disk_address_pattern_list
DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd
prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned
replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for
the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the
disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or
allows the user to ask to make the decision for each disk individually.
One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of
this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to
specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case
of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the
specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify
all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more
examples:
all: all disks
c3 c4t2: all disks on controller 3 and controller 4, target 2
c3t4d2: a single disk (in the c#t#d# naming scheme)
xyz_0 : a single disk (in the enclosure based naming scheme)
xyz_ : all disks on the enclosure whose name is xyz
The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by
vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec-
ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0.
All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate.
Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message.
OPERATIONS
Reconnecting a drive that was temporarily inaccessible
This situation is detected automatically by noting that the specified drive has a disk ID that matches a disk media record with no
currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes
referring the disk are restarted. This reattach action is performed by calling the vxrecover utility.
Initialization of a disk with reserved regions
Initialization of the disk is performed by calling vxdisksetup.
Adding a disk to an existing disk group
This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so
that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free
space.
Creation of new disk groups in which to import a new disk
If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is
offered.
Hardware-Specific Note
Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM
follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the
force option. The force option ignores any such storage-specific guidelines.
FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations.
/etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations.
/etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations.
NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted
as CDS disks.
SEE ALSO vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M)VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)