static sticky entry using source address persistence

You may simply use source_addr as Default Persistence Profile in your virtual-server's config.

If you want to replicate the persistence to HA peer you'll have to enable Mirror Persistence in the source_addr persistence profile.

1 particular client IP need to make a connection to only 1 backend server. we want to make sure the that client :192.168.10.5 has a sticky entry stick to only app1 memeber

this vip contains 12 members in th pool

Then you'll have to use an iRule similar to this:

when CLIENT_ACCEPTED {
  if { [IP::client_addr] == "192.168.10.5" } {
    pool my_Pool member 10.1.2.200 80
  }
}

Christophe thanks for your response ,so how i can verify that all the connection from the client 192.168.10.5 are always going to the pool member 10.1.2.200

please let me know

you can verify with tmsh command:

show sys connection cs-client-addr 192.168.10.5 cs-server-addr vs_server_ip

Thanks all for your response ,I have one more question .if I need have 2 client IPs need to always connects to 2 different servers .Then how should my irule look like . DO i need 2 irules for it .

client :192.168.10.5 -----> server 10.1.2.200 client : 192.168.11.6 ------> server 10.1.2.205

No, you don't need a second iRule, just add an "elseif" statement to the previous iRule.

Have a look to iRule's Wiki (https://devcentral.f5.com/wiki/iRules.HomePage.ashx). There are a lot of example there.