Sponsored Content
Full Discussion: vpath to an hdisk
Operating Systems AIX vpath to an hdisk Post 302116260 by Sprellarinn on Wednesday 2nd of May 2007 04:06:41 PM
Old 05-02-2007
The vpaths you are reffering are virtual paths on san devices over SDD driver. Use the datapath command to map the relation between vpaths and hdisks - that is "datapath query device"
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX hdisk error

Does anyone have an idea what this means? hdisk10 is part of vg1. (vg1 has 11 hdisks) I get this msg every morning @ 5:04 CST This is the orignal message: A PROBLEM WAS DETECTED ON Fri Aug 17 03:02:09 PDT 2001 801014 The Service Request Number(s)/Probable Cause or... (2 Replies)
Discussion started by: Optimus_P
2 Replies

2. AIX

vpath fbvol relationship

Hi, I have a question about AIX vpaths and the fbvols you create via dscli on a DS8100 storage. Is there any command or any way to look which fbvol corresponds which vpath on operating system like the command fget_config -Av on a FastT storage system? I tried the datapath query device, datapath... (1 Reply)
Discussion started by: samaks
1 Replies

3. Shell Programming and Scripting

vpath directive in make

Hi all, I need to check the contents of my vpath directive in my file. Is it possible to check the contents of the vpath directive as we do for a variable like @echo '$vpath' . Please let me know the above is correct or suggest me the correct one. Thanks in advance. -Jerry (6 Replies)
Discussion started by: jerryragland
6 Replies

4. AIX

AIX vpath lun

Hi everyone, how can I check if I have LUNs in a server and the LUNīs vpath in AiX? thx (5 Replies)
Discussion started by: jcpetela
5 Replies

5. AIX

vpath and sharks

Hello everyone: just want to know how to get the name of the shark in which the vpath is? thanks (2 Replies)
Discussion started by: jcpetela
2 Replies

6. AIX

lscfg -vl vpath - error

Hello all, I need to run successfully this command : 1:root@abcd:/root # lscfg -vl vpathXY lscfg: device vpathXY not found. 1:root@abcd:/root # echo $? 1 If I run it on another server I will get no output which is ok : 1:root@efgh:/root # lscfg -vl vpathAB 1:root@efgh:/root # echo... (0 Replies)
Discussion started by: phobus
0 Replies

7. AIX

lscfg -vl vpath - error

Hello all, I need to run successfully this command : 1:root@abcd:/root # lscfg -vl vpathXY lscfg: device vpathXY not found. 1:root@abcd:/root # echo $? 1 If I run it on another server I will get no output which is ok : 1:root@efgh:/root # lscfg -vl vpathAB 1:root@efgh:/root # echo $?... (4 Replies)
Discussion started by: phobus
4 Replies

8. AIX

Flashcopy, ghost hdisk ??

Hi all, I'm getting some errors on AIX regarding Flashcopy and volume group hard disks. The script that activates flashcopy showed this errors: Recreating Flashcopy for lun01_A1 Performing syntax check... Syntax check complete. Executing script... Script execution complete. SMcli... (1 Reply)
Discussion started by: enux
1 Replies

9. Shell Programming and Scripting

Fetching hdisk sequence

Hi, Planning to implement script to fetch whether the hdisks are in proper sequence. Need output for incorrect sequence Correct #lspv hdisk0 hdisk1 hdisk2 :::::::::::: hdisk5 Incorrect sequence #lspv hdisk0 hdisk6 hdisk7 hdisk10 Any idea pls share (2 Replies)
Discussion started by: ksgnathan
2 Replies

10. AIX

How can I map hdisk# to rhdisk#?

Some storage/disks have been added to an existing AIX 6.1 server. The admin sent me the list of hdisk#'s for the new disks, but I need the corresponding rhdisk# for the same hdisk. (I know from past experience that the rhdisk that maps to an hdisk is not always the same number. For instance,... (5 Replies)
Discussion started by: sbrower
5 Replies
ovs-dpctl(8)							Open vSwitch Manual						      ovs-dpctl(8)

NAME
ovs-dpctl - administer Open vSwitch datapaths SYNOPSIS
ovs-dpctl [options] command [switch] [args...] DESCRIPTION
The ovs-dpctl program can create, modify, and delete Open vSwitch datapaths. A single machine may host up to 256 datapaths (numbered 0 to 255). A newly created datapath is associated with only one network device, a virtual network device sometimes called the datapath's ``local port''. A newly created datapath is not, however, associated with any of the host's other network devices. To intercept and process traf- fic on a given network device, use the add-if command to explicitly add that network device to the datapath. If ovs-vswitchd(8) is in use, use ovs-vsctl(8) instead of ovs-dpctl. Most ovs-dpctl commands that work with datapaths take an argument that specifies the name of the datapath. Datapath names take the form [type@]name, where name is the network device associated with the datapath's local port. If type is given, it specifies the datapath provider of name, otherwise the default provider system is assumed. The following commands manage datapaths. add-dp dp [netdev[,option]...] Creates datapath dp, with a local port also named dp. This will fail if a network device dp already exists. If netdevs are specified, ovs-dpctl adds them to the new datapath, just as if add-if was specified. del-dp dp Deletes datapath dp. If dp is associated with any network devices, they are automatically removed. add-if dp netdev[,option]... Adds each netdev to the set of network devices datapath dp monitors, where dp is the name of an existing datapath, and netdev is the name of one of the host's network devices, e.g. eth0. Once a network device has been added to a datapath, the datapath has complete ownership of the network device's traffic and the network device appears silent to the rest of the system. A netdev may be followed by a comma-separated list of options. The following options are currently supported: type=type Specifies the type of port to add. The default type is system. key=value Adds an arbitrary key-value option to the port's configuration. ovs-vswitchd.conf.db(5) documents the available port types and options. set-if dp port[,option]... Reconfigures each port in dp as specified. An option of the form key=value adds the specified key-value option to the port or over- rides an existing key's value. An option of the form key=, that is, without a value, deletes the key-value named key. The type of a port cannot be changed, so type=type is only allowed if type is the port's existing type. del-if dp netdev... Removes each netdev from the list of network devices datapath dp monitors. dump-dps Prints the name of each configured datapath on a separate line. [-s | --statistics] show [dp...] Prints a summary of configured datapaths, including their datapath numbers and a list of ports connected to each datapath. (The local port is identified as port 0.) If -s or --statistics is specified, then packet and byte counters are also printed for each port. If one or more datapaths are specified, information on only those datapaths are displayed. Otherwise, ovs-dpctl displays informa- tion about all configured datapaths. dump-flows dp Prints to the console all flow entries in datapath dp's flow table. This command is primarily useful for debugging Open vSwitch. The flow table entries that it displays are not OpenFlow flow entries. Instead, they are different and considerably simpler flows maintained by the Open vSwitch kernel module. del-flows dp Deletes all flow entries from datapath dp's flow table. This command is primarily useful for debugging Open vSwitch. As discussed in dump-flows, these entries are not OpenFlow flow entries. By deleting them, the process that set them up may be confused about their disappearance. OPTIONS
-s, --statistics Causes the show command to print packet and byte counters for each port within the datapaths that it shows. -t, --timeout=secs Limits ovs-dpctl runtime to approximately secs seconds. If the timeout expires, ovs-dpctl will exit with a SIGALRM signal. -vmodule[:facility[:level]], --verbose=module[:facility[:level]] Sets the logging level for module in facility to level: o module may be any valid module name (as displayed by the --list action on ovs-appctl(8)), or the special name ANY to set the logging levels for all modules. o facility may be syslog, console, or file to set the levels for logging to the system log, the console, or a file respec- tively, or ANY to set the logging levels for both facilities. If it is omitted, facility defaults to ANY. Regardless of the log levels set for file, logging to a file will not take place unless --log-file is also specified (see below). o level must be one of off, emer, err, warn, info, or dbg, designating the minimum severity of a message for it to be logged. If it is omitted, level defaults to dbg. See ovs-appctl(8) for a definition of each log level. -v, --verbose Sets the maximum logging verbosity level, equivalent to --verbose=ANY:ANY:dbg. -vPATTERN:facility:pattern, --verbose=PATTERN:facility:pattern Sets the log pattern for facility to pattern. Refer to ovs-appctl(8) for a description of the valid syntax for pattern. --log-file[=file] Enables logging to a file. If file is specified, then it is used as the exact name for the log file. The default log file name used if file is omitted is /var/log/openvswitch/ovs-dpctl.log. -h, --help Prints a brief help message to the console. -V, --version Prints version information to the console. SEE ALSO
ovs-appctl(8), ovs-vswitchd(8) Open vSwitch August 2009 ovs-dpctl(8)
All times are GMT -4. The time now is 05:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy