Hi Matt,
Here are some comments. If anyone else has more info or corrections, please pipe in
üôÇ
1. A global variable will demote the virtual server from running on more than one CPU core. I think on a Viprion this will be the first CPU on the first blade. You can check this using an iRule:
http://devcentral.f5.com/wiki/default.aspx/iRules/TMM__cmp_group.html
when RULE_INIT {
Set a global variable to demote the virtual server
set ::my_global_var "test"
Log which slot/CPU we're running on
set tmm_unit_cmd TMM::cmp_unit
set tmm_group_cmd TMM::cmp_group
log local0. "CPU ID: [eval $tmm_unit_cmd], slot: [eval $tmm_group_cmd]"
}
2. CMP is potentially enabled whenever the platform has more than CPU core available and the config is CMP compatible.
3. No, I don't believe the mechanism for distributing virtual servers is configurable and they are pinned to the first TMM instance available.
4. CMP only comes into play within the same unit. There isn't any sharing of work across platforms for CMP.
Aaron