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

eos_designs: missing monitor_sessions definition for l3_interfaces #3888

Open
1 task done
c-po opened this issue Apr 21, 2024 · 0 comments
Open
1 task done

eos_designs: missing monitor_sessions definition for l3_interfaces #3888

c-po opened this issue Apr 21, 2024 · 0 comments
Labels
type: enhancement New feature or request

Comments

@c-po
Copy link
Contributor

c-po commented Apr 21, 2024

Enhancement summary

There is no possibility to define / use the provided monitor_sessions also for l3_interfaces.

Which component of AVD is impacted

eos_designs

Use case example

We have a DANZ monitoring fabric connected to our L3LS fabric. The monitoring sessions are configured genericly under port_profiles for all out connected endpoints.

At the time of this writing it's not possible to also re-use the existing YML nodes to enable a monitoring port for a l3_interface.

monitoring_session key is only supported for:

<connected_endpoints_keys.key>:
network_ports:
port_profiles

Describe the solution you would like

network_services_keys.name>:
  - name: foo
    vrfs:
      - name: red
        l3_interfaces:
          - interfaces: Eth1
            monitor_sessions:
              - name: DMF
                role: source
                source_settings:
                  direction: both

Describe alternatives you have considered

Workaround is to use the structured_config field

Additional context

No response

Contributing Guide

  • I agree to follow this project's Code of Conduct
@c-po c-po added the type: enhancement New feature or request label Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant