04-04-2011
We had similar issues with a different product. Eventually, we quit using it because of similar reasons and also because sometimes our boxes would ping, but would be froze up somehow and not respond to login attempts. Now have our NIM server SSH to every box every 15 minutes and run a "/usr/bin/ls" command and check that the return code was "0". One of our other boxes does an SSH to our NIM server to make sure it is running. We have to monitor the monitor.
9 More Discussions You Might Find Interesting
1. AIX
I'm trying to configure Etherchannel on AIX 5.3 and I'm having some problems. I am aggregating both of the onboard NIC's (ent0 and ent1) into a new adapter ent2 for failover reasons obviously. At first I was experiencing a problem where about 50% of all my packets would be dropped. Then after... (4 Replies)
Discussion started by: acascianelli
4 Replies
2. AIX
I have 1 AIX server, 4 dual ported fiber attached ethernet cards and 4 VLANS coming in. Is it possible to present those 8 ports as 1 IP address using etherchannel? Thanks. (5 Replies)
Discussion started by: jwholey
5 Replies
3. Solaris
Dear all,
I am a newbie in solaris and I need your advice.
I have a Solaris version 5.9 installed on Sunfire V240.
I am able to ssh the machine from putty remotely.
My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies
4. SCO
Hi all
I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface?
If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies
5. AIX
I have one p5 server, no lpar, 2 physical network adapter, bundle as one EtherChannel. The two 2 physical network adapter connect to 2 network switches.
How to make this as a redundancy config?
Current is if one physical network adapter down, the seond one will go through the network. but if... (2 Replies)
Discussion started by: rainbow_bean
2 Replies
6. AIX
Hi,
I have a AIX5.3 P6-520 with 8x1Gb Ethernet ports with possible connections to 2 CISCO 2960 switches.
I can create 8023ad Etherchannels which work correctly with the switches (I have set up for LACP passive and a valid channels)
But can create 2x 8023ad 4Gb Etherchannels with no backups.... (2 Replies)
Discussion started by: spitzie
2 Replies
7. IP Networking
Im configuring centos with load balance with ip route and ip rule
Eth0 192.168.1.5
Eth1 192.168.5.128
# ip route
192.168.5.0/24 dev eth1 scope link src 192.168.5.128
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.5
169.254.0.0/16 dev eth1 scope link
# ip route show... (2 Replies)
Discussion started by: hadinetcat
2 Replies
8. AIX
Hi Guys,
I am trying to test an etherchannel failover and switchback.
I did failover from primary to backup adapter, but now I am not able to switch it back to primary.
phcxxxxx:/ > entstat -d ent4 | grep Active
Active channel: backup adapter ... (1 Reply)
Discussion started by: snchaudhari2
1 Replies
9. AIX
Hello,
POWER7 machine.
4 x 1Gbit port ethernet adapter is dedicated to vios. 8023ad etherchannel is created using those 4 ports. Etherchannel adapter is shared to lpars using SEA.
If I test network performance directly from vios partition (using iperf) I'm geting nice 4Gbit throughput. But if... (3 Replies)
Discussion started by: vilius
3 Replies
LEARN ABOUT DEBIAN
pam_ssh
PAM_SSH(8) BSD System Manager's Manual PAM_SSH(8)
NAME
pam_ssh -- authentication and session management with SSH private keys
DESCRIPTION
The SSH authentication service module for PAM, pam_ssh provides functionality for two PAM categories: authentication and session management.
SSH Authentication Module
The SSH authentication component verifies the identity of a user by prompting the user for a passphrase and verifying that it can decrypt at
least one of the user's SSH login keys using that passphrase.
The following options may be passed to the authentication module:
debug syslog(3) debugging information at LOG_DEBUG level.
use_first_pass If the authentication module is not the first in the stack, and a previous module obtained the user's password, then
that password is used to decrypt the user's SSH login keys. If this fails, then the authentication module returns
failure without prompting the user for a passphrase.
try_first_pass Similar to the use_first_pass option, except that if the previously obtained password fails to decrypt any of the SSH
login keys, then the user is prompted for an SSH passphrase.
try_first_pass has no effect if pam_ssh is the first module on the stack, or if no previous modules obtained the
user's password.
allow_blank_passphrase Allow SSH keys with no passphrase.
If neither use_first_pass nor try_first_pass is specified, pam_ssh will unconditionally ask for an SSH passphrase.
In addition to the above authentication procedure, all standard SSH keys (identity, id_rsa, id_dsa) for which the obtained password matches
will be decrypted.
SSH Session Management Module
The SSH session management component initiates sessions by starting an SSH agent, passing it any SSH login keys it decrypted during the
authentication phase, and sets the environment variables accordingly.
The SSH session management component terminates the session by killing the previously started SSH agent by sending it a SIGTERM.
The following options may be passed to the session management module:
debug syslog(3) debugging information at LOG_DEBUG level.
INFORMATION LEAKS
Be careful with the using the try_first_pass option when pam_ssh is the first authentication module because it will then leak information
about existing users without login keys: such users will not be asked for a specific SSH passphrase, whereas non-existing users and existing
users with login keys will be asked for a passphrase.
FILES
$HOME/.ssh/identity
$HOME/.ssh/id_rsa
$HOME/.ssh/id_dsa OpenSSH DSA/RSA keys decrypted by pam_ssh.
$HOME/.ssh/login-keys.d/ Location of (possibly symbolic links to) OpenSSH DSA/RSA keys used for authentication and decrypted by pam_ssh.
/var/log/auth.log Usual log file for syslog(3)
SEE ALSO
ssh-agent(1), syslog(3), pam.conf(5), pam(8).
AUTHORS
Andrew J. Korty <ajk@iu.edu> wrote pam_ssh. Dag-Erling Smorgrav wrote the original OpenPAM support code. Mark R V Murray wrote the original
version of this manual page. Jens Peter Secher introduced the login-key concept.
BSD
November 26, 2001 BSD