Configuring Observation Domain ID and Source ID for Version 9 and IPFIX Flows
For IPFIX flows, an identifier of an observation domain is locally unique to an exporting process of the templates. The export process uses the observation domain ID to uniquely identify to the collection process in which the flows were metered. We recommend that you configure this ID to be unique for each IPFIX flow. A value of 0 indicates that no specific observation domain is identified by this information element. Typically, this attribute is used to limit the scope of other information elements. If the observation domain is not unique, the collector cannot uniquely identify an IPFIX device.
For version 9 flows, a 32-bit value that identifies the Exporter Observation Domain is called the source ID. NetFlow collectors use the combination of the source IP address and the source ID field to separate different export streams originating from the same exporter.
To specify the observation domain ID for IPFIX flows, include the
observation-domain-id domain-id statement at
the [edit services flow-monitoring version-ipfix template
template-name] hierarchy level.
[edit services flow-monitoring version-ipfix]
template template-name {
observation-domain-id domain-id;
}
To specify the source ID for version 9 flows, include the source-id
source-id statement at the [edit
services flow-monitoring version9 template
template-name] hierarchy level.
[edit services flow-monitoring version9]
template template-name {
source-id source-id;
}
Considerations for MX and QFX Series
If you configure the same Observation Domain ID for different template types, such as for IPv4 and IPv6, it does not impact flow monitoring because the actual or the base observation domain ID is transmitted in the flow. The actual observation domain ID is derived from the value you configure and also in conjunction with other parameters such as the slot number, lookup chip (LU) instance, Packet Forwarding Engine instance. Such a method of computation of the observation domain ID ensures that this ID is not the same for two IPFIX devices.
Until Junos OS Release 13.3, the observation domain ID is predefined and is set to a fixed value, which is derived from the combination of FPC slot, sampling protocol, PFE Instance and LU Instance fields. This derivation creates a unique observation domain per LU per family. Starting with Junos OS Release 14.1, you can configure the observation domain ID, which causes the first 8 bits of the field to be configured.
The following modifications have been made:
-
FPC slots are expanded to 8 bits to enable more slots to be configured in an MX Series Virtual Chassis configuration.
-
8 bits of the configured observation domain ID are used.
-
You can configure a value for the observation domain ID in the range of 0 through 255.
-
The Protocol field is increased to 3 bits to provide support for additional protocols in inline flow monitoring.
-
You can associate the observation domain ID with templates by using the
observation-domain-id domain-idstatement at the[edit services flow- monitoring version-ipfix template template-name]hierarchy level.
Table 1 describes observation domain ID values for different combinations of the configured domain ID, protocol family, FPC slot, and the Packet Forwarding Engine and lookup chip instances.
|
Configured Value |
Protocol Family |
FPC Slot |
PFE Inst |
LU Inst |
Observation Domain Id Conf val rsvd 1proto slot LUInst PFEInst xxxx xxxx xxxx 1xxx xxxx xxxx xxxx xxxx |
|---|---|---|---|---|---|
|
None |
IPv4 (0) |
1 |
1 |
0 |
0000 0000 0000 1000 0000 0001 0000 0001 0x00080101 |
|
None |
IPv6 (1) |
1 |
1 |
0 |
0000 0000 0000 1001 0000 0001 0000 0001 0x00090101 |
|
None |
VPLS (2) |
1 |
1 |
0 |
0000 0000 0000 1010 0000 0001 0000 0001 0x000A0101 |
|
None |
MPLS (3) |
1 |
1 |
0 |
0000 0000 0000 1011 0000 0001 0000 0001 0x000B0101 |
|
4 |
IPv4 (0) |
1 |
1 |
0 |
0000 0100 0000 1000 0000 0001 0000 0001 0x04080101 |
|
190 |
IPv4 (0) |
1 |
1 |
0 |
1101 1110 0000 1000 0000 0001 0000 0001 0xBE080101 |
|
4 |
IPv4 (0) |
2 |
1 |
1 |
0000 0100 0000 1000 0000 0010 0001 0001 0x04080211 |
|
4 |
IPv6 (1) |
1 |
1 |
0 |
0000 0100 0000 1001 0000 0001 0001 0000 0x04090110 |
|
190 |
IPv6 (1) |
1 |
1 |
0 |
1101 1110 0000 1001 0000 0001 0001 0000 0xBE090110 |
|
4 |
VPLS (2) |
2 |
2 |
0 |
0000 0100 0000 1010 0000 0010 0010 0000 0x040A0220 |
|
10 |
IPv4 (0) |
28 |
2 |
1 |
0000 1010 0000 1000 0001 1100 0010 0001 0x0A081C21 |
Considerations for PTX Series
When you configure the observation domain ID, the software attaches the ID to a particular template type.
If you configure the same observation domain ID for two different template types, such as for IPv4 and IPv6, this does not impact flow monitoring, because the configured ID is not what is being sent. The value sent in the packets is derived from that configured value and the FPC slot value. This method ensures two IPFIX devices can never have the same value of observation domain ID. As you can see in Table 2:
-
The configurable observation domain ID value is 8 bits. Therefore, the value range is 0 to 255.
-
One bit is always set to 1, ensuring that the observation domain ID value sent in the packet is never 0.
|
Configured observation domain ID value (8 bits) |
(15 bits set to zero) |
1 bit (set to 1) | FPC slot (8 bits) |
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.