The following ports need to be open in the firewall for SolutionPack access.

Port name Port number Description
http 58080 Used for accessing SAS Web portal.
ESRS 58443 Secures access of M&R frontend portal. It will periodically check on port 58443 that SAS install is up and running.
LDAP 389 Used for LDAP authentication.
SSHd 22 Used by text collector.
https 443 SSL connection to vCenter for Vmware VMs/ESX/ESXi's discovery using Vmware APIs.
SNMP 161 SNMP V1/V2/V3
Standard SNMP Polling for discovering network switches or routers.
Load-Balancer Arbiter 2020 Load Balancer connector(LBC) running on Collector hosts will communicate with Load Balancer Arbiter(LBA) running on Primary Backend host for latest Load Factor/ Balancing information.
Backend-1 2101 TCP Socket connector ports for pushing data to additional Backend DBs. This is in case of a 4-VM vApp.
Backend-2 2201 TCP Socket connector ports for pushing data to additional Backend DBs. This is in case of a 4-VM vApp.
Backend-3 2301 TCP Socket connector ports for pushing data to additional Backend DBs. This is in case of a 4-VM vApp.
Backend-4 2401 TCP Socket connector ports for pushing data to additional Backend DBs. This is in case of a 4-VM vApp.
Backend Mgmt 2001 TCP Socket control interface for Backend
Alerting-Backend 2010 Raw data sent from Collector to alerting backend
Topology Service 48443 Topology Mapping Service(TMS)service running on Collector will send data to Topology Service running on Backend Host.
Topology Service 48443 Frontend web application will communicate with Topology Service (TS) running on Primary Backend.
Topology Service 58083 58083 is just internal port for Web service gateway to communicate with Topology Service. However, in all-in-one deployments, where secure communication between components is not required, this could be used instead of 48443 by both TMS, or the frontend.
Event Processing Manager (Alert Consolidation) 2040 Alerts collected for VNX will be posted through this port.
Generic Event Listener(Alert Consolidation) 2042 User action events such as - Acknowledge/Unacknowledged or Assigned/unassigned, triggered from Alerting Dashboard, Situation to Watch or any other relevant Alerting view would be sent to Primary Backends' port 2042.
Web-Service gateway 48443 To connect/register from Frontend to administer remote W4N servers.
Also, Maps Service on Frontend communicates to Topology Service running on Primary Backend via this port.
SNMP Collector-1 2008 Administer remote SNMP Collector
SNMP Collector-2 2108 Administer remote SNMP Collector
SNMP Collector-3 2208 Administer remote SNMP Collector
SNMP Collector-4 2308 Administer remote SNMP Collector
JMX 52569 Alert Manager configuration
MySQL 53306 MySQL Database Access
Event Processing 52001 Listens for incoming requests for event processing
Tomcat-listener 58005 Tomcat listens for incoming requests on this port
Event Processing 52004 TCP port used by the collector to send events to event processor on Primary backend
Event Processing 52007 TCP port to send Cisco UCS events to event processor on Primary backend
Alert Event Processing 2060 Alerting sends the event to Compliance for Impact Analysis. This is specifically for the Binary Installs where Compliance Backend can be installed independently.
Elastic Search 9200, 9300 Elastis Search
SolutionPack for Alcatel-Lucent 5620 SolutionPack for Alcatel-Lucent
JMS port for Alcatel-Lucent SolutionPack 1099 JMS port for Alcatel-Lucent SolutionPack
SolutionPack for Traffic Flows NetFlow: 2055, 9555, 9556, or 9996 SolutionPack for Traffic Flows
sFlow: 6343
SolutionPack for Smarts 15672 SolutionPack for Smarts
Smarts broker 426 Smarts broker
SolutionPack for Network Configuration Manager 5435 SolutionPack for Network Configuration Manager
SolutionPack for Cisco Unified Communications Manager 52006 SolutionPack for Cisco Unified Communications Manager