System information
35
Release Notes for Cisco VPN 3000 Series Concentrator, Release 3.6 Through 3.6.8.B
OL-5637-02
Caveat Resolved in Release 3.6.7
• CSCea04761
A VPN Concentrator with VPN Group configured with Radius with Expiry and “Simultaneous
Logins” set to “1” allows more than one connection.
• CSCea08807
SDI Servers go off line and do not recover. SDIN sockets remain open. This is a frequent but
intermittent problem.
• CSCin30722
Any text When the MIB variable alSepModuleStatsSlotNum is queried on a VPN 3000 Concentrator
with a SEP card, it returns a “No Such Instance” SNMP error.
Caveat Resolved in Release 3.6.7
Release 3.6.7 resolves the following issue:
• CSCdz23343
A defect was introduced in the 3.6.6 Release of the VPN3000 Concentrator that causes the
Concentrator to stop accepting new connections after 40 cumulative connection failures. On the
3005 & 3015 platforms, the threshold is 15 cumulative failures.
Once the cumulative failure total is hit, no more IKE requests are processed. Current sessions are
not immediately affected, but are not be able to rekey. A system reboot is required to reset the
cumulative counter.
Caveats Resolved in Release 3.6.6
Release 3.6.6 resolves the following caveats.
• CSCdv72688
When using Quick Config on the VPN3002 to change IP address and enable DHCP, the user is
locked out from management access as soon as the IP address is changed.
• CSCdw42380
When you use the Monitoring Sessions screen or the Administer Sessions screen to configure a VPN
3000 Concentrator with a LAN-to-LAN tunnel to any device through the Private Interface, the
tunnel shows up under the MANAGEMENT SESSIONS as VCA/IPSEC, rather than under the
LAN-to-LAN Tunnels, as should be the case. The tunnel works fine, as expected.
• CSCdx87630
Using the Mozilla 1.0 Web Browser to manage the VPN 3000 Concentrator, clicking any of the links
always returns you to the login screen. Currently, the VPN 3000 Concentrator only fully supports
Netscape and Internet Explorer.
• CSCdy42182
The VPN 3000 Concentrator failed while freeing memory after telnet session was closed.
• CSCdy51051
New Pin authentication works correctly when authenticating directly to RSA. If RADIUS is used as
a proxy for RSA authentication, then new pin mode fails. This failure occurs when RSA's RADIUS
server is used. There is no problem when a Cisco Secure ACS server is used.