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
LEARN ABOUT OPENSOLARIS
dnet
dnet(7D) Devices dnet(7D)
NAME
dnet - Ethernet driver for DEC 21040, 21041, 21140 Ethernet cards
SYNOPSIS
/kernel/drv/dnet
DESCRIPTION
The dnet Ethernet driver is a multithreaded, loadable, clonable, STREAMS GLD driver. Multiple controllers installed within the system are
supported by the driver. The dnet driver functions include controller initialization, frame transmit and receive, functional addresses,
promiscuous and multicast support, and error recovery and reporting.
APPLICATION PROGRAMMING INTERFACE
The cloning character-special device, /dev/dnet, is used to access all DEC 21040/21041/21140 devices installed in the system.
The dnet driver is dependent on /kernel/misc/gld, a loadable kernel module that provides the dnet driver with the DLPI and STREAMS func-
tionality required of a LAN driver. See gld(7D) for more details on the primitives supported by the driver.
The device is initialized on the first attach and de-initialized (stopped) on the last detach.
The values returned by the driver in the DL_INFO_ACK primitive in response to a DL_INFO_REQ from the user are as follows:
o The maximum SDU is 1500 (ETHERMTU - defined in <sys/ethernet.h>).
o The minimum SDU is 0.
o The DLSAP address length is 8.
o The MAC type is DL_ETHER.
o The sap length value is -2, meaning the physical address component is followed immediately by a 2-byte sap component within the
DLSAP address.
o The broadcast address value is the Ethernet/IEEE broadcast address (FF:FF:FF:FF:FF:FF).
Once in the DL_ATTACHED state, the user must send a DL_BIND_REQ to associate a particular Service Access Point (SAP) with the stream.
PRECONFIGURATION
The PCI configuration process varies from system to system. Follow the instructions provided by the vendor.
Known Problems and Limitations
o On multiport cards (exception: Osicom (Rockwell) RNS2340), the first port is the top port. (On the Osicom RNS2340, the first
port is the bottom port.)
o If the dnet driver fails to determine the correct speed and duplex mode resulting in a corresponding drop in performance, set
the speed and duplex mode using the dnet.conf file.
o The dnet driver incorrectly counts carrier lost or no carrier errors while in full-duplex mode. There is no carrier signal
present when in full-duplex mode and it should not be counted as an error.
o Version 4 SROM formats are not supported.
CONFIGURATION
The /kernel/drv/dnet.conf file supports the following options:
full-duplex For full duplex operation use full-duplex=1, for half duplex use full-duplex=0. Half-duplex operation gives better results
on older 10mbit networks.
speed For 10mbit operation use speed=10, for 100mbit operation use speed=100. Certain 21140 based cards will operate at either
speed. Use the speed property to override the 100mbit default in this case.
FILES
/dev/dnet character special device
/kernel/drv/dnet.conf dnet configuration file
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
SEE ALSO
attributes(5), dlpi(7P), gld(7D) streamio(7I)
Writing Device Drivers
STREAMS Programming Guide
SunOS 5.11 20 OCT 2000 dnet(7D)