'qos_ea' detected the 'fatal' condition 'Unsupported police action for L2 interface'
I tried to configure policing in class-default and applied to L2 interface but after commit i got the error % 'qos_ea' detected the 'fatal' condition 'Unsupported police action for L2 interface'. I try to research but not found any restriction about this. CRS-8/S XR.4.2.1. Thanks in advance
policy-map LTC-150M class class-default police rate 150 mbps conform-action set mpls experimental topmost 5 exceed-action drop ! end-policy-map
In scaled EVPN deployments it can be wise to name ESI that way to represent the site/physical port/etc it is attached to. Thus on some remote location you can easily verify where particular route/MAC is coming from. Similar to phone numbers, where...
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.
XR-vm - CLI's
look for any process crash, review time stamp[if it is too old, then no immediate action needed]
verify if standby state is Ready and NSR-Ready
show proc cpu | exclude " 0%"
It's been a long standing ask for XR to support conditional route advertisements in BGP.
The expected option of using the
option in RPL currently can only be used at the default-inf...
On IOS-XR, Quality of Service has an extension to WRED (Weighted Random Early Detection) called Explicit Congestion Notification (ECN). ECN will mark packets instead of dropping them when the average queue length exceeds a specific threshold value. When c...