cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
New Contributor

Having issue with configuring vlan 1 on 1550-24 after upgrading to R13-5-2

When trying to configure the units IP address I get this overlap and the vlan stays at 0.0.0.0

this is on a clean AOS install.

I can access the switch via CLI however without being able to set vlan 1 I cannot access the GUI.

any help is greatly appreciated.

Thanks

enable

Password:

Switch#config terminal

Switch(config)#interface vlan 1

Switch(config-intf-vlan 1)#ip address 10.10.10.1 255.255.255.0

%10.10.10.0 overlaps with vlan 1

0 Kudos
Reply
2 Replies
Highlighted
Anonymous
Not applicable

Re: Having issue with configuring vlan 1 on 1550-24 after upgrading to R13-5-2

The default configuration of the 1550 series switch is -

!

interface vlan 1

  ip address dhcp

  ip address  10.10.10.1  255.255.255.0  secondary

  ip route-cache express

  no shutdown

!

Therefore setting an IP address in another subnet will bring up the interface and the secondary IP address of 10.10.10.1 /24.

** Beware that leaving this secondary IP address on all switches can cause IP conflicts.

See Re: I have 3 adtran netvanta 1550 wsitches.  for an example.

0 Kudos
Reply
Highlighted
Honored Contributor
Honored Contributor

Re: Having issue with configuring vlan 1 on 1550-24 after upgrading to R13-5-2

By default it has a secondary IP of 10.10.10.1/24 configured, with primary DHCP. If you have console access you can just delete the secondary and reassign the primary. If you're accessing over the network, temporarily assign a primary IP address in a different subnet, then delete the secondary, then re-assign the primary.

interface vlan 1

  ip address 10.10.11.1 255.255.255.0

  no ip address  10.10.10.1  255.255.255.0  secondary

You will lose connectivity. Then re-connect to 10.10.11.1 - you'll need to change the IP of your computer temporarily to something like 10.10.11.2 .

Then:

interface vlan 1

  ip address 10.10.10.1 255.255.255.0

Then move your computer back to 10.10.10.x and reconnect again, then write memory.

0 Kudos
Reply