INDEXING_FAILURES_EXHAUSTED_RETRIES, params: [all] (Error code: 60516)
. "Run the 'start search resync all' CLI command on the NSX appliance to resync"
fails.Following failures are occurring while indexing policy alarms or GenericPolicyRealizedResource
GPRR
2023-08-22T19:25:48.935Z WARN pool-742-thread-1 GenericPolicyRealizedResourceDataProvider 105456 - [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] [IndexDataProvider-GenericPolicyRealizedResource] Could not fetch data to be indexed for GenericPolicyRealizedResource//infra/realized-state/enforcement-points/alb-endpoint/<ANY ALB Objects starts with alb_>/<name of the object>,
cause :
com.vmware.nsx.management.policy.policyframework.exceptions.InvalidPolicyPathException:
The path=[/infra/realized-state/enforcement-points/alb-endpoint/<ANY ALB Objects starts with alb_>/<name of the object>] is invalid
Alam this will be occurred or may not be occurred
2023-08-22T19:25:42.221Z ERROR pool-742-thread-1 UfoGenericConverter 105456 - [nsx@6876 comp="nsx-manager" errorCode="MP60511" level="ERROR" subcomp="manager"] [Indexing: DtoConversion] Could not convert UFO object to
Dto by DTO converter UfoObject{operationType=CREATE, descriptor=IndexingTypeDescriptor{tableName='Alarm', streamTag=POLICY}, identifier=string_id: "/infra/realized-state/enforcement-points/alb-endpoint/<ANY ALB Objects starts with alb_>/<name of the object>/alarms/<UUID>" , timestamp.sequence =16398, timestamp.epoch=0}
java.lang.reflect.InvocationTargetException: null
type.googleapis.com/vmware.nsx.ufostore.advanceloadbalancer.model.AlbControllerAdminCredsMsg not in map!"
VMware NSX
This issue occurs when some ALB objects remain in NSX-T DB.
From VMware NSX 4.1.1 onwards, some ALB integration features were removed, this lead to some stale objects remaining and resulted in the above G
eneric Policy Realized Resource indexing Alarm above: InvalidPolicyPathException
.
Please refer to the following KB for more details on the ALB deprecation
https://knowledge.broadcom.com/external/article?legacyId=87899
Contact Broadcom support for help with this issue