01.01.2013 Views

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table A-4 List of incident IDs (continued)<br />

Appendix: Configuration lists<br />

List of incident IDs<br />

Incident ID Description Origin number and name Severity<br />

932 The appliance is disconnected from NTLM-Agent<br />

server x.<br />

2 Core 3<br />

933 The appliance cannot connect to NTLM-Agent server x. 2 Core 3<br />

1050 An update of the URL Filter module was completed<br />

successfully.<br />

2 URL Filter 6<br />

1051 An update of the URL Filter module failed. 2 URL Filter 3<br />

1052 Download or verification of update files for the URL Filter<br />

module failed.<br />

2 URL Filter 3<br />

1053 URL Filter module status is up-to-date. 2 URL Filter 6<br />

1650 An updated Certificate Revocation List (CRL) was<br />

downloaded and loaded successfully on the appliance.<br />

2 Certificate Chain Filter 6<br />

1651 An updated Certificate Revocation List (CRL) was<br />

downloaded onto the appliance, but could not be loaded<br />

there.<br />

2 Certificate Chain Filter 4<br />

1652 An updated Certificate Revocation List (CRL) could not<br />

not be downloaded onto the appliance.<br />

1653 All Certificate Revocation Lists (CRLs) used by the SSL<br />

Scanner module have up-to-date status.<br />

3000 At least one node in central management is not in<br />

synchronized state (regarding storage and<br />

configuration). The number of unsynchronized nodes<br />

changes. This incident is only recorded on the root node.<br />

3001 After incident 3000 has occurred, all nodes in central<br />

management are in synchronized state again (regarding<br />

storage and configuration).<br />

3004 At least one node in central management did not respond<br />

properly after shared data was sent out. The number of<br />

not properly responding nodes changes. This incident is<br />

only recorded on the root node and only if the shared<br />

data was intended to go to all nodes.<br />

3005 After incident 3004 has occurred, all nodes in central<br />

management have properly responded to the sending of<br />

shared data to them.<br />

2 Certificate Chain Filter<br />

2 Certificate Chain Filter 6<br />

3 Centralized Management 3<br />

3 Centralized Management 6<br />

3 Centralized Management 3<br />

3 Centralized Management 6<br />

<strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong> 329

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!