message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> NETCONF Kill Session During a session conflict or client misuse of the global lock, NETCONF sessions can be monitored via the show netconf-yang sessions command, and non-responsive sessions can be cleared using the clear netconf-yang session command. The clear netconf-yang session command clears both the NETCONF lock and the configuration lock. A request will force a NETCONF session to terminate. When a NETCONF entity receives a request for an open session, it stops all operations in process, releases all locks and resources associated with the session, and closes any associated connections.
A request requires the session-ID of the NETCONF session that is to be terminated. If the value of the session-ID is equal to the current session ID, an invalid-value error is returned. If a NETCONF session is terminated while its transaction is still in progress, the data model infrastructure will request a rollback, apply it to the network element, and trigger a synchronization of all YANG models. If a session kill fails, and a global lock is held, enter the clear configuration lock command via the console or vty. At this point, the data models can be stopped and restarted.
NETCONF-YANG SSH Server Support NETCONF-YANG uses the IOS Secure Shell (SSH) Rivest, Shamir, and Adleman (RSA) public keys to authenticate users as an alternative to password-based authentication. For public-key authentication to work on NETCONF-YANG, the IOS SSH server must be configured. To authenticate users to the SSH server, use one of the RSA keys configured by using the ip ssh pubkey-chain and user commands. NACM is a group-based access control mechanism. When users are authenticated, they are automatically placed in an NACM privilege group based on their configured privilege level. Users can also be manually placed in other user-defined groups. The default privilege level is 1.
There are 16 privilege levels, PRIV00 to PRIV15. If a user authenticates via the public-key; but does not have a corresponding Authentication, Authorization, and Accounting (AAA) configuration, this user is rejected. If a user authenticates via a public-key; but the AAA configuration for NETCONF is using a AAA source other than the local, this user is also rejected. Local and TACACS+ AAA authorization are supported. Token-based RESTCONF authentication is not supported. SSH user certificates are not supported. NETCONF SSH Algorithms The NETCONF-SSH server configuration file contains the list of all supported algorithms.
From Cisco IOS XE Dublin 17.12.1, you can enable or disable these algorithms at runtime by using commands or YANG models. Model-Driven Programmability NETCONF Kill Session Programmability Configuration Guide, Cisco IOS XE 17.16.x 174