TEAMDCTL(8) teamd control TEAMDCTL(8)NAME
teamdctl -- team daemon control tool
teamdctl [options] team_device command [command_args...]
teamdctl is a tool that allows a user to interact with a running teamd instance. It defaults to using Unix Domain Sockets, but will fall
back to using the D-Bus API, to ensure reliable operation in all environments.
OPTIONS -h, --help
Print help text to console and exit.
Increase output verbosity.
Force output to one line if possible.
Force to use D-Bus interface.
-Z address, --force-zmq address
Force to use ZMQ interface. Possible address formats are "tcp://ip:port", "ipc://path" and others. Detailed description of ZMQ
library is in page http://zguide.zeromq.org/page:all.
Force to use UNIX domain socket interface. This is the default behavior.
Dumps teamd JSON config.
config dump noports
Dumps teamd JSON configuration without "ports" section included.
config dump actual
Dumps teamd actual JSON configuration. It includes ports which are currently present.
state dump | state
Dumps teamd JSON state document.
Prints out state of teamd parsed from JSON state document.
state item get state_item_path
Finds state item in JSON state document and returns its value.
state item set state_item_path value
Finds state item in JSON state document and sets its value by value parameter. This is available only for a limited number of paths:
ports.PORTIFNAME.runner.aggregator.selected -- This is available for lacp runner. User can manually select the aggregator.
runner.active_port -- This is available for activebackup runner. User can manually select the active port.
port add portdev
Takes port device name as argument. Adds port device into team.
port remove portdev
Takes port device name as argument. Removes port device from team.
port present portdev
Takes port device name as argument. Checks if the port device is present in team.
port config update portdev portconfig-string
Takes port device name as the first argument and JSON format configuration string as the second argument. Updates port device con-
port config dump portdev
Takes port device name as the first argument. Dumps port device JSON configuration to standard output.
SEE ALSO teamd(8), teamnl(8), teamd.conf(5)AUTHOR
Jiri Pirko is the original author and current maintainer of libteam.
libteam 2013-05-24 TEAMDCTL(8)
Check Out this Related Man Page
ports(7) Miscellaneous Information Manual ports(7)NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports
Default Serial Ports:
/dev/tty01 (not present on a single-port system)
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2
(COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial
printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel
port, for use with a parallel printer.
When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These
devices are located in the /dev directory.
For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a
terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if
one serial port is labeled with an icon for a terminal console) the remaining serial port.
If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also
be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports.
The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral-
lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel
printers, so fewer devices are connected to this port as compared to serial ports.
If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial
devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that
has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and
also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the
device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01).
If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you
use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2
(with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE
Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port
See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the
modem(7) reference page for more information on setting up modems.
Devices: ace(7), modem(7)
System Administration delim off