Unable to connect to destination(sersuri) cluster from source(nagpur) cluster  worker  node when static route is added.

Source cluster has OAM VLAN interrface configured with nmstate. This vlan have 
  static route for subnet of other destination OCP cluster. 

Getting following error when connecting to the nodes

~~~~
$ oc --kubeconfig=tn.config get nodes   -v=9
I0223 16:47:44.692975 1704991 round_trippers.go:495] HTTP Trace: DNS Lookup for api.ck01.rh.ser.tn resolved to [{172.18.228.30 }]
I0223 16:47:44.728686 1704991 round_trippers.go:510] HTTP Trace: Dial to tcp:172.18.228.30:6443 succeed
I0223 16:48:12.388888 1704991 round_trippers.go:553] GET https://api.ck01.rh.ser.tn:6443/api?timeout=32s  in 27698 milliseconds
I0223 16:48:12.388946 1704991 round_trippers.go:570] HTTP Statistics: DNSLookup 2 ms Dial 35 ms TLSHandshake 48 ms Duration 27698 ms
I0223 16:48:12.388970 1704991 round_trippers.go:577] Response Headers:
I0223 16:48:12.389074 1704991 cached_discovery.go:119] skipped caching discovery info due to Get "https://api.ck01.rh.ser.tn:6443/api?timeout=32s": context deadline exceeded - error from a previous attempt: unexpected EOF
error: Get "https://api.ck01.rh.ser.tn:6443/api?timeout=32s": context deadline exceeded - error from a previous attempt: unexpected EOF
~~~~

source cluster (Nagpur):
 IP: 10.55.187.1

destination cluster (Serisuri -chennai):
 IP : 172.18.228.30

OC commands does not work when the static route is added on the destination cluster.

Following static route is added on some of worker nodes on destination cluster
~~~
$ ip r l | grep 172.18.228
172.18.228.0/24  via 10.55.187.1 dev bond0 3803 proto static metric 401
~~~

~~~~
Following curl works with static route and witout static route added

$ curl -H "Authorization: Bearer <token here>" "https://api.<OpenShiftServer>:6443/api/v1/namespaces/<project>/pods/"

~~~~

    4.12.46-assembly.art8712

    OC commads is not working when the static route is added

     OC commads should work when the static route is added