Logical ports are not discovered in AON when searching for 'NSX-T Logical Port' in the search bar.
It is seen in /var/log/arkin/collector.STDOUT-YYYY-MM-DD-hh.mm.ss.log.error that the HttpUtils.checkCodeAndThrow method throws an HttpException due to a 400 status code.
<DATE_TIME> ERROR vmware.nsxcommon.AbstractClusterDataSourceFetchUtils NSXT_###.###.###.###_Config_OpMgr_Policy-2 executeHttpCall:136 Error calling callable for path /policy/api/v1/infra/tier-1s/##-##-####-######/nat/NAT64/nat-rules
<DATE_TIME> ERROR tasks.datafetchers.PolicyManagerNatRuleFetcher NSXT_###.###.###.###_Config_OpMgr_Policy-2 fetchNatRulesPerSection:101 Returning as content is empty. |
VCF Operations for Networks 6.14.0
While calling the API to fetch NAT rules for a specific tier-1 router, the HttpUtils.checkCodeAndThrow method throws an HttpException due to a 400 status code, which ultimately leaves the segment cache unpopulated.
Consequently, the Logical Ports Fetcher is blocked because the segment cache is not ready (remains unpopulated), causing it to return immediately without fetching any logical ports.
This issue is fixed in Aria Operations for Networks 6.14.1
Workaround is available for this in Aria Operations for Networks which involves database modification. Please open a Broadcom support ticket referring to this KB Article.
AON-DS-NSX