Eden Net Self Monitoring Using Zabbix

EdenNet 21 FP 2106
EdenNet Self-monitoring Using Zabbix

DN09243842
Issue: 1-1
EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein.
This document is intended for use by Nokia' customers (“You”) only, and it may not be used except for the purposes defined in the agreement
between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced,
modified or transmitted in any form or means without the prior written permission of Nokia. If you have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You
are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using
it. Nokia welcome Your comments as part of the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity,
fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves
the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of
this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. But,
Nokia' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of
the software in the Product will be uninterrupted or error-free.
N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

WARR ANT Y OF AVA IL ABI LI T Y, AC CU RAC Y, R EL I A B I L IT Y, T I T L E , N O N - I N F R I N G E M E N T, M E R C H A N TA B I L I TY
OR F IT NE SS FO R A PA RT ICU LAR PU RPO SE, I S M A D E IN R E L AT I O N TO T H E C O N T E N T O F T H I S D O C U M E N T.
IN NO EVEN T WI L L NOK IA B E LI ABLE F OR AN Y DA M A G E S , I N C L U D I N G B U T N O T L I M I T E D TO S P E C I A L ,
D IRE CT, IN D IRECT, I NCI DE NTAL OR C ON SEQ UE N T IA L OR A N Y L O S S E S , S U C H A S B U T N O T L I M I T E D TO LO SS
OF PRO F IT, REVE NU E, B US IN ESS IN T ER RU PT I ON , B U S I NE S S O P P O RT U N I T Y O R D ATA T H AT M AY A R I S E
FRO M T HE USE O F TH IS DO CU M EN T O R T HE IN F OR M AT IO N I N I T, E V E N I N T H E C A S E O F E R R O R S I N O R
OM IS SI O NS FRO M T HI S DOC UM EN T O R IT S CO NT E N T.
This document is Nokia’ proprietary and confidential information, which may not be distributed or disclosed to any third parties without the
prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their
respective owners, and they are mentioned for identification purposes only.
Copyright © 2021 Nokia. All rights reserved.
Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the
safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this
document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you
as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for
any additional information.
EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Table of Contents
Contents
1 Summary of changes...................................................................................................................................... 5
2 Overview of EdenNet self monitoring........................................................................................................... 8
3 Accessing the Zabbix server......................................................................................................................... 9
4 Host configuration.........................................................................................................................................10
4.1 Creating SNMP user in Selfmon VM node.............................................................................................10
4.1.1 Checking the status of SNMPD service......................................................................................... 11
4.1.2 Stopping SNMPD service............................................................................................................... 11
4.1.3 Creating SNMP user.......................................................................................................................12
4.1.4 Starting SNMPD service.................................................................................................................12
4.1.5 Changing privileges on snmpd.conf file......................................................................................... 12
4.2 Importing a template............................................................................................................................... 13
4.3 Linking template to host..........................................................................................................................13
4.3.1 Linking a template.......................................................................................................................... 13
4.3.2 Unlinking a template....................................................................................................................... 14
4.4 Configuring Zabbix to forward the SNMP TRAPs for events to an external monitoring system..............14
4.4.1 Creating a new media type............................................................................................................ 14
4.4.2 Mapping media type to user...........................................................................................................15
4.4.3 Creating an action.......................................................................................................................... 16
4.5 Modifying Selfmon node Zabbix agent details........................................................................................17
5 Supported triggers........................................................................................................................................ 19
6 Monitoring triggers in Zabbix GUI...............................................................................................................26

6.1 Modifying attributes of selfmon trigger....................................................................................................26
6.2 Disabling and enabling a selfmon trigger............................................................................................... 26
6.2.1 Disabling default trigger for Central DB VM and PM KPI DB VMs................................................ 26
6.2.2 Enabling default trigger for Central DB VM and PM KPI DB VMs................................................. 27
7 Integrating NetAct with Selfmon..................................................................................................................28

7.1 Common Mediation Node - SNMP v3 changes..................................................................................... 28
7.1.1 Updating ISDK mapping xml.......................................................................................................... 28
7.1.2 Activating ENETNODE element adaptation................................................................................... 29
7.1.3 Inserting SNMP v3 adaptation in NEAC_ADAPTATIONS table..................................................... 29
7.2 Creating NEAC user............................................................................................................................... 29
7.3 Inserting an alarm................................................................................................................................... 31
8 Viewing zabbix selfmon alertscript log.......................................................................................................32
9 Troubleshooting............................................................................................................................................. 34
EdenNet 21 FP 2106 © 2021 Nokia 3

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Table of Contents
10 Appendix A: Enabling SNMP for ESXi...................................................................................................... 35
11 Appendix B: Zabbix log location............................................................................................................... 37

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Summary of changes
1 Summary of changes
Release Change description
EdenNet 21 FP 2106 No change.
EdenNet 21 FP 2103 Updated sections:
• Creating an action - updated the procedure for creating an action.

• Importing a template - Note about the import of ENET_VM_Moni-
toring_Template-v4.xml template is removed.
EdenNet 21 Updated sections:
• Host configuration - A note is added for multi IP scenario.

• Importing a template - A note is added regarding the import of
ENET_VM_Monitoring_Template-v4.xml template.
EdenNet 20 No change.
EdenNet 19A FP 2004 No change.
EdenNet 19A FP 2001 Updated section:
• Overview of EdenNet self monitoring - the note about the MySQL

database connection in zabbix server is modified.
EdenNet 19A Updated sections:
• Creating SNMP user - updated for python 3.7 and non-root user in-
stallation features.

• Overview of EdenNet self monitoring - a note is added regarding the

MySQL database connection in zabbix server.
EdenNet 19 No change.
EdenNet 18 SP1 1901 No change.
EdenNet 18 SP1 1812 Updated sections:
• In Supported triggers section, Mounted filesystem discovery triggers

are updated under ENET_VM_Monitoring_Template.
• In Importing a template section, enet_monitoring_central_
db_template.xml template is added.
EdenNet 18 SP1 1811 Updated section:
• In the Supported triggers section:
– the description of PROCESSOR LOAD IS TOO HIGH trigger is

modified.
– the Zabbix node watcher processes more than 75% busy trig-
ger is removed.
EdenNet 18 SP1 Added section:
• Troubleshooting section is added.
Updated section:
• In Creating a new media type section, Script parameters is

added.
EdenNet 18 Added sections:
• Creating SNMP user in Selfmon VM node.

• Configuring Zabbix to forward the SNMP TRAPs for events to an
external monitoring system.
• Integrating NetAct with Selfmon.
Updated section:
• Supported triggers section, three triggers: DISC NOT FULL, CPU

IDLE, and EdenNet APP SERVICE IS ACTIVE is removed.

EdenNet 17 SP1 FP1 No change.
EdenNet 17 SP1 No change.
EdenNet 17 FP1 Added sections:
• Modifying attributes of selfmon trigger section added.

• Disabling and enabling a selfmon trigger section added.
Updated section:
• Supported triggers section is updated with VM monitoring triggers

and ESXi triggers.
EdenNet 17 EdenNet Self-monitoring, initially an internal document is now delivered

to the customers for EdenNet 17 release.
Table 1: Summary of changes

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Overview of EdenNet self monitoring
2 Overview of EdenNet self monitoring
Self monitoring feature enables the EdenNet system to monitor its resources, connectivity and appli-
cations. Resources refer to hardware devices, virtual machines, CPU, memory and so on. Resource
measurements are monitored continuously and appropriate triggers/events are generated to indicate
a problem. The triggers can be viewed and acknowledged in the zabbix UI. Zabbix is used as the self
monitoring solution in the EdenNet system.
The zabbix server and its agent are installed as part of EdenNet installation. For further details about
installation, contact Nokia technical support.
Note: In EdenNet 19A release, zabbix server in the selfmon node uses login/password secu-
rity to connect to MySQL database.

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Accessing the Zabbix server
3 Accessing the Zabbix server
To access the Zabbix server, do the following:
1. Enter the following URL in the address field of the browser.
https://<selfmon node Address>/zabbix
The Zabbix home page appears.
2. Change the password after the first successful login attempt.
Note: Type the user name as Admin and password as zabbix. Admin user password
change is not enforced and must be done manually after installation.
3. Click Log In.
Expected outcome
The user is able to login successfully.

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Host configuration
4 Host configuration
The Zabbix Host is the Virtual machine or ESXi host to be monitored. This host is monitored for differ-
ent parameters. The host entity needs to be created for each of the EdenNet Virtual machines or ESXi
hosts during deployment.
To create a host, do the following:
1. Navigate to Configuration → Hosts → Create host.

2. Enter the below details for virtual machines:
Parameter Description
Host name Add the host name of the virtual machine
Groups Add the host to virtual machines group
Agent Interfaces Provide the IP address of the host.
Table 2: Parameters for Virtual machines
3. To change the IP of the default host Zabbix server, do the following:
a. Navigate to Configuration → Hosts.

b. Click Zabbix server host, and change the IP address from 127.0.0.1 to the current IP of the
Selfmon server.
c. Click Update.
4. Enter the below details for ESXi:
Parameter Description
Host name Add the host name of the ESXi blade
Groups Add the host Hypervisors group
SNMP Interfaces Provide the IP address of the host
Table 3: Parameters for ESXis
Note: If multi IP scenario is present, give the internal IP of VMs while creating the host entity.

4.1 Creating SNMP user in Selfmon VM node
Prerequisites
To create SNMP user in Selfmon VM Node, SNMPD service should be stopped.
To create SNMP user in Self monitoring VM Node, do the following procedures:
1. Checking the status of SNMPD service.
2. Stopping SNMPD service.
3. Creating SNMP user.
4. Starting SNMPD service.
5. Changing privileges on snmpd.conf file.
4.1.1 Checking the status of SNMPD service

To Check the status of SNMPD service, do the following:
1. Log in to the Selfmon VM node as root user.
2. Check the status of SNMPD service by entering:
systemctl status snmpd
Expected outcome
snmpd.service - Simple Network Management Protocol (SNMP) Daemon.
Loaded: loaded (/usr/lib/systemd/system/snmpd.service; disabled; vendor preset: disabled)
Active: active (running) since Wed 2018-09-05 14:46:14 EEST; 18h ago
Main PID: 4456 (snmpd)
CGroup: /system.slice/snmpd.service
└─4456 /usr/sbin/snmpd -LS0-6d -f
4.1.2 Stopping SNMPD service

• Stop the SNMPD service by entering:
systemctl stop snmpd
Expected outcome
User can check the SNMPD status by entering the following command:

4.1.3 Creating SNMP user
1. Log in as root user.
2. To export the python library path, execute the following command:
#export LD_LIBRARY_PATH=/usr/local/lib
3. Navigate to the following directory in selfmon node:
• cd /usr/lib/zabbix/alertscripts
• python3.7 create_net_snmp_v3_user.py -A <PASSPHRASE for
authentication> -a <authentication PROTOCOL> -X <PASSPHRASE for
privacy> -x <privacy PROTOCOL> -u <user>
For example: python3.7 create_net_snmp_v3_user.py -A Nokia@Test_1234 -a

SHA -X Nokia@Test_1234 -x AES128 -u test
Expected outcome
adding the following line to /var/lib/net-snmp/snmpd.conf:
createUser test SHA "Nokia@Test_1234" AES128 Nokia@Test_1234
adding the following line to /etc/snmp/snmpd.conf:
rwuser test
4.1.4 Starting SNMPD service

• Start the SNMPD service by entering:
systemctl start snmpd
Expected outcome
User can check the SNMPD status by entering the following command:
4.1.5 Changing privileges on snmpd.conf file

• For 777 permissions on net-snmp folder, enter:
chmod -R 777 /var/lib/net-snmp
Note: Recommending 777 permissions on net-snmp folder, as TRAP causes errors

due to privileges on this folder and files.

4.2 Importing a template

Virtual machine and EdenNet application monitoring templates are provided as part of the EdenNet
installation. These templates are located under /opt/nokia/selfmon/config in the Zabbix server
node.
Template Description
ENET_VM_Monitoring_Template-v4.xml Contains all the items, triggers required to

monitor the virtual machine
enet_monitoring_app_template.xml Contains all the items, triggers required to

monitor the EdenNet application
enet_monitoring_db_template.xml Contains all the items, triggers required to

monitor the EdenNet KPI database
enet_monitoring_task_nodes_template.xml Contains all the items, triggers required to

monitor the EdenNet task nodes
enet_monitoring_central_db_template.xml Contains all the items, triggers required to

monitor the EdenNet central database
Table 4: List of templates
Copy the templates to the host from where the Zabbix server GUI is accessed.
To import the templates to the Zabbix server, execute the below steps:
1. Log in to the Zabbix server.

2. Navigate to Configuration → Templates → Import.
3. Click Choose File to browse and select the templates copied from the Zabbix server node.
4. Import the selected template.
4.3 Linking template to host

Linking is a process whereby templates are applied to hosts whereas unlinking removes the host’s as-
sociation with the template.
Note: Template ENET_VM_Monitoring-v4.xml is packaged in /opt/nokia/self-

mon/config/ which could be used for VM monitoring. This template can be downloaded
and linked to the VM hosts which are to be monitored. For hardware monitoring, the default
Zabbix template Template SNMP OS Linux can be linked to the hypervisor/physical host.

4.3.1 Linking a template
To link a template to the host, do the following:
1. Navigate to Configuration → Hosts.
2. Click the required host.
3. Click Templates → Link new templates.
4. Select the appropriate templates to be linked and click Select.
5. Click Update to save the changes.
4.3.2 Unlinking a template
To unlink a template from a host, do the following:
1. Go to Configuration → Hosts.
2. Select the required host and click Templates → Linked templates.
3. Click Unlink or Unlink and clear next to the template to be unlinked.
4. Click Update to save the changes.
4.4 Configuring Zabbix to forward the SNMP TRAPs for events to an

external monitoring system
Zabbix supports triggers for monitoring items and actions to practice predefined operations when the
triggers occur. By combining AlertScript and user defined Media Types, SNMP Version 3 TRAPs can
be sent automatically.
To configure zabbix to send SNMP Version 3 TRAPS to an external monitoring system, follow the be-
low procedures:
1. Creating a new media type.
2. Mapping media type to user.
3. Creating an action.
4.4.1 Creating a new media type

Follow the below steps to create a new media player.
1. Navigate to Administration → Media types → Create media type to create this configuration.
2. Provide the following inputs to create a new media type:

Parameter name Value
Name SNMP Sender
Type Script
Script name alertscript_v3.py
Enabled checked
Script parameters Add command-line parameters to the script.
{ALERT.SENDTO}, {ALERT.SUBJECT}, and

{ALERT.MESSAGE}
Table 5: Inputs for creating a new media type
3. Click Add to save the changes.
Expected outcome
A new media type SNMP sender is created.
4.4.2 Mapping media type to user

Follow the below steps to map the SNMP sender media type to user.
1. Navigate to Administration → Users.
2. Click on the User.
3. Navigate to Media tab.
4. Click Add.
5. Provide the following information.
Type SNMP sender

Send to IP address of the external monitoring system
Table 6: Inputs for mapping media type to user
6. Click Add.
7. Click Update.
4.4.3 Creating an action

To create an action, do the following:
1. Navigate to Configuration → Actions → Create action.
2. In the Actions tab, provide the following inputs:
Name Report issues to NBI
Enabled checked
Table 7: Inputs for creating an action
3. Navigate to Operations tab and provide the following inputs:
Parameter Value
Default subject {TRIGGER.STATUS}: {TRIGGER.NAME}
Default message 'Trigger: {TRIGGER.NAME},
Trigger status: {TRIGGER.STATUS},
Trigger severity: {TRIGGER.SEVERITY},
HostIP: {HOST.IP},
HostName: {HOST.HOST},
Security name: <user>,
{ITEM.NAME1}: {ITEM.VALUE1}'
Table 8: Inputs for action operation
4. In the Operations label, click New.

The Operation details pane appears.
5. In the Operation details pane provide the following inputs:
Parameter Value
Operation type Send message
Send to User groups Click Add and select the required User groups. For example,
Zabbix administrators.
Click Select to add the user groups.
Send to Users Click Add and select the required Users.
Click Select to add the users.
Send only to SNMP sender
Table 9: Inputs for action operation
6. Click Add to add the above provided details.
7. From Action tab, go to New condition.
8. Select Trigger from the drop-down list for a new condition, and then click Select.
9. Choose groups as Templates and ENET VM Monitoring Template as host from the drop-down
list.
10. Choose all the Triggers and click Select.
Repeat the above steps for all the ENET templates. (For ENET_APP_SERVICE_MONITORING,
ENET_CENTRAL_DB_SERVICE_MONITORING, ENET_KPI_DB_SERVICE_MONITORING),
then click Add.
11. Click Add at the bottom right corner of the Actions tab to add the action.
Expected outcome
The Report issues to NBI action is successfully added with the given details.

4.5 Modifying Selfmon node Zabbix agent details

To modify Selfmon node Zabbix agent details, do the following:
2. Click Zabbix server host.
3. Modify the following details:
• Host name: Zabbix server hostname

