HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- traceroute wrong outgoing interface
Operating System - HP-UX
1827844
Members
1265
Online
109969
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
Forums
Discussions
Discussions
Discussions
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
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
02-16-2004 08:33 PM
02-16-2004 08:33 PM
traceroute wrong outgoing interface
Hi forumers!
I've got 2 K570 Machines running in a MC/SG Environment with a simple HA NFS Configuration.
The first problem i had that the cluster seems to be running well but one of the packages was unreachable by its own ip while the node was accepting connections by its stationary ip.
So I shutdown the clusterdeamon and try to allocate the package ip using ifconfig lan0:1...with the same result. No response from ping.
traceroute -i lan0 is fully functional
traceroute -i lan0:1 returns nothing.
The next problem I have is, if i do an ifconfig lan0:1 unplumb and then a traceroute without any options the following message i get:
k570srv1:/ # k570srv1:/ # traceroute paros1
traceroute: Warning: Multiple interfaces found; using 192.83.252.1 @ lan1
traceroute to paros1.cms.fra.dlh.de (192.83.228.11), 30 hops max, 40 byte packets
1 * *.k570srv1:/ #
The following shows any information about my network configuration. Is there something wrong?
k570srv1:/ # lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
10/12/6 0x00108327580C 1 UP lan1 snap1 1 ETHER Yes 119
10/16/8 0x00306E0EAA5E 2 UP lan2 snap2 2 ETHER Yes 119
8/12/1/0 0x001083050690 0 UP lan0 snap0 3 ETHER Yes 119
k570srv1:/ # ifconfig lan0
lan0: flags=1843
inet 192.83.229.203 netmask ffffff00 broadcast 192.83.229.255
k570srv1:/ # ifconfig lan1
lan1: flags=843
inet 192.83.252.1 netmask ffffff00 broadcast 192.83.252.255
k570srv1:/ # netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan1 1500 192.83.252.0 192.83.252.1 10 0 4 0 0
lan0 1500 192.83.229.0 192.83.229.203 717 0 577 0 0
lo0 4136 127.0.0.0 127.0.0.1 144 0 144 0 0
k570srv1:/ # netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
192.83.229.203 192.83.229.203 UH 0 lan0 4136
192.83.252.1 192.83.252.1 UH 0 lan1 4136
192.83.252.0 192.83.252.1 U 2 lan1 1500
192.83.229.0 192.83.229.203 U 2 lan0 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 192.83.229.162 UG 0 lan0 0
I'm really confused about this behavior.
Thanks in advance
cl
I've got 2 K570 Machines running in a MC/SG Environment with a simple HA NFS Configuration.
The first problem i had that the cluster seems to be running well but one of the packages was unreachable by its own ip while the node was accepting connections by its stationary ip.
So I shutdown the clusterdeamon and try to allocate the package ip using ifconfig lan0:1...with the same result. No response from ping.
traceroute -i lan0
traceroute -i lan0:1 returns nothing.
The next problem I have is, if i do an ifconfig lan0:1 unplumb and then a traceroute without any options the following message i get:
k570srv1:/ # k570srv1:/ # traceroute paros1
traceroute: Warning: Multiple interfaces found; using 192.83.252.1 @ lan1
traceroute to paros1.cms.fra.dlh.de (192.83.228.11), 30 hops max, 40 byte packets
1 * *.k570srv1:/ #
The following shows any information about my network configuration. Is there something wrong?
k570srv1:/ # lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
10/12/6 0x00108327580C 1 UP lan1 snap1 1 ETHER Yes 119
10/16/8 0x00306E0EAA5E 2 UP lan2 snap2 2 ETHER Yes 119
8/12/1/0 0x001083050690 0 UP lan0 snap0 3 ETHER Yes 119
k570srv1:/ # ifconfig lan0
lan0: flags=1843
inet 192.83.229.203 netmask ffffff00 broadcast 192.83.229.255
k570srv1:/ # ifconfig lan1
lan1: flags=843
inet 192.83.252.1 netmask ffffff00 broadcast 192.83.252.255
k570srv1:/ # netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan1 1500 192.83.252.0 192.83.252.1 10 0 4 0 0
lan0 1500 192.83.229.0 192.83.229.203 717 0 577 0 0
lo0 4136 127.0.0.0 127.0.0.1 144 0 144 0 0
k570srv1:/ # netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
192.83.229.203 192.83.229.203 UH 0 lan0 4136
192.83.252.1 192.83.252.1 UH 0 lan1 4136
192.83.252.0 192.83.252.1 U 2 lan1 1500
192.83.229.0 192.83.229.203 U 2 lan0 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 192.83.229.162 UG 0 lan0 0
I'm really confused about this behavior.
Thanks in advance
cl
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 10:05 PM
02-17-2004 10:05 PM
Re: traceroute wrong outgoing interface
All problems are solved!
regards
cl
regards
cl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 10:07 PM
02-17-2004 10:07 PM
Re: traceroute wrong outgoing interface
What was it?
Regs David
Regs David
@yourservice
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2004 10:32 PM
02-17-2004 10:32 PM
Re: traceroute wrong outgoing interface
The first was a wrong configured GBE-Interface inside our Network-Switch. There was a problem with Auto-Negotiation. I don´t know why, but now it works fine.
The second was really simple. There are differences between the traceroute-binaries of 11.00 and 11.11.
The version contained by 11.11 requires the "-i" option if there are multiple interfaces installed on the syst
The second was really simple. There are differences between the traceroute-binaries of 11.00 and 11.11.
The version contained by 11.11 requires the "-i" option if there are multiple interfaces installed on the syst
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP