SLNetClientTest tool diagnostic procedures
The procedures below can be used to retrieve data from a DataMiner System. However, be very careful when you apply them, as the SLNetClientTest tool allows actions that can have far-reaching consequences on the functionality of your DataMiner System.
- Activating verbose Correlation logging
- Changing the log levels for a log file
- Checking a hyperlink filter
- Checking whether protocol buffer serialization is enabled
- Consulting connection details
- Consulting Correlation information
- Consulting license information for a DMA
- Consulting replication information for other DMAs in a DMS
- Consulting the trend data inspector
- Creating a dump file for a particular process
- Debugging callback timeout errors
- Exporting data to a CSV file
- Inspecting parameter table rows in SLProtocol and SLElement
- Inspecting the active replication buffers
- Inspecting the contents of a table parameter
- Inspecting the parameter notification queue
- Inspecting the SLNet event subscriptions
- Inspecting the stack sizes in SLNet
- Requesting a list of active merge actions for a protocol
- Requesting an estimate of the number of rows for a storage type in the database
- Requesting information about pending incoming events
- Requesting QAction metrics
- Retrieving connection info for a particular element
- Retrieving DCF debug information
- Retrieving information on open GQI sessions
- Tracking DMA communication
- Verifying sync rules
- Viewing SLNet calls being sent
- Viewing the connection timeout states of an element
- Viewing the memory usage of elements, parameters, and tables