This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

When will CatTools support modifying Juniper EX switch configs?

The subject pretty much says it all.  I was hoping to already be able to use CatTools to send simple one-line command strings to my Juniper EX switches but it seems determined to think of them as Cisco devices with the commands I see it trying to send - even though I've told it these are Juniper devices, and chosen Juniper Routers as the device type.  I know these are switches and not routers, but the CLI is essentially the same for both types of devices.  Is there anyone out there who's already been down this road and reached a successful destination?  If so, I would SO love to hear from you about it!! emoticons_wink.png

Thanks in advance emoticons_happy.png

-John

  • John,

    I am interested to help you.

    So what are you trying to do with CatTools. Which activity are you trying to run? How do you set up the device details?

    And if possible can you please send me the debug log of the device for which the issue is appearing?

    (Debug log can be found under Debug folder; this can be enabled by enable the capture mode under file menu; then activity needs to be run)

    Thanks,

    Nanda

  • Nanda thank you for the reply emoticons_happy.png

    I will get you debug output tomorrow, when I'm at the office.  What I'm attempting to do is use CatTools to make some minor changes to the configuration of our Juniper switches.  Examples of these changes would be to go into each switch and delete a line that directs snmp trap messages to a destination host that no longer exists.  The entire procedure to accomplish that consists of just a few simple lines of text after successfully logging in.  For example:

    > edit

    # delete system snmp trap-group deadhost1 10.1.1.1

    # delete system snmp trap-group deadhost1

    # commit and-quit

    > exit

    The session log data for that is showing the same kinds of problems with 'unknown command', etc. that the original poster talked about.  And I had already gone through all the tricks I could find in the CatTools device and action setup options, for nulling out CanTools trying to speak Cisco IOS type things, like 'set term length 0', etc.

  • Okey John,

    Let me wait for your debug file.

    Nanda

  • I am having this same issue and I was wondering if anyone ever found a solution to it.  I am using CatTools 3.10 with Juniper EX switches that I am trying to get the CLI.Send command to work.  Everything seems to be ok, but I keep getting an error of "Did not receive expected prompt after command" and "Device type: Juniper.Router has not yet had this functionality added." It seems that the commands that I put in are not being ran even though it show successful in logging in.  I also made adjustment in the variations, which is below.  Anyone with some insight please help. 

    Torrence

    Variation Settings:

    DEVICE_USERNAMEPROMPT = "login:"

    DEVICE_PASSWORDPROMPT = "Password:"

    DEVICE_PRIVILEGEDPROMPT = ">"

    DEVICE_CONFIGPROMPT = "#"

    DEVICE_INVALIDCOMMAND = "unknown command."

    DEVICE_INCOMPLETECOMMAND = "syntax error."

    COMMAND_ENTERENABLEMODE = "enable"

    COMMAND_ENTERCONFIG = "edit"

    Cattools.JPG

    This is the Debug log:

    <NEWSESSION CatTools 3.10.0 1/9/2015 3:02:15 PM>

    <PROTOCOL=SSH2>

    <DEVICE TYPE=Juniper.Router>

    <ACTIVITY TYPE=Device.CLI.Modify Config>

    <ACTIVITY SCRIPT=C:\Program Files (x86)\CatTools3\Scripts\Client.Device.CLI.Modify Config.txt>

    <USERS NAME FOR DEVICE=Torrence Switch>

    <C OK 3:02:16 PM>

    <R-3:02:16 PM>This System is for authorized use only[10]

    <R-3:02:16 PM>--- JUNOS 12.3R6.6 built 2014-03-13 06:57:48 UTC[13][10]

    <R-3:02:16 PM>[13][27][3

    <R-3:02:16 PM>g[27][24;9H[27]

    <R-3:02:16 PM>H[27][24;17H[27]H[27][24;25H[27]H[27][24;33H[27]H[27][24;41H[27]H[27][24;49H[27]H[27][24;57H[27]H[27][24;

    <R-3:02:16 PM>65H[27]H[27][24;73H[27]H[13][13]

    <R-3:02:18 PM>root@Torrence-Switch:RE:0%

    <W-3:02:18 PM>[13]

    <R-3:02:18 PM>[13][13][10]root@Torrence-Switch:RE:0%

    <W-3:02:18 PM>set cli screen-length 0

    <W-3:02:18 PM>[13]

    <R-3:02:18 PM>set cli screen-le

    <R-3:02:18 PM>ngth 0[13][13][10]set: Syntax Error.[13][10]

    <R-3:02:18 PM>root@Torrence-Switch:RE:0%

    <W-3:02:18 PM>[13]

    <R-3:02:18 PM>[13][13][10]root@Torrence-Switch:RE:0%

    <W-3:02:18 PM>cli

    <R-3:02:18 PM>cli

    <W-3:02:18 PM>[13]

    <R-3:02:18 PM>[13][13][10]

    <R-3:02:19 PM>{master:0}[13][10]root@Torrence-Switch>

    <W-3:02:19 PM>[13]

    <R-3:02:19 PM>[13][10][13][10]{master:0}[13][10]root@Torrence-Switch>

    <W-3:02:19 PM>set cli screen-length 0

    <W-3:02:20 PM>[13]

    <R-3:02:20 PM>set c

    <R-3:02:20 PM>li scr

    <R-3:02:20 PM>een-leng

    <R-3:02:20 PM>th 0

    <R-3:02:20 PM>[13][10]Screen length set to 0[13][10][13][10]{master:0}[13][10]root@Torrence-Switch>

    ================================================================================

    WFMDRetVal=1 Waiting for: "root@Torrence-Switch:RE:0%"

    WFMDRetVal=2 Waiting for: "root@Torrence-Switch:RE:0>"

    WFMDBuffer="set cli screen-length 0 [13][10]screen length set to 0[13][10][13][10]{master:0}[13][10]root@torrence-switch> "

    ================================================================================

    <W-3:02:50 PM>[13]

    <R-3:02:50 PM>[13][10][13][10]{master:0}[13][10]root@Torrence-Switch>

    ================================================================================

    WFMDRetVal=1 Waiting for: "root@Torrence-Switch:RE:0%"

    WFMDRetVal=2 Waiting for: "root@Torrence-Switch:RE:0>"

    WFMDRetVal=3 Waiting for: "root@Torrence-Switch:RE:0#"

    WFMDRetVal=4 Waiting for: "(config)"

    WFMDBuffer="[13][10][13][10]{master:0}[13][10]root@torrence-switch> "

    ================================================================================

    <W-3:03:20 PM>[13]

    <R-3:03:20 PM>[13][10][13][10]{master:0}[13][10]root@Torrence-Switch>

    ================================================================================

    WFMDRetVal=1 Waiting for: "root@Torrence-Switch:RE:0%"

    WFMDRetVal=2 Waiting for: "root@Torrence-Switch:RE:0>"

    WFMDRetVal=3 Waiting for: "root@Torrence-Switch:RE:0#"

    WFMDRetVal=4 Waiting for: "(config)"

    WFMDBuffer="[13][10][13][10]{master:0}[13][10]root@torrence-switch> "

    ================================================================================

    <W-3:03:50 PM>exit[13]

    <D 3:03:50 PM>

    <SCRIPT VALUES>

    <HOSTNAME="root@Torrence-Switch:RE:0">

    <PROMPT VTY="root@Torrence-Switch:RE:0%">

    <PROMPT ENABLE="root@Torrence-Switch:RE:0>">

    <PROMPT CONFIG="root@Torrence-Switch:RE:0#">

  • Torrence,

    Juniper Router device type is not having the 'Device.CLI.Modify Config'. Instead you can use 'Device.CLI.SendCommands' activity.

    If you want to enter your commands on Config Mode, then just give the command to enter to config mode at first in the set of commands you are going to execute and at-last give the command to come out of the config mode.


    And regarding the variations,

    Set the prompt as below(Refer the image for better clarification)

    Full HOSTNAME=root@Torrence-Switch

    Full VTY PROMPT =root@Torrence-Switch>

    Full ENABLE PROMPT =root@Torrence-Switch#

    Full CONFIG PROMPT =root@Torrence-Switch(

    Thanks,

    Nanda