default route missing...

[MikeL_4]

After a reboot of a server we were missing our default route as defined in netconf file:
ROUTE_DESTINATION[3]=default
ROUTE_MASK[3]=""
ROUTE_GATEWAY[3]=155.90.120.130
ROUTE_COUNT[3]=""
ROUTE_ARGS[3]=""

I added the route and all was fine, but it was mentioned to me that in the netconf file the ROUTE_COUNT had to be set to 1.

Was wondering if this is true and if so why ??

[Pete Randall]

Mike,

Take a look at the comments in the netconf file:

"ROUTE_COUNT: An integer that indicates whether the gateway is a remote interface (one) or the local interface (zero) or loopback interface (e.g., 127.*)."


Pete

[Fred Ruffet]

ROUTE_COUNT must be set to 1. O is for destination accessed directly from a local NIC. As you set a gateway, it must be set to 1.

Regards,

Fred

[Sridhar Bhaskarla]

Hi,

ROUTE_COUNT defines how many 'hops' your system needs to make to reach the ROUTE_GATEWAY. If the interface is on the system itself, then it would be 0. If it in the same subnet, then the COUNT would be 1 as it has to hop once before reaching it.

Almost all the times you will find the default gateways on the same subnet. So, the count would be 1.

-Sri

[MikeL_4]

So on all the static routes that have been added to netconf I should change them to 1, as right now they are all set to "".

[Sridhar Bhaskarla · Accepted solution]

Hi,

I have observed one more issue with your netconf. The index for your 'default' route is 3. It is a good practice to maintain the indexes properly. I assume you have three more static routes before the 'default' entry with the indexes 0,1 and 2. Generally default route starts first with the index of 0.

Regarding your last question, the answer is it depends on where the interface is. If it is on the local system (use netstat -in to determine), then it will be 0. If it is not but on the same subnet, then it would be 1.

-Sri

[MikeL_4]

thanks