Populating Ports
About this task
To begin, you can auto-populate the port ranges that are directed to each instance of the DNCA. All port ranges from 1024 and above are evenly split between the DNCA instances. For example, if you have three DNCA instances, each DNCA receives traffic from an equal number of ports, which equates to the following ports:
(65,536 - 1024) / 3 = 21,504 ports/instance
- For more information, see
http://www.iana.org/assignments/port-numbers
.
Procedure
- To populate the port ranges, click Populate Ports.
- Port ranges are populated across all available instances of the DNCA. Save your changes.
- A restart of the DNCA is required.
Results
After you populated the ports, you must monitor the traffic loading that is sent to each instance. For example, suppose your web server is delivering HTTP responses on port 8080. Then the DNCA instance that is receiving this traffic can be running hot, while others are lightly used.
Current Hits Per Second statistics are reported on the Summary tab, with each DNCA instance reported under a separate ID value.
- SSL Hits/sec rate is reported in the Reassd Hits SSL column.
- Non-SSL Hits/sec rate is reported in the Reassd Hits Non-SSL column.
Adjustments
About this task
- If you see imbalances, you must consider applying more filter rules.
- On multi-core Unica Discover Network Capture Application servers, you can create multiple instances of the DNCA and distribute the load across configurable port ranges. See Load balancing between DNCA instances using port ranges.
- After auto-populating ports, you can configure a virtual IP address. See Editing existing port range filter rules.