So, now that you have the opportunity to take a look at a few screenshots and
some of the
output involved, what do you think the problem is?
Well, let's compare notes and go through the interface together to identify
what the problem
is.
And I would recommend that the first thing we might want to do is go to these
two VMs
just to confirm that they can't actually communicate with each other.
So this one here is at .31 and the purple VM over here is at .41.
So let's confirm those IP addresses.
Let's also confirm they're both connected to those respective segments. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's also confirm they're both connected to those respective segments.
So here at the Site 3 vSphere client, let's go to the networking tab and let's
just confirm
that if we go down to our segment, Site 3 L2 VPN, Site 99 that indeed with the
VM tab
selected here, that little red VM does show up.
So it's on the right segment.
It is powered on.
Let's go ahead and click on it.
And let's also confirm it's IP address 1099-031.
So that part looks great.
Well, we're at it.
Let's also confirm over at Site 4 for the Violet VM over there. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's also confirm over at Site 4 for the Violet VM over there.
So it's IP address 1099-041.
That looks good.
It also indicates right here it's connected to that L2 VPN, Site 99 segment.
So that part looks good.
So we have the right IP addresses.
They're both on the right segments.
So next as Site 3, let's just check the VPN status.
Let's go to the VPN.
So we'll click on networking at Site 3, go down to VPN and the NSX manager here
.
And let's take a look at the L2 VPN sessions, expand that.
And that looks OK.
Everything's green. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Everything's green.
If we look at the IPsec sessions, expand that.
That looks green.
So that part looks good.
So if the L2 VPN session looks good here at Site 3, it's also very likely going
to
look good over at Site 4.
Let's just confirm that as well.
So here is Site 4.
We'll go to networking.
On the left, we'll go down to VPN.
We'll click on L2 VPN sessions and expand that.
That's sure enough, that looks up too.
So let's go back to the Site 3 NSX manager and go to networking.
And let's take a look at the segments. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's take a look at the segments.
So here at Site 3, here is our S3 L2 VPN, SEG 99.
Let's expand that and take a look.
So if we scroll down and take a look at the L2 VPN status, oh, I missed that.
When we were looking back at the overview for our L2 VPN session, it probably
said we
had no segments associated with it.
So let me just confirm that real quick.
So we go back to our VPN section here.
And then here with VPN selected, if we go to our L2 VPN session tab right here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And then here with VPN selected, if we go to our L2 VPN session tab right here,
and
sure enough, I missed it earlier.
Here it says zero segments associated with it.
And that means we don't have any local segments associated with our layer two
VPNs here at
Site 3.
So to fix that, we could actually do it from here or we could go do it at the
segment.
Let's just do it from right here because we're right here.
So we'll click on the three dots, click on edit.
And then over here for segments, we'll click on set and let's add our segment.
So from the dropdown, we'll say we want to include the S3 L2 VPN, SEG 99.
And for the tunnel ID, we use ID of 99, click on save and then click on close WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And for the tunnel ID, we use ID of 99, click on save and then click on close
and then click
on close editing.
So if that was the only problem, we should now have connectivity between the
two VMs when
at site three and when at site four.
So let's bring in those VMs.
So here is the VM from site three right here.
Site address is 1099, 031.
That looks good.
And here is the VM for site four and its IP address is 1099, 041.
So let's test with a quick ping.
So here from the site three red VM, let's do a ping over to 10 dot 99 dot 0 dot WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here from the site three red VM, let's do a ping over to 10 dot 99 dot 0 dot
41 and
hold our breath press center and survey says it is flying.
That is great.
So the problem that the customer had was they failed to right here at site
three.
They failed to include this segment as part of the layer two VPN.
And as a result, this little segment here was isolated just for site three,
like little
island before we connected it.
And one of the beautiful things about layer two VPNs is that we can connect WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And one of the beautiful things about layer two VPNs is that we can connect
multiple sites
and multiple segments and VLANs together just by including them or associating
them with
the layer two VPN.
So thanks for joining me in this adventure in the world of layer two VPNs in NS
X where
we can logically combine multiple segments from multiple sites into one common
layer
two broadcast domain and let devices VMs on those segments communicate as if
they're
on the same local network.
And I look forward to seeing you my friend in another set of skills very, very WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And I look forward to seeing you my friend in another set of skills very, very
soon.
Until then, I hope this has been informative and I'd like to thank you for
viewing.
Thank you so much for watching.