gfaircloth

Yes this should do the trick according to the NTA documentation, but I have this issue with ASR9K's and I have tried this NTA option but it does absolutely nothing. This is not a Cisco issue. It is absolutely best security practice to allow management protocols only on out of band interfaces. 

Update: I have tried Firefox and it works perfectly. Absloutely nothing that has been suggested with Internet Explorer works.

Same issue here except I cant keep it running longer than about a minute. Service stops continuously and it does in fact start as I see messages logged but it dies immediately thereafter. I should have known better than to try something that was this new, so my bad. I also disabled the NCM syslog server even though it was…

This is the error message I get when trying to validate the Orion server connection from the NCM server. This is the screen previous to the error where you enter the connection information. I have always used the IP and not the hostname so its not DNS related. And this is what you get when you try a browser on the NCM…

Here is my event log and its not pretty. 2015-09-15 14:55:18 DNS Resolver: Unknown DNS server response type. Unable to resolve IP address '' (DNS Server Response Code = 0) 2015-09-15 14:55:18 *** INTERNAL PROGRAM ERROR - Please contact http://www.kiwisyslog.com/support/ *** 2015-09-15 14:55:18 Service Version 9.5.0.332 |…

Got it figured out. All good now.

Any way we could write a custom item ourselves like ${Pause} to get this done sooner. This is causing quite a few issues when we do scripts on slower older IOS devices. Don't know if NCM gives you the ability to create your own however. Thanks.

Ok I installed that and then requested a manual scan and the hostnames are still there so that seems to have fixed the issue. Thanks so much for the quick response. Jerry

Was this ever resolved? Many of us have the same issue and have much less traffic so it is NOT related to traffic only.

Thanks Francois, if you would like me to test anything or have any more questions feel free to contact me.

Thanks Denny for the fast response. This should get me fixed up until the next release.

Thanks Matt, I looked into the reverse DNS that Sean had mentioned and sure enough that was fouled up on one of the servers but after fixing that it did not seem to help. I looked into the log file and definately there is an issue with the communications. Have a good weekend I will open up a case on Monday I guess. Snippet…

Thanks! OK I fixed the license issue and ran the services reconfig and it still does the same thing. So I rebooted the NPM server just to make sure everything was started cleanly, still can't upgrade the NCM server. And I can still login to the NPM server from the NCM server with a browser using the same exact IP and…

This looks to be my issue, have no idea how to fix it yet. About to try a dedicated account for the service. 2015-09-15 14:55:18 DNS Resolver: Unknown DNS server response type. Unable to resolve IP address '' (DNS Server Response Code = 0) 2015-09-15 14:55:18 *** INTERNAL PROGRAM ERROR - Please contact…

Thanks for the quick reply. Yes I am on 9.1 SP5. When I click OK the add subnet window seems to be active and accepts input however anything I do in the CIDR field seems to cause an error. The mask and parent IP address fields are always greyed out possibly by design however the CIDR field does not change the mask so hence…

UPDATE It turns out the problem was related to some data that was still in some of the VoIPCCM... tables from some call managers that no longer were being monitored. After truncating those tables the install worked fine. Many thanks to Matthew Harvey in tech support for figuring this out. 

VSS Monitoring 12x4 Distributed Gigabit Ethernet Tap 1.3.6.1.4.1.21671.1.119

Well turns out that is not the issue with my service. Actually when I install this hotfix I can no longer use the KIWI console as it thinks I need to activate my license which turns out to already be activated so it fails to re-activate it. Anyway we are back on the investigation trail on what's causing the parsing error…

Awesome thanks! I have been working on this all day with Chris Foley in support and we have it narrowed down to a parsing issue and were just about to do a couple more tests but I will try the hotfix asap. Thank You!!!!!

Geff did you ever get this resolved. I have exactly the same problem. And it is intermittent. So I don't see how there could be any kind of configuration issue. Maybe it is a DNS timeout or something not sure.

Wow that seems so easy. I guess I was making it too complicaed by telling it to ignore the preceding whitespace and start at the beginning of a line. So I guess this means the whole config file is treated as one big string in NCM? Thanks for the help

Hotfix 2 is out that corrected this issue for me.