The Command “lsnem”
This command, when executed by a FOXMAN‑UN administrator, shows the status of the NEM components. It displays a list of the daemons, services, and database instances with their status. The following is a sample output from the “lsnem” command. Some of the components and services depend on license options and may not be available in your setup.
NEM COMPONENTS:
===============
Host: Running system services Status
-----------------------------------------------
NEM InfluxDB Service active
Telegraf Service active
Postgresql Server active
RabbitMQ Service active
Database: Instances Status
-----------------------------------------------
'NEM_DATABASE' present
'PM_DATABASE' present
'NEMSEC_DATABASE' present
'DIRAC_DATABASE' present
NEM Base: Running services Status
-----------------------------------------------
OMNI Event active
OMNI Names active
Procwatch active
BP Credentials active
BP Event Channel active
BP RabbitMQ VirtualHost active
BP Security Manager active
Event Log Manager - Security active
Voyager API Gateway active
Voyager MainStandby active
Voyager NEMCORE active
NEM Core: Running services Status
-----------------------------------------------
BP Alarm Manager active
BP Business Logic Manager active
BP Network Manager active
BP Network Query Manager active
BP PM Async Manager active
BP PM Collector active
BP Service Manager active
BP Task Manager active
ENP Network Manager active
ENP Security Manager active
Event Log Manager - System active
Supervision Timer active
NEM NP: Running services Status
-----------------------------------------------
NP Network Manager active
NEM CLI: Running services Status
-----------------------------------------------
BP ECLI Proxy active
BP Line Test Manager active
BP Report Manager active
NEM HLM: Running services Status
-----------------------------------------------
HLM SNMP NBI Agent active
NEM Voyager: Running services Status
-----------------------------------------------
Voyager CEM active
Voyager Credential Distribution active
Voyager DCN Manager active
Voyager ESW active
Voyager Healthcheck active
Voyager MIB active
Voyager PM active
Voyager PTP Map active
Voyager Public Gateway active
Voyager QOSTE active
Voyager Tag Manager active
Voyager Task Scheduler active
DIRAC Key Manager: Running services Status
-----------------------------------------------
DKM REST Server active
ELEMENT AGENT COMPONENTS:
=========================
Element Agent Name Host Name Port PID Admin Status
----------------------------------------------------------------------------
Agent-1 localhost LAN 16113 Running Running
Agent-2 localhost LAN 16117 Suspended Suspended
SNMPAgent-1 localhost LAN 16963 Running Running
Please note:
The database server, voyager nemcore services, message broker, security manager, rabbitmq services and procwatch are not affected by the nemstart or nemstop sequences and should always be running.