Cm Ports - Documentation for Bmc Client Management 12.9

Cm Ports - Documentation for Bmc Client Management 12.9

This topic lists the ports used by the BMC Client Management agent for all different modules and provides some details on each.

Port overview

Component

Source

Destina-tion

TCP/ UDP

Service

Port number

Description

Database connection *

Master Server

Database Server

TCP

TCP

Oracle: 1521 Postgres: 5432 SQL Server: 1433

For communication between the master server and the database. (* only if the database is on another server than the master)

Agent Rollout for Windows

Rollout Server

Client Devices

TCP

SMB

445,139

To install the CM agent on the Windows target devices.

Agent Rollout for Linux and macOSRollout ServerClient DevicesTCPSSH22

To install the CM agent on the Unix target devices.

Client Agent communi-cation

Client Devices

Master Server

HTTP

1610, 1611

The connection must be bidirectional between the client and its parent for optimal settings. 

If bidirectional connection is not possible then it must be unidirectional from the client to the parent and, in this case, a tunnel on the port 1611 is used. The downwards direction can be replaced by a tunnel.

1610 is the default main agent communication port.

Addition information about tunnels in BMC Client Management:

  • If a client can be contacted by its parent, the tunnel is not required. When necessary, the parent connects to the client and calls one or more web services.
  • If a client cannot be contacted by its parent, the tunnel is required. When tunnels are used by clients to communicate with their parent, the agent uses the 1611 port so it must be opened. It is created and monitored by the client and all the downstream communication occurs within. Note that this tunnel can be used for the upstream communication also, which is not mandatory (the parent is visible from the client so new transient TCP connections can be opened).

CM console

Administra-tive computer

Master Server and Client Devices

HTTP

1611 (1610)

The default console management port.

Bandwidth Throttling *

Relay

Client

TCP

TCP

1609

The bandwidth management port on relay servers. (* only used if transfer windows are defined with a percentage)

MyApps

1611 (1610)

The MyApps port on the master server.

AutoDiscovery

TCP

TCP, HTTP

135,22, 23,139, 1610

TCP ports scanned for auto-discovery.

Multicast Traffic

Relay

Client

UDP

UDP

2500 *

The multicast transfer agent listen port as configured. * An IP range must also be configured.

Active Directory LDAP

Master Server

LDAP Server

TCP

LDAP

389

To synchronize data from LDAP server to CM .

Email Server

Master Server, console

Email Server

TCP

SMTP

25

To send alerts and reports on email to users. This port must be open on all devices from which emails are sent via the console.

WebAPI

Browser, Web service caller

Master Server

TCP

HTTP

1616

The port for the web services.

Asset discovery

The ports and ranges documented below are the default values. These values can be changed in the RemoteInventory.ini (TcpPortRange and UdpPortRange) file.

Component

Source

Destination

TCP/UDP

Port number

Description

Asset Discovery

Asset Discovery Server

IP Devices

TCP

15, 22, 23, 35, 80, 135, 137, 139, 443, 445, 515, 9100-9102

TCP ports and ranges to be used for the Asset Discovery scans

Asset Discovery

Asset Discovery Server

IP Devices

UDP

161

UDP ports and ranges to be used for the Asset Discovery scans

Asset DiscoveryAsset Discovery ServerIP DevicesTCP1024 -1030Restricted WMI (DCOM)
Asset DiscoveryAsset Discovery ServerIP DevicesTCP49152 - 65535Unrestricted WMI (DCOM)
Alexander Ross
Author

Alexander Ross

Alexander Ross has covered the video game industry for a decade, writing deep dives on game design, esports tournaments, VR developments, and gaming culture.