Wednesday, September 28, 2011

NPC Sites and Groups 1 of 7: The Philosophy

Part of a series of posts.  To see all posts, click here.

A while ago, I started building a document that detailed the best practices I had developed around groups and sites in NPC.  I applied to present this at CA World this November, but the new direction of CA World wasn't compatible with this type of presentation.  As a result, I'm going to post my findings here.  I'll post the sections individually then maybe post the whole thing later as a single document.  I've also built a little applet (using my limited programming skills, so be nice) that takes a majority of the manual work out of following these best practices.

The Philosophy

After having setup countless instances of the NetQoS suite of products and after the most recent release of SuperAgent, I’ve stumbled upon a discovery that I think is significant.  Frankly, I’m surprised no one at NetQoS has realized or built on this relationship.  Perhaps they have, but due to the recent evacuation of NetQoS talent from CA, no one has stepped in to fill the gap.  This is why I’m writing these posts.
This discovery came after being tasked to revamp the group structure in a NetQoS Performance Center (NPC) installation.  At the same time, a request came in to clean up the locations in Unified Communications Monitor (UCM).  It was then, that I noticed that the information required for both was essentially the same.  I needed to know what locations we had and what subnets were in use at those locations.  Not long after that, I realized that the same information is needed, although in a slightly different form, for SuperAgent and NetVoyant configurations.
Therefore, in order to configure four of the NetQoS products, one set of core data is required.  There are obviously other pieces of the configuration that are required to get the best monitoring.  In these posts, I’ll detail how the Sites/Networks list can be used to best configure the core NetQoS products.

To be continued...