anchor.diff:  10.1.0.0/16 dev tun0  proto kernel  scope link                          # This sends all pod traffic into OVS
   10.1.1.0/24 dev tun0  proto kernel  scope link  src 10.1.1.1            # This is traffic going to local pods, overriding the above
   169.254.0.0/16 dev ens3  scope link  metric 1002                        # This is for Zeroconf (may not be present)
  -172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1    # Docker's private IPs... used only by things directly configured by docker; not openshift
  +172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1    # Docker's private IPs... used only by things directly configured by docker; not OpenShift
   192.168.122.0/24 dev ens3  proto kernel  scope link  src 192.168.122.46 # The physical interface on the local subnet
   ....
   
  -You should see the 10.1.x.x lines (assuming you have your pod network set to the default range in your configuration).  If you do not, check the openshift logs (see the <<reading-the-logs>> section)
  +You should see the 10.1.x.x lines (assuming you have your pod network set to the default range in your configuration).  If you do not, check the OpenShift logs (see the <<reading-the-logs>> section)
   
   === Is the Open vSwitch confured correctly?
   
  
positive.code: network.  Only reachable from the client nodes.
  Service Address:: An IP address that represents the service, and is
  mapped to a pod address internally.  These are assigned and managed by
  Openshift.  By default they are assigned out of the 172.30.0.0/16
  network.  Only reachable from the client nodes.
  
  The following diagram shows all of the pieces involved with external access.
  
negative.code: 
  You can list all of the ports that ovs knows about:
  ....
  # ovs-ofctl -O OpenFlow13 dump-ports-desc br0
  OFPST_PORT_DESC reply (OF1.3) (xid=0x2):
   1(vxlan0): addr:9e:f1:7d:4d:19:4f
       config:     0
  