06-19-2016
Quote:
Originally Posted by
bakunin
What do you mean by that? Because the "PVID" (Physical Volume Identifier) has nothing to do with networks at all. Or is that completely unrelated to the rest of your question? In this case please create a new thread (or ask a moderator, we can split this thread into two for the separate questions).
I hope this helps.
bakunin
Sorry for the confusion there Bakunin. What I meant by the PVID is (Port VLAN ID) in the virtual ethernet adapter settings. But I know how this works now.
- K
---------- Post updated at 11:32 AM ---------- Previous update was at 11:26 AM ----------
Quote:
Originally Posted by
agent.kgb
if you can bring your systems offline:
1. add VLAN 31 to the network switch ports.
2. configure a new virtual adapter for VLAN 31 on both of your VIOSes.
3. configure the virtual adapter into the existing SEA.
4. configure a new virtual adapter for VLAN 31 for all of your AIX LPARs.
5. check that it works (usually it is enough to get it up with ifconfig and look at traffic with tcpdump, even without an IP address).
6. on day X, when you have downtime, remove your old virtual adapters with VLAN 30 from the AIX LPARs and configure IP addresses on the new virtual adapters.
7. if everything works ok, remove virtual adapter with VLAN 30 from SEA and from all VIOSes.
8. remove VLAN 30 from the network switch ports.
Thanks agent.kgb. This seems like a good plan. I will try this and see how it goes.
- Kaelu
10 More Discussions You Might Find Interesting
1. IP Networking
I understand how to change the ip address permanently however, I need to also make a permanent change to the subnet mask. How would I accomplish this. (5 Replies)
Discussion started by: johnparksjr
5 Replies
2. IP Networking
Hi,
My project needs to migrate the existing Subnet (255.255.255.0) to a new subnet and change the ipaddresses (currently C class). How can I do that. I need some information.
John (0 Replies)
Discussion started by: johnmarsh
0 Replies
3. Solaris
Hi,
I have a task to edit the subnet mask in almost 100+ solaris servers.Few of the servers are configured with IPMP.There will be no change of IP address or default gateway.If its a single IP we can bring NIC down,change the subnet mask in /etc/netmasks,then bring the NIC back to normal.But... (3 Replies)
Discussion started by: rajip23
3 Replies
4. AIX
AIX:Command to get netaddress/subnet address command in IPv4/IP6
Can anybody help us with a command to retrieve netaddress/subnet address command in IPv4/IP6 on aix machine.
net/subnet address is in the format 172.16.212.0(signifies all 255 machines in an IPv4 network) (2 Replies)
Discussion started by: rookie8278
2 Replies
5. AIX
I am new to this forum so please bare with me. I did search for this answer prior to posting but no luck.
Running an AIX NIM Master at 5.3TL9SP4, with about 100 clients. The subnet of one of the networks defined in the NIM env has changed. When I go to Manage Networks, Change/Show... (0 Replies)
Discussion started by: juredd1
0 Replies
6. Solaris
Hello,
can anyone help me with the command to change the subnet mask on solaris 10? The mask is currently 255.255.255.255 I will like to change it to 255.255.2555.0.
Thank you (5 Replies)
Discussion started by: cjashu
5 Replies
7. AIX
Hi,
I have a p520 with 2 cpus and 10gb of ram.Is it sufficient enough to create 2 lpars.What other things we have to check. (2 Replies)
Discussion started by: sekar52
2 Replies
8. AIX
Hello Everyone,
Can you please help me with the following questions regarding recycling LPARs.
1) Is it recommended to automate the reboot of AIX LPARs with a script ?
i mean we've few App LPARs and Database LPARs. we would like to bring down LPARs on last sunday of every month for about 1... (4 Replies)
Discussion started by: System Admin 77
4 Replies
9. AIX
Hi,
I've verified my AIX 7.1 LPAR , and TCB is disabled by default.
#odmget -q attribute=TCB_STATE PdAt
PdAt:
uniquetype = ""
attribute = "TCB_STATE"
deflt = "tcb_disabled"
values = ""
width = ""
type = ""
generic = ""
... (3 Replies)
Discussion started by: System Admin 77
3 Replies
10. UNIX for Advanced & Expert Users
Dear all,
I have a remote CentOS7 server that has two network cards. Each card has four ports and port one of card one was defined with the IP address assigned to the server. So far, so good and it's been working for over a year. We have now got cables sorted out so there are four paths... (4 Replies)
Discussion started by: rbatte1
4 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)