jhynds ✭✭✭✭✭

Hi Mike, I'm not overly familiar with the NX-OS, but the 'logging level local2' looks incorrect. It should be set to a level as outlined here. Can you also use the checklogs tool within LEM to confirm that the NX-OS logs are actually hitting local2. If the connector is not detecting NX-OS logs in local2, it sounds like the…

It can be done via your Customer Portal and the steps for offline activation are outlined here: Success Center If you need any additional help just let me know.

Patch Manager 2.1.6 is now available and includes support for Windows Server 2019.

PM sent to arrange a log sample

I agree with Justin, that it sounds like an Active Response is being triggered when a user initiates an RDP session. I'd recommend raising a Technical Support ticket​ - they can drill into the rules to determine if an active response is triggering, as well as the LEM appliance and agent logs to determine the root cause.

Will send you a DM to gather some additional information.

You will not need to purchase an LM license in order to configure alerting based on syslog/traps. As you mentioned, the rules from the legacy tools will need to be manually re-created within LM, but you will be able to alert on those rules in LM. Of the 75+ rules that your customer has, they will be able to send emails and…

Unfortunately SQL Server 2017 is not yet supported by the SQL Auditor but is certainly on our radar. Would you have any objections to SQL Auditor moving to Extended Events or is Profiler still your preferred method to monitor SQL?

Hi Liam - yes, we are looking for NPM/Orion based syslog data. Even if you are using Kiwi to take the majority of the workload, if you have syslog/trap rules configured in NPM that analyzes the data forwarded from Kiwi, that will still be helpful.

Thanks for your input Marc, it's very helpful. Would really like to discuss in more detail with you. Will send you a DM to arrange a call.

Thanks Mike. Do you happen to have a rough idea of the Event per Second rate of your chatty device(s)?

That was exactly the root cause. We've updated the package which changes the File Version within the Installed Rule to 8.0.202.8

You can easily add the message body of the log entry by using the Log Entry Message variable within your e-mail alert. Other variables include the rule name that caused the alert to trigger and the hit count of the rule. Is this the main obstacle you were running into or are there some additional limitations? If you'd like…

By default, when log data is received by a node, that node will consume an LM license. However, this can be overwritten and you can exclude nodes from automatically consuming a license if log data is received. You can also add/remove nodes from the LM license pool, in a similar manner to NCM. It is not possible to go over…

Yes, Log Manager can support greater than 1,000 nodes, however you will need to speak with your Account Manager to obtain pricing. Log Manager supports approximately 90 million events per day, so you will need to keep that in mind when transmitting logs from a high number of nodes.

Log archiving is not currently a feature of Log Manager, however you can set a retention period for syslog up to a maximum of one year. Your syslog data will then be persisted in the SQL database for a full year. The size of the database will of course depend on the volume of syslog you are sending to LM. If you are…

If a node is put into an unmanaged state either manually or on a scheduled basis, both syslog and trap messages are discarded until the node is managed again. We are currently working on support for Orion alert integration which will include support the Mute functionality.

Certainly a great idea and something I've heard from other users too. I've created a Feature Request which you can vote on here:

We firmly believe that syslog and traps are an essential part of any network monitoring tool and we fully intend to always include a basic level of syslog & trap functionality with NPM. We also believe that there is strong demand for more extensive log management coverage. We have some very exciting features planned for…

DM sent to determine why LM isn't appearing for you.

Log Manager currently supports NCM Real-time Change Detection alerts, however Orion Alert integration is not currently support. We are currently working on Orion Alert integration as a top priority which aims to satisfy many of comments within this feature request: SNMP Traps and Syslog Can Raise an Advanced Alert in NPM

Hi Adrian - the more logs we get, the better. So, if you would like to submit a sample, please proceed and I will arrange your points.

Hey Bill, Can you confirm if your SMTP host is Exchange or Office 365? Do you know which versions of TLS are running on your mail server?

Happy to announce that the Patch Manager catalog now includes Flash PPAPI installers. -Jamie

Hi Steve - Flash 26.0.0.131 is now available in the catalog.

Yes, Log Manager supports APE's. Worth noting that while the APE's will take some of the syslog/trap load off the primary poller, however you will still be limited to approx 90 million logs/day.

Sorry to hear you are having issues. Have you raised a Tech Support ticket? If so, can you please send me the Case Number so I can investigate for you.

Hi All, As Leon said above, the issue with the catalog is now resolved. Apologies for any inconvenience caused. Jamie

We are actively working on improved SMB support which includes SMB versions 2, 3 and 3.02. Unfortunately I can't provide an updated timeline at present, but I'll be sure to keep this forum updated as soon as I can. Apologies for the inconvenience caused by this issue - I understand it's frustrating.

Can you provide me with your support ticket number so I can investigate?