While NETCONF (and RESTCONF) do provide some operational data, it isn't an exact match to what you see in "show" commands. However, these protocols do provide for some operational data in a structured (i.e., JSON or XML) format. For example, our devices expose all SNMP MIB data via YANG data models, so they are accessible via NETCONF or RESTCONF. The attached Python script will dump the contents of the CDP neighbor table in JSON (via NETCONF). You could use this to then build the "show cdp neighbor" output.
{
"data": {
"@xmlns": "urn:ietf:params:xml:ns:netconf:base:1.0",
"@xmlns:nc": "urn:ietf:params:xml:ns:netconf:base:1.0",
"CISCO-CDP-MIB": {
"@xmlns": "urn:ietf:params:xml:ns:yang:smiv2:CISCO-CDP-MIB",
"cdpCacheTable": {
"cdpCacheEntry": [
{
"cdpCacheIfIndex": "1",
"cdpCacheDeviceIndex": "2",
"cdpCacheAddressType": "ip",
"cdpCacheAddress": "wKgBJA==",
"cdpCacheVersion": "Cisco IOS Software, C3560 Software (C3560-IPSERVICESK9-M), Version 15.0(2)SE10, RELEASE SOFTWARE (fc2)\nTechnical Support: http://www.cisco.com/techsupport\nCopyright (c) 1986-2016 by Cisco Systems, Inc.\nCompiled Mon 18-Jul-16 02:05 by prod_rel_team",
"cdpCacheDeviceId": "jabberwocky.marcuscom.com",
"cdpCacheDevicePort": "FastEthernet0/11",
"cdpCachePlatform": "cisco WS-C3560V2-24TS",
"cdpCacheCapabilities": "AAAAKQ==",
"cdpCacheVTPMgmtDomain": "MARCUSCOM",
"cdpCacheNativeVLAN": "1",
"cdpCacheDuplex": "fullduplex",
"cdpCacheLastChange": "1132114"
},
{
"cdpCacheIfIndex": "8",
"cdpCacheDeviceIndex": "1",
"cdpCacheAddressType": "ip",
"cdpCacheAddress": "wKgBLg==",
"cdpCacheVersion": "1",
"cdpCacheDeviceId": "00180a974f01",
"cdpCacheDevicePort": "Port 3",
"cdpCachePlatform": "MS220-24P",
"cdpCacheCapabilities": "AAAACA==",
"cdpCacheVTPMgmtDomain": null,
"cdpCacheNativeVLAN": "1",
"cdpCacheDuplex": "unknown",
"cdpCacheLastChange": "1082893"
}
]
}
}
}
}
The same can be done with the routing table and the ietf-routing module:
{
"data": {
"@xmlns": "urn:ietf:params:xml:ns:netconf:base:1.0",
"@xmlns:nc": "urn:ietf:params:xml:ns:netconf:base:1.0",
"routing": {
"@xmlns": "urn:ietf:params:xml:ns:yang:ietf-routing",
"routing-instance": [
{
"name": "Mgmt-vrf",
"interfaces": {
"interface": [
"Loopback0",
"GigabitEthernet0/0"
]
},
"routing-protocols": {
"routing-protocol": {
"type": "static",
"name": "1",
"static-routes": {
"ipv4": {
"@xmlns": "urn:ietf:params:xml:ns:yang:ietf-ipv4-unicast-routing",
"route": {
"destination-prefix": "0.0.0.0/0",
"next-hop": {
"next-hop-address": "192.168.1.1"
}
}
}
}
}
}
},
{
"name": "default",
"description": "default-vrf [read-only]",
"interfaces": null,
"routing-protocols": {
"routing-protocol": {
"type": "static",
"name": "1"
}
}
}
]
}
}
}
