|
|
This screen shows comprehensive statistics for all active sessions on the VPN Concentrator.
You can also click the name of a session to see detailed parameters and statistics for that session. See Administration | Sessions | Detail.
To reset, or start anew, the screen contents, click Reset. The system temporarily resets a counter for the chosen statistics without affecting the operation of the device. You can then view statistical information without affecting the actual current values of the counters or other management sessions. The function is like that of a vehicle's trip odometer, versus the regular odometer.
To restore the screen contents to their actual statistical values, click Restore. This icon displays only if you previously clicked the Reset icon.
To update the screen and its data, click Refresh. The date and time indicate when the screen was last updated.
Choose a group from the menu to monitor statistics for that group only. The default is --All-- which displays statistics for all groups.
These active labels let you log out all active sessions of a given tunnel type at once:
To log out the sessions, click the appropriate label. The Manager displays a prompt to confirm the action.
 |
Caution This action immediately terminates all sessions of the given tunnel type. There is no user warning or undo. |
The Manager refreshes the screen after it terminates the sessions.
This table shows summary totals for LAN-to-LAN, remote access, and management sessions.
A session is a VPN tunnel established with a specific peer. In most cases, one user connection = one tunnel = one session. However, one IPSec LAN-to-LAN tunnel counts as one session, but it allows many host-to-host connections through the tunnel.
The number of IPSec LAN-to-LAN sessions that are currently active.
The number of PPTP, L2TP, IPSec remote-access user, L2TP over IPSec, and IPSec through NAT sessions that are currently active.
The number of administrator management sessions that are currently active.
The total number of sessions of all types that are currently active.
The highest number of sessions of all types that were concurrently active since the VPN Concentrator was last booted or reset.
The maximum number of concurrently active sessions permitted on this VPN Concentrator. This number is model-dependent, for example: model 3060 = 5000 sessions.
The total cumulative number of sessions of all types since the VPN Concentrator was last booted or reset.
This table shows parameters and statistics for all active IPSec LAN-to-LAN sessions, sorted alphanumerically by connection name. Each session here identifies only the outer LAN-to-LAN connection or tunnel, not individual host-to-host sessions within the tunnel.
Click these active links to go to the other session tables on this Manager screen.
The name of the IPSec LAN-to-LAN connection.
To display detailed parameters and statistics for this connection, click this name. See the Administration | Sessions | Detail screen.
The IP address of the remote peer VPN Concentrator or other secure gateway that initiated this LAN-to-LAN connection.
See Table 2-1 for definitions of these parameters.
This table shows parameters and statistics for all active remote-access sessions. Each session is a single-user connection from a remote client to the VPN Concentrator. Remote-access sessions include PPTP, L2TP, IPSec remote-access user, L2TP over IPSec, and IPSec through NAT sessions.
Click a column header in this table to sort the table entries in ascending alphanumeric order, using that column as the sort key field.
Click these active links to go to the other session tables on this Manager screen.
The username or login name for the session. The field shows Authenticating... if the remote-access client is still negotiating authentication. If the client is using a digital certificate for authentication, the field shows the Subject CN or Subject OU from the certificate.
To display detailed parameters and statistics for this session, click this name. See the Administration | Sessions | Detail screen.
For the indicated user, this column shows the Assigned IP Address and the Public IP Address stacked in that order.
 |
