![]() ![]() Access to various CLI configuration and show commands (authorization) through NETCONF is controlled through the assigned user profile that is used to authenticate the underlying SSH session. Only authentication through the local user database is supported for NETCONF users (no RADIUS or TACACS+ authentication). The user must be configured with both console and netconf access. NETCONF user accounts must exist on the SR OS to enable a client establishing a NETCONF session to log into the router. Operators can manually disconnect sessions using the admin disconnect command. Unlike CLI sessions, NETCONF sessions are not subject to automatic session timeout. The SSH server and NETCONF protocol must be enabled in the router configuration to use NETCONF. NETCONF SSH sessions (similar to CLI, Secure Copy (SCP), and SSH File Transfer Protocol (sFTP) sessions) are subject to any configurable and non-configurable session limits for example, inbound-max-sessions. SSH transport for NETCONF is supported on TCP port 830 with IPv4 or IPv6 in the “Base” routing instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |