eesun_276598
Cirrus
CirrusRelation between Traffic group and device group
Hi A traffic group is a collection of related configuration objects that run on a BIG-IP® device. Can we say a traffic group is running on a "traffic devices"? Thank you
Forum Discussion
Chris_GrantEmployee
You can say anything you like. Whether people will understand is another thing. Technically a traffic group is a collection of related traffic objects that reside in a sync-failover group on a BigIP Application Delivery Controller.
How much more or less you need to add to the explanation depends heavily on your audience. A group of F5 engineers wouldn't need any more than "Traffic group." A Cisco engineer who has never used a BigIP might benefit from something more complete like:
A Traffic group is a collection of related IP addresses that move between F5 BigIP Application Delivery Controllers in a high availability failover event.
eesun_276598Thank you for your reply. Sorry, I need to correct the post title to "Traffic group and device group". Traffic group and device group are some thing which we can see under Device Management in F5 main page. My question is to know the relation between traffic group and device group. Each traffic group has its own device group, and one device group could have several traffic groups, or one traffic group could go through several device groups, Can I say it like that?
- Chris_Grant
You may have multiple traffic groups in a single device group. You may not have multiple device groups on a traffic group. A device group is a collection of BigIPs that share configuration, and in the case of a sync failover group, that provide redundancy in the event of a failure on one BigIP. A traffic group is a collection of IP addresses that float between two or more BigIPs.
So you could have, for instance, two traffic groups running on two BigIPs in the same traffic group, provided that you didn't overload one in the event of a failover. You could not, however have one traffic group that was assigned to more than one device sync-failover group, as the system would not know where to send the traffic in the even of a failure.
This might help. It's for 11.2.0, but is broadly applicable: https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-redundant-systems-config-11-2-0/6.html