Viewing The Health Of An Access Gateway Cluster - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

Access gateway guide
Hide thumbs Also See for ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010:
Table of Contents

Advertisement

Service Category
Signing, Encryption and SSL Connector
Keys: Indicates whether these keystores contain a
valid key.
System Incoming and Outgoing HTTP Requests:
Appears when throughput is slow. This health check
monitors incoming HTTP requests, outgoing HTTP
requests on the SOAP back channel, and HTTP
proxy requests to cluster members. If one or more
requests remain in the queue for over 2 minutes, this
health check appears.
TCP Listener(s): Indicates whether the listening
port for the Embedded Service Provider is healthy.
Embedded Service Provider's Trusted Identity
Provider: Indicates whether the configuration that
the Access Gateway trusts has been configured to
contain at least one Identity Server.
Audit Logging Server: Indicates whether the audit
agent is functioning and able to log events to the
auditing server.
Auditing must be enabled on the Identity Server to
activate this health check (click Devices > Identity
Servers > Edit > Logging).

4.8.3 Viewing the Health of an Access Gateway Cluster

The Health icon on the cluster row displays the status of the least healthy member of the cluster. For
information on the meaning of the health icons, see
To view details about the status of the cluster:
1 In the Administration Console, click Devices > Access Gateways.
2 On the cluster row, click the Health icon.
3 To ensure that the information is current, click Refresh.
4 To view specific information about the status of an Access Gateway, click the Health icon in
the Access Gateway row.
162 Novell Access Manager 3.1 SP2 Access Gateway Guide
If Not Healthy
Click Access Gateways > Edit > Service Provider
Certificates and replace any missing or expired
keys.
Verify that all members of the cluster have
sufficient bandwidth to handle requests. If a
cluster member is going down, the problem
resolves itself as other members of the cluster are
informed that the member is down.
If a cluster member is slow because it doesn't
have enough physical resources (speed or
memory) to handle the load, upgrade the
hardware.
Restart the Access Gateway.
Modify the Identity Server configuration and add
an Identity Server.
Configure the Access Gateway to trust an Identity
Server configuration. See
Section 1.1.1, "Creating
a Proxy Service," on page
Check the network connection between the
Identity Server and the auditing server.
See
"Troubleshooting Novell Audit" (http://
www.novell.com/documentation/novellaudit20/
novellaudit20/data/al0lh30.html).
Section 4.8.1, "Health States," on page
17.
158.

Advertisement

Table of Contents
loading

Table of Contents