SNMP Integration

SW Installation Guide

The information contained in this document is the property of DAMM Cellular Systems A/S. This document
is subject to copyright and may not be published or reproduced, in whole or in part, without the written
permission of DAMM Cellular Systems A/S. Specifications subject to change without notice.

DAMM Cellular Systems A/S

Møllegade 68
6400 Sønderborg
Denmark
www.dammcellular.com
Table of contents

1 INTRODUCTION 3

1.1 SNMP IMPLEMENTATION 3

1.2 SNMP MODES 3

2 SNMP INSTALLATION 5

2.1 SNMP WINDOWS 10 INSTALLATION (BUILD 1803 AND LATER) 6

2.2 SNMP WINDOWS 201X SERVER INSTALLATION 7

3 SNMP MIB TREE 11

3.1 ALARMS STATES AND CHANGES IN MIB TREE 12

3.2 MIB TABLE VALUES 14

REFERENCES 16

AN-SNMP V1.0 2023.11.12 Page 2 of 16

1 Introduction
DAMM TetraFlex® system offers SNMP integration feature. SNMP is an application-layer protocol that
proved to be an excellent and simple solution, widely used as a common mechanism for monitoring
different single and multi-vendor IP based systems. Typically, it is implemented using a UDP protocol, it is a
connectionless protocol (similar to TCP), but without error-checking and recovery services, as these are not
required. Instead, UDP continuously sends datagrams to the recipient whether they receive them or not.

This document gives an overview of how SNMP is implemented in the TetraFlex system, but also a step-by-
step procedure on how to set it up on the node side. A description of status variables is also provided along
with examples of how status changes are presented.

1.1 SNMP implementation

Any node in the DAMM TetraFlex network can act as an SNMP gateway, as long as the NC service is
running. The SNMP gateway uses Windows' own SNMP service and UDP as a transport protocol, with fixed
port 161. It supports SNMP v2c and only the polling method for data collection is supported, traps are not
generated by the TetraFlex system in accordance with recommendations found in the RFC1157.

To utilise the implemented SNMP feature, an SNMP Management Application is needed. The management
application gains access to the TetraFlex network status through “SNMP Gateway” node via the WAN/DMZ
connection.

The SNMP gateway must have an SNMP extension agent installed. NC software is responsible for updating
all node status variables, whilst the SNMP agent will service the SNMP requests.

1.2 SNMP modes

DAMM TetraFlex system offers two modes for SNMP utilisation:

1. Report local NC only – each node will only update its own status variables

AN-SNMP V1.0 2023.11.12 Page 3 of 16

 2. Report all NC's – SNMP gateway node will update status variables for all nodes.

These two available options open a wide variety of configuration possibilities that could be implemented
and used in real life systems. Normally, one node is set as an SNMP GW node, which is also set as “Report
all NC’s”. By doing so, the SNMP GW node receives statuses from all nodes and will update status variables
for each, the SNMP Management Application uses single MIB file and accesses single DMZ IP addresses to
pool statuses of all nodes in the network. As this solution has a single point of failure if SNMP GW goes
down, redundancy can be achieved by having two SNMP gateways running in parallel. In such case, the
SNMP management application shall always poll from an active gateway.

It is also important to emphasise that configuring multiple nodes (or all) as SNMP gateways wouldn’t cause
excessive traffic in TetraFlex network, even if all nodes are set to report all NCs statuses. Because of the
distributed architecture of the TetraFlex network, nodes exchange statuses among themselves in normal
operation, and by enabling SNMP these updates are then just stored, but no additional signaling or
exchange of messages is required for that purpose in the INT network, it is only pooling on the DMZ side
that creates additional traffic, but not an excessive amount and not in the internal Network.

Note that an SNMP gateway will only update the status variable from nodes. For LogServers, SNMP has to
be enabled at the LogServers.

Also note that the 2nd mode is the recommended implementation. All network changes or extensions are
instantly added to the SNMP information and there is no need to change the clients SNMP Management
Application configuration at any time.

AN-SNMP V1.0 2023.11.12 Page 4 of 16

2 SNMP installation
The SNMP agent software is by default located in C:\TetraFlex\SNMP. It can also be downloaded from the
software download section on the DAMM Extranet at www.dammcellular.com, this can be done in case the
above folder is missing.

The SNMP agent packet consists of:

SNMPAgent.dll This file is the actual SNMP extension agent. It works in correlation
with the Windows SNMP service. This extension agent is responsable
SNMPAgent64.dll* for servicing SNMP requests.
A script file, which will:
SNMP_install.vbs
• Stop the Windows SNMP Service.
SNMP_Install64.vbs* • Copy SNMPAgent.dll to SNMPAgent_.dll
• Import registry settings required to install SNMPAgent_.dll.
• Start Windows SNMP Service.
DAMM-GLOBALMIB.mib Damm MIB tree
*) 64-bit version - If installing on a 64-bit Windows version this file must be used instead of the 32-bit
version.

