Peplink Granular Reporting


#1

Hello,

We have approximately 500 Peplink controllers currently deployed and would like to move almost 300 additional sites to Peplink controllers. However, the inControl reporting features are lacking in what we dial into for reporting as they only show a total grouping of users. We have certain statically set servers on a separate sub-net that we would like to have excluded from reporting. We do not want to have a server as a top client when we are trying to show how much data our guest users have passed through.

In addition, we have some controller functionality at these other sites we would like to migrate over that has built-in ICMP monitoring directly from the existing controller. Since we do not have a stand-alone box that does this, and was included with the current controller, we cannot use Peplinks at these many sites. If there was a way to have even simple ICMP monitoring by IP for server/switching status we could easily migrate these sites to Peplinks. These specific sites are very large existing infrastructure sites, and we like the large availability of reporting features the Peplink controllers, as well as inControl, have and would like to make use of these features without forgoing or existing site reporting.

Does Peplink have any plans to bolster their reporting features with more granular settings? And do you have plans to make use of features for IP monitoring of servers by ICMP?

Thanks


#2

Hello @m-son-neteng,
We had a similar situation for a client here in Australia, we resolved it by splitting apart the devices into lots of specially created groups, allowing for segregation of the groups and also restricting access to the groups from certain activities.
This has now been running successfully like this for over six months, and although it took some effort to do, it is now working very well and has given the client the segregated reporting and better controlled access

If you need help in this, there are several active forum members here, it may be worth while engaging one of them in your local area (or ask Peplink for a recommendation).
Happy to Help,
Marcus :slight_smile:


#3

@m-son-neteng Right now our InControl2 reporting feature aren’t able to filter results based on clients’ subnet. Let me feedback to our IC2 team on this.

Does Peplink have any plans to bolster their reporting features with more granular settings?

Of course. we’ve been constantly updating our IC2 with new features. If you’re logged on to our IC2 now, there should be a small Feedback panel on the right of your screen. Please feel free to use that send us with all your feedbacks on how we can improve our IC2’s user experience.

[Updated] At the moment our InControl2 are more meant for managing our products. Depending on criterias you want to achieve with your network monitoring system I can further recommend on how you can do it, or whether you need a third party software for that. :wink:


#5

@Kv_Chen
Thanks for the reply. We would like to get our 300 clients migrated over to peplink so we would appreciate any suggestions on how to make this work with Peplink controllers.

I understand the requirements for only providing the services to peplink products, so if the exclusion of subnets/vlans from the reporting would give us tons of added accuracy in the client bandwidth reports. As to the other devices, if you have any suggestions on equipment monitoring behind NAT that you feel would co-inside with the peplink controller back-end, we are all ears.

Thanks


#6

In replying your post on Mar 11, you’re talking about two topics:

  1. To exclude some clients from the reports -
    I’d suggest you to use our IC2 API to retrieve the clients report and generate your own one. You report could exclude those servers from the clients.

  2. Monitoring client devices in IC2 -
    Our routers & APs currently treat your client devices as “clients”. I’d suggest you, again, to regular make API call to IC2 to retrieve a group’s client list. You could monitor if any clients disappeared. A client disappeared means the client becomes offline. However, please note that ethernet clients that didn’t contact the router for more than 2 mins would be treated as offline. So your servers would have to contact the router, say, every minute. Pinging the router could do the job. It will ensure the servers to be appeared as online on the client list. Hope this helps.