Comments
-
still there in v11.01
-
Any chance that there will be generic devices' icon(router,switch,fw,server) with color change on the device image itself and not adding a color code shape behind the image? That way, the icon integrate much better with custom background. A good example is the server10 in Devices of Scalable Legacy Icons.
-
it can be tedious but sure to work. Condition to trigger, neighbour IP equals A or neighbour IP equals B or neighbour IP equals C ... ...
-
You can refer to this for more information. https://thwack.solarwinds.com/ideas/7876#comment-265414
-
SW support is saying it will happened in the future release but no timeline.
-
is there a change in v10.5? I dont see this settings under "Database Settings"
-
case #766427 Sent from Windows Mail
-
Thanks, Mark. It worked!!
-
I have downloaded the lastest MIBS.cfg(dated 31 Dec 2010) but it seems that there are some OIDs for packetshaper that is not updated in NPM. Specifically, I need 1.3.6.1.4.1.2334.2.1.4.2.1.64 1.3.6.1.4.1.2334.2.1.4.2.1.65 Latest mibs.cfg is only up to 1.3.6.1.4.1.2334.2.1.4.2.1.57 I have the latest packetshaper mibs on…
-
Yes. https://thwack.solarwinds.com/ideas/7876#comment-265414
-
Mark, thanks for the advice! It has been resolved. I did a comparison btw permission for Reports & Report Old and added "Users" to Reports and that works. Apparently, the orion v8 upgrade process did not set the permission rights correctly.
-
For our cisco model, we had to use "export-protocol ipfix" to get the netflow going.
-
thanks, Stibi. But I am referring more to the real time netflow reports rather than the report writer.
-
Not really. Web interface not display properly after turning of TLS1.0 and 1.1 in the OS. https://thwack.solarwinds.com/ideas/7876#comment-265414
-
How about TLS 1.2 and above only support for NPM?
-
Connection per sec/min is useful to troubleshoot abnormality in the application as well as for general capacity planning. For example, the usual traffic is x connnections per min/hour/day, if it spike or drop by a lot, you will know that something is going on. On multiple circuits running the same application, it can be…
-
Getting Flow/Connection per second for applications will be great!
-
I believe that the limitation is due to information on Neighbor are collected based on Node and has no link to the actual interface. One possible workaround is to do a manual conditional or statement on neighbor IP address match for all the MPLS interfaces.
-
Due to the way netflow data is structured, the logical way is still to use IP Group for viewing traffic for a particular IP.
-
Thanks for taking the time to reply. I have done the first since its a requirement for defining the app. 2nd one is pretty interesting. Both serve its purpose but its not what I was looking for. I hope to see the info in the top app menu. This is just one server that I am referring to, we have a number of services that…
-
I want to see all traffic from a particular server. For that I have to define 2 APPs, one from any to server IP and another from server IP to any. Apparently, NTA is not merging the traffic between the two if you define only 1. Basically I want to see the traffic to my webserver
-
Finally, NPM 12.2 is able to work without TLS 1.0 and 1.1
-
Thanks for the wonderful tip!
-
The default NTA port is 2055. Did you update it to 9996? Do also make sure that your firewall allow udp 9996 if you are going to use this port
-
I find that it work for me if I define the hostname/IP in the NMS's hosts file.
-
try adding "export-protocol ipfix" to to your flow exporter NetFlow-to-SW. That worked on our C4400.
-
I have the same issue and much more after upgrade to NPM 11.5. A lot of stuff seem to break and have opened a ticket with support.