Comments
-
If we actively worked on it for NCM now, I would mark it. Jiri
-
Hi, While merging the databases, we also plan to optimize NCM DB. We are very well aware of the performance concerns. Standalone NCM will be supported. When you have separate NCM now, there are technically two DB's, too -- the NCM one and the Core/"NPM" one. Regards, Jiri
-
I would like to announce that UDT 3.0 Beta 2 is now available. The difference to Beta 1 is that Beta 2 is more thoroghly tested and issues from Beta 1 have been fixed. If you are interested, please sign up here.
-
Hi, It is a feature request. We will consider it in future releases but can't promise any fixed dates. Jiri
-
Hi, This is high on our priority list. Jiri
-
Hi, We don't plan to merge these two products from technical point of view but we definitely plan to improve the integration from user point of view. Regards, Jiri
-
Thank you for your feedback. It's good to have exact information like this. Feel free to post more. Jiri
-
Core doesn't plan to implement this feature.
-
Hi sgreath, You probably wanted to ask whether you can install NCM on the secondary NPM poller and have them integrated. The answer is No. You have to install primary NCM on the primary NPM machine. Regards, Jiri
-
Unfortunately, it's currently not possible to change the font. Jiri
-
Hi, I agreed with your colleague Sanjeev to test SRM 6.3 RC. (You are on cc.) Official releases normally follow in a few weeks after the Release Candidate. Jiri
-
I've contacted you offline. Jiri
-
Hi, If you are sure that you are trying to install the same version of NCM additional pollers as what's installed on the main Orion servers, then please open a support ticket as the problem is not clear without further details (diagnostics). Regards, Jiri
-
We intend to improve the documentation on different Reg-Ex flavours used in NCM.
-
Thanks for the feedback. Is there anything else you'd like to tell us? Regards, Jiri
-
VPLEX is definitely a high priority for us, although I can't share more details on the time lines. It is not an easy device to add due to the nature of its API.
-
I've just sent you the details. Jiri
-
I'm glad it's useful.
-
You're welcome
-
This was fixed in NCM 7.2.2. Jiri
-
Have you updated the inventory?
-
It was not decided that random sorted reports was the intention. The priority of this request just hasn't become high enough for it to be implemented. While it would certainly be great to be able to implement all request and fix all bugs, in reality, we have to prioritize.
-
Just sent you the bits. Jiri
-
I believe you could further improve the template by replacing the IP address with ${StorageAddress} macro and filename with ${StorageFilename}. Jiri
-
Fair enough. Just please make sure the part numbers are included. You can send it to me via e-mail: I'm curious to see the results myself. Regards, Jiri
-
Jon, You can give them my contact details. Have you tried the tool recently again? Jiri
-
Hi jeffnorton, I admit I haven't addressed the whole content of your posts because I focus on the most important issue -- data quality. I'm trying to persuade you to work with us (through support) to find out why your NCM doesn't show the right (green) suggestions when it should. I'm ready to have a call with you on the…
-
One step is migrating NCM from the standalone server to the Orion/NPM server. Another step is migrating device templates from disk to the database. The latter step is done during the upgrade to 7.4. But if you upgrade from 7.2.2 directly, 7.4 (being installed on the Orion/NPM server) won't see the device templates on the…
-
Do you mean on Cisco end?
-
Leny, I'm glad to hear that. Hopefully this thread will be useful to others with the same problem. Thanks, Jiri