Can you please provide more detailed example of correctly and incorrectly displayed connection point (maybe with some screenshots) together with mac address table records?
Best regards,
Victor
Best regards,
Victor
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: mialkfl on May 05, 2014, 10:48:12 AM
1. Event Processing: We have set the "ThresholdRepeatInterval" under Server Configuration to 0 and the "Repeat event" of all DCIs' Thresholds is set to "Use default settings". According to the Thresholds' event, an email is sent as an Action to our teammailbox. Due to using Templates for all vessels, there are a few vessels for which we are monitoring services, which are not installed yet. Against our expectations we receive an Email-Alert every week, which should be only once.
Quote from: mialkfl on May 05, 2014, 10:48:12 AM
2. Configuration File Policies: As we have a standardized structure for every vessel, some nodes are disabled for some vessels. If we try to install a policy on one of these nodes, an error occurs, because no NetXMS client is installed on the disabled nodes and therefore the necessary action is not available. This is especially tricky, when we would like to install a policy on all nodes. Maybe there is a possibility to only link disabled nodes to the policy and install the linked policies, when the node is enabled?
3. Package Manager: Due to communication via satellite, we are facing a lot of connection issues. If we are distributing a new NetXMS Client Package via Package Manager to all of our vessels, only approx. 20% will be completed successfully. In the Package Deployment Monitor we have no possibility to restart failed deployments and if we restart the Deployment via Package Manager for all nodes, the deployment runs for every node (no matter if it has been deployed successfully before or not) again. So finally we don't have a general overview, where the packaged has been deployed successfully and where we do have to restart the deployment.