NCM integration with NPM Node List limitations.

Question

NPM 9.5 SP4 and NCM5.5.1    Integration worked great between my stand alone NCM server and four NPM servers.   One issue:  from the NCM module in NPM, when selecting a Node list grouped by NodeGroup with more than a hundred or so devices... times out and will not display the nodes with thier configs.    Example, I have regional node groups with up to 800 routers per group,, and unable to expand to show the nodes with thier configs... times out in error.   If I select a 'smaller' node group of 50 routers, works great.   If there was a way to filter node groups same as Regions, Depts. buldings etc like in NPM, (Ajax view node tree), then would not have this issue.   In NPM I have the same Regions that match the NCM NodeGroups, but filter the node tree view with Dept. and CPE codes.

chris.lapoint · Answer

Cool, that's certainly the right workaround!    As noted above, we're looking at providing quick select and multi-level grouping from the NCM module view so you'll be able to give full access again at a later time.

juan_kaliente · Answer

${SysName}.    I could break down the Node Groups into Alphabetical extensions works.. but what I ended up doing is to take out the NCM module access for operations, and put in Last XX Configurations and Change Config Report on the Node Details in NPM.  Works great !!

chris.lapoint · Answer

Integration worked great between my stand alone NCM server and four NPM servers.

That's great to hear!

One issue:  from the NCM module in NPM, when selecting a Node list grouped by NodeGroup with more than a hundred or so devices... times out and will not display the nodes with thier configs.

We're looking a multi-level grouping like in the Orion NPM All Nodes resource.    In the meantime, it's likely that the macro parsing may be slowing down the listing of nodes in your NCM All Nodes resource.   In your device details, is Node Name a static value or are you using ${SysName} to fill this in?