Currently RA always tries to reuse the already assigned numbers for a range resource, whenever there is an allocation request for the same resource entity, but a different entity version (change order). For example, let's say we have an active connection with entity ID con1 and version 1, and we have allocated VLAN ID of 201. Now, if there is a change order for this connection the allocation request should have entity ID con1 and version 2. For such requests RA will always first try to retain the same resources, so it will allocate the same VLAN ID of 201 for version 2 of the connection.

However, turns out there are cases, where when we do change order, we want to force a new network interface to be created on the device, which means we need to assign a new VLAN ID.

In order to accommodate such cases, we need a new (optional) flag in the parameters that will tell RA to assign new number(s) for a range resource. The new parameter is:

range-force-new-numbers

Default value is false.