fcaron

For NPM only: Correct, HotFix 2 is included in SP1, no need to re-apply it (if you do, you will likely have error messages). Hotfix 1 is specific to what netlogix describes above and unless you applied it before, it's unlikely you need it now. Hope this helps. Francois Caron - Snr Product Manager

Hi cnorborg, Nice usability requests. I recorded 1, 3 and 4 (51740) since #2 is in 6.1 already (tks Questionario for pointing this out)

Hi Can you open a support case, we will investigate Opened (44057) Francois Caron - Sr Product Manager NPM

Do your symptoms look like these:

I'll ping you off-line

Tks Steve and Network_Guru and others for your votes. We are recording them (62878)

Recorded this enhancement request (69274)

This is a well-identified requirement, unfortunately, Cisco's API (CDS) is not publically available (internal and HW partners). This API is necessary to map automatically discovered devices with vulnerability, EOL info...

Will add to the list. (42607)

All, Tks for input. This definitely adds weight to the requirement (16938) and increases our chance to deliver it in a future release. I also noticed a comment about status, and wanted to attract your attention to this Juniper KB, which might be related and help:…

I will be contacting some of you in this thread, and we'll see how we can be creative. Tks for the input

I have asked and it does not look like we have encountered this issue in the past. Did you open a case for this? Might be worth doing it and loading diags so we can take a look.

This similar issue (on NPM) in another thread, but nothing in our bug database that I could find.

I have seen this happening in 3 cases (not specifically with NPM): - OID reporting octets in/out are wrong (IOS bugs) - unlikelly but possible. - You need to flag the devices that support 64 bits counter . By default NPM considers interfaces and ports have 32 bits counters and on fast interfaces, these 32 bits counter wrap…

Thanks to both for your input, recorded as enhancements. We are working on a few enhancements for the wireless area, such as improving the search, improve some formatting linked to IP V6 (among others), extended support for new device types as well axs bug fixes of course.

HF1 is not generally applicable and you probably don't need it, this HF is specific to a particular use case, related to changing the default e-mail format for email alerts. Your sequence is good up to SP1. Francois Caron - Snr Product Manager

Have you tried modifying the template so it outputs the PWD twice instead of only once?

Posted here. As always, we appreciate your comments as well as your improved versions of the template

Hi Sol, Have you contacted support about this? If not, I suggest you do so, after running the Diagnostics tools. If you are not familiar with this tool, you can find guidance here: Francois Caron - Snr Product Mgr.

Hi Pyro13g, Are you suggesting improvement (to this window, for ex) that would allow to define the retention policy based on the X last stored config? If yes, why is the second control not meeting your requirement (Delete All Except the X most current)? Can you also elaborate on what you mean by "Internal and External"? A…

No need to do that. We have an open enhancement for supporting SSG and ISG sub-interfaces (16938). Adding one more vote to it. Jiangbo, can you say how many of these ISG devices and sub-interfaces you have in total? This enhancement is not confirmed yet in any release but we are looking at it.

Right, as rschroeder eluded to you can see interface data in the Interface tab of the Device detail or in the Interfaces reports. See both snaphots. Does this help?

Tks for input, recorded as enhancement request (64114)

Hi Byron, There is no way to limit access to specific operations, other than what the normal node-based limitations allow. In other words, if a user has access to a node, he/she should be able to see all operations sourced from this node. If not, operations on this node will not be visible.

We are trying to find dev time to lok into this, but as this is a free tool, it's difficult to assign hi priority, especially during end of year period. Can you send us the pcap? This might facilitate

Hi Charlesdf22, NCM 6.1 (available today) can show the violation detail when the user clicks the violation icon. This is from the WEB interface (NPM integration). Is this what you are looking for? If not, can you elaborate, and we can open an enhancement request.

Hi, Looking forward to seeing how others operate in this area of the product. In the mean time, it is well identified (97581) that there is a requirement to be able to manage a node in NCM but not monitor is at all in NPM (in the case of both being integrated). For some, it is a temporary state, like in your case, for…

Biboyeli, This thread might help

Never seen that. I'll let other chime in but I would recommend opening a support case, Byrona. I will also ask around and post here if I find something. Something you can try, is polling these OIDs against these devices, with an SNMP tool and see what the device responds with, now (i.e. after the reboot). Won't tell you…

We just introduced a new product which covers this: FSM, Firewall Security Manager, more here.