Sponsored Content
Operating Systems AIX Packet loss coming with big packet size ping Post 302881910 by MadeInGermany on Thursday 2nd of January 2014 06:18:02 PM
Old 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

Seeing IP packet

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

Response time under packet loss

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

0821-077 ping: illegal packet size.

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

packet loss problem

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

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

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 =... (12 Replies)
Discussion started by: sparcman
12 Replies

7. UNIX for Advanced & Expert Users

Need help with configuring large packet size on Solaris 7 / e6500

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

Need help with configuring large packet size on Solaris 7 / e6500

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

TCP Packet size

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

Solaris ping report failed packet script

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
lan_config(8)						      System Manager's Manual						     lan_config(8)

NAME
lan_config - Modifies low-level configuration parameters for a given LAN interface SYNOPSIS
/usr/sbin/lan_config -i interface_name [-a [0 | 1]] [-m [aui | bnc | utp | fiber]] [-s [10 | 100]] [-x [0 | 1]] OPTIONS
Changes the specified characteristics for interface_name. You must provide an interface name. Enables (1) or disables (0) IEEE 802.3u autonegotiation. This option applies only to those devices that are capable of autonegotiation (for example, DE500-AA and DE500-BA). When enabled, the interface automatically negotiates the link speed (10 or 100 Mb/s) and the mode (half-duplex or full-duplex) with the remote interface. The interface initially advertises the speed and mode previously selected at the console level or with the -s and -x options. The -s and -x options may also be specified on the same command line as the -a option to redefine and renegotiate the interface's capa- bility (when enabled) or to force the interface at a certain configuration (when disabled). Note The interface initiates the autonegotiation process only if and when it is up and running. See ifconfig(8) for information on how the interface is marked up. Changes the type of medium. The following table lists the supported types: -------------------------------------------------------------- Type Meaning -------------------------------------------------------------- aui 10Base5, or thick wire bnc 10Base2, or ThinWire utp 10BaseT (if speed is 10 Mb/s) or 100BaseT (if speed is 100 Mb/s), or twisted-pair fiber 100BaseFX only -------------------------------------------------------------- On some devices, for example, DE435 and DE425, bnc selection is done by means of an on-board gang jumper. When specifying aui or bnc for these devices, be sure that the jumper is in the correct position. Changes the medium speed, if the interface is capable of operating at both regular (10 Mb/s) and fast (100 Mb/s) Ethernet speeds. The fast speed cannot be selected for the aui and bnc media. Enables (1) or disables (0) full-duplex operation when the utp medium is specified. DESCRIPTION
The lan_config command allows you to modify the type of medium, speed, and mode of operation (half- or full-duplex). You can also use the lan_config command to enable or disable autonegotiation, if the underlying device has this capability. Autonegotia- tion is a hardware and software (driver) process that allows determination of the highest common speed and duplex (half or full) configura- tion. The permitted combinations of speed and mode of operation in descending order of precedence, from the highest to the lowest, are: ----------------------- Speed Mode ----------------------- 100 Mb/s full-duplex 100 Mb/s half-duplex 10 Mb/s full-duplex 10 Mb/s half-duplex ----------------------- During autonegotiation, for example, if the local interface advertises that it is capable of 100 Mb/s half-duplex operation, it is by implication also capable of 10 Mb/s, full-duplex and 10 Mb/s, half-duplex operation. If the remote interface advertises that it is capable of 10 Mb/s, full-duplex operation only, the link is established at 10 Mb/s, full-duplex. The autonegotiation process can take several sec- onds to complete. The characteristics managed with the lan_config command are ordinarily set from the console level via the EWx0_MODE environment variable. The lan_config command allows you to override this default and configure the interface as needed after the system is up and running. Modifications made with the lan_config command do not persist across reboots of the operating system. You can also use the ifconfig command to set the speed and mode (half- or full-duplex) either from the command line or in the /etc/rc.local file. If you specify the command in the rc.local file, the command is executed each time the system is booted; you do not have to modify the SRM console environment variables. RESTRICTIONS
Support for the lan_config command is limited to the tu interface for this release of Tru64 UNIX. EXAMPLES
To switch from aui or bnc to utp full-duplex operation on tu0, enter: lan_config -i tu0 -m utp -x 1 To disable full-duplex operation on tu0, enter: lan_config -i tu0 -x 0 To enable autonegotiation on tu1, limiting capability to 100 Mb/s, enter: lan_config -i tu1 -a 1 -s 100 -x 0 To disable autonegotiation on tu1, forcing 10 Mb/s, half-duplex operation, enter: lan_config -i tu1 -a 0 -s 10 -x 1 SEE ALSO
Commands: ifconfig(8) Files: inet.local(4) Interfaces: tu(7) lan_config(8)
All times are GMT -4. The time now is 07:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy