Answer: A 

Explanation: 

Answer: A 

Explanation: 

To configure the autonomous-system number for an Enhanced Interior Gateway Routing

Protocol (EIGRP) routing process to run within a VPN routing and forwarding (VRF) instance, use the

autonomous-system command in address-family configuration mode. To remove the autonomous-system

for an EIGRP routing process from within a VPN VRF instance, use the no form of this command.

autonomous-system autonomous-system-number no autonomous-system autonomous-system-number

Reference: http://www.cisco.com/c/en/us/td/docs/ios/iproute_eigrp/command/reference/ire_book/

ire_a1.htm l#wp1062796

Answer: A 

Explanation: 

Explanation: Extended Unique Identifier (EUI), as per RFC2373, allows a host to assign iteslf a unique 64-

Bit IP Version 6 interface identifier (EUI-64). This feature is a key benefit over IPv4 as it eliminates the

need of manual configuration or DHCP as in the world of IPv4. The IPv6 EUI-64 format address is obtained

through the 48-bit MAC address. The Mac address is first separated into two 24-bits, with one being OUI

(Organizationally Unique Identifier) and the other being NIC specific. The 16-bit 0xFFFE is then inserted

between these two 24-bits to for the 64-bit EUI address. IEEE has chosen FFFE as a reserved value which

can only appear in EUI-64 generated from the EUI-48 MAC address. Here is an example showing how the

Mac Address is used to generate EUI.

Next, the seventh bit from the left, or the universal/local (U/L) bit, needs to be inverted. This bit identifies

whether this interface identifier is universally or locally administered. If 0, the address is locally

administered and if 1, the address is globally unique. It is worth noticing that in the OUI portion, the globally

unique addresses assigned by the IEEE has always been set to 0 whereas the locally created addresses

has 1 configured. Therefore, when the bit is inverted, it maintains its original scope (global unique address

is still global unique and vice versa). The reason for inverting can be found in RFC4291 section 2.5.1.

Reference: https:// supportforums.cisco.com/document/100566/understanding-ipv6-eui-64-bit- address

Answer: Here are the solution as below: 

Explanation: 

First we have to figure out why R3 and R4 can not communicate with each other. Use the show running-config command on router R3. 

Notice that R3 is configured as a stub receive-only router. The receive-only keyword will restrict the router from sharing any of its routes with any other router in that EIGRP autonomous system. This keyword will also prevent any type of route from being sent. Therefore we will remove this command and replace it with the eigrp stub command: 

R3# configure terminal 

R3(config)# router eigrp 123 

R3(config-router)# no eigrp stub receive-only 

R3(config-router)# eigrp stub 

R3(config-router)# end 

Now R3 will send updates containing its connected and summary routes to other routers. Notice that the eigrp stub command equals to the eigrp stub connected summary because the connected and summary options are enabled by default. Next we will configure router R3 so that it has only 2 subnets of 10.0.0.0 network. Use the show ip route command on R3 to view its routing table: 

Because we want the routing table of R3 only have 2 subnets so we have to summary sub-networks at the interface which is connected with R3, the s0/0 interface of R4. 

There is one interesting thing about the output of the show ip route shown above: the 10.2.3.0/24, which is a directly connected network of R3. We can’t get rid of it in the routing table no matter what technique we use to summary the networks. Therefore, to make the routing table of R3 has only 2 subnets we have to summary other subnets into one subnet. 

In the output if we don’t see the summary line (like 10.0.0.0/8 is a summary…) then we should use the command ip summary-address eigrp 123 10.2.0.0 255.255.0.0 so that all the ping can work well. 

In conclusion, we will use the ip summary-address eigrp 123 10.2.0.0 255.255.0.0 at the interface s0/0 of R4 to summary. 

R4> enable 

R4# conf t 

R4(config)# interface s0/0 

R4(config-if)# ip summary-address eigrp 123 10.2.0.0 255.255.0.0 

Now we jump back to R3 and use the show ip route command to verify the effect, the output is shown below: 

Note: Please notice that the IP addresses and the subnet masks in your real exam might be different so you might use different ones to solve this question. Just for your information, notice that if you use another network than 10.0.0.0/8 to summary, for example, if you use the command ip summary-address eigrp 123 10.2.0.0 255.255.0.0 you will leave a /16 network in the output of the show ip route command. 

But in your real exam, if you don’t see the line "10.0.0.0/8 is a summary, Null0" then you can summarize using the network 10.2.0.0/16. This summarization is better because all the pings can work well. Finally don’t forget to use the copy run start command on routers R3 and R4 to save the configurations. R3(config-if)# end R3# copy run start R4(config-if)# end R4# copy run start 

If the “copy run start” command doesn’t work then use “write memory.” 

Answer: D 

Explanation: 

show ipv6 traffic Field Descriptions

Field Description

source- Number of source-routed packets.

routed

truncated Number of truncated packets.

format Errors that can result from checks performed on header fields, errors the version number, and

packet length.

not a Message sent when IPv6 unicast routing is not enabled.

router

Reference:

http://www.cisco.com/c/en/us/td/docs/ios/ipv6/command/reference/ipv6_book/ipv6_16.html

Answer: C 

Explanation: 

Answer: A 

Explanation: 

Answer: A,B 

Explanation: 

Answer: E 

Explanation: 

NPTv6 provides a mechanism to translate the private internal organization prefixes to public globally

reachable addresses. The translation mechanism is stateless and provides a 1:1 relationship between the internal addresses and external addresses. The use cases for NPTv6 outlined in the RFC include peering with partner networks, multi homing, and redundancy and load sharing.

Reference:

http://www.cisco.com/c/dam/en/us/td/docs/solutions/SBA/August2012/Cisco_SBA_BN_IPv6AddressingGuide-Aug2012.pdf

Answer: A 

Explanation: