WEBVTT 00:00:00.000 --> 00:00:04.000 align:middle line:84% In the previous video in this topology 00:00:04.000 --> 00:00:06.000 align:middle line:84% the switches were configured with host names 00:00:06.000 --> 00:00:09.000 align:middle line:84% and unused interfaces were shutdown. 00:00:09.000 --> 00:00:13.000 align:middle line:84% So as an example, switch 4 was given a name of S4 00:00:13.000 --> 00:00:16.000 align:middle line:84% and any unused interfaces were shut down on the switch. 00:00:16.000 --> 00:00:20.000 align:middle line:84% The VTP mode was set to transparent and VLAN 10 and 20 00:00:20.000 --> 00:00:23.000 align:middle line:84% were created on the 4 switches in this topology. 00:00:23.000 --> 00:00:28.000 align:middle line:84% Router 1 and router 2, acting as PCs in the topology 00:00:28.000 --> 00:00:32.000 align:middle line:84% were configured with IP addresses on their FastEthernet interfaces. 00:00:32.000 --> 00:00:35.000 align:middle line:84% Router 3 was also configured with an IP address 00:00:35.000 --> 00:00:39.000 align:middle line:84% in FastEthernet 0/0 as well as on FastEthernet 0/1. 00:00:39.000 --> 00:00:42.000 align:middle line:84% The switches will also configure with IP addresses. 00:00:42.000 --> 00:00:44.000 align:middle line:84% So the access layer switches were configured 00:00:44.000 --> 00:00:47.000 align:middle line:84% with IP addresses in the management VLAN. 00:00:47.000 --> 00:00:51.000 align:middle line:84% Which in this example is gonna be VLAN 1 the default. 00:00:51.000 --> 00:00:54.000 align:middle line:84% The core switches were configured with 3 IP addresses. 00:00:54.000 --> 00:00:59.000 align:middle line:84% 1 in VLAN 1, 1 in VLAN 10 and 1 in VLAN 20. 00:00:59.000 --> 00:01:04.000 align:middle line:84% In this video, the interfaces on the switches will be configured as either trunks 00:01:04.000 --> 00:01:07.000 align:middle line:84% so these ports will be configured as trunks or access ports 00:01:07.000 --> 00:01:13.000 align:middle line:84% So on the access switches, gigabit 0/2 on both switch 3 and switch 4 00:01:13.000 --> 00:01:16.000 align:middle line:84% will be configured as an access port in the relevant VLAN 00:01:16.000 --> 00:01:21.000 align:middle line:84% Once we’ve got this configured properly, the routers acting as PCs 00:01:21.000 --> 00:01:25.000 align:middle line:84% should be able to ping the core switch IP addresses in the same VLAN. 00:01:25.000 --> 00:01:28.000 align:middle line:84% So switch 1 core switch. 00:01:28.000 --> 00:01:31.000 align:middle line:84% This interfaces gonna be configured as trunk ports. 00:01:31.000 --> 00:01:36.000 align:middle line:84% This interface will be configured as an access port in VLAN 1 00:01:36.000 --> 00:01:39.000 align:middle line:84% which is connected to Solarwinds network performance monitor. 00:01:39.000 --> 00:01:44.000 align:middle line:84% In a later video, I’ll show you how to integrate NPM with this topology 00:01:44.000 --> 00:01:49.000 align:middle line:84% using SNMP so that we can manage these switches and the routers using SNMP. 00:01:49.000 --> 00:01:55.000 align:middle line:84% So switch 1, first thing to check is which VLANs are configured on the switch. 00:01:55.000 --> 00:01:59.000 align:middle line:84% So I configured the commands sh vlan or sh vlan brief 00:01:59.000 --> 00:02:03.000 align:middle line:84% sh vlan brief shows me that vlan 1 is configured. 00:02:03.000 --> 00:02:08.000 align:middle line:84% And all these interfaces belong to VLAN 1, VLAN 10 and VLAN 20 have been configured 00:02:08.000 --> 00:02:13.000 align:middle line:84% but no interfaces have been put into VLAN 10 or VLAN 20. 00:02:13.000 --> 00:02:19.000 align:middle line:84% I could also do a command such as sh int gigabit 0/0 switchport 00:02:19.000 --> 00:02:22.000 align:middle line:84% So here’s the command 00:02:22.000 --> 00:02:27.000 align:middle line:84% and its shows me that this interface g0/0 is enabled as a switchport. 00:02:27.000 --> 00:02:33.000 align:middle line:84% In other words, it’s a layer 2 interface not a layer 3 interface. 00:02:33.000 --> 00:02:37.000 align:middle line:84% So it’s acting as a layer 2 switch interface rather than as a routed interface. 00:02:37.000 --> 00:02:42.000 align:middle line:84% This switch is going to be negotiating the encapsulation 00:02:42.000 --> 00:02:45.000 align:middle line:84% as well as the negotiation of trunking. 00:02:45.000 --> 00:02:49.000 align:middle line:84% In other words, it’s using dynamic trunking protocol or DTP. 00:02:49.000 --> 00:02:53.000 align:middle line:84% Now rather than using that were going to statically configure the trunk port 00:02:53.000 --> 00:02:57.000 align:middle line:84% and access ports rather than relying on DTP. 00:02:57.000 --> 00:03:00.000 align:middle line:84% It’s recommended that you disable DTP. 00:03:00.000 --> 00:03:02.000 align:middle line:84% The access mode VLAN is 1. 00:03:02.000 --> 00:03:06.000 align:middle line:84% In other words, if this port negotiates to be an access port 00:03:06.000 --> 00:03:10.000 align:middle line:84% it’s gonna be in VLAN 1 and the native or untagged VLAN 00:03:10.000 --> 00:03:14.000 align:middle line:84% on the trunk port when it's a trunk port will be in VLAN 1. 00:03:14.000 --> 00:03:21.000 align:middle line:84% We can see other information here including the VLANs allowed across the trunk. 00:03:21.000 --> 00:03:23.000 align:middle line:84% All VLANs are allowed by default. 00:03:23.000 --> 00:03:28.000 align:middle line:84% Pruning is enabled for VLANs 2 to 1001 00:03:28.000 --> 00:03:33.000 align:middle line:84% so conf t rather than configuring each interface individually 00:03:33.000 --> 00:03:38.000 align:middle line:84% I’m gonna configure a range of interfaces. 00:03:38.000 --> 00:03:47.000 align:middle line:84% So interface range gigabit is 0/0 to gigabit 0/0 - 3 00:03:47.000 --> 00:03:51.000 align:middle line:84% so I’m gonna configure this interface 00:03:51.000 --> 00:03:55.000 align:middle line:84% this interface, this interface, and this interface to the range command. 00:03:55.000 --> 00:04:01.000 align:middle line:84% Notice what happens when I trying change the mode to trunk. 00:04:01.000 --> 00:04:05.000 align:middle line:84% I’m told that the command is rejected 00:04:05.000 --> 00:04:08.000 align:middle line:84% an interface whose trunking capsulation is set to auto 00:04:08.000 --> 00:04:14.000 align:middle line:84% cannot be configured to trunk mode so the command failed on gigabit 0/0. 00:04:14.000 --> 00:04:17.000 align:middle line:84% On some Cisco switches including this one 00:04:17.000 --> 00:04:21.000 align:middle line:84% you need to specify the trunk encapsulation 00:04:21.000 --> 00:04:23.000 align:middle line:84% before you change the mode to trunk. 00:04:23.000 --> 00:04:29.000 align:middle line:84% this switch supports 802.1Q and ISL 00:04:29.000 --> 00:04:32.000 align:middle line:84% and can negotiate encapsulation with the neighbor 00:04:32.000 --> 00:04:36.000 align:middle line:84% so I want to explicitly set the encapsulation to dot1q 00:04:36.000 --> 00:04:44.000 align:middle line:84% and now I’ll be able to type switchport mode trunk and then I can type end. 00:04:44.000 --> 00:04:48.000 align:middle line:84% So let’s look at how the interface is changed. 00:04:48.000 --> 00:04:53.000 align:middle line:84% Before I do that notice interface VLAN 10 and interface VLAN 20 have come up. 00:04:53.000 --> 00:04:56.000 align:middle line:84% These are SVIs on the switch. 00:04:56.000 --> 00:04:59.000 align:middle line:84% So sh int g0/0 switchport 00:04:59.000 --> 00:05:02.000 align:middle line:84% You can see that the administrative mode is trunk 00:05:02.000 --> 00:05:05.000 align:middle line:84% and the current operational mode is trunk. 00:05:05.000 --> 00:05:10.000 align:middle line:84% I have manually or statically set this interface to trunk. 00:05:10.000 --> 00:05:15.000 align:middle line:84% Previously the administrative mode was dynamic auto 00:05:15.000 --> 00:05:20.000 align:middle line:84% the interface was using dynamic trunk protocol or DTP 00:05:20.000 --> 00:05:24.000 align:middle line:84% to negotiate with neighboring switches to set up trunking. 00:05:24.000 --> 00:05:29.000 align:middle line:84% But now we’ve configured it to manually trunk.