Sponsored Content
Operating Systems HP-UX Are you allowed to use the same vswitch for 2 separate HPVMs? Post 302841553 by lupin..the..3rd on Wednesday 7th of August 2013 01:55:14 PM
Old 08-07-2013
I'm curious to see the solution here, as I have the exact same problem. I have four VM's, all on the same vSwitch. Two of them can reach the gateway, the other two cannot. The two that cannot can ping other machines on the same vSwitch, but nothing outside of the vSwitch.

I've compared netconf, netstat -rn, hosts, nsswitch.conf, ipf is disabled, no vlan tagging, no apa, no serviceguard. All are identical as far as I can see, except for hostname and IP address.

I'm stumped. Smilie

Last edited by lupin..the..3rd; 08-07-2013 at 03:15 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Ldap dn chars allowed

Hi Is it possible to add the following to an ldif entry: dn=estmmartín i.e Note the charchter 'í' Thanks in advance (3 Replies)
Discussion started by: tom123
3 Replies

2. Web Development

access to my server is always allowed

Hi, I can't deny the access to my server. if I visit http://localhost I can always see all the files. Why ? <Directory /> Options FollowSymLinks AllowOverride None Order allow,deny Deny from All </Directory> <Directory "/Users/aneuryzma/Sites"> (4 Replies)
Discussion started by: aneuryzma
4 Replies

3. Solaris

Vswitch in Ldoms on VLAN tagged interface

I 've a T5220 running solaris 10u6 with Ldoms 1.1. following is o/p of my dladm e1000g0 type: non-vlan mtu: 1500 device: e1000g0 e1000g1 type: non-vlan mtu: 1500 device: e1000g1 e1000g531001 type: vlan 531 mtu: 1500 device: e1000g1 e1000g2 ... (0 Replies)
Discussion started by: fugitive
0 Replies

4. AIX

rlogin always allowed ?

Hello, Could someone explain why rlogin is allways allowed in my AIX 6.1 boxes, whatever user I use ? According to documentation it should work only when .rhosts (or hosts.equiv) is properly set. But even these files do not exist - access is allowed. If I use rsh(with specified command) it... (2 Replies)
Discussion started by: vilius
2 Replies

5. UNIX for Advanced & Expert Users

how to check if I'm allowed to ssh several hosts.

Hi guys! I'm working on a little script. I have a txtfile with several hosts, Unix team has copied my keys into several of those servers, but not all of them, I need to figure out which ones I don't have access to, (I want a list of servers I don't have access to, so I can request for it). This... (1 Reply)
Discussion started by: erick_tuk
1 Replies

6. Shell Programming and Scripting

space not allowed in input

I have this script. (options is an array) It works fine. It responds fine to all items that are stored in the array. But when I press spacebar when I am asked for input. It will not give an error only run the function again. While I put : || ] in the script to capture the space. What am I missing... (6 Replies)
Discussion started by: Alex400
6 Replies

7. Programming

Why is subclassing not allowed for many of the SWT Controls?

hi guys, Why is subclassing not allowed for many of the SWT Controls? But Eclipse itself creates our Shell classes in this way (inheriting from Shell) and then overriding checkSubclass() with empty body. So is it good(safe) that we do this way? I have two shells (Shell_1, Shell_2). Shell_1 is... (0 Replies)
Discussion started by: majid.merkava
0 Replies

8. HP-UX

Hpvmmodify: ERROR (host): The vswitch 'vmsw4' does not exist.

Hello Experts, I want to modify the CPU of my VM but when i am going to modify it , it showing the below error : hpvmmodify: ERROR (host): The vswitch 'vmsw4' does not exist. HPVM guest testhost configuration problems: Warning 1 on item vmsw4: Vswitch 'vmsw4' does not exist. These... (0 Replies)
Discussion started by: purushottamaher
0 Replies

9. Post Here to Contact Site Administrators and Moderators

Not allowed to post URLs

