The netmask is used to determine how much of the source address is used to create an entry in the database - i.e. the network component rather than the host component is used. If you use a /16 mask then the first client to connect will create a sticky database entry and all subsequent clients from your NATTed range will match that entry and be load-balanced to the same server. This is probably not what you want.
I tend to use a /32 mask to balance each client individually but if your clients are evenly distributed across the /16 you could use a /24 mask and create fewer sticky entries in the database.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...