Command:
fdpi_cli dump flow cache format
Output example:
nthr=1 slic=3 proto=6 ip_1=192.168.4.20:65163 ip_2=217.69.133.145:443 ssid=1675E5CF5FB1337 dpip=91 ittr=16 tmlb='2019/10/30 02:02:51, -357.642147s (4148500652028035 ticks)' ialf=0 drct=0x1 iown=1 ilst=1 btsip=0x2 tcpbts_0='-APRSF' tcpbts_1='-AP-S-' qoest=0 qoef_0=0 qoef_1=0 qoer_0=6 qoer_1=6 whip=94.140.198.86:33326 itrnsld=1 igcache=0 gre_pid=0 gre_mtd=0
Field descriptions:
nthr=1 — thread number where the entry is placed (for multicluster setups, it may differ from iown)slic=3 — cache slice numberproto=6 — IP protocolip_1=192.168.4.20:65163 ip_2=217.69.133.145:443 — pair of IP addresses and ports identifying the entry. If the protocol does not use ports, the trailing values are 0ssid=1675E5CF5FB1337 — session identifierdpip=91 — DPI protocolittr=16 — index in the reused entry queuetmlb='2019/10/30 02:02:51, -357.642147s (4148500652028035 ticks)' — last access time for the entryialf=0 — processing queue number:en_nalfs_shrt = 0 — short-lived queueen_nalfs_long = 1 — long-lived queuedrct=0x1 — conditions under which the entry was created. The lower 4 bits define the packet direction used to create the key and, accordingly, the ownership of src_ip and dst_ipdrct == 0 — h_ip_1 is src_ipdrct == 1 — h_ip_1 is dst_ipflw_dir used when the key was creatediown=1 — thread number that created the entryilst=1 — thread number that last processed the entrybtsip=0x2 — service bits for flow processingtcpbts_0='-APRSF' tcpbts_1='-AP-S-' — TCP connection flags in both directions:( tcp_bits_ & 0x0020 ) ? 'U' : '-' ( tcp_bits_ & 0x0010 ) ? 'A' : '-' ( tcp_bits_ & 0x0008 ) ? 'P' : '-' ( tcp_bits_ & 0x0004 ) ? 'R' : '-' ( tcp_bits_ & 0x0002 ) ? 'S' : '-' ( tcp_bits_ & 0x0001 ) ? 'F' : '-'
qoest=0 — QoE status:enst_none = 0,enst_ack — waiting for client ACK in response to server SYN+ACKenst_fin_ack — waiting for server FIN+ACK in response to client FINenst_ack_srvfin — waiting for server ACK in response to client FIN+ACK (server sent FIN first)qoef_0=0 qoef_1=0 — number of fragmented packets in both directionsqoer_0=6 qoer_1=6 — number of retransmissions in both directionspktp_0=1 pktp_1=0 — number of packets with payload in both directions, up to 65000btsp_0=1 btsp_1=0 — payload volume in both directions, up to 65Kwhoisc=0 or 1 — connection initiatorwhip=94.140.198.86:33326 — allocated public IP address and portitrnsld=1 — profile data index used to allocate the public addressigcache=0 — index in the corresponding gray-to-public address translation cache slicegre_pid=0 — detected callidgre_mtd=0 — public address allocation method for GRE