unable to ping, ssh or telnet to my server

[David Willams]

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
#

[Patrick Wallek]

Any particular reason you opened a new thread?

For those not aware, this is a continuation of:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1368232

What about trying to talk to other servers FROM this one via the network? ping, telnet, ftp, ssh, something.

If you can't get out, then you have network issues with cabling, configuration, gateway, etc.

Output from commands that fail going OUT from this server would be helpful.

[James R. Ferguson]

Hi David:

There is no need to open a new thread. There has been considerable dialog regarding your problem in you previous thread:

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1368232

The lack of instant and/or continuous updates from the community does not mean that thought ian't being given as time permits.

Regards!

...JRF...

[David Willams]

does my rc.config.c/netconf look good

[Mel Burslan]

Since the thread referenced in the posts abe have been closed, I will answer your question here:

Your netconf file, especially the ROUTE section is a bit suspicious. You're telling the system that it has two default routes, which is not a good thing. It is allowed and let you create more than one default route but in general, network equipment does not like that.

Make your mind up and decide which one you are going to use as default route and use only that interface for it. If you need to route to a different network or host using that other interface, you put the destination host or network on the relevant ROUTE_DESTINATION line.

Then

(from the console)

/sbin/init.d/net stop
/sbin/init.d/net start

Tell us what happens after this.

[David Willams]

I have done that and booted the server.... but it is still the same....

[Steven E. Protter]

Shalom,

boot at console.

Do basic tests.

lanscan

lanadmin

Ping test on gateway.

Check NIC card.

dmesg for dead NIC cards.

Walk up to the box. check lights on the switch and NIC cards.

SEP

[Mel Burslan]

ping 135.11.25.1
ping 135.11.26.1

can you get response from either of them ?

if not,

1) ioscan -fnC lan
do you see both lan0 and lan1 CLAIMED

if yes

2) check if your Network cables are connected securely and the link light (usually the green one) is lit solid.

if yes

you should be able to ping these gateways, provided they do respond to ICMP packets.
At this point, talk to network people to see if they can see your server across the switch ports by their MAC addresses. You can get the MAC address of the interfaces from lanscan output.

lanscan | awk '{print $2}'

give them these addresses and see if your server is visible to network gear.

[David Willams]

I would like to change the ip from lan0 to lan1...

like lan0 should have IP adddress of lan1 & vice versa...

when I do this..

If you wish networking to operate correctly, you must assign the
system a unique Internet Protocol (IP) address. The IP address must:

* Contain 4 numeric components.

* Have a period (.) separating each numeric component.

* Contain numbers between 0 and 255.

For example: 134.32.3.10

Warning: Leading zeros within a component are not allowed!

Your current address is 135.11.34.101. To retain this address,
just press [Enter].
__________________________________________________________________
_____________

Enter your IP address, then press [Enter] or just press [Enter] to select
the current address (a.b.c.d): e.f.g.h

Address already in use by other interface
Press [Enter] to try again...

Now I try

Ifconfig lan0 unplumb and try this again.... but it is still the same';

[Patrick Wallek · Accepted solution]

The easiest way to do that would probably be to modify /etc/rc.config.d/netconf. Where it says lan1, make it lan0 and vice-versa.

You should probably reboot after that, although you could try

/sbin/init.d/net stop
/sbin/init.d/net start