anchor.diff:  Cluster administrators can choose to xref:../admin_guide/pod_network.adoc#admin-guide-pod-network[modify
   the project networks] using the administrator CLI.
   
  +Check VNIDs by running:
  +
  +----
  +$ oc get netnamespace
  +----
  +
   [[external-access-to-the-cluster-network]]
   == External Access to the Cluster Network
   
  
positive.code: [[configuring-sdn-config-pod-network-ansible]]
  == Configuring the Pod Network with Ansible
  
  For initial xref:../install_config/install/advanced_install.adoc#install-config-install-advanced-install[advanced installations], 
  the *ovs-subnet* plug-in is installed and configured by default, though it can 
  be
  xref:../install_config/install/advanced_install.adoc#configuring-ansible[overridden during installation] 
  using the
  xref:../install_config/install/advanced_install.adoc#configuring-cluster-variables[`*os_sdn_network_plugin_name*` parameter], 
  which is configurable in the Ansible inventory file.
  
  .Example SDN Configuration with Ansible
  
negative.code: # would mean a /24 network on the host.
  #osm_host_subnet_length=8
  
  # This variable specifies the service proxy implementation to use:
  # either iptables for the pure-iptables version (the default),
  # or userspace for the userspace proxy.
  #openshift_node_proxy_mode=iptables
  ----
  ====
  
  ifdef::openshift-enterprise[]
  For initial xref:../install_config/install/quick_install.adoc#install-config-install-quick-install[quick installations],
  the *ovs-subnet* plug-in is installed and configured by default as well, and can
  be
  xref:../install_config/master_node_configuration.adoc#master-configuration-files[reconfigured post-installation]
  using the `*networkConfig*` stanza of the *_master-config.yaml_* file.
  endif::[]
  
  