This chapter describes how to use the regadm command, which is part of the new Oracle Solaris Auto Registration feature as of Oracle Solaris 10 9/10.
Auto Registration is a built-in mechanism that enables configuration data about your system to be gathered and automatically registered with the Oracle Product Registration System for inventory and support purposes. The regadm command-line interface (CLI) can be used by a privileged system administrator to manage the Auto Registration feature and to explicitly register a system, independent of the installation or upgrade process.
This chapter does not provide detailed information about auto registration processes that are part of an installation or upgrade. Nor does the chapter contain information about which installation methods and configurations support Auto Registration.
For overview information about Auto Registration and details about how the feature works with the installation process, see Oracle Solaris Auto Registration in Oracle Solaris 10 9/10 Installation Guide: Planning for Installation and Upgrade.
The following is a list of the information that is in this chapter:
Oracle Solaris Auto Registration is a mechanism that is built into Oracle Solaris 10 9/10. This mechanism enables basic asset information about your system, called a service tag, to be transmitted to the Oracle Product Registration System upon reboot after an installation or an upgrade, and again on subsequent reboots, if any system configuration changes have occurred. The Oracle Product Registration System consists of web services that are deployed on the public Internet. These services are responsible for implementing the registration of a system's assets. Oracle uses this information to improve its products and services. You can also retrieve and use this information to more effectively manage your inventory.
Auto Registration leverages the existing service tag technology that enables a system's assets to be discovered on a network and then registered in a local registry. Service tags contain information about the products that are installed on your system, for example, the OS version and the hardware configuration. Each service tag describes a different product. To enable the sending of service tags, use your My Oracle Support credentials. For more information, see How Your Oracle Solaris 10 9/10 System Is Registered.
For more information about how service tags work, go to http://wikis.sun.com/display/ServiceTag/Download+OS+Service+Tag.
For general information about service tags, see the stclient(1M) man page.
For answers to common questions and information about how to gain initial access to My Oracle Support, go to http://www.oracle.com/us/support/044753.html#SS6.
Oracle uses support credentials and network connectivity information that is collected before or during an installation or upgrade to associate product registration with a specific user account. Support credentials can also be provided after an installation by using the regadm auth command. See Authenticating a User by Specifying Named Support Credentials. If no support credentials or network connectivity information is specified, the Auto Registration process assumes a direct HTTP network connection (no proxy), and the registration is anonymous.
To register your system by specifying support credentials, you must have either a valid My Oracle Support account or a valid Sun Online account. Support credentials consist of a user name and password that enable you to authenticate to Oracle's support portal and the Oracle Product Registration System.
For information about obtaining a My Oracle Support account, go to http://www.oracle.com/support/premier/myoraclesupport.html.
For information about obtaining a Sun Online account, go to https://reg.sun.com/register.
If you are running Oracle Solaris 10 9/10, you can provide support credentials, as follows:
Before or during an installation or upgrade
Before an automatic installation or upgrade (by using either a network installation or Oracle Solaris JumpStart), you can provide support credentials by adding the new auto_reg keyword to your sysidcfg file. The same keyword can be used to set up an anonymous registration or to disable the Auto Registration feature. If you do not add the auto_reg keyword to the sysidcfg file, you are prompted to provide your support credentials during the installation or upgrade process.
During an interactive installation or upgrade, you are prompted for your support credentials. Or, you can register anonymously. During an interactive installation or upgrade, you can also provide network configuration information, such as the proxy server and proxy port.
During an installation or upgrade, you can use the new Oracle Solaris Live Upgrade -k command option to provide your support credentials and proxy information, or to register anonymously.
For more information about providing support credentials before or during an installation, see Oracle Solaris Auto Registration in Oracle Solaris 10 9/10 Installation Guide: Planning for Installation and Upgrade.
After an installation or upgrade
After an installation, you can use the regadm command to transition a system from being anonymously registered to fully-registered by providing named support credentials. You can also use the regadm command to provide network configuration information, such as proxy server and proxy port. For more information, see Authenticating a User by Specifying Named Support Credentials.
Auto Registration is managed by the svc:/application/autoreg SMF service. This service runs once at boot time to check for changes in your system's configuration.
If any changes have occurred, the service tag data is automatically sent to the Oracle Product Registration System, as follows:
During an initial reboot after an installation or upgrade
When you reboot your system after an installation or upgrade, information about newly installed products is automatically sent to the Oracle Product Registration System.
During subsequent reboots when system configuration changes have occurred
After an installation or upgrade, if the product database has changed, information is automatically sent to the Oracle Product Registration System.
Explicitly, by using the regadm register command
Using the regadm register command to register your system is essentially the same as performing a reboot of the system. If any system configuration changes have occurred, product registration occurs immediately upon running the command. The configuration data is transmitted to the Oracle Product Registration System automatically, without needing to reboot your system. For more information about using the regadm command to register your system, see How to Register Your System by Using the regadm Command.
To obtain information about your registered products, go to https://inventory.sun.com/inventory/data.jsp. For general information about service tags, go to http://wikis.sun.com/display/ServiceTag/Download+OS+Service+Tag.
After an installation or upgrade, Auto Registration configuration can be managed by using the regadm command.
After an installation, a privileged system administrator can perform the following tasks by using the regadm command:
Administer the SMF service that manages the Auto Registration process.
Display the current Auto Registration configuration.
Authenticate a specific user or account with My Oracle Support by specifying named support credentials.
Configure or reconfigure Auto Registration properties.
Clear Auto Registration properties.
Explicitly register your system, independent of the installation process.
For more information, see the regadm(1M) man page.
For task-related information, see Registering Your System by Using the regadm Command.
During a system reboot, the Auto Registration SMF service checks your system's configuration against the information in the Service Tag Registry to determine whether any changes have occurred since the last reboot. If changes are discovered, a service tag for the newly installed product, for example, the Oracle Solaris 10 9/10 OS, is sent to the Oracle Product Registration System and registered with your recorded support credentials, or anonymously, if no support credentials were provided. The data is transmitted by using a Hypertext Transfer Protocol Secure (HTTPS) connection. If no changes are detected during a reboot, no registration is performed.
Although Auto Registration feature is enabled by default, you can optionally disable the feature. For information, see How to Disable the Auto Registration SMF Service.
The Auto Registration SMF service runs in global zones only.
In addition to the Auto Registration SMF service, the Auto Registration process consists of several other components that work together to affect auto registration of your system's assets. The following figure illustrates these components and their relationship to each other.
Auto Registration consists of the following components:
Auto Registration command-line interface
The Auto Registration CLI (/usr/sbin/regadm) enables a privileged system administrator Auto Registration on an Oracle Solaris system. Single commands can be executed from the command line or automated through the use of a script in large server environments. For more information, see the regadm(1M) man page and Registering Your System by Using the regadm Command.
Oracle Product Registration System
The Oracle Product Registration System consists of web services that are deployed on the public Internet. These services are responsible for implementing the registration of products.
Secure transport mechanism
Oracle uses a secure, one-way transport system for access to its registration system. Client-generated information is encrypted with a private key. Registered products are extracted from the Service Tag Registry and then uploaded to My Oracle Support through the use of a secure HTTPS connection (port 443). The use of an HTTPS connection creates a secure channel over an insecure network. If no HTTP proxy and port are specified during registration, a direct network connection is used. Communications are outbound and are initiated from a customer system only.
Auto Registration data elements
The data elements that comprise a registration are identical to the data elements that are used in the Service Tag schema. For more information about the data that is transmitted to the Oracle Product Registration System, go to https://inventory.sun.com/inventory/.
The following is information that will help you get started with administering Auto Registration by using the regadm command.
The following are situations in which you might need to use the regadm command:
To enable the Auto Registration feature
In this situation, you previously disabled Auto Registration, but you now want to use it. To do so, you must enable the Auto Registration SMF service by using the regadm enable command.
To attach named support credentials to a registered system for support purposes
You previously registered products anonymously, but for support purposes, you now need to attach named support credentials to these products.
To explicitly register a system, independent of the installation or upgrade process
You want to explicitly register your system, independent of the installation or upgrade process.
When you use the regadm register command to register your system, the service tag data is transmitted to the Oracle Product Registration System immediately upon running the command. There is no need to reboot the system for a service tag to be sent.
The following are the requirements for using the regadm command:
You must become superuser or assume an equivalent role.
The regadm command is also assigned to the Software Installation rights profile.
The target system must have network connectivity.
If the target system is not connected to the network, and a registration is attempted, the registration fails silently. The Auto Registration process is attempted again during the next reboot.
The Auto Registration feature is managed by an SMF service. This service is enabled by default. You can manually disable the service by using the regadm disable command. The following procedures describe how to manage the Auto Registration SMF service.
The Auto Registration SMF service runs in a global zone only.
Task |
Instructions |
For Information |
---|---|---|
Display the status of the Auto Registration SMF service. |
You can use the regadm command to determine if the Auto Registration SMF service is running. Note that the service is enabled by default. |
How to Determine If the Auto Registration SMF Service Is Enabled |
Disable the Auto Registration SMF service. |
If you do not want to register, or you want to postpone registration, you can optionally disable the Auto Registration SMF service by using the regadm command. | |
Enable the Auto Registration SMF service. |
If you previously disabled the Auto Registration SMF service, you must enable the service prior to registering your system. |
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
Display the current status of the Auto Registration service.
# regadm status Solaris Auto-Registration is currently enabled |
The Auto Registration feature enabled by default. You can manually disable the service by using the regadm disable command.
Become superuser or assume an equivalent role.
Display the current status of the Auto Registration service.
# regadm status Solaris Auto-Registration is currently enabled |
Disable the Auto Registration service.
# regadm disable |
Verify that the service has been disabled.
# regadm status Solaris Auto-Registration is currently disabled |
Display the current status of the Auto Registration service.
# regadm status Solaris Auto-Registration is currently disabled |
Enable the Auto Registration service.
# regadm enable |
Verify that the service has been enabled.
# regadm status Solaris Auto-Registration is currently enabled |
The regadm command can be used to configure Auto Registration, as well as view configuration details. Note that certain configuration tasks, for example, authentication, must be performed prior to registering your system. For more information, see Tasks That Are Required Prior to Registration.
Table 17–2 Configuring Auto Registration Properties (Task Map)
Task |
Instructions |
For Information |
---|---|---|
Display the current Auto Registration configuration. |
Use the regadm list command to display the current Auto Registration configuration. User account credentials, as well as network connectivity information, is displayed by using this command. | |
Clear the current Auto Registration configuration. |
Use the regadm clear command to reset the current Auto Registration configuration. Note that all properties are cleared during this process. | |
Configure HTTP proxy and port settings. |
Use the regadm set command to configure network connectivity information. | |
Configure HTTP proxy authentication settings. |
Use the regadm set command to also configure HTTP proxy authentication settings, per your site's policy and requirements. | |
Authenticate a specific user or account with My Oracle Support by specifying named credentials. |
Use the regadm auth command if you want to associate a registered system with a specific user or account. |
How to Authenticate a User by Specifying Named Support Credentials |
The process of registering your system by using the regadm command includes gathering information and performing certain tasks prior to registration. The task flow is as follows:
Configure HTTP proxy information, per site policy, if required.
Configure HTTP proxy authentication information, per site policy, if required.
For information about how to configure HTTP proxy settings, see Configuring Auto Registration Properties.
Select a registration method.
You can register in one of two ways, by specifying named support credentials or anonymously:
If you want to register by specifying My Oracle Support credentials or by using a Sun Online account, you must provide those support credentials prior to registration. For instructions, see How to Authenticate a User by Specifying Named Support Credentials.
If you are registering anonymously, you can proceed with the registration. See How to Register Your System by Using the regadm Command.
To display the currently authenticated user name and network connectivity information, use the regadm list command, as follows:
# regadm list |
If you need to reset all of the property settings for a configuration, use the regadm clear command. For information, see How to Clear the Current Auto Registration Configuration.
Following are a few examples of various types of Auto Registration configurations.
# regadm list My Oracle Support username user@example.com HTTP Proxy <not configured> HTTP proxy port <not configured> HTTP proxy user <not configured> HTTP proxy password <not configured> |
# regadm list My Oracle Support username user@example.com HTTP Proxy webproxy.example.com HTTP proxy port 8080 HTTP proxy user <not configured> HTTP proxy password <not configured> |
# regadm list My Oracle Support username user@example.com HTTP Proxy webproxy.example.com HTTP proxy port 8080 HTTP proxy user webuser HTTP proxy password ****** |
Clearing the current configuration sets all of the Auto Registration properties to their default settings. This operation essentially has the same effect as a factory reset.
Become superuser or assume an equivalent role.
List the current Auto Registration configuration.
# regadm list |
Clear the current Auto Registration configuration.
# regadm clear |
Verify that the current configuration was cleared.
# regadm list |
The output now displays the default settings for all property values. The default property values are not configured.
In the following example, the regadm clear command is used to clear the property values of the current Auto Registration configuration.
# regadm list My Oracle Support username user@example.com HTTP Proxy webproxy.example.com HTTP proxy port 8080 HTTP proxy user webuser HTTP proxy password ****** # regadm clear # regadm list My Oracle Support username <not configured> HTTP Proxy <not configured> HTTP proxy port <not configured> HTTP proxy user <not configured> HTTP proxy password <not configured> |
The following Auto Registration properties can be configured by using the regadm command:
My Oracle Support or Sun Online account user name and password (Optional)
The user name and password can be configured by using the regadm auth command. The command can be run in either interactive or non-interactive mode. For instructions, see How to Authenticate a User by Specifying Named Support Credentials.
HTTP proxy name (Optional)
HTTP proxy port (Optional)
By default, a direct network connection is used during the registration process, unless you specify otherwise prior to registering. You can optionally configure HTTP proxy and port settings by using the regadm set command. For instructions, see How to Configure HTTP Proxy and Port Settings.
To determine the HTTP proxy name and port information to use, check with your site administrator. To determine whether you need to specify HTTP proxy authentication information, check the policy that is implemented at your site.
HTTP proxy user name and password for authentication (Required only if HTTP proxy authentication is implemented at your site)
If your site's policy specifies that you must set an HTTP proxy user name and password, you can configure this property prior to registration by using the regadm set command. For instructions, see How to Configure HTTP Proxy Authentication Settings.
Previously configured HTTP proxy and port settings can be changed or reset to a direct network connection by using the regadm clear command. For instructions, see How to Clear the Current Auto Registration Configuration.
If you previously registered your system by using a direct network connection, or if you are performing a new registration, you might need to configure HTTP proxy and port settings prior to registering your system.
Become superuser or assume an equivalent role.
Set the HTTP proxy.
# regadm set -n http_proxy -v webproxy-host |
The web proxy might be an IP address, a non-fully-qualified host name, or a fully-qualified host name.
Set the HTTP port.
# regadm set -n http_port -v port-number |
If your site implements HTTP proxy authentication, you must also configure HTTP proxy authentication settings (user name and password). The password must be specified as a single line in a text file and then passed to the regadm command. The following procedure describes how to protect the password file while it is in use. This file should be removed immediately after running the regadm command.
The regadm command accepts a password file in two cases:
When you are setting a user name and password by using the regadm auth command.
When you are setting the HTTP proxy user name and password by using the regadm set command.
Become superuser or assume an equivalent role.
Set the HTTP proxy user name.
# regadm set -n http_proxy_user -v webuser |
where webuser is the site-supplied value to use for authenticating a user with the HTTP proxy server.
Create a temporary password file.
# touch pwfile |
Secure permissions on the file.
# chmod 600 pwfile |
Using a text editor, edit the temporary password file to insert a one-line entry that contains your password information.
Set the HTTP password authentication information.
# regadm set -n http_proxy_pw -v pwfile |
where pwfile is the password file that you created in Step 3.
Remove the password file.
# rm pwfile |
The following example shows how to configure the HTTP authentication properties for a site that requires an HTTP user name and password for authentication purposes.
# regadm set -n http_proxy_user -v webuser # touch myhttppasswd # chmod 600 myhttppasswd # vi myhttppasswd . . . # regadm set -n http_proxy_pw -v myhttppasswd # rm myhttppasswd |
To switch network connectivity to a direct connection, you must set all of the HTTP proxy settings to a null value (not configured), as shown in the following example:
# regadm set -n http_proxy "" # regadm set -n http_proxy_port "" # regadm set -n http_proxy_user "" # regadm set -n http_proxy_pw "" # regadm list My Oracle Support username <not configured> HTTP Proxy <not configured> HTTP proxy port <not configured> HTTP proxy user <not configured> HTTP proxy password <not configured> |
Before a system's products can be registered, the user or account must be authenticated by specifying valid My Oracle Support credentials or valid Sun Online account credentials. If no support credentials are provided, the system is registered with an anonymous My Oracle Support account. You can use the regadm command with the auth subcommand, either interactively or non-interactively, to authenticate yourself with the Oracle Product Registration System.
Authentication must take place prior to registering by using the regadm register command.
The regadm auth command is used with the -u and -p options, as follows:
# regadm auth -u username -p pwfile |
The -u option specifies a valid user name. The -p option specifies a file that contains password information for the user account.
The password file is a single-line file that you create and then add the credentials that are to be passed to the regadm command. The contents of the password file are private. For security reasons, remove the file immediately after the information is passed to the regadm command and a successful authentication has occurred.
A successful authentication persists across reboots and only needs to be provided one time. You can authenticate before or during an installation, or after an installation by using the regadm auth command. The password is never stored on the system. Only an opaque token is maintained after a successful authentication.
The regadm auth command can be used to authenticate a user with My Oracle Support, either interactively or non-interactively. The following procedure describes how to use the command non-interactively. The examples that follow show how to run the command in both modes.
Become superuser or assume an equivalent role.
Create a temporary password file:
# touch pwfile |
Secure permissions on the file:
# chmod 600 pwfile |
Using a text editor, edit the temporary password file that you just created. Insert a one-line entry that contains your password information.
Authenticate with My Oracle Support by specifying your named support credentials:
# regadm auth -u user@example.com -p pwfile |
where user@example.com is either the My Oracle Support or Sun Online account user name, and pwfile is the password file that you created in Step 2.
A message indicating that the authentication succeeded or failed is displayed.
Proceed as follows:
If the authentication succeeds, you can proceed with the registration.
For instructions, see How to Register Your System by Using the regadm Command.
If the authentication fails, refer to Troubleshooting Auto Registration Issues.
Remove the temporary password file:
# rm pwfile |
# touch mospwfile # chmod 600 mospwfile # vi mospwfile . . . # regadm auth -u jdoe@mycompany.com -p mospwfile Authenticating "jdoe@mycompany.com" with My Oracle Support Authentication sucessful You can now register this system with My Oracle Support via "regadm register" # rm mospwfile |
# regadm auth Enter your My Oracle Support username: jdoe@mycompany.com Enter password: Enter password again: Authenticating "jdoe@mycompany.com" with My Oracle Support Authentication successful You can now register this system with My Oracle Support via "regadm register" |
Task |
Instructions |
For Information |
---|---|---|
1. (Optional) Perform a dry run of a product registration. |
Use the regadm register command with the -d option to display service tag information about products that are yet to be registered, prior to actually registering. The output of the command displays the data that will be transmitted to My Oracle Support during an actual registration. |
How to Display Registration Information About Products Not Yet Registered |
2. Perform a product registration. |
Use the regadm register command to explicitly register your system, independent of an installation or upgrade. |
Using the dry run function of the regadm register command enables you to display service tag information about products that are not yet registered. This function can be useful for system administrators who want to know what information will be sent to My Oracle Support prior to actually registering. Service tags enable automatic discovery of the products that are installed on your system. When you use the register -d command option, the service tag data that is to be transmitted to the Oracle Product Registration System is merely displayed.
To use the dry run command option you must be on a system that has network connectivity.
Become superuser or assume an equivalent role.
Type the regadm register command with the dry run command option, as follows:
# regadm register -d |
The output of the command is displayed in XML file format.
The following example shows the output from running the regadm register command with the -d option. For brevity, the command output has been truncated.
# regadm register -d Registering with My Oracle Support using username user@example.com <?xml version="1.0"?> <st1:request> <agent> <agent_urn>urn:st:5eabd994-12d0-6c6c-bf6e-a2cca89a0287</agent_urn> <agent_version>1.1.5.</agent_version> <registry_version>1.1.5</registry_version> <system_info> <system>SunOS</system> <host>hs-t1000-1</host> <release>5.10</release> <architecture>sparc</architecture> <platform>SUNW,Sun-Fire-T1000::Generic_141444-09</platform> . . . <system_info> </agent> </st1:request> <?xml version="1.0"?> <st1:request> <service_tag> <instance_urn>urn:st:fd96de223-e190-6501-ff8d-dd76f1b708f5</instance_urn> <product_name>Solaris 10 Operating System</product_name> . . . |
The regadm register command is used to register each product in the Service Tag Registry with My Oracle Support. Registration is accomplished by using the current authentication credentials. If no credentials are provided, the registration is performed anonymously by using an anonymous My Oracle Support account.
Be sure to check Tasks That Are Required Prior to Registration for prerequisite instructions.
Consider also the following information:
If you previously registered your system anonymously, and you now want to register by specifying named support credentials, you must authenticate those credentials by using the regadm auth command. The process of authentication is a separate task that must be performed prior to registration. For instructions, see How to Authenticate a User by Specifying Named Support Credentials.
If you previously registered your system by specifying named support credentials, and you now want to register anonymously, you must clear the current Auto Registration configuration prior to registration. For instructions, see How to Clear the Current Auto Registration Configuration.
The clear subcommand clears all configured properties, including any previously configured network connectivity information.
If you previously registered your system by using a direct network connection, and you now want to specify HTTP proxy and port information, you must configure those properties by using the regadm set command prior to registration. For instructions, see How to Configure HTTP Proxy and Port Settings.
Become superuser or assume an equivalent role.
List the current Auto Registration configuration.
# regadm list |
If the output of the regadm list command does not display any configured Auto Registration properties (user name), the registration will be anonymous. Otherwise, the registration is associated with the user name that is displayed. If you are registering your system anonymously, but you prefer to provide support credentials, see How to Authenticate a User by Specifying Named Support Credentials before proceeding.
If the output of the regadm list command does not display any HTTP proxy or port information, the registration will be performed by using a direct network connection. Otherwise, the existing HTTP property settings are used. If you need to reconfigure Auto Registration properties for network connectivity, see How to Configure HTTP Proxy and Port Settings before proceeding.
Register your system.
# regadm register |
The output of the regadm register command varies, depending on how the Auto Registration feature is configured on your system.
The following example shows an anonymous registration on a system where no named support credentials were configured prior to registration. The registration also uses a direct network connection.
# regadm list My Oracle Support username <not configured> HTTP Proxy <not configured> HTTP proxy port <not configured> HTTP proxy user <not configured> HTTP proxy password <not configured> # regadm register Registered Solaris 10 Operating System Registration Successful |
The following example shows a registration on a system where support credentials and HTTP proxy and port information were configured prior to registration.
# regadm list My Oracle Support username user@example.com HTTP Proxy webproxy.example.com HTTP proxy port 8080 HTTP proxy user <not configured> HTTP proxy password <not configured> # regadm register Registering with My Oracle Support using username user@example.com Registered Solaris 10 Operating System Registration successful |
To obtain service tag information for products that are currently registered with the Auto Registration feature, go to https://inventory.sun.com/inventory/data.jsp.
To access service tag information for your registered products, you must first log in with either your My Oracle Support account credentials or your Sun Online account credentials.
Be aware that the inventory web site provides information about discovery and registration methods that are not associated with the new Auto Registration feature. These other registration methods are used on a voluntary basis and registration is not mandatory. If you have installed Oracle Solaris 10 9/10, Auto Registration occurs upon the first reboot after an installation or upgrade.
For general information about how your system's assets are managed with service tags, go to http://wikis.sun.com/display/ServiceTag/Home.
The more common errors that you might encounter while attempting to authenticate or register your system can be resolved by following basic troubleshooting strategies. The following are issues that you might need to troubleshoot when using the regadm command:
If you attempt to authenticate yourself with My Oracle Support by using the regadm auth command, and the authentication fails, the following message is displayed after you type your user name and password:
Authentication failed |
To troubleshoot this issue, verify that you are using the correct account credentials (My Oracle Support user name and password, or Sun Online account user name and password). To verify your account settings, go to https://reg.sun.com/accounthelp.
For answers to common questions and information about how to gain initial access to My Oracle Support, go to http://www.oracle.com/us/support/044753.html#SS6.
For security reasons, the HTTP proxy password must be located in a file rather than specified on the command line. If the password has not been specified in a file, the regadm command cannot locate the password. Consequently, the following message is displayed when you attempt to set your password:
# regadm set -n http_proxy_pw -v secret1 Cannot find file 'secret1' |
For instructions on setting the HTTP proxy password, see How to Configure HTTP Proxy Authentication Settings.
If a problem exists with your HTTP configuration, the following error message might be displayed:
HTTP Communications error with Oracle Support Center Please check your HTTP settings and retry your request. |
There can be one or more reasons that this error message is displayed. To troubleshoot the problem, follow these steps:
Verify that your HTTP configuration is correct by typing the following command:
# regadm list |
If your configuration is correct, check the following information:
Does your system have access to the public Internet, either directly or through an HTTP proxy? If not, you cannot use the regadm command to administer the Auto Registration feature.
Is an HTTP proxy required at your site? If so, ensure that the HTTP proxy host and port have been configured correctly. For instructions, see How to Configure HTTP Proxy and Port Settings.
Is authenticated proxy access required at your site? If so, verify that the proxy user name and password have been configured and typed correctly. For instructions, see How to Configure HTTP Proxy Authentication Settings.
Ensure that your HTTP proxy host setting can be resolved to a valid web proxy host that is up and running and has a name that is resolvable.
For example, if your configured HTTP proxy host is webproxy.example.com, it should be both resolvable and able to respond to a request from the ping utility, as follows:
# getent hosts webproxy.example.com 192.168.1.1 webproxy.example.com # ping webproxy.example.com webproxy.example.com is alive |
For more information, see the getent(1M) and ping(1M) man pages.
If the previous troubleshooting steps do not work, verify your settings with your site administrator.