Connect DNAC VIP Issue

[linfeng]

HI,

I setup DNAC1.2.3, I had config the "Cluster Virtual IP Address". 10.1.1.240.

And the Enterprise 10G Interface set 10.1.1.237.

In the beginning, I can connect DNAC Gui from "10.1.1.240" and "10.1.1.237".

When DNAC upgrade to 1.2.6, Only can connect "10.1.1.237".

Have encountered this situation?

[Tomas de Leon · Accepted solution]

Cisco DNA Center's Virtual IP address (VIP) may become unreachable following
an upgrade to version 1.2.5 or later, if the cluster link is not physically cabled up,
with line protocol up.

Workaround:
Bring clusterlink up and VIP will be reachable within 5 minutes or so.
If not restart keepalived service 

magctl service restart --hard keepalived

[xavierkang]

Hi All, I think I'm facing similar issue as well. Anyone can help me on this.

DNA Center (Standalone, only 1 node)

Old DNA Center Version 1.1.7

Enterprise Port : 10.96.96.131/26 (Physical Connected)

Cluster Port: 10.96.96.195/26 (Disconnected)

VIP for Enterprise: 10.96.96.135/26

At old DNA Version, I'm able to ping and access GUI using VIP.

After upgrade to 1.2.6 or latest version 1.2.10. I'm not able to ping the VIP anymore. I do check on "maglev-config update" which require me to add one more VIP for Cluster Node. And I do add it.

New DNA Center Version 1.2.10

Enterprise Port : 10.96.96.131/26 (Physical Connected)

Cluster Port: 10.96.96.195/26 (Disconnected)

VIP for Enterprise: 10.96.96.135/26

VIP for Cluster: 10.96.96.194/26

Now, I'm totally not able to ping or access  DNA Center using the VIP(Enterprise). Is that mean, I have to connect the cluster node as well, than only able to ping and access through VIP(Enterprise). Or there is other way solution for this?

[VickyShenton53250]

Hi Xavier,

I appreciate that you posted this a while ago however I am experiencing the same issue with the VIP. How did you manage to resolve this?

Kind regards,

Vicky