topic DNAC Virtual IP Question in Software-Defined Access (SD-Access)

DNAC Virtual IP Question

Freemen — Mon, 07 Oct 2019 08:24:15 GMT

I have a new setup DNAC 1.2.10 with Virtual IP, however is not pingable nor enabled for GUI is that normal?

I notice that when i discover the device, the device get push snmp and syslog with the virtual IP, while the VIP not even UP.

Re: DNAC Virtual IP Question

jalejand — Mon, 07 Oct 2019 08:51:32 GMT

VIP reachability in a node directly depends on its physical interface status. There is a VIP for each configured IP.

Try getting these:

$ etcdctl get /maglev/config/cluster/cluster_network
$ kubectl get nodes
$ ip a
$ ping [VIP IP]

Re: DNAC Virtual IP Question

Freemen — Mon, 07 Oct 2019 09:24:45 GMT

$ etcdctl get /maglev/config/cluster/cluster_network << appear here
$ kubectl get nodes 
$ ip a <<< not appear here
$ ping [VIP IP] <<< cannot PING

Hi I not sure if that is normal?

Re: DNAC Virtual IP Question

Freemen — Mon, 07 Oct 2019 09:35:43 GMT

I Think i know why already, I just double check the Installation Guide, because i now is running on 1 node, thus i not connect my cluster port, seam like i need another 10G SFP to make it work then.

Enter a space-separated list of the virtual IP addresses used for traffic between the cluster and your network. This is required for both three-node clusters and single-node clusters that will be converted into a three-node cluster in the future. If you have a single-node cluster setup and plan to stick with it, skip this step and proceed to Step 11.

IMPORTANT: You must enter one virtual IP address for each configured network interface. You will not be able to complete the wizard unless you do so. These addresses are tied to the cluster link's status, which must be in the UP state.