SIMULATION
Physical connectivity is implemented between the two Layer 2 switches,
and the network connectivity between them must be configured.
I . Configure an LACP EtherChanneI and number it as 44; configure it
between switches SWI and SW2 using interfaces EthernetO/O and
Ethernet0/1 on both sides. The LACP mode must match on both ends.
2. Configure the EtherChanneI as a trunk link.
3. Configure the trunk link with 802. Iq tags.
4. Configure VLAN 'MONITORING' as the untagged VLAN of the
EtherChannel.
==================
Guidelines
This is a lab item in which tasks will be performed on virtual devices.
* Refer to the Tasks tab to view the tasks for this lab item.
* Refer to the Topology tab to access the device console(s) and perform the tasks.
* Console access is available for all required devices by clicking the device icon or using
the tab(s) above the console window.
* All necessary preconfigurations have been applied.
* Do not change the enable password or hostname for any device.
* Save your configurations to NVRAM before moving to the next item.
* Click Next at the bottom of the screen to submit this lab and move to the next question.
* When Next is clicked, the lab closes and cannot be reopened.
To configure an LACP EtherChannel and number it as 44, configure it between switches SW1 and SW2 using interfaces Ethernet0/0 and Ethernet0/1 on both sides, configure the EtherChannel as a trunk link, configure the trunk link with 802.1q tags, and configure VLAN 'MONITORING' as the untagged VLAN of the EtherChannel, you need to follow these steps:
On both SW1 and SW2, enter the global configuration mode by using the configure terminal command.
On both SW1 and SW2, select the two interfaces that will form the EtherChannel by using the interface range ethernet 0/0 - 1 command. This will enter the interface range configuration mode.
On both SW1 and SW2, set the protocol to LACP by using the channel-protocol lacp command.
On both SW1 and SW2, assign the interfaces to an EtherChannel group number 44 by using the channel-group 44 mode active command. This will create a logical interface named Port-channel44 and set the LACP mode to active on both ends. The LACP mode must match on both ends for the EtherChannel to form.
On both SW1 and SW2, exit the interface range configuration mode by using the exit command.
On both SW1 and SW2, enter the Port-channel interface configuration mode by using the interface port-channel 44 command.
On both SW1 and SW2, configure the Port-channel interface as a trunk link by using the switchport mode trunk command.
On both SW1 and SW2, configure the Port-channel interface to use 802.1q tags for VLAN identification by using the switchport trunk encapsulation dot1q command.
On both SW1 and SW2, configure VLAN 'MONITORING' as the untagged VLAN of the Port-channel interface by using the switchport trunk native vlan MONITORING command.
On both SW1 and SW2, exit the Port-channel interface configuration mode by using the exit command.
On both SW1 and SW2, save the configuration to NVRAM by using the copy running-config startup-config command.
Refer to the exhibit.
Connectivity between three routers has been established, and IP services must be configured jn the order presented to complete the implementation Tasks assigned include configuration of NAT, NTP, DHCP, and SSH services.
1. All traffic sent from R3 to the R1 Loopback address must be configured for NAT on R2. All source addresses must be translated from R3 to the IP address of Ethernet0/0 on R2, while using only a standard access list named NAT To verify, a ping must be successful to the R1 Loopback address sourced from R3. Do not use NVI NAT configuration.
2. Configure R1 as an NTP server and R2 as a client, not as a peer, using the IP address of the R1 Ethernet0/2 interface. Set the clock on the NTP server for midnight on January 1, 2019.
3. Configure R1 as a DHCP server for the network 10.1.3.0/24 in a pool named TEST. Using a single command, exclude addresses 1-10 from the range. Interface Ethernet0/2 on R3 must be issued the IP address of 10.1.3.11 via DHCP.
4. Configure SSH connectivity from R1 to R3, while excluding access via other remote connection protocols. Access for user root and password Cisco must be set on router R3 using RSA and 1024 bits. Verify connectivity using an SSH session from router R1 using a destination address of 10.1.3.11. Do NOT modify console access or line numbers to accomplish this task.
Answer as below configuration:
conf t
R1(config)#ntp master 1
R2(config)#ntp server 10.1.2.1
Exit
Router#clock set 00:00:00 jan 1 2019
ip dhcp pool TEST
network 10.1.3.0 255.255.255.0
ip dhcp exluded-address 10.1.3.1 10.1.3.10
R3(config)#int e0/3
R3(config)#int e0/2
ip address dhcp
no shut
crypto key generate RSA
1024
Copy run start
All physical cabling is in place. A company plans to deploy 32 new sites.
The sites will utilize both IPv4 and IPv6 networks.
1 . Subnet 172.25.0.0/16 to meet the subnet requirements and maximize
the number of hosts
Using the second subnet
* Assign the first usable IP address to e0/0 on Sw1O1
* Assign the last usable IP address to e0/0 on Sw102
2. Subnet to meet the subnet requirements and maximize
the number of hosts
c Using the second subnet
* Assign an IPv6 GUA using a unique 64-Bit interface identifier
on e0/0 on Sw101
* Assign an IPv6 GUA using a unique 64-Bit interface identifier
on eO/O on swi02
Guidelines
This is a lab item in which tasks will be performed on virtual devices.
* Refer to the Tasks tab to view the tasks for this lab item.
* Refer to the Topology tab to access the device console(s) and perform the tasks.
* Console access is available for all required devices by clicking the device icon or using
the tab(s) above the console window.
* All necessary preconfigurations have been applied.
* Do not change the enable password or hostname for any device.
* Save your configurations to NVRAM before moving to the next item.
* Click Next at the bottom of the screen to submit this lab and move to the next question.
* When Next is clicked, the lab closes and cannot be reopened.
To subnet 172.25.0.0/16 to meet the subnet requirements and maximize the number of hosts, you need to determine how many bits you need to borrow from the host portion of the address to create enough subnets for 32 sites. Since 32 is 2^5, you need to borrow 5 bits, which means your new subnet mask will be /21 or 255.255.248.0. To find the second subnet, you need to add the value of the fifth bit (32) to the third octet of the network address (0), which gives you 172.25.32.0/21 as the second subnet. The first usable IP address in this subnet is 172.25.32.1, and the last usable IP address is 172.25.39.254.
To assign the first usable IP address to e0/0 on Sw101, you need to enter the following commands on the device console:
Sw101#configure terminal Sw101(config)#interface e0/0 Sw101(config-if)#ip address 172.25.32.1 255.255.248.0 Sw101(config-if)#no shutdown Sw101(config-if)#end
To assign the last usable IP address to e0/0 on Sw102, you need to enter the following commands on the device console:
Sw102#configure terminal Sw102(config)#interface e0/0 Sw102(config-if)#ip address 172.25.39.254 255.255.248.0 Sw102(config-if)#no shutdown Sw102(config-if)#end
To subnet an IPv6 GUA to meet the subnet requirements and maximize the number of hosts, you need to determine how many bits you need to borrow from the interface identifier portion of the address to create enough subnets for 32 sites. Since 32 is 2^5, you need to borrow 5 bits, which means your new prefix length will be /69 or ffff:ffff:ffff:fff8::/69 (assuming that your IPv6 GUA has a /64 prefix by default). To find the second subnet, you need to add the value of the fifth bit (32) to the fourth hextet of the network address (0000), which gives you xxxx:xxxx:xxxx:0020::/69 as the second subnet (where xxxx:xxxx:xxxx is your IPv6 GUA prefix). The first and last IPv6 addresses in this subnet are xxxx:xxxx:xxxx:0020::1 and xxxx:xxxx:xxxx:0027:ffff:ffff:ffff:fffe respectively.
To assign an IPv6 GUA using a unique 64-bit interface identifier on e0/0 on Sw101, you need to enter the following commands on the device console (assuming that your IPv6 GUA prefix is 2001:db8::/64):
Sw101#configure terminal Sw101(config)#interface e0/0 Sw101(config-if)#ipv6 address 2001:db8::20::1/69 Sw101(config-if)#no shutdown Sw101(config-if)#end
To assign an IPv6 GUA using a unique 64-bit interface identifier on e0/0 on Sw102, you need to enter the following commands on the device console (assuming that your IPv6 GUA prefix is 2001:db8::/64):
Sw102#configure terminal Sw102(config)#interface e0/0 Sw102(config-if)#ipv6 address 2001:db8::27::fffe/69 Sw102(config-if)#no shutdown Sw102(config-if)#end
Refer to the exhibit.
Connectivity between three routers has been established, and IP services must be configured jn the order presented to complete the implementation Tasks assigned include configuration of NAT, NTP, DHCP, and SSH services.
1. All traffic sent from R3 to the R1 Loopback address must be configured for NAT on R2. All source addresses must be translated from R3 to the IP address of Ethernet0/0 on R2, while using only a standard access list named NAT To verify, a ping must be successful to the R1 Loopback address sourced from R3. Do not use NVI NAT configuration.
2. Configure R1 as an NTP server and R2 as a client, not as a peer, using the IP address of the R1 Ethernet0/2 interface. Set the clock on the NTP server for midnight on January 1, 2019.
3. Configure R1 as a DHCP server for the network 10.1.3.0/24 in a pool named TEST. Using a single command, exclude addresses 1-10 from the range. Interface Ethernet0/2 on R3 must be issued the IP address of 10.1.3.11 via DHCP.
4. Configure SSH connectivity from R1 to R3, while excluding access via other remote connection protocols. Access for user root and password Cisco must be set on router R3 using RSA and 1024 bits. Verify connectivity using an SSH session from router R1 using a destination address of 10.1.3.11. Do NOT modify console access or line numbers to accomplish this task.
Answer as below configuration:
conf t
R1(config)#ntp master 1
R2(config)#ntp server 10.1.2.1
Exit
Router#clock set 00:00:00 jan 1 2019
ip dhcp pool TEST
network 10.1.3.0 255.255.255.0
ip dhcp exluded-address 10.1.3.1 10.1.3.10
R3(config)#int e0/3
R3(config)#int e0/2
ip address dhcp
no shut
crypto key generate RSA
1024
Copy run start
Refer to the exhibit.
What is missing from this output for it to be executed?
Carman
19 days agoAimee
23 days agoRicarda
26 days agoEleanor
2 months agoHenry
2 months agoNoah
2 months agoIsabella
2 months agoAdam
2 months agoJames Amiri
4 months ago