Product and Software: This article applies to all Aruba controllers and ArubaOS versions.
The following network ports must be configured on the firewall to allow other types of traffic in the Aruba network. You should only allow traffic as needed from these ports.
For logging: SYSLOG (UDP port 514) between the Mobility Controller and syslog servers.
- For software upgrade or retrieving system logs: TFTP (UDP port 69) or FTP (TCP ports 20 and 21) between the Mobility Controller and a software distribution server.
- If the Mobility Controller is a PPTP VPN server, allow PPTP (UDP port 1723) and GRE (protocol 47) to the Mobility Controller.
- If the Mobility Controller is an L2TP VPN server, allow NAT-T (UDP port 4500), ISAKMP (UDP port 500), and ESP (protocol 50) to the Mobility Controller.
- If a third-party network management system is used, allow SNMP (UDP ports 161 and 162) between the network management system and all Mobility Controllers. If the ArubaOS version is earlier than 2.5, allow SNMP traffic between the network management system and APs.
- For authentication with a RADIUS server: RADIUS (typically, UDP ports 1812 and 813, or 1645 and 1646) between the Mobility Controller and the RADIUS server.
- For authentication with an LDAP server: LDAP (UDP port 389) or LDAPS (UDP port 636) between the Mobility Controller and the LDAP server.
- For authentication with a TACACS+ server: TACACS (TCP port 49) between the Mobility Controller and the TACACS+ server.
- For NTP clock setting: NTP (UDP port 123) between all Mobility Controllers and the MMS server and the NTP server.
- For packet captures: UDP port 5555 from an AP to an Ethereal packet-capture station; UDP port 5000 from an AP to a WildPackets packet-capture station.
- For telnet access: Telnet (TCP port 23) from the network administrator's computer to any AP if "telnet enable" is present in the "ap location 0.0.0" section of the Mobility Controller configuration.
- For External Services Interface (ESI): ICMP (protocol 1) and syslog (UDP port 514) between a Mobility Controller and any ESI servers.
- For XML API: HTTP (TCP port 80) or HTTPS (TCP port 443) between a Mobility Controller and an XML-API client.