Forum Discussion

David_Wallis's avatar
David_Wallis
Icon for Nimbostratus rankNimbostratus
May 20, 2009

Removing F5 Devices

I have added two LTM's and monitored them sucessfully, but we now have upgraded these to 9.4.7.320.1 however as part of this work we have also changed the management IP of these.

 

 

I cant discover them as it says the mac-address already exists nor can I remove them, as if I right click the device and then choose 'F5 Device Tasks, Remove F5 Device' I get the message "Device [xxx.xxx.x.x] has not been discovered.

 

 

Any suggestions?

 

 

David
management
microsoft
scom
  • Julian_Balog_34's avatar
    Julian_Balog_34
    Historic F5 Account
    May 20, 2009
    David,

     

     

    Try adding a static route in your hosts file (%system%\drivers\etc\hosts) mapping the old management address to the new one and attempt to remove the device, see if it'll work this time. What we think had happened, is when you updated the management IP address, the IP address change did propagate back into our device connection cache, but didn't make it into the SCOM database (at an upper layer). Currently this is not a fully supported scenario. We always recommend removing the device first before changing the IP address on the management interface and re-discovering.

     

     

    Let us know if the suggested workaround was effective. You can remove the static route in your hosts file, if you were able to successfully remove the 'old' device reference and rediscover the new one.

     

     

    Julian
  • David_Wallis's avatar
    David_Wallis
    Icon for Nimbostratus rankNimbostratus
    May 21, 2009
    That didnt work.. I tried hacking the database's with no real luck..

     

     

    reinstalling the management pack worked though - Not too much of an issue as I havent created any overrides yet and currently only have two ltm's being monitored.

     

  • Julian_Balog_34's avatar
    Julian_Balog_34
    Historic F5 Account
    May 21, 2009
    It's good that at least you could reinstall without having to go through a significant haul of reconfiguring the management pack. We'll look into adding support for such and similar discovery / removal scenarios in one of our upcoming releases. In the meantime we'll try to come up with a reasonable workaround for this issue.

     

     

    Thanks for sharing your experience with us.