WEBVTT

1
00:00.000 --> 00:03.260
All right, it's time to jump into the lab and do some ether channel

2
00:03.260 --> 00:04.040
configuration.

3
00:04.040 --> 00:06.680
We're going to start with static ether channels.

4
00:06.680 --> 00:10.100
Now the way this topology works in this lab environment, we've got a lab

5
00:10.100 --> 00:10.840
diagram down

6
00:10.840 --> 00:14.930
below, but just so we have it on the screen here, we are looking at two

7
00:14.930 --> 00:15.800
switches, which

8
00:15.800 --> 00:17.160
is one and two.

9
00:17.160 --> 00:19.080
We have four connections between them.

10
00:19.080 --> 00:20.840
We're probably going to want to ether channel those.

11
00:20.840 --> 00:25.240
And we also have this access switch that has a pair of connections up to each

12
00:25.240 --> 00:25.880
of the parent

13
00:25.880 --> 00:27.040
switches.

14
00:27.040 --> 00:32.590
So here we're on switch one, and let's go ahead and look at, now let's just do
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:27.040 --> 00:32.590
So here we're on switch one, and let's go ahead and look at, now let's just do

15
00:32.590 --> 00:33.120
a show

16
00:33.120 --> 00:36.360
spanning tree, and we'll look at VLAN one.

17
00:36.360 --> 00:39.880
So looking at the spanning tree from a VLAN one perspective, we see that this

18
00:39.880 --> 00:40.680
switch actually

19
00:40.680 --> 00:43.040
has a lot of interfaces.

20
00:43.040 --> 00:47.230
We're going to be focused up here on these three or four interfaces, gig zero

21
00:47.230 --> 00:47.960
slash zero

22
00:47.960 --> 00:52.360
through gig zero slash three, which exists between switches one and two.

23
00:52.360 --> 00:55.040
So we see the effect of having multiple layer two links.

24
00:55.040 --> 00:57.920
Every of them are in a blocked state here.

25
00:57.920 --> 01:01.100
And that's just what we have to do from an ethernet perspective in order to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:57.920 --> 01:01.100
And that's just what we have to do from an ethernet perspective in order to

26
01:01.100 --> 01:01.520
make it

27
01:01.520 --> 01:03.080
work loop free.

28
01:03.080 --> 01:07.990
So the way we prevent that and is, well, I guess bundle all of this bandwidth

29
01:07.990 --> 01:08.600
together

30
01:08.600 --> 01:11.200
as well is to use an ether channel.

31
01:11.200 --> 01:14.570
So we're going to do a config T, we're going to get onto that range of

32
01:14.570 --> 01:15.600
interfaces gig zero

33
01:15.600 --> 01:17.400
slash zero through three.

34
01:17.400 --> 01:21.240
And we're going to use the channel group command.

35
01:21.240 --> 01:26.480
Now this channel group command is going to allow us to create that virtual port

36
01:26.480 --> 01:26.920
channel

37
01:26.920 --> 01:28.160
interface.

38
01:28.160 --> 01:33.080
So when I do channel group and question mark, I see that I can number this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:28.160 --> 01:33.080
So when I do channel group and question mark, I see that I can number this.

39
01:33.080 --> 01:37.040
And so if I make, for example, channel group 10, this will make the interface

40
01:37.040 --> 01:37.760
port channel

41
01:37.760 --> 01:40.200
10 on the switch here.

42
01:40.200 --> 01:42.480
And then I'm going to say mode.

43
01:42.480 --> 01:46.560
And then the question mark here shows me those five different options we talked

44
01:46.560 --> 01:46.720
about where

45
01:46.720 --> 01:53.040
we've got auto and desirable, which are, which is for PAGP, PAGP, there we go.

46
01:53.040 --> 01:56.160
And we also have active and passive for LECP.

47
01:56.160 --> 02:00.740
And then mode on is simply saying, Hey, we want to force these ports into an
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:56.160 --> 02:00.740
And then mode on is simply saying, Hey, we want to force these ports into an