Hi, I tried to post some perl code for discussion (wrapped in swaddling . However, a regex has an escaped backslash so the forum parser sees it as an URL? Had the same experience with the sample data that I tried to provide for the same discussion. It contains emails addresses,... (1 Reply)
Discussion started by: msutfin
1 Replies

10. AIX

VSwitch not showing up on VIO Server

Want to run this by you all before opening a PMR with IBM Support. It's been a few weeks since I have done this so I can't be 100% sure of how I think it worked in the previous version. We upgraded our HMC's yesterday to 7.7.9 SP2 in hopes of fixing some issues we were having. Today I needed... (4 Replies)
Discussion started by: juredd1
4 Replies
ovs-appctl(8)							Open vSwitch Manual						     ovs-appctl(8)

NAME
ovs-appctl - utility for configuring running Open vSwitch daemons SYNOPSIS
ovs-appctl [--target=target | -t target] command [arg...] ovs-appctl --help ovs-appctl --version DESCRIPTION
Open vSwitch daemons accept certain commands at runtime to control their behavior and query their settings. Every daemon accepts a common set of commands documented under COMMON COMMANDS below, and ovs-vswitchd in particular accepts a number of additional commands documented in ovs-vswitchd(8). The ovs-appctl program provides a simple way to invoke these commands. The command to be sent is specified on ovs-appctl's command line as non-option arguments. ovs-appctl sends the command and prints the daemon's response on standard output. In normal use only a single option is accepted: -t target --target=target Tells ovs-appctl which daemon to contact. If target begins with / it must name a Unix domain socket on which an Open vSwitch daemon is listening for control channel connec- tions. By default, each daemon listens on a Unix domain socket named /var/run/openvswitch/program.pid.ctl, where program is the program's name and pid is its process ID. For example, if ovs-vswitchd has PID 123, it would listen on /var/run/open- vswitch/ovs-vswitchd.123.ctl. Otherwise, ovs-appctl looks for a pidfile, that is, a file whose contents are the process ID of a running process as a decimal num- ber, named /var/run/openvswitch/target.pid. (The --pidfile option makes an Open vSwitch daemon create a pidfile.) ovs-appctl reads the pidfile, then looks for a Unix socket named /var/run/openvswitch/target.pid.ctl, where pid is replaced by the process ID read from the pidfile, and uses that file as if it had been specified directly as the target. The default target is ovs-vswitchd. COMMON COMMANDS
Every Open vSwitch daemon supports a common set of commands, which are documented in this section. GENERAL COMMANDS These commands display daemon-specific commands and the running version. Note that these commands are different from the --help and --ver- sion options that return information about the ovs-appctl utility itself. help Lists the commands supported by the target. version Displays the version and compilation date of the target. LOGGING COMMANDS Open vSwitch has several log levels. The highest-severity log level is: OFF No message is ever logged at this level, so setting a logging facility's log level to OFF disables logging to that facility. The following log levels, in order of descending severity, are available: EMER A major failure forced a process to abort. ERR A high-level operation or a subsystem failed. Attention is warranted. WARN A low-level operation failed, but higher-level subsystems may be able to recover. INFO Information that may be useful in retrospect when investigating a problem. DBG Information useful only to someone with intricate knowledge of the system, or that would commonly cause too-voluminous log output. Log messages at this level are not logged by default. Every Open vSwitch daemon supports the following commands for examining and adjusting log levels. vlog/list Lists the known logging modules and their current levels. vlog/set module[:facility[:level]] Sets the logging level for module in facility to level. The module may be any valid module name (as displayed by the --list option) or the special name ANY to set the logging levels for all modules. The facility may be syslog or console to set the levels for log- ging to the system log or to the console, respectively, or ANY to set the logging levels for both facilities. If it is omitted, facility defaults to ANY. The level must be one of off, emer, err, warn, info, or dbg, designating the minimum severity of a mes- sage for it to be logged. If it is omitted, level defaults to dbg. vlog/set PATTERN:facility:pattern Sets the log pattern for facility to pattern. Each time a message is logged to facility, pattern determines the message's format- ting. Most characters in pattern are copied literally to the log, but special escapes beginning with % are expanded as follows: %A The name of the application logging the message, e.g. ovs-vswitchd. %c The name of the module (as shown by ovs-appctl --list) logging the message. %d The current date and time in ISO 8601 format (YYYY-MM-DD HH:MM:SS). %d{format} The current date and time in the specified format, which takes the same format as the template argument to strftime(3). %m The message being logged. %N A serial number for this message within this run of the program, as a decimal number. The first message a program logs has serial number 1, the second one has serial number 2, and so on. %n A new-line. %p The level at which the message is logged, e.g. DBG. %P The program's process ID (pid), as a decimal number. %r The number of milliseconds elapsed from the start of the application to the time the message was logged. %% A literal %. A few options may appear between the % and the format specifier character, in this order: - Left justify the escape's expansion within its field width. Right justification is the default. 0 Pad the field to the field width with 0s. Padding with spaces is the default. width A number specifies the minimum field width. If the escape expands to fewer characters than width then it is padded to fill the field width. (A field wider than width is not truncated to fit.) The default pattern for console output is %d{%b %d %H:%M:%S}|%05N|%c|%p|%m; for syslog output, %05N|%c|%p|%m. vlog/reopen Causes the daemon to close and reopen its log file. (This is useful after rotating log files, to cause a new log file to be used.) This has no effect if the target application was not invoked with the --log-file option. OPTIONS
-h, --help Prints a brief help message to the console. -V, --version Prints version information to the console. BUGS
The protocol used to speak to Open vSwitch daemons does not contain a quoting mechanism, so command arguments should not generally contain white space. SEE ALSO
ovs-appctl can control the following daemons: ovs-vswitchd(8), ovs-controller(8), ovs-brcompatd(8). Open vSwitch November 2009 ovs-appctl(8)
All times are GMT -4. The time now is 08:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy