Closed willowhawk-k closed 7 months ago
logs here are from 4.1.0-Enterprise_Base
Hi @willowhawk-k, this Github organization is for the Community version of SONiC. To get support for Enterprise SONiC, please contact Dell support. Wildcard subscription has not yet been implemented in Community SONiC. Additionally, you may want to try the latest version of Enterprise SONiC, 4.2.0, and see if your issues are addressed in that latest version.
A similar query for counters does the same thing
I'm not sure if you are doing an ON_CHANGE or SAMPLE based subscription, but just FYI, ON_CHANGE functionality is not supported for all objects, counters being one of them. It would be too verbose in an operational setting.
@sneelam20 please close this issue as it's not going to be relevant to the code in the sonic-net Github organization. (I don't have privileges to close issues)
Thanks. Closed.
We’ve come across what I believe to be a bug in the SONiC handling of gNMI requests using the OpenConfig query standards.
The following confirms wildcards are valid query strings (from https://openconfig.net/docs/gnmi/gnmi-path-conventions/): Wildcards in paths · Wildcards are allowed to indicate all elements at a given subtree in the schema – these are used particularly for telemetry subscriptions or Get requests. A single-level wildcard is indicated by specifying the name of a PathElem to be an asterisk (*). A multi-level wildcard is indicated by specifying the name of a PathElem to be the string ... We issue a subscription request to the following gNMI path, among others:
openconfig-interfaces:interfaces/interface[name=*]/ethernet/state
When this is done, we see syslog ERROR level messages that look like this:
A similar query for counters does the same thing:
openconfig-interfaces:interfaces/interface[name=*]/state/counters
When this is done, we see syslog ERROR level messages that look like this:
This is reproducible on multiple versions of SONiC, logs here are from 4.1.0-Enterprise_Base.