07-Apr-2021 09:37
We would like to replace a VIP profile from current "tcp" to "tcp-legacy" in TMSH. The VIP have many other profiles as well and we could like to keep those intact - we just need tcp to tcp-legacy. Is this possible?
Solved! Go to Solution.
13-Apr-2021 11:13
Here is what I ended up doing and it appears to have worked. The other profile remained intact and only it modified tcp to tcp-legacy
modify /ltm virtual test_vip { profiles delete { tcp } profiles add {tcp-legacy}}
12-Apr-2021 15:58
Since there are other profiles assigned, you can take a multi-step approach. List the virtual server first, note the existing profiles ("tcp" should be one of them), then do a replace-all-with specifying the full list, but with "tcp-legacy" instead of "tcp." For example:
(tmos)# list /ltm virtual http_vs
ltm virtual http_vs {
creation-time 2020-03-13:14:59:59
destination 10.10.4.100:http
ip-protocol tcp
last-modified-time 2021-04-12:14:54:50
mask 255.255.255.255
pool http_pool
profiles {
http { }
oneconnect { }
tcp { }
}
source 0.0.0.0/0
translate-address enabled
translate-port enabled
vs-index 2
}
(tmos)# modify /ltm virtual http_vs profiles replace-all-with { http oneconnect tcp-legacy }
(tmos)# list /ltm virtual http_vs
ltm virtual http_vs {
creation-time 2020-03-13:14:59:59
destination 10.10.4.100:http
ip-protocol tcp
last-modified-time 2021-04-12:14:54:50
mask 255.255.255.255
pool http_pool
profiles {
http { }
oneconnect { }
tcp-legacy { }
}
source 0.0.0.0/0
translate-address enabled
translate-port enabled
vs-index 2
}
13-Apr-2021 11:13
Here is what I ended up doing and it appears to have worked. The other profile remained intact and only it modified tcp to tcp-legacy
modify /ltm virtual test_vip { profiles delete { tcp } profiles add {tcp-legacy}}
13-Apr-2021 12:06
Nice! I was looking for something like that but could not quite get there. The example I provided works but yours is more elegant.