01-19-2010
the policy is set to Anti-Collocation, thank you for this hint!
I've found one mistake in the configuration, perhaps that's the problem. I changed the boot ip addresses a few weeks ago, which worked fine. But I didn't change the "communication path to node" in the node configuration screen in smit, it still shows the old boot ip. I don't know the purpose and the impact of this setting, maybe it's just for rsh access. Smit help says "This path will be taken to initiate communication with the node."
Cluster communication and clrsh both are working. I made several takeover tests.
I have to change the communication path during the next downtime of the system, then I can tell more.
cheers
funksen
9 More Discussions You Might Find Interesting
1. AIX
I have an LPAR in a P5 machine which has been setup in an HACMP cluster. The person who set it up allocated the wrong network adapter (en) to the persistent network. For the life of me I cannot find where I can re-assign this adapter. Anyone able to help me as I am tearing my hair out and do not... (1 Reply)
Discussion started by: johnf
1 Replies
2. AIX
Hi,
I have two resource grps in hacmp 5.2 cluster.One is cascading and other is concurrent.
I have apply one svc_ip to cascading rg but not able to apply any svc ip with node bound option for concurrent rg.
Can any one guide me with the step to apply svc ip .
thanks in advance (0 Replies)
Discussion started by: aix_53
0 Replies
3. UNIX for Dummies Questions & Answers
When I was using windowsXP I encountered a file manager called UltraExplorer http://www.mustangpeak.net/ultraexplorer.html that appeared really impressive.
Now in the Linux/UNIX world I was pointed towards a similar idea called 4Pane
http://www.4pane.co.uk/
I'm surprised to do a search on... (3 Replies)
Discussion started by: catch22
3 Replies
4. Solaris
In my Solaris 10 - Netra CP3060, the following particular script is not running:
lrc:/etc/rc2_d/S00set-tmp-permissions
lrc:/etc/rc2_d/S07set-tmp-permissions
Above script is to set the default permission of /tmp & /var/tmp while rebooting if it found any inconsistencies. I changed the file... (4 Replies)
Discussion started by: ramnagaraj
4 Replies
5. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
6. AIX
Hi,
I have a running HACMP Cluster with two nodes. Its working in active/passive mode. (i.e Out of the two nodes in the cluster one will be active and the other one will be on standby. If first node fails the other takes over)
1. There is a Service IP associated with the cluster. Now the... (2 Replies)
Discussion started by: aixromeo
2 Replies
7. UNIX for Dummies Questions & Answers
Hi Everybody,
How can I understand when I login to any unix server that this server is having ftp service running? what I care is that I want to ftp something to this server and I can't, something like connection refuse. is there any ways to understand if the ftp is setup? and if not, how to set... (2 Replies)
Discussion started by: messi777
2 Replies
8. AIX
Would anyone please kindly help to solve this problem...
An LPAR with the below network configuration. ent0 and ent1 are logical lan (virtual ethernet) from VIO SEA.
en0
1.2.3.4 <- boot ip
192.168.1.1 <- persistent ip
192.168.1.10 <- service ip
en1
11.22.33.44 <- boot ip
When I... (6 Replies)
Discussion started by: skeyeung
6 Replies
9. AIX
Hi,
We had a hardware problem with an IBM System p5 server, with AIX 5.2
We restore from a tape the last backup we had, but the server does not boot up as expected.
The server try to mount some directories from a storage, but could not comunicate with them, we check the FC and everything is... (12 Replies)
Discussion started by: trevian3969
12 Replies
LEARN ABOUT OPENSOLARIS
di_path_phci_next_path
di_path_client_next_path(3DEVINFO) Device Information Library Functions di_path_client_next_path(3DEVINFO)
NAME
di_path_client_next_path, di_path_phci_next_path - libdevinfo path node traversal functions
SYNOPSIS
cc [ flag... ] file... -ldevinfo [ library... ]
#include <libdevinfo.h>
di_path_t di_path_client_next_path(di_node_t node node,
di_path_t path);
di_path_t di_path_phci_next_path(di_node_t node node,
di_path_t path);
PARAMETERS
node The handle to a device node in a di_init(3DEVINFO) snapshot. For di_path_client_next_path(), node must be a client device node.
For di_path_phci_next_path(), node must be a pHCI device node.
path DI_PATH_NIL, or the handle to a path node in a snapshot.
DESCRIPTION
Each path node is an element in a pHCI-client matrix. The matrix is implemented by dual linked lists: one list links path nodes related to
a common client head, and the other links path nodes related to a common pHCI head.
The di_path_client_next_path() function is called on a multipathing 'client' device node, where a 'client' is the child of a vHCI device
node, and is associated with a specific endpoint device identity (independent of physical paths). If the path argument is NULL,
di_path_client_next_path() returns the first path node associated with the client. To walk all path nodes associated with a client,
returned di_path_t values are fed back into di_path_client_next_path(), via the path argument, until a null path node is returned. For
each path node, di_path_bus_addr(3DEVINFO) returns the pHCI child path node unit-address.
The di_path_phci_next_path() function is called on a multipathing pHCI device node. If the path argument is NULL, di_path_phci_next_path()
returns the first path node associated with the pHCI. To walk all path nodes associated with a pHCI, returned di_path_t values are fed back
into di_path_phci_next_path(), via the path argument, until a null path node is returned. For each path node, di_path_client_node(3DEV-
INFO) provides a pointer to the associated client device node.
A device node can be a client device node of one multipathing class and a pHCI device node of another class.
RETURN VALUES
Upon successful completion, a handle to the next path node is returned. Otherwise, DI_PATH_NIL is returned and errno is set to indicate the
error.
ERRORS
These functions will fail if:
EINVAL One or more argument was invalid.
ENOTSUP Path node information is not available in the snapshot.
ENXIO The end of the path node list was reached.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|MT-Level |Safe |
+-----------------------------+-----------------------------+
SEE ALSO
di_init(3DEVINFO), di_path_bus_addr(3DEVINFO), di_path_client_node(3DEVINFO), libdevinfo(3LIB), attributes(5)
Writing Device Drivers
SunOS 5.11 15 May 2008 di_path_client_next_path(3DEVINFO)