Nothing Special   »   [go: up one dir, main page]

Allied-Telesis-logo

Allied Telesis x530 Series Switches

Allied-Telesis-x530-Series-Switches-product

Nā kikoʻī

  • Product: x530 Series Switches
  • Software Version: 5.5.4-1 or later
  • Protocol: IP Flow Information Export (IPFIX)
  • Standard: RFC 7011

ʻIke Huahana
IP Flow Information Export (IPFIX) is an IETF protocol that standardizes the exporting of IP flow data for network analysis. It allows network administrators to monitor and analyze flow data, enabling informed decisions regarding network management.

ʻO Feature Overview
IPFIX works by observing flows of packets across a network, collecting flow-related information, exporting this data in a standardized format, and analyzing it at a central collector or monitoring system.

Nā ʻōlelo hoʻohana huahana

ʻO Feature Overview a me ke alakaʻi hoʻonohonoho

Hoʻolauna

IP Flow Information Export (IPFIX) is an IETF protocol defined in RFC 7011 that provides a standard for exporting IP flow data from a network for analysis. Network administrators analyze the IP flow data, and make decisions, such as applying QoS policies or maybe adding more bandwidth to network areas that need it.

In simple terms, here’s how it works:

Flow Observation
When data moves across a network, it generates flows of packets between devices. A flow is a sequence of packets that share certain characteristics, such as the same source and destination IP addresses, the same protocol, and the same port numbers.

Flow Collection
A network device, such as a router or switch, monitors these flows. It keeps track of flow-related information, like how many packets were sent, how many bytes of data were transferred, and how long the flow lasted.

Data Exporting
The device then packages this flow information into a standardized format defined by IPFIX. It creates records that describe each flow and sends these records to a central collector or monitoring system.

ʻIkepili ʻikepili

  • The central collector receives the IPFIX data from multiple devices across the network. It stores and analyzes the data, providing insights into network usage, performance, and potential security issues.
  • This guide describes how to enable IPFIX on a device, enable a flow observation point on an interface, set flow key fields to generate unique flows, and configure a collector to export these flows.

Nā huahana a me nā polokalamu polokalamu e pili ana i kēia alakaʻi
This guide applies to x530 Series switches that are running version 5.5.4-1 or later.

No ka ʻike hou loa, e ʻike i kēia mau palapala:

  • Pepa ʻikepili o ka huahana
  • The AlliedWare Plus Datasheet
  • Kuhikuhi Kauoha o ka huahana

Loaʻa kēia mau palapala mai nā loulou i luna ma kā mākou webpaena ma alliedtelesis.com.

Nā palapala pili
See the following document for more detailed information: RFC 7011.

Laikini
IPFIX is part of the standard feature set of the device software therefore there are no special licensing requirements.

Configuring IPFIX
In simple terms, here’s how you configure IPFIX:

  1. Enable flow service on the device.
  2. Create a flow record to configure match fields for classification of flows on incoming IP traffic.
  3. Create a flow exporter to configure the IPFIX collector to export IPFIX messages.
  4. Create a flow monitor to combine a flow record and a flow exporter configuration.
  5. Assign the flow monitor on a switchport to start IPFIX monitoring.
  6. On a PC/Server, set up an IPFIX collector tool to receive IPFIX messages for analysis.

And here’s a configuration example based on the list above:

  1. Enable flow service on the device
    • awplus(config)# service flow
  2.  Create a flow record to configure match fields for classification of flows on incoming IP traffic. The match fields can include some or all of these fields: DSCP, IPv4 Source Address, IPv4 Destination Address, IP protocol (TCP/UDP), Source port, and
    • awa hoʻokele.
    • awplus(config)# flow record FLOW_RECORD
    • awplus(config-flow-record)# match ipv4 protocol
    • awplus(config-flow-record)# match transport source-port
    • awplus(config-flow-record)# match transport destination-port
  3. Create a flow exporter to configure the IPFIX collector to export IPFIX messages.
    • The IPFIX collector records flows for a given period of time and generates user friendly reports. awplus(config)# flow exporter FLOW_EXPORTER
    • awplus(config-flow-exporter)# description IPFIXCOL-PC
    • awplus(config-flow-exporter)# destination 192.168.1.2
    • awplus(config-flow-exporter)# transport udp
  4. Create a flow monitor to combine a flow record and a flow exporter configuration
    • awplus(config)# flow monitor FLOW_MONITOR
    • awplus(config-flow-monitor)# description MONITORING-PC
    • awplus(config-flow-monitor)# record FLOW_RECORD
    • awplus(config-flow-monitor)# exporter FLOW_EXPORTER
  5. Assign the flow monitor on a switchport to start IPFIX monitoring. This is known as the observation point.
    • awplus(config)# int port1.0.1
    • awplus(config-if)# flow monitor-map FLOW_MONITOR
  6. On a PC/Server, set up an IPFIX collector tool to receive IPFIX messages for analysis.
    • On the Layer 3 device:
    • configure flow classification match fields that correspond to an IPFIX flow key.
    • configure the IPFIX collector information
    • enable IPFIX on the switchport (the Observation point). Any incoming IP traffic on the switchport is classified into unique IPFIX flows based on the flow key extracted from the packet and each flow is then counted by the silicon.
    • The Layer 3 device exports IPFIX messages containing the packet counters and flow information (such as essential IP header fields and observation point details) received on the switchport to the IPFIX collector at regular intervals.
    • IPFIX collector records flows for a given period of time and generates user friendly reports.

Allied-Telesis-x530-Series-Switches-fig- (1)

Monitoring IPFIX
To display brief information about state, configuration, and total number of flows:

Allied-Telesis-x530-Series-Switches-fig- (2)To display flow records and the set match fields:

Allied-Telesis-x530-Series-Switches-fig- (3)

To display flow exporter information:Allied-Telesis-x530-Series-Switches-fig- (4)

To display flow monitor information:Allied-Telesis-x530-Series-Switches-fig- (5)

Limitations in AlliedWare Plus implementation

  • During fast-failover, some flow data may be lost as the new TCP/UDP session with the IPFIX Collector is established on the new Master and flow processing resumes.
  • The number of IPFIX flows supported on the device is approximately the same as the number of ACLs supported/available on the device.

C613-22145-00 REV A

  • Ke keena nui o Amerika Akau | 19800 North Creek Parkway | Huina 100 | Bothell | WA 98011 | USA | T: +1 800 424 4284 | F: +1 425 481 3895
  • Ke keʻena nui o Asia-Pacific | 11 Tai Seng Link | Singapore | 534182 | T: +6563833832| F: +65 6383 3830
  • EMEA & CSA hana | Incheonweg 7 | 1437 EK Rozenburg | Holani | T: +31207950020| F: +31 20 7950021
  • alliedtelesis.com
  • © 2024 Allied Telesis, Inc. Ua mālama ʻia nā kuleana āpau. Hiki ke loli ka ʻike ma kēia palapala me ka ʻole o ka hoʻolaha. ʻO nā inoa ʻoihana āpau, nā logos, a me nā hoʻolālā huahana he mau hōʻailona a i ʻole hōʻailona inoa inoa ʻia ka waiwai o ko lākou mau mea nona.

FAQs

What devices are compatible with IPFIX?
The x530 Series switches running version 5.5.4-1 or later support IPFIX.

Is there any special licensing required for IPFIX?
No, IPFIX is part of the standard feature set of the device software, so no special licensing is needed.

Palapala / Punawai

Allied Telesis x530 Series Switches [pdf] alakaʻi hoʻohana
C613-22145-00, x530 Series Switches, x530 Series, Switches

Nā kuhikuhi

Waiho i kahi manaʻo

ʻAʻole e paʻi ʻia kāu leka uila. Hōʻailona ʻia nā kahua i makemake ʻia *