Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

bad route entry ??? 1

Status
Not open for further replies.

sbrews

Technical User
Jun 11, 2003
413
US
While looking at some routing table entries, I found this on one of the systems:

131.127.21.64/32 131.127.21.1 UG 0 0 en2 - - - =>

This entry doesnt look right to me - nor do I anything similar on any other system. I've tried deleting it via smitty route but have not been successful. Can this entry be removed? If so, what is the correct way to do it?



Add a little color to your PUTTY terminal: faq52-6627
 
It looks like a route to a device - 131.127.21.64 - via a gateway 131.127.21.1
what do you get with
Code:
route del -host 131.127.21.64
If that doesn't work try
Code:
route del -net 131.127.21.64
which would be bizaar but you never know.

Ceci n'est pas une signature
Columb Healy
 
I am hesitant to enter that...
Here is what I see when I look for everything on the .64 network:

# netstat -rn | grep 131.127.21.64
131.127.21.64 131.127.21.70 UHSb 0 0 en0 - - - =>
131.127.21.64/32 131.127.21.1 UG 0 0 en2 - - - =>
131.127.21.64/26 131.127.21.70 U 0 27 en0 - - - =>
131.127.21.64/26 131.127.21.1 U 0 6 en2 - - -


if I enter the "route -del.." command, I think it will take out the 131.127.32.64/26 entry too. That would be bad as the system is in production (and otherwise working - aside from the strange /32 entry).


Add a little color to your PUTTY terminal: faq52-6627
 
the 'H' in the 'UHSb' indicates that it's a host route. Seeing that the 131.127.21.64 is a subnet (/26) which appears to be available via either en0 or en2 (both which appear to be connected to the same LAN) there isn't much to worry about. There won't likely be any traffic from your system to the .64 as that can't be a host. Any traffic in that subnet won't be affected by the host route for .64.

I can't say that the fact the route is there is good, but it isn't something to worry about that would affect production services. In your next change window put it on the list of things to address. Start with the -host variant posted by columb.

peter
 
Do the following

lsattr -El inet0


if you see the route in the output then it's in ODM

to get rid

chdev -l inet0 -a delroute="the output from lsattr -El inet0"

or

odmdelete -q "name= inet0 and value="the output from lsattr -El inet0"

HTH



Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."
 
While I didnt find that funky route in the ODM, that is some good info for future reference.

Add a little color to your PUTTY terminal: faq52-6627
 
Looks like the system is otherwise ok - so... I will put that funky route on the list of things to look into at the next maintenance window.


Add a little color to your PUTTY terminal: faq52-6627
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top