Default Ports and Data Flow

The following lists the default ports:
camm27
DX NetOps
Default Ports
The following lists the default ports:
Component
Port
Type
Comments
MultiController
29599
29600
TCP
Communicates with LocalController via heartbeats to
maintain status.
LocalController
29598
TCP
Communicates with MultiController via heartbeats to maintain status.
Generic Executor
29560
TCP
Listens on this TCP port to receive XML configuration files from MultiController and LocalController.
Web Manager
8005
8880
HTTP
Administrators browse to the Web Manager (located on the MultiConroller) server over port 8880.
Delivery Service
29597
TCP
Communicates with MultiController through LocalController to distribute the data to one or more local or remote Presenters.
Engines/Presenter
29100
29101
29102 etc.
TCP
Communicates with MultiController via heartbeats to maintain status.
Each component of
DX NetOps
listed in the above table uses random ports for the following:
  • Random TCP port for naming services for the communication between
    DX NetOps
    components.
  • Random TCP port for the internal communication between
    DX NetOps
    subcomponents.
Data Flow
  • Engine polls the Element Management System.
  • Engine converts data to XML format.
  • Engine performs any calculation or filtering required.
  • Engine delivers data in CAMM2XML format to the queue directory.
  • Delivery Service reads queue and transfers XML file to the Presenter(s) (Local or Remote) using the name service.
  • Presenter reads the XML file and outputs the data in the required format.
The following diagram shows the typical data flow in
DX NetOps
.
Data Flow in CAMM
Data Flow in CAMM