48
02:00.740 --> 02:01.680
ether channel.

49
02:01.680 --> 02:04.760
So we're going to say mode on here.

50
02:04.760 --> 02:09.520
And then I can do a show run interface port channel 10.

51
02:09.520 --> 02:11.680
And we see that there's no configuration on it.

52
02:11.680 --> 02:16.080
So I can get on to interface port channel 10 and say, let's place this into

53
02:16.080 --> 02:16.840
switch trunk

54
02:16.840 --> 02:19.400
encapsulation dot one queue and switch mode trunk.

55
02:19.400 --> 02:21.360
So we're converting it to a trunk.

56
02:21.360 --> 02:24.280
So I just place that onto interface port channel 10.

57
02:24.280 --> 02:30.240
If I do a show run on interface, just pick gig zero zero, one of these member
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:24.280 --> 02:30.240
If I do a show run on interface, just pick gig zero zero, one of these member

58
02:30.240 --> 02:31.480
interfaces,

59
02:31.480 --> 02:36.590
we see that the configuration that I put on the parent interface, this port

60
02:36.590 --> 02:37.840
channel interface

61
02:37.840 --> 02:41.920
got pushed down to the member interface.

62
02:41.920 --> 02:44.400
So this is the relationship that we want to work with.

63
02:44.400 --> 02:47.940
Any configuration we want to add should go on the port channel interface so it

64
02:47.940 --> 02:48.360
can push

65
02:48.360 --> 02:51.000
down to all the member interfaces.

66
02:51.000 --> 02:55.840
So from here, we can do a verification command to see what it's looking like.

67
02:55.840 --> 02:57.400
And we're going to find that way.

68
02:57.400 --> 03:01.340
Well, at this point, it's not really working, or at least it shouldn't be,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
02:57.400 --> 03:01.340
Well, at this point, it's not really working, or at least it shouldn't be,

69
03:01.340 --> 03:01.800
because I've

70
03:01.800 --> 03:05.360
put the port channel on this side, but not the other side.

71
03:05.360 --> 03:07.680
And this is what I'm talking about here.

72
03:07.680 --> 03:12.720
We do see that we're getting all kinds of errors, because we're fortunately

73
03:12.720 --> 03:13.880
able to interpret

74
03:13.880 --> 03:19.050
some STP BPDUs and figure out that maybe the other side doesn't agree with us

75
03:19.050 --> 03:19.560
on the

76
03:19.560 --> 03:21.320
whole port channel thing.

77
03:21.320 --> 03:26.180
So if I do a show ether channel summary, this is a really good command that we

78
03:26.180 --> 03:26.640
're going

79
03:26.640 --> 03:31.020
to want to get used to, and it shows that port channel 10, if we look at SD in
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:26.640 --> 03:31.020
to want to get used to, and it shows that port channel 10, if we look at SD in

80
03:31.020 --> 03:31.560
here,

81
03:31.560 --> 03:33.840
the S is going to stand for switching.

82
03:33.840 --> 03:37.760
It basically means that we're in a layer two operation rather than layer three,

83
03:37.760 --> 03:38.000
and then

84
03:38.000 --> 03:42.720
the D is going to also tell us something important, which is that we are in a

85
03:42.720 --> 03:44.120
down state.

86
03:44.120 --> 03:47.120
Remember what we said before, we want to see these capital P's.

87
03:47.120 --> 03:48.720
It tells us we're in a port channel.

88
03:48.720 --> 03:52.640
So the fact that we're in, you know, the S is just telling us layer two, the

89
03:52.640 --> 03:53.280
fact that

90
03:53.280 --> 03:56.950
we're in a down state, all these member interfaces are in a down state, that's

91
03:56.950 --> 03:58.760
because really

92
03:58.760 --> 04:02.960
the switch is leveraging spanning tree to say the other side isn't configured
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
03:58.760 --> 04:02.960
the switch is leveraging spanning tree to say the other side isn't configured

93
04:02.960 --> 04:03.400
yet.

94
04:03.400 --> 04:06.660
So let's get on to switch to we'll do a show CDP neighbor just to make sure

