- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: default route issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2011 01:48 AM
04-28-2011 01:48 AM
default route issue
HPUX server stopped serving other networks because of an issue in the default gateway
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.48 0.0.0.168 U 1 16384
10.10.51.1 0.0.0.5 U 4294967295 2130706432
0.0.0.199 * U 4 4294967295
0.0.0.5 * U 0 168440830
default * U 9925576 16
#
attached netconf file.
uname -a
HP-UX HNAME B.11.11 U 9000/800 4217070896 unlimited-user license
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2011 01:51 AM
04-28-2011 01:51 AM
Re: default route issue
you have 2 default routes in the netconf ...
ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="10.10.51.254"
ROUTE_COUNT[0]="1"
ROUTE_ARGS[0]=""
....
ROUTE_DESTINATION[1]=default
ROUTE_GATEWAY[1]=10.10.51.245
ROUTE_COUNT[1]=1
Delete the second one and run '/sbin/init.d/net start'
hth
Stephan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2011 02:03 AM
04-28-2011 02:03 AM
Re: default route issue
anyway, i have removed all the entries except for 10.10.51.254 and restarted the box " It is development".
it starts serving other networks for 5 minutes and STOP again.
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.48 0.0.0.118 U 1 à ºfwúà à º^t 16384
8.10.34.0 0.0.0.5 U 4294967295 2130706432
0.0.0.149 204.186.127.161 U 4 wúà à º^t 4294967295
default 204.186.94.116 U 9864560 à à à ºfXwúà à º^t 16
attached the new netconf after reboot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2011 09:13 AM
04-29-2011 09:13 AM
Re: default route issue
What do you mean by
"serving other networks"
Show/tell us something about what fails.
bv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2011 04:47 PM
04-29-2011 04:47 PM
Re: default route issue
Looks like you are getting bogus routes added after the server starts.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2011 09:53 PM
04-30-2011 09:53 PM
Re: default route issue
i haven't done any changes in the server, and also all these routs are junk we don't have such networks and we never add more routes in any other file.
serving other networks means, the server can serve only who ever in its subnet. 10.10.4.x only, but because the default gateway got corrupted, the server cannot connect to any other subnet.
i have a strong feeling that this might happen in case hardware failure.
please advice!
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2011 07:30 AM
05-01-2011 07:30 AM
Re: default route issue
The "U" entries are normally for direct local network/IPs
**Immediately** after a reboot,
please do
netstat -ivn
netstat -rvn
.
The -ivn will show IPs on all the LANs.
and then run the same commands after the 5 mins when crap starts showing up.
Maybe some rogue program is adding IPs to the LAN(s).
However, it does appear that perhaps memory is being clobbered.
Or at least the routing table is being clobbered.
Look at the HUGE ref counts !!!!
and the garbage chars.
Make sure that you do NOT have gated running.
(The netconf file shows that it should NOT start.
)
Is it possible that this server has been hacked??
Does
"www.thedoghaus.com."
mean anything to you :
## dig -x 204.186.94.116
;; ANSWER SECTION:
116.94.186.204.in-addr.arpa. 86400 IN PTR www.thedoghaus.com.
bv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-01-2011 10:09 PM
05-01-2011 10:09 PM
Re: default route issue
here is the netstat output after reboot.
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49 0.0.0.153 U 1 16384
10.10.51.2 0.0.0.5 U 4294967295 168440576
0.0.0.153 * U 3 4294967295
0.0.0.5 * U 4278190080 2130706433
default * U 1818324529 152
default * U 16 201326607
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49 0.0.0.182 U 1 @O`@B@Q٠@>x@Kh@Qp@;٠@X� 16
384
0.0.3.0 0.0.0.5 U 4294967295 @>x@Kh@Qp@;٠@X� 16844
0576
0.0.0.48 64.1.73.88 U 3 @;٠@X� 4294967295
default 64.1.81.240 U 4278190080 2130706433
64.1.73.88 64.1.81.112 U 1818324529 181
64.1.81.240 * U 16 201326607
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49 0.0.0.189 U 1 16384
0.0.51.0 0.0.0.5 U 4294967295 168440576
0.0.0.144 0.4.55.144 U 3 4294967295
default 0.4.55.144 U 4278190080 2130706433
0.4.49.144 0.4.55.144 U 1818324529 @ 188
0.0.16.16 0.4.55.144 U 16 201326607
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49 0.0.0.195 U 1 16384
10.10.51.2 0.0.0.5 U 4294967295 168440576
0.0.0.195 * U 3 4294967295
0.0.0.5 * U 4278190080 2130706433
default * U 1818324529 194
default * U 16 201326607
changing rapidly, so weird.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2011 12:21 AM
05-02-2011 12:21 AM
Re: default route issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2011 02:18 AM
05-02-2011 02:18 AM
Re: default route issue
i had once a system where hosts and netconf got replaced every time the system has been booted.
It was as well a test system and the solution after nearly a day of search was the hammer new install.
Did you check if in single user mode the routes get screwed up as well?
Did you check profiles, start scripts, cron, ... for something strange?
After that i would go for the hammer solution.
Best,
Stephan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2011 02:40 AM
05-02-2011 02:40 AM
Re: default route issue
they put access list on the VLAN. when they removed the list. it worked.
i put them as the last resort, and the problem usually comes from their sides.
thanks everybody
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2011 03:34 AM
05-02-2011 03:34 AM
Re: default route issue
I don't see how an ACL could cause bad entries to appear in the routing table.
These entries were not dynamic entries added because of ICMP redirects; they were trash.
Doesn't make sense to me.
bv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2011 04:00 AM
05-02-2011 04:00 AM
Re: default route issue
# netstat -rvn
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49/108.97.110.49 0.0.25.191 U 2 16384
10.10.51.1/0.0.0.0 0.0.0.5 U 4294967295 2130706432
0.0.25.222/0.0.0.0 * U 4 4294967295
0.0.0.5/0.0.0.0 * U 9864560 16
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2011 05:41 AM
05-02-2011 05:41 AM
Re: default route issue
I don't want to beat a dead horse, but I think the critter is still breathing, or maybe a zombie or something.
I don't understand why originally it worked for the 5 minutes.
Also, I still would like to see
netstat -ivn
and also both
netstat -ivn
netstat -rvn
IMMEDIATELY after a reboot.
bv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2011 09:21 PM
05-02-2011 09:21 PM
Re: default route issue
# netstat -inv
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan1 1500 10.10.51.0 10.10.51.1 16 0 3 0 0 2147483647 none 255.0.0.0 849 0 0 0 0
#
=============
# netstat -rvn
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 2130706433 lo0 4136
108.97.110.49/108.97.110.49 0.1.13.179 U 2 16384
0.0.0.1/0.0.0.1 0.0.0.5 U 4294967295 2130706432
default/0.0.9.64 * U 9864560 16
=========
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2011 05:28 AM
05-03-2011 05:28 AM
Re: default route issue
That output is totally trash.
Your output should be like the attached file.
I've never seen anything like this, except when something is stomping around on memory, but that usually portends more serious problems, like crashes.
OTOH, the default route seems to be working, so maybe it's just an output problem.
I would look for the latest patches
and also call HP.
bv