FormerMember ✭✭✭

Right on, thank you both!

When we talk to the machine, it tells us it's net-SNMP. We don't have any facility for labelling that as LogLogic.

Thank you patricks! It was right on the money. Now that I understand how to turn it off/on, I know we will eventually introduce the feature! THANKS! PS: Maybe the name should be changed to "Use Models (prompt Asset information)".

I'll give it a try. Thanks.

Where exactly do you put these commands in the new package?

Hello, This question was prompted by analysis of IP SLA Echo operation results by an SLA (service level agreement) analyst but I am sure we will be asked about all IP SLA operations eventually.

SysWiz, how many sub-map layers down do you have to drill to see this problem? I only have maps that go two levels and I'm not seeing this problem with Orion 8.1 running FireFox v2.0.0.5. I have all current hotfixes applied. Are you behind a proxy server? It shows up if you have a map within a map. No proxy server. 

 I use Firefox, too, and for pages that give me troubles, I use the IE Tab extension for Firefox. It lets Firefox render the page with the IE engine. As an end user, it still feels like Firefox. It solves a lot of quirks of this type. https://addons.mozilla.org/en-US/firefox/addon/1419

Best way to move data from Orion to LEM is via a SNMP Trap, though. If you configure an Orion alert that can post an SNMP Trap to LEM when this occurs, you can use LEM to alert on it (or correlate with other behavior, or just store it so you could search back on it later). LEM can really only alert on counts of logs, not…

excellent idea

Thank you for helping me out. What we ran into is a report that does not seem to work. From our "Home" screen we click reports, expand "Historical Traffic Reports" and select the report "Total Bytes Transferred by Node - Last 7 Days". we get a page that indicates the following: Invalid Filter. Selected fields are…

 Is this tread still alive? In that case I have a wrong Juniper SA6000 VPNSSL box which is detected as Linux, the SysObjectID is 1.3.6.1.4.1.2021.250.255 (vendor linkhttp://www.juniper.net/products_and_services/ssl_vpn_secure_access/secure_access_6000/) OK. I'll open a bug, but sometimes, the vendor is actually running…

Hi there, Our Digi Passports are showing up as net-snmp-Linux, is it possible to get them to show as Digi Passports? SysObjectID = 1.3.6.1.4.1.8072.3.2.10 Vendor = Digiboard Model = Digi Passport 32 I hope that is enough info, if not let me know. Regards, David If the device is actually leverage net-snmp, then that's…

Thanks Andy.... I can't wait to see what you guys come up with. In the meantime, can you or someone at SW point me to which table holds the IP Address Group so I can see if I can continue on trying to build a SQL query which will allow me to summarize the traffic for them?

 We need: SysObjectID (which you can find in Node Details) in System Manager. Vendor Model

Juniper Netscreen Firewalls Telco Systems Switches Accedian EtherNIDs It'd be cool to be able to choose an icon for "unknown" devices, such as BSD or Linux machines. Penguins and demon babies are always fun to see on a webpage. Could you provide SysObjectIDs for the specific devices? 

Is up/down (device connected or not to port?) status maintained and statistics collected on "unpluggable" interfaces? This is all I could find in the NPM Admin Guide and implies only alerts are suppressed. Unpluggable Port ModeOrion enables you to designate selected ports as unpluggable, so unnecessary alerts are not…

Not yet. IT's on the roadmap.

Hi, I tried both the RPC and WMI flavor of APM performance counters. Each give the correct value of raw counters but are unable to read the value of calculated counters. I just tried WMI Explorer as you suggested and the result is the same : raw counters works but not calculated ones. Thanks Stephane

geoffinva3 You're posting on a really old thread. The first post was from 2003 and the last post before yours was 2006. We have released quite a few times since then, and most of what's requested in this very long thread has been delivered. I'm also wondering what version of NPM you're using because v9.5 can do quite a bit…

You need to clear the instance of a current triggered alert or the alert will not reset. The alert engine in NPM 11.5.x seems buggy, so hoping in NPM 12 it is improved.

General log management is something we're thinking about. While I agree that it's a reasonable request in APM, it's not something that's coming up a lot. When we talk to folks, most of the ones who want something to solve their log management problem want a lot of other features beyond the ones you describe.

Hey travisj, It's great to see such feedback! You might want to write a product review in the Spread the Word forum to earn a $25 card from Amazon

Thank you for your response, here is a screen shot of one for Aborts. They are all configured the same except for the different OID and MIB name. --S

Thanks docwhite. We've upgraded to 11.0.1 and have decided to backoff from 11.5 for now with all the problems being reported. So, we are planning to proceed with NCM integration with 11.0.1. According to the matrix, NCM 7.3.2 is compatible with 11.0.1. Are you saying we need to install 7.3.1 first or is it okay to go…

tere has to be something changed, as when i upgraded, all my alerts started bouncing emails back from my processing box. I had to remove "(CCM)" from the friendly "from" field in all my alerts before they would stop trying to reply....

Thanks aLTeReGo, this gets me a little closer, however, this pulls the status icon for the node itself, which in this case is just a purple and white arrow because the node is an external website being monitored for response time. What I am looking for are the icons that show the component status as shown below. These…

You can unmanage via the Web Console on a one-time basis. If you want to unmanage on a recurring basis, there's a way to do this. There's a field in the database that identifies whether a node is currently managed or unmanaged. Write a SQL script that updates that field to unmanage. Write another one that updates it to…

 Still trying to get the change into Orion 9. No promises, though.

Thanks, that isn't exactly what I had in mind - but will definitely help me, so that's great!