For meeting the loadbalance requirements for LYNC 2013 FE SERVER, which features will be necessary for HLB ?

Question

        I has read the deployment guide from some vendors, such as A10 networks and coyotepoint, it seems that HLB will have the ability to load balance the lync flow when it support  L4_VS,  least-connections method, source_ip
persistence, as follows
VIP 
Single VIP exposed through ARP
Source Address Affinity
Enabled
TCP Idle Time-Out Interval
1800 sec
Balancing Algorithm
Least-Connections-Based
TCP Resets on Idle
Enable
My first questions is: need  the source_ip_persistence among these L4_VS  be shared ?
For example,  there are two FE servers, they are FE-1, FE-2
                     HLB has two L4_VS, they are   VS_5061, VS_443 (of  course, the vs will be more in real case)
                     When client-1  access  vs_5061, HLB will dispatch the request to FE-1 according to method,  ok, after a while,  if  client-1 try to access vs_443, will this
connections have to be dispatched to the same RS ( FE-1) ?  
Except that this question, there are any other requirement have to be support for HLB ?  such as SNAT ? such as anying else ...
                   I doesn't know the real communication theory about lync server,  so hope anyone could help me, it is very appreciated

Answer 1

For the other port with HLB, I saw the depolyment from F5 networks,  A10 networks( which are HLB vendor), the following link is one  scheme from A10
http://www.a10networks.com/resources/files/A10-DG-Microsoft_Lync_2013.pdf
So I feel that  
A.  The other port should  be able to be loadbalanced by HLB
B.  The HLB can do it with the only  L4  ability
In fact, I come from the vendor too, I want to know whether our new product (which is one type of HLB) could support LYNC,  want to know any potential requirement when deploy HLB to lync.
In other words, if our produce has the ability as follows
VIP 
Single VIP exposed through ARP
Source Address Affinity
Enabled
TCP Idle Time-Out Interval
1800 sec
Balancing Algorithm
Least-Connections-Based
TCP Resets on Idle
Enable
 Will it have the ability to support the LYNC (not just 80 and 443)  ?