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

Incorrect interface names in vl3 example #297

Open
2 of 3 tasks
VitalyGushin opened this issue Feb 13, 2024 · 0 comments
Open
2 of 3 tasks

Incorrect interface names in vl3 example #297

VitalyGushin opened this issue Feb 13, 2024 · 0 comments
Assignees

Comments

@VitalyGushin
Copy link

VitalyGushin commented Feb 13, 2024

Steps to reproduce: Deploy vl3-basic example.

NSM API returns 5 connections.

Issues:

  • The server side MEMIF interface name is incorrect (metrics:{key:\“server_interface\” value:\“MEMIF/\“})
  • In looped endpoint1-endpoint1 connections, the first (KERNEL) interface does not have a name
  • In inter-node endpoint1-endpoint2 connections, the client endpoint does not contain an interface name

Path example:

path_segments:{name:\“nse-vl3-vpp-54d5d7468c-9ln7f\“}
path_segments:{name:\“nsmgr-j6x6m\“}
path_segments:{name:\“forwarder-vpp-zpg6b\”
	metrics:{key:\“client_interface\” value:\“MEMIF/memif1649599747/0\“}
	metrics:{key:\“server_interface\” value:\“VIRTIO/tun0\“}}
path_segments:{name:\“nse-vl3-vpp-54d5d7468c-9ln7f\”
	metrics:{key:\“server_interface\” value:\“MEMIF/\“}}}

Dashboard canvas example:
Screenshot 2024-04-18 at 11 15 57

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

No branches or pull requests

1 participant