[GitHub] [trafficcontrol] mattjackson220 commented on a change in pull request #4142: Allow IPv6 Only Caches, including monitoring and routing

[GitBox <gi...@apache.org>]

mattjackson220 commented on a change in pull request #4142: Allow IPv6 Only Caches, including monitoring and routing
URL: https://github.com/apache/trafficcontrol/pull/4142#discussion_r356297530
 
 

 ##########
 File path: docs/source/admin/traffic_monitor.rst
 ##########
 @@ -50,8 +50,15 @@ Configuring Traffic Monitor
 
 Configuration Overview
 ----------------------
-Traffic Monitor is configured via two JSON configuration files, :file:`traffic_ops.cfg` and :file:`traffic_monitor.cfg`, by default located in the ``conf`` directory in the install location. :file:`traffic_ops.cfg` contains Traffic Ops connection information. Specify the URL, username, and password for the instance of Traffic Ops of which this Traffic Monitor is a member. :file:`traffic_monitor.cfg` contains log file locations, as well as detailed application configuration variables such as processing flush times and initial poll intervals. Once started with the correct configuration, Traffic Monitor downloads its configuration from Traffic Ops and begins polling :term:`cache server` s. Once every :term:`cache server` has been polled, :ref:`health-proto` state is available via RESTful JSON endpoints and a web browser UI.
+Traffic Monitor is configured via two JSON configuration files, :file:`traffic_ops.cfg` and :file:`traffic_monitor.cfg`, by default located in the ``conf`` directory in the install location. :file:`traffic_ops.cfg` contains Traffic Ops connection information. Specify the URL, username, and password for the instance of Traffic Ops of which this Traffic Monitor is a member. :file:`traffic_monitor.cfg` contains log file locations, as well as detailed application configuration variables such as processing flush times, initial poll intervals, and the polling protocols. Once started with the correct configuration, Traffic Monitor downloads its configuration from Traffic Ops and begins polling :term:`cache server` s. Once every :term:`cache server` has been polled, :ref:`health-proto` state is available via RESTful JSON endpoints and a web browser UI.
 
+Polling protocol can be set for peers and caches and has 3 options:
+
+ipv4only (the default): TM will communicate with the peers or caches only over IPv4
+ipv6only: TM will communicate with the peers or caches only over IPv6 (use case for peers is if the other TMs are only available over IPv6)
+both: TM will alternate its communication between IPv4 and IPv6 (note: this does not affect the polling frequency so if polling frequency is 1 second IPv4 will be polled every 2 seconds)
 
 Review comment:
   done

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services