Technical Forum
Ask questions. Discover Answers.
cancel
Showing results for 
Search instead for 
Did you mean: 
Custom Alert Banner

Seeking Efficient Migration Advice: From BIG-IP i2800 (12.1.5.2) to BIG-IP r2600 (17.1.0.3)

igssv
Cirrus
Cirrus

Dears,

I need to migrate configurations from an end-of-support BIG-IP i2800 (12.1.5.2) to a newly purchased BIG-IP r2600 (17.1.0.3).

  • Current Device: BIG-IP i2800 12.1.5.2
  • New Device: BIG-IP r2600 17.1.0.3

Since BIG-IP Journey seems to support only up to v16, I'm considering the following migration steps:

  1. Trial use BIG-IP VE 12.1.5.2, import UCS from i2800: load sys ucs [i2800 UCS File] no-license platform-migrate
  2. With the VE version, verify the configurations while setting up the r2600.

This process seems cumbersome, and I’m wondering if there’s a more efficient alternative. Any advice or information would be greatly appreciated.

1 REPLY 1

Paulius
MVP
MVP

@igssv That seems like a good method and you could also try SCF and modify that file to match the interfaces on the new device. Just make sure you migrate the master key from the old F5 to the new F5 as well.

https://my.f5.com/manage/s/article/K13408