Additional note: I was requested by Cisco Tac to post this. I am currently working on this issue with them but they wanted me to verify if my configuration was correct for Real Netflow Analyzer. It seems to me that the majority of the configuration is in Cisco's hands not SolarWinds since all you really need is the IP address and the SNMP community string of the device your polling.
Bump - Nothing yet??
It sounds like the 2800 is managed by the ISP. If so, there is probably a larger issue of getting them to turn on the netflow exporter and point the data at your NTA server. Has this part been addressed?
Correct the 2800 is managed by my ISP. The issue was not getting them to export the netflow as you can see below...
CISCO#sh ip flow export
Flow export v5 is enabled for main cache
Export source and destination details :
VRF ID : Default
Source(1) HIDDEN (GigabitEthernet0/0)
Destination(1) HIDDEN (2055)
Version 5 flow records
618151 flows exported in 20611 udp datagrams
0 flows failed due to lack of export packet
0 export packets were sent up to process level
0 export packets were dropped due to no fib
0 export packets were dropped due to adjacency issues
0 export packets were dropped due to fragmentation failures
0 export packets were dropped due to encapsulation fixup failures
My ISP sent me this to confirm that they are exporting the netflow so I have no doubt it's being done. The data is being routed to the outside interface of my ASA but all this is explained in detail above.
- I try to setup a new device on the Real Netflow Analyzer for IP 10.100.12.5 (ASA outside interface) but the connection fails.
When you say the connection fails, does this mean you can't ping that outside interface and therefore can't add it to Orion NPM. If so, is it really reachable from the inside network?
Also, can you verify on the ASA that you are receiving NetFlow packets on port 2055 on that outside interface?