- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers - Netservers
- >
- routing problem
ProLiant Servers - Netservers
1753973
Members
7887
Online
108811
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
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
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
03-09-2006 09:05 PM
03-09-2006 09:05 PM
routing problem
Hi all,
when I ping the host with 64 bytes it is ok but traceroute is not working and using wrong interface. with 1024 bytes ping lose packets.
what can cause this case. below you can see inf.
#ping 172.17.110.30
PING 172.17.110.30: 64 byte packets
64 bytes from 172.17.110.30: icmp_seq=0. time=0. ms
64 bytes from 172.17.110.30: icmp_seq=1. time=0. ms
64 bytes from 172.17.110.30: icmp_seq=2. time=0. ms
----172.17.110.30 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
# traceroute 172.17.110.30
traceroute: Warning: Multiple interfaces found; using 172.17.100.222 @ lan3
traceroute to 172.17.110.30 (172.17.110.30), 30 hops max, 40 byte packets
1 * * *
2 *bireycf1:/#
# netstat -nr
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
172.17.104.220 172.17.104.220 UH 0 lan0 4136
172.17.100.222 172.17.100.222 UH 0 lan3 4136
172.17.104.0 172.17.104.220 U 2 lan0 1500
172.17.100.0 172.17.100.222 U 2 lan3 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 172.17.104.1 UG 0 lan0 0
when I ping the host with 64 bytes it is ok but traceroute is not working and using wrong interface. with 1024 bytes ping lose packets.
what can cause this case. below you can see inf.
#ping 172.17.110.30
PING 172.17.110.30: 64 byte packets
64 bytes from 172.17.110.30: icmp_seq=0. time=0. ms
64 bytes from 172.17.110.30: icmp_seq=1. time=0. ms
64 bytes from 172.17.110.30: icmp_seq=2. time=0. ms
----172.17.110.30 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
# traceroute 172.17.110.30
traceroute: Warning: Multiple interfaces found; using 172.17.100.222 @ lan3
traceroute to 172.17.110.30 (172.17.110.30), 30 hops max, 40 byte packets
1 * * *
2 *bireycf1:/#
# netstat -nr
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 4136
172.17.104.220 172.17.104.220 UH 0 lan0 4136
172.17.100.222 172.17.100.222 UH 0 lan3 4136
172.17.104.0 172.17.104.220 U 2 lan0 1500
172.17.100.0 172.17.100.222 U 2 lan3 1500
127.0.0.0 127.0.0.1 U 0 lo0 0
default 172.17.104.1 UG 0 lan0 0
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