1
00:00:00,000 --> 00:00:03,896
[AUDIO LOGO]

2
00:00:03,896 --> 00:00:07,800

3
00:00:07,800 --> 00:00:11,190
So now it's time to finally
jump onto the command line

4
00:00:11,190 --> 00:00:14,410
and get VPLS up and running.

5
00:00:14,410 --> 00:00:16,410
Now, we're going to
start off by looking

6
00:00:16,410 --> 00:00:18,600
at our topology, of
course, and there

7
00:00:18,600 --> 00:00:21,390
is going to be one
change on that topology,

8
00:00:21,390 --> 00:00:24,940
and we'll talk about what
that is and why we needed it.

9
00:00:24,940 --> 00:00:26,940
So let's go ahead and
look at that topology,

10
00:00:26,940 --> 00:00:30,600
and then we'll jump into the
command line and get VPLS up

11
00:00:30,600 --> 00:00:32,880
and running.

12
00:00:32,880 --> 00:00:35,120
So for this
demonstration, we're going

13
00:00:35,120 --> 00:00:38,810
to be using MPLS topology 2.

14
00:00:38,810 --> 00:00:44,300
Now, the reason this changes to
2 is simply because of router 1

15
00:00:44,300 --> 00:00:45,410
right here.

16
00:00:45,410 --> 00:00:50,450
You might notice that this
is not called xr1 like I've

17
00:00:50,450 --> 00:00:51,980
labeled the other routers.

18
00:00:51,980 --> 00:00:58,210
That's because this router
is now running iOS XE.

19
00:00:58,210 --> 00:01:02,230
The reason for this is, as of
the time of this recording,

20
00:01:02,230 --> 00:01:08,590
iOS XR, the version that we are
running, does not support VPLS.

21
00:01:08,590 --> 00:01:11,410
So in order to do this,
we had to swap out

22
00:01:11,410 --> 00:01:14,990
router 1 with an iOS device.

23
00:01:14,990 --> 00:01:17,710
Now, of course, router
3 and 4, they're

24
00:01:17,710 --> 00:01:20,650
going to be fine because they're
just in the transit path,

25
00:01:20,650 --> 00:01:24,940
but iOS XR does not currently
support the configuration

26
00:01:24,940 --> 00:01:27,530
of the VPLS itself.

27
00:01:27,530 --> 00:01:29,770
Now, that said,
let's talk about what

28
00:01:29,770 --> 00:01:30,970
we're going to be building.

29
00:01:30,970 --> 00:01:34,780
We are going to take
VLAN 100, and we're

30
00:01:34,780 --> 00:01:41,350
going to connect router 6,
router 8, and router 9--

31
00:01:41,350 --> 00:01:43,970
all of customer A's sites.

32
00:01:43,970 --> 00:01:47,020
So the headquarter,
site 1 and site 2--

33
00:01:47,020 --> 00:01:49,180
we're going to
connect all of these

34
00:01:49,180 --> 00:01:52,670
on the same VLAN, same
subnet, and get them

35
00:01:52,670 --> 00:01:56,500
so they can communicate with
each other through VPLS.

36
00:01:56,500 --> 00:01:59,140
So this means that the
bulk of our configuration

37
00:01:59,140 --> 00:02:02,050
will be on router
1 and router 5.

38
00:02:02,050 --> 00:02:04,900
We'll also have the default
some of these interfaces

39
00:02:04,900 --> 00:02:08,509
because they do have things like
IP addresses on them and such.

40
00:02:08,509 --> 00:02:10,570
And we'll have to
reconfigure the networks

41
00:02:10,570 --> 00:02:13,490
on routers 6, 8, and 9 as well.

42
00:02:13,490 --> 00:02:15,580
So let's go ahead and
jump into the command line

43
00:02:15,580 --> 00:02:16,670
and get started.

44
00:02:16,670 --> 00:02:19,800
We'll begin on router 1.

45
00:02:19,800 --> 00:02:23,010
So the first thing we want
to do here on router 1

46
00:02:23,010 --> 00:02:26,700
is go ahead and default
interface gigabit 3 just

47
00:02:26,700 --> 00:02:29,670
to wipe out any
existing configuration.

48
00:02:29,670 --> 00:02:32,250
And then we'll go
ahead into gigabit 3

49
00:02:32,250 --> 00:02:34,080
and start configuring it.

50
00:02:34,080 --> 00:02:35,820
Now, the first
thing we want to do

51
00:02:35,820 --> 00:02:39,240
is assign a service instance.

52
00:02:39,240 --> 00:02:43,020
This service instance can really
use any number 1 through 8,000,

53
00:02:43,020 --> 00:02:44,400
as you can see here.

54
00:02:44,400 --> 00:02:47,370
But since we're doing
all of this for VLAN 100,

55
00:02:47,370 --> 00:02:49,990
let's just use the
number 100 for it.

56
00:02:49,990 --> 00:02:54,240
And we want to do this for
ethernet encapsulation.

57
00:02:54,240 --> 00:02:57,540
The next thing we want to
do is set the encapsulation

58
00:02:57,540 --> 00:03:01,140
for the trunk to be VLAN 100.

59
00:03:01,140 --> 00:03:03,300
Now, this, of course,
does have to be

60
00:03:03,300 --> 00:03:07,560
because it's matching on the
VLAN that we're trying to use.

61
00:03:07,560 --> 00:03:12,910
Next, we need to make our
l2vpn VFI configuration.

62
00:03:12,910 --> 00:03:15,480
So we'll say l2vpn.

63
00:03:15,480 --> 00:03:17,850
Again, this is vfi.

64
00:03:17,850 --> 00:03:22,180
We give it a context, and
this is just sort of any name.

65
00:03:22,180 --> 00:03:25,770
So we'll do
something like vfi100

66
00:03:25,770 --> 00:03:29,590
since it's the vfi for
VLAN 100 in our case.

67
00:03:29,590 --> 00:03:31,720
We're going to set the VPN ID.

68
00:03:31,720 --> 00:03:33,840
Now, this just has to
match on both sides,

69
00:03:33,840 --> 00:03:35,580
but again we'll just use 100--

70
00:03:35,580 --> 00:03:37,920
just sort of make this
easy to track what

71
00:03:37,920 --> 00:03:39,700
we're trying to accomplish.

72
00:03:39,700 --> 00:03:42,360
And then we have
to set up a member.

73
00:03:42,360 --> 00:03:44,580
The member is essentially
the remote end,

74
00:03:44,580 --> 00:03:47,910
so this is going to be
router 5's loopback address.

75
00:03:47,910 --> 00:03:52,660
And we want to use the
encapsulation of MPLS.

76
00:03:52,660 --> 00:03:57,120
So this takes care of our
interface and our l2vpn vfi

77
00:03:57,120 --> 00:03:59,220
configuration.

78
00:03:59,220 --> 00:04:01,870
The next thing we need
is a bridge domain.

79
00:04:01,870 --> 00:04:04,230
Now, again, the bridge
domain can pretty much

80
00:04:04,230 --> 00:04:06,270
be any bridge domain ID.

81
00:04:06,270 --> 00:04:10,410
Once again, it just makes sense
to make everything consistent,

82
00:04:10,410 --> 00:04:12,930
so we'll use bridge domain 100.

83
00:04:12,930 --> 00:04:14,940
Just again, keep in
mind, this does not

84
00:04:14,940 --> 00:04:16,740
have to match the VLAN.

85
00:04:16,740 --> 00:04:19,930
This is just a bridge
domain identifier.

86
00:04:19,930 --> 00:04:22,240
Now, we have to put our
two members in here.

87
00:04:22,240 --> 00:04:25,830
So the first member
is gigabit 3--

88
00:04:25,830 --> 00:04:28,900
specifically,
service instance 100.

