To ensure that the SteelCentral products can communicate correctly, you must open up ports across any existing firewalls. The figures in this section show which ports and protocols are necessary for different deployment scenarios. The figures also show external port dependencies for various integrations. For more details about external integrations, see Additional SteelCentral Integration.
Figure 2‑10 shows which ports and protocols you must have open for communications within a Packet Analyzer and a NetShark deployment. External connections are optional, depending on which integrations you use.
Figure 2‑10. Packet Analyzer and NetShark Dependencies
Figure 2‑11 shows which ports and protocols you must have open for communication within a NetProfiler and Flow Gateway deployment. External connections are optional, depending on which integrations you use.
Figure 2‑11. NetProfiler and Port Dependencies
Figure 2‑12 shows which ports and protocols you must have open for communications within a NetProfiler, Flow Gateway, and NetShark deployment. External connections are optional, depending on which integrations you use.
Figure 2‑12. Full Solution Port Dependencies
Figure 2‑13 shows which ports and protocols you must have for communications within an Enterprise NetProfiler, Flow Gateway, and NetShark deployment. Many external connections are optional, depending upon which integrations you use. You must have all components that compose the Enterprise NetProfiler on the same network subnet, using 1-Gb ports and connected to the same switch. If you include a dedicated dispatcher in the deployment, the switch it is connected to must have two available 1-Gb ports and a support channel bonding to allow for the higher bandwidth required.
Figure 2‑13. Enterprise Solution Port Dependencies