• Visible name: Zabbix server hostname
• Agent interfaces: Zabbix server IP address

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Supported triggers
5 Supported triggers
Zabbix server supports the below mentioned triggers to monitor the EdenNet system.
Trigger Severity Polling interval Description
NBI Triggers
CONFIGURED MAX Information 3600 seconds Triggered when the configured maxi-
NUMBER OF PRO- mum number of processes is less than
CESSES IS TOO 256
LOW
MORE THAN 30 Warning 60 seconds Triggered when the average number of

PROCESSES RUN- processes in the last 5 samples is more
NING IN AVERAGE than 30
DISK I/O IS OVER- Warning 60 seconds Triggered when the average i/o wait
LOADED time spent in the last 5 samples is more
than 20
PASSWORD HAS Warning 3600 seconds Triggered when the /etc/passwd has
BEEN CHANGED changed
PROCESSOR LOAD High 60 seconds Triggered when the average load is

IS TOO HIGH higher than 80% for the past 5 minutes
VIRTUAL MACHINE High 30 seconds Triggered when the agent node is not
IS UNREACHABLE accessible for 5 minutes
FOR 5 MINUTES
LACK OF FREE High 300 seconds Triggered when the free swap space is
SWAP SPACE less than 50 M
LACK OF AVAILABLE High 300 seconds Triggered if the available memory is

MEMORY ON SERV- less than 20 M
ER
EDEN-NET APP Warning Every 30 seconds Triggered when any of the registered
SERVICE IS INAC- services hosted in wsgi server move to
TIVE inactive state
EDEN-NET APP High Every 30 seconds Triggered when any of the registered
SERVICE FAILED services hosted in wsgi server move to
failed state.
EDEN-NET MODULE High Every 600 sec- Triggered when an EdenNet module
FAILED onds goes to failed state

EDEN-NET DB High Every 300 sec- Triggered when unable to connect to

SERVICE MYSQL onds mysql db from the APP server
CONNECTION
FAILED
ENET_VM_MONITORING_Template
ENET Free disk space High 3600 seconds Triggered when free disk space is less
is less than 20% on than 20% on filesystem
volume <FileSystem-
Name>
ENET Free disk space Major 3600 seconds Triggered when free disk space is less
volume <FileSystem-
Name>
ENET Free disk space Minor 3600 seconds Triggered when free disk space is less
volume <FileSystem-
Name>
ENET Free inodes High 3600 seconds Triggered when free inodes is less than
is less than 20% on 20% on filesystem
volume <FileSystem-
Name>
ENET Free inodes Not classified 3600 seconds Triggered when free inodes is less than
is less than 30% on 30% on filesystem
volume <FileSystem-
Name>
Zabbix Triggers
Template: ENET_TASK_NODE_MONITORING (Task VM)
Number of available High Every 30 seconds Triggered when number of available

worker's processes worker's processes is equal to 0
equal to 0
Number of available Warning Every 30 seconds Triggered when number of available

worker's processes worker's processes is less than 5
less than 5
Number of task-failed High 60 seconds Triggered when number of task-failed

events greater than 5 events is greater than 5

Number of task-failed Warning 60 seconds Triggered when number of task-failed

events greater than 0 events is greater than 0
Number of task-reject- High 60 seconds Triggered when number of task-rejected

ed events greater than events is greater than 0
0
Template: App Zabbix Agent (Selfmon VM)
Host name of zabbix_ Information 3600 seconds Triggered when the host name of zab-
agentd was changed bix_agent(d) is changed on host
on {HOST.NAME}
Version of zabbix_ Information 3600 seconds Triggered when the Version of zabbix_
agent(d) was changed agent(d) is changed on host
on {HOST.NAME}
Zabbix agent on Average 60 seconds Triggered when Zabbix agent on host is

{HOST.NAME} is un- unreachable for 5 minutes
reachable for 5 min-
utes
Template: Template App Zabbix Server (Selfmon VM)
More than 100 items Warning 600 seconds Triggered when more than 100 items
having missing data have missing data for more than 10
for more than 10 min- minute
utes
Zabbix value cache High 60 seconds Triggered when zabbix value cache
working in low memo- memory is almost close to 1 MB
ry mode
Zabbix proxy poller Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix proxy poller processes are busy
75% busy
Zabbix self-monitoring Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix self-monitoring processes are busy
75% busy
Zabbix poller process- Average 60 seconds Triggered when more than 75% of Zab-
es more than 75% bix poller processes are busy
busy
Zabbix timer process- Average 60 seconds Triggered when more than 75% of Zab-
es more than 75% bix timer processes are busy
busy

Zabbix ipmi poller Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix ipmi poller processes are busy
75% busy
Zabbix unreachable Average 60 seconds Triggered when more than 75% of Zab-
poller processes more bix unreachable poller processes are
than 75% busy busy
Zabbix snmp trapper Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix snmp trapper processes are busy
75% busy
Less than 25% free in Average 60 seconds Triggered when there is less than 25%
the vmware cache free space in the vmware cache
Zabbix java poller Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix java poller processes are busy
75% busy
Zabbix vmware col- Average 60 seconds Triggered when more than 75% of Zab-
lector processes more bix vmware collector processes are
than 75% busy busy
Zabbix icmp pinger Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix icmp pinger processes are busy
75% busy
Zabbix trapper Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix trapper processes are busy
75% busy
Zabbix http poller Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix http poller processes are busy
75% busy
Less than 5% free in Average 60 seconds Triggered when there is less than 5% of
the value cache free space in value cache
Zabbix alerter Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix alerter processes are busy.
75% busy
the history cache of free space in the history cache
the trends cache of free space in the trends cache

