Comments
-
Not to mention we have a server with 40 logical processors which causes problems for 32 bit apps running on 64bit OS. This is a known issue that first came out in 2008 server but still exists in 2012 server, though they did have a hotfix for 2008, not sure about 2012 still looking since that is what we run currently. You…
-
We are moving our scopes to Palo Alto for DHCP and need to be able to monitor as well, really need this functionality!
-
Those are useful, thanks for that. Still think moving forward it would be better to have a built in report available with the product instead of having to go through downloading and adding int the report writer.
-
I'm just curious, we have multiple modules (npm, nta, ncm, wpm, engineers web based toolkit), it is already running on Win 2012 R2, what would you say should be minimimum and recommended CPU for that?
-
It's management, they are counter intuitive by nature haha
-
Yes, I am actually running that as a work around. Been working with SW support, now with their development group. Don't know if this applies to you as well, but this is the last thing they gave me to try. I have not gotten a clear window yet to do the MS fix, hope to do so later this week. Development indicates there is a…
-
No, upon checking the actual SWQL query it errors on orion.npm.interfaces, doesn't recgonzie that. currently building out a SQL query instead.
-
Qwest is in the name, I just didn't show the whole device and interface name
-
Sure. I believe it is with the Dev team at this point. 1189815
-
Thanks, this is great!
-
OH and Yes, I know there is no status showing in the query but I just wanted to make sure it pulled the data first.
-
Thanks. Ill give that a look. I know one is our primary when pinging by hostname and the other apparently is where Netflows are pointed to, not sure why they did it like this but I'll see what i can find.
-
What about when you already have a web server setup and everything is working but you are adding a new module? We are getting ready to install NTM and I just started with this company and have never used an Additional Web Server prior to working here.
-
I appreciate you looking!
-
Thanks. I have a vendor asking for one of the sites we are using it on and they were curious.
-
That's not what I needed, i'm already aware of that and have the tasks alerting on what I need. The scheduling part was a request after I had the alerts set, they just wanted to know that even if the task ran they (mgmt.) wanted to know if it ran at the correct time.
-
I haven't seen that list here so that is nice to have but none of those on the list (and I reviewed the status codes link) speak directly to an active task not running at it's scheduled time. I don't think from what I have researched that a code exists for that. I appreciate the link though!
-
No it's not a matter of scheduling the alert for a time period, it's a matter of the actual time each specific task is scheduled to run.
-
Thanks for that link, i'm going to look at this first thing when i get back in office next week and see if this resolves.
-
I am on same versions, but I get this error on importing nodes.
-
Yeah unfortunately that doesnt show the locations under the folder, just the subnets themselves. i need to see the locations along with it. thanks though.
-
Great, thanks! That was exactly what i needed.
-
Think I just answered my own question, right after I posted this I realized I was under Nodes instead of Interfaces for my query. Changed to Interface and slight modification and now it works! And I can see my expected results in the SQL query so I know it's pulling the right info now. Thanks for all the responses today!
-
So I had not checked against the SWQL and did so just now, it appears the issue is that the SWQL errors out but I can't see it unless checking as you suggested. The error is that the query builds and by default appears to be looking for Orion.NPM.Interfaces but that does not appear valid per the error I am getting. We are…
-
Have not tried the wildcard yet, might be the easiest thing for me to test next.
-
Nope, no difference.
-
Well i'll take a look so I appreciate the response, haven't had time yet to read the whole thing. However I did read the first part and I have to ONLY alert of nodes that start R1 and R2 (case does not matter) and ONLY the interface with Qwest on the specific interface on those devices, so it's not redundant.
-
That worked, exactly what i needed! Thanks a million!
-
Actual found the problem to be ADFS, according to the support team WPM does not currently support ADFS so that was my issue. I was able to work around the issue by finding direct URLs to go to within the site but it does not give me the actual flow that I would like. Unfortunately have to wait until ADFS support is added…
-
We are about to start rolling this out at locations and I have the same question.