diff --git a/NWT/4BHITN-DHCP-LAB-7.4.2.md b/NWT/4BHITN-DHCP-LAB-7.4.2.md index 7a3fc9a..07a14cc 100644 --- a/NWT/4BHITN-DHCP-LAB-7.4.2.md +++ b/NWT/4BHITN-DHCP-LAB-7.4.2.md @@ -71,15 +71,10 @@ though they were host names. ```Router(config)# no ip domain-lookup``` - Set the clock on the router to today’s time and date. ```R1# clock set HH:MM:SS MON DD YYYY``` ### Step 4: Configure Inter-VLAN Routing on R +- Activate interface G0/0/1 on the router. +- Configure sub-interfaces for each VLAN as required by the IP addressing table. All sub-interfaces use 802.1Q encapsulation and are assigned the first usable address from the IP address pool you have calculated. Ensure the sub-interface for the native VLAN does not have an IP address assigned. Include a description for each sub-interface. +- Verify the sub-interfaces are operational. -``` -a. Activate interface G0/0/1 on the router. -b. Configure sub-interfaces for each VLAN as required by the IP addressing table. All sub-interfaces use -802.1Q encapsulation and are assigned the first usable address from the IP address pool you have -calculated. Ensure the sub-interface for the native VLAN does not have an IP address assigned. Include -a description for each sub-interface. -c. Verify the sub-interfaces are operational. -``` ### Step 5: Configure G0/0/1 on R2, then G0/0/0 and static routing for both routers a. Configure G0/0/1 on R2 with the first IP address of Subnet C you calculated earlier. @@ -90,134 +85,88 @@ e. Save the running configuration to the startup configuration file. Close configuration window ### Step 6: Configure basic settings for each switch. - -Open configuration windowa.^ Assign a device name to the switch. - -``` -b. Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as -though they were host names. -c. Assign class as the privileged EXEC encrypted password. -d. Assign cisco as the console password and enable login. -``` - -``` -e. Assign cisco as the VTY password and enable login. -f. Encrypt the plaintext passwords. -g. Create a banner that warns anyone accessing the device that unauthorized access is prohibited. -h. Save the running configuration to the startup configuration file. -i. Set the clock on the switch to today’s time and date. +- Assign a device name to the switch. +- Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as though they were host names. +- Assign class as the privileged EXEC encrypted password. +- Assign cisco as the console password and enable login. +- Assign cisco as the VTY password and enable login. +- Encrypt the plaintext passwords. +- Create a banner that warns anyone accessing the device that unauthorized access is prohibited. +- Save the running configuration to the startup configuration file. +- Set the clock on the switch to today’s time and date. Note: Use the question mark (?) to help with the correct sequence of parameters needed to execute this command. -j. Copy the running configuration to the startup configuration. -``` -### Step 7: Create VLANs on S1. +- Copy the running configuration to the startup configuration. -Note: S2 is only configured with basic settings. -a. Create and name the required VLANs on switch 1 from the table above. -b. Configure and activate the management interface on S1 (VLAN 200) using the second IP address from -the subnet calculated earlier. Additionally, set the default gateway on S1. -c. Configure and activate the management interface on S2 (VLAN 1) using the second IP address from the -subnet calculated earlier. Additionally, set the default gateway on S -d. Assign all unused ports on S1 to the Parking_Lot VLAN, configure them for static access mode, and -administratively deactivate them. On S2, administratively deactivate all the unused ports. -Note: The interface range command is helpful to accomplish this task with as few commands as -necessary. -Close configuration windowOpen configuration window -Close configuration window + +### Step 7: Create VLANs on S1. +- Create and name the required VLANs on switch 1 from the table above. +- Configure and activate the management interface on S1 (VLAN 200) using the second IP address from the subnet calculated earlier. Additionally, set the default gateway on S1. +- Configure and activate the management interface on S2 (VLAN 1) using the second IP address from the subnet calculated earlier. Additionally, set the default gateway on S +- Assign all unused ports on S1 to the Parking_Lot VLAN, configure them for static access mode, and administratively deactivate them. On S2, administratively deactivate all the unused ports. + +#### Note: The interface range command is helpful to accomplish this task with as few commands as necessary. ### Step 8: Assign VLANs to the correct switch interfaces. -a. Assign used ports to the appropriate VLAN (specified in the VLAN table above) and configure them for +- Assign used ports to the appropriate VLAN (specified in the VLAN table above) and configure them for static access mode. -Open configuration window - -``` -b. Verify that the VLANs are assigned to the correct interfaces. +- Verify that the VLANs are assigned to the correct interfaces. Question: + Why is interface F0/5 listed under VLAN 1? -Type your answers here. -``` +#### F0/5 will be a trunk port, but trunking will be configured in the future. + ### Step 9: Manually configure S1’s interface F0/5 as an 802.1Q trunk. +- Change the switchport mode on the interface to force trunking. +- As a part of the trunk configuration, set the native VLAN to 1000. +- As another part of trunk configuration, specify that VLANs 100, 200, and 1000 are allowed to cross the trunk. +- Save the running configuration to the startup configuration file. +- Verify trunking status. -``` -a. Change the switchport mode on the interface to force trunking. -b. As a part of the trunk configuration, set the native VLAN to 1000. -c. As another part of trunk configuration, specify that VLANs 100, 200, and 1000 are allowed to cross the -trunk. -d. Save the running configuration to the startup configuration file. -e. Verify trunking status. Question: -At this point, what IP address would the PC’s have if they were connected to the network using DHCP? -``` -``` -Type your answers here. -``` -Close configuration window - +At this point, what IP address would the PC’s have if they were connected to the network using DHCP? ```Der PC bekommt eine APIPA Addresse: 169.254.0.0/16``` ## Part 2: Configure and verify two DHCPv4 Servers on R - -``` In Part 2, you will configure and verify a DHCPv4 Server on R1. The DHCPv4 server will service two subnets, Subnet A and Subnet C. -``` -### Step 1: Configure R1 with DHCPv4 pools for the two supported subnets. Only the DHCP Pool for +### Step 1: Configure R1 with DHCPv4 pools for the two supported subnets. Only the DHCP Pool for ### subnet A is given below -Open configuration windowa.^ Exclude the first five useable addresses from e ach address pool.^ - -``` -b. Create the DHCP pool (Use a unique name for each pool). -c. Specify the network that this DHCP server is supporting. -d. Configure the domain name as ccna-lab.com -e. Configure the appropriate default gateway for each DHCP pool. -f. Configure the lease time for 2 days 12 hours and 30 minutes. -g. Next, configure the second DHCPv4 Pool using the pool name R2_Client_LAN and the calculated -network, default-router and use the same domain name and lease time from the previous DHCP pool. -``` -### Step 2: Save your configuration - -Save the running configuration to the startup configuration file. -Close configuration window +- Exclude the first five useable addresses from e ach address pool. +- Create the DHCP pool (Use a unique name for each pool). +- Specify the network that this DHCP server is supporting. +- Configure the domain name as ccna-lab.com +- Configure the appropriate default gateway for each DHCP pool. +- Configure the lease time for 2 days 12 hours and 30 minutes. +- Next, configure the second DHCPv4 Pool using the pool name R2_Client_LAN and the calculated network, default-router and use the same domain name and lease time from the previous DHCP pool. ### Step 3: Verify the DHCPv4 Server configuration +- Issue the command show ip dhcp pool to examine the pool details. +- Issue the command show ip dhcp bindings to examine established DHCP address assignments. +- Issue the command show ip dhcp server statistics to examine DHCP messages. -``` -a. Issue the command show ip dhcp pool to examine the pool details. -b. Issue the command show ip dhcp bindings to examine established DHCP address assignments. -c. Issue the command show ip dhcp server statistics to examine DHCP messages. -``` ### Step 4: Attempt to acquire an IP address from DHCP on PC-A +- Open a command prompt on PC-A and issue the command ipconfig /renew. +- Once the renewal process is complete, issue the command ipconfig to view the new IP information. +- Test connectivity by pinging R1’s G0/0/1 interface IP address. -``` -a. Open a command prompt on PC-A and issue the command ipconfig /renew. -b. Once the renewal process is complete, issue the command ipconfig to view the new IP information. -c. Test connectivity by pinging R1’s G0/0/1 interface IP address. -``` ## Part 3: Configure and verify a DHCP Relay on R - -``` In Part 3, you will configure R2 to relay DHCP requests from the local area network on interface G0/0/1 to the DHCP server (R1). -``` + ### Step 1: Configure R2 as a DHCP relay agent for the LAN on G0/0/ +Open configuration window -Open configuration windowa.^ Configure the ip helper-address^ command on G0/0/1 specifying R1’s G0/0/0 IP address.^ - -b. Save your configuration. -Close configuration window +- Configure the ip helper-address command on G0/0/1 specifying R1’s G0/0/0 IP address. +- Save your configuration. ### Step 2: Attempt to acquire an IP address from DHCP on PC-B - -``` -a. Open a command prompt on PC-B and issue the command ipconfig /renew. -b. Once the renewal process is complete, issue the command ipconfig to view the new IP information. -c. Test connectivity by pinging R1’s G0/0/1 interface IP address. -d. Issue the show ip dhcp binding on R1 to verify DHCP bindings. -e. Issue the show ip dhcp server statistics on R1 and R2 to verify DHCP messages. -``` - -End of document +- Open a command prompt on PC-B and issue the command ipconfig /renew. +- Once the renewal process is complete, issue the command ipconfig to view the new IP information. +- Test connectivity by pinging R1’s G0/0/1 interface IP address. +- Issue the show ip dhcp binding on R1 to verify DHCP bindings. +- Issue the show ip dhcp server statistics on R1 and R2 to verify DHCP messages.