VerifyLLDPNeighbors and domain names

[janthon1]

Hello,

Our VerifyLLDPNeighbors are failing due to configured [ dns domain example.net ]. Consider the error report generated below. Other than the domain name, the reported LLDP neighbors are correct.

    {
        "name": "CPOB-AR1",
        "test": "VerifyLLDPNeighbors",
        "categories": [
            "connectivity"
        ],
        "description": "Verifies the connection status of the specified LLDP (Link Layer Discovery Protocol) neighbors.",
        "result": "failure",
        "messages": [
            "Port: Ethernet49/1 Neighbor: HAYS-CR1 Neighbor Port: Ethernet28/1 - Wrong LLDP neighbors: HAYS-CR1.example.net/Ethernet28/1",
            "Port: Ethernet50/1 Neighbor: HUNT-CR1 Neighbor Port: Ethernet28/1 - Wrong LLDP neighbors: HUNT-CR1.example.net/Ethernet28/1"
        ],
        "custom_field": "Generated by AVD"
    }

Could the VerifyLLDPNeighbors test be modified to have an option to ignore domain names?

anta, version v1.4.0
avd, arista.avd-5.4.0
ansible core 2.16.2

Regards,
Jason

[gmuloc]

Hello @janthon1

Thanks for reaching out!

Can you please confirm what role you are using?
Can you please also confirm how you are injecting the domain name?
Basically AVD should be able to detect it when generating the test if it is in your structured_config. My suspicion is that you may be using dns_domain directly in your group_vars / host_vars which is an eos_cli_config_gen variable

You either need to use

1. dns_settings if you are running from devel (newer way, merged yesterday, that will be supported in the next release)
2. custom_structured_configuration_dns_domain

Cheers,

gmuloc

[janthon1]

The playbook is using the arista.avd.anta_runner role.

You were correct, we are using the eos_cli_config_gen variable dns_domain in our global_vars, chaning that to a custom structured config varianet cleared up the VerifyLLDPNeighbors failures we were seeing.

Thanks for the quick assist!

-Jason