You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current page is unclear on where these ports are used. I suggest adding clarification that these are for communication of the Trident pods itself, eg.
The following ports are used by the different Trident pods for communication
In addition (and this is what most users will likely need to request firewall changes) we should probably list the ports used by the different protocols that Trident supports, e.g.
`Trident uses port 443 to communicate with the API endpoint of an Ontap or FSxN system. In addition, the standard ports of the selected storage protocol are required:
iSCSI uses port 3260
NFSv4 uses port 2049
NSFv3 uses ports 111 (portmapper), 635 (mountd), 2049 (NFS), 4045 (NLM), 4046 (NSM) and 4049 (rquota)
NVMe/TCP uses ports 8009 (discovery) and 4420 (data)
`
Public issues must not contain sensitive information
This issue contains no sensitive information.
The text was updated successfully, but these errors were encountered:
Page URL
https://docs.netapp.com/us-en/trident/trident-reference/ports.html
Page title
Astra Trident ports
Summary
The current page is unclear on where these ports are used. I suggest adding clarification that these are for communication of the Trident pods itself, eg.
The following ports are used by the different Trident pods for communication
In addition (and this is what most users will likely need to request firewall changes) we should probably list the ports used by the different protocols that Trident supports, e.g.
`Trident uses port 443 to communicate with the API endpoint of an Ontap or FSxN system. In addition, the standard ports of the selected storage protocol are required:
iSCSI uses port 3260
NFSv4 uses port 2049
NSFv3 uses ports 111 (portmapper), 635 (mountd), 2049 (NFS), 4045 (NLM), 4046 (NSM) and 4049 (rquota)
NVMe/TCP uses ports 8009 (discovery) and 4420 (data)
`
Public issues must not contain sensitive information
The text was updated successfully, but these errors were encountered: