07-12-2011
OK, so I used the open IP from the HMC. and there is no need to connect the remote server to the HMC switch, since the HMC can use its open/public IP to connect to managed system. everything is working now.... sort of
You see, I opened the right ports from the firewall, and the servers appear on my HMC and everything is fine. Except, when I open the virtual terminal and I can't type anything. no keys or letters are registered to the terminal.
After searching for this problem. I found that the output from lscons is /dev/vty1. And I connected the servers on HMC0 port. So I guess i need to change it to /dev/vty0. But lsdev -C | grep vty shows that vty0 is defined, and vty1, vty2 are available. I'm confused now. How to change this to vty0? And do I even need to change it? Is this even correct or should look elsewhere for the solution?
Thanks
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear friends,
i need to connect sftp server from my home directory using script .
Please can anyone help me on this. (1 Reply)
Discussion started by: kittusri9
1 Replies
2. Shell Programming and Scripting
Hello all, I know that is a question which has made too many times, and I have been looking into the threads but all posted was not sucessfully for me so...
I need a shell script which connect two unix servers, but NOT using ssh... Is there another way to do it?
I've tried ssh but it didn't... (1 Reply)
Discussion started by: Geller
1 Replies
3. AIX
We have a production server at a client site running AIX. And recently when users are trying to connect to it via telnet, it prompts "No more multiple IP addresses to connect".
Can I know what does this error mean? and how to rectify this?
Thanks. (2 Replies)
Discussion started by: a_sim
2 Replies
4. Shell Programming and Scripting
Hello,
I have access to several linux servers (mostly centos based) located in a DC in another country.
from day to day I need to login to each of them to do some work (they dont have gui/window manager installed, I work only from console), or even to just do a check like df -h for disc usage.... (3 Replies)
Discussion started by: MaRiOsGR
3 Replies
5. Shell Programming and Scripting
Hi,
I need a script that will connect to a list of servers and first sudo to root and then run a couple of commands.
For security reasons, we can't setup ssh keys as root.
Manually I have to login to a server as user and then sudo to root.
It's not possible to use root@servername , because of... (8 Replies)
Discussion started by: misterx12345
8 Replies
6. UNIX for Dummies Questions & Answers
help me (0 Replies)
Discussion started by: sonu pandey
0 Replies
7. AIX
We have 2 p520 aix6.0 installed server.
Both the server in cluster. and managed by HMC v7
both servers have rebooted due to power outage.
Now both server state is STANDBY in HMC.
I am unable to login or ping to that servers.
Please help (5 Replies)
Discussion started by: reyazan
5 Replies
8. Shell Programming and Scripting
Hello Every one!!
I am trying to write a shell script which will connect to a remote server and execute scripts which are at a certain path in the remote server.
Before this I am using a sudo command to change the user.
The place where I am stuck is, I am able to connect to the... (6 Replies)
Discussion started by: masubram
6 Replies
9. Shell Programming and Scripting
I have a script, which connecting to remote server and first checks, if the files are there by timestamp. If not I want the script exit without error. Below is a code
TARFILE=${NAME}.tar
TARGZFILE=${NAME}.tar.gz
ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;... (3 Replies)
Discussion started by: digioleg54
3 Replies
10. UNIX for Advanced & Expert Users
Greetings Experts,
I am working for a bank client and have a question on connect-direct and SFTP.
We are using Linux RedHat servers. We use connect-direct to transfer (NDM) files from one server to another server. At times, we manually transfer the files using SFTP from one server to another... (2 Replies)
Discussion started by: chill3chee
2 Replies
LEARN ABOUT DEBIAN
llogin
LLOGIN(1) General Commands Manual LLOGIN(1)
NAME
llogin - Connect to a LAT service
SYNOPSIS
llogin [options] service
Options:
[-dvcpblhQ] [-H node] [-R port] [-n name] [-w password | -W] [-q quit char]
DESCRIPTION
llogin connects your terminal to a LAT service via latd, the service name must be known to latd for this to work.
OPTIONS
-d Shows learned services. This is the same as latcp -d -l
-d -v Verbose form of -d. -v without -d is ignored.
-H <node>
Remote nodename. If the service is advertised by more than one node and you want to connect to a particular node then use this
switch. By default you will be connected to the node with the highest rating.
-R <port>
Connect to a specific port on (usually) a terminal server. This is the port NAME on the server and not the port number.
-c Do not convert typed LF to CR. By default the enter key generates LF and llogin converts it CR as it is the most generically useful
translation. This switch will cause the enter key to send LF instead. Occasionally useful for connecting to Unix consoles.
-b Convert typed DEL to BS. By default the DEL key (keyboard, top right usually) send DEL (ASCII 0x7f) to the remote system. This
switch will cause the DEL key to send BS (ASCII 8) instead. Useful for some Unix systems connected via terminal servers.
-l Convert output LF to VT. By default LF output is sent as CRLF which can cause output formatting problems. Changing this to VT should
preserve the output formatting on most devices or terminal emulators.
-q <char>
Change the quit character. By default CTRL-] will quit the terminal session. Entering a character after -q will cause CTRL-<char> to
be the quit character for that session. -q0 will disable the quit character. If you use the latter, make sure you are connecting to
a service that will disconnect you when you log out or you will have to kill llogin from another session to get out of it!
-Q Tells latd that the service you are connecting to is queued service and not a normal login service or port service. Unfortunately
latd cannot tell whether a remote service needs to be queued or not so the onus is on the user to specify this switch when connect-
ing to a queued service.
-n <name>
Sets the local connection name. By default this will be your local TTY name. In most cases this simply affects the display of the
terminal on the remote end so you shouldn't need to change it.
-w <password>
Sends the password for the service. Only needed for services that require a password for access. If the password given is "-" then
you will be prompted for a password and it will not be echoed. This avoids having passwords visible on the screen.
-W Prompts for the service password. This is the same as -w- (see above).
-p Tells llogin to connect to the device named instead of a LAT service. This would usually be a /dev/lat pseudo-terminal but could be
any other device you like really. This switch does not make the program useful as a terminal program because there is no way to set
any serial parameters, nor am I going to add them. This is just a convenient way to use the /dev/lat ports without the overhead of
programs such as minicom.
-h Displays a brief usage description. This is the same as invoking llogin without any parameters at all.
SEE ALSO
latcp(8), latd(8)
LAT utilities January 3 2002 LLOGIN(1)