Netonix Forums

Firmware ver. 1.3.7 (Yes, I want to upgrade but can't as switch is in production, and I need to schedule downtime)

But I need to change IP-address NOW! Unfortunately it's completely impossible....

What to do ????


Feb 20 09:19:52 admin: Reverting to last known good configuration
Feb 20 09:19:54 admin: removing lan (eth0.10) from firewall zone lan
Feb 20 09:19:57 admin: adding lan (eth0.10) to firewall zone lan
Feb 20 09:19:58 system: starting ntpclient
Feb 20 09:21:22 UI: Configuration changed by 192.168.1.100
Feb 20 09:21:22 UI: IPv4_Address: changed from '192.168.1.18' to '10.0.0.53'
Feb 20 09:21:22 UI: IPv4_Netmask: changed from '255.255.255.0' to '255.255.252.0'
Feb 20 09:21:22 UI: IPv4_Gateway: changed from '192.168.1.1' to '10.0.0.1'
Feb 20 09:21:22 UI: Discovery_Ubiquiti: changed from 'Disabled' to 'Enabled'
Feb 20 09:21:22 UI: Discovery_Cisco: changed from 'Disabled' to 'Enabled'
Feb 20 09:21:24 admin: removing lan (eth0.10) from firewall zone lan
Feb 20 09:21:28 admin: adding lan (eth0.10) to firewall zone lan
Feb 20 09:21:29 system: starting ntpclient
Feb 20 09:21:33 switch[1994]: Detected cold boot
Feb 20 09:22:32 admin: Reverting to last known good configuration
Feb 20 09:22:33 admin: removing lan (eth0.10) from firewall zone lan
Feb 20 09:22:36 admin: adding lan (eth0.10) to firewall zone lan
Feb 20 09:22:37 system: starting ntpclient
Feb 20 09:22:41 switch[2474]: Detected cold boot
Feb 20 09:43:26 UI: Configuration changed by 192.168.1.100
Feb 20 09:43:26 UI: IPv4_Address: changed from '192.168.1.18' to '10.0.0.53'
Feb 20 09:43:26 UI: IPv4_Netmask: changed from '255.255.255.0' to '255.255.252.0'
Feb 20 09:43:26 UI: IPv4_Gateway: changed from '192.168.1.1' to '10.0.0.1'
Feb 20 09:43:29 admin: removing lan (eth0.10) from firewall zone lan
Feb 20 09:43:32 admin: adding lan (eth0.10) to firewall zone lan
Feb 20 09:43:33 system: starting ntpclient
Feb 20 09:44:33 admin: Reverting to last known good configuration
Feb 20 09:44:35 admin: removing lan (eth0.10) from firewall zone lan
Feb 20 09:44:38 admin: adding lan (eth0.10) to firewall zone lan
Feb 20 09:44:38 system: starting ntpclient

SSH into switch. Change configuration.

Why do it has to be so difficult ? Why is switch constantly reverting configuration ? Especially when there's nothing wrong with new config....

Revert becomes an issue when using DHCP address.
How revert works is if the browser you are at can not reach the switch within the allotted time it reverts to last known config.

Normally if you change the switch IP the web UI knows where the switch will be and is able to find it again but if using DHCP the changing browser has no idea where it it is and can not reach it in the allotted time.

I need to talk to Eric about this but maybe the solution is to disable the Revert timer if DHCP is used.

If using DHCP maybe disable the revert timer under the Device/Configuration Tab by setting value to 0.

Or maybe he can have to switch remember the IP of the computer making the change and have the switch poke the UI/CLI after it changes address and that way it does not matter that the workstation is not sure where it is going to be?

Actually am I not choosing DHCP. I'm trying to set static IP-address....

sirhc wrote:Or maybe he can have to switch remember the IP of the computer making the change and have the switch poke the UI/CLI after it changes address and that way it does not matter that the workstation is not sure where it is going to be?

Clever idea but if one is changing their IP addressing scheme, they might also be changing the IP on the PC. You might need to get jiggy with ARP.

If the switch was smart enough to realize that an IP address change is likely to pull the rug out from under itself, perhaps it could just give a warning and option to commit without auto-revert?

lligetfa wrote:

sirhc wrote:Or maybe he can have to switch remember the IP of the computer making the change and have the switch poke the UI/CLI after it changes address and that way it does not matter that the workstation is not sure where it is going to be?

Clever idea but if one is changing their IP addressing scheme, they might also be changing the IP on the PC. You might need to get jiggy with ARP.

If the switch was smart enough to realize that an IP address change is likely to pull the rug out from under itself, perhaps it could just give a warning and option to commit without auto-revert?

LOL - Below was a post I made in Skype to Eric a little bit ago! - WE THINK ALIKE LES

Maybe we should pop up a window reminding the user that the switch will revert if it can not be reached and on that window they have the option to disable the revert for that change?

Tried changing the ip a dozen times using different tricks and it always reverts.

What is supposed to be the tried and true way?

Is there a manual I can refer to?

hgregorybadger wrote:Is there a manual I can refer to?

Everything you need here here

There is a search box in the upper right corner

I did a search on Revert and this is the 3rd post
viewtopic.php?f=17&t=1967&p=14554&hilit=revert#p14554

In this post above there are 3 other links for detailed explainations