I configured a HTTPS-HEAD Keepalive in a GSS that fails even if the server responds correctly. The problem could be that the server responds with a not trusted certificate. Does anyone know what the GSS's behaviour is in this particulal case?
That is an interesting question. The GSS does not check the certificate chain or domain, thus, to directly answer your question, no, it doesn't care about trust. I have never tested if the clock is checked against the date range on the certificate, but I would imagine it doesn't check that either.
At this point, if you had a linux box, issue a wget or curl request against the server and see what it sends back for the the page your GSS is probing (GSS only accepts a 200ok.)
※この はじめての Intersight Workload Optimizer / How To "Community" サイトで公開させていただいている情報は、Intersight Workload Optimizer に関わるナレッジを共有させて頂くことを目的としております。なるべく情報の正確性には努めてはおりますが、本 Community サイトで公開させて頂いている情報に基づいておこなわれた構成その他あらゆる設定に関してシスコとして一切の責任を持つことはできませんので、必ず公式なドキュメント、ガ...
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast by Friday, December 3.
To learn what's new in this year's competition or to gain insights into the judging considerations, check out ...
Data Center and Cloud Networking News
Cisco Nexus Dashboard Open Ecosystem with Splunk
End-to-End Flow State Validation with Nexus Dashboard Insights Connectivity Analysis
Cisco Q1 NPI Announcements for Data Center and Cloud Networking
We delivered a partner enablement training session in September 2021 to share the ACI upgrade Best Practices.
The slide deck is enclosed here for wider audience in the community, it provides more details in terms of the best practices, tools and co...