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.

Appendix: Configuration lists<br />

List of incident IDs<br />

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

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

700 The number of concurrent connections exceeds a<br />

configured overload limit. The appliance enters overload<br />

state. Requests sent to the appliance are accepted with<br />

delay.<br />

2 Proxy 2<br />

701 The appliance is in overload state for more than 30<br />

seconds. Requests sent to the appliance are accepted<br />

with delay.<br />

702 The appliance has left overload state. Requests sent to<br />

the appliance are again accepted without delay.<br />

703 The number of concurrent connections exceeds a<br />

configured high load limit. The appliance enters high load<br />

state. Requests sent to the appliance are accepted with<br />

a delay.<br />

704 The appliance is in high load state for more than 30<br />

seconds. Requests sent to the appliance are accepted<br />

with a delay.<br />

705 The number of concurrent connections has dropped<br />

below 85 % of a configured high load limit. The appliance<br />

is still in high load state. Requests sent to the appliance<br />

are accepted with a delay.<br />

328 <strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong><br />

2 Proxy 2<br />

2 Proxy 4<br />

2 Proxy 4<br />

2 Proxy 4<br />

2 Proxy 6<br />

710 A next-hop proxy server is down and will not be available<br />

for n seconds.<br />

2 Proxy 4<br />

711 The appliance cannot connect to a next-hop proxy<br />

server.<br />

2 Proxy 4<br />

712 A next-hop proxy server has moved back from error<br />

state to normal operation.<br />

2 Proxy 6<br />

720 The listener on IP address x, port y could not be opened. 2 Proxy 2<br />

730 A changed proxy mode configuration requires restart of<br />

the appliance.<br />

2 Proxy 2<br />

850 An update of the Anti-Malware module was completed<br />

successfully.<br />

2 Anti-Malware Filter 6<br />

851 An update of the Anti-Malware module failed. 2 Anti-Malware Filter 3<br />

852 Download or verification of update files for the<br />

Anti-Malware module failed.<br />

2 Anti-Malware Filter 3<br />

853 The Anti-Malware module version is up-to-date. 2 Anti-Malware Filter 6<br />

901 The appliance is connected to n servers for NTML<br />

authentication in Windows domain x.<br />

2 Core 6<br />

902 The appliance cannot connect to n servers for NTML<br />

authentication in Windows domain x.<br />

2 Core 4<br />

903 The appliance cannot contact Windows domain x for<br />

NTLM authentication.<br />

2 Core 3<br />

910 The appliance is connected to the LDAP server with<br />

configuration ID n.<br />

2 Core 6<br />

912 The appliance is disconnected from the LDAP server with<br />

configuration ID n.<br />

2 Core 4<br />

913 The appliance cannot connect to any LDAP server with<br />

configuration ID n.<br />

2 Core 3<br />

920 A response has been received on the appliance from<br />

RADIUS server x after attempting to start<br />

communication with this server to retrieve user<br />

information for authentication purposes.<br />

2 Core 6<br />

921 A response has again been received on the appliance<br />

from RADIUS server x after communication with this<br />

server had been interrupted.<br />

2 Core 6<br />

923 An authentication request sent from the appliance to<br />

RADIUS server x has led to a timeout.<br />

2 Core 3<br />

931 The appliance is connected to NTLM-Agent server x. 2 Core 6

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

Saved successfully!

Ooh no, something went wrong!