For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

RahulG's avatar
RahulG
Icon for Altocumulus rankAltocumulus
Oct 16, 2024

Migration from physical Hardware to R series

I have a physical hardware box 4000s in which there are 4 X 1 gig interfaces in a trunk. In new r series device r4600 we have trunk with two 25 gig interfaces. Can I copy the UCS from old device and...
asm
LTM
r series
Jeffrey_Granier's avatar
Jeffrey_Granier
Icon for Employee rankEmployee
Oct 17, 2024

Hi Rahul,

 

When you use journeys it will migrate the BIG-IP Configuration objects - vs,pools,pool members, nodes etc.  pre-configuration of the destination device network details should be completed prior to migrating a configuration.  Posting a snippet of the Journeys pre-req:

 

  1. Destination System preparation for JOURNEYS
    1. Destination BIG-IP should be in Active state.
    2. If migrating from BIG-IP 14.0.x or lower, ensure that mgmt-dhcp value in sys global-settings on the Destination System is set to either disabled or enabled. Any other values - namely dhcpv4 and dhcpv6, available starting at 14.1.0 - will cause an error during configuration loading.
    3. VLANs, trunks and interfaces should already be configured on vCMP, rSeries and VELOS systems. For more details, please refer to: Platform-migrate option overview: K82540512.