+----- On Tue, 09 Nov 1999 16:39:52 PST, "Bruce Sterling Woodcock" writes: | > On Tue, 9 Nov 1999, Eyal Traitel wrote: | > | > > I had something a little similar I suspect... | > > Try toggling your RIP by "routed off|on". | > > You should also check that your /etc/rc contains something like: | > > | > > route add default 223.21.95.254 1 | > | > route add net default 223.21.95.254 1 | > | > to be exact. Otherwise you're putting in a host route. | | Your default route SHOULD be a host route. To the IP address of the | router.
No, it is exactly the opposite. A host route implies a netmask of all 1's i.e. 255.255.255.255 but the default route has a netmask of all 0's i.e. 0.0.0.0 as it has to match all addresses.
/Michael
The results of our morning network downtime are in and the problem was not with the NetApp. Thank you for all of the suggestions. Since I didn't have any replies from someone saying, "Yeah we had that exact problem and we did this to fix it," I had confidence that the problem was with our Cisco configuration and it was. Actually there was one person that had a similar result when their default route was entered incorrectly, but that was not the case for us.
We are using a bridge-group on our Cisco router to forward broadcasts and allow Sun Autoclients to boot across the router. There was an access list to limit these forwarded broadcasts to packets with the Sun manufacturer ID in the hardware address. This access list was also preventing the NetApp from reaching the router on its own subnet which was also part of the bridge-group, probably because the router was dumping its broadcasts since they didn't have a Sun manufacturer ID. The fix was simple, we added the NetApp and other manufacturer IDs to the access list.
Now go back to your partying at LISA...
-- Mike
-
Michael Salmon -
Mike Mueller