89
00:04:28,900 --> 00:04:34,010
So this will tie the
VLAN 100 on gigabit 3

90
00:04:34,010 --> 00:04:36,360
into this bridge domain.

91
00:04:36,360 --> 00:04:40,140
Keep in mind, by the way,
we're doing encapsulation

92
00:04:40,140 --> 00:04:44,610
for VLAN 100 right on
the physical interface

93
00:04:44,610 --> 00:04:46,530
of gigabit 3.

94
00:04:46,530 --> 00:04:50,100
If we wanted to offer multiple
services to the customer,

95
00:04:50,100 --> 00:04:54,580
we could definitely do some
interfaces on gigabit 3,

96
00:04:54,580 --> 00:04:58,020
tie different VLANs to
different subinterfaces,

97
00:04:58,020 --> 00:05:01,260
and therefore, different
service instances

98
00:05:01,260 --> 00:05:03,570
to different subinterfaces.

99
00:05:03,570 --> 00:05:06,090
That's how we would
do this if we were

100
00:05:06,090 --> 00:05:09,270
doing multiple emulated LANs.

101
00:05:09,270 --> 00:05:13,080
So that goes ahead
and ties that member.

102
00:05:13,080 --> 00:05:17,310
The next thing we want
to do is tie-in the vfi.

103
00:05:17,310 --> 00:05:22,090
So we say member,
vfi, then, of course,

104
00:05:22,090 --> 00:05:25,010
we're going to put in
the name of the vfi.

105
00:05:25,010 --> 00:05:28,470
So we named it the
vfi100, and that

106
00:05:28,470 --> 00:05:32,250
should take care of the
configuration here on router 1.

107
00:05:32,250 --> 00:05:34,210
Notice two things here.

108
00:05:34,210 --> 00:05:36,720
First, a little bit further
out, but I didn't mention it

109
00:05:36,720 --> 00:05:39,810
when it happened-- but we
see pretty much as soon as we

110
00:05:39,810 --> 00:05:45,900
created that vfi context, that
line protocol on pseudo wire 0

111
00:05:45,900 --> 00:05:47,980
changed to up.

112
00:05:47,980 --> 00:05:50,970
And now that we have the rest
of our configuration done,

113
00:05:50,970 --> 00:05:55,320
notice that the
status of VFI vfi100

114
00:05:55,320 --> 00:05:58,745
has now changed from down to up.

115
00:05:58,745 --> 00:06:00,620
Now, the next thing we
have to do, of course,

116
00:06:00,620 --> 00:06:02,800
is configure router 5.

117
00:06:02,800 --> 00:06:05,720
Now, router 5 is going to
be pretty much the same,

118
00:06:05,720 --> 00:06:08,750
except we're doing
two interfaces.

119
00:06:08,750 --> 00:06:10,900
So in this case, we
want a default interface

120
00:06:10,900 --> 00:06:14,650
gigabit 2 and gigabit 3.

121
00:06:14,650 --> 00:06:17,950
We'll go into our
interface gigabit 2.

122
00:06:17,950 --> 00:06:22,240
We'll set up our service
instance of 100 for ethernet,

123
00:06:22,240 --> 00:06:24,910
and we'll set up
our encapsulation.

124
00:06:24,910 --> 00:06:28,070
We'll do the same thing
for interface gigabit 3.

125
00:06:28,070 --> 00:06:31,570
So that takes care of the
two physical interfaces.

126
00:06:31,570 --> 00:06:34,660
Next, we'll do our l2vpn.

127
00:06:34,660 --> 00:06:37,060
We'll set up our vfi.

128
00:06:37,060 --> 00:06:40,330
Once again, our
VPN ID will be 100.

129
00:06:40,330 --> 00:06:43,360
The member will, of course,
be router 1's loopback.

130
00:06:43,360 --> 00:06:45,460
This is the
pseudowire going back

