WSM Reference Guide - WatchGuard Technologies
WSM Reference Guide - WatchGuard Technologies
WSM Reference Guide - WatchGuard Technologies
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Alarm Logs<br />
Traffic Alarms<br />
Default<br />
Name<br />
ESP-<br />
Replay-<br />
Error<br />
Message Format Example Message Caused By<br />
alarm_name detected. ESP replay<br />
error, policy_id=policy_id_number,<br />
local_ip=local_IP_address,<br />
peer_ip=peer_IP_address, spi=spi,<br />
sa_id=ID_of_SA,<br />
interface=interface_number, the<br />
first (x) bytes are list_of_first x<br />
number of bytes.<br />
ESP-Replay-Error detected. ESP<br />
replay error, policy_id=2,<br />
local_ip=10.10.10.10,<br />
peer_ip=192.168.228.226,<br />
spi=12345678, sa_id=1000,<br />
interface=1, the first 80 bytes are<br />
A0 B1 C2.........<br />
These alarms are<br />
triggered by the traffic<br />
event<br />
“ESP_REPLAY_ERROR”.<br />
AH-<br />
Replay-<br />
Error<br />
alarm_name detected. AH replay<br />
error, policy_id=policy_id_number,<br />
local_ip=local_IP_address,<br />
peer_ip=peer_IP_address, spi=spi,<br />
sa_id=ID_of_SA,<br />
interface=interface_number, the<br />
first (x) bytes are list_of_first x<br />
number of bytes.<br />
AH-Replay-Error detected. AH<br />
replay error, policy_id=2,<br />
local_ip=10.10.10.10,<br />
peer_ip=192.168.228.226,<br />
spi=12345678, sa_id=1000,<br />
interface=1, the first 80 bytes are<br />
A0 B1 C2.........<br />
These alarms are<br />
triggered by the traffic<br />
event<br />
“AP_REPLAY_ERROR”.<br />
Invalid-<br />
SPI<br />
alarm_name detected. Invalid SPI<br />
%d(0x%x) detected on interface<br />
interface_number, the first (x) bytes<br />
are list_of_first x number of bytes.<br />
Invalid-SPI detected. Invliad SPI<br />
12345678 (0xBC614E) detected on<br />
interface 1, the first 80 bytes are A0<br />
B1 C2........<br />
These alarms are<br />
triggered by the traffic<br />
event “INVALID_SPI”.<br />
Other-<br />
Policy-<br />
Error<br />
alarm_name detected. Policy error<br />
detected on interface<br />
interface_number, the first (x) bytes<br />
are list_of_first x number of bytes.<br />
Other-Policy-Error detected. Policy<br />
error detected on interface 1, the<br />
first 80 bytes are A0 B1 C2............<br />
These alarms are<br />
triggered by the traffic<br />
event<br />
“OTHER_AUTH_ERROR”.<br />
Probe Alarms<br />
Default<br />
Name<br />
Any Probe<br />
Alarm<br />
Message Format Example Message Caused By<br />
Operator [Probe probe_name:<br />
probe_value (value)<br />
alarm_cond_op_name threshold<br />
(threshold)]<br />
NOTE: The content of this alarm<br />
message is based on the event that<br />
triggered the alarm. See the<br />
examples below.<br />
These alarms are<br />
triggered by counter<br />
values.<br />
Link-<br />
Down<br />
[Probe Link Status: 0.00 (value)<br />
becomes 0.00 (threshold)] OR<br />
[Probe Link Status: 1.00 (value)<br />
becomes 0.00 (threshold)] OR<br />
[Probe Link Status: 0.00 (value)<br />
becomes 0.00 (threshold)]<br />
These alarms are<br />
triggered by interface<br />
counters..<br />
40 <strong>WatchGuard</strong> System Manager