Yang Data Models - Alcatel-Lucent 7450 System Management Manual

NETCONF in SR OS
SR OS supports both a CLI content layer and an XML-based content layer for NETCONF.

YANG Data Models

The SR OS NETCONF XML content layer configuration schema is described in a set of
Alcatel-Lucent proprietary YANG modules. The configuration modules are advertised in the
SR OS NETCONF server hello.
The configuration YANG data model closely aligns to the SR OS CLI configuration tree
structure and commands.
A set of YANG modules are published and distributed as part of an SR OS image in the cflash/
support directory (along with files like dictionary-freeradius.txt and stats.dtd).
The following areas of CLI do not have equivalent YANG data models:
Transport and Sessions
SSH transport is supported on TCP port 830 with IPv4 or IPv6 in the Base routing instance.
NETCONF SSH sessions (like CLI, SCP and sFTP sessions) are subject to any configurable
and non-configurable session limits; for example, inbound-max-sessions. Both the SSH server
and NETCONF protocol must be enabled in the router configuration in order to use
NETCONF. NETCONF sessions can be disconnected using the "admin disconnect"
command.
NETCONF sessions do not time out automatically and are not subject to the CLI session
timeout. Operators can disconnect sessions manually if they need to.
A client establishing a NETCONF session must log into the router so user accounts must exist
for NETCONF on the SR. A new access type 'netconf' is provided. The user must be
configured with both 'console' and 'netconf' access.
Only authentication via the local user database is supported for NETCONF users/sessions (no
RADIUS or TACACS+ authentication). Access to various CLI config and show commands
(authorization) via NETCONF is controlled through the profile assigned to the user that is
used to authenticate the underlying SSH session.
Access to LI commands is based on the "access li" setting for the user.
If a NETCONF request attempts to execute a CLI command which is outside the scope of its
access profile, an error response will be sent. For example:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
Page 336
• bof
• admin, tools, debug, or show branches
7450 ESS System Mangement Guide