Sponsored Content
Full Discussion: DISK and MPIO
Operating Systems AIX DISK and MPIO Post 303033233 by Phat on Tuesday 2nd of April 2019 02:50:50 AM
Old 04-02-2019
Quote:
it depends on the layout of your FC fabric and it depends on your FC switches and how they are connected and zoned and, .... You see the problem?
Yes I see it and understand what you want to convey. By some reasons, I have not enough info to assess.
 

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

MPIO Driver

On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem. The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like 5.3 TL3 = IBM.MPIO 5.3.0.30 5.3... (0 Replies)
Discussion started by: clking
0 Replies

6. AIX

MPIO reliability

Hi, we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes. Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Discussion started by: zaxxon
8 Replies

7. AIX

MPIO - list of supported arrays

Hello, we are planning to deploy some of our databases on AIX/LPAR based servers (we didn't bought it yet ...). IBM's engineers says that if we want to boot them from SAN the hardware array has to be compatible with MPIO but they don't want to deliver any document with list of arrays supported... (5 Replies)
Discussion started by: andy55
5 Replies

8. AIX

Upgrading from native MPIO to SDDPCM AIX 6.1

We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC. Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers. My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies

9. AIX

Failed mpio path on AIX5.3

I have found failed mpio path on AIX and enabled that failed path as below failed path on AIX bash-3.2# lspath -l hdisk10 Enabled hdisk10 fscsi0 Enabled hdisk10 fscsi0 Failed hdisk10 fscsi3 Enabled hdisk10 fscsi3 Enabled failed path as below chpath -l hdisk10 -p fscsi3 -s enable... (13 Replies)
Discussion started by: murali969
13 Replies

10. 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
SYNCE_INFO_NEW(3)					       http://www.synce.org/						 SYNCE_INFO_NEW(3)

NAME
synce_info_new - allocate a new SynceInfo struct SYNOPSIS
#include <synce.h> SynceInfo *synce_info_new(const char *device_name); void synce_info_destroy(SynceInfo *info); const char *synce_info_get_name(SynceInfo *info); bool synce_info_get_os_version(SynceInfo *info, int os_major, int os_minor); int synce_info_get_build_number(SynceInfo *info); int synce_info_get_processor_type(SynceInfo *info); const char *synce_info_get_os_name(SynceInfo *info); const char *synce_info_get_model(SynceInfo *info); const char *synce_info_get_device_ip(SynceInfo *info); const char *synce_info_get_local_ip(SynceInfo *info); int synce_info_get_partner_id_1(SynceInfo *info); int synce_info_get_partner_id_2(SynceInfo *info); const char *synce_info_get_object_path(SynceInfo *info); pid_t synce_info_get_dccm_pid(SynceInfo *info); const char *synce_info_get_transport(SynceInfo *info); const char *synce_info_get_password(SynceInfo *info); int synce_info_get_key(SynceInfo *info); DESCRIPTION
The synce_info_new() function returns a pointer to a newly allocated and populated SynceInfo struct for a mobile device. If device_name is non-NULL, the returned struct relates to a mobile device with that name, or NULL if no device of that name is connected. If device_name is NULL, the exact behaviour depends on the flavour of dccm daemon in use. When using vdccm(1) or the deprecated dccm(1), the current active device is selected. This is usually the last device connected, specifically that described in the active_connection file which is by default in the ~/.synce/ directory. With odccm(1) the first device connected will be returned. With synce-hal this depends on the device(s) in question, and should be considered undefined. This struct should be freed with synce_info_destroy(3). typedef struct _SynceInfo { pid_t dccm_pid; /* process id of dccm daemon */ char* device_ip; /* device ip address */ char* local_iface_ip; /* local interface ip address */ char* password; /* device password */ int key; /* device pass key */ int os_major; /* device OS major version */ int os_minor; /* device OS minor version */ int build_number; /* OS build number */ int processor_type; /* device processor */ int partner_id_1; /* first sync partner id number */ int partner_id_2; /* second sync partner id number */ char* name; /* device name */ char* os_name; /* device OS name eg. PocketPC */ char* model; /* device hardware name */ char* transport; /* interface type */ char* object_path; /* path to device's information */ } SynceInfo; These fields must be accessed with the synce_info_get_ functions. The particular fields populated depend on the flavour of dccm daemon in use. The use of dccm(1) is deprecated. When using vdccm(1) all fields are populated except for local_iface_ip and os_minor. With odccm(1) and synce-hal, dccm_pid, password, key, build_number, partner_id_1 and partner_id_2 are not used. odccm(1) also does not populate local_iface_ip. RETURN VALUE
The synce_info_new() function returns a pointer to the allocated SynceInfo struct, or NULL if an error occured. SEE ALSO
synce(7), odccm(1), vdccm(1) The SynCE Project 2007-08-26 SYNCE_INFO_NEW(3)
All times are GMT -4. The time now is 07:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy