Some ipfabric commands returns empty table about nautobot-plugin-chatops-ipfabric HOT 18 CLOSED

@martin-networker did you set the correct snapshot with /ipfabric set-snapshot? Usually the table is only empty if there is no return data from the IP fabric server.

from nautobot-plugin-chatops-ipfabric.

@pke11y I have tried it with several snapshots and the response is the same. By default it use $last snapshot.
The data is in IP Fabric, only the response via chatops do not show anything.
Have you tested these commands on same version of IP Fabric and chatops as we have?

from nautobot-plugin-chatops-ipfabric.

@martin-networker since you're using IP Fabric version 4 you'll need to be using v1.1.0 of the nautobot-plugin-chatops-ipfabric. They made breaking changes in IP Fabric v4 to the way diagrams are accessed using the API. So we implemented a new command to retrieve a diagram for the path trace instead of a table. The end-to-end-path command was deprecated in the most recent release and is intended for use in IP Fabric v3.

/ipfabric pathlookup 10.1.1.1 10.1.2.1 1000 22 tcp 

For the other two commands, be sure you're using the actual device name as it would be in IP Fabric.

/ipfabric routing rtr1 bgp-neighbors active
/ipfabric interfaces rtr1 load

from nautobot-plugin-chatops-ipfabric.

@pke11y we are already using v1.1.0 of the nautobot-plugin-chatops-ipfabric.

from nautobot-plugin-chatops-ipfabric.

@martin-networker great, so /ipfabric pathlookup should work for you.

from nautobot-plugin-chatops-ipfabric.

@pke11y yes, but if you know this command does not work anymore do you intend to remove it?

Just to be sure we already were on 1.1.0 when I have created the ticket.

Do you have any idea why those two commands do return empty tables?
/ipfabric routing device_name bgp-neighbors active
/ipfabric interfaces device_name load

from nautobot-plugin-chatops-ipfabric.

@martin-networker the end-to-end-path command still works for IP Fabric v3.

Can you confirm you're using the actual device name in the command e.g. rtr1 not device_name

/ipfabric routing rtr1 bgp-neighbors active
/ipfabric interfaces rtr1 load

from nautobot-plugin-chatops-ipfabric.

I have confirmed this is not working.

from nautobot-plugin-chatops-ipfabric.

So it seems that all the IP Fabric search are using eq which is a case sensitive search. When running the commands the hostnames are transformed to lowercase which will cause no matches.

I opened a feature request a couple weeks ago internally and we are working on a ieq function but this is not scheduled for release yet.

from nautobot-plugin-chatops-ipfabric.

So if you run the command using the prompted drop-down lists does it work e.g. /ipfabric routing or /ipfabric interfaces?

from nautobot-plugin-chatops-ipfabric.

Currently the workaround would be using a regex.
eq 'l66exr1' -> reg '^[lL]66[eE][xX][rR]1$'

@martin-networker Can you try testing with uppercase HOSTNAME?

from nautobot-plugin-chatops-ipfabric.

So if you run the command using the prompted drop-down lists does it work e.g. /ipfabric routing or /ipfabric interfaces?

Using the dropdown it transforms hostname to lowercase:
devices = [ (device["hostname"], device["hostname"].lower()) for device in ipfabric_api.get_devices_info(snapshot_id) ]

from nautobot-plugin-chatops-ipfabric.

Ok, so if we remove the .lower() we could resolve this issue?

from nautobot-plugin-chatops-ipfabric.

Ok, so if we remove the .lower() we could resolve this issue?

Only if they use the dropdown, if I type in the command and do 'L66exr1' it will not work

from nautobot-plugin-chatops-ipfabric.

Opened #76

Had this feature implemented in python-ipfabric so it was mainly copy/pasta

from nautobot-plugin-chatops-ipfabric.

If I run the command using the prompted drop-down lists does not work either. But @justinjeffery-ipf already confirmed that.

Entering the hostname in uppercase or lowercase does not help. I am not sure how this could help if the hostnames are really transformed to lowercase.

from nautobot-plugin-chatops-ipfabric.

@martin-networker release 1.1.1 should fix this and will be published today.

from nautobot-plugin-chatops-ipfabric.

Fix implemented in 1.1.1

from nautobot-plugin-chatops-ipfabric.