Less than 25% free Average 60 seconds Triggered when there is less than 25%
in the history index of free space in the history index cache
cache
Zabbix configuration Average 60 seconds Triggered when more than 75% of Zab-
syncer processes bix configuration syncer processes are
more than 75% busy busy
Zabbix db watchdog Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix db watchdog processes are busy
75% busy
Zabbix housekeeper Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix housekeeper processes are busy
75% busy
Zabbix history syncer Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix history syncer processes are busy
75% busy
Zabbix escalator Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix escalator processes are busy
75% busy
Zabbix discoverer Average 60 seconds Triggered when more than 75% of Zab-
processes more than bix discoverer processes are busy
75% busy
Less than 25% free Average 60 seconds Triggered when there is less than 25%
in the configuration of free space in the configuration cache
cache
Template: Template OS Linux (Selfmon VM)
Configured max num- Information 3600 seconds Triggered when the Configured max
ber of opened files number of opened files is too low on
is too low on {HOST. host
NAME}
Host information was Information 3600 seconds Triggered when the host information
changed on {HOST. was changed on host
NAME}
Template App Zab- Information 3600 seconds Triggered when the version of zabbix_
bix Agent: Version of agent(d) is changed on host
zabbix_agent(d) was
changed on {HOST.
NAME}

Template App Zabbix Information 3600 seconds Triggered when the host name of zab-
Agent: Host name of bix_agentd is changed on host
zabbix_agentd was
changed on {HOST.
NAME}
Configured max num- Information 3600 seconds Triggered when the configured max
ber of processes is too number of processes is too low on host
low on {HOST.NAME}
Hostname was Information 3600 seconds Triggered when the host name was
changed on {HOST. changed on host
NAME}
{HOST.NAME} has Information 600 seconds Triggered when the host is restarted
just been restarted
Too many processes Warning 60 seconds Triggered when there are too many
on {HOST.NAME} processes on host
Too many process- Warning 60 seconds Triggered when there are too many
es running on {HOST. processes running on host
NAME}
Lack of free swap Warning 60 seconds Triggered when there is lack of free
space on {HOST. swap space on host
NAME}
Processor load is too Warning 60 seconds Triggered when the processor load is
high on {HOST.NAME} too high on host
/etc/passwd has been Warning 3600 seconds Triggered when the /etc/passwd has
changed on {HOST. been changed on host
NAME}
Disk I/O is overloaded Warning 60 seconds Triggered when the Disk I/O is over-
on {HOST.NAME} loaded on host
Template App Zabbix Average 60 seconds Triggered when the Zabbix agent on
Agent: Zabbix agent host is unreachable for 5 minutes
on {HOST.NAME} is
unreachable for 5 min-
utes
Lack of available Average 60 seconds Triggered when there is lack of avail-

memory on server able memory on server
{HOST.NAME}

Table 10: VM monitoring triggers
Disk partitions: Free disk Warning 3600 seconds Triggered when the free
space is less than 20% on disk space is less than 20%
volume XXX
Network interfaces: Opera- Information 3600 seconds Triggered when the oper-
tional status was changed ational status changes on
on {HOST.NAME} interface host interface device vmnic
Device vmnicXXX at 06:00.
X XXX

on {HOST.NAME} interface host interface Link Aggrega-
Link Aggregation XXX on tion on vSwitch0 due to load
switch: vSwitch0, load bal- balancing
ancing algorithm: source
port id hash

on {HOST.NAME} interface host interface Tradition-
Traditional Virtual VMware al Virtual VMware switch:
switch: vSwitch0 vSwitch0

on {HOST.NAME} interface host virtual interface: vmk0
Virtual interface: vmk0 on on vswitch:vSwitch0 and
vswitch vSwitch0 portgroup: portgroup
XXX
Table 11: ESXi triggers
Note: Template OS Linux and Template App Zabbix Server are default templates provided by
Zabbix. The above documented triggers can have a slight mismatch in names, if the operator
is upgrading from EdenNet 18 to EdenNet 18 SP1 or later.

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Monitoring triggers in Zabbix GUI
6 Monitoring triggers in Zabbix GUI
To view the generated triggers, do the following:
• Navigate to Monitoring → Overview.
Expected outcome
All the generated triggers can be viewed in this page.
6.1 Modifying attributes of selfmon trigger

3. Click Triggers in the row of the host.
4. Click the trigger to be modified.
5. Clear the Enabled check box to disable the existing trigger, and save changes.
6. Click the trigger to be modified again.
7. Click Clone to copy the existing trigger.
8. Make the changes required (expression, severity, name, time).
Rename the trigger in line with the expression if required.
9. Enable trigger by selecting the Enabled check-box.
10. Save changes.
6.2 Disabling and enabling a selfmon trigger
6.2.1 Disabling default trigger for Central DB VM and PM KPI DB VMs

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Monitoring triggers in Zabbix GUI
3. Click on Triggers in the row of the host that represent Central DB VM and PM KPI DB VMs.
4. Disable the existing trigger by clicking on Enabled link in Status column for Mounted filesystem
discovery : ENET Free disk space is less than 40% on volume /backupdb, confirm that status
changes to Disabled.
5. Disable the existing trigger by clicking on Enabled link in Status column for Mounted filesystem
discovery: ENET Free disk space is less than 30% on volume /backupdb, confirm that status
changes to Disabled.
6.2.2 Enabling default trigger for Central DB VM and PM KPI DB VMs
3. Click on Triggers in the row of the host that represent Central DB VM and PM KPI DB VMs.
4. Enable the existing trigger by clicking on Enabled link in Status column for Mounted filesystem
discovery : ENET Free disk space is less than 40% on volume /backupdb, confirm that status
changes to Enabled.
5. Enable the existing trigger by clicking on Enabled link in Status column for Mounted filesystem
discovery: ENET Free disk space is less than 30% on volume /backupdb, confirm that status
changes to Enabled.

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Integrating NetAct with Selfmon
7 Integrating NetAct with Selfmon

The configuration changes in NetAct, involves the following:
• Common Mediation Node - SNMP v3 changes

• Creating NEAC user
• Inserting an alarm
Note: Integration of NetAct with EdenNet Selfmon should be done only with NetAct 17.8
or higher versions.
7.1 Common Mediation Node - SNMP v3 changes

EdenNet17 adaptation in NetAct17.2 is not supporting SNMP v3 access service. Currently it supports
only SNMP v2 access. Since adaptation is not bringing SNMP v3 access, ISDK SNMP FM mediation
will not be able to parse SNMP v3 traps.
To provide support for SNMP v3 access for this adaptation, execute following updates as root user:
• Updating ISDK mapping xml

• Activating ENETNODE element adaptation
• Inserting SNMP v3 adaptation in NEAC_ADAPTATIONS table
7.1.1 Updating ISDK mapping xml
1. Login to the common mediation node.
2. Copy the com.nokia.enet.enetnode-17.mdksnmpfm file to /home/omc by entering

command:
# cp /var/opt/nokia/oss/global/isdk/converters/mapping-config/
com.nokia.enet.enetnode-17.mdksnmpfm /home/omc/
3. Edit attribute snmpVersion = V2C to snmpVersion = V3 using vi/vim editor, and save it.
4. To deploy the modified mapping file, enter the command:
# isdk_deployment_suite.sh --type SNMPFM-MAPPINGONLY --deploy --file /

home/omc/com.nokia.enet.enetnode-17.mdksnmpfm
Expected outcome
• INFO: Deploying SNMPFM Mapping for: /home/omc/com.nokia.enet.enetnode-17.mdksnmpfm

• INFO: Overwriting existing SNMPFM Mapping Config for Adaptation Id

com.nokia.enet.enetnode and Version 17
7.1.2 Activating ENETNODE element adaptation

• To activate ENETNODE element adaptation, execute the activate command:
sh /opt/oss/nokianetworks-isdk-snmpfm/bin/ISDKFMActivationManager.sh
--activate --agentId PLMN-PLMN/ENET<ENET_MO_INSTANCE_ID>/ENETNODE-
<ENETNODE_MO_INSTANCE_ID> com.nokia.enet.enetnode 17 PLMN-PLMN/ENET-
<ENET_MO_INSTANCE_ID>/ENETNODE-<ENETNODE_MO_INSTANCE_ID> <Selfmon-IP>
Where,
– ENET_MO_INSTANCE_ID is the instance id of ENET managed object configured in Integration

operations in NEIW section of NetAct Operating documentation, and
– ENETNODE_MO_INSTANCE_ID is the instance id of ENETNODE managed object configured
in Integration operations in NEIW section of NetAct Operating documentation.
For example,
# sh /opt/oss/nokianetworks-isdk-snmpfm/bin/ISDKFMActivationManager.sh --activate --agentId

PLMN-PLMN/ENET-1/ENETNODE-1 com.nokia.enet.enetnode 17
PLMN-PLMN/ENET-1/ENETNODE-1 <Selfmon-IP>
7.1.3 Inserting SNMP v3 adaptation in NEAC_ADAPTATIONS table
1. To insert SNMP v3 adaption in NEAC_ADAPTATIONS table, execute:
# sqlplus omc/omc
SQL>INSERT INTO NEAC_ADAPTATIONS

VALUES('com.nokia.enet.enetnode','ENETNODE','17','SNMP v3
Access','','NE','N','Y','N','com.nokia.enet.enetnode','N');
2. If an error occurs as - ORA-02291: integrity constraint <constraint name>

violated - parent key not found, then execute:
SQL>INSERT into NEAC_SERVICE_TYPES values ('SNMP v3

Access','','','','');
Then, follow with Step1.

7.2 Creating NEAC user
Prerequisites
All standard procedures to integrate EdenNet to NetAct should be completed.
Note: For information on integrating EdenNet to NetAct, see the Integrating EdenNet to
NetAct section in NetAct Operating documentation.
For SNMP v3 Access user creation in NetAct, do the following:
1. Go to NetAct start page.
2. Go to Security → Security → Security → Network Element Access Control → Credentials →

New.
Note: Ensure that the created service user has sysop group permissions.
Table 12: SNMP v3 user creation in NetAct lists the parameter and values used for SNMP v3 user
creation in NetAct.
Parameter Values
Service type SNMP v3 Access
Profile Non-Contest
SNMP UserName test
SNMP Authentication Protocol SHA
SNMP Authentication Passphrase Nokia@test_1234
Confirm SNMP Authentication Passphrase Nokia@test_1234
SNMP Privacy Protocol AES128
SNMP Privacy Passphrase Nokia@test_1234
Confirm SNMP Privacy Passphrase Nokia@test_1234
Network element Maintenance region: MRC-20101947/MR-Eden
Table 12: SNMP v3 user creation in NetAct
For SNMP user name, SNMP authentication passphrase and SNMP privacy protocol, see section
Creating SNMP user.
Note:

The user name and corresponding credentials should be identical to the user created for
SNMP.
SNMP UserName = <user>
SNMP Authentication Passphrase = <PASSPHRASE for authentication>
Confirm SNMP Authentication Passphrase = <PASSPHRASE for authentication>
SNMP Privacy Passphrase = <PASSPHRASE for privacy>
Confirm SNMP Privacy Passphrase = <PASSPHRASE for privacy>
For information on Maintenance region creation procedure, see the Integrating EdenNet to NetAct
section in NetAct Operating documentation.
7.3 Inserting an alarm

log file path: /var/opt/oss/log/nokianetworks-isdk-snmpfm
1. Login to the common mediation VM node as root/omc.
2. Go to /var/opt/oss/log/nokianetworks-isdk-snmpfm directory, and find the following log

files:
• isdk_snmpfm_activity0_0.log
• isdk_snmpfm_error0_0.log
For successful integration of SNMP v3 Trap 'isdk_snmpfm_activity0_0.log', search for a statement

with the following sample syntax:
2017-09-18-T16:05:08.131+0530 | | | fMDBSMIEngine_
fMNotificationProcessor-8 | INFO | com.nsn.oss.mdk.fm.db.dao.
FMEventStatementSetter | Inserting Alarm New to DB with the values:
{Event Time = 2017-09-18T10:35:07+00:00 Specific Problem = 11603
Alarm Text = LACK OF AVAILABLE MEMORY ON SERVER Severity = MAJOR
Additional Text 1 = Additional Text 2 = null Additional Text 3 = null
Additional Text 4 = null Additional Text 5 = null Additional Text 6 =
null Event Type = QUALITY_OF_SERVICE Alarm ID = 11603 Probable Cause
= 564 System DN = PLMN-PLMN/ENET-1/ENETNODE-1/ENETVM-10.61.18.118
Uploadable = true}

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Viewing zabbix selfmon alertscript log
8 Viewing zabbix selfmon alertscript log

log file path: /var/log/zabbix/zabbix_server.log
To view SNMP Traps/errors information, do the following:
1. Login to Selfmon VM node as root user.
2. Open /var/log/zabbix/zabbix_server.log file.
Sample SNMP alertscript 'DISK NOT FULL' trap as follows:
Tue Sep 19 19:14:11 IST 2017:*** *** *** *** snmpv3.sh Script
Triggered from Zabbix *** *** *** ***
Param 1: 10.61.12.226
Param 2: PROBLEM: DISK NOT FULL
---:Msg Started:---
'Trigger: DISK NOT FULL,
Trigger status: PROBLEM,
Trigger severity: Information,
HostIP:10.61.18.121,
HostName:PMDB3G,
Security name:test,
Authentication pass phrase:Nokia@test_1234,
Privacy pass phrase:Nokia@test_1234,
ENET SWAP Available Space: 19016970240'
---:Msg End:---
-----------------
Trap received: Trigger: DISK NOT FULL,Trigger status: PROBLEM,Trigger
severity: Information,HostIP:10.61.18.121,HostName:PMDB3G,Security
name:test,Authentication
pass phrase:Nokia@Sprin_1234,Privacy pass phrase:Nokia@test_1234,ENET
SWAP Available Space: 19016970240
-----------------
nbi_ip: 10.61.12.226
-----------------
----- Started Parsing received trap message -----
security_name :test, authentication_pass_phrase:Nokia@test_1234,
privacy_pass_phrase:Nokia@test_1234
----- End of Parsing received trap message -----
Final Command Sending To NBI:snmptrap -v 3 -u test -a SHA -A
Nokia@test_1234 -x AES128 -X Nokia@test_1234 -l authPriv 10.61.12.
226:162 ""
1.3.6.1.4.1.1751.2.78.5.6.11 1.3.6.1.4.1.1751.2.78.5.6.9.1.2.1 s DISK
NOT FULL 1.3.6.1.4.1.1751.2.78.5.6.9.1.3.1 i 4 1.3.6.1.4.1.1751.2.78.
5.6.9.1.4.1 s 1505828651
1.3.6.1.4.1.1751.2.78.5.6.9.1.5.1 i 564 1.3.6.1.4.1.1751.2.78.5.6.9.1.
7.1 i 5 1.3.6.1.4.1.1751.2.78.5.6.9.1.9.1 s 1.3.6.1.4.1.1751.2.78.5.6.
9.1.15.1 s 11612

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Viewing zabbix selfmon alertscript log
1.3.6.1.4.1.1751.2.78.5.6.9.1.16.1 s 10.61.18.121 1.3.6.1.4.1.1751.2.

78.5.6.9.1.19.1 s PMDB3G

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Troubleshooting
9 Troubleshooting
Problem 1: Sporadic issues with SNMP alarms due to the presence/absence of SNMP v3 user
There can be sporadic issues seen where SNMP v3 alarms are visible in NetAct even when the SNMP
v3 user does not exist in NetAct, and not visible when it exists. When SNMP v3 user in NetAct is
deleted and recreated, there will be a time gap for alarms to be visible in NetAct. After the following
message is seen in isdk_snmpfm_activity.log, triggers/alarms start being visible on the monitor.
2018-03-13-T16:10:09.423+0200 | | | TrapCollector-Thread-20 | INFO | com.

nsn.oss.mdk.snmp.impl.USMManager | Updating the User to the UsmUserEntry
Table : <user>
• If service is not started, agent is not activated, or NASDA service is unavailable, for
troubleshooting these issues see:
http://belk.netact.noklab.net/N17-2_SP08/
topic/troubleshooting_netact/sbi/isdk/concepts/
fm_isdk_snmp_fm_alarm_not_received_on_netact_for_all_the_isdk_snmp_pm_mediation_b
case.html?cp=11_0_1_2_11
• If NEAC configuration is incorrect or NEAC service is unavailable, for troubleshooting these issues
see:
http://belk.netact.noklab.net/N17-2_SP08/
topic/troubleshooting_netact/sbi/isdk/concepts/
fm_alarms_upload_fails_or_hangs_for_all_isdk_snmp_fm_based_ne_case.html?
cp=11_0_1_2_12
Problem 2: SNMP v3 Traps not being sent from Zabbix server
If the traps are not sent and the following message is not seen in /var/log/zabbix/
zabbix_server.log
Final Command Sending To NBI:snmptrap -v 3 -u test -a SHA -A

Nokia@test_1234 -x AES128 -X Nokia@test_1234 -l authPriv 10.61.12.
226:162 ""
Then, change the permission of /opt/nokia/selfmon/config/snmp_v3_data.p file by entering:
chmod 666 /opt/nokia/selfmon/config/snmp_v3_data.p

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Appendix A: Enabling SNMP for ESXi
10 Appendix A: Enabling SNMP for ESXi
For ESXi 5.5
1. Login to ESXi host as root user.
# esxcli system snmp set --communities public
# esxcli system snmp set --enable true

2. Add a firewall rule to allow the SNMP inbound port, and then enable it.
# esxcli network firewall ruleset set --ruleset-id snmp --allowed-all
true
# esxcli network firewall ruleset set --ruleset-id snmp --enabled true
For ESXi 6.0
1. Login to ESXi host as root user.

2. Execute the following:
esxcli system snmp set -r
esxcli system snmp set -c public
esxcli system snmp set -p 161
esxcli system snmp set -L "Helsinki, Europe"
esxcli system snmp set -C admin@example.com
esxcli system snmp set -e yes

3. Verify the settings by executing:
esxcli system snmp get
Sample Output:
# esxcli system snmp get
Authentication:
Communities: public
Enable: true
Engineid: 00000063000000a100000000
Hwsrc: indications
Largestorage: true
Loglevel: info
Notraps:
Port: 161
Privacy:

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Appendix A: Enabling SNMP for ESXi
Remoteusers:
Syscontact: admin@example.com
Syslocation: Helsinki, Europe
Targets:
Users:
V3targets:
4. Add a firewall rule to allow the SNMP inbound port, and then enable it.
# esxcli network firewall ruleset set --ruleset-id snmp --allowed-all
true
# esxcli network firewall ruleset set --ruleset-id snmp --enabled true

EdenNet Self-monitoring Using Zabbix DN09243842 1-1 Appendix B: Zabbix log location
11 Appendix B: Zabbix log location
Service Log Location
Zabbix-server /var/log/zabbix/zabbix_server.log
Zabbix-agent /var/log/zabbix/zabbix_agentd.log
Apache /var/log/httpd/access_log,
/var/log/httpd/error_log
Mysql <MySQL data directory path configured in inventory

file>/<hostname>.log
Note: The actual path comes from <mysql_datadir>

variable in the inventory file, with /mysqld.log added to
it. Hence, the path is <MySQL data directory path config-
ured in inventory file during installation>/mysqld.log.
For example: mysql_datadir=/home/data/mysql
Table 13: Zabbix log location

Eden Net Self Monitoring Using Zabbix

Uploaded by

Eden Net Self Monitoring Using Zabbix

Uploaded by

EdenNet 21 FP 2106

EdenNet Self-monitoring Using Zabbix

N O WA RRA NT Y O F AN Y KI ND , EI T HER EXPR ES S OR I M P L I E D , I N C L U D I N G B U T N O T L I M I T E D TO A N Y

Copyright © 2021 Nokia. All rights reserved.

Important Notice on Product Safety

2 Overview of EdenNet self monitoring........................................................................................................... 8

3 Accessing the Zabbix server......................................................................................................................... 9

6 Monitoring triggers in Zabbix GUI...............................................................................................................26

7 Integrating NetAct with Selfmon..................................................................................................................28

8 Viewing zabbix selfmon alertscript log.......................................................................................................32

EdenNet 21 FP 2106 © 2021 Nokia 3

10 Appendix A: Enabling SNMP for ESXi...................................................................................................... 35

11 Appendix B: Zabbix log location............................................................................................................... 37

EdenNet 21 FP 2106 © 2021 Nokia 4

Release Change description

EdenNet 21 FP 2106 No change.

EdenNet 21 FP 2105 No change.

EdenNet 21 FP 2104 No change.

EdenNet 21 FP 2103 Updated sections:

• Creating an action - updated the procedure for creating an action.

EdenNet 21 Updated sections:

• Host configuration - A note is added for multi IP scenario.

EdenNet 20 FP 2011 No change.

EdenNet 20 FP 2010 No change.

EdenNet 20 FP 2009 No change.

EdenNet 20 FP 2008 No change.

EdenNet 20 FP 2007 No change.

EdenNet 19A FP 2004 No change.

EdenNet 19A FP 2003 No change.

EdenNet 19A FP 2002 No change.

EdenNet 19A FP 2001 Updated section:

• Overview of EdenNet self monitoring - the note about the MySQL

EdenNet 19A FP 1912 No change.

EdenNet 19A FP 1911 No change.

EdenNet 19A Updated sections:

EdenNet 21 FP 2106 © 2021 Nokia 5

Release Change description

• Overview of EdenNet self monitoring - a note is added regarding the

EdenNet 19 FP 1907 No change.

EdenNet 19 FP 1906 No change.

EdenNet 19 FP 1905 No change.

EdenNet 19 FP 1904 No change.

EdenNet 18 SP1 1901 No change.

EdenNet 18 SP1 1812 Updated sections:

• In Supported triggers section, Mounted filesystem discovery triggers

EdenNet 18 SP1 1811 Updated section:

• In the Supported triggers section:

– the description of PROCESSOR LOAD IS TOO HIGH trigger is

EdenNet 18 SP1 Added section:

• Troubleshooting section is added.

• In Creating a new media type section, Script parameters is

EdenNet 18 Added sections:

• Creating SNMP user in Selfmon VM node.

• Supported triggers section, three triggers: DISC NOT FULL, CPU

EdenNet 21 FP 2106 © 2021 Nokia 6

Release Change description

EdenNet 17 SP1 FP1 No change.

EdenNet 17 SP1 No change.

EdenNet 17 FP1 Added sections:

• Modifying attributes of selfmon trigger section added.

• Supported triggers section is updated with VM monitoring triggers

EdenNet 17 EdenNet Self-monitoring, initially an internal document is now delivered

Table 1: Summary of changes

EdenNet 21 FP 2106 © 2021 Nokia 7

2 Overview of EdenNet self monitoring

EdenNet 21 FP 2106 © 2021 Nokia 8

3 Accessing the Zabbix server

To access the Zabbix server, do the following:

1. Enter the following URL in the address field of the browser.

https://<selfmon node Address>/zabbix

The Zabbix home page appears.

2. Change the password after the first successful login attempt.

3. Click Log In.

The user is able to login successfully.

EdenNet 21 FP 2106 © 2021 Nokia 9

To create a host, do the following: