WEBVTT

1
00:00.000 --> 00:05.360
Now, when we get onto our configuration for our switch, we want to configure a

2
00:05.360 --> 00:06.480
port channel.

3
00:06.480 --> 00:08.920
This is going to involve two aspects.

4
00:08.920 --> 00:14.120
First of all, we need to select what becomes known as our member interfaces.

5
00:14.120 --> 00:19.260
The member interfaces are going to be placed into a bundle that, well, I mean,

6
00:19.260 --> 00:19.880
after all

7
00:19.880 --> 00:24.150
the ether channel talk, Cisco calls the bundle a port channel interface,

8
00:24.150 --> 00:25.360
usually something

9
00:25.360 --> 00:29.320
like PO and then we'll say 10 or 20.

10
00:29.320 --> 00:31.560
I give it an ID.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.320 --> 00:31.560
I give it an ID.

11
00:31.560 --> 00:35.960
And so this becomes a logical configuration configured interface.

12
00:35.960 --> 00:39.990
Now, I know I like to use dots for layer three, so we don't want to use a dot

13
00:39.990 --> 00:40.560
here.

14
00:40.560 --> 00:45.850
I'll just use a square because it's not a layer three interface per se, but it

15
00:45.850 --> 00:46.160
is a

16
00:46.160 --> 00:49.240
separate interface that gets configured.

17
00:49.240 --> 00:55.270
All of these member interfaces get connected to this port channel ID and we

18
00:55.270 --> 00:56.240
connect it

19
00:56.240 --> 00:59.440
using the channel group command.

20
00:59.440 --> 01:04.170
So I will say it's a little bit unfortunate that Cisco seems to use a lot of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.440 --> 01:04.170
So I will say it's a little bit unfortunate that Cisco seems to use a lot of

21
01:04.170 --> 01:04.960
different

22
01:04.960 --> 01:07.680
terms for configuring ether channels.

23
01:07.680 --> 01:13.040
For example, as we mentioned, we've got commands like the show ether channel

24
01:13.040 --> 01:13.280
summary and show

25
01:13.280 --> 01:18.000
ether channel summary uses the ethernet or ether channel word.

26
01:18.000 --> 01:19.640
So we've got ether channel in here.

27
01:19.640 --> 01:23.580
Meanwhile, I have to create a port channel interface and I have to use the

28
01:23.580 --> 01:24.440
channel group

29
01:24.440 --> 01:28.280
command in order to add a member interface into the bundle.

30
01:28.280 --> 01:34.100
So yeah, it is what it is, but either way, I'm going to use the ID here and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:28.280 --> 01:34.100
So yeah, it is what it is, but either way, I'm going to use the ID here and

31
01:34.100 --> 01:34.980
this is what

32
01:34.980 --> 01:40.800
gets placed or what gets matched to the logical port channel interface.

33
01:40.800 --> 01:45.340
So these member links now are going to be part of this port channel and the

34
01:45.340 --> 01:46.400
configuration

35
01:46.400 --> 01:50.440
is going to end up getting synchronized between the two.

36
01:50.440 --> 01:54.670
Now what's most proper is that once this has all been configured that I as the

37
01:54.670 --> 01:55.200
admin,

38
01:55.200 --> 01:59.700
if I want to change configuration, let's say I want to add a VLAN to the link,

39
01:59.700 --> 01:59.840
that

40
01:59.840 --> 02:05.220
I should perform that configuration here on the logical interface and then it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:59.840 --> 02:05.220
I should perform that configuration here on the logical interface and then it

41
02:05.220 --> 02:06.240
gets pushed

42
02:06.240 --> 02:09.160
down as part of the syncing process.

43
02:09.160 --> 02:14.000
Furthermore, if it gets out of sync, if I do push configuration down here to

44
02:14.000 --> 02:15.440
the interface,

45
02:15.440 --> 02:22.130
then we might actually see that the interface gets removed from the bundle

46
02:22.130 --> 02:23.480
because the configuration

47
02:23.480 --> 02:24.880
is out of sync.

48
02:24.880 --> 02:28.240
So this synchronization is really a one way synchronization.

49
02:28.240 --> 02:35.390
The configuration gets pushed down from the logical interface and so things
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:28.240 --> 02:35.390
The configuration gets pushed down from the logical interface and so things

50
02:35.390 --> 02:36.720
like VLAN lists

51
02:36.720 --> 02:41.110
and whether it's an access port or a chunk port and all of these types of

52
02:41.110 --> 02:42.240
configurations

53
02:42.240 --> 02:46.880
really need to go up here on the port channel ID and allow it to push that

54
02:46.880 --> 02:48.000
configuration

55
02:48.000 --> 02:51.480
down to our member interfaces.

56
02:51.480 --> 02:55.210
Now we're going to want to zero in on this command later when we get into the

57
02:55.210 --> 02:55.760
lab because

58
02:55.760 --> 03:03.320
this command is very useful and it can tell us our member interface statuses.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:55.760 --> 03:03.320
this command is very useful and it can tell us our member interface statuses.

59
03:03.320 --> 03:06.570
It's important that we be able to interpret this command and there are several

60
03:06.570 --> 03:06.880
status

61
03:06.880 --> 03:09.680
indicators that we're going to want to be aware of.

62
03:09.680 --> 03:15.280
First of all, P means that we are port channeled, which again, now we're using

63
03:15.280 --> 03:16.440
the port channel

64
03:16.440 --> 03:20.730
word instead of ether channel, but the fact that we're port channeled means

65
03:20.730 --> 03:21.440
that we are

66
03:21.440 --> 03:23.640
online and operational.

67
03:23.640 --> 03:25.200
This is what we want to see.

68
03:25.200 --> 03:30.400
We want to see capital P's because that tells us that everything is healthy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
03:25.200 --> 03:30.400
We want to see capital P's because that tells us that everything is healthy.

69
03:30.400 --> 03:34.920
So I might see, for example, as part of this command that we're talking about

70
03:34.920 --> 03:35.520
port channel

71
03:35.520 --> 03:39.640
10 interface and then I've got different member interfaces.

72
03:39.640 --> 03:44.200
So I'll see, for example, like gig zero zero and gig zero one listed.

73
03:44.200 --> 03:49.960
I'll just write them here, gig zero one, and then we'll have status here.

74
03:49.960 --> 03:54.110
And so I'm probably going to want to see that there's a capital P in here that

75
03:54.110 --> 03:54.960
represents

76
03:54.960 --> 04:00.960
that we're online and operational, but we might also see D for being down.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:54.960 --> 04:00.960
that we're online and operational, but we might also see D for being down.

77
04:00.960 --> 04:06.000
So that's not ideal. Maybe I've got a third link in here and it's in a down

78
04:06.000 --> 04:06.920
state.

79
04:06.920 --> 04:11.680
And furthermore, we might see an eye for independent.

80
04:11.680 --> 04:15.930
This one shouldn't show up very often, but where it can show up is that

81
04:15.930 --> 04:16.920
scenario that

82
04:16.920 --> 04:22.850
we diagrammed earlier, where we had four connections and I'm using LACP for

83
04:22.850 --> 04:25.200
dynamic negotiation.

84
04:25.200 --> 04:29.690
At this point, I might place LACP properly on four ports here, three ports down

85
04:29.690 --> 04:30.320
here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:29.690 --> 04:30.320
here,

86
04:30.320 --> 04:35.030
and then we bundle these together, but it's going to report that this interface

87
04:35.030 --> 04:35.320
is in

88
04:35.320 --> 04:39.770
an independent status. It's configured to be part of the bundle, but it's not

89
04:39.770 --> 04:40.240
actively

90
04:40.240 --> 04:45.520
part of the bundle. So it's kind of operating in standalone operation,

91
04:45.520 --> 04:46.800
basically an unbundled

92
04:46.800 --> 04:55.280
state. And lastly, we might see a little s and this stands for suspended.

93
04:55.280 --> 05:00.720
So let's say we've got another one on here. So gig zero three suspended.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:55.280 --> 05:00.720
So let's say we've got another one on here. So gig zero three suspended.

94
05:00.720 --> 05:06.500
What this means is that this is out of sync and therefore it's not allowed to

