Why the idle-timeout parameter configured in the user interface view does not take effect

20

The idle-timeout parameter specifies how long the system waits to disconnect an online user if the user does not perform any operation. If a user does not perform any operation in a specified period, the system disconnects the user to release resources.
Set the idle-timeout parameter for the users who go online through AAA local authentication in either of the following ways:

Run the local-user user-name idle-timeout minutes [ seconds ] command in the AAA view.
Run the idle-timeout minutes [ seconds ] command in the user interface view.

By default, a user is disconnected if the user does not perform any operation within 10 minutes.
The idle-timeout parameter set in the AAA view has a higher priority than that set in the user interface view.
Therefore, the idle-timeout parameter set in the user interface view does not take effect because the idle-timeout parameter has been set in the AAA view.

Other related questions:
Why the idle-timeout parameter configured in the user view on an S series switch does not take effect
The idle-timeout parameter configured on an S series switch (except the S1700 switch) specifies how long the system waits to disconnect an online user if the user does not perform any operation. If a user does not perform any operation in a specified period, the system disconnects the user to release resources. Configure the idle-timeout parameter using either of the following methods: �?Run the local-user user-name idle-timeout minutes [ seconds ] command in the AAA view. �?Run the idle-timeout minutes [ seconds ] command in the user view. The idle-timeout parameter set in the AAA view has a higher priority than that set in the user view. Therefore, the idle-timeout parameter set in the user view does not take effect because the idle-timeout parameter has been set in the AAA view.

Why does not the MTU configuration take effect on tunnel interfaces of a switch
The maximum transmission unit (MTU) configuration is valid for packets sent to and from the control plane, but invalid for packets directly forwarded by hardware. To limit the size of packets forwarded by hardware, configure the MTU on physical interfaces.

Why the MAC-VLAN does not take effect
MAC address-based VLANs take effect only to untagged packets. If an MAC address-based VLAN does not take effect, check whether the incoming packets contain VLAN tags.

Why does the CPCAR rate limit configuration not take effect
The CPU committed access rate (CPCAR) is configured in the attack defense policy view. The CPCAR takes effect only when the attack defense policy is applied on the main control board or interface board on the local area network (LAN) side.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top