Hi, Using the API provided in answer to my previous question.
https://{{vmanage}}:{{port}}/dataservice/data/device/state/CEdgeInterface?count=5000We've noticed that the figures for interface speed reported by the CEdge devices is incorrect. vEdges are fine. This incorrect value is seen in the APU and in the vManage web console.
For example: "speed-mbps": "1024000000", can be seen in the full response from the Sandbox DevNet env below. As the property name states it should be in mbps, but instead it's got something close to a bps figure, though the conversion is neither 1 gigabit (1,000,000,000) nor 1 gibibit (1,073,741,824).
I know we could workaround this and likely determine the correct speed, but this would break if/when the bug was fixed.
Does anyone know if this is fixed in a newer version than that on the DevNet Sandbox, vManage: 19.2.2 CSR1000v: 16.12.3.0.3752 ? If not, how best to go about getting this fixed. Without this being resolved we're not going to be able to use this value to calculate interface utilisation correctly.
{
"recordId": "0:CEdgeInterfaceNode:1605020429927:242",
"vdevice-name": "10.10.1.15",
"rx-errors": 0,
"ipv6-tcp-adjust-mss": "0",
"if-admin-status": "if-state-up",
"tx-errors": 0,
"description": "internet-link",
"@rid": 431,
"ifname": "GigabitEthernet4",
"interface-type": "iana-iftype-ethernet-csmacd",
"if-oper-status": "if-oper-state-ready",
"ifindex": "4",
"ipv4-tcp-adjust-mss": "0",
"rx-packets": 35221,
"bia-address": "52:54:00:0b:ca:ad",
"createTimeStamp": 1605020429927,
"vpn-id": "0",
"vdevice-host-name": "site2-cedge01",
"ipv4-subnet-mask": "255.255.255.252",
"mtu": "1500",
"rx-drops": 0,
"tx-drops": 0,
"ip-address": "10.10.23.46",
"hwaddr": "52:54:00:0b:ca:ad",
"speed-mbps": "1024000000",
"vdevice-dataKey": "10.10.1.15-0-GigabitEthernet4-10.10.23.46-52:54:00:0b:ca:ad",
"vmanage-system-ip": "10.10.1.15",
"tx-octets": 10404769,
"tx-packets": 37511,
"rx-octets": 6442185,
"lastupdated": 1605023090041
},
