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 OSF1
dhcpcemu
dhcpcemu(8) System Manager's Manual dhcpcemu(8)
NAME
dhcpcemu - Emulate a DHCP client
SYNOPSIS
/usr/sbin/dhcpcemu [-b] [-q] [-m | -n | -v] [-dn] [-a server_address] [-c client_address] [-e hardware_address] [-h hostname] [-i
client_identifier] [-r requested_address] [-p bootp | discover | renew | rebind | request | select | decline] [-s size] [-t timeout] [-f
file] interface
OPTIONS
Sets the broadcast bit. Runs quietly: display neither the contents of the incoming nor the outgoing packets. Sets the magic cookie in the
outgoing packet to be the CMU (-m) or the RFC1048 (-v ) value (the default). The -n option means to use no cookie at all. The server
identifier field in the options of the outgoing packet is set to the IP address. To properly emulate a client in the selecting DHCP state,
this field is required regardless of the value given with the -p option. Sets the ciaddr field in the packet to the value client_address
or to the IP address of the interface chosen if client_address equals 0.0.0.0. Pretend to be at the given hardware (MAC) address. The
chaddr field is set to hardware_address. Unless the broadcast bit is also set, this usually means that no replies will be received, as the
server or relay agents will normally try a link-level unicast to the phony address. Sets the hostname option in the outgoing packet to the
given value. Sets the client identifier option in the outgoing packet to the given string. The string is treated literally, not as a hex
representation of an arbitrary octet string. Sets the IP address value in the outgoing packet. This option is required if the outgoing
packet is to validly represent a client in the DHCP states selecting or rebooting or in a DHCP DECLINE message. The string following
determines the kind of BOOTP or DHCP packet sent, and whether the packet is broadcast or unicast. The default is to emulate a BOOTP
client. Sends a packet of size octets (by default 548 octets). Exits after timeout seconds if no responses are received. Sets the file
field in the outgoing packet to the given string.
DESCRIPTION
The dhcpcemu command emulates a DHCP/BOOTP client. Options are provided to set the most important fields in the BOOTP request packet. A
packet is constructed, is sent through the interface specified, and a reply awaited. The emulator exits after the first reply is received
or for a length of time specified by the -t option. Depending on the options specified and/or the DHCP server configuration, no reply may
in fact be forthcoming. If no timeout is specified, the emulator may be killed with any suitable asynchronous signal. The SIGINT signal
(usually generated from the keyboard with Ctrl/c) is available if dhcpcemu is running in the foreground.
It is important to note that with the options available, it is quite possible to create an illegal packet. This is one of the primary func-
tions of dhcpcemu; to test the behavior of servers when confronted with packets that do not conform to the standards.
RESTRICTIONS
A cluster member should never be a DHCP client. It should always use static addressing.
If a cluster is to support a DHCP server, there can be only one DHCP server for all the cluster members using a common database with
failover.
SEE ALSO
RFC2031, RFC2032
dhcpcemu(8)