rlawsha

I had the same problem with alerts. In my case the solution was: Open NPM, click ALERTS button, remove checkmark from box labeled, "Temporarily Disable alll actions for ALL Basic Alerts". How it got checked in the first place is beyond me.

I gave it a long time and it didn't stop. I show no errors in the event viewer for security. All is fine now after a reboot. It may have eventually came back, I don't know. It appeared to be stuck. The whole upgrade went fine until the end when it restarts NPM and it does a new baseline run. that is where it failed.…

I am certain netflow traffic is flowing out of that interface. I can look at it from the router command prompt. I had read in another post ( ) that I may need to wait for version 9 of netflow to be supported by Orion before I can see it or I may have to enable mls. That is, if my 2821 router has the same problem as that…

stand alone here too

I had upgraded from v8.5.1 to v9 with no problems except the cosmetic x-axis problem on some graphs. Today I applied SP1 for v9 and after the upgrade, NPM would not load. The service was stuck in a continual state of 'stopping'. I rebooted and everything came up fine (SL250 with NetFlowV3 amd Cirrus).

All is fine now - thanks!

I have found and added the Temperature Sensor to my node details page. It still shows no data though. The average response time graph works but the custom poller status section says no data. Do yo have to tell this custom poller how often to poll somehwere?

As far as I can tell tell the command: ip flow-export source interface is a global command and can only reference one interface. On each interface you want to mionitor you put the command: ip route-cache flow.

I opened a support ticket and a tech called me but was unable to setup a custom poller to monitor interface stats. Anyone else been able to do this yet on an F5 Big-IP 1600? I can monitor CPU and memory but not the traffic statistics of pool members or interfaces.

Also, in digging in to this further I discovered another little problem. For some reason and I don't know when this happened my alerts for top transmitter or receiver alerts got changed to email me a web page instead of email/page me. I redid those alerts and everythings seems to be okay now.

I have noticed another problem. when I look at a graph covering 30 days the horizontal axis labels are wrong. The view is for 30 days but the horizontal labels mention times of day, a single day. The graph is right the labels are wrong.

SolarWinds Orion Network Performance Monitor 9.5 SP4

It works fine after I took this part off the end: ${SQL:SELECT Macro FROM NetFlowAlertMacros WHERE ID='OutInterfaceDetailsLink'} No more errors.

Support ticket opened...

ok, I can understand that, thanks.

Thanks! That fixes the Network Performance Monitor tab but how about the NetFlow Traffic Analyzer tab? Will that tab be updated with the same type of speedup?

Yes it REALLY is slower. I understand the resoning behind the switch but it does take longer to display the page now. In my case I would say twice as long. It feels like I have a bottleneck somewhere but I don't know where. Loading TaskManager on the server while loading the web page (from a different box) shows that…

A support engineer got back to me right away and suggested I do this: You will need to Go into Add and Remove Programs Remove .Net 4. Most likely there are two installs for 4. Uninstall the one with client in the name second or you will receive an error. Once .Net 4 is uninstalled, it may ask for a Reboot, let the System…

I got it working! I ended up going into NPM and deleting the node altogether. I then re-added the node along with the right interfaces all in one fell swoop. I updated my map, so far so good. Then I went into the web interface and the netflow config.... It was confused, timed out and then went all wacky on me. All kinds of…

I can't figure out why I get no data on my VLAN then. On the VLAN interface I have the command IP ROUTE-CACHE FLOW just like I do on the other interfaces. I also have the following in my main config area: ip flow-export source GigabitEthernet0/0 ip flow-export version 5 ip flow-export destination 10.10.245.1 2055 ip…

The alerts were for rebooted devices. I ended up going into SQL and deleting the data from the active alerts table. I will see if the next alerts allow me to clear them. Not a big deal so far.

Okay, I have the remote temp senser all set up with an IP address and an SNMP password. The device is a Room Alert 7E for AVTech. I go into Orion NPM and add the node. It only supports SNMP V1 but it does work. So then I go into Custom MIB Pollers and select NEW. I browse for the node I just created and then click Browse…

not sure if I did this right but her is what I got: This came from a script on the F5 web site: allInts_OID = ".1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1" ltm_InBytes_Index = "1.3.6.1.4.1.3375.2.1.2.4.4.3.1.3." ltm_OutBytes_Index = "1.3.6.1.4.1.3375.2.1.2.4.4.3.1.5." This came from walking the MIB as an example:…

I was reading this post:

got it working this way.... ip route-cache flow infer-fields ip flow ingress infer-fields ip flow-export source GigabitEthernet5/1 ip flow-export version 5 peer-as ip flow-export destination 10.10.245.1 2055 found a document here: http://www.solarwinds.com/support/Netflow/docs/OrionNetFlowSwitches.pdf

That helped a lot. I found the ports and added them to NetFlow. Thanks!

Thanks for the info. I have been trying to figure out that feature with no luck. Exactly how do you do that? When I go into NetFlow and click on an interface I get a summary page, Top 5 Protocols, Top 10 Endpoints, Top 10 Applications and the like but no IP Address Groups section.

On my box they are NON CLICKABLE - you can't click them. It's like they are an image, not a clickbox. I just put in a service call to get mine fixed.

"Removing or renaming the "AppMon" folder in "\InetPub\SolarWinds\Orion", removed the old Application Monitor tab for me" Worked for me too....

I am still stumped on how to fix this. The alert itself has no quotes in it and it works for other devices. It appears that the way the Cisco ASA box 'names' interfaces is the problem. Other Cisco devices reference interfaces with names like Ethernet 0/0 but the Cisco ASA box names interface with names like 'outside' or…