System information

23
Release Notes for Cisco VPN 3000 Series Concentrator, Release 3.6 Through 3.6.8.B
OL-5637-02
Caveats Resolved in Release 3.6.8.B
Workaround:
Disable L2TP compression and/or EAP-TLS Auth.
CSCeb08162
Clicking apply on any LAN-to-LAN SA causes all LAN-to-LAN sessions to drop.
CSCeb09587
If you have a client user and an admin user with the same name, the client user might not be able to
connect when the admin user is logged in and the client user has a simultaneous logins set to 1.
This caveat has been closed because the VPN 3000 Concentrator has a flat namespace. The
administrator names should be different from the username for security reasons.
Workaround:
Do one of the following:
Use different users name for web and vpn client connection.
Set the simultaneous logins on the group to more than 1.
Connect from a vpn client before making web connection using the same user.
CSCeb13767
In the LAN-to-LAN NAT rules, the VPN Concentrator accepts network/mask rules such as
192.168.1.0/255.255.0.0.
It should consider this as a typo and either modify it to be 192.168.0.0/255.255.0.0 or it should reject
it and warn the user.
CSCeb36140
After some period of time the concentrator will fail to take any new connections. Each new incoming
connection fails with a time-out in building IKE Main Mode Message 6.
Workaround:
Reboot the Concentrator.
CSCeb48289
VPN3000 crash due to a malformed PPP IP Control Protocol message.
Caveats Resolved in Release 3.6.8.B
Release 3.6.8.B resolves the following issues:
CSCdy86551
The following message is shown on the Primary box:
269 10/09/2002 12:20:58.640 SEV=2 IP/25 RPT=32
A device with MAC address 00005E000101 is attempting to use the IP Address of Interface 1
(10.100.1.195)
Although this is not really causing the Secondary to takeover, it is filling up the logs. The Severity
to Log is set to General 1-5 (the Default).
Customer wants to know how we can change the message to something which seems less threatening
and doesn't seem to show something is wrong. Also, do not show it in the log every time.