Configuring Template ID and Options Template ID for Version 9 and IPFIX Flows
Starting with Junos OS Release 14.1, you can define the template ID for version 9 and
IPFIX templates for inline flow monitoring. To specify the template ID for version 9
flows, include the template-id id
statement at
the [edit services flow-monitoring version9 template
template-name]
hierarchy level.
Template ID is implemented differently on SRX Series Firewalls. You cannot configure the template ID, instead you should assign the template ID dynamically.
[edit services flow-monitoring version9] template template-name { template-id id; }
To specify the template ID for version IPFIX flows, include the
template-id
statement at the [edit services
flow-monitoring version-ipfix template
template-name]
hierarchy level.
[edit services flow-monitoring version-ipfix] template template-name { template-id id; }
To specify the options template ID for version 9 flows, include the
options-template-id
statement at the [edit services
flow-monitoring version9 template template-name]
hierarchy level.
[edit services flow-monitoring version9] template template-name { options-template-id id; }
To specify the options template ID for IPFIX flows, include the
options-template-id
statement at the [edit services
flow-monitoring version-ipfix template
template-name]
hierarchy level. The template ID and
options template ID can be a value in the range of 1024 through 65535. For PTX
Series routers, if you do not configure the template ID or options template ID, the
software assigns an ID in the default range of 256-511, and the ID is different for
each template.
[edit services flow-monitoring version-ipfix] template template-name { options-template-id id; }
Considerations for MX and QFX Series
The template ID and options template ID can be a value in the range of 1024 through 65535. If you do not configure values for the template ID and options template ID, default values are assumed for these IDs, which are different for the various address families. If you configure the same template ID or options template ID value for different address families, such a setting is not processed properly and might cause unexpected behavior. For example, if you configure the same template ID value for both IPv4 and IPv6, the collector validates the export data based on the template ID value that it last receives. In this case, if IPv6 is configured after IPv4, the value is effective for IPv6 and the default value is used for IPv4.
Up to Junos OS Release 13.3R1, the default values of template IDs for IPFIX flows for the different protocols or address families are:
-
IPv4 IPFIX flow template ID—256
-
IPv6 IPFIX flow template ID—257
-
VPLS IPFIX flow template ID—258
-
MPLS IPFIX flow template ID—259
Starting with Junos OS Release 14.1R1, the default values of template IDs for version 9 flows for the different protocols or address families are:
-
IPv4 version 9 flow template ID—320
-
IPv6 version 9 flow template ID—321
-
VPLS version 9 flow template ID—322
-
MPLS version 9 flow template ID—323
Up to Junos OS Release 13.3R1, the default values of options template IDs for IPFIX flows for the different protocols or address families are:
-
IPv4 IPFIX flow options template ID—512
-
IPv6 IPFIX flow options template ID—513
-
VPLS IPFIX flow options template ID—514
-
MPLS IPFIX flow options template ID—515
Starting with Junos OS Release 14.1R1, the default values of options template IDs for version 9 flows for the different protocols or address families are:
-
IPv4 version 9 flow options template ID—576
-
IPv6 version 9 flow options template ID—577
-
VPLS version 9 flow options template ID—578
-
MPLS version 9 flow options template ID—579
Table 1 describes for the MX Series the values of data template and option template IDs for different protocols with default and configured values for IPFIX flows.
Family |
Configured Value |
Data Template |
Option Template |
---|---|---|---|
IPv4 |
None |
256 |
576 |
IPv4 |
1024-65535 |
1024-65535 |
1024-65535 |
IPv6 |
None |
257 |
577 |
IPv6 |
1024-65535 |
1024-65535 |
1024-65535 |
VPLS |
None |
258 |
578 |
VPLS |
1024-65535 |
1024-65535 |
1024-65535 |
MPLS |
None |
259 |
579 |
MPLS |
1024-65535 |
1024-65535 |
1024-65535 |
Table 2 describes for the MX Series the values of data template and option template IDs for different protocols with default and configured values for version 9 flows.
Family |
Configured Value |
Data Template |
Option Template |
---|---|---|---|
IPv4 |
None |
320 |
576 |
IPv4 |
1024-65535 |
1024-65535 |
1024-65535 |
IPv6 |
None |
321 |
577 |
IPv6 |
1024-65535 |
1024-65535 |
1024-65535 |
VPLS |
None |
322 |
578 |
VPLS |
1024-65535 |
1024-65535 |
1024-65535 |
MPLS |
None |
323 |
579 |
MPLS |
1024-65535 |
1024-65535 |
1024-65535 |
Table 3 describes for the MX Series the values of data template and option template IDs for different protocols with default and configured values for IPFIX flows.
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
If you choose to configure the template ID and options template ID, the range is 1024 to 65520. If you do not configure these IDs, the default values that are set are in the range 256-511 and are different for each template.
You can configure the template-id
and
option-template-id
statements for family inet
,
inet6
, and mpls
only.
You must not configure the same IDs for different templates (option or data template).
The operating system does not check to ensure that you do not configure the same ID value for different templates. If you configure the same ID value, such a setting is not processed properly and might cause unexpected behavior.
The template ID or options template ID range [configured template-id
or options-template-id
value + 20) is reserved and you must not
configure any another ID in this range. The difference between configured template
IDs or options template IDs across families should be at least 20; for example, if
template-id 1056
is configured for family
inet
, you should not configure template IDs in the range of 1056 to
1075 for any other families.
For Junos OS, if you change the template ID or options template ID, all flows are inactively timed out. New flows are learned afresh.
For Junos OS Evolved, if you change the template ID or options template ID, this change does not impact the flows.
Table 4 summarizes the data and option template ID values that correspond to configured values for template IDs, by family.
Template Family |
Configured Value for Data or Option Template ID |
Tunnel Observation Knob |
Range of Template ID For Primary and Secondary Template |
Template Type |
Reserved Data Template ID |
Reserved Option Template ID |
---|---|---|---|---|---|---|
IPv4 (Junos OS Evolved) |
T1 |
Not specified |
(T1...T1+20) |
IPv4 |
T1 |
T1 (Option Template-System Scope) T1+1 (Option Template – Template Scope) |
IPv4 (Junos OS) |
T1 |
MPLS-O-UDP |
(T1...T1+20) |
IPv4 |
T1 |
T1 (Option Template-System Scope) T1+1 (Option Template – Template Scope) |
IPv4-MPLS-IPv4 |
T1+1 |
T1 (Option Template-System Scope) T1+1 (Option Template – Template Scope) |
||||
IPv4-MPLS-IPv6 |
T1+2 |
T1 (Option Template-System Scope) T1+1 (Option Template – Template Scope) |
||||
IPv6 |
T2 |
Not specified |
(T2...T2+20) |
IPv6 |
T2 |
T2 (Option Template-System Scope) T2+1 (Option Template – Template Scope) |
MPLS |
T3 |
No |
(T3...T3+20) |
MPLS |
T3 |
T3 (Option Template-System Scope) T3+1 (Option Template – Template Scope) |
IPv4 |
(T3+1...T3+20) |
MPLS-IPv4 |
T3+1 |
|||
IPv6 |
(T3+1...T3+20) |
MPLS-IPv6 |
T3+2 |
|||
MPLS-O-UDP (Junos OS only) |
(T3+1...T3+20) |
MPLS-IPv4+UDP+MPLS_IPv4 |
T3+3 |
|||
MPLS-IPv4+UDP+MPLS_IPv6 |
T3+4 |
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.