Forum Discussion
AlaaIbrahim
Nimbostratus
NimbostratusMigration to rSeries using Journeys
Hello All! We were trying to migrate from VE Big-IP v16.1.3.2 to rSeries 2600. Removed all device group config from the configuration, configured VLANs, LAGs and Interfaces manually and tried to us...
zamroni777
Nacreous
Nacreousi suggest to use the gui or tmsh mechanism rather than editing files.
i had failed planned activity in 2013 even though the file editing procedures was made by f5 professional services.
btw, in poc with f5 engineer in 2011, i was able to pair viprion with VE that persistence keys were also synchronized
they definitely has different physical port layout.
so you can try pair the ve with r2600 then break the pair after shared config are synchronized.
if you have second r2600, set the HA pair after it.
yakai
Cirrus
CirrusHello
Using GUI and clustering approach is good, however there are some requirements you have to satisfy :
You should have connectivity between VE and your target r2600 (which is not the case all the time). Moreover performing this action on production env may cause a down time.
UCS approach does not require neither file editing nor connectivity , and I personally performed it manu time with big success and no down time.
Regards