LDSmonitor - Large Display Solutions · 2019. 7. 26. · A USB cable to connect LDSmonitor and...

LDSmonitor 21/06/2018

Document version 1.30

1

LDSmonitor

User & installation manual




2

Table of contents

Table of contents ................................................................................................................................. 2

Introduction ........................................................................................................................................ 4

Product capabilities ............................................................................................................................. 4

Requirements ...................................................................................................................................... 4

Installation and configuration ............................................................................................................. 5

Connections ..................................................................................................................................... 5

Configuration................................................................................................................................... 5

Default configuration .................................................................................................................. 5

Web management ....................................................................................................................... 5

Device administration ................................................................................................................. 7

Display management ................................................................................................................... 9

Automatic recovery modes ............................................................................................................... 12

SNMP OIDs ........................................................................................................................................ 13

Is controller alive? ......................................................................................................................... 13

Is DVI connected? .......................................................................................................................... 13

Get the controller model. .............................................................................................................. 14

Are all modules accessible?........................................................................................................... 15

Is the brightness uniform? ............................................................................................................ 15

How many modules and cabinets are configured? ....................................................................... 16

Average temperature of the CPUs ................................................................................................ 17

Maximum Temperature of the CPUs ............................................................................................ 17

Average voltage of CPUs ............................................................................................................... 17

Maximum voltage of CPUs ............................................................................................................ 18

Minimum voltage of CPUs ............................................................................................................. 18

Nagios setup ...................................................................................................................................... 34

Hostgroup definition ..................................................................................................................... 35

Definition of monitoring devices ................................................................................................... 40

Technical specs .................................................................................................................................. 40



3

Firewall configuration ....................................................................................................................... 40

Reset to factory defaults without network connection .................................................................... 41



4

Introduction LDSmonitor is a monitoring product, that provides SNMP and web based monitoring for Novastar

Controllers Series MSD300, MCTRL300, MCTRL500, MSD600, MCTRL600 and MCTRL660. SNMP

protocol implementation will allow you to monitor from any SNMP monitor, for example Nagios, to

query the state of your displays. If you do not have Nagios, you can connect to the web interface

and query the state manually.

Additionally, you can change the brightness of the display from the web interface.

Product capabilities

LDSmonitor will allow you to query through SNMP the following parameters:

Is the Controller alive?

What is the model of the controller connected?

What is the configuration of ports and CPUs in each port applied?

Is the DVI correctly connected?

Are all CPUs of the display communicating correctly?

Does the display have a uniform brightness?

Does the display have a uniform brightness? And correct it automatically.

Average and maximum temperature of CPUs

Average, maximum and minimum voltage of CPUs.

In the web interface, you can also:

Set the desired brightness (and the color balance) to a module or to a complete display.

Set the brightness of the display based on a schedule table.

Requirements

To monitor remotely a display you will need:

LDSmonitor product.

A power supply for LDSmonitor (included in the package) that provides 5V and 2A.

A USB cable to connect LDSmonitor and Novastar controller (Novastar provides it).

A network connection. If you are outdoors, you will need a 3G (or similar) modem with a

fixed IP or the configuration of a dynamic DNS managed by the 3G modem.

A Nagios installation (www.nagios.com). Important: Nagios is an opens source solution and

is not a part of LDSmonitor.

http://www.nagios.com/



5

If you are planning to use the brightness scheduler, LDSmonitor must have access to a NTPd

server to synchronize with the actual time.

Installation and configuration

You will have to follow two steps, the physical connection of the systems, and the configuration of

LDSmonitor. This process will take you five minutes, approximately.

Connections The diagram on the right, shows you how to interconnect the systems. The only important issue is

to use the upper USB port to connect LDSmonitor to Novastar Controller, if you user the lower port

the system will not detect the controller.

Plug, check, and power on.

Configuration

Default configuration By default, the factory settings are:

Parameter Value

IP of the device 192.168.1.91

Netmask 255.255.255.0

Gateway 192.168.1.1

Nameserver 8.8.8.8

Administrator username admin

Administrator password 1234

Speed of protocol 1000000 bauds (set for MCTRL660)

Modules in port 1 0

Modules in port 2 0

Modules in port 3 0

Modules in port 4 0

Auto recover Disabled

First time server 0.europe.pool.ntp.org

Secondary time server time.nist.gov

Time zone GMT-2

Web management

