Fortinet Product Inconsitencies

[nbctcp]

SUGGESTIONS
I want to propose next fortinet product to have same command on every fortinet product

Example

1. to check gateway
FortiAnalyzer, FortiManager, FortManager, FortiNAC

#show system route

but FortiADC, FortiGate, FortiSwitch, FortiWeb

#show router static

2. show full-configuration
available in FortiADC, FortiGate, FortiMail, FortiNAC, FortiSwitch, FortiWeb

but unavailable in FortiAnalyzer, FortiManager

3.  change console from standard to more

available in FortiADC, FortiGate, FortiManager, FortiSwitch, FortiWeb

but unavailable in FortiMail, FortiNAC

4. show full | grep port1

available in FortiADC, FortiGate,, FortiMail, FortiWeb

unavailable in Fortianalyzer, FortiManager, FortiNAC

5. rename default admin
available in Fortigate, Fortimail (only non default admin)

unavailable in FortiAnalyzer, FortiADC, FortiNAC, FortiManager, FortiWeb

Complete cli differences in

Fortinet.xls

https://we.tl/t-W2HcupuMIq

[mgoswami]

Hi,

Thank you so much for the suggestions. Incase you would like these features to be added to the specific devices, you may request as a new feature (NFR).

Please be informed that a New Feature Request needs to be worked with the Systems Engineer (SE) that covers your territory.

http://www.fortinet.com/aboutus/locations.html

Alternatively, it can be done through Regional Sales Partner Channel

http://www.fortinet.com/partners/reseller_locator/locator.html

BR,

Manosh

[ede_pfau]

Nice that someone pointed out that there is more work ahead than just the Fabric integration.

If you allow, I would even add that there is a need for a decent shell as such. The current CLI is not closely resembling a shell, as it lacks

- looping

- variables

- conditionals

- procedures/subs/functions

- pattern matching/REs

- pipes

just to name a few. Imagine you could work on the configuration in a full shell: create 100 address objects, find all references, ... whatever.

Of course, these are security products, and security needs to be taken into account. So, no direct file system commands, 'sudo' whereever necessary,... But, in times when you could be using the API, isn't this already a moot point?

Just my thoughts on this topic.