.. _example_system_conntrack_logging_logging:
#######
Logging
#######
The following scenarios show how to configure
the conntrack logging option with different
traffic policies and services enabled, in order
to check that all fields are displayed correctly and all events are captured.
***************
Test new events
***************
Description
===========
Test to check NEW sessions events are captured
Scenario
========
.. include:: logging/testnewevents
.. raw:: html
******************
Test update events
******************
Description
===========
Test to check UPDATE sessions events are captured
Scenario
========
.. include:: logging/testupdateevents
.. raw:: html
*******************
Test destroy events
*******************
Description
===========
Test to check DESTROY sessions events are captured
Scenario
========
.. include:: logging/testdestroyevents
.. raw:: html
********************
Test default logging
********************
Description
===========
Set a simple configuration, send a ``ping`` command from one device to other
and check that default fields appear when running ``system journal show``.
Scenario
========
.. include:: logging/testdefaultlogging
.. raw:: html
*********************
Test policies logging
*********************
Description
===========
Set a simple configuration with mark and label traffic policies,
send a ``ping`` command from one device to other
and check that default, mark and label fields appear when running ``system journal show``.
Scenario
========
.. include:: logging/testpolicieslogging
.. raw:: html
****************
Test VRF logging
****************
Description
===========
Set a simple configuration with a vrf,
send a ``ping`` command from one device to other
and check that default and vrf fields appear when running ``system journal show``.
Scenario
========
.. include:: logging/testvrflogging
.. raw:: html
***********************
Test Not-Bypass logging
***********************
Description
===========
Set a simple configuration with a firewall service,
send a ``ping`` command from one device to other
and check that default and bypass fields appear when running ``system journal show``.
Scenario
========
.. include:: logging/testnot-bypasslogging
.. raw:: html
*****************
Test Offload flag
*****************
Description
===========
Set a simple configuration with ``DUT0`` as an intermediary between ``DUT1``
and ``DUT2``. Initiate a ``ssh`` connection from ``DUT1`` to ``DUT2``
and check that default and offload fields appear when running ``system journal show``.
Scenario
========
.. include:: logging/testoffloadflag
.. raw:: html