mcbridea

Good stuff - also note there is a Orion Level II customer training tomorrow and Aug 19 which will cover poller tunning and other topics. Brandon Shopp will be delivering this and he is a guru on this stuff. Tomorrow is booked full but you can still register for the 19th. Here is the reg link...…

I have marked this for a PM to comment.

Hi Justin, This is a bug which is targeted for a fix soon. Andy

Because DCs are so critical to business continuity, most DCs have multiple connections to the core. If this is the case and there is no single point of failure that would isolate the DC you are OK.

Thanks Jeremy, We have also noticed all of the failed transactions are JDBC connection tests. Is there a compatibility issue there? Andy

Reply Suggest as Answer Verify Answer More cfcuomo - - Please open a ticket on these. I was unable to reproduce these issues on my installation.

Avoid Raid 5 and 6. The performance will be dismal.

Nothing on that page refers to KBs and there are 70+ things a user can click on. Not very useful

When I run diags the output references KBs with links to the KB. All of those links are dead. Maybe I a little dense but shouldn't your KBs be plainly listed under some sort of Knowledge Base header or Knowledge base page? Having them on a page with a bunch of stuff that is not KBs is not helpful.

valdemirs, Were you able to make this work?

Or this simplified version...

Thanks Dave!

Can you guys post screen shots?

The way suppression works is that if the suppression condition is true, then the alert will be supperssed no matter what the trigger condition is. This means you cannot suppress on a node name because if the node name exists in the database the suppression condition is true. So what you need to do is include the nodes you…

Hi Bruce, We are looking at some architecture changes that will allow a second collector to off load the work. No dates to share at this point but we understand this can be an issue and are addressing it. The additional collector available today is designed for reachability issues and won't help much for processor. Andy

What I would do is choose the most important interfaces and apply NetFlow there and watch memory and CPU. There is no performance benefit between v5 and v9.

Also note that the Group Owner is an internal assignment and will be hidden in a future release. It has no user functon.

Can you expand one of the 30 PDUs so I can see what is being exported?

Have you seen these blog posts about charts in reports?

That is a cool feature but they will be unmanaging app monitors, not nodes. Is there any way to see what is set there?

Alerts are not currently supported in NetFlow

Looks like you are on the right track. I was only able to walk down to cfwHardwareStatusValue (3). Looks like you are seeing one OID lower. What is that lower OID? Wat are the possible values?

Mdriskell - NPM will not run on .net 4.0 at this point. Stay tuned for updates from PM and dev.

Hi Kevin, Good stuff. Is the SLA Type=Incident Impact=4 - Single User Product Type=Network Infrastructure Urgency=Medium Product Sub-Type=WAN portion just static text within the email? Andy

I don't think we have enough information at this point to know if it is the same issue. Zohllett - do you have any more info on the device and such? Thanks!

smargh - Is that instead of compression on recommendations when using compression?

Hi Epenney, Did you create a UnDP for this? If so, can you publish it to the content exchange area of thwack? Andy

I think you are on the right track. It is probably the switches belonging to multiple groups which have dependencies. Is there a reason they have to belong to both groups?

Hi Paull, Please have your engineers post on this - I am interested in knowing the answer as I have not been able to find anything on this yet. Thanks - Andy

The suppression is tied to the trigger condition, so it can be as specific as the trigger.