Now, If a client LPAR needs to send packets to a external address, how are the packets routed to the extenal network.
Will the packets go from Client LPAR (Virtual Ethernet) --->vios ENT7 - ENT4 - ENT1.
This is the best explanation I can give you. Consider a situation where you have a VLAN (100 for this example) then this VLAN will exist as physical and virtual (in the Hypervisor). Your example above would result in ent0 and ent2 would be connected to the physical VLAN and by virtue of the etherchannel construction ent6 is also connected.
the -defaultid 100 flag sets the VLAN id to 100 for this virtual adapter.
would result in the ent7 adapter being created. This is the virtual adapter which would carry the virtual VLAN address for LPAR communication through the VIO servers. Both VIO servers would have the same characteristics set so there would be identical Ethernet adpaters on both VIOS but the trunk priority would be set to alternate values (1, 2 etc).
When creating the Ethernet adapter on the client LPAR one selects the VLAN 100 on the drop down menu on the HMC on both VIO servers. As the adapters on the VIO server have been configured to talk on VLAN 100 nothing else needs to be done except allocating an IP address when the LPAR is powered on. No IP address needs to be added to the VIO virtual ethernet adapter.
All traffic to the outside world from the client LPAR would be as follows:
Client LPAR Ethernet adpater ent0 > along the Hypervisor VLAN 100 > into the VIO server SEA ent7 > Upto the virtual adapter ent4 > through the etherchannel adapter ent6 > finally out of ent0 and ent2 to the real network infrastructure.
This unfortunately is the hardest part of VIO construction to get your head around!
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 DEBIAN
fipvlan
FIPVLAN(8) Open-FCoE Tools FIPVLAN(8)NAME
fipvlan - Fibre Channel over Ethernet VLAN Discovery
SYNOPSIS
fipvlan [-c|--create] [-s|--start] interfaces
fipvlan -a|--auto [-c|--create] [-d|--debug] [-s|--start] [-l|--link-retry <num>]
fipvlan -h|--help
fipvlan -v|--version
DESCRIPTION
The fipvlan command performs Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) VLAN Discovery over Ethernet interfaces.
fipvlan can be used as a diagnostic tool to determine which VLANs have FCoE services available on a network, prior to configuring VLAN
interfaces and the Open-FCoE initiator. fipvlan can also be used to create VLAN interfaces as they are discovered, and to start the
Open-FCoE initiator. The --create and --start options are primarily intended to be used as part of an Open-FCoE boot solution. FCoE
instances started in this way cannot be destroyed or reset by fcoeadm.
fipvlan takes a list of network interface names to run the VLAN discovery protocol over, or the --auto option to use all available Ethernet
interfaces.
fipvlan will enable any interface which is found to be not enabled by the time the program runs. If no response is received on that
interface it will be shutdown again when fipvlan terminates.
OPTIONS -a, --auto
Use all Ethernet interfaces currently available
-c, --create
Create network interfaces for discovered FCoE VLANs. If a VLAN device already exists for a discovered VLAN, a new VLAN device will not
be created.
-d, --debug
Enable debugging output
-s, --start
Start the Open-FCoE initiator on discovered FCoE VLANs
-f, --suffix <suffix string>
Append the specified string <suffix string> to VLAN interface names.
-l, --link-retry <number of retries>
Retry check for link up up to <number of retries> times. The link state is retried every 500 ms. The default is 20.
-h, --help
Display a help message with basic usage instructions
-v, --version
Display the fipvlan version string
VLAN NAMING CONVENTIONS
The default VLAN device name is dev.vlan; where dev is the name of the Ethernet parent device and vlan is the discovered VLAN ID number. An
optional suffix can be appended to this with -f commandline option.
EXAMPLES
Display all discoverable VLANs with FCoE services
fipvlan --auto
Discover FCoE VLANs on interface eth2, create VLAN devices and start the Open-FCoE initiator
fipvlan --create --start eth2
In this example if FCoE services were available on VLAN 101 of network interface eth2, then a VLAN interface eth2.101-fcoe would be created
and used as the parent device for the initiator.
SEE ALSO fcoeadm(8)fcoemon(8)SUPPORT
fipvlan is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found
at the Open-FCoE website http://open-fcoe.org/
Open-FCoE 10/06/2011 FIPVLAN(8)