CatTools version 3.4.0 - Forinet version 4.0 MR1

WendyD

I am unable to backup a Fortigate 200A running version 4.0 MR1.  Backing up the config worked until we upgraded to 4.0 MR1.  We were at version 3.0 MR6.  We were on CatTools 3.3.4 and upgraded to 3.4.0 thinking that would resolve the issue.  Ran the activity in capture mode.  Here is the output:

<NEWSESSION Kiwi CatTools 3.4.0 9/14/2009 3:19:39 PM>
<PROTOCOL=SSH2>
<DEVICE TYPE=Fortinet.FortiOS.General>
<ACTIVITY TYPE=Device.Backup.Running Config>
<ACTIVITY SCRIPT=C:\Program Files\CatTools2\Scripts\Client.Device.Backup.Running Config.txt>
<USERS NAME FOR DEVICE=REABAH-FW-FortiNet>
<C OK 3:19:40 PM><R-3:19:40 PM>NT-Forti $ <W-3:19:45 PM>[13]<R-3:19:45 PM>[13][13][10]NT-Forti $ <W-3:19:45 PM>[13]<R-3:19:45 PM>[13][13][10]NT-Forti $ <W-3:19:45 PM>config system console<R-3:19:45 PM>config system console<W-3:19:45 PM>[13]<R-3:19:45 PM>[13][13][10]4567: Unknown action 3[13][10]C<R-3:19:45 PM>ommand fail. Return code -1[13][10][13][10]NT-Forti $ <W-3:19:45 PM>config global<R-3:19:45 PM>config <R-3:19:45 PM>global<W-3:19:45 PM>[13]<R-3:19:45 PM>[13][13][10][13][10]NT-Forti (global) $
================================================================================
WFMDRetVal=1 Waiting for: "(console)#"
WFMDRetVal=2 Waiting for: "(console) #"
WFMDRetVal=3 Waiting for: "(console)$"
WFMDRetVal=4 Waiting for: "(console) $"
WFMDRetVal=5 Waiting for: "global #"
WFMDRetVal=6 Waiting for: "(global) #"
WFMDRetVal=7 Waiting for: "NT-Forti#"
WFMDRetVal=8 Waiting for: "NT-Forti $"
WFMDBuffer="config global[13][13][10][13][10]nt-forti (global) $ "
================================================================================
<W-3:20:15 PM>set output standard<R-3:20:15 PM>set output standard<W-3:20:15 PM>[13]<R-3:20:15 PM>[13][13][10]Unknown action 0[13][10][13][10]NT-Forti (global) $ <W-3:20:16 PM>end<R-3:20:16 PM>end<W-3:20:16 PM>[13]<R-3:20:16 PM>[13][13][10][13][10]NT-Forti $ <W-3:20:16 PM>show<R-3:20:16 PM>show<W-3:20:16 PM>[13]<R-3:20:16 PM>[13][13][10]4567: Unknown action 0[13][10]Command fail. Return code -1[13][10][13][10]NT-Forti $
================================================================================
WFMDRetVal=1 Waiting for: "[13][10]#config"
WFMDBuffer="[13][13][10]4567: unknown action 0[13][10]command fail. return code -1[13][10][13][10]nt-forti $ "
================================================================================
<D 3:22:46 PM>
<SCRIPT VALUES>
<HOSTNAME="NT-Forti">
<PROMPT VTY="NT-Forti ">
<PROMPT ENABLE="NT-Forti $">
<PROMPT CONFIG="">

Please help.

Wardini

Hi Wendy,

Well this is a bit of a puzzler. From the debug log when CatTools issues the 'config system console' command the device responds with 'unknown action'.

I did notice that in the CatTools debug log the prompt is a '$' e.g. NT-Forti (global) $ but in your PuTTY capture the prompt is a '#' e.g. NT-Forti(global)#.

Is it possible that when you log in manually you are doing so at a higher priviledge level than CatTools is set to login at and so the 'config system console' command is accepted under these circumstances but not when it is sent from CatTools?

Kind regards,

Wardini