Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Multiple Network Device Groups when importing to ISE using template

I have a question about importing a group of network devices into ISE using the template provided. The template only has a single column for Network Device Groups - is there a way to import devices and include more than one NDG? For instance, the NDG's we use are "Device Type" and "Location". I'd like to include both when doing my import and I've tried multiple ways to seperate the two strings within the column (comma's colons, semi-colons, spaces, pipes, tabs, etc), but i always get an error message that "NDG group does not exist". I also tried adding a new column into the template, but that just plain failed to import.

If there is any way to do this, I would appreciate any advice on how - I have to add about 40 devices per week to our ISE deployment and I'd rather not have to go in and add any parameters manually if it can be helped. Thanks very much!

Ross

BTW, we are running ISE ver 1.1.2 in case it is relevant.             

2 REPLIES

Multiple Network Device Groups when importing to ISE using templ

Yes, you can do it. You have to use the pipe "|" to separate the groups. But please notice you must create the network device groups in advance.

For example, I have the following groups in my csv file to import a lot of network devices

Device Type#All Device Types#SWITCHES#375O-X|Location#All Locations#PERU#LIMA


But as a pre-requisite I have to create the network device groups.

If you have lots of network device groups, you can mass import them instead of creating them one by one.

Please rate if it helps

New Member

Multiple Network Device Groups when importing to ISE using templ

That works! My problem was that I was putting a space just after the pipe. So obvious in retrospect. Thanks very much for your help!

Ross

165
Views
10
Helpful
2
Replies