Forum Discussion

Lukes's avatar
Lukes
Icon for Altostratus rankAltostratus
Dec 31, 2018

LTM 1600 does not boot, setup used one as a replacement

Hi,

 

I have two LTM 1600 and one of them stopped working. It just does not boot anymore and the red light does not go on. I bought used one and I replaced hard drive from the broken one. The system boots but nothing works however I can access the machine via console.

 

What are the steps to make the replacement work? Do I have to reinstall BIG-IP?

 

Thank you for help, Luke

 

8 Replies

  • What do you mean nothing works?

     

    Via the console, can you access the GUI or just the CLI?

     

    Did you renew the license before trying to boot into the replacement device?

     

    Worst case, you should be able to reinstall BIG-IP, do a little config and import a UCS.

     

    • Lukes's avatar
      Lukes
      Icon for Altostratus rankAltostratus

      Nothing works, means that none of the network interfaces are up. I can access CLI via console, but when I try to setup management interface, it says that it cannot do it, because it lost connection to some process (I do not remember the name, have to check it).

       

      Also, the front LCD shows only "F5 Networks Incorporated" and the buttons do not change anything.

       

      I did not renew the licence.

       

      Also, when I boot the used device, it wants to update BIOS and it fails.

       

      I will try to get some screenshots and detail messages. As I understand your answer, I should be able to configure the used machine.

       

    • Lukes's avatar
      Lukes
      Icon for Altostratus rankAltostratus

      This is the output that I get after login to CLI and trying to changer configuration:

      root@(bigip-02-mgmt)(cfg-sync )(INOPERATIVE)(/Common)(tmos) load sys config
      The connection to mcpd has been lost, try again.
      
    • Dylan_375544's avatar
      Dylan_375544
      Icon for Cirrocumulus rankCirrocumulus

      That error does come about when the license was not renewed prior to the redeployment, so since you said you didn't do that, that could be the cause.

       

      HERE is some info on that.

       

      So you could try manually renewing the license from the CLI, HERE is some info on that.

       

      After that, if the Master Control Protocol Daemon is still down, you could try the bash command:

       

      bigstart restart mcpd

       

      From what I've seen, I've had to reinstall BIG-IP when encountering that error, but I only have experience with that error on a virtual machine and not a hardware device.

       

      Hopefully renewing the license does it for you.

       

      Hope that helps! If it does please up-vote and select this answer, it'd be greatly appreciated!

       

      -Dylan