Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual page 159

Service Categories of the Access Gateway Appliance
Service Category
Time: Indicates the type of time configuration. Time
must be configured so that it remains synchronized
with the other servers in the configuration (Identity
Server, SSL VPN server, J2EE Agent, Web
servers, etc.).
Gateway: Specifies the type of routing that is
configured for the gateway.
DNS: Specifies whether the domain name server
has been configured
Services: Indicates the general health of all
configured services.
Address: Indicates whether an IP address has
been configured for the reverse proxy to listen on.
This is required for the Access Gateway to function.
Embedded Service Provider Communication:
Indicates whether the Embedded Service Provider
can communicate with the Identity Server.
L4 and Cache: The L4 status indicates whether
the Linux Access Gateway is responding to health
checks from the L4 switch. The number increments
with each health check for which the Access
Gateway does not send a response.
When it reaches 13, the health is changed to
yellow.
When it reaches 31, the health is changed to
red.
If the Access Gateway recovers and starts
responding, the health turns green after 20 seconds
and the unresponsive count is reset to 0.
To fix the problem if it does not resolve itself, restart
the Access Gateway.
The cache status indicates the current number of
delayed cache requests and whether enough
memory is available to process new requests.
When this number reaches 101, the health is
changed to yellow.
When this number reaches 151, the health
changes to red. To solve the problem, you
need to restart the Linux Access Gateway.
If Not Healthy
See Section 2.6, "Setting the Date and Time," on
page 90.
See Section 2.9.2, "Viewing and Modifying
Gateway Settings," on page
Displays the IP address of the each configured
DNS server and when the server last responded.
See Section 2.9.3, "Viewing and Modifying DNS
Settings," on page 102.
Displays messages about the health of the reverse
proxy, the back end Web servers, and internal
services (the SOAP back channel and the
communication module).
See Section 1.1.1, "Creating a Proxy Service," on
page 17.
Restart the Embedded Service Provider. If
restarting the Embedded Service Provider fails, try
restarting Tomcat.
Restart the Linux Access Gateway by entering the
following commands:
/etc/init.d/novell-vmc stop
/etc/init.d/novell-vmc start
99.
Access Gateway Maintenance 159