jamesbernhard

Chris, Any chance I can get a url to download the beta? I have about 50 w2k8 servers and really missing my built in syslogs into NPM?

I received a new custompoller executable from development to replace the old one and it resolved this issue as an fyi. This was late yesterday afternoon.

Oops looks like I am running an older version of NCM of 5.0.1 instead of 5.1, upgrading that to 5.5 and give that a try. 

I have supplied Collin with development the .net memory statistics and process monitor data for this process via email. Hopefully it will be addressed soon.

No that was removed a while back it appears during the normal uninstallation method. What's interesting in the 9.5 install log I found the following which appears to be correct, then the error appears. 5-27-2009 - 12:49:27 -- Entering DetectAddOns() 5-27-2009 - 12:49:27 -- -- Found APM 5-27-2009 - 12:49:27 -- -- Found…

SWEET! Thanks Josh!

With no changes to my environment on the polled node side or poller I am now seeing this as well. I have 5 windows 2003 servers that are constantly reporting 100% cpu utlization. During this reported period they are not being utilized at all. I run 8.1 w/ only hotfix 1 and 2 installed. I have removed the cpu resource and…

Denny unless I am missing something in APM 2.5 this didn't make this release did it?

Ya tried that as well it was actually already gone from the previous uninstall I believe that my peer did a while back. 

I see the same thing across the board when an APM component type is a windows service monitor. For process monitors via wmi or snmp it reports cpu usage. Below is an example from the APM 2.0 template. I have 3 job engine threads and each averages about 8-10% utilization but shows 0% the entire time. NPM and APM are latest…

Sorry GLE... I had a typo... below is an example of an APM alert that we have in place. It should be ${Node.IP_Address} not ${Nodes.IP_Address} Component Name = ${ComponentName}. Application Name = ${ApplicationName}. Process Name = ${ProcessName}. Service Name or Process = ${ProcessName}. Service Status =…

I believe there's a listed issue in the release notes regarding this event and x64, I am experiencing the same problem w/ x64.

Correct, you can hit Dell via there oids, IBM, etc. Sucks if you have a mixed environment.

Don't bother calling support about it. I clearly differentiated the symptoms of a memory leak and have debug available for the process was informed it's probably my physical memory and then I was told that I need to pull back my polling which has been the same for a year. I have also had the same polling interval since…

3106 I guess I am curious what this would matter... I kind of figured this was simply going to enumerate the remote host for available win32_perf* classes?

That's a big disappointment, for the numerous pollers I have when a new server is added that's 20-25 minutes wasted b/c of the delays within the GUI alone. 

Denny, Just curious if this is slated for 2.0? Our operations team asked about it today so they can see if APM timed out, or the service was actually stopped via the email alert instead of navigating thru the website.

The alert right now kills and restarts the process if it has been running for an hour but due to the unstability of the application sometimes it will fail after 10 minutes, 20, 30, etc. So about 90% of the time the automated alert remediates the condition however there are times when a call comes into the helpdesk that the…

We have had this problem for a while with W2K8 (not R2) and have a alert monitor that triggers if a perfmon based counter is in unknown status and the node is 'up' status without have rebooted in the last 15 minutes. We pass the ${Node.SysName} is a variable to the script. This resolves it w/out the reboot and no manual…

Haven't done it yet b/c I left the previous company but I was pushing hard for a Splunk purchase for over a year and was gonna implement with Orion as the first step.

We send emails via the trigger action to CA Service Desk. We pass a subject list of "request" and in the body pass variables for "group", "category", "title" and "description". Within the title we pass what would normally be in the subject line of an email alert and in the description we pass the remaining alert variables. 

I would track down my exact MF version, feature release and what hotfixes have been installed. I know a few years ago with Metaframe XP and W2K we had issues like this that was fixed with a feature release and subsequent hot fixes. I bet you can find a hotfix or correlating rollup or feature release that addresses your…

I am having the same problem. I am running APM 2.5, NPM 9.1 SP5 and NCM 5.1 however I do recall a peer installing VOIP a while back as a demo but it was uninstalled. I did see the tables in the NetPerfmon db and support said to drop them which I did, rebooted the Orion server however I still receive the same error. I…

I actually asked about this a while back but haven't heard any news on it...

One of our network engineers mentioned this as well... ---- One other request that comes up every once in a while is “How long has a specific port been in the unused state?” We would need syslog history to get that type of information directly from the switch, but if Cirrus can supply the date when a port last reported a…

We would love for the function to be imbedded in the Orion website so that we can provide our remote field technicians the ability to track down a hostname, ip or MAC to a port and then be able to look at the configuration of that port. This would prevent numerous calls from non network engineers asking what is this…

Cleared all snmp registry entries after uninstall, rebooted and installed again to resolve the issue.

You simply need to specify the table so instead of ${IP_Address} use ${Nodes.IP_Address}

You only need one condition group. Property Type: Volume Trigger Alert when all of the following apply - field volume percent used is greater than or equal to value 96 - field snmp community is equal to value naperville - field volume description is not equal to value virtual memory - field volume description is not equal…