In the 7.1 release of Monitor Solution for Servers, one of the key features which was introduced is multiple Remote Monitoring Server (RMS) support. Along with this feature comes the following items which are to be considered during implementation:
By default, the Monitor Service is installed on the Symantec Management Platform (SMP) server. In a simple environment where there is a single subnet and physical / virtual site (or no sites have been defined), having a single RMS installed on the SMP server may be suitable and will function properly out of the box. However, if the environment has multiple subnets and sites and / or multiple RMS's are desired, the following steps should be followed:
First, determine what type of remote monitoring topology is desired:
By default, both the Task and Monitor services are installed on the SMP server. This poses as an issue for centralized monitoring: You must apply all sites and subnets to the Site Server where the Monitor Service resides (this is required as the RMS will only monitor those resources within the sites that are applied to the Site Server). However, you may not want all sites and subnets applied to the Task Service (e.g. any resource could potentially try to get its tasks from the SMP server). This being the case, you'll likely wish to relocate either the Monitor Service or the Task Service from the SMP server to another Site Server. The following steps apply to relocating the RMS to its own Site Server:
In most environments where there are multiple sites and subnets, it will be preferred to have a Site Server hosting both the Task and Package services designated to each site. With this type of distributed setup, the RMS can be conveniently added to each Site Server to ensure all resources are monitored as well as to load balance the agentless monitoring. The key detail to note about this type of configuration, is that each RMS will only monitor those resources which reside within the site which is associated with its Site Server. The following diagram illustrates the distribution of resources amongst multiple RMS's if an agentless policy is applied to "All Computers":
The following steps apply to deploying the Monitor Service across multiple Site Servers (it is assumed that all subnets have already been associated with their appropriate site):
Site-based with redundancy
This configuration is more complicated and involved, however it is not without its advantages. This setup is beneficial for 2 primary reasons: a) Multiple vantage points for critical resource monitoring, and b) Agentless monitoring of RMS health and status. Discretion must be used during implementation of this design as communication over the network as well as data storage will both be increased. Additionally, duplicate alerts will occur since rules will be triggering from multiple RMS sources. The concept of this approach is that each RMS will monitor the resources in its local site and / or a different site where it does not reside. The following diagram illustrates this:
Note that such a topology is not suitable for Task Service and Package Service implementations. This being the case, each RMS must be installed on its own independant Site Server. Also note that most networks were not designed for such concepts. Implementation is very similar to the steps outlined for the Site-based configuration with the following adjustments (it is assumed the steps from the Site-based instructions have already been followed):
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.