Devices are the units to be monitored.
The SMC solution includes e.g.

• NGINX - a commonly used is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache. The ATC environment includes a sample websites, its IP is 172.17.02.
• SNMP server - SNMP is widely used in network management for network monitoring. SNMP exposes management data in the form of variables on the managed systems organized in a management information base (MIB) which describe the system status and configuration. These variables can then be remotely queried (and, in some circumstances, manipulated) by managing applications. In the example it is a pure SNMP server. IP 172.17.03
• Flight Data Processing System (server) - it is a web service on IP 172.17.04. This pedagogical FDPS provides simulated data on arriving and departing flights. The events happen faster than in reality in order to see changes faster.

The SMC solution includes a variety of parameters. By connecting them through drag and drop to the devices, the specific parameters are read out. The parameters include:

• NginxStatus
• SnmpParameter
• LoadAverage
• FlightData
• CpuIdle
• CpuSystem
• CpuUser
• RamUsed
• RamFree
• RamCached

When we click on the parameters (e.g. NginxStatus), we can choose different values. Request per seconds, the active connections of the server, or the number of requests that are in reading or writing state or those which are waiting.

We can for instance refresh the included example website. Consequently the requests per second in the Nginx server will increase.

The pedagogical Monitoring and Control system has additional training oriented tools, e.g. to generate some 100 or 1000 requests per second.

The parameter blocks are configurable. Countless additional parameters can be added, using the standardized Object Identifier Codes (by ITU or/and ISO).

Then we should connect the device to a parameter, e.g. CpuIdle (defining how much of the CPU is idle). And then connect it to a chart. The Gauge chart updates every few seconds. 

The line chart allows you to display the history. Several gauges can be connected to the parameters.

Different devices use different parameter types. The NGINX server for instance provides its statistics via HTTP. The SNMP server provides its data via the SNMP protocol. 

When we click on the parameters (e.g. NginxStatus), we can choose different values. Request per seconds, the active connections of the server, or the number of requests that are in reading or writing state or those which are waiting. We can for instance refresh the website. Consequently the requests per second in the Nginx server will increase:

The component “DiagramPack” is like a folder. It helps us to package / group / classify our diagrams.

It allows us to create groupings and substructures and thus make sure that the screens are always understandable and never overloaded.

This subset of the solution includes:

• training environment with typical applications and emulated data placed on a dedicated server
• Applications  including:
  
  • Radar Data Processing System
  • Website
  • Typical databases

• the students can monitor the environment and learn to run through escalation routines in case of system degradation

A physical environment represents in a simplified way a typical ATC facilities.

This subset of the laboratory shall help to gain hands-on experience in bug-discovery and fixing. It includes:

• connection to the SMC solution
• physical environment of 3 servers, applications and databases, a physical network with routers and software switches, monitoring points and emulated data. Monitoring can be made on power supply, UPS and battery, environmental factors (heating, cooling), as well as fire and security
• the teacher is able to degrade the system
  
  

The system allows to even include technical training laboratories which allow to set up training and monitoring infrastructures for 

• electronics (analog, sequential, combinatory) lab
• analog and digital communication lab
• microprocessors lab
• trouble-shooting lab