--- title: "Manage Sessions" slug: "managing-sessions-lx" tags: ["session types", "management", "assurance sensor 24.07", "Assurance Sensors", "Assurance Sensor LX-S"] updated: 2024-08-07T18:02:07Z published: 2024-08-07T18:02:07Z canonical: "docs.crossworkassurance.cisco.com/managing-sessions-lx" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.crossworkassurance.cisco.com/llms.txt > Use this file to discover all available pages before exploring further. # Managing Sessions The unit’s management system provides multiple configurable management sessions to allow multiple users to control the unit. To view current sessions, access the page **System ▶Session ▶Management**. #### System ▶Session ▶Management ![image.png](https://cdn.document360.io/01d1de5e-a375-4fbc-aa82-666ac04c2113/Images/Documentation/image-4NXW8UE4.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A58%3A18Z&se=2026-11-16T06%3A58%3A18Z&sr=b&sp=r&sig=Cji8fopf%2BdRZC4n8c0d%2Fqb6ESDZdQsAlXG5YIqw1CVU%3D) For more information on specific values, refer to the following table. **Current Sessions (System ▶Session ▶Management)** | Parameter | Description | | --- | --- | | Session ID | Session identification number. | | Type | Interface the session is using. | | Host | IP address of the management station for that session. | | Username | The user account that is currently logged in. An asterisk ( * ) appears beside your own session. | | Uptime | How long the session has been active. | | Terminate | Selecting one or more sessions then clicking Terminate forces a log out. | ### Terminating a User Session It may be sometimes necessary to terminate one or more sessions. --- ***Note:** You need the right privileges to terminate a session. Refer to "Managing Users and Privileges".* --- **To terminate a session** 1. Access the page **System ▶Session ▶Management.** 2. Select the session you want to terminate by checking the **Terminate** check box. 3. Click the **Terminate** button. The session is immediately terminated and the selected user is logged out. ### Configuring Session Options Use this page to configure the following session-related parameters: - The maximum number of CLI sessions allowed - The maximum number of web interface sessions allowed - The maximum number of total sessions (CLI and web combined) - The maximum number of concurrent NETCONF sessions that can be supported - The maximum number of seconds that a NETCONF session can remain idle before it is automatically logged out - The CLI timeout value - The file transfer timeout value, to ensure firmware updates and configuration maintenance entities have sufficient time to load successfully - The Management Web Interface timeout value - Whether or not a telnet server is enabled - The authentication order when users log in to the system **To configure session parameters** 1. Access the page **System ▶Session ▶Configuration**. 2. Update the various session configuration parameters, then click **Apply**. #### System ▶Session ▶Configuration ![image.png](https://cdn.document360.io/01d1de5e-a375-4fbc-aa82-666ac04c2113/Images/Documentation/image-SPLGUT1D.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A58%3A18Z&se=2026-11-16T06%3A58%3A18Z&sr=b&sp=r&sig=mLiahVfBX78fVYVwt9qV8rwcB5eII9Na5BBYEKzjRQw%3D) For more information on specific parameters, refer to the following tables. **Session Configuration (System ▶Session ▶Configuration)** **General** | Parameter | Description | | --- | --- | | Max CLI Sessions | The maximum number of concurrent CLI sessions that can be supported. | | Max WEB Sessions | The maximum number of concurrent Management Web Interface sessions that can be supported. | | Max NETCONF Sessions | The maximum number of concurrent NETCONF sessions that can be supported. ***Note:** Currently, the maximum number of concurrent NETCONF sessions is one.* | | Max Total Sessions | The total number of CLI and Management Web Interface sessions | | that can be supported. | | | CLI Timeout | The maximum number of seconds that a CLI session can remain idle before it is automatically logged out. | | File Transfer Timeout | The maximum number of seconds that must elapse before a file transfer (firmware upgrade, etc.) is automatically terminated. Minimum value is 900 (15 minutes); maximum value is 3600 (60 minutes). Default value is 1800 (30 minutes). | | WEB Timeout | The maximum number of seconds that a Management Web Interface session can remain idle before it is automatically logged out. | | NETCONF Timeout | The maximum number of seconds that a NETCONF session can remain idle before it is automatically logged out. | | Telnet Server | The telnet server on the unit may be enabled or disabled. | **Authentication** | Parameter | Description | | --- | --- | | Order | The authentication method to use in order of availability. Possible values are: - **Local:** Validate locally only - **RADIUS:** Validate on the RADIUS server only - **Local-RADIUS:** Validate locally first; if the validation does not succeed, then validate on the RADIUS server - **RADIUS-Local:** Validate on the RADIUS server first, and if the validation does not succeed, then validate on local server - **Strict RADIUS-Local:** Validate on the RADIUS server first. If the authentication fails, access is denied. The fall back to local only occurs when the RADIUS authentication times out. - **TACACS+:** Validate on the TACACS+ server only - **Local-TACACS+:** Validate locally first; if the validation does not succeed, then validate on the TACACS+ server - **TACACS+-Local:** Validate on the TACACS+ server first, and if the validation does not succeed, then validate on the local server - **Strict TACACS+-Local:** Validate on the TACACS+ server(s) first. If the authentication fails, access is denied. The fall back to local only occurs when the TACACS+ authentication process times out. ***Notes:*** *If you plan on using a remote server for authentication, you should confirm that the remote system is functional before removing the local authentication. If you remove local authentication and the remote system is not working, you will lose access to the unit.* *To ensure that authentication is working on the remote server, log in then out from the unit, then access the **System ▶Agent ▶Syslog** page. You should see a syslog message indicating a successful login attempt*. | **© 2026 Cisco and/or its affiliates. All rights reserved.** For more information about trademarks, please visit: [Cisco trademarks](https://www.cisco.com/c/en/us/about/legal/trademarks.html)[](https://www.cisco.com/c/en/us/about/legal/trademarks.html) For more information about legal terms, please visit: [Cisco legal terms](https://www.cisco.com/c/en/us/about/legal/terms-conditions.html)