To install the SNMP agent on a SB or BS provided by DAMM, complete the following steps:

1. Check if SNMPAgent.dll and SNMP_install.vbs files are located in C:\TetraFlex\SNMP folder at the
SNMP gateway node. If these files are missing, copy them from another node or download
appropriate software release and copy files from release bundle.
2. Check if DAMM-GLOBAL-MIB.mib file is also located in the same C:\TetraFlex\SNMP folder. This
MIB file is used by the SNMP Management Application, thus must be copied from this folder to the
PC where application management application is installed.
3. Run SNMP_install.vbs on the node to install the SNMP extension dll and registry settings, make
sure to select option Run as administrator.
4. Ensure that the NC service is running.
5. Select SNMP mode for a node either by running OM command S71/SNMP/A or from Network
Management application – NC List window, navigate to Config tab and then to SNMP column where
SNMP mode can be selected by double clicking on a related cell.
6. For activating the SNMP agent on a LogServer, ignore steps 4 and 5 above and select “Enable
SNMP” in the “LogServer Config” tab of the LogServerTray

To validate installation, run Windows Services and scroll down to SNMP service to check if the installation
process has succeeded in starting this service.

AN-SNMP V1.0 2023.11.12 Page 5 of 16

If the DAMM SNMP agent is to be installed on a PC or a server instead of SB or BS, the agent has to be
installed manually, depending on OS, specific steps are required and those are listed down.

2.1 SNMP Windows 10 Installation (Build 1803 and later)

1. To install the SNMP agent on a Windows 10 PC, complete the following steps: Make sure the
Windows SNMP Service is installed on the PC. If it isn’t, it should be installed by opening an
elevated powershell console, and run the following command:

Add-WindowsCapability -Online -Name "SNMP.Client~~~~0.0.1.0"

2. Install a NC node on the PC.

3. Copy SNMPAgent.dll and SNMP_Install.vbs to the PC. The files should be placed in
C:\TetraFlex\SNMP folder.
4. Run the SNMP_Install.vbs script, make sure to select Run as administrator option. This script will
a. Copy SNMPAgent.dll to SNMPAgent_.dll
b. Import the following registry settings:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNMP\Parameters\Exten
sionAgents]
"TetraFlexSNMP"="SOFTWARE\\SNMP\\CurrentVersion"

[HKEY_LOCAL_MACHINE\SOFTWARE\SNMP\CurrentVersion]
"Pathname"="C:\\TetraFlex\\SNMP\\SNMPAgent_.dll"

5. Check the SNMP Security settings Services > SNMP Service > Properties > Security. These settings
could be as shown in the example on the following figure:

AN-SNMP V1.0 2023.11.12 Page 6 of 16

 A safer solution is to restrict the SNMP access by ticking ”Accept SNMP packets from the hosts” and
add the Host name, IP or IPX addresses of the specific known hosts.
6. Restart the Windows SNMP Service.
7. Select SNMP mode for a node either by running OM command S71/SNMP/A or from Network
Management application – NC List window, navigate to Config tab and then to SNMP column where
SNMP mode can be selected by double clicking on a related cell.
8. For activating the SNMP agent on a LogServer, ignore steps 2 and 7 above and select “Enable
SNMP” in the “LogServer Config” tab of the LogServerTray

2.2 SNMP Windows 201x Server installation

Enabling SNMP on a server running a supported Windows Server version should be the same as on any
other Windows machine but may require Administrator rights. The only step that differs is the way the
SNMP service is enabled; once enabled all settings are the same.
For a description of enabling the SNMP service on Windows Server 201x, please consult you administrator.
Please note, that before the “Security” panel is displayed (step 7) a restart of the PC is necessary.
Also make sure that the DAMM SNMP extension agent dll (SNMPAgent64_.dll) used is the 64-bit version.

AN-SNMP V1.0 2023.11.12 Page 7 of 16

Installation of SNMP service on Windows Server:

1. Launch “Turn Windows features on or off”

2. Add Roles and Feature Wizard launches.

AN-SNMP V1.0 2023.11.12 Page 8 of 16

 3. Add feature “SNMP Service” and “SNMP WMI Provider”.

4. Reboot Windows.
5. Start services and find SNMP Service.

AN-SNMP V1.0 2023.11.12 Page 9 of 16

 6. Go to properties of SNMP services, and set the following settings:

7. Select SNMP mode for a node either by running OM command S71/SNMP/A or from Network
Management application – NC List window, navigate to Config tab and then to SNMP column where
SNMP mode can be selected by double clicking on a related cell.
8. For activating the SNMP agent on a LogServer, ignore step 7 above and select “Enable SNMP” in the
“LogServer Config” tab of the LogServerTray

AN-SNMP V1.0 2023.11.12 Page 10 of 16

3 SNMP MIB Tree
An SNMP Management Application uses information in the DAMM-GLOBAL-MIB.mib file (default location is
C:\TetraFlex\SNMP). Usually for an SNMP Management Application only loading of the mib file is needed,
along with access to DMZ IP address of the SNMP gateway node, for additional configuration and setup of
such application, please refer to the user guide for your SNMP Management Application.

