Address/subnet already configured on an Interface

Running vThunder 6.0.7 build 78 on ESXi

In my initial setup, I am attempting to assign an IP to my e1 interface, and I continually get this error: Address/subnet 192.168.1.64 already configured on an Interface.

Management IP is 192.168.1.63/24

The IP is open in my subnet and I don’t have the IP assigned anywhere else. I have even reset the instance. Thoughts?

YungMoose: ACOS provides routing so you can’t use the same subnet (192.168.1.0/24) on two different (L3) interfaces. Ideally, you would use 192.168.1.63 for all management related functions on your ADC (SSH, TACACS, SNMP, syslog, etc.). Your e1 interface is part of the dataplane in ACOS and can be used for client and server traffic. However, the e1 interface must be in a different subnet to prevent the error you were seeing.

So , I had a test load balancer up and running with my dummy web servers at .65 and .66 on the same subnet. But when I went to my VPE at .64 it would just take me to the admin GUI. Is this the same reason why? I need to have my dataplane in a different subnet?

YungMoose: The management interface needs to be in a different subnet than the dataplane interfaces.

You can use the IP from a dataplane interface interface for management access by adding the following to the config;

enable-management service ssh
ethernet 1
!
enable-management service http
ethernet 1
!
enable-management service https
ethernet 1

1 Like

I now have my dataplane on a different subnet but my VIP still goes to the GUI login.

vThunder management IP 192.168.1.1

VIP 192.168.3.64/32

Web server 1 192.1688.3.65

Web server 2 192.1688.3.66

Both subnets are on the same interface with default vlan

What am I missing?

YungMoose,

Sorry that you are having these issues. A couple of questions:

  1. When you say your VIP is still going to the GUI, are you saying that when you open a browser and point it at 192.168.3.64, you are seeing the management GUI of the A10?

  2. Please run the following commands from your CLI and reply back to this post with the output. This will help me understand the issue you are seeing.

    show run
    show interface brief
    show ip int
    show ip route
    show slb service-group
    show slb virtual-server