Chapter 6 Configuring a Sun Update Connection Proxy

This chapter describes how to configure a Sun Update Connection Proxy , also referred to as a local patch server, on a Solaris 10 system. This chapter includes the following task-related information:

• Configuring Your Sun Update Connection Proxy (Task Map)

• Configuring Your Sun Update Connection Proxy

The Sun Update Connection Proxy supports client systems that use the Sun Update Connection Hosted product and the Sun Patch Manager 2.0 product. A Sun Update Connection System client system is not compatible with the older local patch server feature associated with the Sun Patch Manager 2.0 product.

The Sun Update Connection Proxy is an optional feature that you can obtain at no charge if you have a Sun Service Plan. For information about obtaining a Sun Service Plan, go to Solaris Operating System Software Support at http://www.sun.com/service/support/software/solaris/ and select the appropriate level of service.

For instructions on how to install the proxy, see How to Install the Update Manager Feature Update or How to Install the Update Manager Client Software.

Configuring Your Sun Update Connection Proxy (Task Map)

The following table identifies the tasks that you can perform with the patchsvr setup command to configure an update server on your intranet. See the patchsvr(1M) man page.

Before you can perform these tasks, you must install the Sun Update Connection Proxy software. For instructions on how to install the proxy, see How to Install the Update Manager Feature Update or How to Install the Update Manager Client Software.

Configuring Your Sun Update Connection Proxy

Client systems are configured to obtain updates from the Sun update server by default. You need a Sun Update Connection Proxy in the following situations:

• Your client systems are not permitted to connect to the Internet.

• You want to minimize the Internet traffic between your client systems and the Sun update server.

  ---

  Note –

  The Sun Update Connection Proxy is an optional feature that you can obtain at no charge if you have a Sun Service Plan. For information about obtaining a Sun Service Plan, go to Solaris Operating System Software Support at http://www.sun.com/service/support/software/solaris/ and select the appropriate level of service.

  ---

For additional information, see Sun Update Connection Proxy .

Configuring Your Update Management Environment to Include a Sun Update Connection Proxy

Configuring your update management environment to include a Sun Update Connection Proxy and configuring your client systems to use the proxy involves completing these tasks:

1. Configure and start your Sun Update Connection Proxy .

   See How to Initially Configure Your Sun Update Connection Proxy (Command Line).

2. Configure your client system or systems to obtain updates from your Sun Update Connection Proxy .

   See How to Specify a Source of Updates (GUI).

After completing these tasks, you are ready to have your client systems obtain updates from your Sun Update Connection Proxy . See Chapter 4, Managing Solaris Updates by Using the Update Manager GUI.

The Sun Update Connection Proxy logs are stored in the /var/patchsvr/logs directory.

Configuration Requirements

Your Sun Update Connection Proxy needs to obtain updates and update data from one of these sources:

• Update server. The update server can be the Sun update server or another Sun Update Connection Proxy in the chain of update servers. The Sun update server is the default source of updates.

• Local collection of updates. A collection of updates and update data that is stored in a directory available to the local system. Such a directory might be a local directory, a shared network directory, or a CD mounted on your local system.

After you set up the Sun Update Connection Proxy , you must configure each of your client systems to communicate with that proxy. Then you are ready to have your client systems obtain updates from that proxy.

If you locally manage a system that is a client of a Sun Update Connection Proxy on your intranet, you do not need to register the client system. You must register the system that acts as the proxy. If, however, your client system is also remotely managed by the Sun Update Connection Hosted web application, the client system must be registered.

Configuring Your Sun Update Connection Proxy by Using the Command-Line Interface

Use the patchsvr command to configure and enable your Sun Update Connection Proxy . See the patchsvr(1M) man page.

How to Initially Configure Your Sun Update Connection Proxy (Command Line)

Before you can use a system as a Sun Update Connection Proxy , you must ensure that the proxy software is installed, configure and start the proxy, and configure clients to communicate with it.

For instructions on how to install the proxy, see How to Install the Update Manager Feature Update or How to Install the Update Manager Client Software.

The Sun Update Connection Proxy supports client systems that use the Sun Update Connection Hosted product and the Sun Patch Manager 2.0 product. A Sun Update Connection System client system is not compatible with the older local patch server feature associated with the Sun Patch Manager 2.0 product.

The system that you want to act as a Sun Update Connection System Proxy on your intranet must meet these software requirements:

• Solaris 10 system with at least the Developer Solaris Software Group (SUNWCdev), the Entire Solaris Software Group (SUNWCall), or the Entire Plus OEM Solaris Software Group (SUNWCXall).

  A software group is a logical collection of Solaris packages that is installed only with an initial Solaris installation. The Developer Solaris Software Group provides the packages needed to support software development.

• Sun Update Manager software

  For step-by-step instructions on installing the Update Manager software, see Installing the Sun Update Connection System Software (Task Map).

If your Sun Update Connection Proxy uses a network proxy to connect to the Internet, you must specify information about the network proxy. See How to Change Configuration Settings for Your Sun Update Connection Proxy (Command Line).

1. As superuser, log in to the system that you plan to use as your Sun Update Connection Proxy .

2. Determine whether the SUNWpsvru and SUNWpsvrr packages are installed on the system.

   # pkginfo | grep SUNWpsvrsystem SUNWpsvrr Patch Server Deployment (Root) system SUNWpsvru Patch Server Deployment (Usr)

3. If the packages are not installed, you must install them before continuing this task.

4. Register this system with Update Manager.

   See Registering Your System With Update Manager (Task Map).

5. If needed, specify the network proxy that your Sun Update Connection Proxy uses to connect to the Internet.

   # patchsvr setup -x network-proxy-name:port

   If you do not have the network proxy information, contact your network administrator.

6. Specify the update source.

   Your Sun Update Connection Proxy can point to a different source of updates. This update source can be used to fulfill update download requests that cannot be fulfilled by your proxy. By default, the source of updates for your Sun Update Connection Proxy is the Sun update server.

   • To specify the next update server in the chain of Sun Update Connection Proxies, type:

     # patchsvr setup -p http://server-name:3816/solaris/

     The port used for a proxy server is 3816.

   • To specify a collection of updates on the Sun Update Connection Proxy , type:

     # patchsvr setup -p file:///directory-name

     The local collection of updates can be in a directory, on a CD, or on a remote file system.

   • To specify the Sun update server, which is the default, type:

     # patchsvr setup -p https://getupdates1.sun.com/

7. Start your Sun Update Connection Proxy .

   # patchsvr start

8. (Optional) Enable your Sun Update Connection Proxy so that it is started each time the system boots.

   # patchsvr enable

Examples: Initially Configuring Your Sun Update Connection Proxy

Each of these examples verify that the Sun Update Connection Proxy software is installed on the system.

• The following example shows how to configure a Sun Update Connection Proxy to point to another proxy in a chain. You configure two proxies to serve systems in two buildings.

  You configure psvr1 to obtain updates from the Sun update server. Also, psvr1 communicates with the Internet by using a network proxy. Before you can make the Sun Update Connection Proxy ready for use, you must specify the host name, networkproxy1, and the port number, 2010, of the network proxy. After you configure psvr1, you must start it. You can also enable it for automatic restart when the system boots.

  psvr1 # pkginfo | grep SUNWpsvr system SUNWpsvrr Patch Server Deployment (Root) system SUNWpsvru Patch Server Deployment (Usr) psvr1 # patchsvr setup -x networkproxy1:2010 psvr1 # patchsvr setup -p https://getupdates1.sun.com/ psvr1 # patchsvr start Starting Local Patch Server psvr1 # patchsvr enable

  You configure psvr2 to obtain updates from psvr1 by specifying the URL to the server, which is http://psvr1:3816/solaris/. After you configure psvr2, you must start it. You can also enable it for automatic restart when the system boots.

  psvr2 # pkginfo | grep SUNWpsvr system SUNWpsvrr Patch Server Deployment (Root) system SUNWpsvru Patch Server Deployment (Usr) psvr2 # patchsvr setup -p http://psvr1:3816/solaris/ psvr2 # patchsvr start Starting Local Patch Server psvr2 # patchsvr enable

  Now that both of the update servers are configured and started, configure client systems to use them. See How to Specify a Source of Updates (GUI).

• The following example shows how to configure a Sun Update Connection Proxy to obtain updates from a local collection of updates in the /export/updates directory. The URL that points to this directory is file:///export/updates. After configuring the proxy, you must start it. You can also enable it for automatic restart when the system boots.

  # pkginfo | grep SUNWpsvr system SUNWpsvrr Patch Server Deployment (Root) system SUNWpsvru Patch Server Deployment (Usr) # patchsvr setup -p file:///export/updates # patchsvr start Starting Local Patch Server # patchsvr enable

  Now that the update server is configured and started, configure client systems to use it. See How to Specify a Source of Updates (GUI).

• The following example shows how to configure a Sun Update Connection Proxy to obtain updates from a local collection of updates on a CD mounted from the first CD-ROM drive. The URL that points to this CD is file:///cdrom/cdrom0. After configuring the proxy, you must start it. You can also enable it for automatic restart when the system boots.

  # pkginfo | grep SUNWpsvr system SUNWpsvrr Patch Server Deployment (Root) system SUNWpsvru Patch Server Deployment (Usr) # patchsvr setup -p file:///cdrom/cdrom0 # patchsvr start Starting Local Patch Server # patchsvr enable

  Now that the update server is configured and started, configure client systems to use it. See How to Specify a Source of Updates (GUI).

• The following example shows how to configure a Sun Update Connection Proxy to obtain updates from a collection of updates that is mounted on a remote system. The URL that points to this directory is /net/mars/export/updates. After configuring the proxy, you must start it. You can also enable it for automatic restart when the system boots.

  # pkginfo | grep SUNWpsvr system SUNWpsvrr Patch Server Deployment (Root) system SUNWpsvru Patch Server Deployment (Usr) # patchsvr setup -p file:///net/mars/export/updates # patchsvr start Starting Local Patch Server # patchsvr enable

  Now that the update server is configured and started, configure client systems to use it. See How to Specify a Source of Updates (GUI).

How to View Configuration Settings for Your Sun Update Connection Proxy (Command Line)

You can check the configuration settings of your Sun Update Connection Proxy to help diagnose problems or to understand your server’s update-related settings.

The information includes the following:

• Location of the update collection. Source of updates to be checked when the requested update is not available on the local server.

• Network proxy information. Host name and port of a network proxy that is used to communicate with the Internet.

• Location of the update cache. Directory where updates are cached.

1. Log in to the Sun Update Connection Proxy as superuser.

2. List the configuration settings for your proxy.

   # patchsvr setup -l Patch source URL: https://getupdates1.sun.com Cache location: /var/sadm/spool/patchsvr Web proxy host name: mars Web proxy port number: 8080

How to Change Configuration Settings for Your Sun Update Connection Proxy (Command Line)

If you want to change the configuration settings of your Sun Update Connection Proxy , you must first stop the proxy. After you change the settings by using the patchsvr setup command, you must restart the proxy.

For information about the configuration settings that you can change, see the patchsvr(1M) man page.

1. As superuser, log in to the system that you plan to use as your Sun Update Connection Proxy .

2. Stop the proxy.

   # patchsvr stop

3. Change one or more configuration settings, one per command line.

   For example, specify a network proxy, network-proxy-name, and a port, port.

   # patchsvr setup -x network-proxy-name:port

4. Start the proxy.

   # patchsvr start

Example: Changing Configuration Settings for Your Sun Update Connection Proxy

This example shows how to change some configuration settings for your Sun Update Connection Proxy. The Sun Update Connection Proxy communicates with the Internet by using a network proxy. First, you stop the Sun Update Connection Proxy , then specify the host name, networkproxy1, and the port number, 2010, of the network proxy.

Then, you specify the next Sun Update Connection Proxy in the chain. You configure two proxies to serve systems in two buildings. The psvr1 server obtains updates from the Sun update server. The second server, psvr2, obtains updates from psvr1. You configure psvr2 to obtain updates from psvr1 by specifying the URL to the server, which is http://psvr1:3816/solaris/.

# patchsvr stop
Shutting down Local Patch Server
# patchsvr setup -x networkproxy1:2010
# patchsvr setup -p http://psvr1:3816/solaris/
# patchsvr start
Starting Local Patch Server