Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Thanks @James Tuddenham , good catch. @sbaker42511 this is actually a known-issue that stems from a requirement on Kubernetes side ( RFC 1123) and should be addressed in a future release for IQ Link. If you return to the Admin console screen you can...
Hi @sbaker42511 ,
Could you share a screenshot of the error presented? Can you also confirm if you are navigating to the FQDN provided by the admin console screen? Does this address correctly reflect the A, PTR, and domain records you've configured i...
Hi, thanks for the question.
Currently, IQ Link v1.1.0 only supports specified devices via hostname or IP Address. This information can be submitted either via the 'assets' CSV file (Available via System Settings -> Connection Management -> Direct Co...
Hi Ed,
I often refer people to the below Smart Call Home document for a general outline of the capability:https://www.cisco.com/c/dam/en/us/td/docs/switches/lan/smart_call_home/SCH_Deployment_Guide.pdf
For specific features regarding MDS devices,...
I see the PKI logs are reflecting a failure to validate the SLA-Trustpoint (aka the Smart License Agent trustpoint) and I think a number of issues arise when a device is unable to complete a CRL revocation check. As a workaround you can apply the bel...
