Answer: C 

Explanation: 

Restrictions for Embedded Packet Capture 

. In Cisco IOS Release 12.2(33)SRE, EPC is supported only on 7200 platform. 

. EPC only captures multicast packets on ingress and does not capture the replicated packets on egress. 

. Currently, the capture file can only be exported off the device; for example, TFTP or FTP servers and local disk. 

Reference: http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/epc/configuration/15-mt/epc-15-mt-book/nm-packet-capture.html 

Answer: A,B 

Explanation: 

RTCP transports statistics for a media connection and information such as transmitted octet and packet counts, packet loss, packet delay variation, and round-trip delay time. An application may use this information to control quality of service parameters, perhaps by limiting flow, or using a different codec. 

Reference: http://en.wikipedia.org/wiki/RTP_Control_Protocol 

Answer: D 

Explanation: 

In OSPFv3, Instance ID is a new field that is used to have multiple OSPF process’ instance per link. By default it is 0 and for any additional instance it is increased, instance ID has local link significance only. OSPFv3 routers will only become neighbors if the instanceIDs match. It is thus possible to have multiple routers on a broadcast domain and all run Ospfv3 but not all of them becoming neighbors. 

Reference: https://supportforums.cisco.com/document/97766/comparing-ospfv3-ospfv2-routing-protocol 

Answer: A,E 

Answer: C 

Explanation: 

In the case of the GRE tunnel interface, the IP maximum transmission unit (MTU) is 24 bytes less than the IP MTU of the real outgoing interface. For an Ethernet outgoing interface that means the IP MTU on the tunnel interface would be 1500 minus 24, or 1476 bytes. 

Reference: A spoke site that is connected to Router-A cannot reach a spoke site that is connected to Router-B, but both spoke sites can reach the hub. What is the likely cause of this issue http://www.cisco.com/c/en/us/support/docs/ip/generic-routing-encapsulation-gre/13725-56.html 

Answer: A,E 

Explanation: 

The following is sample output from the show ip ospf command when entered without a specific OSPF process ID with no authentication. 

Router# show ip ospf 

Routing Process "ospf 201" with ID 10.0.0.1 and Domain ID 10.20.0.1 

Supports only single TOS(TOS0) routes 

Supports opaque LSA 

SPF schedule delay 5 secs, Hold time between two SPFs 10 secs 

Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs 

LSA group pacing timer 100 secs 

Interface flood pacing timer 55 msecs 

Retransmission pacing timer 100 msecs 

Number of external LSA 0. Checksum Sum 0x0 

Number of opaque AS LSA 0. Checksum Sum 0x0 

Number of DCbitless external and opaque AS LSA 0 

Number of DoNotAge external and opaque AS LSA 0 

Number of areas in this router is 2. 2 normal 0 stub 0 nssa 

External flood list length 0 

Area BACKBONE(0) 

Number of interfaces in this area is 2 

Area has no authentication 

SPF algorithm executed 4 times 

Area ranges are 

Number of LSA 4. Checksum Sum 0x29BEB 

Number of opaque link LSA 0. Checksum Sum 0x0 

Number of DCbitless LSA 3 Number of indication LSA 0 

Number of DoNotAge LSA 0 Flood list length 0 

Reference: http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_ospf/command/iro-cr-book/ospf-s1.html#wp8749965360 

Answer: C,D 

Explanation: 

AAA can be used to authenticate user login and the enable passwords. 

Example 1: Same Exec Authentication Methods for All Users 

Once authenticated with: 

aaa authentication login default group radius local 

All users who want to log in to the access server have to be authorized using Radius (first method) or local database (second method). 

We configure: 

aaa authorization exec default group radius local 

Note. On the AAA server, Service-Type=1 (login) must be selected. 

Note. With this example, if the local keyword is not included and the AAA server does not respond, then authorization will never be possible and the connection will fail. 

Reference: http://www.cisco.com/c/en/us/support/docs/security-vpn/terminal-access-controller-access-control-system-tacacs-/10384-security.html 

Answer: A,E 

Answer: A 

Answer: D 

Explanation: 

As the iBGP learned routes are reflected, routing information may loop. The route reflector model has the following mechanisms to avoid routing loops: 

. Originator ID is an optional, nontransitive BGP attribute. It is a 4-byte attributed created by a route reflector. The attribute carries the router ID of the originator of the route in the local autonomous system. Therefore, if a misconfiguration causes routing information to come back to the originator, the information is ignored. 

. Cluster-list is an optional, nontransitive BGP attribute. It is a sequence of cluster IDs that the route has passed. When a route reflector reflects a route from its clients to nonclient peers, and vice versa, it appends the local cluster ID to the cluster-list. If the cluster-list is empty, a new cluster-list is created. Using this attribute, a route reflector can identify if routing information is looped back to the same cluster due to misconfiguration. If the local cluster ID is found in the cluster-list, the advertisement is ignored. 

Reference: http://www.cisco.com/c/en/us/td/docs/ios/12_2/ip/configuration/guide/fipr_c/1cfbgp.html