sknovice,
you seem to verify Oracle RAC network interfaces,
so why don't you just use the tool Oracle provides?
Assuming GI is already installed:
or
Where node1, node2, noden are your cluster nodes (all = all cluster nodes).
Hi All,
I need an automation script to check the connectivity between 2 UNIX servers.
Could anybody please help in this regards?
regards,
janardhan (1 Reply)
We have two servers A and B (both running Solaris 10) out of which one is application server and the other is database server. The two servers faced certain network issues and the two servers were temporarily disconnected.this happened around 5AM GMT monday.Can anyone suggest some log files or... (2 Replies)
HI I have made a connection with external server which is also UNIX. I was tryign connectivity with this by telnet which fails and ping i sshowing socket is alive and traceroute tells the asterisk astersik:traceroute to 153.88.182.28 (153.88.182.28), 30 hops max, 8080 byte packets
1 * * *
2 *... (1 Reply)
hi all
just installed the netsec.options.tcpwrapper from expansion pack, which used to be a rpm, for my aix 6.1 test box.
it is so unpredictable. i set up the hosts.deny as suggested for all and allow the sshd for specific ip addresses/hostnames.
the tcpdchk says the hosts allowed and... (0 Replies)
Hi All
I am having issues using ftp between a solaris 10 server to a HP-UX 11.31 server, but from the solaris server to the hp-ux I am able to ping. This is what I have done so far:
in the solaris server:
root@MPCRS01 # svcs -a | grep ftp
online Jul_26 svc:/network/ftp:default... (12 Replies)
Hello,
I have a requirement to check the tcp network connectivity between server it's running on and the list of host's and ports combination.
i have written the below code but it doesn't work, but when i execute the nc command outside the script it works fine.
please help me where i am... (8 Replies)
Newbie with UNIX here.
Currently troubleshooting a UNIX terminal we have.
I determined it to be bad and swapped it out with a known good terminal. I went in and changed the IP address and host name to reflect the old terminal. Although now there is no connectivity.
I swapped out the NIC... (1 Reply)
Hi everyone!
Some time ago, I had to check connectivity with a big list of hosts, using different formats (protocol://server:port/path/, server:port, ....).
I developed a script that checks the connectivity using different commands (ping, telnet, nc, curl).
It worked for me so I'm sharing it... (9 Replies)
I am trying to establish passwordless connectivity between server A and server B, but unsuccessfuly, because I beleive two issues.
the first one is that on both servers, it is not possible to use root to login, it only allows to connect using a user (any) them su - root, which in turns I am able... (1 Reply)
Discussion started by: fretagi
1 Replies
LEARN ABOUT HPUX
cmdo
cmdo(1m)cmdo(1m)NAME
cmdo - Execute process on multiple remote Serviceguard nodes.
SYNOPSIS
cmdo [[-n node_name]...] [-t timeout] command
DESCRIPTION
cmdo will execute a process on a multiple remote Serviceguard nodes and return any output or return value.
cmdo is limited in several ways. cmdo is best suited for situations where other remote execution facilities are not available. For a more
full featured tool for remote execution within a cluster, see cexec(1m) provided by Distributed Systems Administration Utilities.
To use this command, the local user must have the root access role on each of the involved nodes. For more information on Serviceguard
access control policies, see the manual, Managing Serviceguard.
To use the cmdo command without specifying -n options, the local node must be configured into a Serviceguard cluster. If no -n options are
specified, the command will be executed on all available nodes in the cluster.
The command will be executed in an environment which matches the local node. All environment variables defined locally will be available
on the remote node.
Output from stderr and stdout for the remote process will be combined and delivered in one transmission. This command should not be used
for interactive commands or commands which will return large quantities of output. Output from each node will be displayed sequentially as
the operation is executed on each remote node.
Input via stdin is not supported.
Killing the cmdo process does not stop any remote executions of the command. cmdo should not be used on any command which may hang without
specifying a timeout value.
Options And Arguments
-t timeout
Kill the executed command if it does not exit within the specified timeout (in seconds)
-n node_name
Serviceguard node to execute command on. If no -n options are specified, all the nodes configured in the cluster are used.
command
Command to execute on remote node. May be quoted.
RETURN VALUE
cmdo returns the following values:
0 Successful completed on all nodes.
>0 Command failed on one or more nodes with the specified exit value.
EXAMPLES
Execute an 'ls' in a remote directory on all nodes within the cluster.
cmdo ls /tmp
Execute an 'ls' in a remote directory on two nodes not configured within a Serviceguard cluster.
cmdo -n node1 -n node2 ls /tmp
AUTHOR
cmdo was developed by HP.
SEE ALSO cexec(1m), cmcp(1m), cmexec(1m), cmsync(1m), cmquerycl(1m), cmviewcl(1m)
Requires Optional Serviceguard Software cmdo(1m)