topic Re: Debugging Failed Features in Controllers

Debugging Failed Features

Nathan Sowatskey — Fri, 01 Mar 2019 12:29:58 GMT

The attached image shows that there are failed features for my CSR1Kv device.

How can I debug what APIC-EM is doing, or not, here please?

I believe that I have the global credentials set up properly.

I have tried searching the logs for "csr1kv", but nothing came back from the search.

I expect that I should set the logging level on one of the services, but it is not clear which service. I did try the "network-poller-service", but that didn't work anyway (see other post).

APIC-EM is clearly able to connect to this device to some degree, probably with SNMP. It looks like, I am guessing, the CLI connection is not working. As I note above, I have tried setting the global CLI credentials, and the specific discovery credentials, several times, and that does not seem to make any difference here.

Any and all suggestions related to understanding what APIC-EM is doing here, and how to debug it, would be gratefully received.

Many thanks

Nathan

Re: Debugging Failed Features

aradford — Sat, 23 Jul 2016 07:56:42 GMT

Polaris 16.3 is not supported. That is why it is failing. Support for 16.3 will be in September.

The models are slightly different, hence the error messages in the inventory_status

Re: Debugging Failed Features

Nathan Sowatskey — Sat, 23 Jul 2016 08:48:18 GMT

Thanks Adam.

How could I see the appropriate logs to debug this please?

Regards

Nathan

Re: Debugging Failed Features

aradford — Sat, 23 Jul 2016 08:51:48 GMT

it is shown in your screen capture. inventoryStatusDetail=''<status >.....FAILED_FEAT etc...

Re: Debugging Failed Features

Nathan Sowatskey — Thu, 28 Jul 2016 15:01:09 GMT

Just to close the loop here, with 1.2 there are no logs for inventory and discovery. This is a known issue which might be addressed in 1.3.