Cirrus Download Job for FWSM System Contex

Has anyone been able to create a "Download" job for the System Context in an FWSM. As you might be aware, you need to login to it via an "admin" context which complicates the process.

I can create a simple "Command Script" type job such as this

changeto system

copy /noconfirm startup-config t172.0.0.53/SystemContext\startup-config.cfg

copy /noconfirm running-config t172.0.0.53/SystemContext\running-config.cfg

wr mem

exit

but this forces me to download the configuration to a subdirectory under the TFTP-Root directory and does not give me access to the archiving and "dated" version management that is built in to "Download" jobs.

I have also tried to modify a device template and use a "Download" job with that but it hangs when the prompt changes when I switch from the Admin context to the System context (is there some way to reset the "mprompt" during job execution)?

I am a realative novice with the Cirrus product so any advice would be helpful even if you think it is obvious.

Find more posts tagged with

multiple_config_types_per_device

Accepted answers

All comments

chris.lapoint

Can you upload the template you created to try to make this work? Also, if you can post the session trace of a download using your template? You can enable by going to File > Settings > Advanced > Session Tracing.

kgardiner

Chris,

Thanks for your response. I have posted the modified template and attached the session trace.

<Configuration-Management Device="Cisco PIX" SystemOID=" 1.3.6.1.4.1.9.1.451">
<Commands>
  <Command Name="RESET" Value="no pager"/>
  <Command Name="Reboot" Value="reload noconfirm"/>
  <Command Name="EnterConfigMode" Value="config terminal"/>
  <Command Name="ExitConfigMode" Value="quit"/>
  <Command Name="Startup" Value="startup"/>
  <Command Name="Running" Value="running"/>
  <Command Name="DownloadConfig" Value="changeto system${CRLF}Show ${ConfigType}"/>
  <Command Name="UploadConfig"

Value="${EnterConfigMode}${CRLF}${ConfigText}${CRLF}${ExitConfigMode}"/>
<Command Name="DownloadConfigIndirect" Value="write net

${StorageAddress}:/${StorageFilename}"/>
  <Command Name="UploadConfigIndirect"/>
  <Command Name="EraseConfig" Value="write erase${CRLF}Yes"/>
  <Command Name="SaveConfig" Value="write memory"/>
  <Command Name="Version" Value="show version"/>
</Commands>
</Configuration-Management>

SystemContextSession.txt

jedi755

Did you get this working? I am having trouble with your template.

chris.lapoint

Can you try this template instead? Notice I'm overriding the enable command to get around the issue mentioned where the prompt changes unexpectedly and Cirrus' state machine continues to wait for the old prompt. When Cirrus sends the enable command, it always watches for a change to the previous prompt (called mprompt in session trace) and stores it so that it knows it is in enable mode. You'll need to go to the device details and change Enable Level to "enable". Cirrus will use the EnableCommand value specified in the device command template when logging onto the device.

<Configuration-Management Device="Cisco PIX" SystemOID=" 1.3.6.1.4.1.9.1.451">
<Commands>
<Command Name="RESET" Value="no pager"/>
<Command Name="Reboot" Value="reload noconfirm"/>

<Command Name="EnableCommand" Value="changeto system"/>

  <Command Name="EnterConfigMode" Value="config terminal"/>
  <Command Name="ExitConfigMode" Value="quit"/>
  <Command Name="Startup" Value="startup"/>
  <Command Name="Running" Value="running"/>
  <Command Name="DownloadConfig" Value="${CRLF}Show ${ConfigType}"/>
  <Command Name="UploadConfig"

Value="${EnterConfigMode}${CRLF}${ConfigText}${CRLF}${ExitConfigMode}"/>
<Command Name="DownloadConfigIndirect" Value="write net