Strange behavior on one of my server Post: 302875083

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Strange Behavior on COM2

Hi, I have a problem with a new touch screen controller that I am trying to use on a SCO 3.0 system. THe touch screen controller only wants to talk at 9600baud. I have updated /etc/inittab per the manual and also edited /usr/lib/event/devices to use 9600 baud. The only way I can get the...

2. Shell Programming and Scripting

Very Strange Behavior for redirection

I have searched far and wide for an explanation for some odd behavior for output redirection and haven't come up with anything. A co-worker was working on old scripts which have run for years and embedded in their code were output redirects which worked for the script during execution and then...

3. Shell Programming and Scripting

nawk strange behavior

Dear guys; when deleting repeated lines using nawk as below ; Why the below syntax works? nawk ' !a++' infile > outfile and when using the other below syntax the nawk doesn't work? nawk ' { !a++ } ' infile > outfile or nawk ' { !a++ } ' infile > outfile BR

4. Programming

Strange behavior in C++

I have the following program: int main(int argc, char** argv){ unsigned long int mean=0; for(int i=1;i<10;i++){ mean+=poisson(12); cout<<mean<<endl; } cout<<"Sum of poisson: "<< mean; return 0; } when I run it, I get the...

5. Ubuntu

Ubuntu strange behavior

It is so till login screen. I mean that when I boot my computer, Ubuntu shows a splash screen with mouse instead of Ubuntu logo and in the login screen it shows XUbuntu login screen... It began when I upgraded to previous kernel, I suppose, but I'm not sure... I can't say that it annoys me very...

6. Red Hat

strange mail behavior

Hi I have script to to take backup and send mail to a group once a day. One strange behavior I have observed recently is that most of the time the mail we receive is fine . But someday it just sends out mail without any subject with undisclosed recipients. I dont know how to find the cause...

7. AIX

Strange memory behavior

Hello together, i have a strange memory behavior on a AIX 7.1 System, which i cannot explain. The Filesystem-Cache will not be grow up and drops often after few minutes. I know if a file was deleted, that the same segment in the FS-Cache will also be cleared. But i am not sure if this is the...

8. AIX

Strange behavior with tar

I am trying to create an archive using tar. I am specifying a list of directories using the -L option. For testing purposes I created a simple directory structure: /backup/test /backup/test/test1 /backup/test/test2 The file specified by the -L option, named files.txt, contains:...

9. Shell Programming and Scripting

Strange Ctrl+C behavior

Hello All, I have a strange issue. I've created a shell script which connects to RMAN (Oracle Recovery Manager) and executes full DB backup. I then executed this script with nohup and in the background: $ nohup my_script.sh > logfile.log 2>&1 &The issue is that when I tried to take a look into...

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)