< Previous  | TOC | Index | Next  >

Configuring a peer management server

Configuring a peer management server enables you to expand the scope of the Cluster Management Console to include remote physical locations. Remote locations usually have a management server that is local to them. The management server at the remote location is the one that you configure as a peer to your local management server.

After configuration, both management servers are considered to be peers of the other. Users logging in to either management server are able to administer objects at both sites from a single console, using a single login. The views and tasks available at the peer location are determined by the user's role, just as they are on the local management server.

Symantec recommends that you configure only one management server per physical location.

 To configure a peer management server

1. Configure a trust relationship between the local authentication broker and the peer authentication broker.

   See "Setting up trust between two authentication brokers" on page 135.

2. Run the gaserver -add command on each management server.

   See gaserver for the proper parameters to use for the gaserver command.

3. Both management servers appear in the Management Servers panel in the Home:Summary view. The name of the remote management server appears as a link in the middle of the Management Servers panel. After the first peer-to-peer updates occur, you can click this link to navigate to the peer management server.
4. The file Managmentserver.conf contains the URL of the local management server. This value is sent to the peer management server during the peer-to-peer update process.