Forum Discussion
iamczar_12961
Jun 23, 2016Cirrus
A workaround is possible by changing the order of the objects in the saved config file before loading it.However, every time another config save is issued, the file is rewritten with the original order. So, after every save, or before every load, the order should be changed.
For example, after running "tmsh save sys config":
1. Edit the file /config/bigip.conf
2. Locate the DOS profile in use by the iRule, for example:
security dos profile /Common/dos1 {
...
}
3. Move this block of the DOS profile before the iRule.
That is, before the block of:
ltm rule /Common/dosrule {
...
}
Then running "tmsh load sys config" will succeed.
Manually editing the config and moving the iRule block after the DoS L7 profile block will allow the config to load. However, any configuration save will revert the order. Additionally, F5 does not recommend manually editing config files unless the need is urgent.
- Patrick_Albane_Jun 24, 2016NimbostratusThanks for the explanation. Is this a known behaviour? I fully understand that we should not meddle with the config file manually as human error is inevitable. I do wonder if F5 will release a fix so that iRule section will be written last all the time by the save command either via tmsh or from the configuration utility.