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

ipv6 neighbor data gathering for junos #971

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

amylieb
Copy link

@amylieb amylieb commented Jan 17, 2025

Test inclusion requirements

I browsed through the test folder but didn't see an obvious place to augment an existing test, though I could definitely be missing something. Let me know if there's a particular file I can add data to, or if there's an example of an existing test I could emulate.

Related Issue

N/A

Description

Gather IPv6 neighbor data from junos devices.

Type of change

  • New feature (non-breaking change which adds functionality)

New Behavior

Added a command to arpnd.yaml for gathering ipv6 neighbor data

Contrast to Current Behavior

Currently only IPv4 arp data is gathered for arpnd for junos.

Discussion: Benefits and Drawbacks

  • Why do you think this project and the community will benefit from your
    proposed change? More complete data gathered for junos.

  • What are the drawbacks of this change? None (at least I can think of)

  • Is it backwards-compatible? Yes

  • Anything else that you think is relevant to the discussion of this PR.

Not sure why this data isn't already being gathered, it's not really indicated in the documentation that only arp data is gathered for Junos, and it's an easy thing to implement. My organization has a large Junos deployment and gathering IPv6 neighbor data from these devices is a requirement if we plan to leverage suzieq.

Changes to the Documentation

N/A

...

Proposed Release Note Entry

IPv6 neighbor data gathering for junos

Comments

N/A

Double Check

  • I have read the comments and followed the CONTRIBUTING.md.
  • I have explained my PR according to the information in the comments or in a linked issue.
  • My PR source branch is created from the develop branch.
  • My PR targets the develop branch.
  • All my commits have --signoff applied

@ddutt
Copy link
Member

ddutt commented Jan 26, 2025

Thanks for the contribution @amylieb

Could you please squash the last two commits as one (the code and the typo fix)?
Do you have any sample data that you can provide that can be used to validate this part?

Also, you'll need to move the PR out of draft state for me to merge it.

@amylieb amylieb force-pushed the ipv6-neighbors-for-junos branch from 3afa9ab to b22197d Compare January 27, 2025 17:48
@amylieb
Copy link
Author

amylieb commented Jan 27, 2025

Thanks @ddut - done. I'm new to contributing to open source projects, but I hope to contribute more to this one in the future.

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

Successfully merging this pull request may close these issues.

2 participants