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
ping(8) System Manager's Manual ping(8)
Name
ping - send ICMP ECHO_REQUEST packets to network hosts
Syntax
/etc/ping [ options ] host [ datasize [ npackets ]]
Description
The DARPA Internet is a large and complex network of hardware connected together by gateways. The command utilizes the ICMP protocol's
mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (pings) have an IP and ICMP
header, followed by a struct timeval, and then an arbitrary number of pad bytes used to fill out the packet. The length of the default
datagram 64 bytes, but this may be changed using the command-line option.
Typing ``ping host'' without any options will either report ``host is alive'' or ``no answer from host''. To get more statistics use the
-l option or one of the other options.
When using for fault isolation, it should first be run on the local host to verify that the local network interface is up and running.
Then, hosts and gateways further and further away should be pinged. The command with options sends one datagram per second and prints one
line of output for every ECHO_RESPONSE returned. No output is produced if there is no response. If an optional npackets is given, only
that number of requests is sent. Round-trip times and packet loss statistics are computed. When all responses have been received or the
program times out with npackets specified, or if the program is terminated with a SIGINT, a brief summary is displayed.
Options
-d Turns on SO_DEBUG flag on the socket.
-l Gives more statistics than if is used without options. Long output.
-r Bypasses the normal routing tables and sends directly to a host on an attached network. If the host is not on a directly-attached
network, an error is returned. This option can be used to ping a local host through an interface that has no route through it. For
example, after the interface was dropped by
-v Lists ICMP packets other than ECHO RESPONSE that are received. Verbose output.
Restrictions
This program is intended for use in network testing, measurement, and management. It should be used primarily for manual fault isolation.
Because of the load it could impose on the network, it is unwise to use during normal operations or from automated scripts.
See Also
netstat(1), ifconfig(8c)
ping(8)