Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

export-by-asic

Syntax

Hierarchy Level

Description

For those line cards that support the BX ASIC, configure this statement to export IPFIX packets using the ASIC, for Inline Monitoring Services (IMON). Both the Packet Forwarding Engine on the sampling line card and the Packet Forwarding Engine on the export line card must be running in BX-v2 mode to support this feature.

Table 1: Line card combinations
Sampling line card Packet Forwarding Engine (prepends IPFIX metadata) Export line card Packet Forwarding Engine (encapsulates IPFIX header) Support of hardware-based IMON
BX-v2 BX-v2 Supported
BX-v1 BX-v2 Not Supported. It is not a valid combination. All BX line cards always run on either v1 or v2 mode in a chassis.
BX-v2 BX-v1
BX-v1 BX-v1 Not Supported
BT BX-v2 Not Supported
BX-v2 BT Not Supported

When you configure the export-by-asic statement, the system ignores all configuration of fields on the primary-data-record-fields statement at the [edit services inline-monitoring template template-name] hierarchy level for the instance.

Fields

The fields shown below are always reported in this order when you configure the export-by-asic statement:

Table 2: IE fields reported when you configure the export-by-asic statement
No. IE ID IE Length IE Description Encoding Details

1

OCLJ-CPID

4B

 Discard precedence and traffic class 4'd10, 22'd0, discard_precendence[1:0], traffic_class[3:0]

2

OCLJ-CPID

4B

Upper portion of state byte array

4'd9, 12'd0, state_byte_array[31:16]

3

OCLJ-CPID

4B

Lower portion of state byte array

4'd8, 12'd0, state_byte_array[15:0]

4

OCLJ-CPID

4B

Input physical port and input physical interface index

4'd7, ipp_physical_port, 1'b0, ingress_global_port_id[18:0]

5

OCLJ-CPID

4B

 Input logical interface index

4'd6, 8'd0, ingress_input_interface_index[19:0]

6

OCLJ-CPID

4B

Ingress : VOQ number

Egress : PFE instance number and Output physical port number

ingress : {4'd5, 12'd0, voq_number[15:0]}, egress : {4'd4, 15'd0, tl_num[4:0], ipp_physical_port[7:0]}

7

OCLJ-CPID

4B

 Forwarding nexthop ID

4'd3, 4'd0, egress_nexthop_id[23:0]

8

OCLJ-CPID

4B

Ingress : layer3_vpn

Egress : ignore

ingress : {4'd2, 16'hFFFF, layer3_vpn[11:0]}, egress : {4'd2, 16'hFFFF, 12'hFFF}

9

OCLJ-CPID

4B

Lookup_type and trapcode

4'd1, 13'd0, lookup_type[6:0], trapcode[7:0]

10

325

8B

observationTimeNanoSeconds

timestamp[63:0]

11

61

1B

flowDirection

0: Input , 1:Output

12

312

4B

dataLinkFrameSize

Length of sampled data link frame

13

210

1B

paddingOctets

One byte of padding to make next field as 4Bytes boundary (ASIC consider each field as 4 bytes in length)

14

315

Variable

dataLinkFrameSelection

N octet from data link frame of the monitored packet, including any Layer 2 header. This field muist be encoded as explained in section 7 of RFC 5101.

Limitations

  • When you configure the export-by-asic statement, you can only configure a single collector.

  • When you configure the export-by-asic statement, the IE dataLinkFrameSection is supported in multiples of 128 bytes only.

  • Statistics are maintained by the BX ASIC. These statistics are refreshed to the control plane every 10 seconds. Therefore, statistics displayed by any show command are cached, and are 10 seconds old for the worst case.

  • We do not recommend exporting through the management interface. When you configure hardware-based export, if the collector is reachable through management interface, all export records are sent to the Routing Engine. The Routing Engine then discards those received export records, thereby consuming host path bandwidth.

  • The checksum in the UDP header of IPFIX export record will be always zero.

  • The dataLinkFrameSize field reports an additional 32 bytes (minimum) in the egress sampling case. For example, if the sampled or up-lifted packet size is 96, this field reports 96+32=128. 32 bytes is the size of the loopback header. If the packet carries additional information (DFs), these extra bytes may be more than 32 bytes.

  • The identifier field in the IP header of the IPFIX export record is set to zero.

  • The timestamp_low field reports seconds since 1970 Jan 01. The timestamp_high field reports nano-seconds relative to the current second. The receiver should manipulate the timestamp_low and timestamp_high fields to get a timestamp in nanoseconds since 1970 Jan 01, if needed.

  • When performing sampling of GRE traffic on a node that is de-encapsulating traffic using the firewall action firewall decapsulate tunnel-end-point, the forwarding nexthop ID field reports value 0x80.

  • The auxiliary_egnh_id field reports a value of 0 in the egress sampling case.

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 24.4R1.