Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA 4.2.3 Administrator Guide > Common tasks and user scenarios > Autonomous system requirements

Autonomous system requirements

If you want to monitor autonomous systems via BGP, the flows have to contain information in appropriate bytes or fields.

SolarWinds NTA does not support extracting BGP information from sFlows.

NetFlow v5 and compatible flows

The flow record has to contain data for the following bytes:

Bytes Contents Description
40-41 src_as Autonomous system number
42-43 dst_as Autonomous system number

For more information, search for NetFlow export datagram format on www.cisco.com.

NetFlow v9, IPFIX, and compatible flows

The flow record from autonomous systems has to contain data in the following field types.

Field Type Value Length (bytes) Description
SRC_AS 16 N (default 2) Source BGP autonomous system number where N could be 2 or 4.
DST_AS 17 N (default 2) Destination BGP autonomous system number where N could be 2 or 4.
PeerSrcAS 129   Peer source autonomous system number
PeerDstAS 128   Peer destination autonomous system number

For more information, search for NetFlow version 9 flow record format on www.cisco.com.

 
Last modified

Tags

Classifications

Public