Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Access 'Command Template' variables in 'Conf Change Templates'

I'm attempting to write some Conf Change Templates to upgrade the firmware on a number of different types of Cisco hardware, so they can be run from the web interface instead of via scheduled command jobs via the windows application.

However from reading the documentation, I can't see a replacement for these variables which I've used in the other command scripts:

${StorageAddress}
${TransferProtocol}
${EnterConfigMode}
${ExitConfigMode}
${Reboot}
${RebootAt}

Does anyone know if this information can be access? Or do I have to hard code our TFTP / SCP server and manually specify the commands.

Find more posts tagged with

Accepted answers

All comments

cvachovecj

Hi jmiddleton,

first, sorry for the delay.

Second, I suggest using the scripting functionality:

Here you can use all the commands defined in the device template.

Please update us about your progress.

Regards,

Jiri

FormerMember

Thanks for the reply and the suggestion, however I'm liking the interface for the configuration change templates and it's ability to help reduce configuration errors. Keeping scripts outwith NCM and having to load them for each execution really does not assist in this goal.

Also I could very well end up allowing some users to run the change templates who I would prefer not have the ability to run arbitrary commands on a device. This is of course the permission model allows this, but I've not investigated yet.

If these variables are not available then I'll have to work round by hard coding them, also the lack of ${StorageAddress} will mean that my scripts will not interact well with the planned support for additional pollers in NCM.

cvachovecj

Hi,

I consulted with our dev team ant what they say is: You cannot use device template marcros CLI statements directly; however it should work like this:

string @Address= '${StorageAddress}'

CLI

{

copy @Address …

}

As result ${StorageAddress} will be embedded into script output and will be parsed at the moment of script execution.

In the future, ${StorageAddress} will be made poller-dependent.

Regards,

Jiri

cvachovecj

Very helpful thread is this one:

Regards,

Jiri

FormerMember

Thank you for the pointer, I'm planning on testing your suggestion today.

My script is quite similar but does not use the archive command as we don't deploy the web server files.So far I've also a configuration change template for upgrading an Cisco ASA failover pair and should be working on NX-OS upgrade template in the next couple of weeks.

cvachovecj

Would be good if you could post the results...

Jiri