Forum Discussion

Kim_Stephan_510's avatar
Kim_Stephan_510
Icon for Nimbostratus rankNimbostratus
Dec 08, 2014

Impact of changing Management IP Address

Hello Devcentral Users,

 

is there any impact when changing the management ip of several BigIPs? The expected impact is the network connectivity of management interface, but which other impacts are there?

 

I have at customer side 14 Cluster (28 Machines) which I have to change the management IPs. Most are BigIPs, several are Viprions (vCMP Guests).

 

Thank you and kind regards, Kim

 

APM
application delivery
availability
LTM
management
security

4 Replies

Sort By
  • Brad_Parker's avatar
    Brad_Parker
    Icon for Cirrus rankCirrus
    Dec 08, 2014

    Yes, when you change the management IP your Device Trust is reset. This can cause the devices to not trust each other and thus become Active/Active for the same traffic group. You will need to rebuild the trust for them to communicate again. This could potentially affect application traffic so I would recommend a maintenance period.

     

  • Kim_Stephan_510's avatar
    Kim_Stephan_510
    Icon for Nimbostratus rankNimbostratus
    Dec 08, 2014

    Hello Brad,

     

    thank you for your answer.

     

    I have to do all changes at maintenance windows.

     

    Are there any problems with license? I don't think so but i'm not really sure. The license is not bound at IP-Adress, only at serial-.

     

    Kind regards, Kim

     

    • Brad_Parker's avatar
      Brad_Parker
      Icon for Cirrus rankCirrus
      Dec 08, 2014
      This shouldn't affect licensing at all. One thing to keep in mind, is if you change the management IP of the vCMP guest within the guest, the vCMP host will not reflect that change. I would recommend changing the vCMP guests' IP addresses/default route via the vCMP host in the vCMP config. I would also recommend restarting SOD on all the blade instances of each of the vCMP guests or rebooting the guests all together or you'll get these notice events in your log until you do; Config digest module error: Traffic group device not found. Support tells me this is due to SOD still looking for the old management IPs. Its benign, but I thought I'd share.
  • Emo_Gokay_22518's avatar
    Emo_Gokay_22518
    Historic F5 Account
    May 11, 2017

    Yes it will break the HA or bring the HA in INOP state. Follow these steps below to change the management IP address w/o causing outage: I hope this helps:

     

    Reassign new mgmt. IP or change mgmt. IP to F5 that is in HA pair or environment

     

    1. Create UCS file and download them to your PC from both units
    2. Put the F5 in question in standby mode
    3. Force it offline and KEEP it OFFLINE till you finish this process
    4. Break the HA between those Units by resetting the trust on both units (they will read “standalone”)
    5. Make sure that unit in question is and stays in “OFFLINE” state
    6. Re-assign the new mgmt. IP and make sure you have access to it with the new IP
    7. Make sure that unit in question is still and stays in “OFFLINE” state
    8. Rebuild the HA with the new mgmt. IP from the active unit
    9. Add the units/hostnames in the sync-failover group
    10. Sync the units from the active “self” and check the “override config” check box
    11. if successful they should be in sync
    12. test the sync feature by creating a test http monitor on the active and sync it over
    13. if that replicates it on the offline F5 it is working and you can delete the test monitor and sync
    14. now you can release the unit in question from “OFFLINE” state
    15. if you need to re-assign new IP on the active unit as well, perform failover so the initial active becomes standby and repeat the process above starting from step 3