System information

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

• CSCdx66535

The VPN concentrator reboots if an L2TP connection is attempted to the concentrator with

Bandwidth management enabled.

• CSCdx66566

When the sorting tabs are clicked on in admin/sessions, while both RAS and LAN-to-LAN sessions

are being displayed, the LAN-to-LAN summaries table appears distorted. Specifically, the

LAN-to-LAN entries lose the Bytes Received column and the “Action” entries are shifted two

columns to the left.

• CSCdx69618

HTML quick config allows the administrator to configure DHCP address pool assignment without

specifying a DHCP server. This does not work, because DHCP broadcasts are not supported. All

DHCP requests must be directed.

• CSCdx70385

The session management tables may show very large summary statistics at the top of the html page

after a reset of statistics followed by a refresh. The number is in the vicinity of 4.3 billion. This is

due to the fact that the number of calls has gone down after resetting the counter to zero. We do not

currently display negative numbers for current call count statistics, so negative numbers are

erroneously being displayed as large positive numbers.

of the route; if more are configured they are not be sent.

• CSCdx70496

Occasionally a client connects and cannot receive any data back from the concentrator. If you see

this problem, it usually clears when the client disconnects and reconnects.

• CSCdx72825

If you change the default pre-fragmentation setting on the public interface on the VPN Concentrator,

pre-Release 3.6.1 clients (Unity and 3002) fail to pass large packets after a Phase 1 followed by a

Phase II rekey. To correct this problem, disconnect and re-establish the tunnel.

• CSCdx83474

The remote access session table is not properly displayed when using Netscape 4.78 or 6.2 and

viewing the admin sessions table.

• CSCdx85695

In Release 3.6.1, the VPN 3000 Concentrator software implementation changed the way that the

VPN 3000 Concentrator sends its phase 1 ID. This ID consists of a bundle of information including

IP address, protocol and port number. The change is that the port is now set to ZERO, whereas

before, it was set to 500.

Technically, this is legal because it is up to the peer’s policy to enforce whether a port=0 (ignore) is

allowed.

• CSCdx86604

Enabling bandwidth management with client tunnels already established is not supported in the Beta

2 release.

• CSCdx88812

You may see the following message on the Concentrator console when a VPN client is attempting a

connection:

“RMLogError: bad state=5/event=4 combination”