If a client changes the route in the ID management manager while the ID registration notification from the relay managing the ID is delayed, the route shown in the information associated with the ID may not be updated. Clients for which route information was not updated can be identified by comparing their ID group files to the clients' information files. This subsection describes how to identify clients whose route information was not updated, as well as the corrective action to take.

(a) Create an ID group file

You create an ID group file to determine which of the relays that are managing ID groups are also managing clients. The ID group file is output in NDI format. The following describes how to create an ID group file in CSV format to facilitate comparison.

To create an ID group file:

1. In the Destination window of the ID management manager's remote installation manager, choose File, and then Save ID Hosts to File.
   An ID group file (.NDI format) is created.
   
2. Open the file with a text editor and replace HID=, MAC=, ID=, and, MASTER= with commas.
   Do not replace the , MASTER= in the ID name with a comma ( indicates a single-byte space character).
   
3. Save the ID group file as a CSV file.

For details about what information is output to an ID group file, see 8.3.3(2)(a) Creating an ID group file.

(b) Create a client information file

You output information about the clients managed by the ID management manager into a CSV file. Using the CSV output utility, choose the destination attribute template and output the following information.

• Information that allows the client to be identified, such as host name, IP address, and host ID
• Route
• Associated groups

For information on how to output client information files, see 9.1 Using the CSV output utility to output information to a file in the manual Administrator's Guide Volume 1.

(c) Identify clients whose route changes have not been captured

The subsection describes how to compare an ID group file to a client information file to identify those clients whose route information is not correct.

To identify clients whose route information is not correct:

1. In the ID group file, check the host ID of the relay managing the ID group associated with the clients whose route information you are checking. This gives you the host name (or IP address) of the relay managing the ID group.
2. Use an ends-with condition to compare the host name (or IP address) of the relay managing the ID group from step 1 against the route information from the information file of the clients whose route information you want to check.
   The route information of clients that does not match the ends-with condition has not been updated.
   You do not need to check those clients whose only host ID for the relay managing the ID is a hash mark (#).
   

(d) Correct the route information

Correct the route information of the clients whose route information was not updated. Use either of the following methods.

To edit and re-register the ID group file:

1. In the Destination window of the ID management manager's remote installation manager, choose File, and then Save ID Hosts to File.
   This creates an ID group file.
   
2. Open the file with a text editor and revise the host ID of the relay managing the ID of the client whose route information was not updated.
3. In the Destination window of the ID management manager's remote installation manager, choose File, and then Use File for ID Registration.
   The client is re-registered in the ID group.
   

To delete information belonging to the ID group in the relay managing the ID and re-register information from the client to the ID group:

1. In the Destination window of the ID management manager's remote installation manager, choose the client to be deleted, then choose the Edit menu and select Delete.
   The selected client will be deleted from the ID group.
   
2. Request that the client deleted from the ID group be re-registered in the ID group.

ID group registration is not canceled if the client alters the route in the ID management manager while the ID group registration cancellation notification from the relay managing the ID is delayed. If this happens, use one of the following methods resolve the problem.

• Do another ID registration cancellation from the client whose ID group registration was not canceled
  For more about cancelling registrations from IDs, see 11.2.1 Registering into an ID group in the manual Administrator's Guide Volume 1.
  
• Use the ID management manager's remote installation manager to delete the target client's ID registration information
  For more on how to delete clients registered in ID groups, see 8.3.4(3) Deleting a registered client from an ID group.
  

Notes

One way to prevent this problem is to not cancel an ID group registration immediately before changing a route. After changing a route, also check whether the ID group registration was canceled by the client has been applied.