interface mgmt0 ip address 192.168.0.1 255.255.255.0 no shutdown ! ! interface vlan 1 ip address dhcp no shutdown
EX2010P-F03DE0(config)# int vlan 1 EX2010P-F03DE0(config-if)# ip address 192.168.0.1 255.255.255.0 % This IP Address overlaps with an existing Interface IP Address EX2010P-F03DE0(config)# int vlan 2 EX2010P-F03DE0(config-if)# ip address 192.168.0.1 255.255.255.0 % This IP Address overlaps with an existing Interface IP Address
And this result is the same when we provide an IP address for an in-band VLAN if. from the same subnet as the mgmt0 interface. Mgmt0 should be az out-of-band interface, regarding the vendor documentations and presales presentations.
Is this the correct working or is it a major software bug?
Workaround: set the mgmt0 IP to a link-local address or anything else.
Then I think this can not be marketed as “OOB”, or there should be a warning notice (with bold and red ) in the documentations.
We designed a project with DHCP IP addresses for the switch VLAN if. itself (since only network connectivity is the target to reach cnMaestro, we manage everything remotely from the cloud) and faced at multiple customers that their ISP CPE or so are providing addresses from the same subnet.
I have worked with various vendors and all of them used vrf/vpn-instances for real, out-of-band solution and logical separation. In the cnMatrix case, this behavior is something like “dedicated mgmt” port or so.