SLNetClientTest tool advanced procedures
The procedures below can be applied to troubleshoot issues. However, be very careful when you apply them as they can strongly influence the functionality of your DataMiner System.
- Aborting a running Automation script
- Changing the grace period for the SLNetCom Notification thread
- Changing the number of records in the protocol cache
- Changing the service template child element and child service limitations
- Checking or modifying the settings related to a Refused DMA state
- Clearing alarms from the SLNet event cache
- Comparing the views on two Agents in a DMS
- Configuring how long alarm statistics are kept in memory
- Configuring SMTP
- Configuring the frequency of smart baseline calculations
- Configuring trend caching
- Creating an enhanced view
- Debugging the dataminer.services connection
- Disabling automatic NATS configuration
- Disabling replication buffering
- Editing the connection string between two DataMiner Agents
- Enabling or disabling protocol buffer serialization
- Fine-tuning NATS settings
- Fine-tuning the CPECollectorHelper API timeout
- Forcing file synchronization between DMAs
- Generating SMIv2 MIB files
- Having RCA chains updated by the DCF engine
- Increasing the maximum upload size for upgrade packages in a DMS
- Making DataMiner Cube ignore view updates
- Managing base subscriptions
- Managing scheduled tasks for maintenance of a Cassandra database
- Managing trend patterns
- Modifying the engine ID of a DMA
- Reinitializing Resource Manager
- Removing a DOM manager
- Removing references to items that no longer exist
- Setting the TTL for database records
- Specifying credentials for a shared backup path for Elasticsearch
- Triggering a midnight sync for a DOM manager
- Triggering and managing user-defined APIs