Forum Discussion
William_Them_99
Nimbostratus
Oct 13, 2005Data Group List Naming Anomaly
I created a few data group lists in order to be able to perform exact strings matches with the "matchclass" function. The three data groups were named with hyphens, such as:
verisign-issuer-strings
The GUI accepted everything and allowed me to save the data groups. The iRule editor also accepted these names in the "matchclass" statement (referenced via $::verisign-issuer-strings). However, when the BIGIP executed the iRule containing references to these data groups, I received errors in the log like this:
can't read "::verisign": no such variable
So it looks like it truncated the name of the data group right at the first hyphen, and thus could not find it. When I changed all the hyphens in the data group list names to underscores, all worked well.
Is this a bug? The underscore workaround is fine with me, but if the iRule code can't handle it, it might be a good addition to the GUI to not allow hyphens in the name.
Thanks.
- It's actually a TCL thing in variable substitution
$::{verisign-issuer-strings}
- William_Them_99
Nimbostratus
- Brian_Gupta_115
Nimbostratus
Have you seen any best practice guides for naming conventions for the various objects in BigIP? e.g. VIPs, classes, pools, rules, ssl certs, profiles, variables, etc?
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects