[TC-ETHDIAG-1.1] attribute with default as "null" showing failure response

[ghost]

Summary:
As per spec default value of PHYRate attribute is "null" showing failure response when we executed.

Spec screenshot:

Execution logs and screenshot:

ethdiag.txt

[ghost]

@bzbarsky-apple still facing this issue if we try to read the null value.

[bzbarsky-apple]

That's an UNSUPPORTED_CLUSTER response. Is the cluster involved actually enabled in the server you are trying to read from @manjunathambiger23, on the endpoint you are reading from?

[ghost]

@bzbarsky-apple i uploaded wrong logs i tried it in endpoint 0 its still showing failure response

[bzbarsky-apple]

@manjunathambiger23 Is the response still UNSUPPORTED_CLUSTER?

Which exact commands are being run on which exact SHA on which exact example apps?

[ghost]

@bzbarsky-apple the response is: expected to be null but isn't

exe_log.txt

[bzbarsky-apple]

The spec for PHYRate says:

The PHYRate attribute SHALL indicate the current nominal, usable speed at the top of the physical layer of the Node. A value of null SHALL indicate that the interface is not currently configured or operational.

It's coming back as "5", which is "Rate10G".

Why are you expecting null? Is the interface in question in fact "not configured or operational"? What is the exact server setup? @manjunathambiger23

[bzbarsky-apple]

Resolving, given correct-looking SDK behavior and no response.