09-26-2017 01:29 PM
Hi Team,
My customer tried to upgrade from 2.0 to 2.2 recently and was hit by CSCvd07886: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvd07886/?reffering_site=dumpcr
He came back to me with this.
At this time, and assuming that Cisco’s TAC recommendation to rebuild all VM’s is correct, we would like to know understand what the best approach is to get our deployment to version 2.3:
Do you have any recommendations on what approach is best?
Do you have any guidance here? I would say 1 is easier with the export, but I know policy will be exported but can’t confirm that registered devices will?
Thanks,
Pete
Solved! Go to Solution.
09-26-2017 03:07 PM
CSCvd07886 has a workaround suggested in the release notes enclosure and another workaround done by TAC so running into this bug itself needs no rebuilding of the deployment. Something else, perhaps?
Customers may do either approaches. If resources permit, it's usually better to go for the first one.
Regarding the endpoint export/import, ISE is currently supporting all attributes in the context visibility page but only certain attributes can be imported. If the customers are good in not keeping all attributes, then import will work. Otherwise, backup the configurations from the original deployment and restore them to the new deployment.
Below is a sample CSV file used to import endpoints:
MACAddress,EndPointPolicy,IdentityGroup,Description,DeviceRegistrationStatus,BYODRegistration,PortalUser,StaticGroupAssignment
01:02:03:04:01:05,,RegisteredDevices,test5,Registered,Yes,tt01,TRUE
01:02:03:04:01:06,,RegisteredDevices,test6,Registered,Yes,tt01,TRUE
01:02:03:04:01:07,,RegisteredDevices,test7,Registered,Yes,tt01,TRUE
01:02:03:04:01:08,,RegisteredDevices,test8,Registered,Yes,tt01,TRUE
09-26-2017 03:07 PM
CSCvd07886 has a workaround suggested in the release notes enclosure and another workaround done by TAC so running into this bug itself needs no rebuilding of the deployment. Something else, perhaps?
Customers may do either approaches. If resources permit, it's usually better to go for the first one.
Regarding the endpoint export/import, ISE is currently supporting all attributes in the context visibility page but only certain attributes can be imported. If the customers are good in not keeping all attributes, then import will work. Otherwise, backup the configurations from the original deployment and restore them to the new deployment.
Below is a sample CSV file used to import endpoints:
MACAddress,EndPointPolicy,IdentityGroup,Description,DeviceRegistrationStatus,BYODRegistration,PortalUser,StaticGroupAssignment
01:02:03:04:01:05,,RegisteredDevices,test5,Registered,Yes,tt01,TRUE
01:02:03:04:01:06,,RegisteredDevices,test6,Registered,Yes,tt01,TRUE
01:02:03:04:01:07,,RegisteredDevices,test7,Registered,Yes,tt01,TRUE
01:02:03:04:01:08,,RegisteredDevices,test8,Registered,Yes,tt01,TRUE
09-28-2017 06:27 AM
Thanks for the very quick reply Hsing-Tsu.
I will forward that onto him.
Regards,
Pete
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide