topic Re: Template Variables - vrouter destination in General Topics

Template Variables - vrouter destination

jasonrakers — Fri, 11 Mar 2022 19:37:13 GMT

I seem to not be able to use a template variable as a route destination in a vrouter. There is an option to create a variable in the destination field, but it becomes an invalid option after creating.

If you know how to make this work, please let me know.

Re: Template Variables - vrouter destination

PavelK — Sun, 13 Mar 2022 22:25:15 GMT

Thank you for the post @jasonrakers

After you create a variable, it should be selectable from the drop down menu. If you can't see it, would it be possible to navigate first to Template/Template Stack where you want to create a static route and create a variable from there? Please refer to Step No.3: https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/manage-firewalls/manage-templates-and-template-stacks/configure-template-or-template-stack-variables.html then come back to the Template/Template Stack and confirm you can see it from drop down in the static route's destination field?

Kind Regards

Pavel

Re: Template Variables - vrouter destination

jasonrakers — Sun, 13 Mar 2022 22:33:04 GMT

Thanks, I do see the variable under Manage in the Template, but it does not show up as as a selection for route destination. I opened a case with support it might be a bug with 9.1.12-h3.

Re: Template Variables - vrouter destination

PavelK — Sun, 13 Mar 2022 23:34:34 GMT

@jasonrakers thank you for quick reply. I see. I was not able to preproduce this issue with 9.1.12-h3, however I would appreciate feedback if you find a resolution through TAC.

Kind Regards

Pavel

Re: Template Variables - vrouter destination

jasonrakers — Fri, 18 Mar 2022 14:49:54 GMT

I have been able to get this to work for my immediate needs. However, the behavior to accept a variable entry in this field seems inconsistent. It doesn't appear to like it when you attempt to modify a variable with a different variable. My support case is still pending, but I uploaded a video of the problem where sometimes the variable is recognized as valid and other times it is recognized as invalid. My recommendation is if the variable is not being recognized, delete the route entry, create a new route entry with your pre-existing variable or a new variable. Best I can say is when it works, it works, but sometimes it does not work. As @PavelK mentioned, if you are using pre-existing variables, typing $ in the destination field should locate the variables, if no variables populate that is a bad sign indicating you will need to delete the route entry and create it again.