willhepptemp

Hey Denny, Yes - this is the behavior I see with the Admin account... Thanks, Will

Hey Denny, Case #64546. Honestly, I don't get anywhere with entering tickets. At this point, every upgrade brings new bugs without fixing the old ones and then I spend days of time that I can't afford trying to get the system stable again. Will

Just "0 Rows Imported". I'm trying to import to the interfaces tables specifically using interface.nodeid and interface.interfaceid as the combined key.

hmmm... I have a similar issue whereby, after upgrading to 8.5, passing login information via URL no longer works. Do others with auto login issues have a separate web server? There are still issues in 8.5 with getting data onto the web server (reports schema still has to be copied manually, for example) and the separate…

Okay - thanks Mark. Is there someplace to view the open feature requests per product? Will

As a follow-up, below is what's in the session trace. Clearly, Cirrus is just sitting there wasting time for no reason. Any ideas where "TimerTick" is located and how I can change its frequency and duration? Will Process Line = <* dbnnetaccsw11a-34n.14 # > Pushing back: <* dbnnetaccsw11a-34n.14 # > mPrompt is :…

Hey there, Not sure if this would work for you but I added several custom properties in order to do this. So, for example, I added global region (N. America, Europe, Asia, etc.) location code, environment code (dev, prod, etc.) and a layer code (access, distribution, wan, etc.) The upside with the custom property is you…

Out discards are not errors, strictly speaking. Rather, they're an indication that the device on transmit was unable to enqueue an outbound frame (and, hence, discarded it.) It is an indication of bandwidth congestion. Transmit errors are enqueued or transmitted frames that got borked on the way out. Also, note that…

Transmit discards are *not* errors. They're well formed frames that had to be discarded because the bandwidth of the link + buffer exceeded the offered load. You're just crushing the link. A sniffer won't help you because it can't see what wasn't sent (e.g. discarded before it was transmitted.) The first fix is to stop…

Er.... Never mind.... (I truncated the Traps table without also truncating the TrapVarbinds table which put everything into a funky state. Shutting down the trap receiver and whacking both tables got things back to rights...) Will

Er... I actually have the reverse problem, I think. How did you get that display? I'm trying to group multiple custom pollers into a signle resource and Orion won't let me. I can *only* choose one for the resource summary... Will

I set up custom properties in the interface table so that interfaces could be referred to by function (uplink and WAN, in this example) and then set up advanced alerts to send notification only for those links I care about. This lets you bypass looking at the "Events" section for up/down, ultilization or whatever and you…

Not sure if you're missing something but I see the same behavior under Extreme XOS devices. The weird thing is that the config template for Extreme has the correct syntax ('disable clipaging') but whatever Cirrus is doing makes the command not function correctly. No idea why/how/where... Will