Avalanche: Why do I see #COREDIVIDE in my Action List?

Avalanche: Why do I see #COREDIVIDE in my Action List?

The #COREDIVIDE keyword is limited to specific test configurations and is not recommended for general user configuration. Client subnet associations with Action Lists are assigned in a round-robin fashion onto the cores. If you do not want a client subnet to be divided in this manner, VIAVI recommends that you use #NODIVIDE in your Action List. (See the Avalanche or CyberFlood Help for usage information.) A client subnet associated with this Action List (#NODIVIDE) will not be divided across the cores, but rather, assigned in its entirety to a single core. In this way, you can control the distribution of clients across the cores. NOTES:  • If you remove the #COREDIVIDE keywords from a test exported from CyberFlood as a project file (.spf), test performance might be impacted when you run the test in Avalanche. • When you run an exported test from CyberFlood in Avalanche (Applies for any type of test and protocols used), you should use the same type of port groups (that is, the same number of cores). In general, it is recommended that you use the same device type as used in the original test. If this is not true, performance may impact or unexpected errors/results may occur. • Most common error seen on the Event.log when this happens is a SEGFAULT TRACE, as noted in the next KB Article: KNI16268