95
04:06.660 --> 04:07.200
that we know

96
04:07.200 --> 04:08.880
which ports we're using.

97
04:08.880 --> 04:10.440
Switch one is connected.

98
04:10.440 --> 04:15.130
It looks like gig zero zero to gig zero zero, gig zero one to gig zero one and

99
04:15.130 --> 04:15.680
so on and

100
04:15.680 --> 04:16.680
so forth.

101
04:16.680 --> 04:20.870
So I'm just getting on to those interfaces, interface range, gig zero slash

102
04:20.870 --> 04:21.640
zero through

103
04:21.640 --> 04:23.040
three.

104
04:23.040 --> 04:25.000
And this time I'm going to do something a little different.

105
04:25.000 --> 04:30.120
I'm going to say switch trunk encapsulation dot one Q and switch mode trunk.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
04:25.000 --> 04:30.120
I'm going to say switch trunk encapsulation dot one Q and switch mode trunk.

106
04:30.120 --> 04:33.240
So I just place these member interfaces into a trunk.

107
04:33.240 --> 04:35.280
Now I can use that channel group 10.

108
04:35.280 --> 04:41.860
In fact, let's just a 20 mode on remember, we use 10 on the other side 20 on

109
04:41.860 --> 04:42.520
this side.

110
04:42.520 --> 04:44.480
And what we're going to find is that ID doesn't matter.

111
04:44.480 --> 04:46.800
It's only locally significant.

112
04:46.800 --> 04:51.010
So in the real world, we try to line them up, but it's important to recognize

113
04:51.010 --> 04:51.720
sometimes

114
04:51.720 --> 04:53.480
that this is just an identifier.

115
04:53.480 --> 04:57.680
It doesn't actually get used at the control plane or the data plane.

116
04:57.680 --> 05:01.490
It's just something that we can look at and say, Hey, that is port channel 10
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
04:57.680 --> 05:01.490
It's just something that we can look at and say, Hey, that is port channel 10

117
05:01.490 --> 05:01.740
between

118
05:01.740 --> 05:03.340
those two switches.

119
05:03.340 --> 05:08.910
So port channel 20, if I do a show run interface on port channel 20, we're

120
05:08.910 --> 05:10.220
going to find that

121
05:10.220 --> 05:14.410
it already comes equipped with a couple commands because these commands were

122
05:14.410 --> 05:15.260
the same on those

123
05:15.260 --> 05:16.420
member interfaces.

124
05:16.420 --> 05:19.960
It was able to interpret that it should place the port channel into that.

125
05:19.960 --> 05:23.610
Now if there's any issues whatsoever, I would just recommend getting on to this

126
05:23.610 --> 05:24.180
interface

127
05:24.180 --> 05:28.480
range and doing a default interface or getting rid of the commands that might

128
05:28.480 --> 05:29.360
be preventing

129
05:29.360 --> 05:31.480
it from getting added to a bundle.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

129
05:29.360 --> 05:31.480
it from getting added to a bundle.

130
05:31.480 --> 05:35.480
Because for example, if I were to let's just let's see here.

131
05:35.480 --> 05:38.920
So do show IP and brief.

132
05:38.920 --> 05:41.880
We see we've got a couple more interfaces here.

133
05:41.880 --> 05:49.360
So if I were to do a show run on interface gig one zero, it's not in trunk.

134
05:49.360 --> 05:53.100
So if I get on to gig one zero and say, Hey, I want you to be part of this

135
05:53.100 --> 05:53.880
channel group

136
05:53.880 --> 05:56.960
channel group 20 mode on.

137
05:56.960 --> 05:59.960
So the IO will keep.

138
05:59.960 --> 06:04.250
So remember, we said that iOS XC has a limit of eight ports in the virtual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

138
05:59.960 --> 06:04.250
So remember, we said that iOS XC has a limit of eight ports in the virtual

139
06:04.250 --> 06:04.920
space.

140
06:04.920 --> 06:08.080
These virtual switches, they do limit us to four.

