[arm-allstar] Monitoring of my system.

[Paul Aidukas]

Doug,  check out the lsNodes on this machine. It has the added code for
IRLP and shows all the IRLP information also.


On Tue, May 30, 2017 at 6:05 PM, Paul Aidukas <paulkn2r at gmail.com> wrote:

> Yes Doug he can monitor many hubs and nodes from one screen if he likes.
>
> You would need the ports open in the firewall for access to the AllStar
> Manager  for the hubs to monitor, defaults to port 5038 (TCP).  Then you
> need to add the hostname or IP, port, login, and passwd, for the manager,
> on the web hosting machines allmon.ini file.
> That's it.
>
> Here is an example of three separate bridging Hubs on one screen:
>
> http://stn4067.ip.irlp.net
>
> Paul / KN2R
>
>
> On Tue, May 30, 2017 at 4:36 PM, "C B via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> Hi
>> that did not post correctly.
>> maybe it could be described this way, the same format but separated by
>> node number, just all of the nodes on one list.
>> Chris
>>
>>       From: C B via arm-allstar <arm-allstar at hamvoip.org>
>>  To: ARM Allstar <arm-allstar at hamvoip.org>
>> Cc: C B <harvard5362 at yahoo.com>
>>  Sent: Tuesday, May 30, 2017 1:30 PM
>>  Subject: Re: [arm-allstar] Monitoring of my system.
>>
>> Thanks
>> already using allmon2, works good.
>> please see below example 1 is for each node showing its connected sites.
>> Example 2 is how i would like it to look. just all of my nodes (note the
>> cut and paste did not go well the columns did not align though.
>> I have only 2 sites left and then all of my dying RLC DSP404"s will have
>> been replaced with PI3's. I used your recommendation and each repeater has
>> its own PI3
>> Chris
>>
>> | Node 29883 - N6LXX N6LXX HUB BURBANK,CA Bubble Chart |
>> | Node | Node Information | Received | Link | Direction | Connected |
>> Mode |
>> | 29913 | N6LXX 447.875 DENVER | 000:00:08 | ESTABLISHED | IN | 117:53:52
>> | Transceive |
>> | 2066 | KE6PCV 445.220- Corona, CA | 000:11:15 | ESTABLISHED | IN |
>> 04:56:42 | Transceive |
>> | 43815 | N6LXX/R WILSON HUB | 000:20:09 | ESTABLISHED | IN | 64:06:59 |
>> Transceive |
>> | 42155 | WB6FYR 224.920 -1.6 Flint Peak, Glendale, CA | 018:20:28 |
>> ESTABLISHED | OUT | 89:56:19 | Transceive |
>>
>>
>>
>> | Node 43815 - N6LXX/R WILSON HUB Bubble Chart |
>> | Node | Node Information | Received | Link | Direction | Connected |
>> Mode |
>> | 29883 | N6LXX N6LXX HUB BURBANK,CA | 000:00:09 | ESTABLISHED | OUT |
>> 76:30:41 | Transceive |
>> | 27008 | N6LXX 440 OAT MTN CALIF | 000:20:10 | ESTABLISHED | IN |
>> 76:27:44 | Transceive |
>> | 43812 | N6LXX/R 53.62 - HARVARD | 000:27:20 | ESTABLISHED | IN |
>> 88:36:55 | Transceive |
>> | 43816 | N6LXX BLUE RIDGE | 000:53:25 | ESTABLISHED | IN | 45:43:37 |
>> Transceive |
>> | 43818 | N6LXX/R Sunset | 001:24:47 | ESTABLISHED | IN | 48:13:32 |
>> Transceive |
>> | 43814 | N6LXX/R 927.5625 - HARVARD | 003:28:26 | ESTABLISHED | IN |
>> 88:36:55 | Transceive |
>> | 1121 |   | 023:46:47 | ESTABLISHED | IN | 88:36:54 | Transceive |
>> | 43820 | N6LXX 53.56 -0.5 OAK GLEN, CA | Never | ESTABLISHED | IN |
>> 11:37:48 | Transceive
>>
>>  |
>>
>>
>> Exampel 2
>> |  Node
>>
>>   |  Node Information
>>
>>   |  Received
>>
>>   |  Link
>>
>>   |  Direction
>>
>>   |  Connected
>>
>>   |  Mode
>>
>>   |
>> |  29913
>>
>>   |  N6LXX 447.875 DENVER
>>
>>   |  000:00:08
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  117:53:52
>>
>>   |  Transceive
>>
>>   |
>> |  2066
>>
>>   |  KE6PCV 445.220- Corona, CA
>>
>>   |  000:11:15
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  04:56:42
>>
>>   |  Transceive
>>
>>   |
>> |  43815
>>
>>   |  N6LXX/R WILSON HUB
>>
>>   |  000:20:09
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  64:06:59
>>
>>   |  Transceive
>>
>>   |
>> |  42155
>>
>>   |  WB6FYR 224.920 -1.6 Flint Peak, Glendale, CA
>>
>>   |  018:20:28
>>
>>   |  ESTABLISHED
>>
>>   |  OUT
>>
>>   |  89:56:19
>>
>>   |  Transceive
>>
>>   |
>>
>>
>>
>>
>> |
>>  |  |  |  |  |  |  |
>> |  27008
>>
>>   |  N6LXX 440 OAT MTN CALIF
>>
>>   |  000:20:10
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  76:27:44
>>
>>   |  Transceive
>>
>>   |
>> |  43812
>>
>>   |  N6LXX/R 53.62 - HARVARD
>>
>>   |  000:27:20
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  88:36:55
>>
>>   |  Transceive
>>
>>   |
>> |  43816
>>
>>   |  N6LXX BLUE RIDGE
>>
>>   |  000:53:25
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  45:43:37
>>
>>   |  Transceive
>>
>>   |
>> |  43818
>>
>>   |  N6LXX/R Sunset
>>
>>   |  001:24:47
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  48:13:32
>>
>>   |  Transceive
>>
>>   |
>> |  43814
>>
>>   |  N6LXX/R 927.5625 - HARVARD
>>
>>   |  003:28:26
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  88:36:55
>>
>>   |  Transceive
>>
>>   |
>> |  1121
>>
>>   |
>>
>>   |  023:46:47
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  88:36:54
>>
>>   |  Transceive
>>
>>   |
>> |  43820
>>
>>   |  N6LXX 53.56 -0.5 OAK GLEN, CA
>>
>>   |  Never
>>
>>   |  ESTABLISHED
>>
>>   |  IN
>>
>>   |  11:37:48
>>
>>   |  Transceive
>>
>>   |
>>
>>
>>
>>
>>
>>       From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
>>  To: ARM Allstar <arm-allstar at hamvoip.org>
>> Cc: Doug Crompton <wa3dsp at gmail.com>
>>  Sent: Tuesday, May 30, 2017 11:49 AM
>>  Subject: Re: [arm-allstar] Monitoring of my system.
>>
>> Chris,
>>
>>  First of all congratulations on all those nodes! Have you tried supermon
>> or allmon2. Both would show the currently transmitting node. I think one
>> screen would get very busy for the number of nodes you have though. Based
>> on the complexity of your system it is a little hard to understand exactly
>> what you want to do.
>>
>> I suspect you need to have all or many of those nodes report back to one
>> location. I would defer to Paul KN2R on this since he authored supermon
>> and
>> I think he monitors many nodes himself.
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>> On Tue, May 30, 2017 at 1:51 PM, "C B via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> > Hi
>> > Sorry if this has been asked before.
>> > I am looking for a way to see all of my connected nodes to see which
>> > repeater (node) the incoming signal  comes from. This is handy for may
>> > things including troubleshooting.
>> > In the beginning I connected all of my to one hub node, this allowed me
>> to
>> > easily see which repeater (node) any incoming signal came from.
>> > at this point I have more than 25 (pi3) nodes up (on my way to about 40)
>> > and permanently connected, thus connecting all to one node considering
>> the
>> > way my system is connected did not make a lot of sense.
>> > as the system is connected primarily by microwave site to site, it
>> seemed
>> > to be more logical the sites that have  more than one repeater to have a
>> > HUB node at the site connecting all of the repeaters at that site
>> together
>> > then connecting to the next site.
>> > with the old method if the microwave failed, each site wood no longer be
>> > linked to repeaters at the same site or to sites that still had
>> > connectivity.
>> > this method seems to be better with respect to linking, however it is
>> not
>> > as good for monitoring with allmon2. signals can be traced back  by
>> looking
>> > at the main Hub Node then seeing what sub-hub node it cam from and
>> trace it
>> > back. While this is works with watching during normal times, it does not
>> > allow to see things quickly as it was when all connected to one hub
>> node.
>> > is there a way to list all of my nodes on one screen similar to when i
>> > have all connected to one hub node to watch activity with existing
>> tools?
>> > (grouped nodes to dose not provide a good screen)
>> > If not would it be possible for me  to modify something to do this?
>> > on the simple usb tune menu command "v" provides other useful
>> information
>> > that would be nice to see for all of my nodes at once, is there anything
>> > available that does that?
>> > Thank you
>> > Chris
>> >
>> > _______________________________________________
>> >
>> > arm-allstar mailing list
>> > arm-allstar at hamvoip.org
>> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> >
>> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>>
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>
>
>