06-07-2009
Guys I need help, any thoughts & comments would be appreciated.
I have two VIOS
VIO_1
en0 = physical
mkvdev -sea ent0 -default ent2 -defaultid 101
en1 = physical / 172.16.101.10
ent0 = adapter with two ports
en3 = virtual / sea / 172.16.101.11
VIO_2
en0 = physical
mkvdev -sea ent0 -default ent2 -defaultid 101
en1 = physical / 172.16.101.12
ent0 = adapter with two ports
en3 = virtual / sea / 172.16.101.13
Lpar_1
en0 = 172.16.101.20
en1 = 10.10.10.20
Lpar_2
en0 = 172.16.101.21
en1 = 10.10.10.20
Lpar_3 ( HACMP )
en0 = 172.16.101.21
en1 = 10.10.10.20
en2 = 172.16.102.21 {boot IP}
en3 = 172.16.103.21 {Admin IP}
in HMC
- what is the VLAN ID, I should give to VIO_1 ?
{ should it be same as VLAN_ID i give it to LPAR_1 ? }
- VLAN ID for each LPARs for the subnet 10.x.x.x ?
- How can the subnet 10.x.x.x & 172.16.102.21 reach external network ?
any help would be appreciated.
9 More Discussions You Might Find Interesting
1. AIX
Hi,
I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7).
I extend my vg vg000 (on the partition) and add the 2 hdisks.
I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies
2. UNIX for Advanced & Expert Users
I understand that one should setup virtual ethernet adapters in the lpars which is the best way for various lpars to communicate with each other - Does anyone have info on this or can point me to a doc that explains how to set this up? (1 Reply)
Discussion started by: capeme
1 Replies
3. AIX
We're using VIO (not an HMC) to manage our LPAR's We have 3 physical adapters and 4 LPARs. Through the VIO interface we assigned 2 virtual interfaces but require a 3rd interface assigned to these LPARs. I am experiencing issues understanding exactly how to create another virtual adapter, either... (1 Reply)
Discussion started by: scottsl
1 Replies
4. AIX
Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR.
How can I do it without rebooting the LPARS.
POWER6 with HMC
LPARS = AIX 6.1
Any info
developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ...
But... (5 Replies)
Discussion started by: filosophizer
5 Replies
5. AIX
Lucky me, someone has installed a server and got it running with the best intentions, but leaving me a headache. :wall:
We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too.
The other two disks form a... (3 Replies)
Discussion started by: rbatte1
3 Replies
6. AIX
All
I am trying allocate an IVE to an LPAR (not a VIO) running AIX 7.1. I am getting the error:
HSCL068A
Explanation
Logical port can not be assigned to Logical Partition because this Logical Partition is not the promiscuous LPAR for the physical port.
Has anyone encountered this... (1 Reply)
Discussion started by: johnf
1 Replies
7. AIX
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)
Discussion started by: newtoaixos
1 Replies
8. AIX
Hi,
I just successfully build a Virtual Machine in virtual box with Perfectly running HMC v7. I have a IBM eServer pSeries Model 630 Model 6C4 (Power 4) i.e. 7024-6C4. I am not able to have it connect to the HMC console on the Virtual Box.
Can anyone help me on how to connect it to the... (8 Replies)
Discussion started by: uzair_rock
8 Replies
9. AIX
I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
2 Replies
LEARN ABOUT DEBIAN
ovs-vlan-test
ovs-vlan-test(1) Open vSwitch Manual ovs-vlan-test(1)
NAME
ovs-vlan-test - check Linux drivers for problems with vlan traffic
SYNOPSIS
ovs-vlan-test [-s | --server] control_ip vlan_ip
Common options:
[-h | --help] [-V | --version]
DESCRIPTION
The ovs-vlan-test utility has some limitations, for example, it does not use TCP in its tests. Also it does not take into account MTU to
detect potential edge cases. To overcome those limitations a new tool was developed - ovs-test. ovs-test is currently supported only on
Debian so, if possible try to use that on instead of ovs-vlan-test.
The ovs-vlan-test program may be used to check for problems sending 802.1Q traffic which may occur when running Open vSwitch. These prob-
lems can occur when Open vSwitch is used to send 802.1Q traffic through physical interfaces running certain drivers of certain Linux kernel
versions. To run a test, configure Open vSwitch to tag traffic originating from vlan_ip and forward it out the target interface. Then run
the ovs-vlan-test in client mode connecting to an ovs-vlan-test server. ovs-vlan-test will display "OK" if it did not detect problems.
Some examples of the types of problems that may be encountered are:
o When NICs use VLAN stripping on receive they must pass a pointer to a vlan_group when reporting the stripped tag to the networking
core. If no vlan_group is in use then some drivers just drop the extracted tag. Drivers are supposed to only enable stripping if a
vlan_group is registered but not all of them do that.
o On receive, some drivers handle priority tagged packets specially and don't pass the tag onto the network stack at all, so Open
vSwitch never has a chance to see it.
o Some drivers size their receive buffers based on whether a vlan_group is enabled, meaning that a maximum size packet with a VLAN tag
will not fit if no vlan_group is configured.
o On transmit, some drivers expect that VLAN acceleration will be used if it is available, which can only be done if a vlan_group is
configured. In these cases, the driver may fail to parse the packet and correctly setup checksum offloading or TSO.
Client Mode
An ovs-vlan-test client may be run on a host to check for VLAN connectivity problems. The client must be able to establish HTTP connec-
tions with an ovs-vlan-test server located at the specified control_ip address. UDP traffic sourced at vlan_ip should be tagged and
directed out the interface whose connectivity is being tested.
Server Mode
To conduct tests, an ovs-vlan-test server must be running on a host known not to have VLAN connectivity problems. The server must have a
control_ip on a non-VLAN network which clients can establish connectivity with. It must also have a vlan_ip address on a VLAN network
which clients will use to test their VLAN connectivity. Multiple clients may test against a single ovs-vlan-test server concurrently.
OPTIONS
-s, --server
Run in server mode.
-h, --help
Prints a brief help message to the console.
-V, --version
Prints version information to the console.
EXAMPLES
Display the Linux kernel version and driver of eth1.
uname -r
ethtool -i eth1
Set up a bridge which forwards traffic originating from 1.2.3.4 out eth1 with VLAN tag 10.
ovs-vsctl -- add-br vlan-br
-- add-port vlan-br eth1
-- add-port vlan-br vlan-br-tag tag=10
-- set Interface vlan-br-tag type=internal
ifconfig vlan-br-tag up 1.2.3.4
Run an ovs-vlan-test server listening for client control traffic on 172.16.0.142 port 8080 and VLAN traffic on the default port of 1.2.3.3.
ovs-vlan-test -s 172.16.0.142:8080 1.2.3.3
Run an ovs-vlan-test client with a control server located at 172.16.0.142 port 8080 and a local VLAN ip of 1.2.3.4.
ovs-vlan-test 172.16.0.142:8080 1.2.3.4
SEE ALSO
ovs-vswitchd(8), ovs-ofctl(8), ovs-vsctl(8), ovs-test(8), ethtool(8), uname(1)
Open vSwitch December 2010 ovs-vlan-test(1)