Hide this message
Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at firstname.lastname@example.org
This article provides information on NCM not being able to connect to nodes after upgrading to NCM 7.3 or later.
Prior to NCM 7.3, the use of Additional Polling Engine was either not supported or was optional and in most installations not being used. This would mean NCM would work from the Primary NCM server for the connection to devices (either Primary Polling Engine or designated NCM server).
A lot of the time an ACL was in place to permit the vty, tftp, ssh, telnet and so from the NCM server specifically and this could be accomplished with a single ip address
After the introduction of NCM 7.3, not only were the databases merged but also:
If there was an ACL or even a Wwindows Firewall that was set up to permit the connection from NCM, it is likely the ACL and/or firewalls would need to be modified to allow connections from all engines involved or if NCM was moved to a different server.