nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

ASA5520

root0

ASA5520 with asa821-k8.bin is supported by Netflow v3.1

Find more posts tagged with

Accepted answers

mcbridea

To close the look on ASA , NTA 3.5 does function with ASAs running 8.2+.

See

All comments

root0

Debug log

2009-05-19 15:29:01,893 [STP SmartThreadPool Thread #56] WARN SolarWinds.Orion.NetFlow.Workflow.PacketProcessingWorkflow - Failed to parse packet from IP 10.80.80.199.
2009-05-19 15:29:01,940 [STP SmartThreadPool Thread #56] WARN SolarWinds.Orion.NetFlow.V9PacketFactory - Packet was dropped because of invalid template id: 263
2009-05-19 15:29:01,940 [STP SmartThreadPool Thread #56] WARN SolarWinds.Orion.NetFlow.Workflow.PacketProcessingWorkflow - Failed to parse packet from IP 10.80.80.199.
2009-05-19 15:29:01,940 [STP SmartThreadPool Thread #54] WARN SolarWinds.Orion.NetFlow.V9PacketFactory - Packet was dropped because of invalid template id: 256

Hi,

if you want to netflow be able process data from Netflow-V9, than the template must contains following fields (according RFC).

(ID // RFC name)

1 // octetDeltaCount,
2 // packetDeltaCount,
4 // protocolIdentifier,
5 // ipClassOfService
7 // sourceTransportPort
8 // sourceIPv4Address
10 // ingressInterface
11 // destinationTransportPort
12 // destinationIPv4Address
14 // egressInterface

If one item is missing, than the template is invalid for our collector and we drop all packets which belongs to this template. So you need to set up router to export all these fields.

root0

NTA 3.1 don't work with Cisco ASA

So you are not able to set up these fields for your templates or there is some other issue? If you know that you have all these fields in your templates and you are still not able collect data, can you please send me some short pcap from this device? I can check it. (I need template definition there)

Thanks, ET