The NetMRI and Event Collector (EC) interact over the network in several different modes. Different ports are used for these different modes, as follows:

NetMRI to EC

• Port 8089 is used for the Event Indexer API. This is used to retrieve and save search criteria, as well as perform the auto-login when the user hits the Event Browser link. It is also used internally for performing searches related to the Event Summary screen, and other places.
• Port 80 is used for the EAM API. This includes updating how the symptoms map to search criteria, the administrator password, and pushing device, interface, and group data to the EC for event enhancement.
• Port 22 is used to create a tunnel from the NetMRI to the EC GUI. This proxies NetMRI port 9100 to EC port 8000.

EC to NetMRI

• Port 80 or 443 is used to send symptom reports to the NetMRI from the EC, as well as to register the EC with the NetMRI, depending on whether HTTPS is enabled on the NetMRI or not. The setting in the "Register" page is used for the initial registration request. After that, if https is enabled on the NetMRI, it will be used, and the EC will be reconfigured to show this.

Browser To NetMRI

• Port 9100 must be open from the browser to the NetMRI for the Event Browser to work. This is forwarded by the ssh tunnel to port 8000 on the EC.
• Of course Port 80 or 443 must be open on NetMRI (this is not a new requirement).

Browser to EC

• No ports are needed from the browser to the EC. This is why we use the ssh tunnel to proxy the EC on the NetMRI.
• Port 22 is required for any admin user that needs ssh access to the EC.

 Was this usefull ?