Abstract: A packet communications network includes a route management system in which routes can be remotely changed by using a simple set command to set a data value in the originating or terminating node of the route. Storage tables in the originating and destination nodes record the route changes and administrative data concerning the route. This administrative data can be retrieved from the originating node by simple get or get-next commands. The administrative data can include the specific specification of the route in links, the time of creation of the route, the route replaced and the reason for initiating the change in route. Together these capabilities permit centralized management of route changes in the entire network from a single manager node, and using only simple set, get and get-next command structures.

Abstract: A packet communications network includes a route management system in which routes can be remotely changed by using a simple set command to set a data value in the originating or terminating node of the route. Storage tables in the originating and destination nodes record the route changes and administrative data concerning the route. This administrative data can be retrieved from the originating node by simple get or get-next commands. The administrative data can include the specific specification of the route in links, the time of creation of the route, the route replaced and the reason for initiating the change in route. Together these capabilities permit centralized management of route changes in the entire network from a single manager node, and using only simple set, get and get-next command structures.

Abstract: A packet communications network includes a centrally controlled route testing system in which each node includes test results tables containing the results of all path tests originated at that node. A centralized route management facility initiates a path test originating at any node by remotely altering a trigger value in a trigger data object at that node. A general results table contains general test results for an entire path between the local node and a remote node while a detailed test results table contains detailed, hop-by-hop test results for each transmission leg of a multi-leg path. The general results table contains a name trigger field for identifying a point-to-point path to be tested, and a connection trigger field for identifying a link-by-link path to be tested.