perfsonar-user - Re: [perfsonar-user] how to identify the currently-running test?
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Eli Dart <>
- To: Pete Siemsen <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] how to identify the currently-running test?
- Date: Wed, 12 Oct 2016 11:44:12 -0700
- Ironport-phdr: 9a23:ZN1krByaQ+eXnj/XCy+O+j09IxM/srCxBDY+r6Qd0uIUIJqq85mqBkHD//Il1AaPBtqLra8fwLOL+4nbGkU+or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6aijSI4DUTAhTyMxZubqSwQ9aKzpf/6+fnw5DPbk1zhTe4er50ZEGtrAjUrcQQqZZpI7x3xxfU9ChmYeNTkE5sJBq/lgzgrpO89YR/2ylL/fQs65gTAu3BY60kQOkAX3wdOGcv6Ziu7EGbQA==
- Ironport-phdr: 9a23:hndPQRxUXHaaUkrXCy+O+j09IxM/srCxBDY+r6Qd0e8TIJqq85mqBkHD//Il1AaPBtSBra4ewLOM7+jJYi8p2d65qncMcZhBBVcuqP49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL2PbrnD61zMOABK3bVMzfbWvXNKIxJ3ti6ibwN76W01wnj2zYLd/fl2djD76kY0ou7ZkMbs70RDTo3FFKKx8zGJsIk+PzV6nvp/jtLYqySlbuuog+shcSu26Ov1gFf0LRAghZlg4+MCjjhjOSBCC4DNISWQblwFFBSDY5xjgGJr9r32pmPB63Xy3Ocy+YbkuRXz2465xVDflk2EBOiJvozKfsdB5kK8O+EHpnBd42YOBJdjNbPc=
Hi Pete,
Is flow control enabled between the host and the router? One possible cause for this circumstance is the host being unable to sink traffic, and sending pause frames to the router (which it should), and the router then filling its queue and dropping packets.
Another possibility would be if you were running owamp and throughput tests on the same host. If the throughput test and the owamp test enter the router via different interfaces (or a common faster interface), then the traffic for both tests might not fit into the interface connected to the host - that could also cause output drops.
Do you feel that either of these circumstances are a good fit for the current config?
Thanks,
Eli
On Wednesday, October 12, 2016, Pete Siemsen <> wrote:
On Wednesday, October 12, 2016, Pete Siemsen <> wrote:
We have a perfSONAR server that is directly connected to a router. The router reports that the "Output drops" counter is going up on the interface that connects to the perfSONAR server. We graph output drops on all interfaces, so I have a nice graph that shows that the drops occur in regular spurts. So, some test that runs regularly causes the drops. Like, every ~20 minutes, there's a spurt of 2000 output drops.There are 18 tests defined on the server. I want to identify the one that is causing the drops.I can monitor the interface on the router, and see the "output drops" counter bump up once in a while. I could wait for a spurt, then identify the test that is running "right now". To identify the test running right now, I could do a "top" command and see the "iperf3" or "java" process that is consuming the most CPU. I also see several bwctl processes, each of which shows the remote site name/IP.This is almost enough, but I feel like I don't have my mind right :-) What's the clueful way to approach this problem?-- Pete
--
Eli Dart, Network Engineer NOC: (510) 486-7600
ESnet Science Engagement Group (800) 333-7638
Lawrence Berkeley National Laboratory
- [perfsonar-user] how to identify the currently-running test?, Pete Siemsen, 10/12/2016
- Re: [perfsonar-user] how to identify the currently-running test?, Eli Dart, 10/12/2016
- Re: [perfsonar-user] how to identify the currently-running test?, Matthew J Zekauskas, 10/12/2016
- Re: [perfsonar-user] how to identify the currently-running test?, Eli Dart, 10/12/2016
- Re: [perfsonar-user] how to identify the currently-running test?, Matthew J Zekauskas, 10/12/2016
- Re: [perfsonar-user] how to identify the currently-running test?, Mark Feit, 10/12/2016
- Re: [perfsonar-user] how to identify the currently-running test?, Eli Dart, 10/12/2016
Archive powered by MHonArc 2.6.19.