AIX

I forgot to mentionned that we have over 50 AIX servers and almost all of them are showing this behavior...

I didn't use it to set the gateway, just to check what it was set to.

You are saying that the NIM server set those gateways on the remote system ? Effectively all our servers were build via a NIM server but we rarely use the NIM server for other operation on the clients. And as I already said, the 2nd default gateway come back when we reboot the server.

Some of our machines do have etherchannel but its not use on the main IP address (primary default).

Thanks all for your inputs

It's important that you do not use smitty mktcpip on the second adapter. Instead, use

Code:

smitty chinet

. This will set the IP on that adapter without adding an additional default gateway.

I've had this problem in the past, and I've always cleared it using

Code:

smitty rmroute

Can you post your routing table with the extra route listed?

We have that kind of phenomenom sometimes too - and as zxmaus says we also think it might be something from our NIM server after an installation of an LPAR.
Though we always had entries in the ODM like shockneck noted.

If you are absolutely sure that there is no entry of that wrong additional default gateway in the ODM, you can try to write a new boot image with

Code:

bosboot -ad /dev/ipldevice
# or
savebase

and check if it is still there after a reboot.

If so, you also might want to check if there is a line in any of your scripts in /etc like rc.tcpip or rc.net that have a line for adding that default GW, just to make sure there isn't:

Code:

find /etc -type f -exec grep -lE "route add|chdev|mktcpip" {} \;

It might list some relevant looking files which might be worth to check.

Like zxmaus, we had this issue too. Cat your /etc/niminfo file and look at the last line that starts with "export ROUTES=". It probably looks something like this:

[CODE]export ROUTES=" default:0:192.168.1.1 ..."[CODE]

Rename the /etc/niminfo file to /etc/niminfo.old and run "smitty nim" on your client machines and go through the setup steps again. Then look at the /etc/niminfo file and see if it looks correct after that.