Want to enable Feature EPFT with “routing-protocols-enable”. However ,it is throwing an error and ask to configure the following command: “non-subscriber-interfaces mac” which once enabled drops the traffic without any penalty.
EPFT for routing-protocols can be enabled with “non-subscriber-interfaces mac” command only which means bad actor identification will be done on mac basis .When a bad actor is identified based on mac there will be complete drop no penalty policing will be done for penalty policing to happen please change the config as “non-subscriber-interfaces”.
The complete drop is for traffic from bad actor. All other mac on the interface should be able to pass traffic via the interface.
My understanding of enabling ‘routing-protcols-enable’ for EPFT is that itpreventsrouting protocols (eg: BGP) from triggering any ‘bad actor’ condition; Is that correct?
Without enabling "routing-protocols-enable" command:
> EPFT functionality bypasses all routing protocols by default. This is done to explicitly avoid dropping of necessary control-plane packets like route updates. Control-plane is already protected via LPTS.
> By default EPFT is not enabled, thus BGP packets <updates> will not fall under penalty as per design. By default LPTS has configured rate for BGP packets to be policed if it goes over the limit.
The correct command to check the same is following:
show lpts pifib hardware police location <>
show lpts pifib dynamic-flows statistics location <>
show lpts pifib hardware entry location <> | be <SIP>
SIP > Source IP with which peering is done and who sent big updates to check the rate of traffic.
Once EPFT for routing protocols is enabled:
lpts punt excessive-flow-trap non-subscriber-interfaces mac^ routing-protocols-enable
> EPFT, if enabled for routing-protocols can cause issues with dropping the traffic frombad actor<which can be updates if sent at a very high rate, and are not expected>. Usually normal updates are never identified as bad actor.
*Bad actoris a term to state a user sending huge amount of “for-us” traffic
My understanding is also that it’s correct behaviour for the above knob to only be useable in conjunction with ‘non-subscriber-interfaces mac’ enabled.
The EPFT feature for routing protocols issupported only with non subscriber mac interfaces.
It only supports source based MAC filtering.
Once a bad actor is identified all the traffic with that particular source will be dropped for penalty-timeout which can be modified as follows:
lpts punt excessive-flow-trap
penalty-rate arp 10
penalty-rate icmp 0
penalty-rate igmp 50
penalty-rate ip 100
penalty-timeout ospf 0
penalty-timeout bgp 0
exclude interface <back_bone_interface> // Can exclude both physical and sub-interface
Want to confirm why the default parameters are set <seen by the output of command “show lpts punt exc info” >though EPFT is not configured?
The output of this command is just to let us know that once EPFT is enabled than following parameters will be set which can be changed by using commands. If we want to see whether EPFT is enabled or not. It can be confirmed via following command:
- Show lpts punt excessive-flow-trap trace | in Elephant
- Show lpts punt excessive-flow-trap trace | in routing_protocol_enable >> it should have value =1
>> The output will show Elephant trap enabled or disabled and it will also show various parameters for which it is enabled once configured.
I understand what "urgent priority" does. I also understand what ! does in a route pattern. But when they were put together, I'm confused.! is usually used on variable length dial strings, e.g. international dialing. CallManager usually ...
Hi all;I have a carrier network with NCS 5501, we deliver L2VPN service to customers, how can I configure NCS 5501 UNI interface which is Bundle-Ether interface to process LACP PDU locally ?Note that for my service, customer promise equipement (CPE) conne...
Hi all,on all our new ASR9k we are observing a loss of NTP synchronization. We have many IOS devices which do not show this issue, so obviously it is not a network problem as the NTP servers are the same for all devices (internal server). I see...
So I picked up a used 2911 to replace my aging 3825 that I use for home router and intercom system via low end cisco 69xx voip phones. Was hoping the newer unit, advertised with CME 12, would let me maybe upgrade my phones to something more colorful.Note:...