jwhitten

Yeah, I'm fine with that. Just seems like a jagged edge. Thanks John

YES! That did it, thanks guys! Appreciate the assistance ;-) John

Yes, but that is an ambiguous definition. After the "Time and date of last Node/Interface/Volume database and memory synchronization", do you know: (A) The machine is actually there and talking or (B) We gave it a whack ??

Hmm-- it's still happening. I don't know if the word filter is presently on or off. But it's still not accepting my post.

Yes, there are a number of ways that it is possible to search, I'd like to set a *different* one to search on by default. Instead of "Node Name" as the default type, I'd like to search on "IP Address" as the default type. And, if I could have anything, I'd like the search to be "Node Name *AND* IP Address", since I have to…

Thanks for the info. That's kind of what I suspected / figured, but didn't actually 100% know for sure. The whole thing came into question recently when my boss asked me to set up some reports for upper mgmt and asked me about the directionality. I just wanted to make sure I was telling him the correct answer. Didn't know…

Thanks for the kind words! I feel exactly the same way about all the other great help and information I've received from this site! John

Here is another one:

Here's one of ours

In a program that I wrote (unrelated to Orion) that had lots of properties (fields), the way I handled this was to have several "lists" of fields that could be adjusted to arrange the way fields would be ordered. An internal view that the program would use by default, a user-configurable view which could override the…

Hmm... very strange -- now it started working... very strange. I changed a sort setting for one of the custom fields. Now it pops up a message: Detected usage of a macro, which links to a nonexistent field in the report. Therefore WebURL, which uses this macro, will not be generated correctly. Missing fields: NodeID But…

Talking to myself again I see... Oh well, at least it's a good thing I'm easy to amuse... I posted a write-up on How to use variables in Network Atlas and also How to Generate a WAP Map if you have Thin WAP devices (not normally supported in Network Atlas). See my post here: HOWTO - Create a Spiffy WAP MAP with Network…

Nice idea-- and the other post too. One useful improvement that could be made, is to add a second set of mute fields, so that dual alerts could be generated and/or suppressed for a single device. Say a customer set and a provider set. Each would have their own mute fields they could twiddle to control their own alert sets…