SIMULATION

Scenario:
Click on the PE7 router icon to access the PE7 router’s CLI.
You only have access to the PE7 router CLI
The PE8 router has been preconfigured. You only need to configure the PE7 router.
PE7 and PE8 are directly connected and IPv4 and IPv6 static routes have been configured for the loopback addresses.
The management interface (MgmtEth0/RSP0/CPUO/0) IPv4 address has been preconfigured and there is no need to enable routing on the management interface.

Your task is to configure the PE7 router per the following requirements:
1.Configure IPv4 and IPv6 addresses and enable the loopbackO and gi0/0/0/1 interfaces. Refer to the topology diagram for the IP addresses to use.
2.Configure iBGP using AS 65001 for both IPv4 and IPv6 routing. Establish an iBGP peering relationship between loopbackO interfaces.
3.Create two BGP peering sessions, one for IPv4 and one for IPv6.
4.After successfully completing all the above configurations, you should be able to successfully establish in iBGP peer relationship with PE8. If you successfully complete the required BGP configurations on PE7, from PE7, you should see the 10.100.100.100/32 IPv4 BGP route and the 2001:db8:10:100:100::100/128 IPv6 BGP route advertised byPE8.
Note:The ping command is not supported in this simulation. Please use the proper show commands to verify the BGP peerings and the BGP routes on the PE7 router.

Topology


PE7
% Some configuration options may have changed %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/1, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/2, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/3, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/4, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/5, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/6, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/7, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/8, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/9, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/10, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/11, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/12, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/13, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/14, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/15, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/16, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/17, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/18, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/19, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/20, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/21, changed state to administratively down %LINK-3-UPD0WN: Interface GigabitEthernet0/0/0/22, changed state to administratively down .....

A.	conf t int loopback 0 no shut ipv4 address 10.7.1.1 255.255.255.255 ipv6 address 2001:db8:10:7:1::1/128 int Gi0/0/0/1 no shut ipv4 address 192.168.178.70 255.255.255.0 ipv6 address 2001:DB8:192:168:178::70/64 commit router bgp 65001 address-family ipv4 unicast redistribute connected neighbor 10.8.1.1 remote-as 65001 update-source loopback 0 commit exit address family ipv6 unicast redistribute connected neighbor 2001:db8:10:8:1::1 remote-as 65001 update-source loopback 0 commit
B.	.