The cascading tree enumerates the parent server and all child servers in a Control Manager network.
The parent server and child server communication uses a user-specified port for MCP agents and port 10319 through TCP/UDP for Control Manager agents.
The following table describes the connection status in a Control Manager cascading tree:
Action |
Parent Child |
Parent Child |
Parent Child |
Parent Child |
Standalone Server |
Direct unregistration |
|
|
|
| |
Forced unregistration |
| ||||
Registration |
|
|
|
|
|
Uninstall Control Manager (save Database) |
|||||
Uninstall Control Manager (delete Database) |
When both Child and Parent servers are Control Manager 5.0 servers, no forced unregistration is supported.
Parent and child server relationship
Based on the table:
Direct unregistration of a disabled child server is not allowed
Direct or forced unregistration of an active child server removes the child server record in the parent server database and removes the child server record in the child server database
If you uninstall the Control Manager application on a disabled child server, save the Control Manager database, re-install Control Manager, and then re-register it to the same parent server, the child server status will remain the same—disabled
If you uninstall the Control Manager application on a disabled child server, delete the Control Manager database, re-install Control Manager, and then re-register it to the same parent server, the child server status will become active
In addition, the table highlights the following parent and child server relationship when the cascading relationship is set to enable:
The parent server:
Polls each child servers to update the Status Summary screen in real-time
Updates a child server connection status every three minutes
The child server:
Sends logs to parent server according to log sending configuration which is configurable from parent side
Sends new or updated report profiles
Disabling a child server does not permanently sever the connection between the two Control Manager servers. The parent and child server connection is still present. The parent server issues a single command to the child server — Enable Cascading Control Manager. Once the child server receives and accepts this command, the parent server resumes managing the child server.