Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interfaces created after lldpd started don't use configuration from a conf file #204

Open
paulnice opened this issue Nov 1, 2016 · 2 comments

Comments

@paulnice
Copy link

paulnice commented Nov 1, 2016

How to reproduce:

  1. Start lldpd with the following configuration file:
    "configure ports Ethernet64 lldp portidsubtype local fortyGig0/64 description test"
  2. Then create Ethernet64 interface.
  3. lldpd will see Ethernet64 and it will start to send lldp frames out of the Interface, but it will announce a mac address of interface in portid instead of configured value in the configuration file.

To fix this behaviour we can apply the configuration again with lldpcli -c "config file".
I think it's better to wait that the interface from the configuration will be created and then just use configuration from the config.

@vincentbernat
Copy link
Member

The overall issue is valid but I don't have an immediate fix. As a short term fix, you could just start lldpd later. Which init system are you using?

@paulnice
Copy link
Author

paulnice commented Nov 1, 2016

It was already "fixed" by this https://github.com/Azure/sonic-buildimage/blob/master/dockers/docker-lldp-sv2/reconfigure.sh
I'm going to work on the permanent fix in lldpd later if I have enough time.
I left this issue to you as you requested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants