config gelan card, cannot connect to the server?

[James Ellis_1]

I did this:
installed recommended patches
install gelan driver
installed NIC (A4926A)
connect fiber to card
ifconfig lan0 unplumb
ifconfig lan1 143.134.55.40 netmask 255.255.255.0
ifconfig lan1
testing by ping to broadcast address
edit /etc/rc.config.d/netconf
edit /rc.config.d/hpgelanconf
inetd -c
/sbin/init.d/net start

I am able tp ping to broadcast address, and even ping from another server. But I am unable to connect to the server outside of the web console. Any advice?

Thanks.

[Sridhar Bhaskarla]

Hi James,

Can you connect to the server from the server from which you can ping?.

I didn't understand exactly what you meant by "unable to connect to the server".

I feel this could be a default router issue. Can you ping to your default router from the system?.

-Sri

[James Ellis_1]

Yes, when I am in the web console I can ping to my default router. I got my default router from the netconf file and it is:

Route_Gateway=143.134.55.1

ping 143.134.55.1 was successful while I was in the web console.

Thanks...

[James Ellis_1]

Sridhar,

What I meant by "unable to connect to the server"

I am unable to connect to the server outside the web console. I usually connect to the server through an Xsession or Xterm. This does not work for me where it has usually worked for me.

Thanks for your help!

[James Ellis_1]

One thing:

I did not do a /sbin/init.d/net stop before following the unplumb above.

Also, we had problems with the system not detecting the card and had to reseat the card this evening. Then the system could see the card

lanscan -v
ioscan nkfC lan

What else am I doing wrong? I noticed that the /etc/rc.config.d/hpgelanconf file is set up with

HP_GELAN_INTERFACE_NAME=lan1 but the other parameters are not configured. Should I configure the other entries in hpgelanconf?

[James Ellis_1]

By the way, I am unable to ping to the server from the msdos command line. But I can pint to another identical server. What does this indicate?

[Sridhar Bhaskarla]

James,

If you could be able to ping your default gateway and the broadcast, then the network is fine. What does your

netstat -in say?

Did you do a traceroute to the server from the system that you are trying to connect using xterm?

-Sri

[James Ellis_1]

When I execute:

netstat -in

it shows:

lan1 1500 143.134.55.0 143.134.55.40 820 1719

lan0 4136 127.0.0.0 127.0.0.1 1605 1605

This is what puzzles me. I am able to ping to the router from the web console and from the msdos comand line. But I cannot ping to the IP address or the server name itself.

[James Ellis_1]

I thought about resetting the gelan card? Would this be necessary, but I doubt it.

Also, you should know that the drivers were installed before the lan card was properly set, but I think you normally install the drivers first and then the gelan card?

[James Ellis_1]

When I ping to my broadcast address, it seems to work. When I stop the ping, I get something strange.

5 packets transmitted, 45 packets received, -800% packet loss.

Does not seem you can receive 45 packets from transmitting 5 packets...and getting -800% loss?

[Sridhar Bhaskarla · Accepted solution]

James,

Your network seems to be ok. I believe the second line in your netstat -i is "lo0" instead of lan0.

It does not hurt you to run net stop and start. Do this -

#ifconfig lan1 unplumb
#ifconfig lan0 unplumb
#netstat -in

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

You do not need to worry about resetting etc., as your card is up and you are able to ping to the default router.

Do the above. Try pinging to different servers in the same subnet, default router and then see if it works.

-Sri

[James Ellis_1]

If I do this

ifconfig lan1 unplumb then that will mean I will lose my network connection because this is the default nic I want?

You know what I am talking about? Also unplumb lan0 will not matter because I am concerned about getting lan1 the default. Ok, I'll try and see what happens. But I would need to
ifconfig lan1 (IP) netmask (IP) Up again right?

[Sridhar Bhaskarla]

About the ping to broadcast, that's ok. Server sent only 5 broadcast packets, but 45 servers responded with return packets so the package gain/loss is calculated by the formula

(packets sent - packets received) * 100/
packagets sent

5-45/5 = -40/5 = -800%

Your network is looking perfect. I believe your default router is not setup. Try this.

#route add default 143.134.55.1 1

Then try.

-Sri

-Sri

[Sridhar Bhaskarla]

You have access to the server since you are on webconsole. So the next /sbin/init.d/net should add the default router too. Look at netstat -rn and see if the default router is listed in there.

-Sri
PS: I wish there is a chat session here. This is almost looking like chat.

[James Ellis_1]

I did what you asked, and was able to ping to a different server in the same subnet and was also able to ping to the default router. Do I need to run ipconfig again?

[Sridhar Bhaskarla]

No, YOu dont' need to run ifconfig.

Can you post your "netstat -rn" the routing table?

Looks like your default gateway is missing in the configuration.

-Sri

[James Ellis_1]

Yes, netstat -rn shows the default router. Let me see if I can ping now.

[James Ellis_1]

I am able to ping from a msdos command line, and I tried connecting to the server from my Xterm Window and it worked! I am not sure what your steps had to do or how it helped. I unplumbed both lan1 and lan0 and it is now working. What the hell, ha.

Did your steps cause me to reset the card or re-initialize the card?

Thanks and points will be awarded!

[Sridhar Bhaskarla]

OK.

Your configuration seems perfect if the default router is listed in your netstat -rn and if you are able to ping to other systems in the same subnet. Now, I would suggest the following.

Pick up an IP address (the IP of the server from where you are trying to connect) and do a traceroute from the server to this IP.

#traceroute

If it stops at the default router, then you will need to talk to your network group.

-Sri

[James Ellis_1]

Sridhar,

Yes, it would be nice if a chat session was part of this forum.

Anyway, its working now so I'll bring up the other services.

I appreciate your help, and I owe ya one!

Thanks!

[Sridhar Bhaskarla]

Hi James,

I am glad it worked.

I believe we just added the default router. Previously you were pinging to default router but was somehow got dropped out of the network configuration. With the next net start, it would have added.

-Sri

PS:

Now, please don't assign points to all the posts. Depending on your satisfaction, give points to only one post and the put "0"s for the rest of the posts.

[James Ellis_1]

I did the traceroute (IP) from another server to this server, and it went through ok. It did not stop at the router. I think its fixed because I am able to connect to the server from another server, and was not able to do this before.

By the way, the router works for all of the other servers, so I believe I did something wrong although my hpgelconf and netconf files seem configured right?

Thanks.

[James Ellis_1]

Well, I done assigned the points and cannot rectract. But I'll remember you and the next time you help me you will not get many points from me. But I felt you helped me in a crunch because this has to be up and running before the backups tonight and before everyone comes to work tomorrow. Being its late here, I was not sure if I could get this darn thing working.

It does appear that the default router was the culprit!
Thanks.

[Sridhar Bhaskarla]

Hi,

I am connected through dial-up. So it's slow. I posted my traceroute message before I saw your "working" message. Even my points message got posted after you assigned points.

Your netconf file is good as it worked with "net start" You don't need to bother about hpgelanconf. gelan gets configured fine even without any entries in hpgelanconf. Keep an eye on your next reboot though.

Enjoy hp-ux'ing.

-Sri

[rick jones]

One thing to consider - no idea if it was involved or not though.

When you moved the IP address from the old interface to the new one, you changed the IP address to MAC address mapping.

Some devices/systems may not update their IP address to MAC address mappings immediately - they may not "wiretap" the ARP messages your system was (likely) sending and so would not pick-up the new mapping until after a timeout of some sort.