The SNMP gateway has been tested to work with WhatsUp Gold 14.2, LorioPro V6 and iReasoning MIB
Browser, but will also work with any standard SNMP Management application.

The following figure is a graphical representation of the DAMM-GLOBAL-MIB module (The Damm MIB tree).

AN-SNMP V1.0 2023.11.12 Page 11 of 16

The variable scope covered by SNMP service can be seen by going into MIB tree. Each variable set can be
monitored separately, but also general overview of all available alarms can be seen from the same file. By
navigating through the MIB tree:
iso.org.dod.internet\private\enterprises\dammRoot\dammProducts\dammTetraFlex\dammBsc\...

… dammBscTable for nodes

… dammLogServerTable for LogServers

right click on the table and from the drop down menu select Table View. As it is shown on the following
figure, this option displays a preview of all available status variables per each node.

3.1 Alarms states and changes in MIB tree

Changes in the TetraFlex network can be easily seen in the above table. To illustrate status changes
representation in the MIB table, a couple of examples are listed. As it was previously explained, traps are
not supported, therefore the MIB browsing application would need to execute pooling on its own. No
change seen on the system will be visible in the MIB browser application, unless the user (or application)
pools the data.

AN-SNMP V1.0 2023.11.12 Page 12 of 16

 1. Preview of any MIB changes is displayed when NC1 was active and NC2 was redundant, then
switched over and NC2 becomes an active one and NC1 redundant. Additionally, as NC1 was set as
subscriber register master, it can also be seen that once active/redundant switchover was done,
subscriber register alarm went off as there was no other master available in the network, this also
triggers general alarm on all nodes.

2. Changes seen upon configuring Application Gateway and Terminal Gateway on the same node.
Value 255 changed to 0 and usually 255 indicates that something is not configured while 0 indicates
that a feature or service is configured but has no alarms.

3. If DMR T3 cell is configured, but no DMR T3 carrier is added as logical carrier, an alarm will be
triggered. This can also be seen in the SNMP application as it is showing the change of
alarmDmrTier3 state change from 255 (not configured) to 3 which is indicating L3 alarm level,
meaning it’s blocked.

AN-SNMP V1.0 2023.11.12 Page 13 of 16

3.2 MIB table values
An explanation of variable values is provided below; however, these descriptions can also be seen by
opening the mib file with a text viewer.

The most important variables are explained in detail in the following table:

Name Description
dammRoot The root of the Damm MIB tree.
dammGlobalModule Contains info on when the MIB file was updated. This is not a scalar
variable, which means the data is located in the mib file and is not
polled from the BSC.
dammBscTable Contains a dammBscEntry for each BSC running in the system.
dammBscEntry Contains each variable in a given BSC which is going to be monitored.
nodeNumber The node number of the BSC which is monitored. Values range from
1 to 999.
bscNumber The BSC number of the polled BSC. Values range from 1-2. (Used for
redundant BSCs).
bscIdString The description for the given BSC.
alarmNode Node alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured).
alarmCommon Common alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured).
alarmSubscriber Subscriber alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured).
alarmTetra Radio alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured).
alarmVoiceGw Voice Gateway alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked,
255=Not configured).
alarmPdGw Packet Data Gateway alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked,
255=Not configured).
alarmAppGw Application Gateway alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked,
255=Not configured).

AN-SNMP V1.0 2023.11.12 Page 14 of 16

 Name Description
alarmTerminalGw Terminal Gateway alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked,
255=Not configured).
hwType Hardware type (0=PC, 1=BSC421, 2=BSC412, 3=BS422, 4=PC422).
swVersion Software version string.
activationDate Activation date.
Active BSC active status (1=active, 0=not active).
alarmDMR Radio alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured).
alarmAnalog Radio alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured).
logserverNumber LogServer number (1-999)
logserverIdString LogServer ID string (e.g. Log server 25)
logserverAlarmCommon Common alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured
logserverAlarmVoice Voice alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked, 255=Not
configured)
logserverAlarmMulticastJoin Multicast join alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked,
255=Not configured)
logserverAlarmAllResourcesUsed All resources used alarm (0=OK, 1=Warning, 2=Alarm, 3=Blocked,
255=Not configured)
logserverSwVersion Software version string
logserverActivationDate Activation date
logserverCpuLoadServer LogServer CPU load in percentage
logserverMemUsageServer LogServer memory usage in kB
logserverCpuLoadDatabase Database CPU load in percentage
logserverMemUsageDatabase Database memory usage in kB

AN-SNMP V1.0 2023.11.12 Page 15 of 16

References

Document Description

OP-SYSTEM_PARAMETERS System parameter reference manual

OP-LOG_SERVER LogServer parameter description

AN-SNMP V1.0 2023.11.12 Page 16 of 16