topic Re: ftp, ssh in Operating System - HP-UX

ftp, ssh

David Willams — Tue, 01 Sep 2009 17:16:24 GMT

I cannnot access my server remotely...

I can't ping the server remotely... but I can login from MP...

how to go about it

Re: ftp, ssh

Tingli — Tue, 01 Sep 2009 17:24:20 GMT

Able to login from MP doesn't mean you have a network connection to the system. When you try to ping the system, what does there response it says?

Three possible causes. There is no connection to the remote site. Or the gateway setting is wrong from either your one server or the remote server. And last but not the least, you can not get a correct IP address of the remote site.

Re: ftp, ssh

Steven Schweda — Tue, 01 Sep 2009 17:28:36 GMT

> I cannnot access my server remotely...
>
> I can't ping the server remotely...

Is it running? Is it connected to the
network? Are you sure that you're using the
right IP address?

> but I can login from MP...

Does that mean that you can log into the MP,
or that you can log into HP-UX on the system?
Serial port on the MP, or Telnet, or what?

As usual, showing actual commands with their
actual output might be more helpful than
vague descriptions and interpretations.

> how to go about it

Start with a better description of the
situation. Then check the obvious things.

Some description of "my server" might also be
of some value to those of us who can't see
it.

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 17:38:10 GMT

well I have rx7640

I can login remotely to MP and from there I login to the console..

Pinging 147.22.41.125 with 32 bytes of data:
Request timed out.

I have the IP address set up in /etc/hosts & rc.config.d/netconf

what else should I look for to login remotely.

Re: ftp, ssh

Patrick Wallek — Tue, 01 Sep 2009 17:52:04 GMT

Once logged into the system via the console can you: ping your default gateway? ping other system? telnet/ssh to other systems?

Have you verified that networking is set up correctly on the server?

Re: ftp, ssh

Steven Schweda — Tue, 01 Sep 2009 18:07:45 GMT

> As usual, showing actual commands with their
> actual output might be more helpful than
> vague descriptions and interpretations.

I'm wasting my e-breath, I can tell.

> [...] from there I login to the console..

What, exactly, does this mean? Are you
logging into HP-UX, or talking to the system
console, or what? From your description, I
don't even know if the system has been
powered on yet.

> Pinging 147.22.41.125 with 32 bytes of data:
> Request timed out.

And you did this where? And who is
147.22.41.125?

> I have the IP address set up in /etc/hosts
> & rc.config.d/netconf

I should trust your opinion?

> what else should I look for to login
> remotely.

What _else_ other than what? What have you
checked up to now? Is the network cable
plugged in?

Provide some basic info, or else you might do
better if you called a psychic hot-line.

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 18:08:17 GMT

I guess networking is not set up correctly on the server ... as I cannot ping to other server/telnet to ther servers

# ping 127.0.0.1
PING 127.0.0.1: 64 byte packets
64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms
64 bytes from 127.0.0.1: icmp_seq=1. time=0. ms
64 bytes from 127.0.0.1: icmp_seq=2. time=0. ms
64 bytes from 127.0.0.1: icmp_seq=3. time=0. ms

----127.0.0.1 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss

Re: ftp, ssh

Patrick Wallek — Tue, 01 Sep 2009 18:14:06 GMT

>>I guess networking is not set up correctly
>>on the server ... as I cannot ping to other
>>server/telnet to ther servers

That would do it.

>># ping 127.0.0.1
>>PING 127.0.0.1: 64 byte packets
>.64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms
>>64 bytes from 127.0.0.1: icmp_seq=1. time=0. ms
>>64 bytes from 127.0.0.1: icmp_seq=2. time=0. ms
>>64 bytes from 127.0.0.1: icmp_seq=3. time=0. ms

I'm not sure what you are trying to show with this. All this proves is that you can ping to loopback address. This shows that the IP stack is working, but nothing else.

If you want additional help, things like:

output of 'netstat -in'
output of 'netstat -rn'
output when you try to log into or ping some other host

will be extremely helpful.

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 18:15:24 GMT

steven,

system is powered on

147.22.41.125 is the IP address of the server of which i am talking on

>>What, exactly, does this mean?

means like log on to Mp to access the OS

147.22.41.125 hp01.hp.com
127.0.0.1 localhost loopback

Cables are all connected properly... Networking has not been done from the OS side

Re: ftp, ssh

Patrick Wallek — Tue, 01 Sep 2009 18:35:57 GMT

>>Networking has not been done from the OS side

What exactly do you mean by this?

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 18:43:47 GMT

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan0 1500 147.22.41.0 147.22.41.125 8 0 8 0 0
lo0 32808 127.0.0.0 127.0.0.1 55549 0 55549 0 0
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 32808
147.22.41.125 147.22.41.125 UH 0 lan0 32808
147.22.41.0 147.22.41.125 U 2 lan0 1500
default 147.22.41.1 UG 0 lan0 1500

# telnet 147.22.41.124
Trying...
telnet: Unable to connect to remote host: Network is unreachable

Re: ftp, ssh

Patrick Wallek — Tue, 01 Sep 2009 18:52:20 GMT

OK. That's a start. Now for some additional information:

output from 'ifconfig lan0'
output from 'ping 147.22.41.1'

The error you give seems to indicate that there is no route available to the 147.22.41 network, even though the host you are trying to access APPEARS to be on the same subnet, assuming a 255.255.255.0 subnet mask.

