The Replace Guide To 300-101 exam question

Answer: Here is the solution below: 

Explanation: 

To troubleshoot the problem, first issue the show running-config on all of 4 routers. Pay more attention to the outputs of routers R2 and R3 The output of the "show running-config" command of R2: 

The output of the "show running-config" command of R3: 

We knew that all areas in an Open Shortest Path First (OSPF) autonomous system must be physically connected to the backbone area (Area 0). In some cases, where this is not possible, we can use a virtual link to connect to the backbone through a non-backbone area. The area through which you configure the virtual link is known as a transit area. In this case, the area 11 will become the transit area. Therefore, routers R2 and R3 must be configured with the area <area id> virtual-link <neighbor router-id>command. + Configure virtual link on R2 (from the first output above, we learned that the OSPF process ID of R2 is 1): 

R2>enable 

R2#configure terminal 

R2(config)#ipv6 router ospf 1 

R2(config-rtr)#area 11 virtual-link 3.3.3.3 

Save the configuration: 

R2(config-rtr)#end 

R2#copy running-config startup-config 

(Notice that we have to use neighbor router-id 3.3.3.3, not R2's router-id 2.2.2.2) + Configure virtual link on R3 (from the second output above, we learned that the OSPF process ID of R3 is 1 and we have to disable the wrong configuration of "area 54 virtual-link 4.4.4.4"): 

R3>enable 

R3#configure terminal 

R3(config)#ipv6 router ospf 1 

R3(config-rtr)#no area 54 virtual-link 4.4.4.4 

R3(config-rtr)#area 11 virtual-link 2.2.2.2 

Save the configuration: 

R3(config-rtr)#end 

R3#copy running-config startup-config 

You should check the configuration of R4, too. Make sure to remove the incorrect configuration statements to get the full points. 

R4(config)#ipv6 router ospf 1 

R4(config-router)#no area 54 virtual-link 3.3.3.3 

R4(config-router)#end 

After finishing the configuration doesn’t forget to ping between R1 and R4 to make sure they work. 

Note. If you want to check the routing information, use the show ipv6 route command, not "show ip route". 

Answer: C 

Explanation: 

The 0.0.0.0/0 route is the default route and is listed as the first CEF entry. Here we see the next hop for this default route lists 192.168.201.1 as the default router (gateway of last resort).

Answer: A 

Explanation: 

Answer: B 

Explanation: 

Answer: D 

Explanation: 

Answer: A 

Explanation: 

The following security models exist: SNMPv1, SNMPv2, SNMPv3. The following security

levels exits: "noAuthNoPriv" (no authentiation and no encryption noauth keyword in CLI),

"AuthNoPriv" (messages are authenticated but not encrypted auth keyword in CLI), "AuthPriv" (messages

are authenticated and encrypted priv keyword in CLI). SNMPv1 and SNMPv2 models only support the

"noAuthNoPriv" model since they use plain community string to match the incoming packets. The SNMPv3

implementations could be configured to use either of the models on per-group basis (in case if

"noAuthNoPriv" is configured, username serves as a replacement for community string). Reference: http://

blog.ine.com/2008/07/19/snmpv3-tutorial/

Answer: A,B,C 

Explanation: 

show crypto ipsec sa This command shows IPsec SAs built between peers. The encrypted

tunnel is built between 12.1.1.1 and 12.1.1.2 for traffic that goes between networks 20.1.1.0 and 10.1.1.0.

You can see the two Encapsulating Security Payload (ESP) SAs built inbound and outbound.

Authentication Header (AH) is not used since there are

no AH SAs.

This output shows an example of the show crypto ipsec sa command (bolded ones found in answers for

this question).

interface: FastEthernet0

Crypto map tag: test, local addr. 12.1.1.1

local ident (addr/mask/prot/port): (20.1.1.0/255.255.255.0/0/0) remote ident (addr/mask/prot/port):

(10.1.1.0/255.255.255.0/0/0) current_peer: 12.1.1.2

PERMIT, flags={origin_is_acl,}

#pkts encaps: 7767918, #pkts encrypt: 7767918, #pkts digest 7767918 #pkts decaps: 7760382, #pkts

decrypt: 7760382, #pkts verify 7760382 #pkts compressed:

0, #pkts decompressed: 0

#pkts not compressed: 0, #pkts compr. failed: 0,

#pkts decompress failed: 0, #send errors 1, #recv errors 0 local crypto endpt.: 12.1.1.1, remote crypto

endpt.: 12.1.1.2 path mtu 1500, media mtu 1500

current outbound spi: 3D3

inbound esp sas:

spi: 0x136A010F(325714191)

transform: esp-3des esp-md5-hmac ,

in use settings ={Tunnel, }

slot: 0, conn id: 3442, flow_id: 1443, crypto map: test sa timing: remaining key lifetime (k/sec):

(4608000/52) IV size: 8 bytes

replay detection support: Y

inbound ah sas:

inbound pcp sas:

inbound pcp sas:

outbound esp sas:

spi: 0x3D3(979)

transform: esp-3des esp-md5-hmac ,

in use settings ={Tunnel, }

slot: 0, conn id: 3443, flow_id: 1444, crypto map: test sa timing: remaining key lifetime (k/sec):

(4608000/52) IV size: 8 bytes

replay detection support: Y

outbound ah sas:

outbound pcp sas:

Reference: http://www.cisco.com/c/en/us/support/docs/security-vpn/ipsec-negotiation-ike- protocols/5409-

ipsec-debug-00.html

Answer: A 

Explanation: 

Answer: A 

Explanation: 

To enable the exporting of information in NetFlow cache entries, use the ip flow-export destination

command in global configuration mode.

Syntax Description

ip- IP address of the workstation to which you want to send the address NetFlow information.

udp-port UDP protocol-specific port number.

Reference:

http://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/12s_mdnf.html#wp1023091

Answer: A,B,C 

Explanation: 

A trunk interface can carry traffic for multiple EVNs. To simplify the configuration process, all

the subinterfaces and associated EVNs have the same IP address assigned. In other words, the trunk

interface is identified by the same IP address in different EVN contexts. This is accomplished as a result of

each EVN having a unique routing and forwarding table, thereby enabling support for overlapping IP

addresses across multiple EVNs. Reference: http://www.cisco.com/en/US/docs/ios-xml/ios/evn/

configuration/xe-3sg/evn- overview.pdf