To access the web management utility follow the next steps:



6

1. Connect your computer to the same network of LDSmonitor,

2. You can check that “they are seeing”, by making a ping to the LDSmonitor IP

3. Open your browser, and enter the IP of device. In this page, you can directly click in the

“Configure” button. In this moment you will be required to enter a user and password. By

default it is admin and 1234, but shortly you will see how to change it.

The web management interface is divided two sections, the “device administration” and the “display

management”.

The “Display management” configuration groups the following options:

Display configuration. How is the display configured, including the controller detection, and

the number of cabinets in each port, the automatic recovery mode, and the time

management settings.

Display status. This page will show you the active configuration, and the state of the DVI,

CPUs and brightness.

Brightness control. This page will inform you about the brightness of the CPU taken as a

reference (the first cpu in the first port), and will allow you to change the brightness (and

the value of each of its components) of an individual cabinet or to all the display. In this

page you can indicate if the display is working in manual mode or in scheduled mode.

The “Device administration” groups the following configuration options:

Device registration. Registration of the LDSmonitor unit.

Change the LAN settings (IP, mask, gateway and DNS). After applying any change, you have

to reboot the device so that the changes are effective.

Change the password of the administrator.

Reset to factory defaults.



7

Reboot the device.

This options are very straight and, probably you will not need any further assistance.

Device administration

IP Configuration

In this section you will be able to configure the LAN configuration of the device

You can change any configuration parameter, and when you think that the configuration is how you

want, press Apply button. The configuration will be saved and after rebooting the device, the new

parameters will apply.

Password change for the administration site.

To modify the default password, which is 1234, go to the “Change password” menu. You will have

to enter twice the password, and after rebooting the device it will be applied.



8

Reset to system defaults

The reset to system defaults can be done through two different ways, in the web management

system, you have to go to the Reset menu:

And press “Reset to default values”, and confirm. After resetting, please reboot the device.

The second way for resetting to default values is done through the USB. Follow these steps:

1. Take a USB memory stick, clean it completely, and create a file named “reset”.

2. Insert it in the top USB port.



9

3. Restart the system and wait about 30 seconds.

4. Then the default values will be recovered, and you will be able to access the device using

the IP address 192.168.1.91

Display management

Display config

In this menu you will be able to configure the display and controller that the system has to monitor.

Follow these steps:

1. Install your display, with your controller, and when the display is properly configured and

running, proceed to the configuration. The controller and the display has to be turned on to

be able to auto configure the system.

2. Open the display configuration menu. You will see a page similar to this one:

3. Press the “Auto detect” button, and the page will display the information of your display

(what controller you have, and the modules connected to each RJ port of the controller).



10

4. If you want, you can set an auto repair option.

5. Press Save.

You may also want to change the primary and secondary time servers (ntpd servers), the timezone

or set the time manually. To work with the time set manually you have to remove the time servers,

if you do not, each 5 minutes it will try to synchronize with them and will change your time. Please

note that if you power off the LDSmonitor the time will be reset to 0:00 if you do not have access to

a ntpd server.

The ntpd servers are a freely available service in internet, so if you have Internet access you have

them.

Display status

When you open the display status page, you will be able to see:

1. The model of your controller.

2. The number of cabinets that are

configured.

3. The state of the DVI connection

4. The operation status of the cabinets

5. The brightness uniformity status

6. The average and maximum temperature

of the cabinets.

7. The minimum, maximum and average

voltage of the cabinets.

8. The measure read from the light sensor

If is there any error, it will be displayed as shown in the second image:

DVI error

Cabinets that are not

connected

Cabinets with non

uniform brightness



11

Brightness control

Manual mode

With this mode you, you can manage the brightness of the display, its global brightness and the

individual brightness of each CPU independently.

Scheduled Mode

When selecting the scheduled

mode, you can indicate the

brightness value of the display

for each 30 minutes interval.

LDSmonitor, each minute, will

check that all the display is in

the desired brightness for the

time it is.

Sensor Mode

When LDSmonitor is configured

to work with the sensor mode,

the display brightness will be

selected depending on the

value read by the sensor, and

the table seen in the left page.

The administrator task is to

select the desired brightness

depending on the sensor reads,

but it may be different in

different environments. Please

note that the values shown in

this figure are just an example.



12

Automatic recovery modes

As you will see in the configuration page, you have two different autorecovery. You can select none

or one, but not both.

The mode “Auto repair brightness each minute” indicates that LDSmonitor, each minute will check

if the brightness is uniform, and if it is not, it will make it uniform. In this operation mode you do not

need to be connected to the network, it’s a device independent function.

The mode “Auto repair brightness when query” implies that the recovery will be done when the

monitoring system queries about its brightness uniformity. This will imply that the monitoring

system will be able to log when a correction has been made.



13

SNMP OIDs

Is controller alive?

Query Is the controller alive

OID: NET-SNMP-EXTEND-MIB::nsExtendResult."isAlive" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.4.7.105.115.65.108.105.118.101 Description Query if the controller is alive and answering requests. Returns 0 – Alive, OK.

2 – The USB cable is not connected. Please check the connection. 3 – USB connected but not responding -> The controller USB is plugged but not powered

Query Is the controller alive detail

OID: NET-SNMP-EXTEND-MIB:: nsExtendOutputFull."isAliveOutput" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.13.105.115.65.108.105.118.101.79.117.116.112.117.116 Description Query if the controller is alive and answering requests, and returns the text detail of the operation Returns SNMP OK - Controller type: CONTROLLER_ID

SNMP OK - [ErrCode 2] Unable to open connection to Nova. Check connection. SNMP OK - [ErrCode 3] Nova is connected but not responding. Check power.

Is DVI connected?

Query Test the DVI connection

OID: NET-SNMP-EXTEND-MIB::nsExtendResult."testDVI" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.4.7.116.101.115.116.68.86.73 Description Checks the DVI signal, you can see if the cable is disconnected or if the content provider is turned off. Returns 0 – Connection OK.



14

1 – DVI is not connected. 2 – The USB cable is not connected. Please check the connection. 3 – USB connected but not responding -> The controller USB is plugged but not powered

Query Test the DVI connection detail

OID: NET-SNMP-EXTEND-MIB:: nsExtendOutputFull."testDVIOutput" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.13.116.101.115.116.68.86.73.79.117.116.112.117.116 Description Checks the DVI signal, you can see if the cable is disconnected or if the content provider is turned off., and returns the text detail of the

operation Returns SNMP OK - Controller type: CONTROLLER_ID

SNMP OK – IsDVIConnected: 1 SNMP OK - [ErrCode 2] Unable to open connection to Nova. Check connection. SNMP OK - [ErrCode 3] Nova is connected but not responding. Check power.

Get the controller model.

Query Get the controller model

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."getControllerModel" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.18.103.101.116.67.111.110.116.114.111.108.108.101.114.77.111.100.101.108 Description Informs you about the controller model that is connected to the LDSmonitor Returns 0 – SNMP OK - Controller type: <MODEL IDENTIFIER>.

1 – DVI is not connected. 2 – The USB cable is not connected. Please check the connection. 3 – USB connected but not responding -> The controller USB is plugged but not powered



15

Are all modules accessible?

Query Queries about the accessibility of the configured modules of the system

OID: NET-SNMP-EXTEND-MIB::nsExtendResult."getCabinetsStatus" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.4.17.103.101.116.67.97.98.105.110.101.116.115.83.116.97.116.117.115 Description Checks the connectivity, one by one, with all the modules that are configured in the system, in each port. Returns 0 – All cabines accessible. OK.

1 – Some cabinets are not accessible. 2 – The USB cable is not connected. Please check the connection. 3 – USB connected but not responding -> The controller USB is plugged but not powered

Query Queries about the accessibility of the configured modules of the system detail

OID: NET-SNMP-EXTEND-MIB:: nsExtendOutputFull."getCabinetsStatusOutput" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.23.103.101.116.67.97.98.105.110.101.116.115.83.116.97.116.117.115.79.117.116.112.117.116 Description Shows the detail of the cabinet connectivity. If is there any problem is will inform you the cabinets that have problem in the following notation

[RJ output, cabinet number] Returns SNMP OK – All cabinets active.

SNMP OK - Cabinets with problems: [1, 1] [1, 2] [1, 3] [1, 4] [1, 5] [1, 6] [1, 7] [1, 8] (Example) SNMP OK - [ErrCode 2] Unable to open connection to Nova. Check connection. SNMP OK - [ErrCode 3] Nova is connected but not responding. Check power.

Is the brightness uniform?

Query Is the brightness of the display uniform?

OID: NET-SNMP-EXTEND-MIB::nsExtendResult."isBrightnessUniform" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.4.19.105.115.66.114.105.103.104.116.110.101.115.115.85.110.105.102.111.114.109 Description Compares the brightness of all the cabinets and checks if is it the same anywhere. The reference value, is the first cabinet connected.



16

Returns 0 – It is uniform, OK. 1 – It is not uniform. See details. 2 – The USB cable is not connected. Please check the connection. 3 – USB connected but not responding -> The controller USB is plugged but not powered

Query Is the brightness of the display uniform? Detail information.

OID: NET-SNMP-EXTEND-MIB:: nsExtendOutputFull."isBrightnessUniform" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.25.105.115.66.114.105.103.104.116.110.101.115.115.85.110.105.102.111.114.109.79.117.116.112.117.116 Description Compares the brightness of all the cabinets and checks if is it the same anywhere. The return is the detail about the status. Returns SNMP OK - Brightness is uniform at 15.00 %

SNMP OK – Brightness reference 15.00 % - Cabinets with differences [1, 6, 20.00%] [1, 7, 23.00%] -> Indicates the reference (the first module brightness), and which modules are not correct, and its read value. SNMP OK - [ErrCode 2] Unable to open connection to Nova. Check connection. SNMP OK - [ErrCode 3] Nova is connected but not responding. Check power.

How many modules and cabinets are configured?

Query How is set the configuration in LDSmonitor

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."displayConfiguration" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.20.100.105.115.112.108.97.121.67.111.110.102.105.103.117.114.97.116.105.111.110 Description Retrieves the configuration information that is set in LDSmonitor. You will see how many modules are defined in each RJ output. Returns 0 – SNMP OK - Port 0: 8 - Port 1: 0 - Port 2: 0 - Port 3: 0 , OK. (Example values)

2 – The USB cable is not connected. Please check the connection. 3 – USB connected but not responding -> The controller USB is plugged but not powered



17

Average temperature of the CPUs Query How is set the configuration in LDSmonitor

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."mediumTemperature" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.17.109.101.100.105.117.109.84.101.109.112.101.114.97.116.117.114.101 Description Retrieves the average temperature of the CPUs. Non accessible CPUs are not included in the average computation. Returns Temperature in ºC

1000 ºC means invalid temperature (when all cpus are inaccessible , for example)

Maximum Temperature of the CPUs Query How is set the configuration in LDSmonitor

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."maximumTemperature" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.18.109.97.120.105.109.117.109.84.101.109.112.101.114.97.116.117.114.101 Description Retrieves the maximum temperature measured when reading CPU temperature information. Non accessible CPUs are not included in the

average computation. Returns Temperature in ºC

1000 ºC means invalid temperature (when all cpus are inaccessible , for example)

Average voltage of CPUs Query How is set the configuration in LDSmonitor

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."mediumVoltage" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.13.109.101.100.105.117.109.86.111.108.116.97.103.101 Description Retrieves the average voltage measured when reading CPU voltage information. Non accessible CPUs are not included in the average

computation. Returns Volts with two decimals.

100 V means invalid voltage (when all cpus are inaccessible , for example)



18

Maximum voltage of CPUs Query How is set the configuration in LDSmonitor

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."maximumVoltage" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.14.109.97.120.105.109.117.109.86.111.108.116.97.103.101 Description Retrieves the maximum voltage measured when reading CPU voltage information. Non accessible CPUs are not included in the average



Minimum voltage of CPUs Query How is set the configuration in LDSmonitor

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."minimumVoltage" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.14.109.105.110.105.109.117.109.86.111.108.116.97.103.101 Description Retrieves the minimum voltage measured when reading CPU voltage information. Non accessible CPUs are not included in the average





19

Query Is light sensor enabled

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull." isLightSensorEnabled" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.20.105.115.76.105.103.104.116.83.101.110.115.111.114.69.110.97.98.108.101.100 Description Query if the controller can access to the light sensor Returns “Enabled” or “Disabled”

Query Is light sensor working

OID: NET-SNMP-EXTEND-MIB::nsExtendResult." isLightSensorWorking" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.4.20.105.115.76.105.103.104.116.83.101.110.115.111.114.87.111.114.107.105.110.103 Description Query if the controller can access to the light sensor Returns 0 – The access ir correct, OK.

2 – The USB cable is not connected. Please check the connection. 3 – USB connected but not responding -> The controller USB is plugged but not powered 5 – There is no response from the light sensor, probably it is not installed.

Query Read a light measure

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."readLightSensorMeasure" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.22.114.101.97.100.76.105.103.104.116.83.101.110.115.111.114.77.101.97.115.117.114.101 Description Read the measure of light (in LUX) of the light sensor. Please note that to be sure that the measure is correct, you must check the OID

‘isLightSensorWorking’ Returns The measure in lux (integer value)

Query System uptime

OID: nOID: .1.3.6.1.2.1.25.1.1.0 Description Returns the time since the last reboot Returns The information is in tics (Example: “Timeticks: (19919) 0:03:19.19”)



20

Query What time is it in LDSmonitor internal clock

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."whatTimeIsIt" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.12.119.104.97.116.84.105.109.101.73.115.73.116 Description Returns the time of LDSmonitor, so that you can manage if ntpd has offered correctly the time. Returns The information is in text

Query Is ColorMatrixTechnology enabled?

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."isCMTActive" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.11.105.115.67.77.84.65.99.116.105.118.101 Description Informs you about the state of the ColorMatrixTechnology, if it is enabled or not. Returns 0 => not active, 1 => Active.

Query Get Humidity for sensor in MON300 number 1

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."humidity_0" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.10.104.117.109.105.100.105.116.121.95.48 Description Returns the humidity in % of the value read by the sensor Returns -1 no data. Else, the value





21





Query Voltage measured by MON300 cards. Voltage point number 2

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."voltagePoint_1" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.14.118.111.108.116.97.103.101.80.111.105.110.116.95.49 Description Returns the voltage in volts measured Returns -1 no data. Else, the value


OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."voltagePoint_2" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.14.118.111.108.116.97.103.101.80.111.105.110.116.95.50





22

Description Returns the voltage in volts measured Returns -1 no data. Else, the value











23








OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."voltagePoint_10" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.15.118.111.108.116.97.103.101.80.111.105.110.116.95.49.48 Description Returns the voltage in volts measured Returns -1 no data. Else, the value


OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."voltagePoint_11" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.15.118.111.108.116.97.103.101.80.111.105.110.116.95.49.49



24

Description Returns the voltage in volts measured Returns -1 no data. Else, the value











25









Query Fan speed measured by MON300 cards. Fan number 1

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."fan_0" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.5.102.97.110.95.48



26

Description Returns the speed of the fan in RPM Returns -1 no data. Else, the value


OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."fan_1" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.5.102.97.110.95.49 Description Returns the speed of the fan in RPM Returns -1 no data. Else, the value









27










OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."fan_9" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.5.102.97.110.95.57



28

Description Returns the speed of the fan in RPM Returns -1 no data. Else, the value

Query Is the door open?. Door number 1

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."door_0" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.6.100.111.111.114.95.48 Description Returns the 1 if the door is open, 0 if closed Returns Returns the 1 if the door is open, 0 if closed. -1 if not configured.









29










OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."door_8" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.6.100.111.111.114.95.56



30

Description Returns the 1 if the door is open, 0 if closed Returns Returns the 1 if the door is open, 0 if closed. -1 if not configured.



Query Is smoke detected on monitoring card 1

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."smoke_0" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.4.7.115.109.111.107.101.95.48 Description Returns the 1 if smoke is detected, 0 if not Returns Returns the 1 if smoke is detected, 0 if not. -1 if card is not available







31





Query Get temperature measured on monitoring card 1

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."tempMonCard_0" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.13.116.101.109.112.77.111.110.67.97.114.100.95.48 Description Returns the temperature in ºC Returns Returns the temperature, -255 if the read is not valid, -1 if there is no card detected




OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull."tempMonCard_2" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.13.116.101.109.112.77.111.110.67.97.114.100.95.50



32

Description Returns the temperature in ºC Returns Returns the temperature, -255 if the read is not valid, -1 if there is no card detected





Query Check redundant line.

OID: NET-SNMP-EXTEND-MIB::nsExtendOutputFull." checkRedundantLine" nOID: .1.3.6.1.4.1.8072.1.3.2.3.1.2.18.99.104.101.99.107.82.101.100.117.110.100.97.110.116.76.105.110.101 Description Checks if the configured redundant line if operative. Have to access all cabinets Returns “OK”, or an error message



33



34

Nagios setup

Nagios is an Open Source application to monitor your SNMP capable devices, from printers to LED

displays. To obtain Nagios you can go to www.nagios.com and select the type of product you want:

free or licensed.

In this point, a knowledge of how to configure a Nagios system is supposed and it is beyond of the

scope of this user manual.

In this chapter we will suggest one possible configuration, but it is up to you to apply the

configuration you think is better. Our proposed configuration will be composed by:

A standard hostgroup definition.

A definition of a host for each display you are monitoring.

Notes about the listing:

1. The idea of the following pages of the manual is that they can be copied to your hostsgroup

definition file, and work.

2. Please note that you have to modify the warning and critical level of the temperature and

voltage to adapt it to your needs.

3. You can introduce a prefix to the service names so that they can appear together in an

alphabetic sort.

http://www.nagios.com/



35

Hostgroup definition

The following listing shows the suggested configuration file for the hostgroup.

define hostgroup { hostgroup_name LDSmonitor alias LDSmonitor } # Define a service to check HTTP on the local machine. # Disable notifications for this service by default, as not all users may have HTTP enabled. define service{ use local-service ; Name of service template to use hostgroup_name LDSmonitor service_description HTTP check_command check_http notifications_enabled 0 } # Define a service to check SSH on the local machine. # Disable notifications for this service by default, as not all users may have SSH enabled. define service{ use local-service ; Name of service template to use hostgroup_name LDSmonitor service_description SSH check_command check_ssh notifications_enabled 0 } # Define a service to "ping" the local machine define service{ use local-service ; Name of service template to use hostgroup_name LDSmonitor



36

service_description PING check_command check_ping!100.0,20%!500.0,60% } define service { use local-service hostgroup_name LDSmonitor normal_check_interval 5 servicegroups DVIs service_description DVICONNECTED

check_command check_snmp! -t 10 -c0 -o '.1.3.6.1.4.1.8072.1.3.2.3.1.4.7.116.101.115.116.68.86.73' -C public notifications_enabled 0 } define service { use local-service hostgroup_name LDSmonitor service_description DVICONNECTED_DETAIL normal_check_interval 5

check_command check_snmp! -o '.1.3.6.1.4.1.8072.1.3.2.3.1.2.13.116.101.115.116.68.86.73.79.117.116.112.117.116' -C public notifications_enabled 0 }

define service { use local-service hostgroup_name LDSmonitor service_description ISALIVE normal_check_interval 5

check_command check_snmp! -c0 -o '.1.3.6.1.4.1.8072.1.3.2.3.1.4.7.105.115.65.108.105.118.101' -C public notifications_enabled 0 } define service { use local-service hostgroup_name LDSmonitor service_description ISALIVE_DETAIL normal_check_interval 5

check_command check_snmp! -o '.1.3.6.1.4.1.8072.1.3.2.3.1.2.13.105.115.65.108.105.118.101.79.117.116.112.117.116' -C public notifications_enabled 0



37

} define service { use local-service hostgroup_name LDSmonitor service_description MODEL normal_check_interval 5 check_command check_snmp! -o

'.1.3.6.1.4.1.8072.1.3.2.3.1.2.18.103.101.116.67.111.110.116.114.111.108.108.101.114.77.111.100.101.108' -C public notifications_enabled 0 }

define service { use local-service hostgroup_name LDSmonitor service_description CABINETS_ACCESSIBLE servicegroups CABINETS_ACTIVE normal_check_interval 5 check_command check_snmp! -c0 -o

'.1.3.6.1.4.1.8072.1.3.2.3.1.4.17.103.101.116.67.97.98.105.110.101.116.115.83.116.97.116.117.115' -C public notifications_enabled 0 } define service { use local-service hostgroup_name LDSmonitor service_description CABINETS_ACCESSIBLE_DETAIL normal_check_interval 5 check_command check_snmp! -o

'.1.3.6.1.4.1.8072.1.3.2.3.1.2.23.103.101.116.67.97.98.105.110.101.116.115.83.116.97.116.117.115.79.117.116.112.117.116' -C public notifications_enabled 0 } define service { use local-service hostgroup_name LDSmonitor servicegroups BRIGHTNESS_UNIFORM service_description UNIFORM_BRIGHTNESS normal_check_interval 5



38

check_command check_snmp! -c0 -o

'.1.3.6.1.4.1.8072.1.3.2.3.1.4.19.105.115.66.114.105.103.104.116.110.101.115.115.85.110.105.102.111.114.109' -C public } define service { use local-service hostgroup_name LDSmonitor service_description UNIFORM_BRIGHTNESS_DETAIL normal_check_interval 5 check_command check_snmp! -o

'.1.3.6.1.4.1.8072.1.3.2.3.1.2.25.105.115.66.114.105.103.104.116.110.101.115.115.85.110.105.102.111.114.109.79.117.116.112.117.116' -C public } define service { use local-service hostgroup_name LDSmonitor service_description DISPLAY_CONFIGURATION normal_check_interval 5 check_command check_snmp! -o

'.1.3.6.1.4.1.8072.1.3.2.3.1.2.20.100.105.115.112.108.97.121.67.111.110.102.105.103.117.114.97.116.105.111.110' -C public } define service { use local-service hostgroup_name LDSmonitor service_description TEMPERATURE AVG normal_check_interval 5 check_command check_snmp! -w45 -c50 -o '.1.3.6.1.4.1.8072.1.3.2.3.1.2.17.109.101.100.105.117.109.84.101.109.112.101.114.97.116.117.114.101' -C public } define service { use local-service hostgroup_name LDSmonitor service_description TEMPERATURE MAX normal_check_interval 5 check_command check_snmp! -w45.00 -c50.00 -o '.1.3.6.1.4.1.8072.1.3.2.3.1.2.18.109.97.120.105.109.117.109.84.101.109.112.101.114.97.116.117.114.101' -C public }

define service {



39

use local-service hostgroup_name LDSmonitor service_description VOLTAGE AVG normal_check_interval 5 check_command check_snmp! -w4.60 -c4.70 -o '.1.3.6.1.4.1.8072.1.3.2.3.1.2.13.109.101.100.105.117.109.86.111.108.116.97.103.101' -C public } define service { use local-service hostgroup_name LDSmonitor service_description VOLTAGE MAX normal_check_interval 5 check_command check_snmp! -w4.60 -c4.70 -o '.1.3.6.1.4.1.8072.1.3.2.3.1.2.14.109.97.120.105.109.117.109.86.111.108.116.97.103.101' -C public } define service { use local-service hostgroup_name LDSmonitor service_description VOLTAGE MIN normal_check_interval 5 check_command check_snmp! -o '.1.3.6.1.4.1.8072.1.3.2.3.1.2.14.109.105.110.105.109.117.109.86.111.108.116.97.103.101' -C public }



40

Definition of monitoring devices

You have to define a host for each of your monitoring devices.

define host{ use linux-server host_name orange_box ; Here place the name you want. alias OrangeBox LDSmonitor address 192.168.1.93 ; IP address of the device hostgroups LDSmonitor }

Technical specs

Input voltage 5 V

Input current 2 A

CPU Operting temperature -40º C – 85º C

Monitoring protocols SNMP

Configuration protocol HTTP

Network connection RJ45

Usable USB ports 1 (upper)

Network ports 80, 22, 161(udp)

Firewall configuration

If you are installing the system behind a firewall, you should allow the firewall to allow the traffic

through some ports, so that the monitoring system can ask LDSmonitor for the status of the display.

The system uses the following ports:

- 80 (HTTP) for configuration or accessing the web interface.

- 22 (SSH) for possible maintenance operations

- UDP/161 for SNMP queries.

If you have more than one LDSmonitor behind one firewall, you will have to map different input

ports in the firewall to the indicated destination ports in the LDSmonitor device.



41

Reset to factory defaults without network connection

If you are not able to connect to LDSmonitor through the network, and you have to return to the

factory defaults, you have to follow the next steps:

1. Get a USP pen drive, and format it.

2. Create a file, that can be blank or with any content, and rename it to ‘reset’ (without

extension, just ‘reset’)

3. Plug the USB pen drive in the upper USB port of LDSmonitor.

4. Take the power off, and 5 seconds later, plug it again.

5. In 30 seconds, you will be able to connect to LDSmonitor using the original IP: 192.168.1.91

From this point you can configure LDSmonitor as you want.

LDSmonitor - Large Display Solutions · 2019. 7. 26. · A USB cable to connect LDSmonitor and...

Documents

Transcript of LDSmonitor - Large Display Solutions · 2019. 7. 26. · A USB cable to connect LDSmonitor and...