Multi-Domain Management includes the following item in the NETWORK Configuration.
The ROUTE-TO statement of the NETWORK Configuration enables routing to a Management Server using a route metric. This provides an alternative mechanism for defining the Management hierarchy, similar to the MANAGED-NODES statement.
This must be a valid Prognosis node name.
ie. It must start with a leading slash (\) and can only contain a node name as shown in any of the Server navigation panels in either the Web Application or Windows Client.
IP Addresses are not valid here.
|[: route metric]|
The route metric is used to provide an optional cost of the network path. This is used when multiple routes are available, so the best one can be selected.
The input range is 1 (best) to 15 (worst) with a default value of 1.
Using this statement, multiple routes can be added to the server, there can be one or more ROUTE-TO statements added in the Configuration.
Each ROUTE-TO statement can have one or more node names as parameters, and they must be comma-separated as shown in the syntax above.
|Indicates a managed to managing node physical connection with routing enabled.|
|Indicates a managed to managing node physical connection without routing enabled.|
The ROUTE-TO token does not establish a connection. It will be effective when the connection from or to a Management Server is established.
No routing is supported on HPE NonStop EXPAND connections, such as the NSK-MANAGING-NODES statements in the NETWORK Configuration.
Routing only takes place from managed node to managing node. Hence, using the ROUTE-TO token, indicating an auto-discovered node, will have no effect. However, a node that has been discovered via auto-discovery may be routed to another non-auto-discovered node by the invocation of a MANAGED-NODE connection from the non-auto-discovered node.
A maximum of 7 routers on a path are supported, the 8th router will ignore the received message.
Routing may be dynamically enabled or disabled by restarting the NETWORK Configuration.
Be careful not to configure loops in the managed nodes set up. This will cause the late discovery of a node disconnection.