04-07-2010
I think I only have one other thought. bakunin suggested installing on some spare hardware and taking down the production machine to avoid duplicate IP address after the spare hardware comes up.
I have done the same thing here but placed the spare hardware on a different VLAN than the production hardware. Setup a temp hostname in the /etc/hosts file, such as unixtest and given it an unused IP from the other VLAN. Create a new host within NIM called unixtest. Then you should be able to leave the current production up because after the install finishes on test hardware even when the production IP is placed on test hardware it will not be detected since it will be on a different VLAN.
Then you can get in through the console, HMC, etc..... to change the IP to a usable one for that VLAN. Just be cautious about crontab entries on the test machine running and doing things you don't want them to.
10 More Discussions You Might Find Interesting
1. AIX
I have multiple LPARS on p650 with mix of AIX5.2 and AIX5.1 with different rml level
My understanding is creating mksysb nim on NIM server is for new installation of LPARS
Then;
How do I do mksysb backup on existing lpars for recovery purpose or how do I do all mksysb to a NFS mounted Filesystem... (1 Reply)
Discussion started by: melindaj
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I'm trying to use my NIM server to get a mksysb of an lpar on another machine on my network.
I'm trying to define a resource through smitty and i've entered the resource name, Server of resource & location of resource, they are as follows
Resource Name : gmt_fail_mksysb
Server of... (1 Reply)
Discussion started by: KeesH
1 Replies
3. Shell Programming and Scripting
#!/bin/ksh
#
# nim_mksysb
# get mksysb from each client machine specified with -m. If no
# machines specified, get mksysb from ALL machines. -r flag says
# remove oldest existing mksysb for the machines being backed up.
# use -n no_make flag with -r to remove a generation of mksysb,
#... (0 Replies)
Discussion started by: barkath
0 Replies
4. AIX
Can a NIM client mksysb restore be performed via NIM (smitty nim) without the NIM client machine having the NIM server's IP and hostname in its /etc/hosts file? (10 Replies)
Discussion started by: kah00na
10 Replies
5. AIX
Hi,
I am trying to backup a system ("client") through a slow network using "nim mksysb" on a nim server ("master")
The backup starts, but doesn't success.
Thanks if you can help me to resolve this problem :
Creating information file (/image.data) for rootvg...
Creating list of files to... (2 Replies)
Discussion started by: astjen
2 Replies
6. AIX
Hello,
I need to install "bos.adt.libm 5.3.0.0" on a server (AIX5.3 power 5).
How to install it from a nim mksysb of an another partition ?
Thank you (3 Replies)
Discussion started by: astjen
3 Replies
7. AIX
please provide me with the steps to restore from mksysb tape. i m using AIX 5.3 TL 7 (2 Replies)
Discussion started by: debasis9
2 Replies
8. AIX
Hi All,
Please excuse the possibly naive question but I'm trying to clone/install a new AIX 5.3 LPAR on a p570 from a mksysb image file using nim. Has anyone done this before and if so, what would the exact command look like?
Does it even remotely resemble something like
nim -o... (1 Reply)
Discussion started by: combustables
1 Replies
9. AIX
I am implementing mksysb backups using NIM. I am using nimsh as client communication and mksysb backup are working fine, but this requires remote logon to be enabled for root.
Any thoughts on how can I implement mksysb backups using NIM without enabling remote logon for "root" ? (1 Reply)
Discussion started by: mk8570
1 Replies
10. AIX
Hi,
I am an newbie to AIX.
Recently, I being assigned to do an mksysb restoration at our DR site.
It always encounter "Out of Space" during restoration, this is even when I restored to 4x146GB HDD.
Even though, on production, it only need 2x146GB HDD for the rootvg.
What is the problem, I... (19 Replies)
Discussion started by: AIXBlueCat
19 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)