Adding new rSeries Tenant to existing Device Group

jomedusa​ 

What I would likely do:

1. Restore the rSeries to the factory configuration.
2. Manually add the VLAN to the correct partitions.
3. Then import all the other configuration. 

Refreshing BIG-IP hardware is challenging. Every BIG-IP install is unique. 

I never have been able to directly import the configuration from an older BIG-IP hardware platform on to a new BIG-IP hardware platform.  There are always issues with the configuration conversion. 

Why do you need the VLAN configuration objects to be in child partitions / folders?

My experience is that it's easier to support having all the VLAN in Common.  It's my general recommendation is to put all the VLAN in Common.

A child partition of the parent Common partition should be able to use a VLAN object from Common.  

I view partitions / folders as a multi tenancy feature.  When the BIG-IP device is being used in a single customer environment. Partitions can add unneeded complexity to the configuration. Some of the BIG-IP modules do not fully support partitions. 

A good use for partitions is limiting remote user access to the BIG-IP. Pulting the VLAN in Common should not affect user access to the other configuration objects in a partition.

Are you using a route domain for each partition to isolate traffic? In my mind this would be a justifiable reason to place the VLAN in the partition. 

Matt