ISE endpoint export - Template

[mustafa83]

Hi,
we have a project to migrate from ISE 2.2 deployment to separate 2.6 deployment, we are doing it on Site by Site basis, we are exporting statically assigned endpoint for that specific site from 2.2 and trying to import that CSV file to 2.6 but it error out due to the template rows not matching between 2.2 and 2.6, 

We don't want to export the entire endpoints then have workaround implemented to import them one time, because new statically endpoint added to 2.2 deployment daily while we in the middle of the migration project, we would like to export static endpoints on the day of migrating of that specific site.

Thanks,
Mustafa

[mustafa83]

So, we came up with below cheat sheet, we copy a row from 2.2 template and paste it in 2.6 template(row by row) then save that CSV file and finally import to 2.6, is there any better/easier way that Cisco would recommend? 

2.2---> 2.6
A  ---> A
B  ---> B
J  ---> J
L  ---> Q
N  ---> P
Q  ---> R
AD---> AE
AR---> I
AS---> H
AT---> S

[hslai]

Only three fields/columns (see below) are required in the CSV file(s) so we may chop off the rest unless you have a reason to import the others.

The required fields are:

MAC,Endpoint Policy, Endpoint Identity Group

If not statically assigning Endpoint Policy, we may leave it blank.

[mustafa83]

Thanks Hslai, will the BU figure this out so 2.6 accepts 2.2 template? 

[hslai]

The import/export templates for context visibility, internal users, guest users, network device groups, and network devices, may vary by ISE releases. They might not be backward compatible.

The three fields are required as far back as in ISE 1.0, and we usually need only these to update the static assignments.

[mustafa83 · Accepted solution]

Thank you Hslai, we place static assignment in different containers based on their function or geolocation in the old deployment and created those containers in the new deployment and want statically assigned endpoints to be in the same containers in the new deployment along with other fields such as description which includes some internal info, customer should not be slapped for buying more hardware and building separate deployment to migrate from the old deployment, just my thought, our Cisco SE working with the BU on this.