Comments
-
That's pretty cool thanks for upping to the content exchange... looks good.
-
I'm already running NTA3.6RC3 which from what I've been told is the same as the actual release.... so according to your post I should only have to run my 9.5.1_SL500 .exe on my NPM SP2 and everything should be taken care of for me. Since NTA is NTA3.6RC3 and same as release then I shouldn't have to do ne thing else…
-
One solution in this case is to monitor the actual WAN endpoint interfaces instead of the loopbacks... then you will always know which or if both are up or down. In normal circumstances you want to monitor network devices by loopback... but that is NOT always the case.
-
Such a huge Relief to read you have 500 alerts... any of these big changes scares me that I'll come in one day and have a bunch of emails saying a bunch of stuff was down and no one got pages or emails all night lol!
-
Thank's that's a relief to hear.
-
I usually wait until the next new version is about to be released. I let two systems get too far behind. They were 11.5.3 or something and had to be brought all the way up to 12.2. That was rough... you can see earlier in this thread how many steps it took.
-
The two window thing doesn't sound good.
-
I'm getting the follow from tooltip and Avdvanced Alert Engine variable link: Sorry, there was a problem with your last request! Either the site is offline or an unhandled error occurred. We apologize and have logged the error. Please try your request again or if you know who your site administrator is let them know too.
-
What is it exactly that you are trying to monitor that needs a UnDP?
-
Exactly if you don't do this NPM won't know what it is unless you set it!
-
How about the alerts between 11.0.1 and where you're at now byron? I just upgraded to SAM 6.1.1, QoE 1.0, NCM 7.3.2, NPM 11.0.1, NTA 4.1.0 and have been most concerned about the report issues with moving the alerting to the web. What is the groups problem you have been referring to?
-
Hmmmm interesting I tried copying the query into SQL Server Management Studio and running the query there. It works fine an returns almost immediately using use OrionNetPerfMon. Seems like if it works in there it would work in report writer also. I wonder if it has something to do with the version I'm using? Seems like it…
-
How long should it take to run? I did the same thing I think and changed use netperfmon to Orionnetperfmon and then ran the query from report writer... it goes to Querying database... and just sits there with the hourglass. I'll let it run for while... maybe someone else can test also. Is it supposed to run quickly or take…
-
No problem... I know how it is with security scans finding things!
-
You could use a netflow forwarder duplicator... there are a few of them: How-to configure a free NetFlow forwarder or NetFlow duplicator - Brad Reese
-
Thanks Brandon... it's good to know things like this. This makes updating to newer version that much more important if you can't extend devices support by just updating the MIB file.
-
Thanks again janene16 you really helped me avoid some serious problems and get my alerting back on track!
-
I don't have this issue and am still running 9.5SP2 even with NTA3.6 with it and tooltip hover overs on the maps are working for me.
-
Ugh I mean honestly who still uses http on much anymore???
-
The application monitors are under Admin -> Settings -> SAM Settings Then in Manage Application Monitor Templates you'll find all of the exchange templates you can apply to your exchange nodes. Depending on the version and what you want apply some of these to your exchange nodes and let them collect some data. Now you'll…
-
I agree with deverts... and on top of that we have enough forums as it is to try and stay on top of. Also I think a lot more environments the tools are used on are bigger than you think. Also as far as the SW isn't just for mom and pop shops anymore... TELL THAT TO EOC ctmidnight!
-
For me I just point my webrowser at the NPM server by name and it the login dialog comes right up! Your homepage URL should look something like this: https://yourNPMServernameorIPhere/Orion/SummaryView.aspx?ViewID=1 It's possible it's not https that depends on how you set it up.
-
Outside... what's that? Great post by the way...
-
See! You've come to the right place! I used to live in columbus while going to school too... go OSU!
-
I have to agree with cahunt here... I think what you are trying to say is you like SAM's warning and critical and wish the alert configuration had two levels of alert in the same alert config. To me status rollup is when if a node in the node tree is down the indicator will roll-up to the top level and show yellow to…
-
This makes me think my current Pi2's usb nic is better than the onboard wifi in the Pi3 for sure. I may get another 802.11ac dongle for my new Pi3 after all since I like smooth hi def video. That's a good article you linked. This is my Pi2 dongle which works without needing to add any drivers and I've never had any…
-
yes, you can filter based on any of the event types on anything you see in the event log which includes node removed events. Here's mine that I just tested after removing a couple nodes: Give it a shot... working great for me. I think this should work for you also. Also you can use the fields event name instead of Event…
-
Glad to hear your working valdemirs. This is actually really good to know especially since a few of us could reproduce the problem... I can see how any number of people could run into this same problem.
-
So I assume this is causing the pings from NPM to your nodes to show high ms response times for all your nodes response times graphs also then. Also when you ping then NPM server from your client machine with an -t option do the ping times rise high sporadically also?... I would pretty much assume they would. It definitely…
-
The NPMv10 RC3 is about as production ready as it's going to get. I understand companies being afraid of Release Candidates after some of the things that have happened with Microsoft. I'd look at the NPMv10RC3 and W2k8R2 if you require it.