Default IPLM port requirements

The Port configurations required for a Perforce IPLM deployment. Each has a default, which can be configured as needed for a particular deployment.

Perforce IPLM ports

Perforce IPLM provides the ability to configure which ports are used for which services, these are configured via configuration files, it is typically necessary to restart the corresponding service for the changed port settings to take effect.

Perforce IPLM Server port

Default Port: 8080

Configuration file: /etc/mdx/piserver.yml

The Perforce IPLM Server port is the port used for Perforce IPLM clients to access the Perforce IPLM server. This port needs to opened on the Perforce IPLM server. The piserver.yml file is described on the piserver.yml Configuration File page.

Perforce IPLM Web port

Default Port: 80

Configuration file: /etc/mdx/piweb.conf

The Perforce IPLM Web port is the port used to access the IPLM Web client. This port needs to be opened on the IPLM Web server. The piweb.conf file is described on the IPLM Web configuration page.

Perforce IPLM Cache port

Default Port: 5000

Configuration file: /etc/mdx/picache.conf

IPLM Cacheservers managed cached IP data, there can be multiple IPLM Cache servers, often distributed by geographical site. Each IPLM Cache server machine requires this port to be opened. More information is available on the picache.conf Configuration file page.

Perforce IPLM Metrics Dashboards

Default Port: 2000

Configuration file: /etc/mdx/mdx-metrics.grafana.conf

Port to access the Perforce IPLM Metrics dashboards (Grafana). More information is available on the Events administration page.

Other Ports

Perforce

Default Port: 1666

Configuration: The Perforce port is typically defined by the startup arguments to the p4d process.

More information is available on the P4 Server administration page.