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.
This fault typically occurs when a uuid pool does not contain any uuids.
If you see this fault, take the following actions:
Step 1 If the pool is in use, add a block of uuids to the pool.
Step 2 If the pool is not in use, ignore the fault.
FC pool [purpose] [name] is empty
This fault typically occurs when a fc pool does not contain any fc.
If you see this fault, take the following actions:
Step 1 If the pool is in use, add a block of fc to the pool.
Step 2 If the pool is not in use, ignore the fault.
This fault typically occurs when a mac pool does not contain any mac.
If you see this fault, take the following actions:
Step 1 If the pool is in use, add a block of mac to the pool.
Step 2 If the pool is not in use, ignore the fault.
This fault typically occurs when duplicate ID is assigned.
If you see this fault, take the following actions:
Step 1 check FC Pool and make sure no duplicate address is assigned.
Step 2 check IP Pool and make sure no duplicate address is assigned.
Step 3 check IQN Pool and make sure no duplicate address is assigned.
Step 4 check MAC Pool and make sure no duplicate address is assigned.
Step 5 check UUID Pool and make sure no duplicate address is assigned.
ID is defined in multiple systems
This fault typically occurs when ID is defined in multiple systems.
If you see this fault, take the following actions:
Step 1 check FC Pool and make sure an address is not defined in multiple systems.
Step 2 check IP Pool and make sure an address is not defined in multiple systems.
Step 3 check IQN Pool and make sure an address is not defined in multiple systems.
Step 4 check MAC Pool and make sure an address is not defined in multiple systems.
Step 5 check UUID Pool and make sure an address is not defined in multiple systems.
This fault typically occurs when a ip pool does not contain any ip.
If you see this fault, take the following actions:
Step 1 If the pool is in use, add a block of ip to the pool.
Step 2 If the pool is not in use, ignore the fault.
This fault typically occurs when a iqn pool does not contain any iqns.
If you see this fault, take the following actions:
Step 1 If the pool is in use, add a block of iqns to the pool.
Step 2 If the pool is not in use, ignore the fault.
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.
If you see this fault, take the following actions:
Step 1 Identify the Trustpoint(s) affected.
Step 2 For affected trust-points, delete those keyrings using this trustpoint. Obtain new CA certificate and install.
[name] Keyring’s certificate is invalid, reason: [certStatus].
This fault occurs when certificate status of Keyring has become invalid.
If you see this fault, take the following actions:
Step 1 Identify the keyring(s) affected.
Step 2 If default keyring certificate is affected, regenerate the certificate.
Step 3 For other keyrings create new cert-req and get it signed by CA and set to keyring.