01-02-2014
Are you sure it's actual packet loss or is it packets being retransmitted?
Can you indicate the path from database server to application server and what virtual (hyper visors) are involved at each step?
What level of AIX are you running, and what level of firmware code?
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 OPENSOLARIS
auscope
AUSCOPE(1) General Commands Manual AUSCOPE(1)
NAME
auscope - Network Audio System Protocol Filter
SYNOPSIS
auscope [ option ] ...
DESCRIPTION
auscope is an audio protocol filter that can be used to view the network packets being sent between an audio application and an audio
server.
auscope is written in Perl, so you must have Perl installed on your machine in order to run auscope. If your Perl executable is not
installed as /usr/local/bin/perl, you should modify the first line of the auscope script to reflect the Perl executable's location. Or,
you can invoke auscope as
perl auscope [ option ] ...
assuming the Perl executable is in your path.
To operate, auscope must know the port on which it should listen for audio clients, the name of the desktop machine on which the audio
server is running and the port to use to connect to the audio server. Both the output port (server) and input port (client) are automati-
cally biased by 8000. The output port defaults to 0 and the input port defaults to 1.
ARGUMENTS
-i<input-port>
Specify the port that auscope will use to take requests from clients.
-o<output-port>
Determines the port that auscope will use to connect to the audio server.
-h<audio server name>
Determines the desktop machine name that auscope will use to find the audio server.
-v<print-level>
Determines the level of printing which auscope will provide. The print-level can be 0 or 1. The larger numbers provide greater
output detail.
EXAMPLES
In the following example, mcxterm is the name of the desktop machine running the audio server, which is connected to the TCP/IP network
host tcphost. auscope uses the desktop machine with the -h command line option, will listen for client requests on port 8001 and connect
to the audio server on port 8000.
Ports (file descriptors) on the network host are used to read and write the audio protocol. The audio client auplay will connect to the
audio server via the TCP/IP network host tcphost and port 8001:
auscope -i1 -o0 -hmcxterm
auplay -audio tcp/tcphost:8001 dial.snd
In the following example, the auscope verbosity is increased to 1, and the audio client autool will connect to the audio server via the
network host tcphost, while displaying its graphical interface on another server labmcx:
auscope -i1 -o0 -hmcxterm -v1
autool -audio tcp/tcphost:8001 -display labmcx:0.0
SEE ALSO
nas(1), perl(1)
COPYRIGHT
Copyright 1994 Network Computing Devices, Inc.
AUTHOR
Greg Renda, Network Computing Devices, Inc.
1.9.3 AUSCOPE(1)