Hi Phil,
Thanks for trying Calisti! My initial suspicion is that this sounds like it matches symptoms seen when the cluster-name auto-learned by SMM does not comply to Istio resource naming validation ("_" or "." or ":" characters). On the cluster ...
The pertinent info here is the graphql error. The license check error is thrown because the access to the backend failed (graphql error). Are there any obvious problems with the SMM related pods (`kubectl get pods -n smm-system`)?
Thanks for sharing the info, Hiro! Is there an example of setting up the device config (authgroup, device-type, etc) for being able to access both cli and snmp for the same device?
