ENCOR Exam QuestionsBrowse all questions from this exam
Go to Exam

ENCOR Exam - Question 798

SIMULATION

-

Guidelines

-

This is a lab item in which tasks will be performed on virtual devices.

• Refer to the Tasks tab to view the tasks for this lab item.

• Refer to the Topology tab to access the device console(s) and perform the tasks.

• Console access is available for all required devices by clicking the device icon or using the tab(s) above the console window.

• All necessary preconfigurations have been applied.

• Do not change the enable password or hostname for any device.

• Save your configurations to NVRAM before moving to the next item.

• Click Next at the bottom of the screen to submit this lab and move to the next question.

• When Next is clicked, the lab closes and cannot be reopened.

Topology

-

Tasks

-

Configure logging on SW01 and NetFlow on R01 to achieve these goals:

1. Enable archive logging on SW01 to track each time a change is made to the configuration and the user who made the change.

2. The NetFlow Top Talkers feature has been preconfigured on R01. Enable the feature for all inbound traffic on interface E0/2 of R01.

R01

-

SW01

-

Show Answer
Correct Answer:

Discussion

6 comments
Sign in to comment
blitzstorm
Sep 6, 2023

For 1st part I'd go with (starting in global config mode): archive log config logging enable For 2nd part I'd go with(starting in interface config mode): ip flow ingress

eddgg
Sep 12, 2023

The "ip route-cache flow" can be used only under the main interface, while the "ip flow ingress" was an enhancement to be used under subinterfaces.

eearmani
Dec 25, 2023

ip route-cache flow ( works only under L3 interface IP native interface )

JJBIG
Sep 17, 2023

I try on IOS version 15.9 ip route-cache flow = ip flow ingress only on the interface ip flow egress = outbound ip flow ingress= inbound So we should use command "ip flow egress" on router for monitor outbound traffic

JJBIG
Sep 17, 2023

Sorry the question ask: "all inbound traffic on interface E0/2 of R01" "ip route-cache flow" and "ip flow ingress" has the same functions

Rfvaz
Sep 15, 2024

This is the description of the command from IOS: ### LAB-SW(config-if)#ip ? route-cache Enable fast-switching cache for outgoing packets ### Well, the question is saying to us "ingress", so why use "route-cache" where this means "outgoing"?!

NetworkJanitor
Nov 20, 2024

Despite reading a few sources, both can be used -one at a time on the main interface. R01(config-if)#ip route-cache flow ? <cr> <cr> R01(config-if)#ip route-cache flow R01(config-if)#ip flow ingress ? <cr> <cr> R01(config-if)#ip flow ingress And, so 17.1 code contradicts what AI sources put together: ip flow ingress and ip route-cache flow should not be used together effectively. The key differences are: "ip route-cache flow" can only be configured on main interfaces. "ip flow ingress" is designed for use on subinterfaces. If you configure "ip flow ingress" on subinterfaces and then enable "ip route-cache flow" on the main interface: The main interface configuration will overwrite the subinterface settings. Data collection will start from the main interface and all subinterfaces hth

NetworkJanitor
Nov 20, 2024

But, for the purposes of answering the question, it should be: ! int g0/2 R01(config-if)#ip flow ? egress Enable outbound NetFlow ingress Enable inbound NetFlow <---------------- monitor Apply a Flow Monitor "ip flow ingress" command enables NetFlow data collection on the ingress (incoming) traffic of an interface

chmacnp
Feb 8, 2025

SW01 conf t archive log config logging enable R01 conf t int eth 0/2 ip flow ingress <----- no IOS version is given here so I assume post 12.2 which works well in lab end write mem <------------- don't forget this in any simulation 8-)