Step 3: Configure basic settings for each router
This commit is contained in:
parent
49ba704b60
commit
f993c063c3
|
|
@ -26,4 +26,198 @@
|
|||
| 100 | Clients | S1: F0/6 |
|
||||
| 200 | Management | S1: VLAN 200 |
|
||||
| 999 | Parking_Lot | S1: F0/1-4, F0/7-24, G0/1-2 |
|
||||
| 1000 | Native | N/A |
|
||||
| 1000 | Native | N/A |
|
||||
|
||||
## Objectives
|
||||
- Part 1: Build the Network and Configure Basic Device Settings
|
||||
- Part 2: Configure and verify two DHCPv4 Servers on R
|
||||
- Part 3: Configure and verify a DHCP Relay on R
|
||||
|
||||
## Part 1: Build the Network and Configure Basic Device Settings
|
||||
### Step 1: Establish an addressing scheme
|
||||
Subnet the network 192.168.1.0/24 to meet the following requirements:
|
||||
|
||||
- One subnet, “Subnet A”, supporting 58 hosts (the client VLAN at R1). Record the first IP address in the Addressing Table for R1 G0/0/1.100.
|
||||
|
||||
- One subnet, “Subnet B”, supporting 28 hosts (the management VLAN at R1). Record the first IP address in the Addressing Table for R1 G0/0/1.200. Record the second IP address in the Address Table for S1 VLAN 200 and enter the associated default gateway.
|
||||
|
||||
- One subnet, “Subnet C”, supporting 12 hosts (the client network at R2). Record the first IP address in the Addressing Table for R2 G0/0/1. Record the second IP address in the
|
||||
Address Table for S2 VLAN 1 and enter the associated default gateway.
|
||||
|
||||
### Step 2: Cable the network as shown in the topology.
|
||||
|
||||
### Step 3: Configure basic settings for each router.
|
||||
Open configuration window. Assign a device name to the router.
|
||||
|
||||
- Assign a device name to the router. ```Router(config)# hostname <hostname>```
|
||||
- Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as
|
||||
though they were host names. ```Router(config)# no ip domain-lookup```
|
||||
- Assign class as the privileged EXEC encrypted password.```R1(config): enable secret class```
|
||||
- Assign cisco as the console password and enable login.
|
||||
```
|
||||
R1(config)# line con 0
|
||||
R1(config-line)# password cisco
|
||||
R1(config-line)# login
|
||||
```
|
||||
- Assign cisco as the VTY password and enable login.
|
||||
```
|
||||
R1(config)# line vty 0 1114
|
||||
R1(config-line)# password cisco
|
||||
R1(config-line)# login
|
||||
```
|
||||
- Encrypt the plaintext passwords. ```R1(config)# service password-encryption```
|
||||
- Create a banner that warns anyone accessing the device that unauthorized access is prohibited. ```R1(config)# banner motd # Authorized Access only #```
|
||||
- Save the running configuration to the startup configuration file. ```R1# write memory```
|
||||
- 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
|
||||
|
||||
```
|
||||
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.
|
||||
b. Configure interface G0/0/0 for each router based on the IP Addressing table above.
|
||||
c. Configure a default route on each router pointed to the IP address of G0/0/0 on the other router.
|
||||
d. Verify static routing is working by pinging R2’s G0/0/1 address from R1.
|
||||
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.
|
||||
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.
|
||||
|
||||
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 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
|
||||
static access mode.
|
||||
Open configuration window
|
||||
|
||||
```
|
||||
b. Verify that the VLANs are assigned to the correct interfaces.
|
||||
Question:
|
||||
Why is interface F0/5 listed under VLAN 1?
|
||||
Type your answers here.
|
||||
```
|
||||
### Step 9: Manually configure S1’s interface F0/5 as an 802.1Q trunk.
|
||||
|
||||
```
|
||||
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
|
||||
|
||||
|
||||
## 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
|
||||
|
||||
### 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
|
||||
|
||||
### Step 3: Verify the DHCPv4 Server configuration
|
||||
|
||||
```
|
||||
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
|
||||
|
||||
```
|
||||
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 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
|
||||
|
||||
### 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
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user