McAfee HISCDE-AB-IA Product Guide - Page 96

Verifying Solaris installation files, Verifying the Solaris client is running

Page 96 highlights

Working with Host Intrusion Prevention Clients Overview of the Solaris client To... • BO • HTTP Run... Turn off the engine indicated. Turn on all engines. Turn off all engines. hipts engines :off hipts engines all:on 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. Verifying Solaris installation files After an installation, check that all the files were installed in the appropriate directory on the client. The /opt/McAfee/hip directory should contain these essential files and directories: File/Directory Name HipClient; HipClient-bin HipClientPolicy.xml hipts; hipts-bin *.so log directory Description Solaris client Policy rules Troubleshooting tool Host Intrusion Prevention and McAfee Agent shared object modules Contains debug and error log files Installation history is written to /opt/McAfee/etc/hip-install.log. Refer to this file for any questions about the installation or removal process of the Host Intrusion Prevention client. Verifying the Solaris client is running The client might be installed correctly, but you might encounter problems with its operation. If the client does not appear in the ePO console, for example, check that it is running, using either of these commands: • /etc/rc2.d/S99hip status • ps -ef | grep Hip Stopping the Solaris client You might 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: • Set IPS Options to Off in the ePO console and apply the policy to the client. • Logged in at root, run the command: hipts engines MISC:off 2 Run the command: /sbin/rc2.d/S99hip stop Restarting the Solaris client You might need to stop a running client and restart it as part of troubleshooting. 96 McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154

Run...
To...
BO
HTTP
hipts engines <engine name>:off
Turn off the engine indicated.
hipts engines all:on
Turn on all engines.
hipts engines all:off
Turn off all engines.
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.
Verifying Solaris installation files
After an installation, check that all the files were installed in the appropriate directory on the
client. The /
opt/McAfee/hip
directory should contain these essential files and directories:
Description
File/Directory Name
Solaris client
HipClient; HipClient-bin
Policy rules
HipClientPolicy.xml
Troubleshooting tool
hipts; hipts-bin
Host Intrusion Prevention and McAfee Agent shared object modules
*.so
Contains debug and error log files
log directory
Installation history is written to
/opt/McAfee/etc/hip-install.log
. Refer to this file for any questions
about the installation or removal process of the Host Intrusion Prevention client.
Verifying the Solaris client is running
The client might be installed correctly, but you might encounter problems with its operation. If
the client does not appear in the ePO console, for example, check that it is running, using either
of these commands:
/etc/rc2.d/S99hip status
ps –ef | grep Hip
Stopping the Solaris client
You might 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:
Set
IPS Options
to
Off
in the ePO console and apply the policy to the client.
Logged in at root, run the command:
hipts engines MISC:off
2
Run the command:
/sbin/rc2.d/S99hip stop
Restarting the Solaris client
You might need to stop a running client and restart it as part of troubleshooting.
Working with Host Intrusion Prevention Clients
Overview of the Solaris client
McAfee Host Intrusion Prevention 8.0 Product Guide for ePolicy Orchestrator 4.5
96