Network Communication Requirements (end-user to core)

End-User (Workstatio

n)

Server Automation

Core

HP Server Automation: Core Related

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, SA End-user workstation, gt 1023 SA Cores 443 (tcp) SAS Client, Opsware Web Services (2.2) Also any inbound WSAPI

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)

Global Shell - SSH (2222 TCP )

Opsware Global File System

HTTP/HTTPS (80/443 TCP)

Opsware Command Center

8080 tcp – Load balanced gateway to SA Core

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)

Server Automation

Core

Server Automation

Core

Component Purpose Source Src Port Destination Dst PortCore to Core

Management Gatway Tunnel Tunnel Tibco Conns Core (Bi Directional) 2001 (tcp) Core (Bi Directional) 2001 (tcp)

Management Gateway Tunnel (2001) *

Multi-master Mesh Component

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.

Server Automation

Core

Server Automation

Satellite

Component Purpose Source Src Port Destination Dst PortCore to Core

Core GatewayInbound tunnels from other Gateways Any SA Satellite Any SA Core 2001 (tcp)

Core Gateway Tunnels

2001 (TCP) Bi-Directional

Network Communication Requirements(server to core/satellite)

HP Server Automation: ProvisioningThese 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.

Server Automation Core*/ Satellite

Managed Server /To be Provisioned

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)

DHCP 67 UDPPXE Preboot eXecution Environment

TFTP 69 UDP

NFS and SMB (adding netbios ports below)

Network Communication Requirements(managed server to core/satellite)

Server Automation Core* / Satellite

Managed Server (post provisioning)

Core/Satellite Initiated

Component Purpose Source Destination Port

Opsware Agent Core to Agent connections SA Core or Satellite gt 1023 Managed Server 1002 (tcp)

Agent Gateway Agent to Core connections Managed Server gt 1023SA Core or Satellite 3001 (tcp)

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.

3001 (TCP)

1002(TCP)

Agent (Server) Initiated