HPE Intelligent Management Center SQL Server 2008 Installation Guide
HPE Intelligent Management Center SQL Server 2008 is a powerful tool that can help you manage your SQL Server environment. With IMC SQL Server 2008, you can:
- Monitor the performance of your SQL Server instances
- Identify and resolve performance issues
- Manage your SQL Server databases
- Secure your SQL Server environment
- Automate your SQL Server administration tasks
IMC SQL Server 2008 is a valuable tool for any organization that uses SQL Server.
광고
광고
HPE Intelligent Management Center
SQL Server 2008
Installation and Configuration Guide
Abstract
This document describes configuration during and after database installation when IMC is used with the Microsoft SQL
Server. This document is applicable to the SQL Server 2008 SP3 Enterprise edition and slightly different from other editions of SQL Server 2008. This document is intended for use by network engineers and system administrators responsible for installing network software and components.
Part number: 5200-2701
Software version: IMC PLAT 7.3 (E0501)
© Copyright 2015, 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Document ation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Contents
SQL Server 2008 in IMC ··································································· 1
Installing SQL Server 2008 ································································ 2
Registering the SQL Server license ···················································· 17
Installing the SQL Server client ························································· 19
Configuring SQL Server 2008 ··························································· 25
Uninstalling SQL Server 2008 ··························································· 36
FAQ ···························································································· 37
About HPE IMC documents ······························································ 47
Document conventions ···································································· 48
Support and other resources····························································· 49
i
SQL Server 2008 in IMC
Before installing IMC, install the SQL Server on a database server used for storing IMC data, or install it on the server on which you plan to install IMC.
This document provides installation and configuration procedures for the Microsoft SQL Server 2008.
For more information about using the database for IMC, see HPE IMC deployment guides.
If you plan to install the database on a separate database server, follow these guidelines:
Before installing IMC, install a SQL Server client on the same server as IMC. The client version must match the version of the SQL Server database.
On the database server, create a file folder for storing IMC data. You must specify the local path
to the folder during IMC installation, as shown in Figure 1 .
Figure 1 Checking installation parameters dialog box during IMC installation
NOTE:
Use Microsoft SQL Server licensed installation software for the Microsoft SQL Server. Localized software or other unauthorized editions might cause a failure in database installation and operation.
1
Installing SQL Server 2008
1. Run the installation program.
The SQL Server Installation Center
wizard opens, as shown in Figure 2 .
Figure 2 SQL Server Installation Center wizard
2. Select Installation in the navigation tree, and then select New SQL Server stand-alone installation or add features to an existing installation to enter the Setup Support Rules
2
Figure 3 Setup Support Rules page
3. Click OK to enter the Product Key
Figure 4 Product Key page
3
4. Enter the product key and click Next .
The License Terms
page opens, as shown in Figure 5 .
Figure 5 License Terms page
5. Select I accept the license terms , and click Next .
The Setup Support Files
page opens, as shown in Figure 6 .
Figure 6 Setup Support Files page
4
6. Click Install to begin installing the setup support files.
The Setup Support Files
page displays the installation progress, as shown in Figure 7 .
Figure 7 Setup Support Files installation progress
When the installation is complete, the Setup Support Rules
page opens, as shown in Figure 8 .
Figure 8 Setup Support Rules page
5
7. Click Next .
The Feature Selection
page opens, as shown in Figure 9 .
Figure 9 Feature Selection page
8. Select the appropriate features and click Next .
The Instance Configuration
page opens, as shown in Figure 10 .
Figure 10 Instance Configuration page
6
9. Install a default instance or a named instance of the SQL Server.
To install the default instance, select Default instance and specify an instance ID. The default instance ID is MSSQLSERVER .
To install a name instance, select Named Instance and specify an instance ID. You are required to provide the instance name during IMC installation.
When installing the SQL Server 2008 Express edition, install the default instance as a best practice. If you have installed a named instance, you must start the SQL Server Browser
service for IMC to connect to the database. For more information, see " Starting the SQL
In this example, select Default instance and use the default instance ID MSSQLSERVER .
10. Click Next .
The Disk Space Requirements
page opens, as shown in Figure 11 .
The system calculates the required disk space for the selected features, and then checks and displays the disk usage results.
Figure 11 Disk Space Requirements page
11. Click Next .
The Server Configuration
page opens, shown in Figure 12 .
7
Figure 12 Server Configuration page
12. If you selected Named instance
for the SQL Server in Figure 10 , set
Startup Type for the SQL
Server Browser service to Automatic .
13. Click Use the same account for all SQL Server services .
A dialog box opens, as shown in Figure 13 .
Figure 13 Use the same account for all SQL Server 2008 services dialog box
14. Select NT AUTHORITY\SYSTEM as the login account for all SQL Server services, and then click OK .
Verify that NT AUTHORITY\SYSTEM is added to the Account Name list on the Service
Accounts
8
Figure 14 Server Configuration page
15. Click the Collation
Figure 15 Collation tab
9
16. Use the default collation settings, or modify the settings to meet specific language requirements, and then click Next .
The Database Engine Configuration
page opens, as shown in Figure 16 .
Figure 16 Database Engine Configuration page
17. Under Authentication Mode , select Mixed Mode , set the password for user sa , and add a
SQL Server administrator, as shown in Figure 17 .
SQL Server 2008 has password complexity requirements. For more information, see the
SQL Server 2008 online help.
For IMC to correctly identify the sa logon password during installation, make sure the password does not contain any of the following characters:
Left angle bracket (<)
Right angle bracket (>)
Vertical bar (|)
Tab (\t)
If the password of the sa user must contain the previous characters, create a superuser with sa user privileges before the IMC installation. Make sure the password of the superuser does not contain any of the previous characters. For information about creating a database superuser,
10
Figure 17 Specifying SQL Server administrators
18. Use the default settings on the Data Directories
Figure 18 Data Directories tab
11
19. Use the default settings on the FILESTREAM
Figure 19 FILESTREAM tab
20. Click Next .
The Error and Usage Reporting
page opens, shown in Figure 20 .
Figure 20 Error and Usage Reporting page
12
21. Use the default settings and click Next .
The Installation Rules
page opens, shown in Figure 21 .
Figure 21 Installation Rules page
22. Click Next .
The Ready to Install
page displays a tree view of the installation options, as shown in Figure
13
Figure 22 Ready to Install page
23. Click Install .
The Installation Progress
page displays the installation progress, as shown in Figure 23 .
Figure 23 Installation Progress page
displays that the setup operation is complete.
14
Figure 24 Completing setup process
24. When the installation is complete, click Next .
The Complete
page opens, as shown in Figure 25 .
Figure 25 Complete page
15
25. Click Close .
26. Restart the operating system.
16
Registering the SQL Server license
The SQL Server supports the following license registration modes:
Per User licensing —Used to register the SQL Server 2008 Developer and Parallel Data
Warehouse.
Per Processor licensing —Used to register the SQL Server Developer and Parallel Data
Warehouse. The number of Per Processor licenses is determined by the number of processors on a SQL server. You must buy a Per Processor license for each processor on a server on which the SQL server component is installed. With Per Processor licensing, the number of SQL servers and IMC servers is not relevant. Per Processor licensing is applicable to networks that
contain several SQL servers and IMC servers. Figure 26 displays an example of Per Processor
licensing for SQL Server 2008 R2.
NOTE:
The number of Per Processor licenses is irrelevant to the number of kernels in a processor.
Figure 26 Per Processor licensing
Server/CAL licensing —The number of Server/CAL licenses is determined by the number of
SQL servers and IMC servers. You must buy a server license for each SQL server and a CAL license for each IMC server. Server/CAL licensing is applicable to networks that contain few
SQL servers and IMC servers. Figure 27
displays an example of Server/CAL licensing for SQL
Server 2008 R2.
17
Figure 27 Server/CAL licensing
Before choosing a license registration mode, determine the IMC deployment mode:
If IMC is deployed in centralized mode, buy a CAL license for the IMC server only
If IMC is deployed in distributed mode, buy a CAL license for each IMC server that must access the SQL Server.
For more information about SQL Server license registration, see the related Microsoft documentation.
NOTE:
The license registration modes apply to the Standard and Enterprise editions of SQL Server
2005/2008/2008 R2/2012. You do not need to buy a license for other editions such as the Express edition.
18
Installing the SQL Server client
Installation procedure
1. Run the SQL Server 2008 installation program.
2. On the Feature Selection page, select the features Management Tools - Basic and SQL
Client Connectivity SDK
For information about displaying the Feature Selection
page, see " Installing SQL Server
Figure 28 Feature Selection page
3. Click Next .
The Disk Space Requirements
page opens, as shown in Figure 29 .
19
Figure 29 Disk Space Requirements page
4. Click Next .
The Error and Usage Reporting
page opens, as shown in Figure 30 .
Figure 30 Error and Usage Reporting page
20
5. Use the default settings and click Next .
The Installation Rules
Figure 31 Installation Rules page
6. Click Next .
The Ready to Install
page opens, as shown in Figure 32 .
21
Figure 32 Ready to Install page
7. Click Install .
The Installation Progress
page opens, as shown in Figure 33 .
Figure 33 Installation Progress page
22
When the installation is complete, the page displays the following message: Setup process complete
Figure 34 Setup process complete
8. Click Next .
The Complete
page opens, as shown in Figure 35 .
Figure 35 Complete page
23
9. Click Close .
Testing connectivity
To test the connectivity between the SQL Server client and the SQL Server database:
1. Select Run from the Start menu, and then enter cmd in the Run dialog box.
2. In the CMD window, enter one of the following commands:
For the default instance: osql –h172.8.9.63 –Usa –PiMC123
For a named instance: osql –h172.8.9.63\instancename –Usa –PiMC123
In these commands, 172.8.9.63
is the IP address of the SQL Server database, sa and iMC123 are the username and password of the default superuser, and instancename represents the named instance.
If the SQL command prompt is displayed, you have connected to the SQL Server database, as
Figure 36 Testing connectivity
24
Configuring SQL Server 2008
The following information describes the steps and procedures to configure the SQL Server database.
Configuring TCP/IP properties
1. Select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager
Figure 37 Starting SQL Server Configuration Manager
The SQL Server Configuration Manager
opens, as shown in Figure 38 .
Figure 38 SQL Server Configuration Manager
2. From the navigation tree, select SQL Server Network Configuration > Protocols for
MSSQLSERVER .
3. Right-click TCP/IP and select Properties from the shortcut menu.
The TCP/IP Properties
dialog box opens, as shown in Figure 39 .
25
Figure 39 TCP/IP Properties dialog box
4. On the Protocol tab, make sure Yes is selected for Listen All .
5. Click the IP Addresses tab, select Yes for the Enabled option of each IP address, and set TCP
Port to 1433
Figure 40 IP addresses tab
6. Click OK .
The system displays a message that indicats the database service must be restarted to validate the configuration.
7. Click OK .
26
8. Restart the SQL Server service to validate the configuration. For more information, see
" Restarting the SQL Server service ."
NOTE:
When Yes is selected for Listen All on the Protocol tab, the SQL Server automatically updates
IP address settings after an IP address is changed. If No is selected, you must manually update
IP addresses.
You can enable the Named Pipes property in the same way.
In distributed deployment, make sure you configure all database servers to use the same listening port.
Modifying the maximum server memory for the
SQL Server
To ensure optimum performance, the SQL Server is preemptive and uses a default maximum server memory setting of 2147483647 MB. When IMC and the SQL Server are installed on the same server, you must reduce the maximum server memory for the SQL Server. As a best practice, set the maximum server memory to half the server's physical memory.
To modify the maximum server memory for the SQL Server:
1. Select Start > All programs > Microsoft SQL Server 2008 > SQL Server Management
Studio .
Figure 41 Database login dialog box
2. Select SQL Server Authentication from the Authentication list.
3. Enter superuser username sa in the Login field, enter the password, and click Connect .
The Microsoft SQL Server Management Studio
page opens, as shown in Figure 44 .
27
Figure 42 Microsoft SQL Server Management Studio page
4. Right-click the server name and select Properties from the shortcut menu.
The server properties page opens.
5. Select Memory in the navigation tree, set the maximum server memory to half the server's physical memory, and click OK . This example uses 2048 MB.
Figure 43 Setting memory options for SQL Server
6. Restart the operating system to validate the configuration.
28
Starting the SQL Server Browser service
To enable IMC to connect to a named instance of SQL Server 2008 Express, you must start the SQL
Server Browser service after the SQL Server installation is complete.
If you set Startup Type for the SQL Server Browser service to Automatic during the SQL Server installation process, you do not need to start the SQL Server Browser service after the installation is complete.
To start the SQL Server Browser service:
1. Select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager .
Figure 44 Starting SQL Server Configuration Manager
2. Select SQL Server Services in the navigation tree, right-click SQL Server Browser on the main pane, and then select Properties from the shortcut menu.
Figure 45 Launching the SQL Server Browser Properties dialog box
3. Click the Service tab, and then select Automatic for Start Mode .
29
Figure 46 Setting the start mode of the SQL Server Browser service
4. Click OK .
The dialog box closes.
5. Right-click SQL Server Browser and then select Start from the shortcut menu.
Figure 47 Starting the SQL Server Browser service
Configuring the logon account used by the SQL
Server service
When you specify a superuser for IMC to use a remote SQL Server database, you must have write permissions to all the disks on the database server. To ensure that, you must configure the SQL
Server service to start up using the built-in local system account.
To configure the logon account used by the SQL Server service:
30
1. Select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager .
2. In the navigation tree, select SQL Server Services .
The main pane displays the services installed by the SQL Server, as shown in Figure 48 .
Figure 48 Services installed by SQL Server
3. Verify that the value of the Log On As column of the SQL Server service is Local System .
If the value is not Local System , modify the Log on as property for the service.: a. Double-click the SQL Server service.
The SQL Server Properties dialog box opens. b. Select Built-in account , and then select Local System
from the list, as shown in Figure 49 .
c. Click OK .
31
Figure 49 Log On tab
4. Restart the SQL Server service to validate the configuration.
Restarting the SQL Server service
1. Select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager .
2. In the navigation tree, select SQL Server Services .
3. Select SQL Server (MSSQLSERVER) on the main pane.
4. Click the Restart service icon
on the toolbar, as shown in Figure 50 .
Figure 50 Restarting the SQL Server Service
32
Creating a superuser
The SQL Server database has a default superuser named sa . To specify another user for database access during IMC installation, first create a login user and grant the administrator privilege to that user on SQL Server.
To create a superuser:
1. Select Start > All programs > Microsoft SQL Server 2008 > SQL Server Management
Studio .
The database login page opens, as shown in Figure 51 .
Figure 51 Login page
2. Select SQL Server Authentication from the Authentication list, select a login username, enter the password, and click Connect .
The Microsoft SQL Server Management Studio page opens.
3. Expand the Security node in the navigation tree, right-click Logins , and select New Login
from the shortcut menu, as shown in Figure 52 .
33
Figure 52 Microsoft SQL Server Management Studio page
The page for adding a login user opens, as shown in Figure 53 .
Figure 53 Adding a login user
34
4. On the General page, enter the login name, click SQL Server authentication , set the password, and clear User must change password at next login .
For IMC to correctly identify the password, make sure the password does not contain any of the following characters:
Left angle bracket (<)
Right angle bracket (>)
Vertical bar (|)
Tab (\t)
5. In the navigation tree, select Server Roles .
Figure 54 Setting server roles
6. Select sysadmin and click OK .
The user is granted database administrator privilege and is displayed under the Security >
Logins node in the navigation tree of Microsoft SQL Server Management Studio .
35
Uninstalling SQL Server 2008
Uninstall SQL Server 2008 using the Remove function on the Control Panel > Add or Remove
Programs page.
The setup.exe
process might not respond because of operating system configuration problems. To resolve the issue, click Change/Remove for SQL Server 2008 on the control panel, as shown in
Figure 55 Uninstalling SQL Server 2008 with the Change function
36
FAQ
The default instance of the database is used by another application. How do I install the database using a named instance?
The installation procedure for using a named instance is similar to the installation procedure for using the default instance. The following information describes only the differences.
1. After the Setup Support Rules check is complete, click Next .
The Installation Type
page opens, as shown in Figure 56 .
Figure 56 Installation Type page
2. Select New installation or add shared features and click Next .
3. Enter the product key, accept the license terms, and select the setup role.
The Feature Selection page opens.
37
Figure 57 Feature Selection page
4.
Select the features shown in Figure 57 and click
Next .
The Instance Configuration
page opens, as shown in Figure 58 .
Figure 58 Instance Configuration page
38
5. Select Named instance and enter an instance name, set the Instance root directory , and click Next .
The Server Configuration page opens.
Figure 59 Server Configuration page
6.
Configure the account names for the SQL Server services shown in Figure 59 , and then click
Next .
The Database Engine Configuration
page opens, as shown in Figure 60 .
39
Figure 60 Database Engine Configuration page
7. Under Authentication Mode , select Mixed Mode , and then enter the user sa password. Make sure the password does not contain any of the following characters:
Left angle bracket (<)
Right angle bracket (>)
Vertical bar (|)
Tab (\t)
Use the default settings on the Data Directions and FILESTREAM tabs. The next setup steps are the same as those for the default instance.
Does changing the computer name affect the database? How do I restore the database?
Changing the name of a computer running SQL Server might cause database operations to fail.
Perform the following steps to update the computer name saved in the database. In this example, the old computer name is SERVER_1 , and the new computer name is SERVER_2 .
1. Open the CMD window and execute the following scripts (the login username is sa , and the password is iMCpass ): osql -Usa -PiMCpass select @@SERVERNAME go
The old computer name SERVER_1 is displayed on the interface.
2. Execute the following commands to modify the computer name saved in the database: sp_dropserver @server=‘SERVER_1’, @droplogins=NULL go sp_addserver @server=‘SERVER_2’, @local='local', @duplicate_ok= 'duplicate_OK' go exit
The old computer name SERVER_1 is deleted, and the new computer name SERVER_2 is added.
40
3. Restart the SQL Server service in the Windows Service Manager to restore the database.
During IMC installation, the following message is displayed: MS SQLServer is not Installed
Correctly, MSSOLSERVER Service Does not Exist. How do I resolve the issue?
The MSSQLSERVER string is the default instance name of the Microsoft SQL Server. This message indicates that you have selected the default instance, but the instance does not exist. If you do not select the default instance but specify the instance name ABC, MSSQL$ABC is displayed.
To resolve the issue, check the default instance name in the SQL Server Configuration Manager, and specify the correct instance name during IMC installation.
41
During IMC installation, the following message is displayed: Database Service
MSSQLSERVER Is not Configured to Be Started with Local System. How do I resolve the issue?
To create the database file for IMC, the MSSQLSERVER service must start with the local system and must have write privileges to any local disk. Otherwise, IMC cannot be installed.
To resolve the issue:
1. Select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager
Figure 61 Starting SQL Server Configuration Manager
2. In the SQL Server Configuration Manager, right-click SQL Server (MSSQLSERVER) and select Properties
Figure 62 SQL Server Configuration Manager
3. In the Properties dialog box, select Built-in account and then select Local System from the
42
Figure 63 Properties dialog box
4. Click OK .
The dialog box closes.
5. Restart the SQL Server service to validate the configuration.
During IMC installation, the following message is displayed: The ADO1.5 Component Is not
Found in Current System. How do I resolve the issue?
IMC uses ADO 1.5 to connect the database. ADO 1.5 is provided by the operating system.
The message indicates that ADO 1.5 is corrupted. To resolve the issue, re-install ADO on the host.
During IMC installation, the following message is displayed: Provider Cannot Be Found. How do I resolve the issue?
This message indicates that MDAC is not installed on the server, or that the MDAC installation is corrupted. MDAC corruption typically occurs when application programs attempt to install a partial version of MDAC.
To resolve the issue, download the installation program mdac_typ.exe
from the Microsoft website, and then reinstall MDAC. If MDAC installation fails, perform the following steps:
1. In Windows Explorer, open the C:\WINDOWS\inf folder. (This folder might be hidden.)
2. Right-click the mdac.inf
file and select Install .
You can select files from the Service Pack CD or the current operating system.
To select files from the Service Pack CD, locate the i386 directory on the CD drive. For example, if the CD drive is D:, select the directory D:\i386 .
To select files from the current operating system, click Browse , select a file, and then click
Retry .
The following files must be located during installation:
43
File name: adcjavas.inc
Location: C:\Program Files\Common Files\System\msadc
File name: adojavas.inc
Location: C:\Program Files\Common Files\System\ado
File name: msdadc.dll
Location: C:\Program Files\Common Files\System\ole db
File name: dao360.dll
Location: C:\Program Files\Common Files\Microsoft shared\dao
File name: handler.reg
Location: C:\Program Files\Common Files\System\msadc
File name: oledbjvs.inc
Location: C:\Program Files\Common Files\System\ole db
File name: MDACRdMe.htm
Location: If you cannot locate this file, change the name of the file MDACReadme.htm
to MDACRdMe.htm
.
3. When the installation is complete, reboot the operating system.
NOTE:
The MDAC installation is successful if no error message is displayed.
4. If the problem persists, use the MDAC Component Checker to identify MDAC installation problems: a. Download a free MDAC Component Checker cc_pkg.exe
from the Microsoft website. b. Decompress the file to the C:\ComponentChecker directory. c. In the Component Checker dialog box, select the first option, and then click OK .
Figure 64 Component Checker dialog box
After performing the analysis, mismatch information is displayed under File Details . This information indicates potential problems with the MDAC installation.
44
Figure 65 Mismatch information under File Details d. Click MISMATCH and view the files in the main pane. These file versions are different from the MDAC version. The Mismatch Field column displays expected file versions. The File
Version column displays actual file versions.
5. If the version mismatch information cannot be resolved through MDAC installation, copy files to the corresponding directories. a. Locate the mdacxpak.cab
file from the depressed file MDAC_TYPE.exe
and use WinZip to decompress the mdacxpak.cab
file. The file contains most of the important MDAC files. b. Copy the depressed files to corresponding paths displayed in MISMATCH . c. Reboot the operating system.
6. If you cannot resolve the issue, reinstall the operating system and databases, or contact
Hewlett Packard Enterprise Support.
During IMC installation, the following message is displayed: Failed to run bcp.exe, Database tools not installed or Windows not restarted after MS SQL Server installed. How do I resolve the issue?
For IMC to access a remote database server using the bcp.exe
tool, make sure the Client Tools
Connectivity feature is installed on the IMC server.
To install the feature:
1. Run the SQL Server 2008 R2 installation program.
2. Select Client Tools Connectivity on the Feature Selection
45
Figure 66 Feature Selection page
3. Restart the operating system to make the client software bcp.exe
take effect after the Client
Tools Connectivity feature is installed.
How can I update database passwords for IMC?
After the database password of an IMC component is changed using the database management tool, execute pwdmgr.bat
to update the password in the file server-addr.xml
on the IMC server. The file is located in directory \common\conf in the IMC installation path. It stores database passwords of all
IMC components in ciphertext.
The following example uses 192.168.20.107 as the IP address of the database. The dbpassword string represents the new database password of the imc_config user. The config_db string represents the database name. The database IP address and name can be retrieved from the file server-addr.xml
.
Figure 67 Updating database passwords for IMC
If IMC is deployed in distributed mode, you must update the database password on every IMC server
46
About HPE IMC documents
The following are the documents available for HPE IMC:
Documents
Hardware specifications and installation
Purposes
HP IMC Getting Started Guide
HP IMC Installation Guide
HP IMC Probe Installation Guide
Quickly guides you through the IMC main features and troubleshooting common problems.
Provides a complete guide to IMC platform and component installation and deployment.
Provides a complete guide to IMC Probe installation and deployment.
SQL Server 2008 Installation and Configuration Guide
Guides you through installing SQL Server 2008 for
IMC.
SQL Server 2008 R2 Installation and Configuration
Guide
Guides you through installing SQL Server 2008 R2 for IMC.
SQL Server 2012 Installation and Configuration Guide
Guides you through installing SQL Server 2012 for
IMC.
SQL Server 2014 Installation and Configuration Guide
Guides you through installing SQL Server 2014 for
IMC.
Oracle 11g Installation and Configuration Guide(for
Linux)
Oracle 11g R2 Installation and Configuration
Guide(for Linux)
Guides you through installing Oracle 11g on Linux for IMC.
Guides you through installing Oracle 11g R2 on
Linux for IMC.
Oracle 12c Installation and Configuration Guide(for
Linux)
MySQL 5.5 Installation and Configuration Guide (for
Linux)
MySQL 5.5 Installation and Configuration Guide (for
Windows)
MySQL 5.6 Installation and Configuration Guide (for
Linux)
MySQL 5.6 Installation and Configuration Guide (for
Windows)
Red Hat Enterprise Linux 6.4 Installation Guide
Software configuration
Guides you through installing Oracle 12c on Linux for IMC.
Guides you through installing MySQL 5.5 on Linux for IMC.
Guides you through installing MySQL 5.5 on
Windows for IMC.
Guides you through installing MySQL 5.6 on Linux for IMC.
Guides you through installing MySQL 5.6 on
Windows for IMC.
Guides you through installing Red Hat Enterprise
Linux 6.1 for IMC
HP IMC Base Platform Administrator Guide
Online Help
Operations and maintenance
Readme
Describes operation procedures on the IMC base platform.
Helps you properly use IMC.
Provides most recent IMC release information.
47
Document conventions
This section describes the conventions used in the documentation.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
Command conventions
Convention
Boldface
Italic
#
GUI conventions
Description
Bold text represents commands and keywords that you enter literally as shown.
Italic text represents arguments that you replace with actual values.
A line that starts with a pound (#) sign is comments.
Convention
Boldface
Description
Window names, button names, field names, and menu items are in Boldface. For example, the New User window opens; click OK .
Multi-level menus are separated by angle brackets. For example, File > Create >
Folder .
Symbols
>
Convention
WARNING!
CAUTION:
IMPORTANT:
NOTE:
TIP:
Description
An alert that calls attention to important information that if not understood or followed can result in personal injury.
An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software.
An alert that calls attention to essential information.
An alert that contains additional or supplementary information.
An alert that provides helpful information.
48
Support and other resources
Accessing Hewlett Packard Enterprise Support
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website: www.hpe.com/support/hpesc
Information to collect
Technical support registration number (if applicable)
Product name, model or version, and serial number
Operating system name and version
Firmware version
Error messages
Product-specific reports and logs
Add-on products or components
Third-party products or components
Accessing updates
Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method.
To download product updates, go to either of the following:
Hewlett Packard Enterprise Support Center Get connected with updates page:
www.hpe.com/support/e-updates
Software Depot website: www.hpe.com/support/softwaredepot
To view and update your entitlements, and to link your contracts, Care Packs, and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on
Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.
Websites
Website
Networking websites
Link
49
Website
Hewlett Packard Enterprise Information Library for
Networking
Hewlett Packard Enterprise Networking website
Hewlett Packard Enterprise My Networking website
Hewlett Packard Enterprise My Networking Portal
Hewlett Packard Enterprise Networking Warranty
General websites
Hewlett Packard Enterprise Information Library
Hewlett Packard Enterprise Support Center
Hewlett Packard Enterprise Support Services Central
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Software Depot
Customer Self Repair (not applicable to all devices)
Insight Remote Support (not applicable to all devices)
Link www.hpe.com/networking/resourcefinder www.hpe.com/info/networking www.hpe.com/networking/support www.hpe.com/networking/mynetworking www.hpe.com/networking/warranty www.hpe.com/info/enterprise/docs www.hpe.com/support/hpesc ssc.hpe.com/portal/site/ssc www.hpe.com/assistance www.hpe.com/support/e-updates www.hpe.com/support/softwaredepot www.hpe.com/support/selfrepair www.hpe.com/info/insightremotesupport/docs
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website: www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback ( [email protected]
). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
50
다운로드
광고