Service Registry Faults

fltExtpolProviderProviderLostConnectivity

Fault Code: F10000190

Message

Service provider ([capability], [ip], [ipv6]) lost connectivity

Explanation

This provider is not reachable from UCS Central registry. This fault typically occurs if the provider process has crashed or too busy to respond to hearbeat message sent by registry.

Recommended Action

If you see this fault, take the following actions:


Step 1 In the Cisco UCS Central CLI, check the provider process state through show pmon state in local-mgmt shell. You can check the same information through GUI from Administrator in UCS Central.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical
Cause: provider-lost-connectivity
mibFaultCode: 10000190
mibFaultName: fltExtpolProviderProviderLostConnectivity
moClass: extpol:Provider
Type: network
Auto Cleared: true
Affected MO: extpol/reg/providers/prov-[type]

fltExtpolControllerControllerLostConnectivity

Fault Code: F10000191

Message

Management controller ([capability], [ip], [ipv6]) lost connectivity

Explanation

This controller is not reachable from UCS Central registry. This fault typically occurs if the controller process has crashed or too busy to respond to hearbeat message sent by registry.

Recommended Action

If you see this fault, take the following actions:


Step 1 In the Cisco UCS Central CLI, check the provider process state through show pmon state in local-mgmt shell. You can check the same information through GUI from Administrator in UCS Central.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical
Cause: controller-lost-connectivity
mibFaultCode: 10000191
mibFaultName: fltExtpolControllerControllerLostConnectivity
moClass: extpol:Controller
Type: network
Auto Cleared: true
Affected MO: extpol/reg/controllers/contro-[id]

fltExtpolClientClientLostConnectivity

Fault Code: F10000192

Message

Managed endpoint ([capability], [ip], [ipv6]) lost connectivity

Explanation

This registered UCS Domain is not reachable from UCS Central registry. This fault typically occurs if the UCS Domain has lost network access or UCS Domain DME process has crashed or too busy to respond to hearbeat message sent by registry.

Recommended Action

If you see this fault, take the following actions:


Step 1 In the Cisco UCS Central CLI, check the client process state through show clients detail in service-reg shell. You can check the same information through GUI from Administrator in UCS Central.

Step 2 Check the network connectivity from UCS domain to UCS Central. Also check, if UCSM is busy processing a bulkier, lengthy transaction.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major
Cause: client-lost-connectivity
mibFaultCode: 10000192
mibFaultName: fltExtpolClientClientLostConnectivity
moClass: extpol:Client
Type: network
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolRegistryServiceRegistryVersionMismatch

Fault Code: F10000193

Message

Service Registry ([capability], [ip], [ipv6]) software version is not compatible

Explanation

UCS Central regsitry is not running the compatible version in the package.

Recommended Action

If you see this fault, take the following actions:


Step 1 Upgrade to a valid UCS Central package or contact Cisco TAC.

Fault Details

Severity: critical
Cause: service-registry-version-mismatch
mibFaultCode: 10000193
mibFaultName: fltExtpolRegistryServiceRegistryVersionMismatch
moClass: extpol:Registry
Type: network
Auto Cleared: true
Affected MO: extpol/reg

fltExtpolProviderProviderVersionMismatch

Fault Code: F10000194

Message

Service provider ([capability], [ip], [ipv6]) software version is not compatible

Explanation

UCS Central provider is not running the compatible version in the package.

Recommended Action

If you see this fault, take the following actions:


Step 1 Upgrade to a valid UCS Central package or contact Cisco TAC.

Fault Details

Severity: critical
Cause: provider-version-mismatch
mibFaultCode: 10000194
mibFaultName: fltExtpolProviderProviderVersionMismatch
moClass: extpol:Provider
Type: network
Auto Cleared: true
Affected MO: extpol/reg/providers/prov-[type]

fltExtpolControllerControllerVersionMismatch

Fault Code: F10000195

Message

Management controller ([capability], [ip], [ipv6]) software version is not compatible

Explanation

UCS Central controller is not running the compatible version in the package.

Recommended Action

If you see this fault, take the following actions:


Step 1 Upgrade to a valid UCS Central package or contact Cisco TAC.

Fault Details

Severity: critical
Cause: controller-version-mismatch
mibFaultCode: 10000195
mibFaultName: fltExtpolControllerControllerVersionMismatch
moClass: extpol:Controller
Type: network
Auto Cleared: true
Affected MO: extpol/reg/controllers/contro-[id]

fltExtpolClientClientVersionMismatch

Fault Code: F10000196

Message

Managed endpoint ([capability], [ip], [ipv6]) software version is not compatible

Explanation

UCS Domain is not running the compatible software version to UCS Central.

Recommended Action

If you see this fault, take the following actions:


Step 1 Upgrade UCS Domain to a compatible version, in order to get it registered with UCS Central.

Fault Details

Severity: critical
Cause: client-version-mismatch
mibFaultCode: 10000196
mibFaultName: fltExtpolClientClientVersionMismatch
moClass: extpol:Client
Type: network
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltCommSvcEpCommSvcNotDeployed

Fault Code: F10000339

Message

Communication Service configuration can’t be deployed. Error: [configStatusMessage]

Explanation

This fault typically occurs because Cisco UCS Manager has detected an invalid communication policy confiuration.

Recommended Action

If you see this fault, take the following actions:


Step 1 Verify that ports configured across all communication services is unique.

Fault Details

Severity: major
Cause: comm-svc-config-error
mibFaultCode: 10000339
mibFaultName: fltCommSvcEpCommSvcNotDeployed
moClass: comm:SvcEp
Type: comm-svc-not-deployed
Auto Cleared: true
Affected MO: sys/svc-ext

fltLicenseInstanceGracePeriodWarning1

Fault Code: F10000362

Message

license for feature [feature] on UCS Central [scope] has entered into the grace period.

Explanation

At lease one UCS domain is registered with UCS Central without having a license. This fault typically occurs if one or more UCS domains are registered with UCS Central after all default (and procured) licenses are asigned to other UCS domains.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and cosumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Admin tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under license scope from service-reg session.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-entered
mibFaultCode: 10000362
mibFaultName: fltLicenseInstanceGracePeriodWarning1
moClass: license:Instance
Type: management
Auto Cleared: true
Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fltLicenseInstanceGracePeriodWarning2

Fault Code: F10000363

Message

license for feature [feature] on UCS Central [scope] is running in the grace period for more than 10 days

Explanation

At least one UCS domain is registered with UCS Central without having a license. This fault typically occurs if one or more UCS domains are registered with UCS Central after all default (and procured) licenses are asigned to other UCS domains.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Admin tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-10days
mibFaultCode: 10000363
mibFaultName: fltLicenseInstanceGracePeriodWarning2
moClass: license:Instance
Type: management
Auto Cleared: true
Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fltLicenseInstanceGracePeriodWarning3

Fault Code: F10000364

Message

license for feature [feature] on UCS Central [scope] is running in the grace period for more than 30 days

Explanation

At least one UCS Domain with UCS Central has been running in the grace period for more than 30 days. This fault typically occurs if one or more UCS domains are registered with UCS Central after all default (and procured) licenses are asigned to other UCS domains and the unlicensed UCS Domains have been running for more than 120 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Manager GUI, you can access the licensing information from the Admin tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-30days
mibFaultCode: 10000364
mibFaultName: fltLicenseInstanceGracePeriodWarning3
moClass: license:Instance
Type: management
Auto Cleared: true
Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fltLicenseInstanceGracePeriodWarning4

Fault Code: F10000365

Message

license for feature [feature] on UCS Central [scope] is running in the grace period for more than 60 days

Explanation

At least one UCS Domain with UCS Central has been running in the grace period for more than 60 days. This fault typically occurs if one or more UCS domains are registered with UCS Central after all default (and procured) licenses are asigned to other UCS domains and the unlicensed UCS Domains have been running for more than 60 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Centralt. In the Cisco UCS Central GUI, you can access the licensing information from the Admin tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-60days
mibFaultCode: 10000365
mibFaultName: fltLicenseInstanceGracePeriodWarning4
moClass: license:Instance
Type: management
Auto Cleared: true
Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fltLicenseInstanceGracePeriodWarning5

Fault Code: F10000366

Message

license for feature [feature] on UCS Central [scope] is running in the grace period for more than 90 days

Explanation

At least one UCS Domain with UCS Central has been running in the grace period for more than 90 days. This fault typically occurs if one or more UCS domains are registered with UCS Central after all default (and procured) licenses are asigned to other UCS domains and the unlicensed UCS Domains have been running for more than 90 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed by UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Admin tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major
Cause: license-graceperiod-90days
mibFaultCode: 10000366
mibFaultName: fltLicenseInstanceGracePeriodWarning5
moClass: license:Instance
Type: management
Auto Cleared: true
Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fltLicenseInstanceGracePeriodWarning6

Fault Code: F10000367

Message

license for feature [feature] on UCS Central [scope] is running in the grace period for more than 119 days

Explanation

At least one UCS Domain with UCS Central has been running in the grace period for more than 119 days. This fault typically occurs if one or more UCS domains are registered with UCS Central after all default (and procured) licenses are asigned to other UCS domains and the unlicensed UCS Domains have been running for more than 119 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Admin tab for UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical
Cause: license-graceperiod-119days
mibFaultCode: 10000367
mibFaultName: fltLicenseInstanceGracePeriodWarning6
moClass: license:Instance
Type: management
Auto Cleared: true
Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fltLicenseInstanceGracePeriodWarning7

Fault Code: F10000368

Message

Grace period for feature [feature] on UCS Central [scope] is expired. Please acquire a license for the same.

Explanation

At least one UCS Domain with UCS Central has been running in the grace period for more than 120 days. UCS domains are registered with UCS Central after all default (and procured) licenses are asigned to other UCS domains and the unlicensed UCS Domains have been running for more than 120 days. At this stage, the system licensing state is set to expired.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Admin tab for UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 Disable the unlicensed UCS Domains to bring the number of enabled Domains down to the number of total licenses.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC immediately to procure more licenses.

Fault Details

Severity: critical
Cause: license-graceperiod-expired
mibFaultCode: 10000368
mibFaultName: fltLicenseInstanceGracePeriodWarning7
moClass: license:Instance
Type: management
Auto Cleared: true
Affected MO: sys/license/feature-[name]-[vendor]-[version]/inst-[scope]

fltLicenseFileBadLicenseFile

Fault Code: F10000369

Message

license file [name] on UCS Central [scope] can not be installed

Explanation

The installation of a license file on UCS Central failed. This fault typically occurs if the license file is badly formatted or its host ID does not match that of the UCS Domain.

Recommended Action

If you see this fault, take the following actions:


Step 1 In the Cisco UCS Central CLI, check the host IDs for UCS Domains. You can access the host ID information by entering the show server-host-id detail command under the license scope.

Step 2 Match the host IDs with the contents of the license file. If the host ID matches that of one of the UCS Domain, create a show tech-support file and contact Cisco TAC. If it does not match, contact Cisco TAC to obtain the correct license File.

Fault Details

Severity: critical
Cause: license-file-uninstallable
mibFaultCode: 10000369
mibFaultName: fltLicenseFileBadLicenseFile
moClass: license:File
Type: management
Auto Cleared: false
Affected MO: sys/license/file-[scope]:[id]

fltLicenseFileFileNotDeleted

Fault Code: F10000370

Message

license file [name] from UCS Central [scope] could not be deleted

Explanation

The deletion of a license file on UCS Central has failed. This fault typically occurs if license framework is not able to delete a file.

Recommended Action

If you see this fault, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical
Cause: license-file-not-deleted
mibFaultCode: 10000370
mibFaultName: fltLicenseFileFileNotDeleted
moClass: license:File
Type: management
Auto Cleared: false
Affected MO: sys/license/file-[scope]:[id]

fltExtpolClientGracePeriodWarning

Fault Code: F10000372

Message

UCS domain [name] registered with UCS Central has entered into the grace period.

Explanation

A UCS domain is registered with UCS Central without having a license. This fault typically occurs if this UCS domain is registered with UCS Central after all default (and procured) licenses are assigned to other UCS domains.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Operations Management tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under license scope from service-reg session.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-entered
mibFaultCode: 10000372
mibFaultName: fltExtpolClientGracePeriodWarning
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning2

Fault Code: F10000373

Message

UCS Domain [name] registered with UCS Central is running in the grace period for more than 10 days

Explanation

This UCS domain is registered with UCS Central without having a license. This fault typically occurs if this UCS domain is registered with UCS Central after all default (and procured) licenses are assigned to other UCS domains.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Operations Management tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-10days
mibFaultCode: 10000373
mibFaultName: fltExtpolClientGracePeriodWarning2
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning3

Fault Code: F10000374

Message

UCS Domain [name] registered with UCS Central is running in the grace period for more than 30 days

Explanation

This UCS Domain registered with UCS Central has been running in the grace period for more than 30 days. This fault typically occurs if this UCS domain is registered with UCS Central after all default (and procured) licenses are assigned to other UCS domains and the unlicensed UCS Domains have been running for more than 120 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Manager GUI, you can access the licensing information from the Operations Management tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-30days
mibFaultCode: 10000374
mibFaultName: fltExtpolClientGracePeriodWarning3
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning4

Fault Code: F10000375

Message

UCS Domain [name] registered with UCS Central is running in the grace period for more than 60 days

