- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- routing default gateway
Operating System - HP-UX
1753510
Members
5683
Online
108795
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО11-19-2010 01:35 AM
тАО11-19-2010 01:35 AM
routing default gateway
Hello:
I have two rp3440 RP-A and RP-B,interconnected with router ,and geographically at different sites.
RP-A (10.0.198.242)...Router-A(10.0.198.241)...WAN...Router-B(10.9.3.193)...RP-B(10.9.3.194)
We are testing fail recovery "SW" between machines. One is active and the other standby.
We will focus on RP-A network configuration.
RP-A (lan0 = 10.0.198.242) is on subnet 10.0.198.242/255.255.255.240
RP-A (lan1 = 10.0.198.226) is on subnet 10.0.198.224/255.255.255.240
RP-A> route to access RP-B (10.9.3.194) is:
10.9.3.192/255.255.255.240 10.0.198.241 UG 0 lan0 0
Beside this, and based in customer requirements ,we have a default gateway on lan1 to access services.
RP-A> Default gateway is lan1 (10.0.198.226) :
default/0.0.0.0 10.0.198.225 UG 0 lan1 0
Now, the problem:
I launch a ping from RPA (10.0.198.242) to RP-B (10.9.3.194) ,ICMP packet are sent using lan0 (Router-A).OK
I do a cable unplug, and I "wireshark" that ICMP packets are redirected to lan1, because it is the default gateway & lan0 is KO.
I assume that this is the correct behaviour.
After 10 mn , I recover the situation on lan0, plug the cable back.lanadmin status for lan0 is OK.
But,the amazing point , is that pings still going using default router in lan1......
traceroute confirms this point:
RP-A,sys,root # traceroute RP-B (go to lan1)
traceroute to RP-B (10.9.3.194), 30 hops max, 40 byte packets
1 10.0.198.225 (10.0.198.225) 0.487 ms 0.310 ms 0.263 ms
2 10.0.198.225 (10.0.198.225) 0.359 ms !H * 0.389 ms !H
The situation is recovered if I reboot the machine....
I have two rp3440 RP-A and RP-B,interconnected with router ,and geographically at different sites.
RP-A (10.0.198.242)...Router-A(10.0.198.241)...WAN...Router-B(10.9.3.193)...RP-B(10.9.3.194)
We are testing fail recovery "SW" between machines. One is active and the other standby.
We will focus on RP-A network configuration.
RP-A (lan0 = 10.0.198.242) is on subnet 10.0.198.242/255.255.255.240
RP-A (lan1 = 10.0.198.226) is on subnet 10.0.198.224/255.255.255.240
RP-A> route to access RP-B (10.9.3.194) is:
10.9.3.192/255.255.255.240 10.0.198.241 UG 0 lan0 0
Beside this, and based in customer requirements ,we have a default gateway on lan1 to access services.
RP-A> Default gateway is lan1 (10.0.198.226) :
default/0.0.0.0 10.0.198.225 UG 0 lan1 0
Now, the problem:
I launch a ping from RPA (10.0.198.242) to RP-B (10.9.3.194) ,ICMP packet are sent using lan0 (Router-A).OK
I do a cable unplug, and I "wireshark" that ICMP packets are redirected to lan1, because it is the default gateway & lan0 is KO.
I assume that this is the correct behaviour.
After 10 mn , I recover the situation on lan0, plug the cable back.lanadmin status for lan0 is OK.
But,the amazing point , is that pings still going using default router in lan1......
traceroute confirms this point:
RP-A,sys,root # traceroute RP-B (go to lan1)
traceroute to RP-B (10.9.3.194), 30 hops max, 40 byte packets
1 10.0.198.225 (10.0.198.225) 0.487 ms 0.310 ms 0.263 ms
2 10.0.198.225 (10.0.198.225) 0.359 ms !H * 0.389 ms !H
The situation is recovered if I reboot the machine....
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-25-2010 08:36 PM
тАО11-25-2010 08:36 PM
Re: routing default gateway
Do you have any alternate gateway defined ?
What's your HP-UX version ?
What's your HP-UX version ?
Regards
Shibin
Shibin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2010 12:30 AM
тАО11-26-2010 12:30 AM
Re: routing default gateway
In HP-UX, if you have more than one network interface, you should always use traceroute with the '-i' option to explicitly select the network interface you wish to test. Otherwise the results can be misleading.
Please see this thread:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1171990
MK
Please see this thread:
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1171990
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2010 12:05 PM
тАО11-28-2010 12:05 PM
Re: routing default gateway
Do you have any alternate gateway defined ?
What's your HP-UX version ?
Only one default gateway on lan1.Hpux is 11.11
We don't use multihoming.We have reproduced the problem in our lab. In our lab we have:
RPA,sys,root # netstat -nrv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
10.0.198.226/255.255.255.255 10.0.198.226 UH 0 lan1 4136
134.134.134.65/255.255.255.255 134.134.134.65 UH 0 lan0 4136
134.134.134.64/255.255.255.240 134.134.134.65 U 2 lan0 1500
10.0.198.224/255.255.255.240 10.0.198.226 U 2 lan1 1500
159.23.14.0/255.255.255.0 134.134.134.66 UG 0 lan0 0
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0
default/0.0.0.0 10.0.198.225 UG 0 lan1 0
After lan0 switch off, ping are sent using lan1. When we recover/plug the lan0, ping's still going on lan1. Even, more, we get ping requests from the other side ,that are replied on the wrong lan1.
About traceroute with argument -i ,it makes feel confused in this case. I thought that the lan interface would be selected as a result of routing tables .
Gonzalo.
What's your HP-UX version ?
Only one default gateway on lan1.Hpux is 11.11
We don't use multihoming.We have reproduced the problem in our lab. In our lab we have:
RPA,sys,root # netstat -nrv
Routing tables
Dest/Netmask Gateway Flags Refs Interface Pmtu
127.0.0.1/255.255.255.255 127.0.0.1 UH 0 lo0 4136
10.0.198.226/255.255.255.255 10.0.198.226 UH 0 lan1 4136
134.134.134.65/255.255.255.255 134.134.134.65 UH 0 lan0 4136
134.134.134.64/255.255.255.240 134.134.134.65 U 2 lan0 1500
10.0.198.224/255.255.255.240 10.0.198.226 U 2 lan1 1500
159.23.14.0/255.255.255.0 134.134.134.66 UG 0 lan0 0
127.0.0.0/255.0.0.0 127.0.0.1 U 0 lo0 0
default/0.0.0.0 10.0.198.225 UG 0 lan1 0
After lan0 switch off, ping are sent using lan1. When we recover/plug the lan0, ping's still going on lan1. Even, more, we get ping requests from the other side ,that are replied on the wrong lan1.
About traceroute with argument -i ,it makes feel confused in this case. I thought that the lan interface would be selected as a result of routing tables .
Gonzalo.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP