HTTP GET for /2.0/device/fqname/{fqname}/configversion/{externalid}/nativeconfiguration

When the NSM client user requests the /device/fqname/{fqname}/configversion/{externalid}/nativeconfiguration URI using the GET method, a copy of the native configuration of the device that matches the device fully qualified name and configuration version external ID entered is returned. These URIs require version information (2.0) in the URI.

Input parameters

{ fqname } ,

{externalid}

If the fqname contains forward slashes, these must be escaped using the %252F value as shown in the example below.

Available HTTP Headers

Accept: application/json

Accept: text/xml

Sample request

http://www.example.com:16310/nsm/2.0/device/fqname/ITNCM%252FEMULATED%252Femulcli4-17/configversion/2016-05-11T10:09:15.615+0000/nativeconfiguration

Sample response

XML

device>
<configVersion>
<nativeConfiguration>
version 12.2
no service timestamps debug uptime
no service timestamps log uptime
no service password-encryption
service compress-config
!
hostname bfo2610a
!
boot system flash dummy;
exec-timeout 0 0
transport input pad v120 telnet rlogin udptn
!
ntp clock-period 17208292
end
</nativeConfiguration>
</configVersion>
</device>

JSON

{
    "configVersion": {
        "nativeConfiguration": "version 12.2
no service timestamps debug uptime
no service timestamps log uptime
no service password-encryption
service compress-config
!
hostname bfo2610a
!
boot system flash dummy;
exec-timeout 0 0
transport input pad v120 telnet rlogin udptn
!
ntp clock-period 17208292
end”
}
}

XML response details

Table 1. Response details
Tag	Type	Description
`configVersion`	Container tag	Specifies the configuration version
`nativeConfiguration`	Container tag	Specifies the native configuration for the requested device configuration version. The sample response shows a sample device configuration. The full device configuration is not documented because it is large.