AIOps - Unable to login, "502 Bad Gateway" error after adding a 2nd nic
search cancel

AIOps - Unable to login, "502 Bad Gateway" error after adding a 2nd nic


Article ID: 219304


Updated On:


DX Operational Intelligence DX Application Performance Management CA App Experience Analytics


We added a 2nd nic to the k8s master server: 

- one nic for k8s communication
- one nic for management

after adding the 2nd nic we are no longer able to open the DX Admin login page, we get "502 Bad Gateway" error message


we tried restarting dxi using <dx-platform>/tools/ stop/start but it didn't help

we can see many axa-services pods are unable to startup and remain in "Init" status


DX Platform 2x


This is not a Broadcom issue, instead an Nginx, calico or flannel configuration issue.

Calico cni node pods are using the new interface eth1 instead of the eth0 due its ip autodetect mode.

Below are two lines that tell calico to use a different interface:

  value: "interface=eth0"

For more information refer to


1. Login to k8s master

2. Edit calico-node Daemonset:

kubectl -n kube-system edit ds calico-node

3. Add below property:

  value: "interface=eth0"

As below:

4. Verification: 

a) Check all the  pods in kube-system are running:

kubectl get pods -nkube-system

NAME                                                   READY   STATUS    RESTARTS   AGE
calico-kube-controllers-7f4f5bf95d-hh4bn               1/1     Running   0          102m
calico-node-5xzw7                                      1/1     Running   0          95m
calico-node-nrnff                                      1/1     Running   0          96m
calico-node-qv9st                                      1/1     Running   0          96m
calico-node-wj4ch                                      1/1     Running   0          96m
calico-node-wm4bb                                      1/1     Running   0          96m
coredns-f9fd979d6-p92cw                                1/1     Running   0          133m
coredns-f9fd979d6-vs66l                                1/1     Running   0          133m                     1/1     Running   0          133m           1/1     Running   0          84m  1/1     Running   1          133m
kube-proxy-5t2qg                                       1/1     Running   0          101m
kube-proxy-7g762                                       1/1     Running   0          101m
kube-proxy-97qx4                                       1/1     Running   0          101m
kube-proxy-p8kdb                                       1/1     Running   0          101m
kube-proxy-r7d5k                                       1/1     Running   0          133m           1/1     Running   1          133m

b) check each of  the calico-node-xyzzyx pod report the below message.

kubectl logs calico-node-wm4bb -nkube-system | grep "Using autodet"

2021-07-07 20:09:05.084 [INFO][9] startup/startup.go 788: Using autodetected IPv4 address #.#.#.#/21 on matching interface eth0


c) check ingress endpoint is working

In this example:


<head><title>404 Not Found</title></head>
<center><h1>404 Not Found</h1></center>

NOTE: when you use curl on port 80 i.e http , it usually returns  404 Not Found , that means your ingress is working fine. 


<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<center><h1>400 Bad Request</h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>

Additional Information

DX AIOPs Troubleshooting, Common Issues and Best Practices