Issue: Destination MAC Resolve Failed for One or More Streams in Ostinato

[Adeeb Fahim]

I'm encountering an issue with Ostinato where the destination MAC address resolution fails for one or more streams, leading to a "Port 0: Source mac resolve failed for one or more streams - Device matching stream's source IP not found" error. I am simply trying to complete the 10 UDP Packet Tutorial.

Network Configuration:

• Ostinato Container:

  • eth1: 192.168.1.2/24
  • eth2: 192.168.2.2/24

• Nokia SR OS Router:

  • eth1: 192.168.1.1/24
  • eth2: 192.168.2.1/24

Steps Taken:

1. Interface Configuration:

   • Verified interfaces are up and correctly configured on both Ostinato and SR OS router.
   • Ping works between the interfaces.

2. Stream Configuration in Ostinato:

   • Ethernet:
     • Source MAC: Manually set to aa:c1:ab:57:2a:3c (taken from ip a command in Ostinato container)
     • Destination MAC: Manually set to 0c:00:eb:39:64:01 (taken from eth1 on the vSIM)
   • IPv4:
     • Source IP: 192.168.1.2
     • Destination IP: 192.168.1.1
       

3. Issues Encountered:

   • When using ARP resolution (Protocol Data - Media Access Protocol section set SMAC and DMAC on "Resolve"), I get an error - Port 0: Source mac resolve failed for one or more streams - Device matching stream's source IP not found
   • When manually configuring the MAC addresses for SMAC and DMAC, the stream works and the 10 UDP packets send without fail

Any assistance or suggestions to streamline this process and troubleshoot the MAC resolution issue effectively would be greatly appreciated.

Thanks!

[Srivats P]

Adeeb,

Please share a screen shot like this -

Select eth1 in the ports list, Devices Tab, Information, Click on the ARP value

Srivats (Founder, Ostinato)
Now generate up to 100Gbps 🚀 with the Ostinato Turbo add-on!

--
Get Ostinato News and Updates on Twitter - Follow @ostinato (http://twitter.com/ostinato)
---
You received this message because you are subscribed to the Google Groups "ostinato" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ostinato+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ostinato/89aef449-97ca-44c0-858c-e3034a0d3440n%40googlegroups.com.

[Adeeb Fahim]

Hi Srivats,

Here is the screen cap you requested:

Let me know if you need anything else.

[Srivats P]

Hi Adeeb,

It looks like you haven't configured an IP address on the port (what is the output of "ip addr show") when that screenshot was taken?

You either need to assign a IP address on the port in the OS or configure an emulated device within Ostinato with the IP address configuration - see Device Emulation - Ostinato Guides (also includes a video tutorial)

Srivats

To view this discussion on the web visit https://groups.google.com/d/msgid/ostinato/75ad2b41-fec9-466a-9d30-233a53264674n%40googlegroups.com.

[Srivats P]

Adeeb,

Ah, I think I know what's happening!

Ostinato/Drone reads the port Mac and IP address when the container starts - at that time there is no IP address. You add it manually later using "ip addr add". But Ostinato/drone does not re-read this information again.

Please use Device Emulation for Ostinato on ContainerLab for now. We will consider how to solve this problem in the future.

Srivats

On Thu, Jun 6, 2024 at 11:04 PM Adeeb Fahim <adeeb...@gmail.com> wrote:

Thanks for the reply Srivats,

eth1@if97: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 9500 qdisc noqueue state UP group default
    link/ether aa:c1:ab:a8:4e:05 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet 192.168.1.2/24 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fea8:4e05/64 scope link
       valid_lft forever preferred_lft forever

At the time of that screenshot (and now) the IP address on the interface was configured using the command "ip addr add 192.168.1.2/24 dev eth1". I can give the device emulation a shot. 

Connectivity is fine, as mentioned in the original message, I can ping from the virtualized SROS router to the Ost. container no problem. From that, it also resolves the MAC address using ARP.
[/]
A:admin@vSIM# ping 192.168.1.2
PING 192.168.1.2 56 data bytes
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=3.62ms.
64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.449ms.
64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.425ms.
64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=0.478ms.
64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=0.467ms.

---- 192.168.1.2 PING Statistics ----
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 0.425ms, avg = 1.09ms, max = 3.62ms, stddev = 1.27ms

After running the ping on the SR


So connection between the two nodes isn't an issue, but the source MAC resolution seems to be failing.

Let me know what you think. In the mean time, I will try the device emulation.

Thanks,
Adeeb

[Adeeb Fahim]

[Srivats P]

You are using 198.x.x.x instead of 192.x.x.x

Also, if you are using device emulation you don't need to configure a IP address on the port in the OS using "ip address add". Better to remove it otherwise both the OS and Ostinato will reply to the ping.

Srivats (Founder, Ostinato)

On Fri, Jun 7, 2024 at 8:02 PM Adeeb Fahim <adeeb...@gmail.com> wrote:

Morning Srivats,

I'm giving the device emulation a shot. I am having trouble configuring it for my use case. I have the following configuration:

I matched the MAC address field to the one of the actual eth1 (taken from the ip a output for eth1). I still cannot ping from the DUT to eth1's IP address. Nothing shows up in the Device Information tab either, especially for ARP.

A:admin@vSIM# ping 192.168.1.2
PING 192.168.1.2 56 data bytes

Request timed out. icmp_seq=1.
Request timed out. icmp_seq=2.
Request timed out. icmp_seq=3.
Request timed out. icmp_seq=4.
Request timed out. icmp_seq=5.

---- 192.168.1.2 PING Statistics ----

5 packets transmitted, 0 packets received, 100% packet loss



I have a feeling it's a configuration issue on my end, so if you could point me in the right direction that would be greatly appreciated!

Thanks,

Adeeb

[Adeeb Fahim]

Morning Srivats,

I'm giving the device emulation a shot. I am having trouble configuring it for my use case. I have the following configuration:

I matched the MAC address field to the one of the actual eth1 (taken from the ip a output for eth1). I still cannot ping from the DUT to eth1's IP address. Nothing shows up in the Device Information tab either, especially for ARP.

A:admin@vSIM# ping 192.168.1.2
PING 192.168.1.2 56 data bytes

Request timed out. icmp_seq=1.
Request timed out. icmp_seq=2.
Request timed out. icmp_seq=3.
Request timed out. icmp_seq=4.
Request timed out. icmp_seq=5.

---- 192.168.1.2 PING Statistics ----

5 packets transmitted, 0 packets received, 100% packet loss



I have a feeling it's a configuration issue on my end, so if you could point me in the right direction that would be greatly appreciated!

Thanks,

Adeeb

[Adeeb Fahim]

Ah, that was it. My mistake. Thank you for pointing that out!

I got the device emulation to work as a result. Please keep me updating if you can in regards to configuring the interfaces on the OS level in containerlab version of Ostinato. 



Take care!

Adeeb

[Srivats P]

Hi Adeeb,

I hope you are getting the email course about using Ostinato and its various features?

Srivats (Founder, Ostinato)
Now generate up to 100Gbps 🚀 with the Ostinato Turbo add-on!