Flow of data
There are several different interactions that occur between the components of the License Metric Tool infrastructure and between the user and tool.
Arrow indicates the connection origination.
License Metric Tool domain
Interaction | Type | Connection | Description |
---|---|---|---|
a | REST API data traffic | Default port | 9081 |
Protocol | HTTPS | ||
Origination | Client that uses REST API connections | ||
b | Web browser data traffic | Default port | 9081 |
Protocol | HTTPS | ||
Origination | Web browser | ||
![]() |
Extraction of virtualization hierarchy by using REST API | Default port | Specific to the type of virtualization manager |
Protocol | TCP (HTTP/HTTPS) | ||
Origination | VM Manager Tool |
BigFix domain
Interaction | Type | Connection | Description |
---|---|---|---|
A | BigFix console data traffic | Default port | 52311 |
Protocol | HTTPS | ||
Origination | BigFix console | ||
Network controls | There is a "refresh rate" for each BigFix console user (default 15 seconds) | ||
B | Directory server user authentication | Default port | 389 or 636 (for SSL) |
Protocol | TCP (LDAP/LDAPS) | ||
Origination | WebReports | ||
Network controls | N/A | ||
C | REST API data traffic | Default port | 8080 or 8083 |
Protocol | TCP (HTTP/HTTPS) | ||
Origination | BigFix server | ||
Network controls | N/A | ||
D | Directory server user authentication | Default port | 389 or 636 (for SSL) |
Protocol | TCP (LDAP/LDAPS) | ||
Origination | BigFix server | ||
Network controls | N/A | ||
E | Download of new data from external HCL fixlet
servers Note: For more information, see: Firewall exceptions (BigFix scenario)
|
Default port | 80 (typically); possibly 443 |
Protocol | TCP (HTTP/HTTPS) | ||
Origination | BigFix server | ||
Network controls |
|
||
F | Gather, post, download | Default port | 52311 |
Protocol | TCP (HTTP/HTTPS) | ||
Origination | BigFix client | ||
Network controls |
|
||
G | UDP new informationmessage |
Default port | 52311 |
Protocol | UDP | ||
Origination | UDP messages are sent from the immediate parentof the BigFix client. It can be either a BigFix relay or the BigFix server. |
||
Network controls |
|
||
H | Relay selection | Default port | None |
Protocol | ICMP | ||
Origination | Each BigFix client sends
progressive roundsof ICMP packets to each relay with increasing TTLs until a BigFix relay responds. For example, in a network of 2 relays, one 1 hop away and one 2 hops away, the BigFix client sends an ICMP message to both with TTL 1 and receives 2 time exceededmessages from the local router. The BigFix client then sends an ICMP message to both relays with TTL 2 and receives one time exceededmessage and one reply message. The BigFix client then chooses the relay that is one hop away. |
||
Network controls |
|
||
I | Extraction of virtualization hierarchy by using REST API | Default port | Specific to the type of virtualization manager |
Protocol | TCP (HTTP/HTTPS) | ||
Origination | VM Manager Tool | ||
Network controls | N/A |
Cross domain
Interaction | Type | Connection | Description |
---|---|---|---|
1 | Download of the scan results from endpoints | Default port | 52311 |
Protocol | TCP (HTTP/HTTPS) | ||
Origination | License Metric Tool server | ||
2 | Directory server user authentication | Default port | 389 or 636 (for SSL) |
Protocol | TCP (LDAP/LDAPS) | ||
Origination | License Metric Tool server |