Network Communication Requirements enduser to core HP Server

Network Communication Requirements (end-user to core) HP Server Automation: Core Related 8080 tcp – Load balanced gateway to SA Core End-User (Workstation ) Opsware Command Center Server Automation Core HTTP/HTTPS (80/443 TCP) Opsware Global File System Global Shell - SSH (2222 TCP ) Component Purpose Source Src Port Destination Dst Port Opsware Command Center HTTP redirector SA End-user workstation gt 1023 SA Cores 80 (tcp) Opsware Command Center HTTPS Proxy for SAS Web Client UI, SAS Client, Opsware Web Services (2. 2) SA End-user workstation, Also any inbound WSAPI gt 1023 SA Cores 443 (tcp) Opsware Command Center Load Balancing Gateway for the SAS Client SA End-user workstation gt 1023 SA Cores 8080 (tcp) Opsware Global File System Global shell session from an SSH client SA End-user workstation gt 1023 SA Cores 2222 (tcp)

Network Communication Requirements (Core to Core Communication) HP Server Automation: Core Related The Server Automation Cores replicate changes in real-time via Tibco Rendezvous. This enables the cores to remain synced with minimal network bandwidth. * Tibco communications are encapsulated over the management gateway tunnel ports (2001) Multi-master Mesh Component Server Automation Core Management Gateway Tunnel (2001) * Component Purpose Source Src Port Core to Core Management Gatway Tunnel Tibco Conns Core (Bi Directional) 2001 (tcp) Destination Dst Port Core (Bi Directional) 2001 (tcp)

Network Communication Requirements (Satellite to Core Communication) HP Server Automation: Core Related The communication between satellite servers and cores is encrypted and tunneled over a single port. Core Gateway Tunnels Server Automation Satellite Component Core to Core Gateway Server Automation Core 2001 (TCP) Bi-Directional Purpose Inbound tunnels from other Gateways Source Src Port Destination Dst Port Any SA Satellite Any SA Core 2001 (tcp)

Network Communication Requirements (server to core/satellite) HP Server Automation: Provisioning These are the various communications required to provision a new server. These are initiated through a small pre boot OS which is pushed to the server after PXE boot. * we will be placing Satellite Serves in front of ALL Cores for server to core communications. DHCP 67 UDP PXE Preboot e. Xecution Environment Managed Server / To be Provisioned TFTP 69 UDP NFS and SMB (adding netbios ports below) Server Automation Core*/ Satellite Component Purpose Source Src Port Destination Port Build Manager Register in server pool OS Prov server mini-agent Gt 1023 SA Satellites 8017(tcp) Boot Server DHCP OS Prov server mini-agent 68 (udp) SA Satellites 67 (udp) Boot Server TFTP OS Prov server mini-agent gt 1023 SA Satellites 69 (udp) Boot Server, Media Server RPC (portmapper), required for NFS OS Prov server mini-agent gt 1023 SA Satellites 111 (udp, tcp) Boot Server, Media Server rpc. mountd, required for NFS OS Prov server mini-agent gt 1023 SA Satellites Dynamic * Boot Server, Media Server NFS OS Prov server mini-agent gt 1023 SA Satellites 2049 (udp, tcp) Agent Gateway Interface to the Build Manager OS Prov server mini-agent gt 1023 SA Satellites 8017 (udp, tcp) Boot Server, Media Server SMB/Netbios (name svc) OS Prov server mini-agent gt 1023 SA Satellites 137 (udp, tcp) Boot Server, Media Server SMB/Netbios (datagram svc) OS Prov server mini-agent gt 1023 SA Satellites 138 (udp, tcp) Boot Server, Media Server SMB/Netbios (session svc) OS Prov server mini-agent gt 1023 SA Satellites 139 (udp, tcp)

Network Communication Requirements (managed server to core/satellite) HP Server Automation: Managed Agent (Server) The ports listed here are utilized once the servers have been provisioned. All post-provisioning tasks such as management, patching, audit and remediation as well as package/application deployment utilize these ports. Both ports are configurable. * we will be placing Satellite Serves in front of ALL Cores for server to core communications. Agent (Server) Initiated 3001 (TCP) Server Automation Core* / Satellite Managed Server (post provisioning) Core/Satellite Initiated 1002(TCP) Component Purpose Source Opsware Agent Core to Agent connections SA Core or Satellite gt 1023 Agent Gateway Agent to Core connections Managed Server gt 1023 Destination Port Managed Server 1002 (tcp) SA Core or Satellite 3001 (tcp)