{"type":"api","title":"Single Device Config","meta":{"id":"/apps/pubhub/media/nso-devnet/1c23a525ba18b706002c55f3caf3a12d8eae1758/10a25535-dfdf-3984-9ecc-efb87c8c69fa","info":{"title":"NSO Read-Only Interactive Docs","description":"These sample requests are Read-Only by design to work with the Always-on DevNet Sandbox.\n\nFor Read/Write requests see the Postman Collection: https://github.com/NSO-developer/cisco-nso-postman\n\nNewer NSO releases (starting with 5.3) also include a \"| display restconf\" option to more easily get API paths:\nshow running-config devices | display restconf","contact":{"email":"nso-oas-feedback@cisco.com"},"version":"4.0"},"security":[{"httpBasic":[]}],"tags":[{"name":"View IOS Device Config","description":"The NSO Device Manager loads in the data models for each device type. The IOS network element driver (NED) covers any command you may want to configure on any IOS device. If a command is not supported yet, the NED developers can add it for customers within a short period of time.\n\nDevices can also be loaded into NSO as NETCONF devices, but these examples are assuming that NSO is using the CLI based NED."},{"name":"View NX Device Config","description":"The NSO Device Manager loads in the data models for each device type. The Nexus network element driver (NED) covers any command you may want to configure on any Nexus device. If a command is not supported yet, the NED developers can add it for customers within a short period of time.\n\nDevices can also be loaded into NSO as NETCONF devices, but these examples are assuming that NSO is using the CLI based NED."},{"name":"View IOS-XR Device Config","description":"The NSO Device Manager loads in the data models for each device type. The IOS-XR network element driver (NED) covers any command you may want to configure on any IOS-XR device. If a command is not supported yet, the NED developers can add it for customers within a short period of time.\n\nDevices can also be loaded into NSO as NETCONF devices, but these examples are assuming that NSO is using the CLI based NED."},{"name":"View ASA Device Config","description":"The NSO Device Manager loads in the data models for each device type. The ASA network element driver (NED) covers any command you may want to configure on any ASA device. If a command is not supported yet, the NED developers can add it for customers within a short period of time.\n\nDevices can also be loaded into NSO as NETCONF devices, but these examples are assuming that NSO is using the CLI based NED."},{"name":"NSO Services","description":"NSO Services provide a powerful set of features to manage your configuration and expose those network services over the NSO APIs. \n\nTo learn more about NSO and services, check out the learning labs: https://developer.cisco.com/learning/tracks/get_started_with_nso"},{"name":"Device Groups / Alarms / Authgroups","description":"NSO has a number of core features that help manage the devices and application. This grouping of APIs shows a couple of common calls that beginners may be interested in: Device Groups, Authgroups, and Alarms"}],"x-parser-conf":{"serverConfig":true,"httpBasic":{"username":"developer","password":"Services4Ever"},"meta":{"useProxy":true}},"openapi":"3.0.0","servers":[{"url":"https://sandbox-nso-1.cisco.com/{basePath}","variables":{"basePath":{"default":"restconf/data"}}}],"securitySchemes":{"httpBasic":{"type":"http","scheme":"basic"}}},"spec":{"tags":["View IOS Device Config"],"summary":"Single Device Config","description":"The CLI equivalent of show running-config devices device DEVICENAME.\nThis returns both the device config and the NSO app config for that device.","operationId":"SingleDeviceConfig","parameters":[{"name":"Accept","in":"header","description":"","required":true,"style":"simple","schema":{"type":"string","example":"application/yang-data+json"}}],"responses":{"200":{"description":"","headers":{}}},"deprecated":false,"__originalOperationId":"SingleDeviceConfig","security":[{"httpBasic":[]}],"method":"get","path":"/tailf-ncs:devices/device=dist-rtr01"}}