Tru64UNIX V5.1A sp1
The good answer is to upgrade to V5.1B and set the inet parameter called
icmp_redirecttimeout. We're saving the 5.1B upgrade for future
application upgrade when it will be more know what version of the
database is used and on what Tru64UNIX version it is supported.
Problem: icmp routing redirects (natural to tcp) are essentially
becoming static routes as they don't time out or leave the table
(netstat -r | more). These resident and stay static redirects can
become black holes.
Options are:
1) upgrade to 5.1B
2) disable reacting to routing redirects:
#dbx -k /vmunix
dbx> assign|patch icmp_rejectcodemask=32
dbx> q
3) manually delete (route delete -host $hostname $gatewayname)
4) cron a shell script for #3 (netstat -r | grep UGHD, use AWK, run loop
w/ route delete)
5) reboot frequently
I'd like to try #4, say cron'ing every 10 minutes.
Any strong feelings about cron'ing a shell script #4, or to not reacting
to the redirect #2?
Has anybody tried #4, or anticipate any problems doing this?
Best Regards, Blake
Blake Brehl
Sys Admin/DBA
Anritsu Company United States
Morgan Hill, CA
This message is intended for the use of the individual/entity to whom it is addressed. This message may contain privileged information exempt from disclosure. If you are not the addressee, distribution or copying of this message, or dissemination of the information contained herein, is strictly prohibited. If you should receive this message in error, please destroy it, or return to sender. Thank You.
Received on Tue Feb 07 2006 - 00:14:59 NZDT