MIB/Oid for Ucopia controller ( Wifi/Wired Lan captive portal)

Hello,

Please find MIB & OID for the Ucopia Controller

http://bit.ly/2tFvQ9z
(file available for download till 25th July)

As I’m a customer from this company, I got those files/info received directly from their IT dept.

OID References:

DAA UCOPIA
Ucopia Database status
.1.3.6.1.4.1.31218.4.2.0
Ucopia Disconnection service
.1.3.6.1.4.1.31218.4.6.0
Ucopia Splash pages availability webServerService
.1.3.6.1.4.1.31218.4.1.0
Ucopia Splash pages availability portalService
.1.3.6.1.4.1.31218.4.4.0
Ucopia URL logging
.1.3.6.1.4.1.31218.4.3.0
Ucopia Web proxy
.1.3.6.1.4.1.31218.4.5.0
Ucopia concurrent users
.1.3.6.1.4.1.31218.3.1.0

Ucopia cpuTemperature
.1.3.6.1.4.1.31218.3.3.0

(high = +76.0°C, crit = +86.0°C)
Ucopia dhcpServerService
.1.3.6.1.4.1.31218.4.8.0
Ucopia diskTemperature
.1.3.6.1.4.1.31218.3.4.0
Ucopia dnsServerService
.1.3.6.1.4.1.31218.4.9.0
Ucopia highAvailabilityService
.1.3.6.1.4.1.31218.4.11.0
Ucopia ldapDirectoryService
.1.3.6.1.4.1.31218.4.12.0
Ucopia ldapReplicationManagerService
.1.3.6.1.4.1.31218.4.13.0
Ucopia syslogService
.1.3.6.1.4.1.31218.4.18.0
Ucopia usersLogService
.1.3.6.1.4.1.31218.4.19.0

Regards,

Vdbseb1983 - Sébastien

Some of those are really random, what do you even want monitoring under usersLogService?

Hello,

I tried to include it by using the tutorial on the website, but it seems a little bit difficult for me to convert the OID to the YAML file requested. (I’m not used to work with snmpwalk, etc…). I’m at easy with most of linux commands but not used to SNMP tools.

French (Belgium, Switzerland, France, etc… for some examples please see http://www.ucopia.com/en/ucopia-industries/wifi-stadiapublic-venues/ ) seems to work a lot with this captive portal.

If you could help it’ll be great :wink:

Even if I’m only a IT Technician & customer, I’ll do my best to promote LibreNMS which is honestly one of the best & easyiest monitoring tool on the market for the moment.

Regards,

vdbseb1983 - Sébastien

By the way, the main purpose is to use/analyse everything regarding users (LDAP, users, logging ).

:wink:

I’m asking really what some of those OIDs actually mean, what is value does usersLogService give, same with syslogService and others.

Hello,

Please find hereunder a sample of the values returned

For a quick explanation of what I saw with their technician:
Ucopia Database status
.1.3.6.1.4.1.31218.4.2.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the user/password database
Ucopia Disconnection service
.1.3.6.1.4.1.31218.4.6.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the auto disconnection service that kicks users out when they are not transmitting data within a certain amount of time

Ucopia Splash pages availability webServerService
.1.3.6.1.4.1.31218.4.1.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the (? apache/nginx ?) web service

Ucopia Splash pages availability portalService
.1.3.6.1.4.1.31218.4.4.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the availability of webpages created for each captive portal.

Ucopia URL logging
.1.3.6.1.4.1.31218.4.3.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the URL logging service.

Ucopia Web proxy
.1.3.6.1.4.1.31218.4.5.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the proxy service if enabled by the administrator for the users.

Ucopia concurrent users
.1.3.6.1.4.1.31218.3.1.0
——> Return a value regarding the quantity of users who are connected with the same user&password.

Ucopia cpuTemperature
.1.3.6.1.4.1.31218.3.3.0
—> returns cpu temp

Ucopia dhcpServerService
.1.3.6.1.4.1.31218.4.8.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the dhcp service on the controller

Ucopia diskTemperature
.1.3.6.1.4.1.31218.3.4.0
——> Returns the cpu temp

Ucopia dnsServerService
.1.3.6.1.4.1.31218.4.9.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the internal dns service

Ucopia highAvailabilityService
.1.3.6.1.4.1.31218.4.11.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding a H.A. environment.

Ucopia ldapDirectoryService
.1.3.6.1.4.1.31218.4.12.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the internal ldap service used for storing user & passwords

Ucopia ldapReplicationManagerService
.1.3.6.1.4.1.31218.4.13.0
—> this I don’t know what’s for but I guess it’s for checking status in a H.A. environment.

Ucopia syslogService
.1.3.6.1.4.1.31218.4.18.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding the internal syslog service of the controller.

Ucopia usersLogService
.1.3.6.1.4.1.31218.4.19.0
——> Return a status code (ok/not ok/ok but not master in ha config) regarding regarding the event log of the users (connected/disconnected/end-of-life passsword/mac addresses & user ip’s)

Hope this will help.

Regards,

vdbseb1983 - Sébastien

I got new information and access to api/faq to the “extranet” website . Please find it below:

What information can I monitor on the controller’s resources?

Last modified : 21 March 2017

UCOPIA enables you to access real-time information about the load of the controller, the CPU usage, number of processes, free RAM, number of connected users, free space on the log partition, as well as the real-time UP and DOWN bandwidth consumption in the IN and OUT interface. This information is to be found in the administration tool of your controller, in the tab “Monitoring > Controller status”. The evolution in time of some of these criteria is showed graphically in the tab “Monitoring > System”

If you want to monitor and store all these data on the controller status, instead of just seeing their real-time values or some graphs on the administration interface, you can use an external SNMP monitoring tool. Thanks to an embedded SNMP agent, UCOPIA can be supervised by an SNMP-compatible monitoring tool:

Either via SNMP traps for passive monitoring. A trap is an unsolicited SNMP message sent from UCOPIA to indicate a change in status, such as a threshold value being reached by the disk space or swap space… You can enable SNMP traps on the administration tool “Configuration > Interfaces with the controller > SNMP > Configuring SNMP alerts ».

Either via polling for active monitoring. UCOPIA then regularly sends information to the SNMP server on a service…. It is possible to monitor the evolution CPU load, temperature, number of connected users, bandwidth, disk space, etc. You can enable SNMP polling on the administration tool “Configuration > Interfaces with the controller > SNMP > SNMP agent configuration ».

UCOPIA controllers support 2 MIB :

The UCOPIA MIB, which can be downloaded from the administration interface through the menu “Configuration > Interfaces with the controllers > SNMP”

The standard MIB-2 which provides more information on the system (process, bandwidth, CPU load, RAM memory …

SNMP can only be used to monitor the controller resource.

==================================================================================

If you need more technical informations, I might try get in touch with them to see if they can give you the infos you need.

Regards,

vdbseb1983 (on3svb on github) - Sébastien