With the product service models (intent types) provided in the artifacts section of the Nokia Support Portal are documentation folders, which contain SR OS CLI configurations for both model and classic modes, based on the product artifact YANG model. Both raw CLI and JSON/HTML formats are included for ease of use. These files can be used to determine the attributes that may be available to you when creating services, depending on the types of nodes in your network. The contents of this folder depends on the complexity of the related service model and includes:

• intent.html — an HTML tree view of the attributes included in the product L3 VPN service intent

• payload1.NodeTypeAndVersion.mdcli.json — CLI output, in JSON format, of the attributes supported on model-driven nodes

• payload1.NodeTypeAndVersion.mdcli.txt — CLI output, in plain text, of the attributes supported on model-driven nodes

• payload1.NodeTypeAndVersion.cli.text — CLI output, in plain text, of the attributes supported on classically-managed nodes

Note: The procedures in this document assume that the Nokia-provided intent type artifacts have been used to configure service templates, and that those templates will be used to configure services. As such, the parameters and options documented in this guide are limited to what is available when using those intent types and may not allow for certain capabilities - such as mutivendor management - that may be enabled by custom intent types. Please consult Nokia for assistance when using intent types other than those described here.