Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Essentials edition. Server & Application Monitor (SAM) is also available in a standalone module.

CiscoWorks LAN Management Solution

This SAM application monitor template assesses the status and overall performance of a CiscoWorks LAN Management Solution.

This template was tested on CiscoWorks LAN Management Solution 4.

Prerequisites

WMI access to the target server.

Credentials

Windows Administrator on the target server.

Component monitors

Service: CiscoWorks ANI database engine

This monitor returns the CPU and memory usage of CiscoWorks ANI database engine. This service performs Data Collection for purposes of build a layer 2 network topology. Also handles all Network Topology, Layer 2 Services and User Tracking client requests.

Service: CiscoWorks Daemon Manager

This monitor returns the CPU and memory usage of CiscoWorks Daemon Manager. This is administrative service for CiscoWorks processes.

Service: CiscoWorks RME NG database engine

This monitor returns the CPU and memory usage of CiscoWorks RME NG database engine. This service stores all Inventory and Configuration data pertaining to inventory and Syslog messages, but only references config files and software images stored outside of the database.

Service: CiscoWorks Tomcat Servlet Engine

This monitor returns the CPU and memory usage of CiscoWorks Tomcat Servlet Engine. This is the main application engine for CiscoWorks running Java servlets, and compiling and serving Java Server Pages.

Service: CiscoWorks Web Server

This monitor returns the CPU and memory usage of CiscoWorks Web Server (Apache).

Service: CWCS Cmf database engine

This monitor returns the CPU and memory usage of CiscoWorks Cmf database engine. This service stores job data, DCR data, and OGS data for Common Services, Fault Management, and Network Topology, Layer 2 Services and User Tracking. Reinitializing this database will remove all devices from all applications.

Service: CWCS rsh/rcp service

This monitor returns the CPU and memory usage of CiscoWorks rsh/rcp service. This service is responsible for using Remote Copy Protocol and Remote Shell.

Service: CWCS syslog service

This monitor returns the CPU and memory usage of CiscoWorks Syslog service.

Service: CWCS tftp service

This monitor returns the CPU and memory usage of CiscoWorks tftp serveice. This service is responsible for accepting tftp connections.

Service: DFM dfmEpm database engine

This monitor returns the CPU and memory usage of DFM dfmEpm database engine. This service serves database connections for storing and retrieving Fault Management alerts and events.

Service: DFM dfmFh database engine

This monitor returns the CPU and memory usage of DFM dfmFh database engine. This service stores archived Fault Management alerts and events for 31 days.

Service: DFM dfmInv database engine

This monitor returns the CPU and memory usage of DFM dfmInv database engine. This service stores CiscoWorks copy of Fault Management inventory.

Port: SSH

This component monitor tests the ability of a Cisco SSH to accept incoming sessions. By default, it monitors TCP port 22.

Port: Remote Copy Protocol

This component monitor tests the ability of a Remote Copy Protocol (RCP) to accept incoming sessions. RCP allows users to copy files to and from a file system residing on a remote host or server on the network. By default, it monitors via TCP port 514.

Port: HTTP server in SSL mode

This component monitor tests the ability of a CiscoWorks HTTP server in SSL mode to accept incoming sessions. By default, it monitors TCP port 443.

Port: HTTP Protocol

This component monitor tests the ability of a CiscoWorks HTTP Protocol to accept incoming sessions. By default, it monitors TCP port 1741.

Port: OSAGENT

This component monitor tests the ability of an OSAGENT to accept incoming sessions. This is one of the base components needed for certain inter-process communication functions. By default, it monitors TCP port 42342.

Port: Log Server

This component monitor tests the ability of a Log Server to accept incoming sessions. By default, it monitors TCP port 8898.

Port: DynamID authentication (DFM Broker)

This component monitor tests the ability of a Device Fault Manager (DFM) broker service to accept incoming sessions. By default, it monitors TCP port 9002.

Port: Ajp13 connector used by Tomcat

This component monitor tests the ability of an Ajp13 connector used by Tomcat to accept incoming sessions. By default, it monitors TCP port 9009.

Port: ANIServer

This component monitor tests the ability of an ANIServer to accept incoming sessions. ANI service performs Data Collection for purposes of build a layer 2 network topology. Also handles all Network Topology, Layer 2 Services and User Tracking client requests. By default, it monitors TCP port 43242.

Port: Event Services Software (ESS) Listening

This component monitor tests the ability of an Event Services Software (ESS) to accept incoming sessions. Event Services Software (ESS) is an asynchronous messaging service that provides a messaging infrastructure based on a publish-and-subscribe paradigm. It enables distributed, loosely coupled interprocess communications. By default, it monitors TCP port 42350.

Port: CMF Database

This component monitor tests the ability of a CMF database to accept incoming sessions. CMF database stores job data, DCR data, and OGS data for Common Services, Fault Management, and Network Topology, Layer 2 Services and User Tracking. By default, it monitors TCP port 43441.

Port: RME Database

This component monitor tests the ability of a RME database to accept incoming sessions. RME database stores all Inventory and Configuration data pertaining to inventory and Syslog messages. By default, it monitors TCP port 43455.

Port: ANIDbEngine

This component monitor tests the ability of a ANI database engine to accept incoming sessions. By default, it monitors TCP port 43443.

Port: Fault History Database

This component monitor tests the ability of a Fault History Database to accept incoming sessions. This database stores stores the history of DFM events and alerts from the past 31 days. By default, it monitors TCP port 43445.

Port: Inventory Service Database

This component monitor tests the ability of an Inventory Service Database to accept incoming sessions. This database stores all inventory information. By default, it monitors TCP port 43446.

Port: HUM Database

This component monitor tests the ability of a HUM database to accept incoming sessions. This database stores information about network elements (such as CPU, memory, interfaces/ports, and links) and provides historical reporting. By default, it monitors TCP port 43800.

Port: IPM Database

This component monitor tests the ability of a CiscoWorks Internetwork Performance Monitor (IPM) database to accept incoming sessions. This database stores network response time and availability of network devices. By default, it monitors TCP port 43820.

Port: Event Promulgation Module Database

This component monitor tests the ability of an Event Promulgation Module Database to accept incoming sessions. This database stores Fault Management alerts and events. By default, it monitors TCP port 43447.

Port: SOAPMonitor

This component monitor tests the ability of a SOAP monitor to accept incoming sessions. Cisco SOAP-Performance Monitoring APIs service allows you to use performance monitoring counters for various applications through SOAP APIs. By default, it monitors TCP port 50001.

Events: CRM log events

This component returns the number of warning and error log messages of CRM log service.

  • Source name: crmlog
  • Log file: Application

This monitor should be zero at all times. If not, you should investigate this in the Windows Event Viewer.

Events: CRM tftp events

This component returns the number of warning and error log messages of CRM tftp service.

  • Source name: crmtftp
  • Log file: Application

This monitor should be zero at all times. If not, you should investigate this in the Windows Event Viewer.

Events: CRM rsh events

This component returns the number of warning and error log messages of CRM rsh service.

  • Source name: crmrsh
  • Log file: Application

This monitor should be zero at all times. If not, you should investigate this in the Windows Event Viewer.

Events: CRM Daemon Management events

This component returns the number of warning and error log messages of CRM Daemon Management service.

  • Source name: CRMdmgtd
  • Log file: Application

This value should be zero at all times. If not, you should investigate this in the Windows Event Viewer.