
that ships with the client (abcde12345), or send a Client UI policy to the client with either an
administrator’s password or a time-based password set with the policy, and use this password.
Use the troubleshooting tool to:
• Indicate the logging settings and engine status for the client.
• Turn message logging on and off.
• Turn engines on and off.
Log on as root and run the following commands to aid in troubleshooting:
To do this...Run this command...
Obtain the current status of the client indicating which type of
logging is enabled, and which engines are running.
hipts status
Turn on logging of specific messages types.hipts logging on
Turn off logging of all message types. Logging is off by default.hipts logging off
Display the message type indicated when logging is set to “on.”
Messages include:
hipts message <message name>:on
• error
• warning
• debug
• info
• violations
Hide the message type indicated when logging is set to “on.”
Message error is off by default.
hipts message <message name>:off
Display all message types when logging is set to “on.”hipts message all:on
Hide all message types when logging is set to “on.”hipts message all:off
Turn on the engine indicated. Engine is on by default. Engines
include:
hipts engines <engine name>:on
• MISC
• FILES
• GUID
• MMAP
• BO
• ENV
• HTTP
Turn off the engine indicated.hipts engines <engine name>:off
Turn on all engines.hipts engines all:on
Turn off all engines.hipts engines all:off
TIP: In addition to using the troubleshooting tool, consult the HIPShield.log and HIPClient.log
files in the /opt/McAfee/hip/log directory to verify operations or track issues.
Stopping the Solaris client
You may need to stop a running client and restart it as part of troubleshooting.
Task
1 To stop a running client, first disable IPS protection. Use one of these procedures:
Working with Host Intrusion Prevention Clients
Overview of the Solaris client
101McAfee Host Intrusion Prevention 7.0 Product Guide for use with ePolicy Orchestrator 4.0
Comentarios a estos manuales