.. _network_docker_container_range:

Network Docker Container Range
------------------------------

.. index:: network;network container range
.. index:: cluster;cluster run


.. _12.5(1)|VOSSUC-20683:
.. _19.1|VOSSUC-20683:
.. _19.2.1|EKB-2601:

.. important::
   
   When troubleshooting network issues, verify that the address range is not in use.

   If it is in use, modify the Private Address Space using the 
   **network container range add <private IP>** command as 
   described below.


RFC-1918 states that the following three blocks of the IP address space
are reserved for private internets:

::

     10.0.0.0        -   10.255.255.255  (10/8 prefix)
     172.16.0.0      -   172.31.255.255  (172.16/12 prefix)
     192.168.0.0     -   192.168.255.255 (192.168/16 prefix)

This subnet block address range can be modified to another Private Address Space
if needed. 

Use the command **network container range list** to see
the current Private Address Space.

For example:

::

   $ network container range list
       range: 10.1.2.1/24

Use the command **network container range add <private IP>** to modify
the Private Address Space.

.. important::

   A valid Private Address IP is required as input.

   The range ``/24`` is appended to the IP.
   For example, if ``192.168.0.6`` is used, the
   Private Address range ``192.168.0.0/24`` is
   used.

In a clustered environment, you could use **cluster run all network container range add <private IP>**,
but if required, the Private Address Space can be also set to be different on each node by running the **add** command
on each individual node.


For example:

::

   $ network container range add 192.168.2.3
   You are about to restart all services. Do you wish to continue?y
   Application processes stopped.  (note this line changes dynamically)
   
   Reconfiguring applications....
   Application  processes started. (note this line changes dynamically)