Are you ABSOLUTELY POSITIVE that you have connected the cable to the LAN0 network port?

NOTE: The LAN0 network port is DIFFERENT from the MP network port. If you only have 1 cable plugged into the back of the server, and you are accessing the MP from the network, then that is your problem.

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 19:00:59 GMT

#ifconfig lan0
lan0: flags=1843
inet 147.22.41.124 netmask ffffff00 broadcast 147.22.41.255

Re: ftp, ssh

Steven Schweda — Tue, 01 Sep 2009 19:15:34 GMT

> # netstat -in
> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
> lan0 1500 147.22.41.0 147.22.41.125 8 0 8 0 0
> [...]

> #ifconfig lan0
> lan0: flags=1843
> inet 147.22.41.124 netmask ffffff00 broadcast 147.22.41.255

So, as I see it, "netstat -in" says that lan0
is 147.22.41.125, while "ifconfig" says that
lan0 is 147.22.41.124.

Someone's confused. (I certainly am.)

> > I have the IP address set up in /etc/hosts
> > & rc.config.d/netconf
>
> I should trust your opinion?

Are you willing to show the evidence?

Do these commands do anything different
after a re-boot?

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 19:35:53 GMT

I have rebooted and it is still the same

Re: ftp, ssh

Tingli — Tue, 01 Sep 2009 19:42:52 GMT

Get your target system gateway address, then try to ping it from your system.

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 19:59:21 GMT

I have the same issue on my other server B..

On this from thee outside world I can ping my gateway..

I have two lan's configured here..

lan0 & lan1

I can ping the gateway for lan1 but lan 0 I cannot...

Re: ftp, ssh

Tingli — Tue, 01 Sep 2009 20:13:36 GMT

Then try to telnet to your lan1.

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 20:35:51 GMT

I can't telnet and I can't ping it

rc.config.c/netconf

INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=135.11.26.125
SUBNET_MASK[0]=255.255.255.0
BROADCAST_ADDRESS[0]=""
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
INTERFACE_MODULES[0]=""

DEFAULT_INTERFACE_MODULES=""
INTERFACE_NAME[1]=lan1
IP_ADDRESS[1]=134.11.25.125
DHCP_ENABLE[1]=0
SUBNET_MASK[1]=255.255.255.0
ROUTE_MASK[0]=255.255.255.0
ROUTE_GATEWAY[0]=135.11.26.1
ROUTE_COUNT[0]=1
ROUTE_DESTINATION[0]=default
ROUTE_MASK[1]=255.255.255.0
ROUTE_GATEWAY[1]=135.11.25.1
BROADCAST_ADDRESS[1]=""
ROUTE_COUNT[1]=1
ROUTE_DESTINATION[1]=default

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
1/0/1/1/0/6/0 0x00110A426CC0 0 UP lan0 snap0 1 ETHER Yes 119
1/0/1/1/0/6/1 0x00110A426CC1 1 UP lan1 snap1 2 ETHER Yes 119
1/0/6/1/0/6/0 0x00163573A23C 2 UP lan2 snap2 3 ETHER Yes 119
1/0/6/1/0/6/1 0x00163573A23D 3 UP lan3 snap3 4 ETHER Yes 119
1/0/14/1/0/6/0 0x00163573E20C 5 UP lan5 snap5 5 ETHER Yes 119
1/0/14/1/0/6/1 0x00163573E20D 6 UP lan6 snap6 6 ETHER Yes 119
LinkAgg0 0x000000000000 900 DOWN lan900 snap900 8 ETHER Yes 119
LinkAgg1 0x000000000000 901 DOWN lan901 snap901 9 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 10 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 11 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 12 ETHER Yes 119
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 32808
134.11.25.125 134.11.25.125 UH 0 lan1 32808
135.11.26.125 135.11.26.125 UH 0 lan0 32808
134.11.26.0 135.11.26.125 U 2 lan0 1500
134.11.25.0 134.11.25.125 U 2 lan1 1500
127.0.0.0 127.0.0.1 U 0 lo0 32808
default 135.11.25.1 UG 0 lan1 1500
default 135.11.26.1 UG 0 lan0 1500
# ifconfig lan0
lan0: flags=1843
inet 135.11.26.125 netmask ffffff00 broadcast 135.11.31.255
# ifconfig lan1
lan1: flags=1843
inet 134.11.25.125 netmask ffffff00 broadcast 135.11.34.255
# cat /etc/hosts
# @(#)B.11.31_LRhosts $Revision: 1.9.214.1 $ $Date: 96/10/08 13:20:01 $
#
# The form for each entry is:
#
#
# For example:
# 192.1.2.34 hpfcrm loghost
#
# See the hosts(4) manual page for more information.
# Note: The entries cannot be preceded by a space.
# The format described in this file is the correct format.
# The original Berkeley manual page contains an error in
# the format description.
#

135.11.26.125 hpvm.us1.hp.com hpvm
127.0.0.1 localhost loopback
# hostname
hpvm
#

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan1 1500 134.11.25.0 134.11.25.125 1 0 1 0 0
lan0 1500 134.11.26.0 135.11.26.125 2425 0 2425 0 0
lo0 32808 127.0.0.0 127.0.0.1 1297 0 1297 0 0
#

Re: ftp, ssh

David Willams — Tue, 01 Sep 2009 21:51:08 GMT

i will open a new threadd for this