Originally posted by: GarlandJoseph
Several things to try:
as you know routes impacts getting outside of subnet, what do the current routing tables look like, netstat -rn), do this on the problem host and a good one in the same subnet
also do lsattr -Elinet0
on the node in the same subnet that you pinged, check the entry in it's arp cache, on that node do... arp -an | and look for mac address of this node that has the problem, look for the mac address of the default router on both the good node and problem node and compare them
can you ping the default router
what mac address appears in the arp cache for the default router from this machine, do an arp -an to see, if you can't ping the router, delete it's arp entry with the arp -d command and try again to ping the router
Things to try (at your own risk): reconfigure this problem host from beginning, run /etc/tcp.clean, down the interface, rmdev it, then try cfgmgr to rediscover, note that permanent routes reside in the odm, so you have to change the attributes of inet0 to make routes permanent, routes can be added temporarily, then try initial configuration of interface on machine,
your errpt shows rebooting around 03/28/2013, show does alog -t boot -o show about the interface when you rebooted, what does alog -t cfg -o show about this interface