- Community Home
- >
- Networking
- >
- IMC
- >
- adding variable in configuration template
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2016 07:43 AM
09-06-2016 07:43 AM
adding variable in configuration template
Hi,
i noticed you can use a variable in the configuration template. But this variable is fixed for all switches you apply the template on.
If for example you want to add a description on a certain port on 20 switches, which contains the name of each individual switch, then it does not seem to be possible?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2016 05:28 PM
09-08-2016 05:28 PM
Re: adding variable in configuration template
There are some ways of using SNMP variables, which might let you do things like using sysName.
But what's the point in putting the switch name in the interface description? Seems a waste of useful real estate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2016 04:26 AM
09-09-2016 04:26 AM
Re: adding variable in configuration template
Hi,
You can try the following:
1. In the script (ProCurve example)
interface 1
name ${SystemName}_YourSpecifcInterfaceDescription
exit
PS: adapt to your appropriate switch syntax.
2. in the workflow:
In the "Enter SystemName" field: $(RFC1213-MIB|sysName|0)
then your SystemName will be added in your interface description.
Cheers
Ray
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2016 06:35 AM
09-14-2016 06:35 AM
Re: adding variable in configuration template
I think Rpapaux probably provided the answer I think your after, but wanted to be sure. The first time I read through the post I took it a different way.
i noticed you can use a variable in the configuration template. But this variable is fixed for all switches you apply the template on.
If you place a variable like ${interface 1 desc} in the template, then it will always be "interface 20 desc" everytime you deploy the template, but you can obviously populate it with any value you want.
If you deploy the template to 20 switches it will give you the option to either use the same value for all switches in the deployment task, or to step through each switch so you can provide a different value. On top of that a more recent feature gives you the ability to export a parameter file for the deployment, then import it with the values (or you can just import as long as you follow the required format of the csv). Either way you can provide a different value for the variable on each of the 20 switches.
I'd try the system variable Rpapaux mentioned though. If the sysname is what you're after as the int desc. then that would be less effort than filling in the value for 20 switches.
PL