Users Guide

Protocol Flows |
1028 OMNM 6.5.2 User Guide
Protocol Flows
The following network protocol flows represent the application’s interactions with Network Devices
(for example: Dell Powerconnect switches). The (N) in these lines identifies dynamic port
assignments. Often, OpenManage Network Manager establishes several communication flows to a
specified static port so N can represent several dynamic ports. This list also outlines alternative
flows for JBoss JMS activation.
NOTE:
This does not identify time service flows like ntp that can manage the time on the servers.
The following were changes to a standard installation done for the sake of measuring the protocol
flows. In the J2EE Naming Service: the RMIPort was changed to 31310. Also,
owappserver.properties (turns off mediation v2 services on application server) was
changed: mediation true->false. This essentially disables mediation on the application server.
The following is the installation that produced the listed protocol flows: Full Application Server
Installation, Custom Mediation Installation, toggling off 2 (MySQL) and 5 (App Server). The
client was a simple client installation.
Application Server to Mediation Server Flows
J2EE
TCP Med Svr (N) -> App Svr (1098)
TCP Med Svr (N) <-> App Svr (1098)
TCP Med Svr (N) -> App Svr (1099)
TCP Med Svr (N) <-> App Svr (1099)
TCP Med Svr (N) -> App Svr (4446)
TCP Med Svr (N) <-> App Svr (4446)
TCP Med Svr (N) -> App Svr (4445)
TCP Med Svr (N) <-> App Svr (4445)
JBoss JMS enabled:
TCP Med Svr (N) -> App Svr (8093)
TCP Med Svr (N) <-> App Svr (8093)
Application Server to Application Server in Application Server
Cluster
IGMP App Svr-A/B -> 230.13.13.13 (Multicast address assigned per application cluster)
UDP App Svr-A/B (45566) -> 230.13.13.13 (45566)
IGMP App Svr-A/B -> 230.0.0.253