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

Steven_J__Willi's avatar
Steven_J__Willi
Icon for Nimbostratus rankNimbostratus
Apr 27, 2014

Node vs. Member

After going through F5 university and reading from docs, I am still struggling with the difference of Node vs. Member and when to use one or the other when determining the LB method. Does any one have their own terminology or definition that maybe I would understand better? thanks.

 

9 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Steven,

     

    Node is just the server IP address, for example. Whilst Member will be Node + port.

     

    You may have two pools, an http one and an ftp one. Both pools have the same pool members, for example. So, to decide between Node or Member for load balancing you would ask yourself, do you care if pool member A, for example, is serving multiple FTP requests when you deliver HTTP traffic to it. If you would rather this was taken into account then Node would be the answer, if you don't then using Member would just care about current http requests to a pool member, disregarding how many ftp connections there are.

     

    Does this make sense?

     

    N

     

  • So I am going to say that real world cases are going to use "node" the most because we do care how many other connections are serving outside a particular protocol because this will have an affect on performance. Would this be a good assumption?

     

    • nathe's avatar
      nathe
      Icon for Cirrocumulus rankCirrocumulus
      Real world...yes, best to consider all load on pool members, but....I have seen both.
  • More often than not, you're probably not going to have multiple load balanced protocols load balanced from the same server. That would be like running an FTP server on your web server. So to elaborate on Nathan's advice, if you for example have FTP and WWW services running on the same boxes, and you have separate pools for each (and FTP pool and a WWW pool), then the node vs. member decision becomes most relevant. A node is just an IP address, while a member is a service (IP and port). If you choose member, the any load balancing or health monitoring will be based on the service (irrespective of anything else that may be load balanced). If you choose node, then a load balancing or health monitoring decision will take into consideration all services being load balanced. For load balancing, that involves looking at ALL of the connections to that server (FTP and WWW). If health monitoring, a failure of one service can remove the node from both pools.

     

  • node is not only ip address, it can be (IP Address + Port) so it is equal to member? ??

     

    • Kevin_Stewart's avatar
      Kevin_Stewart
      Icon for Employee rankEmployee
      In what way have you been able to define a port with a node creation?
    • Mahmoud_Eldeeb_'s avatar
      Mahmoud_Eldeeb_
      Icon for Cirrostratus rankCirrostratus
      I'm wrong, it is only IP Address. port only can bee added either to pool member or VS. member(pool)
  • Steven, you mentioned going through the F5 university, but did you go through the LTM essentials modules?

     

    I'm still new to the BIG-IP platform, but it was extremely helpful to go through these. I've returned to these many times. You may need a support contract to register.

     

    http://f5.learn.com > Go to Training Catalog > LTM Essentials.

     

  • Can anybody will explain me the structure of node, pool, VIPs, server etc? I am not sure which consist what? I hope you people can explain it to me! And also what is the difference between pool and pool member? (It will sound stupid but I am really confused.)

     

    Thanks R