NCM wish list

jon0966

Please find my wish list for NCM....   :-)

 

1.   Multi-level
grouping of devices.  Our  implementation of NCM groups network devices by
region, but optimally we need to also sub-group by site name.  When 2500+
devices are added within NCM, and a region may have 500+ devices, scrolling
through 500+ devices to locate a single device is expected to be more resource
intensive than desired for this process.

 

2.     
Ability to add new devices via the
webui instead of logging directly into the NCM server via
RDP.

 

3.     
Enhanced logic when adding new
devices for SNMP and console input (telnet or ssh).  For example, when a new
device is added to NCM, the SNMP string must be specified manually.  If that
SNMP string is incorrect, the add device process fails.  NCM currently has the
ability to store multiple snmp strings, and KBR has four SNMP strings specified,
so it would be extremely helpful if when adding a new device, that NCM attempts
to connect first with the default SNMP string, and then try the second SNMP
listed within NCM, and so on down the list.

 

4.     
Improvements on Cisco Card Data
Serial # inventory discovery.

 

5.  Security Roles.  I would love to be able to limit a user designated as "Engineer" to only specific devices instead of global.

 

 

Thanks,

 

 

 

Jonathan

 

 

chris.lapoint

1.   Multi-level grouping of devices.  Our  implementation of NCM groups network devices by region, but optimally we need to also sub-group by site name.  When 2500+ devices are added within NCM, and a region may have 500+ devices, scrolling through 500+ devices to locate a single device is expected to be more resource intensive than desired for this process.

Thanks, I've got this on the list.   Are you using the website or the NCM desktop client?

2.      Ability to add new devices via the webui instead of logging directly into the NCM server via RDP.

Web-based node management is definitely on our roadmap.   When you say webui, do you mean the NCM integration module (for Orion NPM) or do you mean the standalone NCM website?

3.      Enhanced logic when adding new devices for SNMP and console input (telnet or ssh).  For example, when a new device is added to NCM, the SNMP string must be specified manually.  If that SNMP string is incorrect, the add device process fails.  NCM currently has the ability to store multiple snmp strings, and KBR has four SNMP strings specified, so it would be extremely helpful if when adding a new device, that NCM attempts to connect first with the default SNMP string, and then try the second SNMP listed within NCM, and so on down the list.

Great idea.   I'll add this to the list.   BTW, even if SNMP fails, you can add the device anyway and change this in the device details.

4.      Improvements on Cisco Card Data Serial # inventory discovery.

Can you elaborate on this?

5.  Security Roles.  I would love to be able to limit a user designated as "Engineer" to only specific devices instead of global.

Ok, I think this answers my question above.   If you have Orion NPM, you can install the NCM integration module and it will respect Orion NPM node limitations and account view limitations.   We're looking at expanding this capability to NCM standalone in the future.