Forum Discussion

CJI_252924's avatar
CJI_252924
Icon for Nimbostratus rankNimbostratus
Mar 04, 2016

tmsh command string tuncated !!!

Hi F5 folks,

We have a script to run tmsh command remotely to setup BIGIP pool members. Here is our command example to delete a pool member from the "SFO" pool, remotely. 

expect our_expect_script host_name user_name user_password  
      'modify ltm pool SFO members add { 10.123.123.111:8888 }
        save / sys config
        run cm config-sync to-group device-group-failover '

This command runs perfectly when we were using the 10.x F5 system. And just recently, ours is migrated to 11.x version and we start to see some failed ones.

Based on the log message we got, this command => 

 modify ltm pool SFO members add { 10.123.123.111:8888 },

when it reaches F5 system, sometimes it has been truncated as: 

modify ltm pool SFO members add { 10. ^H123.123.111:8888 }.

And it fails the operation.

So far we have noticed about 5 similar failures of total 1000+ running.

Does anyone have some clue why we have this extra 

 ^H
piece ?

Thanks,

Chun

BIG-IP
cloud
devops
TMSH

3 Replies

Sort By
  • Night_67217's avatar
    Night_67217
    Historic F5 Account
    Mar 07, 2016
    Hi Chun, Is the script executing automatically (like a cron job, for example) or is it done by human intervention? It seems that the "^H" appears when someone is pressing the "delete" key: http://answers.google.com/answers/threadview/id/386870.html
  • CJI_252924's avatar
    CJI_252924
    Icon for Nimbostratus rankNimbostratus
    Mar 07, 2016
    It is being executed automatically. But we do have a group of person and also our script trying to access the F5 with the same user account. I don't know if some other session sends such things and if it matters ?
  • Night_67217's avatar
    Night_67217
    Historic F5 Account
    Mar 08, 2016
    Hi Chun, Well, the easiest way to determine this would be to create another user especially for the script. That way you know that the script can only be executed in an automated fashion and there's no chance of another user sending similar commands at the same time, for example. You can also track in the audit log how the messages get logged and by whom.