Additional information pertaining to ERS4500,
8300, and IP Flow Manager chapter
Abstract
This document provides configuration procedures for Protocol Flow Information eXport (IPFIX)
feature for the Ethernet Routing Switch 8600, 8300, 5000, and 4500 series as well as information
pertaining to the Avaya IP Flow Manager.
Protocol type
Source IP
Destination IP
Ingress port
Type-of-service byte
TCP/UDP source port
TCP/UDP destination port
Source IP
Destination IP
Protocol Type
Source protocol port
Destination protocol port
Type-of-service byte
Byte/packet count
Ingress VLAN ID
Ingress port and observation point
(VLAN or port)
1. Overview: Internet Protocol Flow
Information eXport (IPFIX)
Internet Protocol Flow Information eXport (IPFIX) has evolved as an improvement upon the
Netflow V9 protocol. It is a standard that has been proposed by an IETF Working Group -
http://www.ietf.org/html.charters/ipfix-charter.html. IPFIX is an effort to standardize on
architecture for IP flow measurement and export. In an IPFIX model, an exporter such as a switch
or router collects IP flows and then exports the IP flow information using a transport protocol to a
collection server or servers. An IP flow is defined as a set of packets over a period of time that
has some common properties.
1.1 IPFIX Support on Avaya Switches
1 – If IPFIX is enabled, a QoS policy precedence is used
Table 1: IPFIX support on ERS8600 ERS5000, and ERS4500
Avaya Inc. – External Distribution
5
avaya.com
2 - The switch will automatically disable IPFIX if CPU utilization exceeds 90% or if there is less than 2 Mb of system
memory available. The switch will automatically enable IPFIX again when CPU utilization returns to less than 50% or
there is 5 Mb of system memory available. The disabling and enabling of IPFIX will not affect the IPFIX configuration.
3 – Required R/RS modules, not supported on legacy modules
Avaya Inc. – External Distribution
6
avaya.com
1.2 DSCP/TOS
Please note that DSCP/TOS value collected by IPFIX depends on how a port is configured on an
Ethernet Routing Switch. For example, if a port is configured as untrusted, the TOS/DSCP value
is remarked for 0x00. Hence, all IPFIX flows collected by IPFIX will also display the appropriate
value. If filters are used to remark traffic, then IPFIX will display the DSCP/TOS value according
to how the filter or filters remark the traffic.
1.3 IPFIX with Filters
By default, IPFIX will collect all traffic as shown in table 1 above. Filters can be used with IPFIX
on the Ethernet Routing Switch 8600. This allows IPFIX to collect traffic only for specific flows
according to the traffic filter or filters configured or simply to cut down on the amount of traffic
collected. Note that this feature is not supported on the Ethernet Routing Switch 8300.
1.4 IPFIX Collectors
Collectors can be enabled or disabled on the switch. Up to two collectors are supported and if
both are enabled, the same information is sent to both collectors. Exported traffic from the switch
is in Netfow v9 format using UDP as the transport protocol using UDP port 9995. The export
interval, which specifies the interval at which updates are sent to the collector, is configurable.
Avaya Inc. – External Distribution
7
avaya.com
2. IPFIX Configuration on ERS 8600 & ERS
8300:
2.1 Enabling IPFIX globally and on a port level
To enable or disable IPFIX globally, enter the following command.
CLI:
ERS-Switch(config)# ip ipfix enable
ERS-Switch(config)# no ip ipfix enable
PPCLI:
ERS-Switch# config ip ipfix state <enable|disable>
To enable IPFIX on a port level, enter the following command:
Specifies that the records be flushed. You can export records
before flushing.
hash-key
Enter a hash-key id from 1 to 4 or hashKeyOne | hashKeyTwo
|hashKeyThree | hashKeyFour.
Hash Key 1 – Use all bits of source IP (lower 20-bits), destination
IP (lower 19-bits), Protocol (1-5 bits), Source Port (lowever 10
bits), and Destination Port (lower 10 bits).
Hash Key 2 – Use lower 20-bits of source IP, lower 19-bits of
Destination IP, and lower 24 bits of protocol (8-bits), source port
(16-bits) and destination port (16-bits)
Hash Mask 3 – Use source IP (32-bits) and destination IP (32bits)
Hash Mask 4 – Use source IP (32-bits), source port (16-bits) and
destination IP (16-bits)
Default setting is hashKeyOne (1).
hash-polynomial
Specifies the coefficient and seed values. Note: If you do not
specify a coefficient, the default value (0x7cc) is used. If you do
not specify a seed value, the default value (0) is used.
info
Displays current configuration.
sampling-rate
Configures the IPFIX sampling rate from 1 to 10,000 for every N
packets. The default setting is 1 for continuous monitoring.
ERS-8300# config ip ipfix port <slot|port>?
Sub-Context:
Current Context:
all-traffic <enable|disable>
flush [export-and-flush]
info
where:
Avaya Inc. – External Distribution
9
avaya.com
Parameter
Description
active-timeout
Specifies the active timeout in minutes. Range is from 1 to 60 minutes.
aging-interval
Specifies the interval, in minutes, when to flush out the old flows after
they have stopped. Range is from 10 to 3600 seconds. Default setting
is 30 minutes.
export-interval
Specifies the interval, in seconds, between exports. Range is from 10
to 3600 seconds. Default value is 50 seconds.
exporter-state
Indicates whether IPFIX is enabled or disabled on the switch.
info
Displays configuration.
2.2 Setting IPFIX timers
CLI (same output as shown via PPCLI below):
ERS 8600
o ERS-8600(config)# ip ipfix slot <slot #> ?
ERS 8300
o ERS-8300(config)# ip ipfix ?
PPCLI:
ERS 8600
o ERS-8600# config ip ipfix slot <slot #> ?
Sub-Context: collector
Current Context:
active-timeout <value in mins>
aging-interval <value in secs>
export-interval <value in secs>
exporter-state <enable|disable>
info
Sub-Context: collector port
Current Context:
active-timeout <value in mins>
aging-interval <value in secs>
export-interval <value in secs>
exporter-state <enable|disable>
info state <enable|disable>