Managed networks are named lists of network segments serviced by a specific SPP (SPP) or Safeguard for Privileged Sessions (SPS) appliance in a clustered environment. Managed networks are used for scheduling tasks, such as password or SSH key change, account discovery, sessions recording, and asset discovery to distribute the task load. Using managed networks, you can:
- Distribute the load so there is minimal cluster traffic.
- Specify to use the appliances that are closest to the target asset to perform the actual task.
A SPP cluster has a default managed network that consists of all cluster members. Other managed networks can be defined.
|
CAUTION: If the role of a managed host that belongs to a linked Safeguard for Privileged Sessions cluster is changed or if a managed host is added or removed from the cluster, SPP will detect the change by querying each Central Management node and attempt to stay in sync with the Safeguard for Privileged Sessions cluster topology. If the Central Management node is down, SPP warns the administrator there may be invalid policies with a message like: The session connection policy was not found, in addition to flagging each broken Access Request Policy with an Invalid notation (Security Policy Management > Entitlements > Access Request Policies tab). Based on the size of your network and other factors, this will take one to 10 minutes and, during this time window, an unavailable managed host may continue to appear on the Managed Networks page. Any requests made will be invalid and will not be able to be launch sessions. |
Precedence
The selection made on the Entitlement > Access Request Policy tab takes precedence over the selections on Appliance Management > Cluster > Managed Networks page. If a Managed Networks rule includes nodes from different Safeguard for Privileged Sessions clusters, Safeguard for Privileged Passwords will only select the nodes from the same cluster that was assigned on the Session Settings page of the Access Request Policy tab.
IMPORTANT: Discovery, password and SSH key check and change will not work if a managed network has been configured with a subnet but is not assigned to an appliance (the appliance is blank). If the managed network does not have an assigned appliance, a message like the following displays: No appliances in network '<NameOfEmptyNetwork>' available to execute platform task request. To resolve the issue, assign at least one appliance to manage the passwords, SSH key, and/or sessions or delete the managed network entry.
Go to Managed Networks:
- web client: Navigate to Appliance Management > Cluster > Managed Networks.
The Managed Networks page displays the following information about previously defined managed networks. Initially, this page contains the properties for the Default Managed Network, which implicitly includes all networks and is served by all appliances in the cluster.
Property | Description |
---|---|
Name |
The name assigned to the managed network when it was added to SPP. |
Subnets |
A list of subnets included in the managed network. Double-click an entry in the Managed Networks grid to display details about the subnets associated with the selected managed network. If you have linked Safeguard for Privileged Sessions, the following apply:
|
Passwords Managed By |
The host name and IP address of the appliances and the MAC address assigned to manage the specified subnets. |
Sessions Managed By |
The host name and IP address of the cluster nodes. |
Description |
The descriptive text entered when defining the managed network. |
Use these toolbar buttons to define and maintain your managed networks.
Option | Description |
---|---|
New | Add a managed network. For more information, see Adding a managed network. |
Delete Selected |
Remove the selected managed network from SPP. You cannot delete the Default Managed Network. |
Refresh | Update the list of managed networks. |
Edit |
Modify the selected managed network configuration. You can not modify the Default Managed Network. |
Resolve Network text box |
Locate an IP address in a managed network's list of subnets. For more information, see Resolving IP address. |