Explanation

This UCS Domain registered with UCS Central has been running in the grace period for more than 60 days. This fault typically occurs if this UCS domain is registered with UCS Central after all default (and procured) licenses are assigned to other UCS domains and the unlicensed UCS Domains have been running for more than 60 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Operations Management tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: warning
Cause: license-graceperiod-60days
mibFaultCode: 10000375
mibFaultName: fltExtpolClientGracePeriodWarning4
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning5

Fault Code: F10000376

Message

UCS Domain [name] registered with UCS Central is running in the grace period for more than 90 days

Explanation

This UCS Domain registered with UCS Central has been running in the grace period for more than 90 days. This fault typically occurs if this UCS domains is registered with UCS Central after all default (and procured) licenses are assigned to other UCS domains and the unlicensed UCS Domains have been running for more than 90 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed by UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Operations Management tab for the UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: major
Cause: license-graceperiod-90days
mibFaultCode: 10000376
mibFaultName: fltExtpolClientGracePeriodWarning5
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning6

Fault Code: F10000377

Message

UCS Domain [name] registered with UCS Central is running in the grace period for more than 119 days

Explanation

This UCS Domain registered with UCS Central has been running in the grace period for more than 119 days. This fault typically occurs if this UCS domain is registered with UCS Central after all default (and procured) licenses are assigned to other UCS domains and the unlicensed UCS Domains have been running for more than 119 days.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Operations Management tab for UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

Fault Details

Severity: critical
Cause: license-graceperiod-119days
mibFaultCode: 10000377
mibFaultName: fltExtpolClientGracePeriodWarning6
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning7

Fault Code: F10000378

Message

Grace period for UCS Domain [name] registered with UCS Central has expired. Please acquire a license for the same.

Explanation

This UCS Domain registered with UCS Central has been running in the grace period for more than 120 days. UCS domains are registered with UCS Central after all default (and procured) licenses are assigned to other UCS domains and the unlicensed UCS Domains have been running for more than 120 days. At this stage, the system licensing state is set to expired.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check the number of licenses installed and consumed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Operations Management tab for UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 Disable the unlicensed UCS Domains to bring the number of enabled Domains down to the number of total licenses.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC immediately to procure more licenses.

Fault Details

Severity: critical
Cause: license-graceperiod-expired
mibFaultCode: 10000378
mibFaultName: fltExtpolClientGracePeriodWarning7
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltExtpolClientGracePeriodWarning1

Fault Code: F10000379

Message

UCS Domain [name] is registered with UCS Central without a valid license.

Explanation

This UCS domain is registered with UCS Central without having a license. This fault typically occurs if this UCS domain is registered with UCS Central without the initial activation license and after all default licenses are assigned to other UCS domains.

Recommended Action

If you see this fault, take the following actions:


Step 1 Check if the initial activation license is installed on UCS Central. In the Cisco UCS Central GUI, you can access the licensing information from the Operations Management tab for UCS Central. In the Cisco UCS Central CLI, you can access the licensing information by entering the show usage detail command under the license scope.

Step 2 Disable the unlicensed UCS Domains to bring the number of enabled Domains down to the number of total licenses.

Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC immediately to procure more licenses.

Fault Details

Severity: critical
Cause: license-insufficient
mibFaultCode: 10000379
mibFaultName: fltExtpolClientGracePeriodWarning1
moClass: extpol:Client
Type: management
Auto Cleared: true
Affected MO: extpol/reg/clients/client-[id]

fltPkiTPStatus

Fault Code: F10000591

Message

[name] Trustpoint’s cert-chain is invalid, reason: [certStatus].

Explanation

This fault occurs when certificate status of TrustPoint has become invalid.

Recommended Action

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.

Fault Details

Severity: major
Cause: invalid-trustpoint-cert-chain
mibFaultCode: 10000591
mibFaultName: fltPkiTPStatus
moClass: pki:TP
Type: security
Auto Cleared: true
Affected MO: sys/pki-ext/tp-[name]

fltPkiKeyRingStatus

Fault Code: F10000592

Message

[name] Keyring’s certificate is invalid, reason: [certStatus].

Explanation

This fault occurs when certificate status of Keyring has become invalid.

Recommended Action

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.

Fault Details

Severity: major
Cause: invalid-keyring-certificate
mibFaultCode: 10000592
mibFaultName: fltPkiKeyRingStatus
moClass: pki:KeyRing
Type: security
Auto Cleared: true
Affected MO: sys/pki-ext/keyring-[name]