1. Network Communication Requirements (end-user to core) End-User (Workstation) Server Automation Core HP Server Automation: Core Related ComponentPurposeSourceSrc PortDestinationDst Port Opsware Command CenterHTTP redirectorSA End-user workstationgt 1023SA Cores80 (tcp) Opsware Command CenterHTTPS Proxy for SAS Web Client UI,SA End-user workstation,gt 1023SA Cores443 (tcp) SAS Client, Opsware Web Services (2.2)Also any inbound WSAPI Opsware Command CenterLoad Balancing Gateway for the SAS ClientSA End-user workstationgt 1023SA Cores8080 (tcp) Opsware Global File SystemGlobal shell session from an SSH clientSA End-user workstationgt 1023SA Cores2222 (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

2. 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 ComponentPurposeSourceSrc PortDestinationDst Port Core to Core Management Gatway Tunnel Tunnel Tibco ConnsCore (Bi Directional)2001 (tcp)Core (Bi Directional)2001 (tcp) Management Gateway Tunnel (2001) * Multi-master Mesh Component

3. 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 ComponentPurposeSourceSrc PortDestinationDst Port Core to Core Core Gateway Inbound tunnels from other GatewaysAny SA Satellite Any SA Core2001 (tcp) Core Gateway Tunnels 2001 (TCP) Bi-Directional

4. 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. Server Automation Core*/ Satellite Managed Server / To be Provisioned Managed Server / To be Provisioned ComponentPurposeSourceSrc PortDestinationPort Build ManagerRegister in server poolOS Prov server mini-agentGt 1023SA Satellites8017(tcp) Boot ServerDHCPOS Prov server mini-agent68 (udp)SA Satellites67 (udp) Boot ServerTFTPOS Prov server mini-agentgt 1023 SA Satellites 69 (udp) Boot Server, Media ServerRPC (portmapper), required for NFSOS Prov server mini-agentgt 1023 SA Satellites 111 (udp, tcp) Boot Server, Media Serverrpc.mountd, required for NFSOS Prov server mini-agentgt 1023 SA Satellites Dynamic * Boot Server, Media ServerNFSOS Prov server mini-agentgt 1023 SA Satellites 2049 (udp, tcp) Agent GatewayInterface to the Build ManagerOS Prov server mini-agentgt 1023 SA Satellites 8017 (udp, tcp) Boot Server, Media ServerSMB/Netbios (name svc)OS Prov server mini-agentgt 1023SA Satellites137 (udp,tcp) Boot Server, Media ServerSMB/Netbios (datagram svc)OS Prov server mini-agentgt 1023SA Satellites138 (udp,tcp) Boot Server, Media ServerSMB/Netbios (session svc)OS Prov server mini-agentgt 1023SA Satellites139 (udp,tcp) DHCP 67 UDP PXE Preboot eXecution Environment TFTP 69 UDP NFS and SMB (adding netbios ports below)

5. Network Communication Requirements (managed server to core/satellite) Server Automation Core* / Satellite Managed Server (post provisioning) Core/Satellite Initiated ComponentPurposeSource DestinationPort Opsware Agent Core to Agent connectionsSA Core or Satellitegt 1023Managed Server 1002 (tcp) Agent Gateway Agent to Core connectionsManaged Servergt 1023 SA 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