
14
Release Note for Cisco ACNS Software, Release 5.5.7
OL-13139-01
Open Caveats in Software Version 5.5.7
• CSCed77655
Symptom: The Content Engine stops spoofing the client IP address and uses its own IP address to
retrieve content from the origin server.
Condition: The http l4-switch spoof-client-ip enable global configuration command turns on IP
spoofing on a Content Engine that is functioning as a caching engine. When a
rule action use-server global configuration command is used, the Content Engine stops spoofing
the client IP address and instead uses its own IP address to retrieve the content.
Workaround: Remove the rule configurations.
• CSCed84227
Symptom: The network management system (NMS) host does not know where SNMP traps are
coming from.
Condition: This problem occurs if there are two interfaces and you configure interface redundancy
using both interfaces. You must use a dummy IP address for the physical addresses. You then
configure a real IP address that floats between the two interfaces. If you then configure SNMP traps,
the traps are being sourced from the dummy IP address and not the routable IP address. Therefore,
the NMS host does not know from where the trap originates.
Workaround: Configure the Content Engine to generate SNMP version 2c type trap messages.
Because the SNMP version 2c trap message does not contain the IP address of the SNMP agent, the
NMS software will use the source IP address of the UDP message to identify the IP address of the
SNMP agent.
• CSCee67330
Symptom: Microsoft NT LAN Manager (NTLM) authentication fails and the pop-up window is
displayed again.
Condition: This problem occurs if NTLM authentication is being used and the specified domain
name is greater than 50 characters.
Workaround: For NTLM authentication, use a domain controller (DC) that has a domain name less
than 35 characters.
• CSCee90245
Symptom: Microsoft NT LAN Manager (NTLM) authentication occurs even though you disabled it
on the Content Engine.
Condition: This problem occurs rarely. In rare situations, even though you entered the no ntlm
server enable global configuration command to disable NTLM proxy authentication on the
Content Engine, NTLM proxy authentication is still not disabled. In such cases, NTLM
authentication still occurs, although the output of the show running EXEC command shows that the
NTLM server is disabled on the Content Engine.
Workaround: reenter the no ntlm server enable global configuration command on the
Content Engine.
• CSCee92698
Symptom: The ICAP service is enabled on the Content Engine, but the Content Engine is unable to
retrieve the content.
Condition: This problem occurs when the Content Engine is running the ACNS 5.5.7 software, and
you configure two or more ICAP services to subscribe to the same vectoring point (the response
modification [RESPMOD] vectoring point).
Workaround: None. This problem has not been seen in any of our customer sites; the scenario was
assumed by our testing team in an attempt to provide support in future releases.
Comentarios a estos manuales