mirror 되거나 clone 된 이미지의 OS에 대해 discover를 할 경우...

- http://publib.boulder.ibm.com/infocenter/director/pubs/topic/com.ibm.director.discovery.helps.doc/fqm0_t_discovering_systems_mirrored_image.html?resultof=%22%44%69%73%63%6f%76%65%72%69%6e%67%22%20%22%64%69%73%63%6f%76%22%20%22%73%79%73%74%65%6d%73%22%20%22%73%79%73%74%65%6d%22%20%22%75%73%65%22%20%22%75%73%22%20%22%6d%69%72%72%6f%72%65%64%22%20%22%6d%69%72%72%6f%72%22%20%22%69%6d%61%67%65%22%20%22%69%6d%61%67%22%20

Discover를 위해서는 UID, GUID, SSH 가 모두 unique해야 함

Discovering systems that use a mirrored image

Systems that are cloned (or use a mirrored image) and managed by must be correctly configured to ensure their successful discovery.

To discover cloned systems, they must be configured in the following ways:

• All cloned systems must have a unique identifier (UID).
• Each cloned Common Agent managed system must have a globally unique identifier (GUID).
• Any cloned system that uses Secure Shell (SSH) must have a unique Secure Shell (SSH) host key.

To discover cloned systems, perform the following steps.

Note: You can also use the reset_diragent_keys command to perform these steps. See "reset_diragent_keys command" for information.

1. For the specified mirrored systems, view and compare the UID entries on the host and the mirrored system to ensure that the UID entries are unique. For Common Agent managed systems, perform a similar comparison for the Tivoli® GUID entries.

   Platform	Instructions
   AIX®, Linux	For Platform Agent managed systems, run the following command: od -t x1 /etc/ibm/director/twgagent/twgagent.uid For Common Agent managed systems, run the following command: For AIX: LANG=C;/usr/tivoli/guid/tivguid -Show For Linux: LANG=C;/opt/tivoli/guid/tivguid -Show
   IBM® i (formerly i5/OS®)	Note: Some characters are not readable. For Platform Agent managed systems, run the following command: DSPF STMF('/etc/ibm/director/twgagent/twgagent.uid') For Common Agent managed systems, run the following command: DSPF STMF('/etc/TIVGUID') Note: Alternatively, use the following command to create a spoolfile that contains the viewable TIVGUID: SBMJOB CMD(CALL PGM(QCASNATIVE/GUID) PARM('-show')) JOBD(QCPMGTDIR/QCPMGTDIR)
   Windows	For all mirrored systems, compare the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName\TWGMachineID Note: The UID is displayed in reverse byte order. For Common Agent managed systems, from the \Program Files\tivoli\guid directory, run tivguid.exe -Show.

2. For all mirrored systems, delete the UID entry that might have been duplicated.

   Platform	Instructions
   AIX, Linux	Run the following command: rm -f /etc/ibm/director/twgagent/twgagent.uid
   IBM i (formerly i5/OS)	Remove the following file: /etc/ibm/director/twgagent/twgagent.uid
   Windows	For all mirrored systems, delete the following value in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ ComputerName\ComputerName key Value: TWGMachineID For Common Agent managed systems, from the C:\Program Files\IBM\Director\agent\runtime\agent\bin\ directory, run endpoint.bat stop

3. For Agentless managed systems, proceed to step 4. For Common Agent managed systems generate a new Tivoli GUID and a new UID. ForPlatform Agent managed systems, generate a new UID:

   Platform	Instructions
   AIX, Linux	Run the following command: For AIX: /opt/ibm/director/bin/genuid For Linux: /opt/ibm/platform/bin/genuid And, for Common Agent managed systems, also run the following commands: /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop For AIX: LANG=C;/usr/tivoli/guid/tivguid -Write -New For Linux: LANG=C;/opt/tivoli/guid/tivguid -Write -New /opt/ibm/director/agent/runtime/agent/bin/endpoint.sh start
   IBM i	For Platform Agent managed systems, restart the platform agent. For Common Agent managed systems, perform the following steps: Run the following command to stop the Platform Agent: ENDTCPSVR SERVER(*CIMOM) Run the following command to stop the Common Agent: ENDTCPSVR SERVER(*HTTP) HTTPSVR(CAS) Run the following commands: SBMJOB CMD(CALL PGM(QCASNATIVE/GUID) PARM('-Remove')) JOBD(QCPMGTDIR/QCPMGTDIR) SBMJOB CMD(CALL PGM(QCASNATIVE/GUID) PARM('-Create')) JOBD(QCPMGTDIR/QCPMGTDIR) Use the following command to start the Platform Agent: STRTCPSVR SERVER(*CIMOM) Use the following command to start the Common Agent: STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS)
   Windows	For Common Agent managed systems, run the following commands: From the C:\Program Files\tivoli\guid\ directory, run tivguid.exe -Write -New From the C:\Program Files\IBM\Director\bin\ directory, run GENUID.exe For Platform Agent managed systems, from the C:\Program Files\IBM\Director\bin\ directory, runGENUID.exe

4. If the mirrored system does not use SSH, go to step 10.
5. If you must determine the SSH key, run the following command: ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub.
6. If the mirrored system uses SSH, stop ssh:

   Platform	Instructions
   AIX	Run the following command: stopsrc -s sshd
   Linux	Run one of the following commands: /etc/init.d/sshd stop service sshd stop
   IBM i	The command you must run depends on which version of the operating system you are running. For more information, see IBM Portable Utilities for i.
   Windows	Consult the documentation for the SSH client that you are using.

7. Delete the SSH host keys:

   Platform	Instructions
   AIX, Linux	Run the following commands: rm /etc/ssh/ssh_host_key rm /etc/ssh/ssh_host_rsa_key rm /etc/ssh/ssh_host_dsa_key
   IBM i	The command syntax depends on which version of the operating system you are running. For more information, see IBM Portable Utilities for i.
   Windows	Delete the following files: C:\Program Files\OpenSSH\etc\ssh_host_rsa_key C:\Program Files\OpenSSH\etc\ssh_host_dsa_key

8. If your SSH client requires that you explicitly regenerate the SSH host keys, run the commands to regenerate them.
   Note: Some SSH clients require that you run specific commands to regenerate the SSH host keys, but some regenerate the SSH host keys when you restart SSH.

   Platform	Instructions
   AIX, Linux	Run the following commands: Note: In the following commands, " represents two single quotation mark characters ('). /usr/bin/ssh-keygen -f /etc/ssh/ssh_host_key -N '' -t rsa1 /usr/bin/ssh-keygen -f /etc/ssh/ssh_host_rsa_key -N '' -t rsa /usr/bin/ssh-keygen -f /etc/ssh/ssh_host_dsa_key -N '' -t dsa
   IBM i	How you regenerate the SSH host keys depends on which version of the operating system you are running. For more information, see IBM Portable Utilities for i.
   Windows	Determine if you must manually regenerate the SSH host keys by consulting the documentation for the SSH client that you are using.

9. Restart the SSH service:

   Platform	Instructions
   AIX	Run this command: startsrc -s sshd
   Linux	Run one of the following commands: /etc/init.d/sshd start service sshd start
   IBM i	The command syntax depends on which version of the operating system you are running. For more information, see IBM Portable Utilities for i.
   Windows	Consult the documentation for the SSH client that you are using.

10. For Platform Agent managed systems and Agentless managed systems, go to the next step.

    For Common Agent managed systems, follow these steps:

    1. Stop IBMSA by running net stop ibmsa. Respond Yes to the prompt that asks to stop tier1slp.
    2. Start IBMSA by running net start ibmsa.
    3. Start Tier1slp by running net start tier1slp.
    4. Start Common Agent Services by running endpoint.bat start, located in this directory:<install_directory>\IBM\Director\agent\runtime\agent\bin\endpoint.bat start.
11. Run system discovery to discover the cloned system:
    1. In the IBM Systems Director Web interface, click Inventory > System Discovery.
    2. Specify either the IP address or the host name of the cloned system, then click Discover Now.
12. If the endpoint was incorrectly mirrored previously, other systems must reauthenticate to the newly mirrored system and any other endpoints that might have been merged with it.

Parent topic: Discovering systems with system discovery

Related concepts:

Discovery protocols

Related reference:

reset_diragent_keys command