300-410 Exam Dumps - Implementing Cisco Enterprise Advanced Routing and Services (300-410 ENARSI)

When R2 & R5 are route reflectors (RRs), routes from R4 & R8 are advertised to R5 and R5

advertises to R2. But R2 would drop them as R2 is also a RR. Therefore some routes are

missing on R1 to advertise to eBGP peers.

Good reference:

https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2015/pdf/TECRST-2310.pdf

Route reflectors (RR) must be fully iBGP meshed so we cannot configure RR on both R1 and

R5.

We should choose routers at the center of the topology RRs, in this case R4 & R5.

When the aggregate-address command is used within BGP routing, the aggregated address is advertised, along with the more specific routes. The exception to this

rule is through the use of the summary-only command. The “summary-only” keyword suppresses the more specific routes and announces only the summarized

route.

https://community.cisco.com/t5/other-network-architecture/out-of-band-router-access/td-p/333295

The “transport output none” command prevents any protocol connection made from R1.

Therefore our SSH connection to 192.168.12.2 was refused. In order to fix this problem we can

configure “transport output ssh” under “line console 0” of R1.

Note: The parameter “-l” specifies the username to log in as on the remote machine.

EIGRP does not have process ID as it uses Autonomous System (AS) numbers only.

This is not an authentication problem or we would see this error from the debug:

EIGRP: Ethernet0/0: ignored packet from 10.1.1.3, opcode = 1 (missing authentication or key-chain missing)

If the AS numbers between two routers are different then the neighbor relationship cannot be formed.

DHCP options 3, 66, and 150 are used to configure Cisco IP Phones. Cisco IP Phones download their configuration from a TFTP server. When a Cisco IP Phone starts, ifit does not have both the IP address and TFTP server IP address preconfigured, it sends a request with option 150 or 66 to the DHCP server to obtain this information.+ DHCP option 150 provides the IP addresses of a list of TFTP servers.+ DHCP option 66 gives the IP address or the hostname of a single TFTP server.

Diagram Description automatically generated

The MPLS LDP Inbound Label Binding Filtering feature can be used to control the amount of

memory used to store Label Distribution Protocol (LDP) label bindings advertised by other

devices. For example, in a simple Multiprotocol Label Switching (MPLS) Virtual Private Network

(VPN) environment, the VPN provider edge (PE) devices might require label switched paths

(LSPs) only to their peer PE devices (that is, they do not need LSPs to core devices). Inbound

label binding filtering enables a PE device to accept labels only from other PE devices.