Vyatta Network OS Documentation

Learn how to install, configure and operate the Vyatta NOS, which helps drive our virtual networking & physical platforms portfolio.

Supported NETCONF operations

Information about NETCONF operations that Vyatta NOS supports.

Vyatta NOS supports these top-level operations, via NETCONF RPCs.

For reference, where you have a TACACS+ server, Vyatta NOS also shows the audit string for each command that it receives. In some cases, Vyatta NOS will send multiple strings/arguments when you make a commit operation.

<get-schema>

Get a list of the YANG schemas that the device supports. See RFC 6022, 3.1 The <get-schema> Operation.

TACACS+ audit string: Not audited.

<lock>

Lock the NETCONF session (candidate configuration only). See RFC 6241, 7.5 <lock>.

TACACS+ audit string: Not audited.

<unlock>

Unlock the NETCONF session. See RFC 6241, 7.5 <lock>.

TACACS+ audit string: Not audited.

<get>

Get the running configuration and device state information. See RFC 6241, 7.7 <get>.

TACACS+ audit string: Not audited.

<get-config>

Get the configuration from the specified datastore. See RFC 6241, 7.1 <get-config>.

TACACS+ audit string: Not audited.

<edit-config>

Edit the configuration that is in the specified datastore. See RFC 6241, 7.2 <edit-config>.

TACACS+ audit string: set/delete for each line of the equivalent CLI configuration, with following strings for each element in the CLI command.

<delete-config>

Delete the configuration from the specified datastore. See RFC 6241, 7.4 <delete-config>.

TACACS+ audit string: .

<validate>

Validate the configuration. The configuration may be either candidate/running, or provided by the caller. See RFC 6241, 8.6 Validate Capability.

TACACS+ audit string: validate.

<copy-config>

Copy the configuration. See RFC 6241, 7.3 <copy-config>.

TACACS+ audit string: load, encoding, xml, copy-config.

<commit>

Copy changes in the candidate configuration datastore to the running configuration datastore.

A commit may be either of these:

  • Unconditional — that is, not subject to further confirmation.
  • Conditional — that is, subject to further confirmation. In this case, you send an initial 'confirmed commit' with a timeout. Then you need to follow this with either an unconditional commit to confirm it, or an explicit cancel-commit operation to revert it.
Note: Unfortunately, the 'confirmed commit' terminology from RFC 6241 is a bit confusing. 'Unconditional' and 'conditional' are not terms from the RFC — we just use them for explanation.

In the absence of either of these, Vyatta NOS will automatically revert the initial commit when the timeout expires. See RFC 6241, 8.3.4.1 <commit>.

TACACS+ audit string: commit for unconditional commit and confirmed commit.

<cancel-commit>

Cancel an ongoing confirmed commit. See RFC 6241, 8.4.4.1 <cancel-commit>.

TACACS+ audit string: cancel-commit.

<discard-changes>

Discard uncommitted changes to the candidate configuration. See RFC 6241, 8.3.4.2 <discard-changes>.

TACACS+ audit string: discard.

<close-session>

Request graceful termination of the current NETCONF session. See RFC 6241, 7.8 <close-session>.

TACACS+ audit string: Not audited.

Custom YANG RPCs

YANG RPCs as implemented in YANG modules. See RFC 6241, 4.1 <rpc> Element.

TACACS+ audit string: Not audited.