You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this test , CreateFlow creates a raw tx only port mode raw traffic flow with no rx port specified .
func (a *testArgs) createFlow(t *testing.T, name, dstMac string) string {
flow := a.top.Flows().Add().SetName(name) flow.Metrics().SetEnable(true) flow.Size().SetFixed(300) e1 := flow.Packet().Add().Ethernet() e1.Src().SetValue(atePort1.MAC) flow.TxRx().Port().SetTxName("port1") <<<<<<< e1.Dst().SetChoice("value").SetValue(dstMac) v4 := flow.Packet().Add().Ipv4() v4.Src().SetValue(atePort1.IPv4) v4.Dst().SetValue(dstPfxMin) a.ate.OTG().PushConfig(t, a.top)
I believe since Rx port is not specified , Rx stats is not expected in this case of generating 1-arm test traffic. The 0 Rx in the logged o/p in this case should not be relevant to test pass/fail. Test/pass in this test appears to be driven by port stats on rx test ports using the port metrics and not the flow metrics.
Please let us know if test is passing or not and if failing , is it failing in some other point e.g. verifying port metrics on OTG ports.
Seeing RX stats missing in flow statistics even though stats are received on port .
Script seeing issue is :
https://github.com/openconfig/featureprofiles/tree/main/feature/gribi/otg_tests/backup_nhg_multiple_nh_test
OTG Flow Metrics
-------------------------------------------------------------------------------- Name Frames Tx Frames Rx FPS Tx FPS Rx
BaseFlow 60040 0 0 0
-------------------------------------------------------------------------------- backup_nhg_multiple_nh_test.go:383:
OTG Port Metrics
------------------------------------------------------------------------------------------------------------------------ Name Frames Tx Frames Rx Bytes Tx Bytes Rx FPS Tx FPS Rx Link
port1 60040 2 18012000 366 0 0 up
port2 0 60044 0 18012504 0 0 up
port3 0 4 0 504 0 0 up
port4 0 4 0 504 0 0 up
------------------------------------------------------------------------------------------------------------------------
The text was updated successfully, but these errors were encountered: