Lost IP address after switch to interface mode

[Mark_Woodward]

After upgrading a 200A to 4.00_b0639 (MR3 Patch 10), we needed to change into interface mode to support some additional internal segments. Steps were: - Backed the configuration up Used diagnose checkused system.interface.name internal to find out where the internal interface was referenced Removed any references to interface " internal" One more checkused... to ensure that all references are gone Using GUI, changed mode of " internal" to interface Box rebooted Seems as though it came back up but with what IP address? Checking from the LCD, interface list shows " Internal" , " WAN1" , etc but no Int1, Int2 etc and no address is set for " Internal" nor can we set one from the LCD panel ;-( Am I missing something here, I' ve done this before on another box and everything worked fine (couple of years ago though)? Any help would be appreciated... Mark

[ede_pfau]

hi, and welcome to the forums. As you can watch the LCD, why can' t you connect to the console port then? A simple ' conf sys interface' would put you into control again. Just wondering.

[Mark_Woodward]

Hi Ede, Thanks for the reply... At the time, I didn' t have my console cable with me....but I do now ;-) I' ll give it a try again and follow your suggestion and let you know. Thanks again for taking the time to help, All the best, Mark

[ede_pfau]

Chances are that it might have reverted to the default IP address. But don' t ask me what that was again...192.168.0.99 on ' internal' , and 192.168.1.99 on ' wan' from memory, but don' t take my word for it, sorry.

[Mark_Woodward]

Finally got round to sorting this out (change control and all that) with the console cable... Changing to interface mode removes any IP address from the internal ports so the only way in is to do what Ede suggests and attack it with a console cable ;-) All sorted now, Thanks chaps Mark

[FortiRack_Eric]

Is interface mode support on this particular 200A? Depending on serial no this might not be the case.

[Fermin]

Last time I had to do this I first configured one of the wan ports for admin access over https and ssh (after disconnecting it from the internet), and used that to get access to the box after reboot and then configured the internal ports.