Example: Verifying AppTrack Operation (CLI)

The following examples provide two ways to monitor AppTrack operation.

• View AppTrack counters periodically to monitor tracking.
  user@host> show security application-tracking counters

  AVT counters:              				Value
   Session create messages            1
   Session close messages             1
   Session volume updates             0
   Failed messages                    0
  

• Compare byte and packet counts in logged messages with the session statistics from the show command output.
  user@host> show security flow session

  Flow Sessions on FPC6 PIC0:
  
  Session ID: 120000044, Policy name: policy-in-out/4, Timeout: 1796, Valid
  In: 4.0.0.1/39075 --> 5.0.0.1/21;tcp, If: ge-0/0/0.0, Pkts: 22, Bytes: 1032
  Out: 5.0.0.1/21 --> 4.0.0.1/39075;tcp, If: ge-0/0/1.0, Pkts: 24, Bytes: 1442
  
  Valid sessions: 1
  Pending sessions: 0
  Invalidated sessions: 0
  Sessions in other states: 0
  Total sessions: 1
  

  Byte and packet totals in the session statistics should approximate the counts logged by AppTrack but might not be exactly the same. AppTrack counts only incoming bytes and packets. System-generated packets are not included in the total, and dropped packets are not deducted.

For command option descriptions and values, see the Junos OS CLI Reference.

For general information about monitoring events and managing system log files, see the Junos OS Administration Guide for Security Devices.