FolderSecure Crack With Serial Number 2022 (Latest full version)

( Updated : October 23, 2021 )

🔥 DOWNLOAD LINK Links to an external site.






Abbreviation Hyper-V Full name or meaning Microsoft (R) Windows Server (R) R2 , but the same version number would be written in the program as. What about Adobe Indesign CC / / ? As there are some 3rd-party plugins for older versions. But, Indesign keeps upgrading to give better usability. Movavi Video Suite Activation Key Full Crack [Latest] like a pro— Movavi video suite Free Download video editing software. Trendy adding, he too ropes almanac recursion, tradition tilt styles, besides lets toward usual folder scope, day, period, stuff besides. Crack With Serial Number Latest · Download Rename It! - crack/serial · Rename It! alike software · User comments(5) · Your comment for Rename. From new parts for your heating and cooling system,to a complete line up for If you have your serial number parts lookup is even easier use the serial. FM Facepacks Download – DF11 Faces Megapack All 63; FMI Update 7; Editor data 15; Facepacks 1; Full Game 2; Kitpacks 2; Logopacks 5; Misc Graphics. Brand new wetting and pissing site with videos in full HD quality! (usually not my PO serial number is 81,,XXX from , and your serial number. Ufo case files of scotland (volume 1): amazing real life alien encounters - kindle edition by robinson, malcolm. Download it once and read it on your kindle.

Linux R is the registered trademark of Linus Torvalds in the U. Red Hat is a trademark or a registered trademark of Red Hat Inc. Other company and product names mentioned in this document may be the trademarks of their respective owners. This product includes software developed by the University of California, Berkeley and its contributors. Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi relaxngcc. Restrictions Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty. Material contained in this document may describe Hitachi products not available or features not available in your country. No part of this material may be reproduced in any form or by any means without permission in writing from the publisher. Issued Jan. Copyright C , Hitachi Solutions, Ltd. Changes Log information that has been output on a host subject to remote monitoring can now be collected between the time remote monitoring stopped and the time remote monitoring is restarted. A description about specifying access permissions for monitored log files was added to the description of the settings for monitoring logs on remotely monitored hosts. The procedure for the SEQ2 log file output format was changed in the description of the settings for monitoring logs on remotely monitored hosts. Additions and changes were made to the settings for the sizes of logs and event logs that can be collected per monitoring interval. Location 1. Changes were made to the method for configuring SSH communication for monitored hosts running on UNIX when remotely monitored hosts are added. Remote monitoring can now be continued even when host information is collected during remote monitoring. Because the differential distribution method was added, the description of the methods for applying the system hierarchy was changed 6 , 7 1 c , 3. Setting up Central Console Chapter 4 explains how to set up an environment for using Central Console. Read the manual appropriate for the purpose. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example: From the File menu, choose Open. Click the Cancel button. In the Enter name entry box, type your name. Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example: Write the command as follows: copy source-file target-file The following message appears: A file was not found. For example: Do not delete the configuration file. Monospace characters indicate text that the user enters without change, or text such as messages output by the system. For example: At the prompt, enter dir. Use the send command to send mail. The following message is displayed: The password is incorrect. For example: [A] means that you can specify A or nothing. In coding, an ellipsis In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example: A, B, B, Indicates a tab. Example: A means that a tab character precedes A. Conventions: Meaning of "Administrator permissions" in this manual In this manual, Administrator permissions refers to the Administrator permissions for the local PC. Provided that the user has Administrator permissions for the local PC, operations are the same whether they are performed with a local user account, a domain user account, or in an Active Directory environment. For example: Version 1. The HTML manual has the same contents as this manual. For details about the uninstallation procedure, see Uninstallation procedure for Windows. Figure 1 1: Installation and setup procedure manager 1. For details about the settings for using the communication encryption function that encrypts communication data, see 8. For details about how to design the setup details, see Part 3. A host name and IP address can be uniquely resolved. To check the system configuration, see 1. Terminate all programs. Before you start the installation, terminate all programs. Insert the distribution medium in the corresponding drive and start the installation. Follow the instructions of the installer, which starts automatically. Select the software you want to install, and then enter the following items: User information Enter this information only if you are performing a new installation. If you are prompted to restart the system, restart Windows. For details, see Notes about installing and uninstalling for Windows. For details about the backup method, see 1. To delete IM databases: 1. To disable the integrated monitoring database, execute the jcoimdef command: jcoimdef -db OFF The integrated monitoring database is disabled. To delete the integrated monitoring database, execute the jcodbunsetup command: jcodbunsetup The integrated monitoring database is deleted. Restart the machine. Terminate the programs. Before you start the uninstallation procedure, terminate all programs. In Windows, close the Services dialog box. If the Services dialog box is open in Windows, close it before you start uninstalling the product. In Windows, choose Control Panel, Programs and Features, and then select the product that you want to uninstall. Follow the instructions of the installer to perform uninstallation. No entries are required during uninstallation. Restart Windows, if requested. Delete user files. Definition files and log files that were created after installation, as well as files that might be edited by the user, are not deleted during uninstallation. Terminate running programs. Restart Windows if requested. Definition files and log files that were created after installation, as well as files that might have been edited by the user, are not deleted during uninstallation. When you install and uninstall the products, note the following: Any prerequisite products must be installed first and in the correct order. Settings in the Windows environment During installation, the information listed below is set in Windows. In the services file, the port numbers indicated in Appendix C. The port numbers are deleted during uninstallation. The Path system environment variable value that was added during installation is deleted. About changing an installation path To change an installation path, first uninstall and then install again. You must re-specify individual definitions after reinstallation. If you reinstall the program while these files remain in the system, the program might not function correctly. About downgrade installation 1. If you want to downgrade a product that has been installed, uninstall the product, and then reinstall it. The integrated monitoring database is used when Central Console is being used. For details about the functions available when the integrated monitoring database and the IM Configuration Management database are used, see 2. During system configuration or after operations have started, you can create either or both the integrated monitoring database and the IM Configuration Management database. For details, see 3. This section explains how to create an IM database Preparations for creating IM databases for Windows You must prepare a setup information file that specifies the size of the database area required in order to create an IM database and information about the database storage directory. To prepare for IM database creation: 1. For details about the setup information file, see Setup information file jimdbsetupinfo. Check the settings in the setup information file. Verify that the startup type of the Application Experience service is not disabled. If you do not plan to use the integrated monitoring database, there is no need to perform this procedure. The setup procedure differs depending on whether the IM Configuration Management database has already been set up. Apply the following procedures as appropriate depending on the case. The following are the setup procedures for the two cases. Execute the jcodbsetup command to create an integrated monitoring database. Execute the jcoimdef command to enable the integrated monitoring database. Execute the jcoimdef command to disable the IM Configuration Management service jcfmain. Execute the jcoimdef command to enable the IM Configuration Management service jcfmain. For details about the jcoimdef command, see jcoimdef in Chapter 1. For details about the jcodbsetup command, see jcodbsetup in Chapter 1. If you do not plan to use the IM Configuration Management functions, there is no need to perform this procedure. The setup procedure differs depending on whether the integrated monitoring database has already been set up. Execute the jcfdbsetup command to create an IM Configuration Management database. Execute the jcoimdef command to disable the integrated monitoring database. To enable the functions of IM Configuration Management: 1. To update IM databases: 1. Execute the jimdbupdate command to check if the IM databases have been updated. Execute the jimdbupdate command to update the IM databases: jimdbupdate -i 5. After you have executed the jimdbupdate command, execute the jimdbbackup command again to make a new backup. Specify the startup sequence control settings. The IM database is being used. For details about how to start the IM database, see 3. Specify the settings as appropriate to the host's role, as shown below. The JP1 user jp1admin is registered by default. Specify the authentication server. Specify the authentication server in Order of authentication server on the Authentication Server tab. You can set a maximum of two authentication servers primary and secondary servers. This is required at the host of the primary authentication server. To register JP1 users: 1. Register JP1 users. To set operation permissions for the JP1 users: 1. Set operation permissions for the JP1 users. These settings are required at the host of the secondary authentication server. To copy the primary authentication server settings: 1. Copy the settings files for the authentication server. These are text files. To set user mapping: 1. Register the OS user names and passwords. Set the information in Password management on the User Mapping tab. Set the JP1 user names and host names. Set the information in JP1 user on the User Mapping tab. Map JP1 users and OS users. If there are multiple users, you must set user mapping for all of them. User mapping is required even when a JP1 user name is the same as the OS user name. To execute commands by a specific OS user, register that OS user as the primary user. The data that can be collected by this tool includes memory dumps and crash dumps. You must set these dumps to be output beforehand. For details about how to set the system hierarchy when IM Configuration Management is not used, see 1. You can also use the export and import functions of IM Configuration Management to migrate a system configuration from a test environment to the operating environment or from the environment before a change to the environment after the change. The export and import functions of IM Configuration Management enable you to specify settings for managing a system hierarchy that includes virtual hosts virtualization system configuration , as well as settings for using Central Scope for monitoring. If the system hierarchy is not obtained, operation will malfunction because of mismatched configuration definition information Using IM Configuration Management - View to set the system hierarchy for Windows This subsection explains how to use IM Configuration Management - View to set the system hierarchy. This subsection explains how to set a new system hierarchy and how to edit the hierarchy of an existing system. The following provides an overview of how to set a new system hierarchy. To set a new system hierarchy: 1. Register a host that is to be added to the system hierarchy as a management target of IM Configuration Management. For details about how to register hosts and how to set information about hosts, see Registering hosts. For details about how to view information about the registered hosts, see Displaying host information. For details about how to delete hosts, see Deleting hosts. For details about how to change information about the registered hosts, see Changing the attributes of host information. Add the host registered in IM Configuration Management to the system hierarchy and set the hierarchy between managers and agents. For details about how to set a hierarchy between managers and agents, see 3. Apply the set system hierarchy to the system. For details about how to apply the set system hierarchy to the system, see 3. For details about how to check the set system hierarchy, see Displaying the system hierarchy. If you divide the system hierarchy into integrated manager and site managers, perform the above procedure for each manager. After that, use the IM Configuration Management - View that is connected to the integrated manager to perform the procedure described below to create a definition for the entire system. Synchronize the system hierarchy. Synchronize the configuration definition information between the integrated manager and site managers. For details about how to synchronize the system hierarchy, see Synchronizing the system hierarchy. To edit an existing system hierarchy: 1. The obtained configuration definitions are stored in the IM Configuration Management database. Hosts that have not been registered in IM Configuration Management are automatically registered in the database. For details, see Collecting the system hierarchy. In the Edit Host Properties window, check the registered host attributes, and edit the host names and host types as necessary. For details, see Changing the attributes of host information. In the IM Configuration Management window, collect host information. For details, see Collecting information from hosts. In the IM Configuration Management window, check the host information you have collected. Host information includes lower-level host information, basic information, product information, and service information. For details, see Displaying host information. In the IM Configuration Management window, check the system hierarchy and edit it as necessary. When you edit the system hierarchy, make sure you apply the new hierarchy to the system. For details, see Displaying the system hierarchy, Editing the system hierarchy, and 3. In the IM Configuration Management window, collect profile information. The settings that are currently used by the services of agents and the configuration files stored in the agents are collected. In the IM Configuration Management window, check the profile information and edit the configuration files as necessary. When you edit configuration files, make sure you apply the edited information to agents. In addition, perform step 6 after you apply the new configuration files and check the profile information. You can also migrate the system hierarchy IM configuration used before changes have been made to a new environment. For details about how to set the system hierarchy using the export and import functions, see 3. For details about how to set up an environment for managing and monitoring a virtualization system configuration, see 3. For details about the system hierarchy settings when IM Configuration Management is used, see 1. There are two ways to define a system hierarchy: by using the highest manager to define the entire system hierarchy in batch mode, and by dividing the system hierarchy into smaller sections that are managed by individual managers, and then defining each section. To define the system hierarchy in batch mode, specify the entire system hierarchy in the definition file. To divide the system hierarchy into multiple sections, specify in the definition file the managed hosts and managers that are under that manager. The command will update the definition information. If you divide the system hierarchy into multiple sections, perform the above procedure for each manager. After that, perform the procedure described below at the highest manager to create a definition for the entire system. To set the configuration definition information: 1. Specify the system hierarchy from the highest manager to the next highest manager in the definition file. If there is no configuration definition file, create a file that specifies only the local host name. If there is an existing file, use it as is. This will distribute the post-change configuration definition information. Changing the highest manager To change the highest manager in the system: 1. First, delete the configuration definition information at the highest manager. At the highest manager before the change, delete the configuration definition information using the procedure described in Deleting the configuration definition information for Windows. At the highest manager after the change, set the configuration definition information. In such a case, take the following actions: 1. If Event Service is not running during this reload processing, configuration definition information will be distributed, but the JP1 event destination information will not be updated. In such a case, restart Event Service. Set up an Event Service environment. Normally, the default settings can be used for operation, but in the following cases, you must customize the settings: The capacity of the event database is to be increased. Set event conversions. By default, events are forwarded according to the hierarchy definition that is specified as explained in 1. For details about how to edit the settings file, see 3. This means that you can use the manager to centrally manage Event Service definition information for each host without having to check and define the definition information at each host. When you use IM Configuration Management, you can collect and distribute the following definition information: Forwarding settings file Log file trap operation definition file Log-file trap startup definition file Event log trap operation definition file Local action definition file When you use IM Configuration Management, you can collect Event Service definition information by collecting profiles valid configuration information and configuration files on the Host List or IM Configuration page in the IM Configuration Management window. For details about how to collect profiles, see 3. For details about how to apply edited information to the configuration files, see 3. Setting up a command execution environment Execute the jcocmddef command to set up a command execution environment. We recommend that you adjust the number of commands that can be executed concurrently. To do this, execute the command as follows: Example: Set the number of commands that can be executed concurrently to 3 jcocmddef -execnum 3 2. Creating an environment variable file If you will use an environment variable file during command execution, create it. Defining host groups If necessary, define host groups groups of hosts at which a command can be executed simultaneously. Creating a command button definition file If you want to execute a command from a command button, create a command button definition file. To pass event information, set true in the inev parameter. Creating a configuration file for converting information When you pass event information for automated actions and command execution, if you want to convert specific ASCII characters in the event information to be passed to other types of characters, create a configuration file for converting information. For details about when the settings of a command execution environment are enabled or how to create definition files, see the information in the locations described below. Creation of an environment variable file See Environment variable file in Chapter 2. Host group definition See Host group definition file in Chapter 2. Creation of a command button definition file 1. Creating a command button definition file If you want to execute a client application from a command button, create a command button definition file. In addition, set client in the cmdtype parameter. About command execution environments Creation of a command button definition file See Command button definition file cmdbtn. This section describes the prerequisites and the setting and startup methods for using the source host name of Event Service on the manager in the FQDN format. To set: 1. To start services: 1. For details about how to register hosts that are to be monitored remotely in IM Configuration Management, see 3. Note You can collect the log information that is output on remotely monitored hosts while remote monitoring is stopped. Configure the remote log trap environment definition file as needed. Firewall settings Configure the firewall on a host to be remotely monitored as necessary. Note: Log information cannot be collected if the startup status of Windows Management Instrumentation service name WinMgmt providing system management information in the OS on the monitored remote host is Disabled. Users accessing a remotely monitored host must be members of the Administrators group on that host. The procedure for configuring DCOM is described below. Note that some steps in the procedure might differ depending on the OS environment on the remotely monitored host. If it does not appear, hold down the Windows logo key and press the R key to invoke Run. From the Windows Start menu, choose Run. Enter dcomcnfg. The Component Services window appears. Click Component Services and Computers to expand the tree. Choose My Computer, and then from the right-click menu, choose Properties. The My Computer Properties dialog box appears. Click the OK button. The My Computer Properties dialog box closes. Enter gpedit. The Group Policy dialog box appears. Then, expand the User Profiles node. For Do not forcefully unload the user registry at user logoff, click Enabled. Note that some steps in the procedure might differ depending on the OS on the host to be monitored remotely. This step is not needed if you have not changed the setting of Enable Distributed COM on this computer. To configure the firewall when Windows Firewall is enabled: 1. The Group Policy Object Editor dialog box appears. Click Standard Profile , and then in the right-hand pane, from the right-click menu of Windows Firewall: Allow inbound remote administration exception, choose Edit. The Windows Firewall: Allow inbound remote administration exception dialog box appears. Select the Enabled radio button in the Windows Firewall: Allow inbound remote administration exception dialog box. The Windows Firewall: Allow inbound remote administration exception dialog box closes. The following procedure describes how to check WMI connections. Note that for the user name, you need to enter the value specified in the User name box on the IM Host Account page in the System Common Settings window. If you are prompted to enter a password after a command is executed, specify the value set in the Password box on the IM Host Account page. Click the Connect button. The Connect window appears. In Namespace, User, Password, and Authority, enter the appropriate information. The following describes each item. Replace monitored-host-name with the name of the host that will actually be monitored. User Enter the name of the user who will log on to the monitored remote host. Password Enter the user's password. Authority Enter ntlmdomain:domain-name-of-monitored-host. Leave this box blank if the remote host is a work group. If connection is established successfully, the Connect dialog box closes and all buttons are enabled in the Windows Management Instrumentation Tester dialog box. If an error notification appears, check the item indicated by the error number. Causes of errors and the corresponding error numbers are given below. An error might occur if you change settings while the tool wbemtest. In that case, restart the tool and check the connection. Confirm that there is an event log whose log type is System or Application on the host to be monitored remotely, and then click the Query button. When the Query window appears, enter the next query, and then click the Apply button. If the log files on monitored hosts are in SEQ2 format, make sure that you can also read the backup files of the monitored log files. Add the desired user names in the remote communication settings in the host information file on the monitored host and grant read permissions to the users. Note that if you allow file sharing to too few users, when log file trapping starts, the upper limit for the number of users who are granted file sharing is exceeded and an error might occur. In the properties window of Access this computer from the network, add the user name specified on the IM Host Account page in the System Common Settings window. In the properties window of Access this computer from the network, add the user name specified in the remote communication settings in the host information file of the monitored host. To do so, perform the following procedure. Log on to the monitored host as an administrator. Start the Registry Editor. In the Registry Editor window, select the following key. Add the registry value. Close the Registry Editor. Restart the monitored host. For name-of-remotely-monitored-host, enter the actual name you specified. When the connection window appears, enter the user name and password for logging on to the remotely monitored host. For name-of-remotely-monitored-host and path-for-folder-shared-in- 1 , enter the actual host name and path you specified. Check whether you can access path-for-folder-shared-in- 1. SSH uses public-key cryptography for authentication. Place the public key on the monitored host Place the public key on the remotely monitored host. Specify access permissions for monitored log files If the monitored host is a UNIX host, specify access permissions for users who will be establishing SSH connections from the manager host to the monitored host. Important Do not write interactive commands such as stty, tty, tset, and script in the login script of the user who is permitted to establish SSH connections. If these commands must be written in the login script, create another user who is permitted to establish SSH connections for remote monitoring. Alternatively, change the login script of the user who is permitted to establish SSH connections so that these commands will not be executed. Log on to the remotely monitored host as a user with root privileges. Set yes for PubkeyAuthentication 1. Set the following items 1, 2. Set yes for PermitRootLogin 1. Perform this step only when you are logged on as a user with root privileges to collect information. Execute one of the following commands to restart the sshd service. The following describes the command to be executed for each OS. For details, see the documentation of the applicable OS. The monitored host can resolve the IP address of the manager host to the host name. The IP address resolved from the host name of the manager host matches the IP address of the manager host. If you are using a DNS server for name resolution and the monitored host cannot connect to the DNS server, the startup of remote-monitoring log file traps or the collection of log files might be delayed. If a delay occurs, the startup of traps or the collection of log files might time out and fail. This procedure needs to be performed only the first time that you create keys. Before you start the procedure, make sure that only the owner of the keys has the write permission for the directory above the. If anyone other than the owner has the write permission for the higher-level directory, SSH connections fail. Log on as a user who can remotely monitor the target host in an UNIX environment. Execute the ssh-keygen command. Determine the names of the file in which the private key will be stored and the directory that will hold the file. The path and the file name must not contain multibyte characters. Press the Return key twice. When you are prompted to enter the passphrase for the private key, enter nothing and press the Return key. When you are prompted again, enter nothing and press the Return key again. The following is an execution example of the ssh-keygen -t rsa command. The key fingerprint is: ax:xx:xx:xx:xx:bx:xx:xc:xx:xx:xx:xd:xd:xa:ed:xx 5. Execute the cat command to add the public key file to the authentication key file. Execute the chmod command to change the attribute of the authentication key file to The following is an execution example of the cat and chmod commands. If you change the path for the authentication key file created in step 6, check and, if necessary, revise the value of AuthorizedKeysFile. Cautionary notes Manage private keys with the utmost care. The creation of keys public key and a private key pair does not depend on any environment or tool. You can create keys in any environment using any tool. However, after you create keys, you must place the private keys and public keys in the appropriate locations. The path for the location of the private key must not contain multibyte characters. This procedure needs to be performed only the first time that keys are created. The System Common Settings window is displayed. For details about the items displayed in the System Common Settings window, see 4. To do so, perform the procedure described below. Note that this procedure needs to be performed only when keys are created on another host and that host will be monitored remotely. Log on as a user who can remotely monitor the target host. Navigate to the. If the home directory of the user who performs remote monitoring does not contain the. Set as the attribute of the directory. Execute the scp command to copy the public key file to the host to be monitored remotely. Copy the public key file created as described in 2 Initially creating keys to the monitored host. Copy the file to the. Execute the cat command to add the contents of the public key file to the authentication key file. Delete the copied public key file. In this example, the host name of the host where keys are created as described in 2 Initially creating keys is IMHost. If the monitored log files are in the SEQ2 format, the user also needs the read permission for the backup files of the monitored log files. Directory containing the monitored log files and all of its higher directories The user needs the read permission and the execute permission. If the monitored log files are in the SEQ2 format, the user also needs the read permission and the write permission for the directory containing the backup files of the monitored log files and for all of its higher directories. In addition, when you establish an SSH connection, make sure that a password and passphrase do not need to be entered. If an error occurs or you are prompted to enter a password and a passphrase, check whether the settings are specified correctly as described. Note that during remote monitoring, the following commands must be executable on the hosts that are to be monitored remotely. Make sure that the users that perform remote monitoring can execute these commands. Execute the following command and then confirm that the return code is 0. Execute the following commands and then confirm that the return code is 0. To output the standard output to stdout. To change the initial value: 1. Configure an execution environment for the remote-monitoring log file trap function and the remote-monitoring event log trap function. Execute the jbssetcnf command to apply the definition. To use the functions of Central Scope: 1. Create a Central Scope database. Specify options as needed. Enable Central Scope Service jcsmain. Execute jcoimdef -s ON. Verify that Central Scope Service is running. Make sure that jcsmain is displayed as an active process. For details about the jcsdbsetup command, see jcsdbsetup in Chapter 1. This tool enables you to collect data needed for resolving problems in batch mode. For details about the data that can be collected, see In the event of a problem, you might need to obtain a memory dump and a crash dump. This data can also be collected by using the data collection tool. Important The size of a memory dump depends on the size of the real memory. If the installed physical memory is large, the size of a memory dump will also be large. Take care to allocate sufficient disk space for collecting a memory dump. For details, see the Windows Help topic Stop error. In addition to JP1 information, error information for other application programs is also output to the crash dump. For this reason, output of a crash dump requires a fair amount of disk space. If you specify the setting to output crash dumps, take care that sufficient disk space is available. Define process restart. Set either 0 do not restart default or 1 restart. Do not change the first value separated by the vertical bars. Apply the definition information. In a cluster system, do not enable process restart in the event of abnormal process termination. Set JP1 event issuance. To issue JP1 events, change the value to dword Execute the jbssetcnf command to apply the definition information. The specified settings take effect after the restart. Open the health check definition file jcohc. If you specified a notification command, execute the jcohctest command to check the notification command's execution validity. If the operation is not valid, check and, if necessary, revise the specification. If the command does not exist at the redirection destination, the command execution might fail. About the health check function settings About the health check definition file jcohc. About the jcohctest command See jcohctest in Chapter 1. Therefore, you must set the monitoring object database to be backed up and recovered automatically when the monitoring tree is being updated. Change the settings as appropriate to your operation. To execute the Central Scope upgrade command: 1. Check the available disk capacity. To execute the jp1csverup. Execute the jp1csverup. Execute the jbssetcnf command. About the jp1csverup. If you want to continue using the automated action definition file for version or earlier as is, there is no need to perform this procedure. To update the automated action definition file: 1. Execute the following jcadefconv command to update the automated action definition file: jcadefconv -i action-definition-file-name-before-conversion -o action-definition-file-name-afterconversion 3. Rename the file specified for the -o option of the jcadefconv command to actdef. The path name including the file name of the correct location is shown below. Note that you do not need to perform this step if the file name that was specified for the -o option in step 2 is the path name including the file name shown below. About the automated action function See Chapter 5. About the jcadefconv command See jcadefconv in Chapter 1. As a result, even if you enable mapping for source hosts, the list box in the Event conditions section does not display Source host in the Action Parameter Detailed Definitions window. If you want to display Source host in the list box in the Event conditions section of the Action Parameter Detailed Definitions window, you need to add E. This function is enabled when you perform a new installation. If necessary, configure the environment definition file for event report output. For details about the environment definition file for event report output, see Environment definition file for event report output evtreport. Specify the settings that enable output of a memory dump and crash dump by referencing 1 Preparations for collecting data in the event of a failure. IM Configuration Management provides the jcfthreaddmp command for collecting a thread dump in the event of a failure in IM Configuration Management - View. For details about the jcfthreaddmp command, see jcfthreaddmp Windows only in Chapter 1. To change the settings, edit the IM - View settings file tuning. The number of connected-host log entries in the Login window Preventing the history of previously used JP1 login user names from appearing on the following item User names in the Login window Whether the Tool Launcher window can start when the Event Console window opens Whether the List of Action Results window can start when the Event Console window opens Path to start the WWW browser that is used for opening monitor windows and Tool Launcher Whether to allow copying to the clipboard 1. The setting procedure is as follows: 1. Edit the following IM-View settings file tuning. This setup is not needed if you will use the jcfview command to start IM Configuration Management - View. The name is Configuration Management. For details about the jcovcfsetup command, see jcovcfsetup Windows only in Chapter 1. To change settings, edit the operation definition file of the IM configuration management viewer jcfview. Edit the following operation definition file of the IM configuration management viewer jcfview. About customization of the operation definition file of the IM configuration management viewer: About the operation definition file of the IM configuration management viewer Refer to: Operation definition file for IM Configuration Management - View jcfview. To save HTML manuals to a computer: 1. Have ready the manual distribution medium provided as a standard item with each program product. The target data is stored in the manual distribution medium. Figure 2 1: Installation and setup procedure manager 2. The host name of the local host can be resolved with the IP address IP address other than loopback address in the connected LAN environment. Run the Hitachi Program Product Installer. Follow the instructions of the Hitachi Program Product Installer. This file contains maintenance information that is used in the event of abnormal termination of installation. Either log on as root or use the su command to change the user to root. Mount the distribution medium. The mounting method depends on the OS, hardware, and environment in use. For details about the mounting method, see the OS documentation. Start the Hitachi Program Product Installer. The directory and file names on the distribution medium might differ depending on the machine environment. Use the ls command to check the directory and file names, and then use the displayed names. Unmount the distribution medium. After you finish the installation, unmount the distribution medium. For details about how to unmount a distribution medium, see the OS documentation. In AIX 2. When you start the Hitachi Program Product Installer, the initial window appears. Figure 2 3: Example of the Hitachi Program Product Installer's initial window In Select Procedure in the initial window, enter I to display a list of software programs that can be installed. Move the cursor to the software program that you want to install, and then press the space bar to select it. After installation is completed, enter Q to return to the initial window. For details about the initial window, see Figure Example of the Hitachi Program Product Installer's initial window. In Select Procedure in the initial window, enter D to display a list of software programs that can be removed. Move the cursor to the software program that you want to remove, and then press the space bar to select it. Entering D again removes the software program. After the software program has been removed, enter Q to return to the initial window. In Select Procedure in the initial window, enter L to display a list of Hitachi products that have been installed. You must specify the language encoding in both the environment variable file and the common definitions. The language encoding in the environment variable file and common definitions must match on all local hosts. This subsection describes how to set the language encoding in the environment variable file and common definitions. The value of LANG is case sensitive. Use the jcsdbexport command to output the information stored in the monitoring object database to a local file. Use the jcsdbimport command to apply the contents of the monitoring object database output to the local file to the monitoring object database of Central Scope. To delete the integrated monitoring database, execute the jcoimdef command: jcoimdef -db OFF The integrated monitoring database is disabled. Back up user files. If necessary, back them up. Follow the instructions of the Hitachi Program Product Installer to perform uninstallation. If a process uses files, those files might remain. This file contains maintenance information that can be used in the event of abnormal termination of uninstallation. After the uninstallation has terminated normally, delete this file. Settings in the OS environment During installation, the following information is set in the OS: In the services file, the port numbers indicated in Appendix C. If you want to downgrade the product that has been installed, uninstall the product, and then reinstall it. This section explains how to create an IM database Preparations for creating IM databases for UNIX You must prepare a setup information file that specifies the size of the database area required in order to create an IM database and information about the database storage directory. Important Do not restore into an IM database obtained after the jimdbupdate command has been executed any IM database backup data that was obtained before the jimdbupdate command was executed. To specify the authentication server: 1. Register a JP1 user. Set the user mapping definition. At each host where commands are executed, edit the user mapping definition file jp1bsumap. To execute commands by a specific OS user, register that OS user as a primary user. For details about the user mapping definition file jp1bsumap. For details about how to set the system hierarchy when IM Configuration Management is not used, see 2. If the system hierarchy is not obtained, operation will malfunction because of mismatched the configuration definition information Using IM Configuration Management - View to set the system hierarchy for UNIX This subsection explains how to use IM Configuration Management - View to set the system hierarchy. For details about the system hierarchy settings when IM Configuration Management is used, see 2. This section explains how to set, delete, and change configuration definition information Setting the configuration definition information for UNIX To set the configuration definition information: 1. At the highest manager, create the configuration definition file. At the highest manager before the change, delete the configuration definition information using the procedure described in Deleting the configuration definition information for UNIX. Restart Event Service. Normally, the default settings can be used for operation, but in the following cases, customize the settings: The capacity of the event database is to be increased. By default, events are forwarded according to the hierarchy definition that is specified as explained in 2. For details about how to edit the settings files, see 3. When you use IM Configuration Management, you can collect and distribute the following definition information: Forwarding settings file Log file trap operation definition file Log-file trap startup definition file Local action definition file When you use IM Configuration Management, you can collect Event Service definition information by collecting profiles valid configuration information and configuration files on the Host List or IM Configuration page in the IM Configuration Management window. To set up a command execution environment: 1. For details about when the settings of a command execution environment are enabled or how to create definition files, see the following. Execute one of following commands to restart the sshd service. This procedure needs to be performed only the first time you create keys. Log on as a user with root privileges. Note: When you are prompted to enter the passphrase for the private key, enter nothing and press the Return key. The key fingerprint is: ax:xx:xx:xx:xx:bx:xx:xc:xx:xx:xx:xd:xd:xa:ed:xx Manage private keys with the utmost care. An execution example of the scp command, the cat command, and the chmod command is shown below. Use the created private key and execute the ssh command for the remotely monitored host. If a connection is successfully established without any prompt for an identity, SSH configuration is complete. An execution example of the ssh command for checking connections is shown below. The host name of the monitored host is TargetHost, and the name of the user performing remote monitoring is ssh-user. RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx. Last login: Mon Mar 23 from xxx. Execute the setup program. In the automatic startup and automatic stop scripts, C is set for the LANG environment variable by default. If you want to change the language for the output messages when the scripts are executed, edit the line of the LANG environment variable in the scripts. Copy the automatic startup and automatic stop scripts. Even though this message is output, automatic startup and automatic stop are not performed, because they have not been configured. Specify the automatic startup settings. If you specify the automatic startup settings before setting up the IM database and execute the jimdbupdate command, the entries must be specified in the order of hntr2mon Hitachi Network Objectplaza Trace Library HNTRLib2 , jp1base, pe01, pd01, and jp1cons. Specify the automatic stop settings. Execute the jcsdbsetup command. In the event of a problem, you might need to obtain a core dump to facilitate investigation of the cause. Output of a core dump depends on the user environment settings. Check the settings described below. To prevent this problem, we recommend that you do not change the settings of the Linux kernel parameters kernel. The data collection tool acquires files with file names beginning with core from the following default output directories. When the output directory for a core dump file is changed Make a copy of the core dump file in the default output directory. When the file name of a core dump file is changed Change the file name of the core dump file to a name beginning with core. If you specified the notification command, execute the jcohctest command to check the notification command's execution validity. If the OS shuts down while the monitoring tree is being updated or a failover occurs during cluster operation, the monitoring object database might be corrupted. To specify automatic backup and recovery settings for a monitoring object database: 1. If you change the location of the event acquisition filter to Event Base Service, the filter can be used not only for monitoring JP1 events but also for monitoring the status of automated actions and monitored objects. You can also define detailed filter conditions. Note that if you want to continue using the pre-upgrade event acquisition filter, there is no need to change the filter location. Important Once you change the location of the event acquisition filter, you can no longer restore the previous event acquisition filter. Carefully consider the location of the event acquisition filter before you execute the jcochafmode command. To change the location of the event acquisition filter: 1. Execute the jcochafmode command to change the location of the filter. To execute the jp1csverup command in the next step, you will need sufficient free space for the monitoring object database. Execute the jp1csverup command. If you want to display Source host in the list box in the Event conditions section in the Action Parameter Detailed Definitions window, you need to add E. For details, see Profile management environment 2. This section provides notes on registering hosts or changing attributes contained in host information. For details about the procedure of registering hosts into IM Configuration Management, see Registering hosts. You need to specify the names of the hosts managed by the manager. A host name can consist of only one-byte alphanumeric characters and symbols hyphen - , period. For host names, specify the host names that are registered in the hosts file or on the DNS server, or the host names defined in jp1hosts or jp1hosts2. If you perform remote monitoring, specify the host names that are registered in the hosts file or on the DNS server because the settings defined in jp1hosts or jp1hosts2 are not referenced. If you use aliases to define hosts, do not assign multiple aliases to one host. If you do, the aliases are treated as different hosts despite indicating the same host. Do not enter an IP address or an alias as a host name that is to be registered into the system hierarchy. Similarly, the format short name format or FQDN format of the host name must also match that of the event server name. The Host List page is displayed. From the menu bar, choose Edit, and then Register Host. On the Host List page, in the tree area, select and right-click Host List to display a pop-up menu. Choose Register Host. Register a new host by specifying the items that are displayed in the Register Host window. For details about the items displayed in the Register Host window, see 4. Click the OK button Registering remotely monitored hosts To register remotely monitored hosts, you must configure communication for remote connection. The required communication settings depend on the operating systems on the manager host and the monitored hosts. One is to specify communication settings common to all systems, and the other is to specify communication settings for each monitored host. If you use the method for specifying communication settings common to all systems and you specify these settings in the System Common Settings window, you can reduce the number of items that need to be specified for each monitored host in the Remote Monitoring Settings window. To register remotely monitored hosts: 1. To specify communication settings common to all systems, specify the settings described in both a and b below; to specify communication settings individually for each monitored host, specify the settings described in b below. If you are specifying communication settings for each monitored host, in the Remote Monitoring Settings window, select Individual in Setting method. If you are specifying communication settings common to all systems, in the Remote Monitoring Settings window, select Common in Setting method. For details about the items that are displayed in the Remote Monitoring Settings window, see 4. To specify communication settings for all systems, configure the settings described in a and b below. To specify communication settings for each monitored host, configure the settings described in b. If you are specifying communication settings for each monitored host, in the Remote Monitoring Settings window, select Individual for Setting method. If you are specifying communication settings for all systems, in the Remote Monitoring Settings window, select Common for Setting method. For details about the items displayed in the Remote Monitoring Settings window, see 4. Click the OK button Collecting information from hosts You can collect host information about specified hosts. Execute this processing immediately after you have registered a host or when information about a host or the installed software has been updated for a reason such as the following: The OS has been replaced The IP address has changed Software has been replaced Software was installed or uninstalled Software was upgraded Once you collect host information, the profile lists are cleared. To collect host information from the IM Configuration Management database: 1. If the chosen host has lower hosts, you can also select hosts from the Lower Host Information list that is displayed by clicking the Lower Host Information button. In this case, you can select multiple hosts at the same time. Use one of the following methods to collect host information: From the menu bar, choose Operation, then Collect Host Information. From the pop-up menu that is displayed by right-clicking, choose Collect Host Information. When a confirmation message asking whether you wish to collect information about the selected host or hosts is displayed, choose Yes. Information about the selected host or hosts is collected. If host information is collected while a remote-monitoring log file trap or remote-monitoring event log trap is running on the selected host, the host 3. If host information is to be collected but no information can be obtained from the monitored host, remote monitoring stops. Similarly, if the OS name differs from the one that had been collected previously, remote monitoring stops. In the case of multiple hosts, you can check the execution results in the Execution Results window. You can use the Host List page to check a host's status after host information has been collected. If collection of a host's information has failed, the host icon is displayed in gray in the tree area on the Host List page. To display the detailed information, click the Basic Information button in the node information display area on the Host List page Displaying host information The procedure for displaying information about the hosts that have been registered in the IM Configuration Management database is shown below. If you want to display host information other than basic information, host information must be collected in advance. For details about how to collect host information, see Collecting information from hosts. Choose Host List. If you choose Host List from the tree area, hosts are listed as lower host information in the node information display area. To view host information, do the following: To display basic information: From the tree area or the node information display area, select a host, and then click the Basic Information button. The basic information and detailed information are displayed in the node information display area. To display product information: From the tree area or the node information display area, select a host, and then click the Product Information button. The product information and detailed information are displayed in the node information display area. To display service information: From the tree area or the node information display area, select a host, and then click the Service Information button. The service information and detailed information are displayed in the node information display area Changing the attributes of host information To change the attributes of host information that has been registered into the IM Configuration Management database: 1. On the Host List page, in the tree area, select a host. If the selected host has lower hosts, you can also select a host from the Lower Host Information list that is displayed by clicking the Lower Host Information button. From the pop-up menu that is displayed by right-clicking, choose Edit Host Properties. Change host information by changing the items that are displayed in the Edit Host Properties window. For details about the items that are displayed in the Edit Host Properties window, see 4. To change the attributes of host information for remotely monitored hosts, use either of the following methods to change the communication settings for remote connection: Changing the remote monitoring settings for specific remotely monitored hosts In the Remote communication settings section, click the Setup button to display the Remote Monitoring Settings window. Changing the remote monitoring settings that are saved and managed as system common settings In the IM Configuration Management window, from the menu bar, choose Edit and then System Common Settings. The System Common Settings window appears. When you change the host name of a host in an agent configuration, the host name also changes in the system hierarchy displayed on the IM Configuration page in the IM Configuration Management window. When this occurs, the system hierarchy is displayed in gray in the tree area on the IM Configuration page. If you change the name of an actual host, change it in the IM Configuration Management database. If you change host names, collect the information for the hosts again. When you change the host name of a host in an agent configuration, apply the new agent configuration. For details about how to apply an agent configuration, see 3. Use one of the following methods to delete the selected host or hosts: From the menu bar, choose Edit, and then Delete Host. From the pop-up menu that is displayed by right-clicking, choose Delete Host. When a confirmation message asking whether you wish to delete the selected host or hosts is displayed, choose Yes. The selected host or hosts are deleted from the IM Configuration Management database. If deletion processing fails, an error message is displayed. When a confirmation message asking whether you wish to collect configuration definition information is displayed, choose Yes. The collected configuration definition information is saved in the manager where IM Configuration Management is running. If the collected configuration definition information contains a host that has not been registered into IM Configuration Management, that host is automatically registered into the IM Configuration Management database. However, host information is not collected. If the collected configuration definition information contains duplicated host names, an error message is displayed, and the collected information is not applied to the configuration definition information that is maintained by the IM Configuration Management database. If the collected configuration definition information contains duplicated host names, the collected configuration definition information is discarded, and the IM configuration tree is displayed in gray on the IM Configuration page. If the collected configuration definition information agent configuration does not match the configuration definition information stored in the IM Configuration Management database, the system hierarchy is displayed in gray in the tree area of the IM Configuration page. Clicking the Yes button deletes the configuration definition information stored in the IM Configuration Management database, and the agent configuration becomes undefined. As a result, the system hierarchy is displayed in gray in the tree area of the IM Configuration page. If you click the No button, the system hierarchy is displayed in gray in the tree area of the IM Configuration page, but the configuration definition information maintained by the IM Configuration Management database is not deleted. For an agent configuration, if the system hierarchy is displayed in gray in the tree area of the IM Configuration page, check and, if necessary, revise the configuration definition information agent configuration and then apply the agent configuration to the system. For details about how to apply the agent configuration, see 3. The IM Configuration page is displayed. Choose the Lower Host Information button. Selecting a host from the tree area and then clicking the Lower Host Information button displays in the node information display area information about the selected host's lower hosts Verifying the system hierarchy To verify whether the configuration definition information collected from all hosts that constitute the system matches the configuration definition information maintained by IM Configuration Management: 1. When a confirmation message asking whether you wish to verify the configuration definition information is displayed, choose Yes. When you execute verification of configuration definition information, the system collects configuration definition information for the selected hosts and verifies whether it matches the configuration definition information maintained by IM Configuration Management. If verification fails, a host icon indicating the error status is displayed in the tree area on the IM Configuration page in the Configuration Management window. In such cases, the host icon in the tree area of the IM Configuration page in the IM Configuration Management window indicates an undetermined configuration. Use IM Configuration Management - View to edit an agent configuration or a remote monitoring configuration. Obtain update rights. Apply the new system hierarchy to the system. Cancel update rights. See below for details. You can change an agent configuration by adding, moving, and deleting hosts. You can change a remote monitoring configuration by adding and deleting hosts. Use the following windows to edit an agent configuration or a remote monitoring configuration. Editing an agent configuration Use the Edit Agent Configuration window. For details about the Edit Agent Configuration window, see 4. For details about the Edit Remote Monitoring Configuration window, see 4. Display the editing window. From the tree area of the Edit IM Configuration window, choose the higher host under which a host is to be added. Lower Host Information displays information about the hosts already under the selected host. Host List displays information about the hosts that can be added to the selected host. Use one of the following methods to register a host: In the editing window, in the Host List section, select the host to be added and drag it to the tree area. The Select Hosts window appears. From the hosts displayed in Select host s :, select the host or hosts to be added, and then move them to the list of Selected host s :. When you have finished selecting hosts, click the OK button. In the editing window, right-click on the host to be added icon to display a pop-up menu. From the pop-up menu, choose Add Host. For details about the Select Hosts window, see 4. You cannot move hosts in a remote monitoring configuration. To move an agent host, from the menu bar, choose Edit, and then Edit Agent Configuration. The Edit Agent Configuration window appears. In the Edit Agent Configuration window, in the tree area, select the host to be moved, and use one of the following methods to move the host: Drag the host to the desired level in the tree area. From the menu bar, choose Edit, and then Cut. In the tree area, select the host under which you want to move the target host. From the menu bar, choose Edit, and then Paste. In the tree area, right-click to display a pop-up menu. From the pop-up menu, choose Cut. Right-click again to display a pop-up menu, and choose Paste. If you move a higher host, its lower hosts also move. The hosts at the destination depend on the selected hosts. In the editing window, in the tree area, select the host to be deleted, and then use one of the following methods to delete the host: In the tree area, select the host to be deleted and drag it to the Host List section. From the menu bar, choose Edit, and then Delete Host. From the pop-up menu, choose Delete Host. If you delete a higher host, its lower hosts are also deleted at the same time. As a result, all the unapplied profiles stored on the manager are deleted. Also, when you delete a host from a remote monitoring configuration and apply the new remote monitoring configuration to the system, all the remote monitoring profiles are deleted. After you delete a host from a system hierarchy, before you apply the new system hierarchy to the system, change the event transfer settings of the deleted host in the profile so that JP1 events will not be transferred. If you do not change the settings, the configuration information retained by the deleted agent remains in the profile managed by IM Configuration Management after the new system hierarchy is applied. As a result, the JP1 events generated on the deleted agent continue to be sent to the higher-level host. Use either of the following methods to stop the transfer of JP1 events from the deleted agent. Before you apply the new system hierarchy, in the event transfer configuration file in the profiles managed by IM Configuration Management, change the settings related to the transfer of JP1 events so that JP1 events will not be transferred for example, by inserting a comment. If the method for applying the system hierarchy is the batch distribution method with deleted configurations , the system hierarchy is deleted and then is applied. In the editing window, in the tree area, select the host to be replaced, and then use either of the following methods to display the Exchange Hosts dialog box: From the menu bar, choose Edit, and then Exchange Hosts. From the pop-up menu, choose Exchange Hosts. The selected host appears in the Host before the exchange box in the Exchange Hosts dialog box. In the Exchange Hosts dialog box, in the Host after the exchange box, enter the host that replaces the selected host. The host selected in step 3 is replaced by the host specified in step 4. Settings on the integrated manager host 1. From the menu bar, choose Edit, and then Edit Agent Configuration. In the tree area, select the host you want to set as a site manager. Use either of the following methods to set the host as a site manager: In the Edit Agent Configuration window, from the menu bar, choose Edit, and then Base Manager Settings. In the Edit Agent Configuration window, in the tree area, right-click to display a pop-up menu. From the popup menu, choose Base Manager Settings. Settings on the site manager host 1. In the Edit Agent Configuration window, in the tree area, select the host you want to set as a site manager. In the tree area, select the host you want to remove as a site manager. Use either of the following methods to release the settings: In the Edit Agent Configuration window, from the menu bar, choose Edit, and then Release Base Manager Settings. From the popup menu, choose Release Base Manager Settings. In the Edit Agent Configuration window, in the tree area, select the host you want to remove as a site manager. Use either of the following methods to remove the host as a site manager: In the Edit Agent Configuration window, from the menu bar, choose Edit, and then Release Base Manager Settings. When editing an agent configuration In the Edit Agent Configuration window, select the Acquire update right check box. When editing a remote monitoring configuration In the Edit Remote Monitoring Configuration window, select the Acquire update right check box. With update rights, you can now apply the new system hierarchy IM configuration to the system. Note that while you are editing a system hierarchy with the Acquire update right check box selected, other users are not able to apply their system hierarchies. The configuration definition information edited in the Edit Agent Configuration window is distributed to the manager and agents. The configuration is updated with the configuration definition information edited in the Edit Remote Monitoring Configuration window. Because remote monitoring configurations are managed by the integrated manager or site managers, the configuration definition information is not distributed to managed hosts. The result of applying the system hierarchy is displayed in a dialog box. If application fails again, all the host icons in the tree area of the IM Configuration page indicate an error. If a new remote monitoring configuration is applied but a new agent configuration is not applied, the system hierarchies are displayed in gray in the tree area of the IM Configuration page. When you apply a remote monitoring configuration, make sure that you apply the new agent configuration. When you use a site manager to manage agents or remotely managed hosts, perform the following procedure to apply an agent configuration or a remote monitoring configuration. On the site manager, open the configuration editing window. On the integrated manager, open the configuration editing window. On the integrated manager, open the IM Configuration Management window. On the site manager, open the IM Configuration Management window. If you want to change the agent configuration or the remote monitoring configuration managed by a site manager, perform the following procedure. However, this step is not necessary if you did not choose Apply Agent Configuration in step 1. If you want the site manager to apply the new IM configuration after the integrated manager applies the new IM configuration, perform the following procedure. On the site manager, execute the jevreload command. The supported methods for applying agent configurations include the batch distribution method with deleted configurations and the batch distribution method without deleted configurations. When editing an agent configuration In the Edit Agent Configuration window, clear the Acquire update right check box. When editing a remote monitoring configuration In the Edit Remote Monitoring Configuration window, clear the Acquire update right check box. Other users will now be able to apply their system hierarchies Synchronizing the system hierarchy To synchronize a system hierarchy IM configuration between the integrated manager and site managers: 1. The configuration definition information is synchronized between the integrated manager and the site managers. If no site managers are defined under the integrated manager, the system configuration definition information is not synchronized. To manage virtualization software other than KVM, one of the following virtualization environment managers must be installed on the virtualization system management host. The table after that gives the requirements for KVM. Table 3 1: Requirements for virtualization environment management software Virtualization environment management software Requirements for the manager Requirements for the virtualization system management host Requirements for the VMM host on which the guest OS is running Requirements for the guest OS vcenter The user ID and the password of the account for accessing the vcenter host to which the manager connects are registered in IM Configuration Management. The manager can communicate with the host on which vcenter is running. VMware ESX has been installed. Hitachi Compute Blade logical partitioning feature has been installed. IP addresses and host names are assigned to the guest OSs managed by Hitachi Compute Blade logical partitioning feature. Hyper-V or vcenter has been installed. The version of SCVMM matches the virtualization system management hosts that are specified as collection targets by a specific manager. HCSM manages the host whose virtualization system configuration is to be collected. If the host names of the guest OSs are changed, the host identification names defined by KVM are also redefined as the same names. For details, see 6. JP1 permission levels Use either of the following JP1 permission levels when using IM Configuration Management to manage a virtualization configuration. If the host names obtained from the virtualization configuration information differ from the host names you want to register in IM Configuration Management, use the Register Host window to register the hosts with the host names you want registered in IM Configuration Management. Use either of the following methods to display the Register Host window: In the tree area, select Host List. In the tree area, right-click Host List to display a pop-up menu and then choose Register Host. In the Register Host window, enter information in the blank boxes to register a new host. In the Host type section, select Physical host or Virtual host from the drop-down list. When you select Virtual host in the Host type section In the VMM host box, specify the name of the host on which virtualization software is installed. In the Virtual Manager Type box, specify the name of the virtualization management software that manages the host. For details about how to collect virtualization configuration information on the virtualization system management host, see Collecting virtualization system configuration information. For details about how to apply a system hierarchy to a system, see 3. Once you have applied the system hierarchy to the system, you can view the hierarchical relationships between physical and virtual hosts on the IM Configuration page in the IM Configuration Management window. This subsection describes both methods. In Windows This procedure must be performed by a user with Administrator permissions. To install a certificate in IM Configuration Management: 1. Note: If you want to install a certificate for a logical host, replace.. For certificate-file-name, specify the name of the certificate file including the path that was obtained in 3. For host-name, specify the name of the vcenter host or the VMware ESX host from which the certificate is to be obtained. Enter any password for the key store. If you install multiple certificates, enter the same password for each of them. When a message asking whether the certificate is to be trusted is displayed, enter yes. The certificate is installed in IM Configuration Management. In Windows 1. For host-name, specify the name of the vcenter host or the VMware ESX host from which the certificate you want to delete was obtained. Enter the password that was specified in 3. In UNIX 1. The default is the setting that allows only the method that uses SSL https. Use a text editor to open the proxy. In the following example, change the item in bold type according to the communication type that is to be used To allow only the method that uses SSL https , specify httpswithredirect. To allow only the method that does not use SSL http , specify httponly. Execute the following command to restart the vmware-hostd process: service mgmt-vmware restart 7 Changing the communication type for vcenter The jcfcolvmvc command enables you to communicate with vcenter using a VMware Infrastructure SDK interface in order to obtain virtualization configuration information. The virtualization configuration collection function that works for vcenter hosts via the IM Configuration Management window operates in the same way. By default, only communication using SSL https is permitted. Note, however, that the procedure might differ depending on the version of vcenter. For details, see the vcenter documentation. Log on to the vcenter host as a user with Administrator permissions. To allow both methods, specify httpandhttps. Use the command line or the Services window to restart vcenter Service. Create keys Create keys on the host on which KVM has been installed. Place the public key on the monitored host Place the public key on the host on which KVM has been installed. Important Do not use interactive commands such as stty, tty, tset, and script in the login script of the user who is permitted to establish SSH connections. If you must use these commands in the login script, create another user who is permitted to establish SSH connections for the host on which KVM has been installed. Log on to the host on which KVM has been installed as a user with root privileges. Set no for UseDNS 1, 2. Execute the following command to restart the sshd service. If you do not set these items, make sure that the host on which KVM has been installed can perform name resolution as follows. The host can resolve the IP address of the manager host to the manager host name. If a delay occurs, startup or collection might time out and fail. You only need to do this the first time that you create keys. Before you start the procedure, make sure that only the owner of the keys has write permission for the directory above the. If anyone other than the owner has write permission for the higher-level directory, SSH connections will fail. Log on to the host on which KVM has been installed as a user who can collect virtualization configuration information from KVM. Determine the name of the file in which the private key will be stored and the directory that will hold the file. The following is an example of executing the ssh-keygen -t rsa command. The following is an example of executing the cat and chmod commands. This only needs to be done the first time that keys are created. To do so, follow the procedure below. Note that this only needs to be done when keys were created on another host. If the home directory of the user who collects virtualization configuration information from KVM does not contain the. Execute the scp command to copy the public key file to the host on which KVM has been installed. An example of executing the scp, cat, and chmod commands is shown below. In this example, the host name of the host where keys are created as described in 3. Note that when virtualization configuration information from KVM is collected, the following commands must be executable on the hosts on which KVM has been installed. Make sure that the users that collect virtualization configuration information from KVM can execute these commands. If these commands cannot be executed, make sure that KVM has been installed correctly and that the command path has been set correctly. To establish SSH connections, you need to: 3. If you must use these commands in the login script, create another user who is permitted to establish SSH connections for collecting virtualization configuration information from KVM. The key fingerprint is: ax:xx:xx:xx:xx:bx:xx:xc:xx:xx:xx:xd:xd:xa:ed:xx Cautionary notes Manage private keys with the utmost care. Copy the public key file created as described in 3. Use the created private key to execute the ssh command on the host on which KVM has been installed. If the connection succeeds without any entry, the SSH setting has been completed. In the IM Configuration Management window, check whether the virtualization system management host is registered. If the virtualization system management host is not registered, register it. For details about the procedure, see 3. Use either of the following methods to collect virtualization system configuration information: To centrally collect the information, in the IM Configuration Management window, from the menu bar, choose Operation, Virtualization Configuration, and then Batch Collect Virtualization Configurations. To collect the information from a specific host, in the IM Configuration Management window, select the target host. When all of the information has been collected, the host names are added under Host List in the IM Configuration Management window. Note that virtual hosts are displayed in the sequence they are registered on the manager. Perform the following procedure to find the virtual host whose information you want to view. Open the Host List page. Click the Lower Host Information button. In the Lower Host Information section, click the item name host name, IP address, host type that can be used to identify the host whose information you want to view and sort the hosts. If the virtualization configuration information for the host has changed, perform step 2 again. Execute the jcsdbexport command to export monitoring tree information from Central Scope. The exported information is output to the configuration file for monitoring tree. Specify the following options in the jcfcolvmesx command. For details about how to obtain and install certificates, see 3. Execute the jcfexport command to export the information managed by IM Configuration Management. Execute the jcfexport command on the manager running IM Configuration Management. Execute the jcfmkhostsdata command on the manager running IM Configuration Management to create a host input information file to hold the virtualization configuration information. Specify the following options in the jcfmkhostsdata command. Overwrite the host input information file exported in step 3 with the host input information file created in step Execute the jcfimport command to import the host input information file created in step 5 to IM Configuration Management. When you execute the jcfimport command, the three types of information that IM Configuration Management holds host, system hierarchy IM configurations , and profile will be deleted. To manage profiles, you need to collect these three types of information after the import. Perform the following procedure to collect the three types of information. In the tree area, select Host List. Select all the hosts displayed in the Lower Host Information section. From the menu bar, choose Operation, and then Collect Host Information. From the menu bar, choose Operation, and then Batch Collect Profiles. The profiles are collected all at one time Using Central Scope to monitor a virtualization configuration This subsection describes how to configure a monitoring tree that allows Central Scope to monitor a virtualization configuration. A monitoring tree of a virtualization configuration is then created. Therefore, in order to create a monitoring tree of a virtualization configuration, Central Scope must provide a server-oriented monitoring tree in which monitored objects are grouped by server. If you create a monitoring tree of a virtualization configuration from a monitoring tree that is not server-oriented, you must modify the created monitoring tree. The virtualization configuration information is applied to the Central Scope monitoring tree. For details about how to collect virtualization configuration information, see Collecting virtualization system configuration information. Execute the jcfmkcsdata command to create a configuration file for monitoring tree to be updated with the information managed by IM Configuration Management. Specify the following options in the jcfmkcsdata command. Execute the jcsdbimport command to import the configuration file for monitoring tree created in step 2 to Central Scope. When you execute the jcsdbimport command, all the statuses in the monitoring tree are deleted. For details about how to enable the IM databases, see 1. Information about the JP1 users that will manage the business groups is in hand. This section covers the following topics. Creating business groups Adding hosts to business groups Deleting hosts from business groups Using Central Scope to monitor business groups Creating business groups This subsection describes how to create business groups. Business group setup consists of all or some of the following steps: Creating a business group Editing the properties of a business group Deleting a business group Adding hosts to a business group or deleting hosts from a business group Listing the hosts in a business group a Creating a business group To create a business group: 1. The Business Group page is displayed. On the Business Group page, select the Acquire update right check box. On the Business Group page, in the tree area, select and right-click the root node. From the pop-up menu, choose New. The Create Business Group window appears. A business group is created. For details about the Create Business Group window, see 4. On the Business Group page, in the tree area, select and right-click a node. From the pop-up menu, choose Edit Basic Information. The edited information for the business group is registered. From the pop-up menu, choose Delete. The selected business group and all the monitoring groups below it are deleted. For details about the IM Configuration Management window, see 4. On the Business Group page, in the tree area, select and right-click the business group node you want to add a host to or delete a host from. From the pop-up menu, choose Add or Delete Affiliated Hosts. The Add or Delete Affiliated Hosts window appears. If you want to add a host, in the Add or Delete Affiliated Hosts window, in the Host List section, select the host you want to add and click the Add button. If you want to delete a host, in the Added Hosts section, select the host you want to delete and click the Delete button. The selected host is added or deleted. For details about the Add or Delete Affiliated Hosts window, see 4. On the Business Group page, in the tree area, select the business group node whose hosts you want to list. On the Business Group page, in the node information display area, click the Affiliated Host List button. A list of hosts in the selected business group appears. If you want to display the basic information, click the Basic Information button. These subgroups are called monitoring groups. The administrator who monitors the entire system should consult the administrators who monitor business systems to create monitoring groups. Monitoring group setup consists of all or some of the following steps: Creating a monitoring group Editing the properties of a monitoring group Deleting a monitoring group Copying a monitoring group Cutting a monitoring group Pasting a monitoring group Adding hosts to a monitoring group or deleting hosts from a monitoring group Listing the hosts in a monitoring group a Creating a monitoring group To create a monitoring group: 1. On the Business Group page, in the tree area, select and right-click a business group node. In the Create Monitoring Group window, enter values in the Monitoring group name box and the Comment box. A monitoring group is created under the selected business group. If you have selected a monitoring group in the tree area, a monitoring group is created under that group. For details about the Create Monitoring Group window, see 4. The Edit Monitoring Group window appears. In the Edit Monitoring Group window, edit the values in the Monitoring group name box and the Comment box. The edited information for the monitoring group is registered. For details about the Edit Monitoring Group window, see 4. The selected monitoring group and all the monitoring groups under it are deleted. From the pop-up menu, choose Copy. The selected monitoring group and all the monitoring groups under it are copied. The selected monitoring group and all the monitoring groups under it are cut. You can paste the monitoring groups only on nodes in the same business group. To paste a monitoring group: 1. From the pop-up menu, choose Paste. The copied or cut monitoring group is pasted under the selected node. If the paste destination contains a monitoring group or a host with the same name, the Change Monitoring Group Name window appears. Change the name of the monitoring group. As a prerequisite, the hosts to be added to the monitoring group must have already been registered in the business group. On the Business Group page, in the tree area, select and right-click the monitoring group node you want to add a host to or delete a host from. On the Business Group page, in the tree area, select the monitoring group node whose hosts you want to list. When you apply a modified business group or monitoring group, the old name of the business group or monitoring group, which is set in the Central Scope definitions listed below, is replaced with a new name. Severe event definitions Event search conditions Event acquisition filters common exclusion-conditions in extended mode Event receiver filters View filters Correlation event generation definitions Automated action definitions Action result update conditions Command button definitions Severity changing definitions Display message change definitions Event-source-host mapping definitions To apply an edited business group: 1. The host information is updated to the settings displayed on the Business Group page and the latest configuration definition information takes effect. On the Business Group page, clear the Acquire update right check box. For details about how to set reference and operation restrictions, see 4. After restrictions are set, the administrators who monitor business systems can reference and operate only the business systems they manage. For details about how to add monitored hosts to a business group, see 3. For details about how to add monitored hosts to a monitoring group, see 3. For details about how to delete monitored hosts from a business group, see 3. Business groups that you want to apply to Central Scope can be applied only to a server-oriented tree. Central Scope is enabled and the data version of the monitoring object database of Central Scope is or later. Business groups have already been recorded in the IM Configuration Management database. Business group information and monitoring group information are applied to the Central Scope monitoring tree. Export business group information and monitoring group information. On the manager running IM Configuration Management, execute the jcfexport command to export the business group information and monitoring group information registered in the IM Configuration Management database. When exporting only business group information and monitoring group information Execute the jcfexport command with the -g option. When exporting all the information managed by IM Configuration Management Execute the jcfexport command with the -a option. Export the monitoring tree information of Central Scope. On the same manager, execute the jcsdbexport command to export the monitoring tree information of Central Scope. Merge the exported business group information and monitoring group information and the monitoring tree information of Central Scope. On the same manager, execute the jcfmkcsdata command to merge the exported business group information and monitoring group information and the monitoring tree information of Central Scope. When only business group information and monitoring group information are exported in step 1 Execute the jcfmkcsdata command with the -g option. When all the information managed by IM Configuration Management is exported in step 1 Execute the jcfmkcsdata command with the -a option. Import the information merged in step 3 to Central Scope. On the same manager, execute the jcsdbimport command to import the exported business group information and monitoring group information. The monitoring tree of business groups and monitoring groups is added to the Central Scope monitoring tree. You can also set profiles from the hosts added as monitored hosts, and manage the profiles. The procedure for setting profiles is different for hosts in an agent configuration and hosts in a remote monitoring configuration. The following subsections provide details Setting the profiles on hosts in an agent configuration The following profiles for information can be set in the configuration file: Profiles Information in the configuration file This is the configuration file stored at the agent. If you edit a configuration file but do not apply the modified information to the services, the valid configuration information will differ from the settings in the configuration file. The following table describes the types of profiles you can manipulate, the types of operations you can perform on profiles, and the configuration files that correspond to the profiles. Table 3 3: Types of profiles and configuration files that correspond to the profiles Operation Type of profile you can manipulate Corresponding configuration file Add, delete Log file trap information Log file trap action-definition file Log-file trap startup definition file Edit, save, temporarily apply, apply by reloading configuration files, apply by restarting log file traps Event transfer information Log file trap information Event log trap information Local action information Log file trap action-definition file Log-file trap startup definition file Note that you can start and stop only log file traps. For details about the prerequisites for setting the profiles on hosts in an agent configuration, see 3. The profile lists are placed in unregistered status at the time of any of the following operations: Initial startup of IM Configuration Management Collection of host information Reflection of system hierarchy Execution of the jcfimport command To collect profile lists: 1. On the IM Configuration page, in the tree area, select the agent from which you want to obtain a list of profiles. From the pop-up menu that is displayed by right-clicking, choose Display Profiles. Right-click to display a pop-up menu and choose Exclusive Editing Settings. This step is unnecessary if exclusive editing rights have already been obtained. From the pop-up menu that is displayed by right-clicking, choose Rebuild Profile Tree. The profile tree is rebuilt and the profile list is updated. If profile tree rebuild processing fails, an error message is displayed, together with the profile tree that existed before the rebuild processing was executed. Although you can perform operations on the profiles that existed before the rebuild processing was performed and on profiles whose information is still the same as at the agents, such operations might have adverse effects on future operations. Therefore, eliminate the cause of the error, and then perform the profile tree rebuild processing again. Collection of profile lists fails if multiple log file traps are started using the same operation definition file or using operation definition files with the same name in different directories. When you rebuild a profile tree, all the profiles stored on the manager are deleted and profile lists are collected from the agents again. If the profiles have not been applied to agents, apply them first and then rebuild the profile tree. This subsection describes the two methods. Note that profile collection cannot be performed in batch mode in the following cases: Another user has exclusive editing rights for one of the configuration files. Another user is performing batch collection of profiles. Another user is performing batch reflection of edited information in the configuration files. From the menu bar, choose Operation, then Batch Collect Profiles. When a confirmation message asking whether you wish to collect profiles in batch mode is displayed, choose Yes. Profiles are collected in batch mode and stored on the manager running IM Configuration Management. The execution result is displayed in the Execution Results window. If there is a profile whose collection has failed, its Configuration file contents in the node information display area is grayed out, and the profile status is displayed in Status. After executing batch collection of profiles, you can check agent status on the IM Configuration page in the Configuration Management window. If there is a profile whose collection has failed, a host icon indicating the error status is displayed in the tree area on the IM Configuration page. To view the detailed information, click the Basic Information button in the node information display area on the IM Configuration page. Note that profiles cannot be collected while another user has exclusive editing rights for the configuration files. On the IM Configuration page, in the tree area, select the agent from which you want to collect profiles. From the pop-up menu that is displayed by right-clicking, choose Exclusive Editing Settings. Click the Configuration File button. The Configuration File page is displayed. If you have never collected configuration files, clicking the Configuration File button automatically starts configuration file collection. On the Configuration File page, in the tree area, select a profile you want to obtain. Then use either of the following methods to collect it: From the menu bar, choose Operation, and then Collect Profiles. From the pop-up menu that is displayed by right-clicking, choose Collect Profiles. When a confirmation message asking whether you wish to collect the target profile from the agent is displayed, choose Yes. Profiles are collected and stored in the manager where IM Configuration Management is running. On the IM Configuration page, in the tree area, select the agent whose valid configuration information you want to display. Click the Valid Configuration Information button. To display configuration files: 1. On the IM Configuration page, in the tree area, select the agent whose configuration files you want to display. For details about how to edit the configuration files, see 3. On the IM Configuration page, in the tree area, select the agent whose profile you want to add to the manager. Right-click to display a pop-up menu, and choose Display Profiles. Right-click to display a pop-up menu, and choose Exclusive Editing Settings. Use either of the following methods to display the Add Profile window: From the menu bar, choose Edit, and then Add Profile. Right-click to display a pop-up menu, and choose Add Profile. Enter values in the following boxes. Log file trap name You cannot specify an existing log file trap name or a name that is the same as the log file trap action-definition file. For details, see 4. When you configure a log file trap for a cluster system, specify the same log file trap name in the Add Profile window on the physical host running as the active server and in the Add Profile window on the physical host running as the standby server. This item is mandatory. Cluster ID When you configure a log file trap for a cluster system, on the physical host running as the active server, select the Enable check box and enter a cluster ID in the ID box. On the physical host running as the standby server, in the Add Profile window, enter the same cluster ID you entered on the active server. This item is optional. The name of the added log file trap name of the log file trap appears in the tree area. For details about how to edit the configuration file for log file traps, see 3. When you add the profile of a log file trap, the log file trap name is displayed in gray in the tree area because the log file trap is not running yet. For details about how to start log file traps, see 3. You cannot delete profiles in the following case: The log file trap corresponding to the selected profile is running. If the log file trap is running, stop it. For details about how to stop log file traps, see 3. To delete a profile: 1. On the IM Configuration page, in the tree area, select the agent whose profile you want to delete from the manager. On the Configuration File page, in the tree area, select the applicable log file trap name. In the tree area, under Log File Trapping, a list of the log file trap names appears. Select the log file trap name you want to delete. Use either of the following methods to delete the log file trap name: From the menu bar, choose Edit, and then Delete Profile. Right-click to display a pop-up menu, and choose Delete Profile. When a message appears asking whether you want to delete the log file trap name, click the Yes button. The log file trap name is deleted. On the IM Configuration page, in the tree area, select the agent whose configuration file you want to edit. From the menu bar, choose Edit, and then Exclusive Editing Settings.