On pci (a-/n-class) systems with 100bt cards, you're more likely to see 'recv dropped: addr' counts due to the way the
card handles (or not, actually) traffic routed for a different destination.
Typically these counts are nothing to be concerned about.
What is concerning are the tcp statistics. Retransmits are almost* always a function of using the default (or otherwise
messed up) tcp timers. - d
* let's just say I've never seen a case where it's not....
---
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Kevin Smeltzer
> Sent: Friday, July 29, 2011 10:29 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Deteriorating Network response times
>
> The second network card, is where we are getting the high 'Recv dropped'
> activity.
> Recv dropped: addr 1158497
> These packets that can not be identified by the HP3000 are coming from a
> Window server running some Tivoli enterprise software monitoring system.
> Few users know the IP address or DNS entry that will allow them to connect
> to the Fastlnk2 card. Used by HP3000 system to send and receive FTP.
> The 'Recv Dropped' activity also makes my NMLG files very difficult to
> use. >99% messages about failure to process these packets.
>
> To catch everyone up:
> :run nettool.net;info="status;tcp;tcp"
>
> NETTOOL Version: B07050A8
>
> Enter HELP HELP for an explanation of the help facility.
>
> Enter HELP OPERATION for guidance on NETTOOL use.
>
> Commands can be abbreviated, HELP keywords cannot.
>
> Menu-specific commands for the ROOT:
>
> >>>status
> >>>tcp
> >>>tcp
> Local IP Address : @
> =============================================================================
> TCP GLOBAL Statistics
> Current Time: FRI, JUL 29, 2011, 12:39:22 PM
> =============================================================================
> TCP GLOBAL Statistics
> Maximum number of connections allowed : 1024
> Maximum number of sockets allowed : 4096
> Number of connections currently open : 23
> Maximum re-transmissions per packet : 8
> Cumulative Statistics
> ---------------------
> . Total active opens : 148
> . Total passive opens : 203
> . Total inbound segments : 119625
> . Total outbound sengments : 103467
> . Total re-transmitted segments : 2235
> . Total number of RESETS sent : 121
> . Total connection failures : 3
> [1]STATUS.TCPSTAT>>>q
>
> HMO-DEV:linkcontrol @,a
> Linkname: DTSLINK Linktype: PCI 100BT Linkstate: CONNECTED
> Physical Path: 0/0/0/0
> Current Station Address: 00-30-6E-C3-E3-CB
> Default Station Address: 00-30-6E-C3-E3-CB
> Current Multicast Addresses:
> 09-00-09-00-00-01 09-00-09-00-00-03 09-00-09-00-00-04
> 09-00-09-00-00-06
>
> Transmit bytes 22758713 Receive bytes 107527191
> Transmits 108933 Receives unicast 121952
> Transmits no error 108933 Receives broadcast 39348
> Transmits dropped 0 Receives multicast 0
> Transmits deferred 0 Receives no error 161297
> Transmits 1 retry 0 Recv CRC error 0
> Transmits >1 retry 0 Recv Maxsize error 0
> Trans 16 collisions 0 Recv dropped: addr 3
> Trans late collision 0 Recv dropped: buffer 0
> Trans underruns 0 Recv dropped: descr 0
> Carrier losses 0 Recv dropped: other 0
> Trans jabber timeout 0 Recv watchdg timeout 0
> Link disconnects 0 Recv collisions 0
> Link speed 100 Recv overruns 0
> Link duplex Full Link auto sensed No
> Link mode 100Base-TX Core Secs since clear 67328
>
> Linkname: FASTLNK2 Linktype: PCI 100BT Linkstate: CONNECTED
> Physical Path: 1/8/0/0
> Current Station Address: 00-30-6E-EA-85-0F
> Default Station Address: 00-30-6E-EA-85-0F
> Current Multicast Addresses:
> 09-00-09-00-00-01
>
> Transmit bytes 4750 Receive bytes 118738144
> Transmits 83 Receives unicast 95
> Transmits no error 83 Receives broadcast 1315933
> Transmits dropped 0 Receives multicast 0
> Transmits deferred 0 Receives no error 157531
> Transmits 1 retry 0 Recv CRC error 0
> Transmits >1 retry 0 Recv Maxsize error 0
> Trans 16 collisions 0 Recv dropped: addr 1158497
> Trans late collision 0 Recv dropped: buffer 0
> Trans underruns 0 Recv dropped: descr 0
> Carrier losses 0 Recv dropped: other 0
> Trans jabber timeout 0 Recv watchdg timeout 0
> Link disconnects 0 Recv collisions 0
> Link speed 100 Recv overruns 0
> Link duplex Full Link auto sensed No
> Link mode 100Base-TX Addon Secs since clear 67318
> _________________
> Kevin Smeltzer
> IT Specialist - HP MPE systems
> 804-354-7950
> Cell: 804-651-5428
> [log in to unmask]
>
>
>
> From: Jeff Kell <[log in to unmask]>
> To: [log in to unmask]
> Date: 07/29/2011 11:29 AM
> Subject: Re: [HP3000-L] Deteriorating Network response times
> Sent by: HP-3000 Systems Discussion <[log in to unmask]>
>
>
>
> On 7/29/2011 10:53 AM, Kevin Smeltzer wrote:
> > Linkname: DTSLINK Linktype: PCI 100BT Linkstate: CONNECTED
> >
> > Transmits no error 62694 Receives broadcast 33532
> > Link mode 100Base-TX Core Secs since clear 57355
> >
> > Linkname: FASTLNK2 Linktype: PCI 100BT Linkstate: CONNECTED
> >
> > Transmits no error 32 Receives broadcast 1120014
> > Link mode 100Base-TX Addon Secs since clear 57345
> >
>
> Thats a broadcast every 2 seconds (roughly) on the first, and 20
> broadcasts/second on
> the second.
>
> Something looks terribly fishy with the second link.
>
> Jeff
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