141
06:08.080 --> 06:10.080
So that's something to keep in mind as well.

142
06:10.080 --> 06:13.440
So different platforms, especially the virtual platforms might be a little

143
06:13.440 --> 06:14.120
different.

144
06:14.120 --> 06:20.520
So if I were to get on to and let's just say gig zero three and say no channel

145
06:20.520 --> 06:21.760
group 20

146
06:21.760 --> 06:23.360
mode on.

147
06:23.360 --> 06:26.710
Now if I do a show either channel summary, we should see that we only have

148
06:26.710 --> 06:27.240
three ports

149
06:27.240 --> 06:33.670
in the channel and we do now I can go into gig zero one and say channel group
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
06:27.240 --> 06:33.670
in the channel and we do now I can go into gig zero one and say channel group

150
06:33.670 --> 06:34.920
20 mode

151
06:34.920 --> 06:35.920
on.

152
06:35.920 --> 06:44.880
All right, so now if I do a show run on interface gig one zero, notice exactly

153
06:44.880 --> 06:46.760
what this error

154
06:46.760 --> 06:48.880
message actually told me.

155
06:48.880 --> 06:51.920
It's that this doesn't match the configuration.

156
06:51.920 --> 06:56.680
So we might in some situations see that, you know, like in this example, I don

157
06:56.680 --> 06:57.320
't have this

158
06:57.320 --> 07:00.820
in a trunk operation, port channels already in a trunk operation, and therefore
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

158
06:57.320 --> 07:00.820
in a trunk operation, port channels already in a trunk operation, and therefore

159
07:00.820 --> 07:01.240
they're

160
07:01.240 --> 07:02.520
not compatible.

161
07:02.520 --> 07:07.640
Other times it might take those ports and push configuration down, especially

162
07:07.640 --> 07:08.000
if it's

163
07:08.000 --> 07:11.520
from the perspective of adding configuration to the port channel interface.

164
07:11.520 --> 07:13.720
So sometimes iOS will handle it for us.

165
07:13.720 --> 07:16.360
Other times we're going to have to handle it ourselves.

166
07:16.360 --> 07:24.780
So if I do a show ether channel summary, we're going to find that one of these

167
07:24.780 --> 07:25.720
ports is in

168
07:25.720 --> 07:31.440
a suspended state because it is not compatible with the port channel.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
07:25.720 --> 07:31.440
a suspended state because it is not compatible with the port channel.

169
07:31.440 --> 07:34.940
As soon as I say, hey, let's go ahead and put you into a trunk, then it will

170
07:34.940 --> 07:35.720
show up.

171
07:35.720 --> 07:40.990
But I do want to just say default interface gig one zero, which will pull it

172
07:40.990 --> 07:41.920
out of being

173
07:41.920 --> 07:49.110
in the bundle, and let's get back onto gig zero three and say channel group 20

174
07:49.110 --> 07:50.120
mode on.

175
07:50.120 --> 07:51.560
There we go.

176
07:51.560 --> 07:55.640
So show ether channel summary.

177
07:55.640 --> 07:59.040
I want to make sure that all four are online.

178
07:59.040 --> 08:02.000
They all have that capital P there over on the right.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

178
07:59.040 --> 08:02.000
They all have that capital P there over on the right.

179
08:02.000 --> 08:05.000
Each port is in the port channeled state.

180
08:05.000 --> 08:10.580
The U here replaced the D. So we see over here it's up and down, or I guess

181
08:10.580 --> 08:11.280
they technically

182
08:11.280 --> 08:12.280
say in use.

183
08:12.280 --> 08:15.630
But you know, however you want to think of it, I always think of it as being up

184
08:15.630 --> 08:15.880
.

185
08:15.880 --> 08:20.240
But then over here, we see that we get different statuses as well, like P, like

186
08:20.240 --> 08:21.000
we said, being

187
08:21.000 --> 08:25.440
part of the port channel, a lowercase s is for being suspended.

188
08:25.440 --> 08:29.400
And we have now seen those specific examples throughout this video.