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.
How does everyone feel about service graphs in a brownfield network centric cutover? maybe I'm an old school engineer but I was taught that if you have to do a Pbr then your design is wrong. they are a pain to troubleshoot because you always f...
To participate in this event, please use the button to ask your questions
This special event - formerly known as Ask the Expert- is open only to Cisco Customers and Partners.
Many pages in the Cisco Community are acce...
Going to Cisco LIVE EMEAR 2020? Give your Data Center agenda a boost with these top recommended sessions. Register and join us!
Data Center Networking:
From Reactive to Proactive NetOps With Cisco Network Assurance and Insights- The Power of Data...
Hi allWe're trying to tackle a DHCP relay problem between a set of N9K-C9332PQ (NXOS 9.3.2) and dnsmasq (doesn't work) resp Windows 2016 DHCP service (works with some tweaking).SITUATION:We have a BGP EVPN VXLAN (L2VNI and L3VNI) with anycast gateway setu...