11-09-2021 08:24 AM - edited 11-09-2021 08:26 AM
Hi Gents
i need to implement subject. & so far i've figured out imaging 1st new box with 2.2 then restore from 2.1 backup then backing up from 2.2 then reimaging with 2.7 then restoring from 2.2 backup.
does it look optimal or is there better path?
br andy
Solved! Go to Solution.
11-11-2021 08:53 AM - edited 01-14-2022 10:29 AM
actually the goal is to migrate from 2.1 on SNS-3495 to 2.7 on SNS-3655 keeping the old deployment addressing.
because on 2.7 restore from 2.1 backup is not n option interim SW is needed. this is where the dancing begins. reimaging of SNS-36XX with 2.[24] wont work. with TAC it was identified that reimaging with 2.6 will work & restore on 2.6 from 2.1 backup is n option. then reimaging with 2.7 with restoring from 2.6 backup.
good luck to everyone
UPD: yesterday i was reimaging SNS-3655 to 2.7. it was horror: i've been w8ing 1H per CARSise* & 30m per Oraclesw* package. despite the fact that win-machine's browser with its "DAS"-located images is just 1 hop away from ISE-node in the same DC. i suspect "DAS" to be n issue here.
11-09-2021 09:25 AM
yes that should work, backup out of the box always prefer.
11-09-2021 09:45 AM
tnx Balaji.
so... it looks like i'm on only right way? :0)
11-09-2021 12:41 PM
You are, I am guessing here you are doing VM deployment, so your ISE 2.1(OLD suggest to keep still keep offline ) until you total move 2.7 as roll back plan.
11-11-2021 08:53 AM - edited 01-14-2022 10:29 AM
actually the goal is to migrate from 2.1 on SNS-3495 to 2.7 on SNS-3655 keeping the old deployment addressing.
because on 2.7 restore from 2.1 backup is not n option interim SW is needed. this is where the dancing begins. reimaging of SNS-36XX with 2.[24] wont work. with TAC it was identified that reimaging with 2.6 will work & restore on 2.6 from 2.1 backup is n option. then reimaging with 2.7 with restoring from 2.6 backup.
good luck to everyone
UPD: yesterday i was reimaging SNS-3655 to 2.7. it was horror: i've been w8ing 1H per CARSise* & 30m per Oraclesw* package. despite the fact that win-machine's browser with its "DAS"-located images is just 1 hop away from ISE-node in the same DC. i suspect "DAS" to be n issue here.
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