General Netconf Behavior - Alcatel-Lucent 7450 System Management Manual

Ethernet service switch
Hide thumbs Also See for 7450:
Table of Contents

Advertisement

The <startup> datastore and <url> tags can only be used with <copy-config> and <delete-
config> and are not supported with any other operations (including <edit-config>, <get-
config>, <get>, <validate>, etc).
The :startup capability is advertised in the SR OS NETCONF server <hello>:
url supports the same options as CLI <file-url>: local urls (CF) and remote urls (ftp and tftp).
The :url capability is advertised in the SR OS NETCONF server <hello>:
The following examples show the format of each URL scheme (Note the "///" for the 'file'
URL. The 'file://localhost/...' format is not supported.):
The <startup> datastore is identified by following the bof primary-config/secondary-config/
tertiary-config paths as configured by the operator. <startup> is effectively an alias for a url (a
special url used for system startup) with some extra resiliency (primary/secondary/tertiary).
The bof is not considered as part of any config datastore.
Debug config (such as debug mirrors, or anything saved with "admin debug-save") is not
considered as part of any config datastore.
Lawful Interception configuration information is contained in the <running> datastore but is
not saved in the <startup> datastore. The equivalent of the CLI "li save" command is available
in an <edit-config>.
Configuration changes done via NETCONF are subject to CLI Rollback (revert, save, etc) and
are included in the configuration when the operator performs an "admin save" in CLI.

General NETCONF behavior

Pressing Ctrl-C in a NETCONF request will immediately terminate the session.
In the rpc tag, the only allowable namespace or prefix declaration is for the standard
NETCONF "urn:ietf:params:xml:ns:netconf:base:1.0" namespace. If any other namespace is
7450 ESS System Mangement Guide
<capability>urn:ietf:params:netconf:capability:startup:1.0</capability>
<capability>urn:ietf:params:netconf:capability:url:1.0?scheme=ftp,tftp,file</
capability>
<target><url>ftp://name:passwd@a.b.c.d/usr/fredf/myfile.cfg</url></target>
<target><url>tftp://name:passwd@a.b.c.d/usr/fredf/myfile.cfg</url></target>
<target><url>file:///cf3:/myfiles/myfile.cfg</url></target>
Note: The following format is also supported (no 'file:///'): <target><url>cf3:/myfiles/
myfile.cfg</url></target>
NETCONF
Page 341

Advertisement

Table of Contents
loading

Table of Contents