The Conversations View for a node does not contact the preferred RMON agent of the segment even if the SNMP service is stopped on the node
Severity:
ZENworks 7 Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The Conversations View always contacts the local machine if the RMON service is implemented on that agent and it is discovered. If it does not contact the local machine, it contacts the preferred RMON agent of the segment to which it is bound. If the RMON service or the agent is stopped, the Conversations View continues to contact the local agent and not the preferred RMON agent of the segment.
Action:
Use the Database Object Editor to remove the RMON service and Lanz Agent discovered on this node and relaunch the Conversations View.
Unable to add nodes to monitor Nodes for Inactivity.
Severity:
ZENworks 7 Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The INM View always contacts the preferred RMON agent of the segment. It adds the MAC address of the selected nodes to the RMON service. Sometimes the RMON service fails to add the node addresses provided by the INM view. Because the INM view refers to the RMON service for getting the list of nodes and respective status, it fails to add nodes.
Action:
Reload the Traffic Analysis Agent on the preferred RMON service.
The Conversation View for nodes fails to come up if one of the IP Addresses is disabled
Source:
ZENworks 7 Server Management with Support Pack 1; Management and Monitoring Services; Traffic Analysis.
Possible Cause:
This occurs when one of the interfaces in a multiple NIC is down.
Action:
Use the DBOE to remove the interface that is down, then relaunch the Conversation View.