Managing your HP servers through firewalls with HP SIM (481364-002, February 2008)

14
Y
3
2367 RMI HP SIM RMI connection
Y Y 2381 HTTPS Web agent Web server
Y 5432 ProstgreSQL Server database
Y Y 5988 HTTP WBEM service
Y Y 5989 HTTPS WBEM service
Y 50000 HTTPS HP SIM Web server
Y 50001 HTTPS
HP SIM SOAP (configurable
6
)
Y 50002 HTTPS HP SIM SOAP with client certificate
authentication (configurable
7
)
Y 50003 HTTP HP SIM SOAP (configurable
8
)
Y Y 50004 HTTPS/HTTP WBEM event receiver (configurable)
Y 50005 WBEM WBEM Events
Y 50006 PostgreSQL PostgreSQL
Y 50008 SIM JMS JMS port
Y 50009 SIM JNDI JNDI port
Y Y 50010
DMI
5
DMI
50013 RMI Web Services RMI Loader
50014 JRMP JRMP Invoker
50015 Pooled invoker Pooled invoker
Y
4
Y 411 HTTP IBM Director agent
Y
4
Y 1311 HTTPS Server administrator
Y
4
2069 HTTP OSEM
Y
4
Y 3202 HTTPS StorageWorks NAS
Y
4
Y 3257 HTTPS Rack & Power Manager
Y
4
Y 4095 HTTP CommandView ESL
Y
4
Y 4096 HTTP CommandView SDM
Y
4
Y 8000 HTTP HP Web letAdmin
Y
4
Y 8008 HTTP Default home page
Y
4
Y 8443 HTTPS HP Web JetAdmin
Notes:
Outbound (out) – Request or response sent from a server is called outbound
Inbound (in) – Request or response received by a server is called inbound
1
All ports are for TCP and UDP (except ICMP).
2
The CMS will normally have all managed system ports open, as the CMS is a managed system itself. Firewalls may be
configured to block these ports if the CMS is not to be managed from another system.
3
RMI port is used within the CMS for inter-process communication. Connections from outside the CMS are not accepted, and
firewalls may block this port.