95
05:06.500 --> 05:07.160
be part

96
05:07.160 --> 05:12.650
of the bundle. So maybe I got on to one of these interfaces and I made a

97
05:12.650 --> 05:13.480
configuration

98
05:13.480 --> 05:19.440
change that made it out of sync with its logical port.

99
05:19.440 --> 05:24.380
So because of this change, it was placed into the suspended state until we fix

100
05:24.380 --> 05:25.360
this issue.

101
05:25.360 --> 05:28.620
So if we see suspended, that usually means that we need to look at the

102
05:28.620 --> 05:29.520
configuration

103
05:29.520 --> 05:35.440
of the member interface itself. Now fortunately, port channels and ether
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
05:29.520 --> 05:35.440
of the member interface itself. Now fortunately, port channels and ether

104
05:35.440 --> 05:36.200
channels, these are

105
05:36.200 --> 05:42.500
fairly dynamic and I can add and remove members without taking down the entire

106
05:42.500 --> 05:43.880
connection.

107
05:43.880 --> 05:48.290
So I might have, for example, two connections bundled together and then I

108
05:48.290 --> 05:49.200
decide to pull

109
05:49.200 --> 05:53.960
two more. So now that I've got these two, I need to get on here and I need to

110
05:53.960 --> 05:54.520
use this

111
05:54.520 --> 06:00.330
channel group command to place them into the bundle. So I say channel group
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
05:54.520 --> 06:00.330
channel group command to place them into the bundle. So I say channel group

112
06:00.330 --> 06:01.360
here, I place

113
06:01.360 --> 06:07.060
them into the bundle and I do that on both sides. Furthermore, if I'm removing

114
06:07.060 --> 06:07.960
those two,

115
06:07.960 --> 06:11.700
then I can just remove the channel group configuration and it will no longer be

116
06:11.700 --> 06:13.040
part of the bundle.

117
06:13.040 --> 06:16.510
But if I'm adding it now, all of a sudden, we've got all four of these bundled

118
06:16.510 --> 06:17.040
together

119
06:17.040 --> 06:20.980
and the switches can handle that again without us having to shut those port

120
06:20.980 --> 06:22.040
channels down.

121
06:22.040 --> 06:29.320
The main thing that I'll say is that when we add a interface into a bundle that

122
06:29.320 --> 06:30.640
the config
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
06:29.320 --> 06:30.640
the config

123
06:30.640 --> 06:38.210
should sync. But this should is a big problem at times. It doesn't always quite

124
06:38.210 --> 06:38.600
work out

125
06:38.600 --> 06:48.080
that way. So we might need to manually sync those configurations if needed.

126
06:48.080 --> 06:48.720
Once again,

127
06:48.720 --> 06:54.120
we're going to want to especially pay attention to the suspended state because

128
06:54.120 --> 06:55.000
if I add two

129
06:55.000 --> 06:59.760
additional ports to the bundle and I think that they should be online and run

130
06:59.760 --> 07:00.440
that show
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
06:59.760 --> 07:00.440
that show

131
07:00.440 --> 07:04.230
either channel summary command, if I'm seeing suspended, then I probably need

132
07:04.230 --> 07:04.880
to manually

133
07:04.880 --> 07:10.400
sync the configurations. So long story short, this configuration should

134
07:10.400 --> 07:11.560
synchronize. It

135
07:11.560 --> 07:15.710
doesn't always synchronize when maybe when we're not expecting it to and it

136
07:15.710 --> 07:16.400
does or vice

137
07:16.400 --> 07:20.020
versa. But either way, we can always manually sync it once they are

138
07:20.020 --> 07:21.280
synchronized between

139
07:21.280 --> 07:26.370
our port channel interface up here and the individual member interfaces, then

140
07:26.370 --> 07:26.960
ideally

141
07:26.960 --> 07:31.370
we're going to find that they enter the port channel state and our port channel
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
07:26.960 --> 07:31.370
we're going to find that they enter the port channel state and our port channel

142
07:31.370 --> 07:32.320
is operational.

143
07:32.320 --> 07:40.180
[BLANK_AUDIO]