01-02-2014
ping and 70% packet loss.
Most likely this is caused by HW or layer 2. The first thing to check is cabling. Then mismatching config (speed,duplex,LACP) between LAN switch port and NIC.
10 More Discussions You Might Find Interesting
1. IP Networking
Hi,
Is there any way that i can directly take out the IP packet and see its contents.
Waiting for your answer ..............
Bye (4 Replies)
Discussion started by: manjunath
4 Replies
2. UNIX for Advanced & Expert Users
I am experiencing a problem where under a dial condition I am experiencing packet loss, which is failrly normal, but the response to the packet loss is taking bewteen 6 and 10 seconds. Could someone please advise what the industry standard is on the response time under a packet loss senario. (1 Reply)
Discussion started by: shane
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
When i try this command
ping ukblx151.ukhx.astrazeneca.net -n 3 | grep icmp
it gives following error :mad::
0821-077 ping: illegal packet size.
But when i give command
ping ukblx151.ukhx.astrazeneca.net
It returns correct output.:D
Could you please help? (2 Replies)
Discussion started by: vishal_ranjan
2 Replies
4. IP Networking
I have 4 network ports on our T5240 sun server.
all but 1 gives packet losses (nxge1)
nxge0 gives on average 50% packet loss, very bad.
nxge2 gives on average 1-2% packet loss.
nxge3 gives on average 20% packet loss.
Is there a tool or something to help me find the problem? (11 Replies)
Discussion started by: photon
11 Replies
5. HP-UX
how to get network packet size
I would like get network output rate(kb/sec)
I type command "netstat -i"
Ipkts Ierrs Opkts Oerrs 653387 0 678202 0
but i didn't know what is it packet size ,
how could i get it? (1 Reply)
Discussion started by: alert0919
1 Replies
6. Solaris
Hi,
I am using the ce interface on my Solaris 9 server and there is significant packet loss when transmitting large packets. Does anyone have a fix for this?
----10.1.0.0 PING Statistics----
51 packets transmitted, 42 packets received, 17% packet loss
round-trip (ms) min/avg/max =... (12 Replies)
Discussion started by: sparcman
12 Replies
7. UNIX for Advanced & Expert Users
We're running Solaris 7 on FDDI n/w on an E6500 host and wish to use MTU (packet size) > 1500, more like 3072 bytes to begin with and possibly up to 4096 bytes.
Linux has /etc/network/interfaces. Does ANYONE remember the equivalent in Unix? When I do ifconfig eth0 mtu 4000, I get the error... (0 Replies)
Discussion started by: sharique
0 Replies
8. Solaris
Greetings, I'm stuck in a time warp using ancient machines from the prehistoric era that should be rightfully displayed in the Smithsonian.
We're running Solaris 7 on FDDI n/w on an E6500 host and wish to use MTU (packet size) > 1500, more like 3072 bytes to begin with and possibly up to 4096... (9 Replies)
Discussion started by: sharique
9 Replies
9. IP Networking
Hi!
I'm writing an application (using BSD sockets on a Linux host) which communicates over TCP/IP with an embedded device. This embedded device has an old and real slow integrated circuit (Epson S1S6000) which handles all of the TCP/IP communication for it.
Problem is, this circuit (S1S6000)... (7 Replies)
Discussion started by: olle
7 Replies
10. Shell Programming and Scripting
Hello,
on Solaris ping command does not report failed packet as in i.e. Windows (Connection timeout)
Instead it reports the sequence of the sent packet:
64 bytes from 10.80.4.120: icmp_seq=11. time=36.0 ms
64 bytes from 10.80.4.120: icmp_seq=12. time=35.9 ms
64 bytes from 10.80.4.120:... (6 Replies)
Discussion started by: drbiloukos
6 Replies
LEARN ABOUT DEBIAN
rds-ping
RDS-PING(1) BSD General Commands Manual RDS-PING(1)
NAME
rds-ping -- test reachability of remote node over RDS
SYNOPSIS
rds-ping [-c count] [-i interval] [-I local_addr] remote_addr
DESCRIPTION
rds-ping is used to test whether a remote node is reachable over RDS. Its interface is designed to operate pretty much the standard ping(8)
utility, even though the way it works is pretty different.
rds-ping opens several RDS sockets and sends packets to port 0 on the indicated host. This is a special port number to which no socket is
bound; instead, the kernel processes incoming packets and responds to them.
OPTIONS
The following options are available for use on the command line:
-c count
Causes rds-ping to exit after sending (and receiving) the specified number of packets.
-I address
By default, rds-ping will pick the local source address for the RDS socket based on routing information for the destination address
(i.e. if packets to the given destination would be routed through interface ib0, then it will use the IP address of ib0 as source
address). Using the -I option, you can override this choice.
-i timeout
By default, rds-ping will wait for one second between sending packets. Use this option to specified a different interval. The timeout
value is given in seconds, and can be a floating point number. Optionally, append msec or usec to specify a timeout in milliseconds
or microseconds, respectively.
Specifying a timeout considerably smaller than the packet round-trip time will produce unexpected results.
AUTHORS
rds-ping was written by Olaf Kirch <olaf.kirch@oracle.com>.
SEE ALSO
rds(7), rds-info(1), rds-stress(1).
BSD
Apr 22, 2008 BSD