NCM - Node Grouping

jgardner

Good afternoon,

After speaking with support on this issue within NCM, we have determined that the only way to best fit the following obstacle would be to use custom properties.

For example:

You have sites in multiple regions and within NCM you would like to customize the view but there are only three levels in which you could do it and using custom properties would be more of a challenge in order to fulfill the gap to design in what an organization would be looking for.

Right now under the view you can customize the view (home page) for up to three levels which by default is Vendor and Status and X.

However, being an MLP let’s look at the following example:

1. Orion Instance 1 (Web Console)

• Vendor
• Region A
  1. a.     Site A
     1. Subsite – A (Within these sites it might break down further depending on the naming convention or one would want to further breakdown by equipment at each location, but this is all dependent upon management etc. This is just an example)
     2. Corp
     3. LAN
     4. Misc.
     5. ETC.
• Vendor
• Region B
  1. a.     Site A
     1. Subsite – A (Within these sites it might break down further depending on the naming convention or one would want to further breakdown by equipment at each location, but this is all dependent upon management etc. This is just an example)
     2. Corp
     3. LAN
     4. Misc.
     5. ETC.

As on can see that you can only filter up to three levels, however, if one were an MSP/ Multi Service provider you can see their dilemma.

An example of this would be to expand all nodes within an equipment ring, and having to scroll or use CTRL + F to find the note (not that this is an issue). Thought, from an organization prospective it would be more fluent and intuitive to filter object based on the needs and goals of the organization in order to be more “efficient” at network management. In addition, it could also be used to run daily/incremental/differential/full backups based on the Region, Site, Sub-site, etc.

I have also taken the time to use custom properties but it still will not accomplish in which the organization is trying to effectively and efficiently manage the nodes within certain regions, sites, sub-sites, etc.

This may have been brought up before, however, I have not seen any other threads that relate to this type of specific issue. If there is does anyone know of the thread/steps to resolve the issue (not just temporary?)

Thanks