BRAS tracing [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • ODT export
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • ODT export
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Next revision    		Previous revision
    en:dpi:bras_bng:cli:bras_l2_vlan_trace [2024/09/26 15:29] – created - external edit 127.0.0.1en:dpi:bras_bng:cli:bras_l2_vlan_trace [2026/01/26 08:02] (current) – elena.krasnobryzh
    Line 16: Line 16:
           * 0x0080 - to capture PPPoE packets using pcap; if the ''bras_pppoe_trace_mac'' option is not specified all the PPPoE traffic is written       * 0x0080 - to capture PPPoE packets using pcap; if the ''bras_pppoe_trace_mac'' option is not specified all the PPPoE traffic is written
           * 0x0100 - ICMP echo tracing       * 0x0100 - ICMP echo tracing
     +      * 0x1000 - output of errors in PPPoE packets in slave logs
     +      * 0x20000 - LAG tracing
      
     <note warning>Note that the tracing modes are ** highly** resource-consuming since the BRAS operating in such modes actively writes to the fastdpi_slave_x.log files. It is not recommended to apply tracing modes to the SSG at peak times.</note> <note warning>Note that the tracing modes are ** highly** resource-consuming since the BRAS operating in such modes actively writes to the fastdpi_slave_x.log files. It is not recommended to apply tracing modes to the SSG at peak times.</note>