Forum Discussion

PeteW's avatar
PeteW
Icon for Nimbostratus rankNimbostratus
Jul 10, 2013

tmsh httpclass creation issues with paths

Chaps,

 

Just wondering if I'm hitting a bug with TMSH on LTM version BIG-IP 10.2.0 Build 1707.0 Final.

 

We have config that we're migrating from one environment to another and as its live we'll have to use TMSH to add the config rather than the tried and tested approach of amending the bigip.conf file and loading.I

 

 

Issue:

 

If I issue the following command it works:

 

create ltm profile httpclass test_httpclass pool test_pool paths replace-all-with { glob:/text1/test2 } redirect none

 

 

However if I issue the command with the actual path I receive a syntax error when i use the "*" wildcard after the /.

 

create ltm profile httpclass test_httpclass pool test_pool paths replace-all-with { glob:/text1/test2/* } redirect none

 

Error:

 

admin@spare(Active)(tmos) create ltm profile httpclass test_httpclass pool test_pool paths replace-all-with { glob:/text1/test2/* } redirect none

 

Syntax Error: ("glob:/text1/test2/\*") is missing prefix value. The prefix is either "regex:" or "glob:". It should be either regex:"glob:/text1/test2/\*" or glob:"glob:/text1/test2/\*".

 

admin@spare(Active)(tmos)

 

 

Any ideas why I can't utilise the path glob:/text1/test2/*

 

 

Does the TMSH on v10.2 not support the use of wildcards? If I use the suggested syntax it still baulks at it.

 

4 Replies

  • Okay, I had to spin up a 10.2 box to finally see what you were describing. 😉

    It appears it is a bug that was fixed in 11.0.

    You can get around this in 10.2.x by using the bigpipe command instead:

    
    b profile httpclass test_httpclass '{ defaults from httpclass paths regex "/text1/text3/*" pool test_pool redirect none }'
    

  • PeteW's avatar
    PeteW
    Icon for Nimbostratus rankNimbostratus

    Thanks Kevin, I suspected as much. I must admit I was expecting more from TMSH/TMOS but I guess its early code on the version we are currently using.

     

    Personally I think it's a little too "bugged", still more of an excuse to push the client for an upgrade.

     

     

    Thanks again Kevin much appreciated.

     

     

    Pete