Client Monitor Limit - HMOL

  • 1
  • Question
  • Updated 1 year ago
  • Answered
Why is the Client Monitor set at 1 for HMOL? There are times when it would be helpful to have multiple going at the same time (no more than 2-4).
Photo of Bradley Chambers

Bradley Chambers, Champ

  • 302 Posts
  • 53 Reply Likes

Posted 5 years ago

  • 1
Photo of Brian Ambler

Brian Ambler

  • 245 Posts
  • 126 Reply Likes
Hi Bradley,

As I understand it, the one Client Monitor per HMOL VHM is set for load limiting on each instance but one of our HiveManager PLMs can confirm.
Photo of Praveen Raghuraman

Praveen Raghuraman

  • 55 Posts
  • 9 Reply Likes
Yes, confirming Brian's answer. We can touch base offline to better understand your use-case for multiple client sessions.
Photo of Bradley Chambers

Bradley Chambers, Champ

  • 302 Posts
  • 53 Reply Likes
Sounds good.
Photo of Jeremy Stewart

Jeremy Stewart

  • 47 Posts
  • 0 Reply Likes
Sorry to bring this post to life after being inactive for so long. Is there any reason for this limitation, and can the limitation can be removed? I'm managing 18 locations, and sometimes need to have a couple of clients on the monitor. This setup causes me more time to do my job.
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Jeremy,
We impose that limit on HMOL customers only because multiple HMOL instances share the same host hardware within our data centers, and we don't want to create what I call the "noisy neighbor" syndrome. If a different customer consumed too much CPU processing or network capability on your host you would be starved and would get angry at Aerohive. Our on-premises edition of HiveManager does not have this limitation; you own the hardware and can use it fully.

We are making changes in the underlying architecture of future versions of HiveManager so that this (and other) limitations can be removed.
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Just stumbled across this limit with HMOL 6.6r3a... Mike, is there any movement on "changes in the underlying architecture of future versions of HiveManager so that this (and other) limitations can be removed"?
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
Carsten,
Yes, but that product is called HiveManager-NG. The existing HiveManager Classic architecture is unlikely to be significantly changed. We have cosmetic changes coming that I think you will very much appreciate, but the fundamental architecture is still the same.
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Thanks Mike - yes, this makes sense.
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
We were lucky enough to have the local Aerohive SE run through the underlying architecture of HiveManager NG and how different it is to HiveManager 6 ("Classic").   Once you see how fundamentally different NG is under the hood you can see why there is minimal development of HiveManager 6 ("Classic").

There are some HiveManager 6 features that still need a workaround in NG (device classifiers in HiveManager 6 can be replaced with map classifiers in NG, for example) but the number of HiveManager 6 features not directly supported in NG (CVGs, for example) is quickly reducing and some are able to be implemented in NG - just differently.
(Edited)
Photo of Carsten Buchenau

Carsten Buchenau, Champ

  • 356 Posts
  • 117 Reply Likes
Thanks Crowdie! Yes, I fully agree, it looks like NG is finally coming together :-)

I am interested though in all the different workarounds / different ways of implementation for effected features. Probably worth to start a new topic for this :-)