Download Implementing Cisco Enterprise Advanced Routing and Services (300-410 ENARSI).300-410.CertDumps.2020-11-11.100q.vcex

By default, RADIUS uses UDP port 1812 for authentication and port 1813 for accounting. In the exhibit above we see port 1814 is being used for authentication to AAA server at 10.1.1.1 which is not the default port so we must adjust the authentication port to the default value 1812.

The class-map NMS in the exhibit did not classify traffic into specific protocols so many packets were dropped. We should create some class-map to classify the receiving traffic. It is also a recommendation of CoPP/CPP policy:“Developing a CPP policy starts with the classification of the control plane traffic. To that end, the control plane traffic needs to be first identified and separated into different class maps.” Reference: https://ptgmedia.pearsoncmg.com/images/9781587143694/downloads/i9781587143694_app02.pdf

vty 0:+ cisco + 0csic vty 1:+ no username + no password The command “aaa authentication login default none” means no authentication is required when access to the device via Console/VTY/AUX so if one interface does not specify another login authentication method (via the “login authentication …” command), it will allow to access without requiring username or password. In this case VTY 1 does not specify another authentication login method so it will use the default method (which is “none” in this case).

In the above configuration we have not had activated our IP SLA operation. We can start it with this command:R1(config)#ip sla schedule 100 life forever start-time now Also we should specific the rate of ICMP echo:R1(config-ip-sla-echo)#frequency 5 // Send ICMP echo every 5 seconds

Even PC2 cannot reach PC1 so there is something wrong with RIP redistribution in R2. Because RIP has higher Administrative Distance (AD) value than OSPF and EIGRP so it will be looped when doing mutual redistribution.

The entry and exit routers of an MPLS network are called edge LSR (or label edge routers – LER), which, respectively, inject (push) an MPLS label onto an incoming packet (label assignment) and remove (pop) it off the outgoing packet (label removal).

From the exhibit, we learned:+ VRF customer_a was exported with Route target (RT) of 1:1 so at the remote site it must be imported with the same RT 1:1.+ VRF customer_a was imported with Route target (RT) of 1:1 so at the remote site it must be exported with the same RT 1:1.Therefore at the remote site we must configure the command “route-target both 1:1” (which is equivalent to two commands “route-target import 1:1” & “route-target export 1:1”.

Label Switch Router:+ Reads the labels and forwards the packet based on the labels + Performs penultimate hop popping Label Edge Router:+ Handles traffic between multiple VPNs + Assigns labels to unlabelled packets

By default BGP advertises all prefixes to external BGP neighbors. This means that if you are multihomed (connected to two or more ISPs) then you might become a transit AS. For example, ISP 2 in AS 200 can send traffic to your router in AS 100 to reach ISP 3 in AS 300 because you advertised prefixes in ISP 3 to ISP 2. This is what will be seen in the BGP routing table of ISP1:     In order to prevent this we have to ensure that your router only advertises prefixes from its own autonomous system. One of the method to solve this problem is using Filter-list with AS-PATH access-list:     R1(config)# ip as-path access-list 1 permit ^$ R1(config-router)#neighbor 192.168.12.2 filter-list 1 out R1(config-router)#neighbor 192.168.23.3 filter-list 1 out It ensures that we will only advertise prefixes from our own AS. The ^$ regular expression ensures that we will only advertise locally originated prefixes. We should apply this filter to both ISPs.