commands for cli not working...

[#1]

I' m new to fortios, but reading the installation via CLI i' ve tried to change the ip address on an interface and when I type set ip <ip address>/<subnet> (and yes i' m using an actual ip and subnet not the <ip address etc...) I get the error message: command parse error before ' (with the ip address i typed in) Command fail. Return code -61 now all the instructions i have seen show this to be the command and well it simply isn' t working. Appreciate any info or help, thank you

[rwpatterson]

Welcome to the forums. Are you typing in the preceding commands as well?

 # config system interface
 # edit <interface name>
 # set ip x.x.x.x y.y.y.y
 # end

Hope this helps

[#3]

yes i' m typing exactly as follows Fortigate # config system interface Fortigate # edit internal Fortigate # set ip <ip address> <subnet mask> and when i use # set ? it does not give me an option for ip except for ipmac here is my system status not sure if that helps Version: Fortigate-60B 3.00,build5115,071026 Virus-DB: 6.671(2006-09-21 08:17) IPS-DB: 2.391(2007-05-24 11:23) Serial-Number: FGT60B3908633686 BIOS version: 04000006 Log hard disk: Not available Hostname: QuaidTemFirewall Operation Mode: Transparent Current virtual domain: root Max number of virtual domains: 10 Virtual domains status: 0 in NAT mode, 1 in TP mode Virtual domain configuration: disable Common Criteria mode: disable Current HA mode: a-a, master Distribution: International Branch point: 568 MR/Patch Information: MR5 Patch 3 System time: Thu Oct 9 22:02:23 2008

[rwpatterson]

In transparent mode, all interfaces have a common IP (I believe). Someone here can give you more info on that. Mine are all in NAT/Route mode.

[#5]

ah ok Thank you for your help! If that is the case then i' ve just got to try and figure out why i can telnet to the device but i cannot http or https to it even though both are accessallowed for that interface. Any suggestions?

[laf]

When running Transparent mode, you can reach the equipment from any port by its management IP. But, what can you access when connected: telnet, ping, http....depends on the port you re connected. I suggest you to connect to internal as usually has most the access methods enabled.

[FortiRack_Eric]

I allways recommend to leave the root vdom in NAT/Route mode and create a seperate transparant vdom with the interfaces needed. With a FG60B you have 9 interfaces (w/o vlans) if you set the internal switch in interface mode. In this scenario you have all the functionality available for both functions, you can access the FG in the root vdom (which should be the management vdom). Regards, Eric