We've created a PW that works between the ASR907 and the ASR903 with a single service instance on each side that expects a single VLAN tag. When we create a flow in the Spirent with 9000 MTU, we see close to 100% utilization, which is expected. So basically, setup works perfectly. This works with two kinds of Spirent generated flows: one, ethernet frames exclusively and the second same succesful results when using IPv4 payload within ethernet frames. At this point, we're good and everything works.
Our problem starts when we use the exact same flows (mind you, we change the VLAN tag) and instead of using a P2P PW, we use a P2P via VPLS configuration (a multipoint scenario with only two endpoints). As long as the Spirent test traffic is solely ethernet-based (no IPv4) we see close to 100% utilization with no drops on the Spirent. Basically, same successful scenario as mentioned above. But, when we change that flow to use ethernet+IPv4, the see around 40% traffic loss, being this (and the VLAN tag) the only changes we make to the Spirent.
Please keep in mind that we're using the exact same Spirent created devices and flows for both tests, 3 of which work a expected. The problem arises when we configure the Spirent to instead of ethernet-only frames, it should send IPv4 payload within the ethernet frames.
We tried creating, 2 separate VPLS services with 5G worth of trafic each via the Spirent, and see the same behavior.
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...