Thanks to the following people for their input. Everyone gave
valuable hints and directions to search in and discuss. The first 3 guys hit the
problem on the head.
Sergey Bobrovnikov
Robert McMillin
Jeff Stelzner
Bruce Platt
Anil Khullar
Arnaud Valeix
SPlusNet Inc.
The solution was actually simpler than I suspected:
I was running the routed daemon - all I did was unconfigured the
routed daemon and only had a default static router setup in
/etc/routes like this:
default xxx.xxx.xxx.xxx
We then disable RIP between the router/gateway and the 8200 and
enabled OSPF.
However an ip address conflict could also cause a similar problem but
that was not our case.
This solved this problem. The 8200 was then a dumb host on the network
that only spoke when it got spoken to and had no real intelligence in
which to make routing decisions. This worked fine for us.
Thanks to all. This list is an important part of my Support probably
better than the Support we get from DEC *chuckle*
Regards
Paulo
Description of problem:
I have a customer running 3.2D-1 on a 8200. They are experiencing
intermittent problems across their network (WAN). They have afew hundred users
on their network spread geographically across the country.
I have a configured a default route in /etc/routes to point to their main
cisco router/gateway where all the Clients across the country come into.
This default router is running RIP between the 8200 and the router
and it is running OSPF between all the routers(CISCO) across the country.
The problem: Every now and again no one can login and the 8200
looses its' default route. It is not possible to "ping" remote hosts
- however from other hosts on the same network segment as the 8200, they can
see these remote hosts!?
When I do a "netstat -r" the default route has disappeared. I either
have to reboot or do a #rcinet restart to resolve this problem. Lately I have solved this
problem by adding a route online by using the
"route add -host hostname gateway" or "route add -net network
gateway". However /etc/routes with the default router should do the
trick, shouldn't it?
This customer is busy setting up a Windowns NT DNS server and firewall.
Would it be better to configure the 8200 as a DNS client? Possibly it
wouldn't rely so heavily on routes. The 8200 /etc/hosts file is
updated with all the relevant hosts and routers. Could an ip
conflict be causing these problems?
Please guys - any suggestions or ideas would be welcome.
Thanks
Paulo
Received on Fri Feb 28 1997 - 17:21:20 NZDT