Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

data-record-fields

Syntax

Hierarchy Level

Description

Use this configuration statement to add Information Elements to an IPFIX or a version 9 data record template. Any new or changed configuration of this statement is effective immediately and the exported packets contain the new information. Each Information Element is independent of the others and can be exported separately in the collector record.

For CoS, for IPFIX and version 9, you can export the following in the data record in the ingress direction only:

  • BGP community

  • AS path information

  • Policy map name

You configure policy maps at the [edit class-of-service policy-map] hierarchy level. For the ingress direction, if the packet does not have a policy map associated with it, IE 32765 reports "<empty string>". For the egress direction, IE 32765 reports "-NA-". See Assigning Rewrite Rules on a Per-Customer Basis Using Policy Maps to learn more about policy maps.

You can also export the BGP community and AS path information in the data record using IPFIX, per RFC 8549. The IPFIX collector should be RFC 6313 compliant to decode data records carrying fields with the basicList format.

count defines the size of the list that will be exported for that Information Element in the data record. If the total number of items exceeds the configured list size, the exported list contains the first and subsequent items up to and including the configured list size. For example, if the AS path list for the source prefix contains 8 AS numbers, but count is set to 4, only the first four AS numbers are exported in the data record.

Default

When this statement is not configured, the routing protocol process (rpd) only sends the peer AS number, origin AS number, and the BGP next-hop information. When this statement is configured with at least one Information Element, rpd sends all of the community and AS-path-related information. You do not have to configure all of the Information Elements.

Options

include-policy-map-name

Export the Juniper-specific enterprise Information Element ID 32765 in the data record templates ip4-template and ipv6-template. This new IE ID is 4 bytes long and contains the first 4 characters of the policy-map name. Therefore, the first 4 letters of your policy-map names should be unique. For example, if you have a policy map that sets DSCP code point 001011, you could begin your policy map name with the characters DS11.
source-prefix-as-path count

Export the source prefix AS path (Information Element 16, per RFC 6313).

  • Default: 8
destination-prefix-as-path count

Export the destination prefix AS path (Information Element 17, per RFC 6313).

  • Default: 8
bgp-source-standard-community count

Export the standard BGP community list for the source prefix, corresponding to a specific flow's source IP address (Information Element 484, per Appendix A of RFC 8549).

  • Default: 8
bgp-destination-standard-community count

Export the standard BGP community list for the destination prefix, corresponding to a specific flow's destination IP address (Information Element 485, per Appendix A of RFC 8549).

  • Default: 8
bgp-source-extended-community count

Export the extended BGP community list corresponding to a specific flow's source IP address (Information Element 487, per Appendix A of RFC 8549).

  • Default: 8
bgp-destination-extended-community count

Export the extended BGP community list corresponding to a specific flow's destination IP address (Information Element 488, per Appendix A of RFC 8549).

  • Default: 8
bgp-source-large-community count

Export the large BGP community list corresponding to a specific flow's source IP address (Information Element 490, per Appendix A of RFC 8549).

  • Default: 8
bgp-destination-large-community count

Export the large BGP community list corresponding to a specific flow's destination IP address (Information Element 491, per Appendix A of RFC 8549).

  • Default: 8

Additional Information

AS path and BGP community information are exported using the following Information Elements, as shown in Table 1:

Table 1: AS Path and BGP Community Information Elements
IE Name IE ID Export Data Type Format

BGP Community

 483

Unsigned 32-bit value

BGP Source Community List, which is a list of BGP community numbers (IE 483)

 484

basicList: data is exported in the format defined in the example in Appendix A of RFC 8549.

BGP Destination Community List, which is a list of BGP community numbers (IE 483)

 485

basicList: data is exported in the format defined in the example in Appendix A of RFC 8549.

BGP Extended Community

 486

8-byte octetArray

BGP Source Extended Community List, which is a list of BGP extended community numbers (IE 486)

 487

basicList: data is exported in the format defined in the example in Appendix A of RFC 8549.

BGP Destination Extended Community List, which is a list of BGP extended community numbers (IE 486)

 488

basicList: data is exported in the format defined in the example in Appendix A of RFC 8549.

BGP Large Community

 489

12-byte octetArray

BGP Source Large Community List, which is a list of BGP large community numbers (IE 489)

 490

basicList: data is exported in the format defined in the example in Appendix A of RFC 8549.

BGP Destination Large Community List, which is a list of BGP large community numbers (IE 489)

 491

basicList: data is exported in the format defined in the example in Appendix A of RFC 8549.

Source AS Path List

 16

basicList: data is exported in the format defined in RFC 6313.

Destination AS Path List

 17

basicList: data is exported in the format defined in RFC 6313.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Evolved Release 21.4R1.

Option include-policy-map-name introduced in Junos OS Evolved 24.4R1.

Related Documentation