The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
[type] Download Policy Configuration Error. Check scheduler Name, Username, Password and HTTP URL
This fault typically occurs when the download configuration is not correct
If you see this fault, take the following actions:
Step 1 Review the fault and the error message on the FSM tab.
Step 2 Check scheduler Name, Username, Password and HTTP URL in download configuration
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
Communication Service configuration can’t be deployed. Error: [configStatusMessage]
This fault typically occurs because Cisco UCS Manager has detected an invalid communication policy confiuration.
If you see this fault, take the following actions:
Step 1 Verify that ports configured across all communication services is unique.
[name] Trustpoint’s cert-chain is invalid, reason: [certStatus].
This fault occurs when certificate status of TrustPoint has become invalid.
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.
[name] Keyring’s certificate is invalid, reason: [certStatus].
This fault occurs when certificate status of Keyring has become invalid.
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.
scheduler [schedName] not found
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. If you cannot resolve the issue, create a show tech-support file and contact Cisco Technical Support.