Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 CLI Reference | 2025.1

# P4TARGET

- For the P4 Proxy and replica servers, the name and port number of the target P4 Server (that is, the P4 Server for which P4P acts as a proxy).
- For a replica or edge server, the upstream server Any server in the inward direction, that is, toward the central server. For example, in an edge-to-edge configuration with a commit, edge1, and edge2, both edge1 and the commit server are upstream servers for edge2. See also 'central server'. from which it retrieves its data, and towards which changelists, if applicable, are forwarded.

## Usage notes

Used by Client? | Used by Server? | Command-Line Alternative | Can be set in P4CONFIG file?
--- | --- | --- | ---
No | Yes | `p4p -t host:port` `p4d -t host:port` | N/A

## Value if not explicitly set

Program | Value
--- | ---
P4 Proxy | `perforce:1666`
Replicated environments | None

## Examples

P4 Server examples
`1818`
`london:11111`
`perforce.example.com:1234`
`192.168.0.123:1818`

## Notes

The format of `P4TARGET` is ``host`:`port``, or `port` by itself if both the P4 Server and the proxy, replica, or edge server are running on the same host.

Port numbers must be in the range `1024` through `32767`.

For more about replicas, edge servers, and the P4 Proxy, see Deployment architecture in the P4 Server Administration Documentation.

Your search for returned results