01-05-2011
Packet loss on ce interface.
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 = 91/91/98
Thanks,
Sparcman
9 More Discussions You Might Find Interesting
1. 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
2. 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
3. HP-UX
Hello,
I'm writing to you because I encountered the following problem. My program displayes all network interfaces that are available in the system, but I would like to add a functionality in which a user can enter a destination address IP (ex. the IP address of the Google search engine) and will... (1 Reply)
Discussion started by: foxrafi
1 Replies
4. Solaris
Dear all,
I am a newbie in solaris and I need your advice.
I have a Solaris version 5.9 installed on Sunfire V240.
I am able to ssh the machine from putty remotely.
My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies
5. SCO
Hi all
I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface?
If you have any ideas, please tell me then. Thank you (2 Replies)
Discussion started by: TinhNhi
2 Replies
6. IP Networking
This is my situation
DOS pc serial cable (sl0) Linux Pc eth1
192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router)
I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface.
... (3 Replies)
Discussion started by: mghis
3 Replies
7. UNIX for Dummies Questions & Answers
I have a RHEL 5 system with a bonded interface configure using only one network port (eth0). So I have config file for ifcfg-bond0 and ifcfg-eth. I'd like to configure eth5 to be the second SLAVE in the bond. My question is, after I modify ifcfg-eth5, can I add eth5 to the bond0 interface without... (1 Reply)
Discussion started by: westmoreland
1 Replies
8. AIX
(5 Replies)
Discussion started by: Vishal_dba
5 Replies
9. IP Networking
RHEL 7.0, IPV6
Scenario:
I have routed specific network using network scripts.
1. "ip -6 route show" shows that route has been added. ( with metric 1024)
2. Ping of the specific IP through that route is successful.
3. Now after few days, for some reason, we see that cache route appears for... (3 Replies)
Discussion started by: msr1981
3 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