1 Reply Latest reply on Feb 7, 2011 5:01 PM by Steve Welsh

    Cattools and Fortigate 200A

    thomasliau

      Hi,

      My company has a Fortigate 200A firewall running firmware version 3.00 which I am configuring Cattools to backup the configuration.  However, I keep getting the error "Did not receive expected  prompt after sending end command".  I used the same username and password to perform on both the Cattools and telnet.  Please assists.

      I telnet into my firewall and did the following successfully.

       

      Fortigate-200A-MAST~$ config system console
       
      (console)$ set output standard
       
      (console)$ end
       
      Fortigate-200A-MAST~$ config system console
       
      (console)$ set output more
       
      (console)$ end
       
      Fortigate-200A-MAST~$

       

      Debug log shows:-

       

      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=8 Waiting for: "Fortigate-200A-MAST~$#"
      WFMDRetVal=9 Waiting for: "Fortigate-200A-MAST~$ $"
      WFMDRetVal=10 Waiting for: "Fortigate-200A-MAST~$ #"
      WFMDBuffer="end[13][00][13][10][13][10]fortigate-200a-mast~$ "

        • Re: Cattools and Fortigate 200A
          Steve Welsh

          Hi thomasliau,

          I believe the problem is most likely related to your device hostname.

          If I am presuming correctly that the $ on the end of Fortigate-200A-MAST~$ is the actual hostname mode prompt; then the issue is that normally there would have been a space between the hostname 'Fortigate-200A-MAST' and the '$'.

          Your device appears to contain a ~ which is most likely causing CatTools to determine the hostname as the full Fortigate-200A-MAST~$.    CatTools then tries to check for this hostname plus various mode prompts after the 'end' command has been issued.  This can be seen in the debuglog lines:

          WFMDRetVal=8 Waiting for: "Fortigate-200A-MAST~$#"
          WFMDRetVal=9 Waiting for: "Fortigate-200A-MAST~$ $"
          WFMDRetVal=10 Waiting for: "Fortigate-200A-MAST~$ #"

          If your device hostname prompt can be re-configured to use a space instead of the ~, then this should fix the issue.

          If it can't, then you will need to raise a ticket with SolarWinds tech support as this will need to be added as a Customer Feature Request (as the device type script will need modification)

          Kind regards,

           

          Steve