animelov ✭✭✭✭✭

Version 3, removed out Network nodes, and changed it to NAM or NOM nodes, which is defined as the total number of nodes, minus those that have applications assigned to them (Total Nodes - ACM Nodes).

Updated the logic for all other nodes, so instead of ACM/NAM, it is now Total, ACM, Network Nodes, and NCM nodes

Would it be possible to post or IM me a screenshot of how you have it entered please?

Well crap, the query has been wrong for almost a year. The line on the VLan should be VLanID, not DisplayName. Here are the corrected queries: select UP.Node.Caption as [Node Name], UP.Node.DetailsUrl as [_LinkFor_Node Name], UP.name as [Interface Name], UP.DetailsUrl as [_LinkFor_Interface Name], UP.PortDescription as…

Can you search for 8301 instead of 8031 instead? The three results you get are different from the drill down screenshot you posted.

Would it be possible to post a screenshot?

Hey, sorry for the delay, been out for alot of personal things. Out of curiosity, are you seeing any VLan information when you drill down into a UDT port? Namely, I'm wondering if you ARE seeing it within NPM, but NOT seeing it within UDT.

Yessir, Just replace the VLan with (in both top and bottom queries): UP.MACAddress as [MAC Address] And you should be good to go

Add the word "distinct" to the select query, so you have... select distinct UP.Node.Caption as [Node Name],

This can potentially happen for a couple of reasons: 1) "unique" is not set 2) not shown in the query is that the query is returning all of the devices connected to that port. Even though that is not shown, it would still return a value for each one of the instances of a device connected to it.

Fantastic! Thank you! To add to the IP tables troubleshooting, if you find that it is indeed iptables that is the problem, rather than keeping the service stopped, you can run the following lines to add a firewall rule and restart the service: iptables -I INPUT -p udp -m udp --dport 161 -j ACCEPT iptables -I INPUT -p udp…

Updated the report. Asset Inventory was taking from the wrong table. Now it is going against whether or not asset inventory polling is enabled.

Made another change. The math was wrong in a couple of places, but now it has been validated and charts have been added:

Made a minor change to include both the summation of groups as well as the individual volumes in each group:

I remember this from yeeeeears ago. The bug isn't on STM's side unfortunately. If I remember correctly, the bug was on QLogic's end, namely when monitoring the HBA via WMI (which we are doing). Support is correct in that the workaround is to remove the files. If memory serves me right, those files are memory dumps, and…

Shouldn't be a problem with running the Profiler Server and the LSI (or any) provider on the same machine as long as the machine is spec'd out well enough. Make sure the process is running, but my question is which version of the provider are you running? The newer provider the CIM instance name is '/root/lsiarray13', but…

I'd agree, that shouldn't be right. I'd open a ticket with support. As far as I know, that field should take the average of the change per day (Today's average usage - Yesterday average usage) over the last 30 days and report on that.

Not sure why it's doing that, I'll get someone to look into it. In the meantime...what's the question? :)

So, there isn't a real firm answer on this because it all depends on little factors (number of arrays, how large the array is, are you gathering VMWare, etc.), but there is a preferred setup for minimalizing the amount of bandwidth across the WAN. SMI-S providers are built to synchronize with the array, and therefore will…

Vote please http://thwack.solarwinds.com/ideas/2472

Looks like we figured it out AlterEgo. It was a combination of things. First was that we were actually looking at the wrong server to setup (different IP Address). The other was that he had both the read and read/write strings filled in. So, we removed the read/write, now it works like a champ!

This won't do historical, but this definitely gives you a place to start: select TriggeredMessage, count(TriggeredMessage) as Number from alertactive group by TriggeredMessage Gives you:

Yup, this can be done. If you click the edit icon (the pen and paper icon) for the specific agent, there is a checkbox for 'Monitor Agent' which will send a trap whenever the Agent goes from a Green to a Red or Yellow status (yellow is defined as collection or real time hasn't occured in 5 minutes, red is defined as yellow…

I've seen this once or twice before, and it seems to be more or less a provider issue. Not sure if a new version will help or not (always worth a shot), but the one thing that worked for me is resetting the provider. To do that: 1) Stop the ECOM service 2) Remove/Rename the Program Files\EMC\SYMAPI\db\symapi_db.bin file 3)…

Technically yes, in general you need to have the read-only account + datastore.browse permissions. But this doesn't solve your issue, you'll just have different issues later on. Anyway, did you assign the ESX hosts by Cluster or by individual ESX host? If you do it by individual, then you may not see cluster information.

While this article is more geared towards 'how to add view into Orion', this will contain the URLs you are looking for. Let me know if there's anything else I can do to help!

The IP Address that you are trying to integrate it to, that is the IP address of the virtual appliance of Virtualization Manager, correct? +1 to bhopkins, the integration piece wants to login with the https link of VMan on 443, and as far as I know, there isn't a way to change that in the DB.

Other solutions: 1) EMC has a 'feature' that the password resets every so often (3 months?). To change it, go to localhost:5989/ecomconfig. Login with the current username and password (by default, it's admin/#1Password). Once you login, you will be asked to change the password. If you do change it instead of using…

Maybe I should read through the entire board first :). What version of Profiler are you currently running? There should be some exchange fixes for 4.12.3+