Note If the remote client is a VPN 3002 using network extension mode, this field shows the network address of the private interface of the 3002. Therefore, you cannot ping the address. |
The group name of the client for this remote-access session. Clicking the column head for Group sorts the table entries in ascending alphanumeric order and also sorts the usernames within each group in ascending alphanumeric order.
The client type of connected clients, and, when available, the associated operating system, sorted by username. For example:
| Client Type | Operating System |
|---|---|
The software version number (for example, rel. 3.6,_int 50) for connected clients, sorted by username.
See Table 2-1 for definitions of these parameters.
This table shows parameters and statistics for all active administrator management sessions on the VPN Concentrator.
Click these active links to go to the other session tables on this Manager screen.
The administrator username or login name for the session.
The lock icon indicates the administrator who has the configuration lock, that is, the person who has the right to make changes to the active system configuration. See the "Configuration locked by" section of this chapter.
The IP address of the manager workstation that is accessing the system. Local indicates a direct connection through the Console port on the system.
See Table 2-1 for definitions of these parameters.
Table 2-1 Parameter definitions for Administration | Administer Sessions Screen
The administrator (IP address or Console) who has the right to make changes to the active system configuration.
The configuration is locked by the administrator who first makes a change to the active (running) configuration. That administrator holds the lock until logout, or until the Session Idle Timeout period expires (see the Administration | Access Rights | Access Settings screen). For example, an administrator who is just viewing and refreshing statistics on a Monitoring screen for longer than the timeout period, loses the lock.
These Manager screens show detailed parameters and statistics for a specific remote-access or LAN-to-LAN session. The parameters and statistics differ depending on the session protocol. There are unique screens for:
The Manager displays the appropriate screen when you click a highlighted connection name or username on the Administration | Administer Sessions screen. Figure 2-3 shows an example of one kind of detail screen. Depending on the type of connection you select, your detail screen might look somewhat different from the example shown. But, each session detail screen shows three tables: summary data, bandwidth statistics, and detail data. The summary data echoes the session data from the Administration | Administer Sessions screen. The Bandwidth Statistics table shows the effect of bandwidth policing on the session. The session detail table shows all the relevant parameters for each session and subsession.
See Table 2-2 for definitions of the possible session detail parameters, in alphabetical order.
Table 2-2 Parameter Definitions for Administration | Administer Sessions | Detail Screens
| Parameter | Definition |
|---|---|
The private IP address assigned to the remote client for this session. This is also known as the "inner" or "virtual" IP address, and it lets the client appear to be a host on the private network. |
|
The total number of bytes received from the remote peer or client by the VPN Concentrator. |
|
The total number of bytes transmitted to the remote peer or client by the VPN Concentrator. |
|
The data compression algorithm this session is using. LZS is the data compression algorithm used by IPComp. MPPC uses LZ. |
|
The algorithm and key size used to generate IPSec SA encryption keys. |
|
The elapsed time (HH:MM:SS) between the session login time and the last screen refresh. |
|
The mode for applying IPSec ESP (Encapsulation Security Payload protocol) encryption and authentication, in other words, what part of the original IP packet has ESP applied. |
|
The data encryption algorithm this session is using, if any. |
|
The algorithm used to create a hash of the packet, which is used for IPSec data authentication. |
|
The elapsed time (HH:MM:SS) between the last communication activity on this session and the last screen refresh. |
|
The IKE (IPSec Phase 1) mode for exchanging key information and setting up SAs: Aggressive or Main. |
|
The total number of IKE (IPSec Phase 1) sessions; usually 1. These sessions establish the tunnel for IPSec traffic. |
|
The IP address of the remote peer VPN Concentrator or other secure gateway that initiated the IPSec LAN-to-LAN connection. |
|
The total number of IPSec (Phase 2) sessions, which are data traffic sessions through the tunnel. Each IPSec remote-access session might have two IPSec sessions: one showing the tunnel endpoints, and one showing the private networks reachable through the tunnel. |
|
The total number of user sessions through this L2TP or L2TP / IPSec tunnel; usually 1. |
|
The IP address (and wildcard mask) of the destination host (or network) for this session. |
|
The date and time (MMM DD HH:MM:SS) that the session logged in. Time is displayed in 24-hour notation. |
|
The Diffie-Hellman algorithm and key size used to generate IPSec SA encryption keys using Perfect Forward Secrecy. |
|
The total number of user sessions through this PPTP tunnel; usually 1. |
|
The public IP address of the client for this remote-access session. This is also known as the "outer" IP address. It is typically assigned to the client by the ISP, and it lets the client function as a host on the public network. |
|
The lifetime in kilobytes of the IPSec (IKE) SA encryption keys. |
|
The lifetime in seconds of the IPSec (IKE) SA encryption keys. |
|
The IP address (and wildcard mask) of the remote peer (or network) that initiated this session. |
|
The Scalable Encryption Module that is handling cryptographic processing for this session. |
|
An identifier for session components (subsessions) on this screen. With IPSec, there is one identifier for each SA. |
|
The effect of bandwidth management on this session's traffic rate. |
|
The effect of bandwidth management on this session's traffic volume. Note The Bandwidth Management Traffic Volume byte counters include the outer IP tunnel header and MAC layer and therefore show larger totals than those shown for user statistics. |
|
The UDP port number used in an IPSec through NAT connection. |
|
The username or login name for the session. If the client is using a digital certificate for authentication, the field shows the Subject CN or Subject OU from the certificate. |
Posted: Fri Apr 18 18:44:53 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
