Forum Discussion

fouad's avatar
fouad
Icon for Altostratus rankAltostratus
Jan 24, 2020
Solved

F5 BIG IP LTM VE tmm re

Hello everyone :)

 

I am trying to integrate a F5 LTM VE (15.1.x) on my ESXI.

Just after the deploiment, the console is crawling under broadcast message about tmm, here an example :

 

Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:33:07 CEST): logger[13322]: Re-starting tmm3

 

It seems to be related to the virtual network device from Vsphere.

I also tried to list my current interfaces with tmsh list net interface, but the interface have no MAC address, thats weird right ?

 

Does anyone had this situation before ?

 

Best Regards

  • Ok, i have found a solution on this.

    It seems that my esxi is not delivering amount of memory I asked for.

     

    I reduced the memory per VM and now everything seems to work correctly.

     

    Thanks !

     

    Best Regards,

4 Replies

  • Hi Fouad,

    did you pick the OVA and loaded it into your ESXi ? and checked compatibilty with your ESXi version ?

    and when you start the VE from the OVA, be sure to not upgrade the ovftools inside your VE.

    HTH

    • fouad's avatar
      fouad
      Icon for Altostratus rankAltostratus

      Hi Philipe,

       

      Yes the ESXI is compatible with my version of F5 LTM, and I did not upgraded the ovftools in my VM.

      The broadcast are happening right after the boot.

       

      If I try to get the mac adress from my interface with this command :

       

      tmsh list net interface

       

      The broadcast message start for sure every time ...

       

      Best Regards,

      • fouad's avatar
        fouad
        Icon for Altostratus rankAltostratus

        Hi again,

         

        I checked the file /var/log/tmm and I have this error message all over the file

         

        <13> Jan 28 08:11:10 node-02 notice map_tmm_memory: set_mempolicy 0 node 0x0 failed 22 (Invalid argument)

         

        Hmm seems to be a memory problem ....

  • Ok, i have found a solution on this.

    It seems that my esxi is not delivering amount of memory I asked for.

     

    I reduced the memory per VM and now everything seems to work correctly.

     

    Thanks !

     

    Best Regards,