HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SSH problem
Operating System - HP-UX
1830899
Members
2910
Online
110017
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2005 09:30 AM
10-26-2005 09:30 AM
Users started to report they could no longer login to the server.
myhost:/:>ssh -v HostA
OpenSSH_3.9, OpenSSL 0.9.7d 17 Mar 2004
HP-UX Secure Shell-A.03.91.002, HP-UX Secure Shell version
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug1: Connecting to HostA [142.101.x.y] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/3
debug1: identity file /.ssh/id_rsa type 1
debug1: identity file /.ssh/id_dsa type -1
debug1: ssh_exchange_identification:
debug1: ssh_exchange_identification: Destination server does not have Ssh activated.
debug1: ssh_exchange_identification: Contact Cisco Systems, Inc to purchase a
debug1: ssh_exchange_identification: license key to activate Ssh.
ssh_exchange_identification: Connection closed by remote host
ANy ideas? checked google, nothing relevant.
myhost:/:>ssh -v HostA
OpenSSH_3.9, OpenSSL 0.9.7d 17 Mar 2004
HP-UX Secure Shell-A.03.91.002, HP-UX Secure Shell version
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug1: Connecting to HostA [142.101.x.y] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/3
debug1: identity file /.ssh/id_rsa type 1
debug1: identity file /.ssh/id_dsa type -1
debug1: ssh_exchange_identification:
debug1: ssh_exchange_identification: Destination server does not have Ssh activated.
debug1: ssh_exchange_identification: Contact Cisco Systems, Inc to purchase a
debug1: ssh_exchange_identification: license key to activate Ssh.
ssh_exchange_identification: Connection closed by remote host
ANy ideas? checked google, nothing relevant.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2005 09:38 AM
10-26-2005 09:38 AM
Re: SSH problem
I am not familiar with this problem but it seems like your ssh connection gets hijacked by a cisco device and not allowed to proceed.
Check if you have an IP address conflict between this server and a cisco device interface IP. Best bet is to take the message to the network admins and by their help sniff the traffic to figure out which device is stronarming you to buy a cisco ssh license key, looking at the mac addresses.
Check if you have an IP address conflict between this server and a cisco device interface IP. Best bet is to take the message to the network admins and by their help sniff the traffic to figure out which device is stronarming you to buy a cisco ssh license key, looking at the mac addresses.
________________________________
UNIX because I majored in cryptology...
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2005 12:51 PM
10-26-2005 12:51 PM
Re: SSH problem
Richard,
You need to talk to your network folks and have the ssh port opened up from the firewall.
DP
You need to talk to your network folks and have the ssh port opened up from the firewall.
DP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2005 09:58 PM
10-26-2005 09:58 PM
Solution
I guess the error messages is clear:
ssh access is not working anymore on the cisco device because the license key is missing.
If the user used to reach a server under that address this might reveal a networking/routing problem. Maybe it's a kind of NAT or policy routing activated and configured the wrong way.
Maybe just the IP address changed?
May 2 cents,
Armin
BTW: Please assign points!
ssh access is not working anymore on the cisco device because the license key is missing.
If the user used to reach a server under that address this might reveal a networking/routing problem. Maybe it's a kind of NAT or policy routing activated and configured the wrong way.
Maybe just the IP address changed?
May 2 cents,
Armin
BTW: Please assign points!
And now for something completely different...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP