Unable to apply route info at boot

[Doug Short]

I've just built a D380 with 11i, and Dec. 2004 Q-pack. When ever I reboot the box I get an error in /etc/rc.log about not being able to apply route information due to the adapter not being initialized. At first, network was plugged into a J3516 card, and my presumption was that I did not have the correct drivers. However I've since moved the network drop to the built in LAN and rebooted with the same results. Any thoughts?

[Mel Burslan]

I am assuming you can initialize the same routes with a route add... command after the server completes the reboot. Right ?

Well, I am not sure if this is a fluke or not, but I was on the same boat. And magically after I added the words "host" and "net" preceeding the ROUTE_DESTINATION ip addresses, it started to work. I had to specify 24 static routes and no default route for a server of mine.

my static routes are looking like this right now:

for the host routes:

ROUTE_DESTINATION[1]="host 14.67.82.221"
ROUTE_MASK[1]=""
ROUTE_GATEWAY[1]="10.44.5.254"
ROUTE_COUNT[1]="1"
ROUTE_ARGS[1]=""


and for the net routes

ROUTE_DESTINATION[22]="net 10.40.12.0"
ROUTE_MASK[22]="255.255.255.0"
ROUTE_GATEWAY[22]="10.44.12.254"
ROUTE_COUNT[22]="1"
ROUTE_ARGS[22]=""


Also, I specified my host routes prior to net routes in the file. I found the process as a crap shoot. This config worked and others I tried failed with many errors.

HTH

[john kingsley]

Is there more than one adapter? Make sure the network information is set for the correct network interface.

Check the ouput to:
ioscan -funC lan
ifconfig lan# ; # corresponds to the instance for your network adapter from ioscan.
netstat -rn

Check /etc/rc.config.d/netconf and make sure the correct lan# is assigned to your network config.

[baiju_3]

Attach a console and do ioscan -fnC lan and see the driver state .

You may configure the on board lan first for that the drivers would be there in installed kernel .


thx,
bl.

[Doug Short]

All of my ioscans come back as being ok, in other words I don't have any unclaimed HW. I have verified that the network drop that I'm trying to use is good by plugging it into my laptop, where I can get out to the network, but then plugging back into any of the adapters yields the same results. The netconf has been compared to several other 11i boxes and is identical to those currently working.

The part that really bugs me is that I cannot manually do a route add command to get my route in, says that the network is unreachable, but shouldn't be since that router is on the same network. I don't believe this to be a driver problem based on the fact that the built in lan is giving the same results and using a completely different driver.
Any other thoughts come to mind? Any help is greatly appreciated, thanks.

[Mel Burslan]

are you adding the "1" hop count at the end of your route add command ? It is the most common pitfall I fall into still today, by a quick hit of the enter key. i.e., is your command looking like this :

(This is for a host route)
route add x.y.w.z A.B.C.D 1

where x.y.w.z is teh destination host
A.B.C.D is the gateway
1 is the indicator that this destination is not directly connected to yuor host.

HTH

[Doug Short]

Yes I was. This is the snippet from /etc/rc.config.d/netconf for the route portion:

ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="172.18.4.1"
ROUTE_COUNT[0]="0"
ROUTE_ARGS[0]=""

It is the same as every other 11i box I've touched here in house, with the exception of course that the gateway might be a little different depending on the vlan. Mel, given your hint on adding host or net, do you know the syntax for adding just one default route?

[Mel Burslan · Accepted solution]

default does not require a host or net keyword as it does not discriminate between the two.

the startling thing in your config is

ROUTE_COUNT="0"

line. Usually, this is set to 1 for the purpose I explained in my previous post. 0 here means that, the interface on this very same server is the router itself, which is a very poor way of configuring a default route, equivalent to throwing out the packet and hoping that some actual cisco/extreme/foundry/etc. router is going to pick it up and forward it. Instead, you should be putting the actual router's IP address and set the ROUTE_COUNT to 1.

if you have the luxury of rebooting this server one more time, try this approach.

[Doug Short]

Thanks so much Mel. I set the ROUTE_COUNT to 1 and rebooted and all appears to be fine. I appreciate all of your input and help in resolving this. Thanks again.

[Doug Short]

the startling thing in your config is

ROUTE_COUNT="0"

line. Usually, this is set to 1 for the purpose I explained in my previous post. 0 here means that, the interface on this very same server is the router itself, which is a very poor way of configuring a default route, equivalent to throwing out the packet and hoping that some actual cisco/extreme/foundry/etc. router is going to pick it up and forward it. Instead, you should be putting the actual router's IP address and set the ROUTE_COUNT to 1.