131
00:06:45,460 --> 00:06:49,760
to router 1 and, of
course, it's using MPLS.

132
00:06:49,760 --> 00:06:52,450
Now, we only need one
vfi because we're only

133
00:06:52,450 --> 00:06:55,210
going back to one other router.

134
00:06:55,210 --> 00:06:58,030
And note, now that both
sides are configured,

135
00:06:58,030 --> 00:07:04,412
we now see that targeted LDP
session come up to router 1.

136
00:07:04,412 --> 00:07:06,870
Now, of course, we're still
going to need our bridge domain

137
00:07:06,870 --> 00:07:08,830
to link these together.

138
00:07:08,830 --> 00:07:12,700
So again, we'll just use bridge
domain 100 to be consistent.

139
00:07:12,700 --> 00:07:15,360
We'll add our
gigabit 2 interface,

140
00:07:15,360 --> 00:07:18,000
we'll add our
gigabit 3 interface,

141
00:07:18,000 --> 00:07:20,100
and we'll add our vfi.

142
00:07:20,100 --> 00:07:23,010
Once again, we
see the vfi go up.

143
00:07:23,010 --> 00:07:25,390
We'll exit configuration.

144
00:07:25,390 --> 00:07:27,510
And let's do some verification.

145
00:07:27,510 --> 00:07:31,180
Let's just go back to router
1 to do our verification.

146
00:07:31,180 --> 00:07:33,880
So some good commands
we can do here--

147
00:07:33,880 --> 00:07:36,840
we can start with just
a show bridge domain.

148
00:07:36,840 --> 00:07:39,090
Things to note in the
bridge domain-- it is

149
00:07:39,090 --> 00:07:41,820
up and Mac learning is enabled.

150
00:07:41,820 --> 00:07:45,960
And we also see that our
gigabit 3 service instance 100

151
00:07:45,960 --> 00:07:51,240
and our VFI vfi100 with
the neighbor 10.5.5.5--

152
00:07:51,240 --> 00:07:55,970
VPN ID 100 is currently up.

153
00:07:55,970 --> 00:08:00,770
We can also do a show l2vpn vfi.

154
00:08:00,770 --> 00:08:05,180
We see that our vfi name
vfi100 is currently up.

155
00:08:05,180 --> 00:08:08,540
It is a multipoint
connection, and the signaling

156
00:08:08,540 --> 00:08:10,430
is being done by LDP.

157
00:08:10,430 --> 00:08:13,200
We saw that LDP session come up.

158
00:08:13,200 --> 00:08:15,710
We also see the VPN ID of 100--

159
00:08:15,710 --> 00:08:19,310
that it's attached to
bridge domain 100 using

160
00:08:19,310 --> 00:08:21,920
pseudo-port
interface pseudowire,

161
00:08:21,920 --> 00:08:24,440
and this is an automatically
created number.

162
00:08:24,440 --> 00:08:30,260
It just created 100001, and it's
connecting interface pseudowire

163
00:08:30,260 --> 00:08:35,570
100002 going over to router 5.

164
00:08:35,570 --> 00:08:38,419
Another good command is
if we take off the vfi

165
00:08:38,419 --> 00:08:42,409
and instead say
service vfi, and then

166
00:08:42,409 --> 00:08:46,640
ask for the particular
name vfi100,

167
00:08:46,640 --> 00:08:48,930
we can get more
information on this.

168
00:08:48,930 --> 00:08:50,730
It's a slightly
different output,

169
00:08:50,730 --> 00:08:53,600
but we see both sides
of the pseudowire,

170
00:08:53,600 --> 00:08:56,070
so we see both of those numbers.

171
00:08:56,070 --> 00:08:58,610
We see that one of them
is, of course local,

172
00:08:58,610 --> 00:09:02,120
and the other one is
encapsulating MPLS going over

173
00:09:02,120 --> 00:09:06,650
to router 5, but both of
these are currently up.

174
00:09:06,650 --> 00:09:08,840
Another good command to watch--

175
00:09:08,840 --> 00:09:16,820
show ethernet service-- instance
ID is 100 on interface gig 3,

176
00:09:16,820 --> 00:09:20,270
and we can ask for detail.

177
00:09:20,270 --> 00:09:22,550
Here, of course, we see
the instance ID, which

178
00:09:22,550 --> 00:09:24,530
is exactly what we asked for.

179
00:09:24,530 --> 00:09:27,746
We see that it's
associated to gigabit 3.

180
00:09:27,746 --> 00:09:31,550
We see that the
encapsulation is dot1q 100,

181
00:09:31,550 --> 00:09:34,280
so it's going to VLAN 100.

182
00:09:34,280 --> 00:09:40,670
The protocol type is 0x8100,
which remember, is 802.1Q.

183
00:09:40,670 --> 00:09:43,160
The status is currently up.

184
00:09:43,160 --> 00:09:46,190
And we actually see that we have
a couple of packets and bytes

185
00:09:46,190 --> 00:09:49,080
coming in at this point.

186
00:09:49,080 --> 00:09:52,260
So all of this looks like
it's functioning properly.

187
00:09:52,260 --> 00:09:54,710
Let's go ahead and check
the actual connectivity

188
00:09:54,710 --> 00:09:56,340
through our environment.

189
00:09:56,340 --> 00:10:00,380
Let's go over to router 6, which
is customer A's headquarters.

190
00:10:00,380 --> 00:10:02,360
What we're going
to do on router 6

191
00:10:02,360 --> 00:10:05,870
is simply go into the
interface gigabit 1--

192
00:10:05,870 --> 00:10:08,450
set the IP address
so that all of these

193
00:10:08,450 --> 00:10:09,870
are on the same subnet.

194
00:10:09,870 --> 00:10:14,450
So we'll set this
to 192.168.100.6,

195
00:10:14,450 --> 00:10:19,340
so just representative of
VLAN 100 and host ID 6.

196
00:10:19,340 --> 00:10:24,080
We'll just make that a slash
24, and exit configuration.

197
00:10:24,080 --> 00:10:26,960
We'll do the same basic
thing on routers 8 and 9.

198
00:10:26,960 --> 00:10:34,840

199
00:10:34,840 --> 00:10:36,190
And again, on router 9.

200
00:10:36,190 --> 00:10:44,920

201
00:10:44,920 --> 00:10:46,760
So now, let's do some testing.

202
00:10:46,760 --> 00:10:53,710
We should be able to ping
192.168.100.6 and dot 8.

203
00:10:53,710 --> 00:10:56,470
So we can see that
after the ARP completes,

204
00:10:56,470 --> 00:11:00,320
that we are, in fact, able to
ping both of those devices.

205
00:11:00,320 --> 00:11:03,970
Now, just for one final
test, let's bring up

206
00:11:03,970 --> 00:11:06,400
routing between our customers.

207
00:11:06,400 --> 00:11:08,950
Now, we'll just do this
a real quick, easy way.

208
00:11:08,950 --> 00:11:12,580
We'll just bring up OSPF
on all of the interfaces

209
00:11:12,580 --> 00:11:14,350
on the customer's routers--

210
00:11:14,350 --> 00:11:16,820
real simple configuration.

211
00:11:16,820 --> 00:11:18,820
So let's go over to router 6.

212
00:11:18,820 --> 00:11:20,740
Now, we've set this
up numerous times,

213
00:11:20,740 --> 00:11:23,650
so I'm just going to paste
in the configuration.

214
00:11:23,650 --> 00:11:26,080
Again, all we're doing
is turning on OSPF,

215
00:11:26,080 --> 00:11:29,710
setting the router ID, and then
using the network statement

216
00:11:29,710 --> 00:11:33,400
to put all interfaces
into area 0.

217
00:11:33,400 --> 00:11:36,130
We're going to do the same
thing on routers 8 and 9.

218
00:11:36,130 --> 00:11:38,720
We'll just be using a
different router ID.

219
00:11:38,720 --> 00:11:42,640
So that takes care of
router 8 and router 9.

220
00:11:42,640 --> 00:11:45,370
So we see here in the console
that our neighborships

221
00:11:45,370 --> 00:11:49,120
with routers 8 and
6 have both come up.

222
00:11:49,120 --> 00:11:51,590
Let's go ahead and verify that.

223
00:11:51,590 --> 00:11:53,860
If we do a show
ip ospf neighbors,

224
00:11:53,860 --> 00:11:55,960
we see that they are in fact up.

225
00:11:55,960 --> 00:12:00,040
Router 6 is listed as the
DR-OTHER, or the DROTHER.

226
00:12:00,040 --> 00:12:04,900
Router 8 is listed as the
BDR, which means router 9 here

227
00:12:04,900 --> 00:12:07,060
is going to be the DR.

228
00:12:07,060 --> 00:12:10,090
If we do a show
IP route OSPF, we

229
00:12:10,090 --> 00:12:13,180
see here that we are
learning other routes

230
00:12:13,180 --> 00:12:17,170
from the other routers in
the customer a network.

231
00:12:17,170 --> 00:12:19,870
Let's go ahead and verify
that those are working.

232
00:12:19,870 --> 00:12:23,410
Rather than a ping, let's
go ahead and do this time.

233
00:12:23,410 --> 00:12:26,050
Let's trace through that
network on router 6.

234
00:12:26,050 --> 00:12:30,370
Let's trace to the 10.100.1.6.

235
00:12:30,370 --> 00:12:34,030
And notice that it looks
like it's going directly.

236
00:12:34,030 --> 00:12:35,890
We, of course, reached
the destination.

237
00:12:35,890 --> 00:12:37,790
That's working as it
would be expected,

238
00:12:37,790 --> 00:12:40,090
but we don't see any of
the hops in the middle

239
00:12:40,090 --> 00:12:43,510
because it's going
through our l2vpn.

240
00:12:43,510 --> 00:12:45,800
We can verify 8 as well.

241
00:12:45,800 --> 00:12:49,580
It has an address
10.100.1.8, on it.

242
00:12:49,580 --> 00:12:52,300
And this should look
pretty much the same way.

243
00:12:52,300 --> 00:12:54,620
We can see here that it does.

244
00:12:54,620 --> 00:12:56,920
So this is working properly.

245
00:12:56,920 --> 00:13:00,700
Our l2vpn is up and running,
we have OSPF neighborships

246
00:13:00,700 --> 00:13:05,200
between the customer routers,
and we have full reachability

247
00:13:05,200 --> 00:13:08,100
between the devices.

248
00:13:08,100 --> 00:13:14,070
In this video, we got VPLS
up and running for customer A

249
00:13:14,070 --> 00:13:18,160
using VLAN 100 between
all of their sites.

250
00:13:18,160 --> 00:13:21,750
Now, of course, we could do
different networks for them

251
00:13:21,750 --> 00:13:22,530
if we wanted to.

252
00:13:22,530 --> 00:13:24,840
This has just been an
example of doing one,

253
00:13:24,840 --> 00:13:26,880
but we could just
duplicate exactly what

254
00:13:26,880 --> 00:13:29,430
we did using, of course,
different numbers

255
00:13:29,430 --> 00:13:31,530
and subinterfaces.

256
00:13:31,530 --> 00:13:35,910
So the next thing we want to
look at is ethernet over MPLS,

257
00:13:35,910 --> 00:13:39,070
and that's exactly what
we get to look at next.

258
00:13:39,070 --> 00:13:42,240
Until then, I hope this has
been informative for you

259
00:13:42,240 --> 00:13:45,320
and I'd like to thank
you for viewing.

260
00:13:45,320 --> 00:13:49,000