HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Logical IP not reachable
Operating System - HP-UX
1833290
Members
2869
Online
110051
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
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
07-26-2009 09:08 PM
07-26-2009 09:08 PM
Logical IP not reachable
Hello,
I am facing a strange problem.
We have a physical ip configured on lan0 (172.16.5.74). This IP is rechable remotely from our Desktops through ssh .
Now we have a package IP (172.16.5.99) configured on the same subnet and it gets mapped on lan0 when the package is started. But the problem is that we are not able to login to this IP using ssh . There is no login prompt.
We are confused that how this is possible when the network policies are open to this subnet as confirmed by network team.
IS there any other change we need to make from System side?
Here is network setting
lan0:1 1500 172.16.5.64 172.16.5.99 53 0 38 0 0
lan0 1500 172.16.5.64 172.16.5.74 1221297 0 4130881 0 0
I am facing a strange problem.
We have a physical ip configured on lan0 (172.16.5.74). This IP is rechable remotely from our Desktops through ssh .
Now we have a package IP (172.16.5.99) configured on the same subnet and it gets mapped on lan0 when the package is started. But the problem is that we are not able to login to this IP using ssh . There is no login prompt.
We are confused that how this is possible when the network policies are open to this subnet as confirmed by network team.
IS there any other change we need to make from System side?
Here is network setting
lan0:1 1500 172.16.5.64 172.16.5.99 53 0 38 0 0
lan0 1500 172.16.5.64 172.16.5.74 1221297 0 4130881 0 0
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2009 10:27 PM
07-26-2009 10:27 PM
Re: Logical IP not reachable
sshd never produces an actual login prompt: the username is supposed to be reported by the client within the ssh protocol initialization packets.
Some SSH clients (like PuTTY) will locally produce something that looks like a login prompt if the username has not been specified in the configuration. If PuTTY cannot get that far, that indicates PuTTY could not establish a network connection to the target address. Other SSH clients may work differently.
Please show us the full output of "ifconfig lan0", "ifconfig lan0:1" and "netstat -rnv".
If you run "telnet 172.16.5.99 22" (=telling telnet to connect to the SSH port) from your desktop, what happens?
What does happen if you run the same command on the HP-UX server? Is the error the same as with the desktop?
If the telnet command says "Connection established", then the network side is definitely OK and the problem is somehow with the ssh client or the sshd process.
Try stopping and restarting sshd, and then test again with telnet. Did it change anything?
MK
Some SSH clients (like PuTTY) will locally produce something that looks like a login prompt if the username has not been specified in the configuration. If PuTTY cannot get that far, that indicates PuTTY could not establish a network connection to the target address. Other SSH clients may work differently.
Please show us the full output of "ifconfig lan0", "ifconfig lan0:1" and "netstat -rnv".
If you run "telnet 172.16.5.99 22" (=telling telnet to connect to the SSH port) from your desktop, what happens?
What does happen if you run the same command on the HP-UX server? Is the error the same as with the desktop?
If the telnet command says "Connection established", then the network side is definitely OK and the problem is somehow with the ssh client or the sshd process.
Try stopping and restarting sshd, and then test again with telnet. Did it change anything?
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2009 01:04 AM
07-27-2009 01:04 AM
Re: Logical IP not reachable
Hi ,
Please share the outputs of
#netstat -nvr
#netstat -in
and
#cmviewcl
#cmviewcl -v
Please share the outputs of
#netstat -nvr
#netstat -in
and
#cmviewcl
#cmviewcl -v
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