Network and port requirements (BigFix scenario)
When planning the infrastructure, ensure that port numbers used by License Metric Tool, BigFix®, and the database are free to enable communication between those components.
The following is the list of default ports used within the License Metric Tool infrastructure. You can change them during the installation of each component.
License Metric Tool domain
Interaction | Type | Default port |
---|---|---|
a | REST API data traffic | 9081 |
b | Web browser data traffic | 9081 |
c | Connection to the database |
|
d | VM Manager Tool RMI communication. The communication is internal. The port does not have to be open externally. | 25001 |
e | Extraction of virtualization hierarchy by using REST API | Specific to the type of virtualization manager |
f (optional) | Export of license usage data to IBM® Software Central or Red Hat® Marketplace | 443 |
g (optional) | Export of license usage data to IBM Software Central or Red Hat Marketplace through a proxy server | Specific to the proxy server |
BigFix domain
Interaction | Type | Default port |
---|---|---|
A | BigFix console data traffic | 52311 |
B | Directory server user authentication | 389 or 636 (for SSL) |
C | REST API data traffic | 8080 or 8083 |
D | Directory server user authentication | 389 or 636 (for SSL) |
E | Download of new data from external fixlet servers | 80 (typically); possibly 443 |
F | Gather, post, download | 52311TCP |
G | UDP new informationmessage |
52311 |
H | Relay selection | None |
I | Extraction of virtualization hierarchy by using REST API | Specific to the type of virtualization manager |
J | VM Manager Tool RMI communication. The communication is internal. The port does not have to be open externally. | 25001 |
Cross-domain communication
Interaction | Type | Default port |
---|---|---|
1 | Download of the scanner catalog | 9081 |
2 | Download of the scan results from endpoints | 52311 |
3 | Directory server user authentication | 389 or 636 (for SSL) |