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

Variables on Config templates?

Any chances for including variables in templates? Say.. i have a generic configuration for all of my nodes. Only certain commands such as the ip address, hostname, gateway etc needs to be different.

For example: hostname $hostname$ //where anything bewteen $$ is treated as a variable.

If this feature is not available, how about considering it to be a future request?

Heres some of my suggestions: for a single node, I can apply the template to it, and then i will input the values for the variables in a separate form (eg another page to fill in the variables value). For mulitple nodes, i can apply the template to all, and import a .csv documents with the appropriate variables values.

This will definately help to safe alot of time in deployment of new devices! I welcome feedback to help make this better for the Solarwind guys!

scott

Find more posts tagged with

template

Configuration

variable

Accepted answers

Scott, Any SNMP-learned variable can be used by Cirrus in a configuration template, and you can define your own custom properties just like Orion.

File, Settings, Custom Properties will list (or allow you to add) any additional fields you want to have available to you with NCM.

Once you initially do an SNMP discovery on the node within NCM, (verify SNMP credentials works too if you have Node Monitoring disabled) many variables will be expanded.

Check the Help documents - Help, Network configuration manager administrator guide, working with command scripts, using variables within scripts. There is also a "command template commands" variable expansion that you can see here.

Below, SysName, MachineType, and SysContact are learned from SNMP. The rest I have described myself.

banner exec %
----------------------------------------------------------------------
Hostname:      ${SysName}
Model:         ${MachineType}
Location:      ${StreetAddress}, ${City}, ${Province}, ${Country}, ${PostalCode}
Location:      ${CLLI} - ${City}, ${Building},
Location:      Floor: ${Floor} Room: ${Room}, Rack: ${Rack} Unit: ${Unit}
Description:   ${LogicalDescription}
TBS ID:        ${TBS_ID}
Contact:       ${SysContact}
System Serial: ${SerialNumber}
----------------------------------------------------------------------
%
banner login %
______________________

All comments

orionofmyeye

i agree.

Scott,

${SysName} may be what you're looking for. I'm looking at your post, and I make heavy use of 'config snippets' for my IOS standardization. Particularly, banners;

banner exec %

-------------------------------

Hostname: ${SysName}
MachineType ${MachineType}
Address: ${StreetAddress}, ${City}, ${Province} - ${PostalCode}

I'm not exactly sure what else you're looking for - Forgive me if this isn't like what you're looking for.

I just drag and drop my templates onto my routers after I initially configure basic AAA and management for my devices, and just have NCM drop over my AAA, Telnet VTYs, security, banners, DNS, and other such options on the device.

As long as those variables are defined (Some of them may be custom properties) you can use them in a configuration template or configuration snippet.

scottkwei

Thanks JP. Your respond sure sounds interesteding! I'm going to give it a try. A qn here, where can I input my variable for, say ${SysName}? Is there any form in CIRRUS which i missed?

thanks once again!

scott

Scott, Any SNMP-learned variable can be used by Cirrus in a configuration template, and you can define your own custom properties just like Orion.

File, Settings, Custom Properties will list (or allow you to add) any additional fields you want to have available to you with NCM.

Once you initially do an SNMP discovery on the node within NCM, (verify SNMP credentials works too if you have Node Monitoring disabled) many variables will be expanded.

Below, SysName, MachineType, and SysContact are learned from SNMP. The rest I have described myself.