McAfee M4050 Troubleshooting Guide - Page 65

Get peer DoS, Invalid SSL

Page 65 highlights

McAfee® Network Security Platform 6.0 System Fault Messages Fault Invalid SSL decryption key Severity Error Description/Cause Action The Sensor detects that a particular Re-import the key (which is SSL decryption key is no longer identified within the error valid; for example, it may be failing message). The fault will clear to decrypt traffic. itself when the key is determined to be valid. Sensor Configuration update failed Error Sensor reports a Error anti-virus dat file error SSL decryption Error key invalid Sensor configuration update failed while See the ems.log file to isolate reason for failure. transferring from the Manager server to the Sensor. A Sensor is detecting an error on av-dat file. Ensure that the Sensor is online and in good health. The Manager will make another attempt to push the file to the Sensor. This fault will clear when the av-dat file is successfully pushed to the Sensor. The Manager detects that a particular SSL decryption key is no longer valid. The detailed reason why the fault is occurring is shown in the fault message. These reasons can range from the Sensor re-initializing itself with a different certificate to an inconsistency between the decryption key residing on a primary Sensor and its failover peer Sensor. Re-import the key (which is identified within the error message). The fault will clear itself when the key is determined to be valid. Get peer DoS profile failure Error Get peer DoS profile failure Error The Manager was unable to obtain the requested profile from a peer Sensor. This was likely due to the requested profile or a valid, saved version being unavailable. Check NSM connection to peer NSP Get peer DOS profile request from Check NSM connection to the Sensor. NSP. failed because the profile cannot be pushed to the Sensor that requested it. See log for details. 56

  • 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

McAfee® Network Security Platform 6.0
System Fault Messages
56
Fault
Severity
Description/Cause
Action
Invalid SSL
decryption key
Error
The Sensor detects that a particular
SSL decryption key is no longer
valid; for example, it may be failing
to decrypt traffic.
Re-import the key (which is
identified within the error
message). The fault will clear
itself when the key is
determined to be valid.
Sensor
Configuration
update failed
Error
Sensor configuration
update failed while
transferring from the
Manager server to the
Sensor.
See the ems.log file to isolate
reason for failure.
Sensor reports a
anti-virus dat file
error
Error
A Sensor is detecting an error on
av-dat file.
Ensure that the Sensor is
online and in good health.
The Manager will make
another attempt to push the
file to the Sensor. This fault
will clear when the av-dat file
is successfully pushed to the
Sensor.
SSL decryption
key invalid
Error
The Manager detects that a
particular SSL decryption key is no
longer valid. The detailed reason
why the fault is occurring is shown
in the fault message. These
reasons can range from the Sensor
re-initializing itself with a different
certificate to an inconsistency
between the decryption key
residing on a primary Sensor and
its failover peer Sensor.
Re-import the key (which is
identified within the error
message). The fault will clear
itself when the key is
determined to be valid.
Get peer DoS
profile failure
Error
The Manager was unable to obtain
the requested profile from a peer
Sensor. This was likely due to the
requested profile or a valid, saved
version being unavailable.
Check NSM connection to
peer NSP
Get peer DoS
profile failure
Error
Get peer DOS profile request from
the Sensor.
failed because the profile cannot be
pushed to the Sensor that
requested it. See log for details.
Check NSM connection to
NSP.