08-15-2008
Have you setup vdevvio1 as a NIM client yet?
Try logging into your vdevvio1 server as root (login as padmin, then oem_setup_env) and running "smitty nim" and set it up as a NIM client. This may be what the problem is.
10 More Discussions You Might Find Interesting
1. AIX
I have a standard template I deploy for each of my AIX servers. It's in a mksysb format which I pulled via the nim server after I originally set it up.
I'm trying to restore this mksysb over the wire to a remote system. The remote system is an lpar running under vio (no HMC attached). The disk... (1 Reply)
Discussion started by: scottsl
1 Replies
2. Shell Programming and Scripting
#!/bin/ksh
#
# nim_mksysb
# get mksysb from each client machine specified with -m. If no
# machines specified, get mksysb from ALL machines. -r flag says
# remove oldest existing mksysb for the machines being backed up.
# use -n no_make flag with -r to remove a generation of mksysb,
#... (0 Replies)
Discussion started by: barkath
0 Replies
3. Shell Programming and Scripting
Hi All,
I have some script that run some commands and send results to my email. I want to run same script on mulitiple servers. How can I do that. I know there is an option "ssh". But I'm not quite sure how to use it in the script.
And also. scripts has some parameters like following,
if :... (10 Replies)
Discussion started by: s_linux
10 Replies
4. Shell Programming and Scripting
Hello,
I am a Unix newbie and I need a script in which I can run a command on multiple servers at work. The command is to start a storage process and I am sick of doing it manually on all servers..
Here's the command:
/opt/bss/bin/snmptable -CB -v2c -c P67LzuBm hostname hrStorageTable... (4 Replies)
Discussion started by: kinyyy
4 Replies
5. Shell Programming and Scripting
Hi all,
I have a task for which I need to run some commands on one server1 and then jump from the server1 (using ssh and asking user to enter login credentials manually for server2 server) to server2 and run some commands there and exit.
I know the script I need here but problem is when I... (5 Replies)
Discussion started by: pat_pramod
5 Replies
6. UNIX for Dummies Questions & Answers
I want to grab all the luns in vscsi disks from vio that are assigned to client lpars. They are not powerpath disks. Now when I do lspv as root in vio server I see 956 disks..the problem right now is that each disks lun are in hex so when I do lscfg vpl from vio..the FRU number is on hex.
Can... (3 Replies)
Discussion started by: pregmi
3 Replies
7. AIX
Dears i have a total of 6 VIO servers i was trying to take a mksysb to the VIOs through NIM server but i can not process with it (6 Replies)
Discussion started by: thecobra151
6 Replies
8. AIX
I need run a command such as ps -ef |grep xxx on a batch of servers, how to write a script to run it without password? don't need go in each server to check?
Thanks (7 Replies)
Discussion started by: rainbow_bean
7 Replies
9. Shell Programming and Scripting
I need to run a script on a bunch of remote servers. how can this be done without ssh into each individual server and run it
its under /sbin/script.sh on each server (1 Reply)
Discussion started by: tdubb123
1 Replies
10. Shell Programming and Scripting
We have 15 servers. Hostnames for these 15 servers are stored in a text files and loop through each server to connect to the remote server and run a command, but this loop process runs the command one after another. However, the requirement is to run the same command on all 15 servers at the same... (10 Replies)
Discussion started by: laknar
10 Replies
LEARN ABOUT MINIX
rlogind
RLOGIND(8) System Manager's Manual RLOGIND(8)
NAME
rlogind, in.rld - remote login server
SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld
tcpd login /usr/sbin/in.rld
DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port
numbers from trusted hosts.
Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). When a service request
is received the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2) The server checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and
named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used.
Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so
that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance
of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in
rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line.
The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process
and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q
type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and
terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from
the client, and window size changes from the client are propagated to the pseudo terminal.
SEE ALSO
rlogin(1).
DIAGNOSTICS
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
``Try again.''
A fork by the server failed.
``/bin/sh: ...''
The user's login shell could not be started.
BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an ``open'' environment.
A facility to allow all data exchanges to be encrypted should be present.
A more extensible protocol should be used.
4.2 Berkeley Distribution May 24, 1986 RLOGIND(8)