Sponsored Content
Operating Systems AIX Upgrading from native MPIO to SDDPCM AIX 6.1 Post 302512743 by manojbiswakarma on Monday 11th of April 2011 12:59:55 PM
Old 04-11-2011
Upgrading from native MPIO to SDDPCM AIX 6.1

Try these command and paste the output:
# datapath query adapter
# datapath query device


Regards
Manoj
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX MPIO and EMC

We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies

2. AIX

AIX 5.3 MPIO vs RDAC on DS4000 range

Hi I would like to ask what the benefits are of changing from RDAC to MPIO when connecting to a DS4000 on AIX 5.3? I have heard that IBM MPIO "might" support more than 1 active path to a LUN when connecting to a DS4800 through more than 1 host connection on the same AIX client. I understand that... (8 Replies)
Discussion started by: kimyo
8 Replies

3. AIX

AIX native MPIO

Hi folks, does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
3 Replies

4. AIX

SDD SDDPCM MPIO lspath Jargon

Can anyone recommend me some reading material surrounding how AIX handles LUNs: - with and without MPIO installed - with and without SDD or SDDPCM installed Where does lspath sit in all of this (MPIO layer?). Can a system be built with just MPIO software? Is MPIO software even needed? I guess... (0 Replies)
Discussion started by: apra143
0 Replies

5. AIX

Upgrading AIX 5.2 to AIX 6.1 - GCC compatibility

Hi All, We are in the processing of upgrading our AIX server OS from 5.2.0.0 to 6.1. And we have a set of highly critical running C applications in AIX box. I have a question like whether this upgradation of OS will affect any C code compilation and C runtime enviornment... how does AIX 6.1... (1 Reply)
Discussion started by: karthikc
1 Replies

6. AIX

Uninstall native MPIO driver on AIX

Hi, I was trying to uninstall the native MPIO driver on the AIX 6.1 machine we have in our lab and ran into a whole bunch dependent filesets initially. I deleted the disks, fcsX, fscsiX, fcnetX and tried again, but ran into the same error. Subsequently, I figured out that the OS disks in... (4 Replies)
Discussion started by: ronykris
4 Replies

7. AIX

AIX with SDD to VIOed SDDPCM?

Hi folks. We want to move a "physical" AIX box to a VIOed LPAR. The physical box is running SDD with disks from a DS8300. I want to be able to reattach those LUNs from the DS8300 to my VIO server which is running SDDPCM and then assigned them back to my AIX LPAR. Any thoughts about this? I... (1 Reply)
Discussion started by: Stephan
1 Replies

8. AIX

New to AIX need help Installing/Upgrading Samba on AIX 7.1?

Hello, I am trying to update Samba on my AIX 7.1 system as there is an issues with it, the smbd process coredumps and I have had no luck figuring it out why. My approach is to try to re-install a newer samba and I have found the latest 3.x package for samba in ppc.rpm format at perlz.org ... (6 Replies)
Discussion started by: c3rb3rus
6 Replies

9. AIX

Need Help with SDD / SDDPCM / MPIO

This is getting very confusing for me, and appreciate if someone can help. Platform: Power VM ( Virtual I/O Server) ioslevel 2.1.3.10-FP23 # oslevel -s 6100-05-00-0000 Storage: IBM DS4300 Two HBAs - Dual Port Fibre Adapter Channels Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
3 Replies

10. AIX

issue AIX MPIO path closed

Hello, I have encountered the issue on my AIX 6.1. As you can see below, the hdisk1 & hdisk8 are not recognized by the system / > lspv hdisk0 00fa6d1288c820aa rootvg active hdisk1 00fa6d1288c8213c None hdisk2 ... (9 Replies)
Discussion started by: Phat
9 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 07:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy