1
00:00:00,000 --> 00:00:00,956

2
00:00:00,956 --> 00:00:03,346
[AUDIO LOGO]

3
00:00:03,346 --> 00:00:08,130

4
00:00:08,130 --> 00:00:12,720
So now that we have VPLS up
and running for customer A,

5
00:00:12,720 --> 00:00:17,340
we're now going to configure
Ethernet over MPLS for customer

6
00:00:17,340 --> 00:00:20,550
B. Before we do that
though, let's go ahead

7
00:00:20,550 --> 00:00:24,450
and jump in and take a look
at some of the details of how

8
00:00:24,450 --> 00:00:27,030
Ethernet over MPLS functions.

9
00:00:27,030 --> 00:00:30,330
Then in the next video, we'll
be jumping into the command line

10
00:00:30,330 --> 00:00:32,340
and getting it up and
running, but let's

11
00:00:32,340 --> 00:00:34,005
start off with those details.

12
00:00:34,005 --> 00:00:36,660

13
00:00:36,660 --> 00:00:42,480
Ethernet over MPLS is really
the most popular form of--

14
00:00:42,480 --> 00:00:45,720
remember the Virtual Private
Wire Service or AToM,

15
00:00:45,720 --> 00:00:48,420
Any transport over MPLS.

16
00:00:48,420 --> 00:00:50,580
And one of the things
it brings to the table

17
00:00:50,580 --> 00:00:55,560
is it's going to remove unneeded
headers from the Ethernet

18
00:00:55,560 --> 00:00:58,320
frame, while it's in transit.

19
00:00:58,320 --> 00:01:02,190
So in other words, while it's
going through the MPLS core.

20
00:01:02,190 --> 00:01:06,180
We're not going to need
things such as the preamble

21
00:01:06,180 --> 00:01:09,750
or the start of frame
limiter or the SFD.

22
00:01:09,750 --> 00:01:12,510
It's also not going to
need the Frame Check

23
00:01:12,510 --> 00:01:15,030
Sequence or the FCS.

24
00:01:15,030 --> 00:01:17,070
Now, of course, these
will be added back

25
00:01:17,070 --> 00:01:22,320
on when it's sent out as plain
Ethernet on the other side.

26
00:01:22,320 --> 00:01:26,460
Also, when we're operating
in Ethernet port mode,

27
00:01:26,460 --> 00:01:31,300
all of the VLAN information
is going to be transmitted.

28
00:01:31,300 --> 00:01:38,430
Now, that said, the VLAN tag can
be overwritten on the egress PE

29
00:01:38,430 --> 00:01:41,850
if you have a need
or desire to do so.

30
00:01:41,850 --> 00:01:45,990
Now, these Ethernet
Virtual Circuits or EVCs,

31
00:01:45,990 --> 00:01:49,500
define the following
aspects of attachment

32
00:01:49,500 --> 00:01:51,390
and virtual circuits.

33
00:01:51,390 --> 00:01:58,500
First is frame matching based
on either one or more VLAN tags.

34
00:01:58,500 --> 00:02:02,970
Number two, the optional
VLAN tag manipulation.

35
00:02:02,970 --> 00:02:04,980
That's what we were just
talking about earlier

36
00:02:04,980 --> 00:02:07,200
with being able to override it.

37
00:02:07,200 --> 00:02:08,880
Of course, we're
going to be handling

38
00:02:08,880 --> 00:02:14,280
traffic forwarding with the
EVC and any additional services

39
00:02:14,280 --> 00:02:17,980
such as QoS.

40
00:02:17,980 --> 00:02:19,900
Something else, of
course, it's important

41
00:02:19,900 --> 00:02:23,950
in any service provider
environment is redundancy.

42
00:02:23,950 --> 00:02:27,640
We have several different ways
to provide this redundancy

43
00:02:27,640 --> 00:02:30,100
in Ethernet over MPLS.

44
00:02:30,100 --> 00:02:35,050
First, we could just do
redundant remote PE routers.

45
00:02:35,050 --> 00:02:37,600
That would certainly
provide redundancy.

46
00:02:37,600 --> 00:02:42,550
We could also have redundant
attachment circuits going out

47
00:02:42,550 --> 00:02:43,930
to the CE.

48
00:02:43,930 --> 00:02:47,890
And we could have
redundant Pseudowires.

49
00:02:47,890 --> 00:02:52,990
Now, something to keep in mind
that if the path between the PE

50
00:02:52,990 --> 00:02:53,990
routers--

51
00:02:53,990 --> 00:02:55,780
so of course, this
means we're referring

52
00:02:55,780 --> 00:02:57,970
to the service provider core.

53
00:02:57,970 --> 00:03:01,900
If that can be
repaired using the IGP,

54
00:03:01,900 --> 00:03:06,160
well, honestly, it's never going
to look like this went down.

55
00:03:06,160 --> 00:03:10,790
The IGP, be it ISS or
OSPF, will converge

56
00:03:10,790 --> 00:03:14,950
so quickly that the original
Pseudowire will simply

57
00:03:14,950 --> 00:03:15,910
be rerouted.

58
00:03:15,910 --> 00:03:18,200
Again, it won't even
look like it went down.

59
00:03:18,200 --> 00:03:20,780
It'll just start following
a different path.

60
00:03:20,780 --> 00:03:25,180
Now, if the failure actually
prevents that repair--

61
00:03:25,180 --> 00:03:27,310
in other words, there's
no way to repair

62
00:03:27,310 --> 00:03:29,200
the primary Pseudowire--

63
00:03:29,200 --> 00:03:33,250
then it would switch to
the backup Pseudowire.

64
00:03:33,250 --> 00:03:36,070
Now, redundancy
can be implemented

65
00:03:36,070 --> 00:03:39,280
either one way or two way.

66
00:03:39,280 --> 00:03:44,260
With one way, only one
side has redundancy.

67
00:03:44,260 --> 00:03:47,470
Normally, that's not
something we're going to want.

68
00:03:47,470 --> 00:03:49,780
Although, it would be
possible that maybe

69
00:03:49,780 --> 00:03:52,900
a customer wants redundancy,
maybe at their headquarters

70
00:03:52,900 --> 00:03:55,240
but maybe, not at a remote site.

71
00:03:55,240 --> 00:03:58,510
But more commonly, we're
going to go ahead and do

72
00:03:58,510 --> 00:04:03,620
two way, where there's
two PEs on both sides.

73
00:04:03,620 --> 00:04:06,100
Now if we do this,
we're going to end up

74
00:04:06,100 --> 00:04:09,370
with a full mesh of Pseudowires.

75
00:04:09,370 --> 00:04:14,560
We're going to end up with only
one Pseudowire being active.

76
00:04:14,560 --> 00:04:17,290
All the rest of them
will be standby.

77
00:04:17,290 --> 00:04:22,180
This also requires
Multi--Chassis Link Aggregation

78
00:04:22,180 --> 00:04:25,360
Group or MC-LAG.

79
00:04:25,360 --> 00:04:30,310
And the protocol used for that
is InterChassis Communication

80
00:04:30,310 --> 00:04:33,880
Protocol or ICCP.

81
00:04:33,880 --> 00:04:37,160
This is what's used to actually
form the redundancy group

82
00:04:37,160 --> 00:04:41,440
so the devices know which
Pseudowires are primary,

83
00:04:41,440 --> 00:04:43,970
which ones are backup,
which ones are active,

84
00:04:43,970 --> 00:04:45,490
which ones are standby.

85
00:04:45,490 --> 00:04:51,430
So ICCP is the protocol that
makes the Multi-Chassis Link

86
00:04:51,430 --> 00:04:54,800
Aggregation Group possible.

87
00:04:54,800 --> 00:04:57,370
So in this video,
we just jumped in

88
00:04:57,370 --> 00:05:00,730
and got a little bit more
detailed information about how

89
00:05:00,730 --> 00:05:03,280
Ethernet over MPLS operates.

90
00:05:03,280 --> 00:05:06,760
And we got to see a little
bit about how redundancy

91
00:05:06,760 --> 00:05:08,990
can work in this environment.

92
00:05:08,990 --> 00:05:10,780
Now, of course,
though, it's time

93
00:05:10,780 --> 00:05:13,360
to jump onto the command
line and get this up

94
00:05:13,360 --> 00:05:17,120
and running for customer
B in our environment.

95
00:05:17,120 --> 00:05:19,580
And that's exactly what
we're going to do next.

96
00:05:19,580 --> 00:05:22,960
Until then, I hope this has
been informative for you,

97
00:05:22,960 --> 00:05:25,950
and I'd like to thank
you for viewing.

98
00:05:25,950 --> 00:05:29,000