This issue I believe should be escalated and its severity raised.
We've confirmed that the bulk API /dataservice/data/device/state/Interface?count=count does in fact NOT contain interfaces for cEdge devices.
Existing client monitoring applications that rely on this endpoint no longer have visibility of [some] interfaces.
Using real-time endpoints may not be practical as a workaround. For example it may take too long to query 100's or 1000's of devices. In fact, we were explicitly instructed by Viptela/Cisco NOT to use real-time interfaces to acquire bulk data due to resource concerns.
Example
Using the Cisco DevNet system (Cisco 4D Secure SD-WAN (Viptela) Single DC v3.3) we see cEdge devices listed under /dataservice/device, but no cEdge interfaces listed under /dataservice/data/device/state/Interface.
Devices:
HOST-NAME SITE-ID DEVICE-TYPE VERSION SYSTEM-IP STATE STATUS
vManage 10 vmanage 19.2.099 10.10.10.10 green normal
vSmart-1 10 vsmart 19.2.099 12.12.12.12 green normal
vSmart-2 20 vsmart 19.2.099 22.22.22.22 green normal
vBond-1 - vbond 19.2.099 11.11.11.11 green normal
vBond-2 - vbond 19.2.099 21.21.21.21 green normal
BR1-CEDGE1 300 vedge 16.12.1e.0.66 10.3.0.1 green normal
BR1-CEDGE2 300 vedge 16.12.1e.0.66 10.3.0.2 green normal
DC1-VEDGE1 100 vedge 19.2.099 10.1.0.1 green normal
DC1-VEDGE2 100 vedge 19.2.099 10.1.0.2 green normal
Interfaces:
HOST-NAME VDEVICE-NAME IFINDEX IFNAME IP-ADDRESS SPEED-MBPS OPER-STATUS
DC1-VEDGE1 10.1.0.1 6 eth0 198.18.3.100/24 0 Up
DC1-VEDGE1 10.1.0.1 1 ge0/0 10.1.10.150/24 1000 Up
DC1-VEDGE2 10.1.0.2 3 ge0/2 100.64.2.30/30 1000 Up
vBond-1 11.11.11.11 2 system 11.11.11.11/32 0 Up
vManage 10.10.10.10 1 eth0 198.18.1.10/24 - Up
vBond-2 21.21.21.21 1 ge0/0 - 1000 Up
DC2-VEDGE2 10.2.0.2 1 ge0/1 100.64.0.14/30 1000 Up
DC1-VEDGE2 10.1.0.2 5 system - 0 Up
DC1-VEDGE2 10.1.0.2 1 ge0/0 10.1.10.250/24 1000 Up
vBond-1 11.11.11.11 1 ge0/0 - 1000 Up
vBond-1 11.11.11.11 2 system - 0 Up
DC2-VEDGE2 10.2.0.2 2 ge0/2 10.2.254.6/30 1000 Up
vBond-2 21.21.21.21 2 system - 0 Up
DC2-VEDGE1 10.2.0.1 1 ge0/1 - 1000 Up
DC1-VEDGE1 10.1.0.1 2 ge0/1 - 1000 Up
DC2-VEDGE1 10.2.0.1 3 system 10.2.0.1/32 0 Up
vSmart-2 22.22.22.22 2 system 22.22.22.22/32 - Up
DC2-VEDGE1 10.2.0.1 3 system - 0 Up
DC2-VEDGE1 10.2.0.1 4 ge0/0 10.2.10.150/24 1000 Up
vManage 10.10.10.10 2 system - - Up
DC2-VEDGE1 10.2.0.1 5 ge0/3 10.2.20.150/24 1000 Up
vSmart-1 12.12.12.12 1 eth0 - - Up
vSmart-2 22.22.22.22 1 eth0 - - Up
vManage 10.10.10.10 2 system 10.10.10.10/32 - Up
DC2-VEDGE2 10.2.0.2 5 ge0/3 10.2.20.250/24 1000 Up
vSmart-1 12.12.12.12 1 eth0 198.18.1.12/24 - Up
vSmart-2 22.22.22.22 2 system - - Up
vBond-2 21.21.21.21 1 ge0/0 198.18.1.21/18 1000 Up
vSmart-1 12.12.12.12 2 system - - Up
DC2-VEDGE1 10.2.0.1 6 eth0 198.18.3.102/24 0 Up
vSmart-2 22.22.22.22 1 eth0 198.18.1.22/24 - Up
vSmart-1 12.12.12.12 2 system 12.12.12.12/32 - Up
vManage 10.10.10.10 1 eth0 - - Up
DC2-VEDGE1 10.2.0.1 2 ge0/2 10.2.254.2/30 1000 Up
DC1-VEDGE1 10.1.0.1 2 ge0/1 100.64.0.2/30 1000 Up
DC1-VEDGE1 10.1.0.1 5 system 10.1.0.1/32 0 Up
DC1-VEDGE2 10.1.0.2 4 ge0/3 10.1.20.250/24 1000 Up
DC1-VEDGE1 10.1.0.1 3 ge0/2 - 1000 Up
DC1-VEDGE1 10.1.0.1 4 ge0/3 10.1.20.150/24 1000 Up
DC2-VEDGE2 10.2.0.2 1 ge0/1 - 1000 Up
DC2-VEDGE1 10.2.0.1 1 ge0/1 100.64.0.10/30 1000 Up
DC1-VEDGE2 10.1.0.2 5 system 10.1.0.2/32 0 Up
DC2-VEDGE2 10.2.0.2 2 ge0/2 - 1000 Up
DC1-VEDGE2 10.1.0.2 6 eth0 198.18.3.101/24 0 Up
DC1-VEDGE2 10.1.0.2 3 ge0/2 - 1000 Up
DC1-VEDGE2 10.1.0.2 2 ge0/1 100.64.0.6/30 1000 Up
DC1-VEDGE1 10.1.0.1 5 system - 0 Up
DC2-VEDGE2 10.2.0.2 3 system 10.2.0.2/32 0 Up
DC2-VEDGE2 10.2.0.2 3 system - 0 Up
vBond-2 21.21.21.21 3 eth0 - 0 Up
DC2-VEDGE2 10.2.0.2 4 ge0/0 10.2.10.250/24 1000 Up
DC2-VEDGE2 10.2.0.2 6 eth0 198.18.3.103/24 0 Up
DC1-VEDGE2 10.1.0.2 2 ge0/1 - 1000 Up
vBond-2 21.21.21.21 2 system 21.21.21.21/32 0 Up
DC2-VEDGE1 10.2.0.1 2 ge0/2 - 1000 Up
vBond-1 11.11.11.11 1 ge0/0 198.18.1.11/24 1000 Up
DC1-VEDGE1 10.1.0.1 3 ge0/2 100.64.2.26/30 1000 Up
vBond-1 11.11.11.11 3 eth0 - 0 Up
