uscallesen

I've looked into the case numbers referenced and these specific cases refer to the Orion Broadband product. This product reached end of life on March 20, 2008. For those with active maintenance you will be covered until March 20 of 2009. It shows yours has expired, hence the non-response from support. EOL policy states…

I actually reportet this bug sometime back in the beginning of 2008 aswell.... I ended up simply renaming the file instead of waiting for a fix... But I gotta say - and this is meant as constructive critisime - that this kind of bug and case handeling is what I've come to expect of Solarwinds. It has gotten ALOT better…

Turns out pasting the text from the sites caused the " " characters to be entered as "something else" works now - We seem to be getting better performance after using this fix.

My chart gaps (which were few and far between, like days and only for 5-10min on a handful of systems) became much more prevalent with v9, ICMP working well, but any SNMP stats gap for 1-2hrs on most devices. I haven't applied SP1 yet (that will most likely be this evening). For the most part though v9 has helped in a few…

@Mattlggo - did you manage to get that working ? - my Orion websites is unable to load when I make the change descriped.

We are actually seeing this bug whenever we switch IOS train on Cisco devices.

I found another bug after upgrading to SP1 (cant say for sure if it was there before) Using the webbased Node Manager - when I List Resources for a CMTS (Cisco UBR7246) i get the usual options under each interface - Interface Traffic Charts and Interface Error Charts - but I also get an option called Signal Quality Charts…

We're eagerly awaiting this functionality as well ! 

I've been having this issue for more than a year - previous support ticket ended with the problem unresolved - but guess I'll try again..

I checked the actual Custom Poller - the 'MIB Value Type' is set to 'Raw Value' - So I assume polling the Rate might be wrong - there is no option to poll the Raw Value though ? The condition I'm trying to trigger on - is when there is zero traffic on the interface but more than zero Cable modems (Kabelmodems i danish) -…

I'm getting the error aswell but only with IE Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Timestamp: Wed, 28 Oct 2009 14:01:03 UTC Message: Type mismatch Line: 2701 Char: 4 Code: 0 URI:…

The interfaces are all on the same device - sorry if that was unclear. I dont assume that changes anything in regards to my problem.

I'm having a similar issue - I'm trying to monitor a MS DHCP server. The OID's I'm monitoring are also increasing constantly but Orion fails to make any kind of useful output out of the data. Has anyone managed to get this working or is it a bug ?!? 

Try increasing the Interface Poll and node poll Interval - I'm monitoring 5500 interfaces with my installation and my interface polling interval is set at 120 seconds ! think about it - with your low 30 sec. intervals every chart will be generated on 4 times as much data.. I'd suggest lowering the interval and letting it…

It refers to Custom Interface Pollers.rate - being the value read by the Custom interface poller on the triggered interface (or at least so I assume) - I've tried with Custom Interface Pollers.Numeric Status aswell - makes no difference :(

You can either do this be editing the Universal device poller (when you 'assign' it you choose how it should be shown in the website) I prefer to simply edit the 'View' that the poller is assigned to - you do this through the admin page -> Manage Views in the Orion website. Just remove the Gauge and add the 'Node Charts -…

Solarwinds actually improved on the functionality - There's a fix available for 9.5.1 - Unfortunately the fix causes new problems with ALL interfaces on a node that's temperarily down to become Unknown Interfaces untill you MANUALLY do a rediscover on the Node..

The only issue with that is that I'm running SQL 2000 and going straignt to 2008 because of time and bugetary concerns. If I was able to make a stop at SQL 2005 along the way I would upgrade to 2005, upgrade to 9.5, then move to 2008. Right now my plan of attack is to shut down the entire Orion system first thing in the…

I like the new grapics used for the charts - however from a 'funtional' perspective they're just terrible. Take a look at this 7-day time period - there is no way of telling when in the past 7 days a reading was taken - and even worse If you choose the send the chart to someone via email (as we do when we report errors)…

I've been running a pretty basic Orion V9 (upgraded from 8.5.1sp3) for the past week now. With 8.5.1 sp3 we were finally getting down to only a single open case with Solarwindssupport - and a few issues which was supposed to be fixed in V9. With V9 however we've had numorous NEW problems - at this point I'm about to…

Thanks for the input guys - as I've been trying to do this with pollers assigned to different interfaces it's not possible. Instead I have located an OID that allows me to read all the interface values as one table - that leaves me with the same problem though - How do I sum up the values in the table to one number and…

Here's a thought.. what if you could instruct a custom poller to enter "0" into the DB for unsuccessfull polls ? Ie - If I poll a node that suddently stops responding to that particual poller I could have an alert that triggered on the value=0 Would this be possible (and practical) to implement??

@Byrona - thanks for sharing - this Idea actually came to me in the shower (of all places) this morning - But I couldnt figure out what the variable should be called - thanks for the tip !!! this GREATLY simplifies alert handling - Solarwinds should seriously consider including this in the documentation !

For some strange reason the performance is amazing 24 hours after upgrading to 10.2 - during the first 10 hours after the upgrade the installation was unusable.

After upgrading from Orion 9.1 to 9.1sp1 - we now have this issue too ! Any word on when it will be fixed ??

It's still only node filtering - What I'm getting at here is that everything works like you says when I want to add a Universal Device Poller to a node - it's quick and simple. But for interfaces there is no way around browsing to and marking each and every interface manually - what's _really_ annoying about this is that…

This very simple alert works for our purpose - unfortunately it generates a lot of false positives as we cannot check the numeric value of a custom poller assigned to the interface. This is how I'd like it to look - unfortunately this never triggers :(

I'm gonna have to agree - I've had several (basic) cases with response times of several weeks.

If your issue is that Orion is not picking up the interface descriptions he configured on the devices after adding them to Orion, then that will be fixed in the next release. We're very much in need of this feature as well - could you give some indication of when a fix can be expected ?

We've been having this problem for a long time aswell - basicly any node that enters the down state will often have most if not all it's interfaces marked as unknown afterwards. Typically it can be resolved by _manually_ rediscovering all interfaces and _manually_ polling them the first time. It's VERY annoying as logging…