Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
Discover how to get the most of Juniper labs and share what you've built.To easily navigate to other communities, select Communities > All Communities in the navigation.
Yes, that is a helpful document. It turns out that the .yml file existed, but was different. I've since attempted a new lab, and et-0/0/0 is behaving as expected. Thanks for the clarification :D ------------------------------ SIMON BROOKS --------- ...
Have been configuring using the unchannelized, or at least not setting the channelized configuration. I will check Vignesh's response below, as the yml config doesn't match what I have in the EVE-NG. thanks. ------------------------------ SIMON ...
Thanks, I will check this. ------------------------------ SIMON BROOKS ------------------------------
I see you are using latest 23.2 image. Hope you are using the below yml config at EVE https://community.juniper.net/blogs/shalini-mukherjee/2023/05/11/deploying-vjunos-in-a-bare-metal-eve-ng-server root@eve-ng:/opt/unetlab/html/templates/intel# ...
Are you running in channelized or unchannelized mode? And which release of vJunosEvolved? Art ------------------------------ Art Stine ------------------------------
Hello, Firing up the evo image for the first time, I used et-0/0/0 to start with, and nothing came up. Ran a wireshark and could see LLDP packets starting on et-0/0/4. Checked with further interfaces and continues to go up but not start at et-0/0/0 ...
It also looks like the notification to the hypervisor for the source interface also does not take place when the interface is shut down on the guest. As long as it is known expected behavior, both sides of the interface can be disabled in the guest devices ...