Software Development Kit (SDK) and API Discussions

Broken ic-get-error-stats on new controllers?

kevingraham

The sfo-connection-state element in an ic-get-error-stats is documented in the 1.15 API (haven't looked at others) as:

Connection state with peer. Possible value: "not connected", "waiting for connected", "waiting for not connected", "connected", "waiting for teardown", "unknown"

...which is correct on older models, for example a healthy 3170A running 8.0.2P5D6 reports:    

          <sfo-connection-state>connected</sfo-connection-state>

However, on 3270's (8.0.1P5) and 62x0's (running 8.1D4) invented a new value, "Established":

          <sfo-connection-state>Established</sfo-connection-state>

While this is easy enough to accommodate for (despite the inconsistent use of capitalization relative to the rest of the API), the bigger concern is what other states should I expect? Is there an open BURT to attach a case to?

4 REPLIES 4

kunalm

Kevin

A burt has been open for the reported issue.

-Kunal

amirm

This issue also seen with ONATPI version 1.13.

Regards,

-Amir

kevingraham

Awesome, thanks. Do you have the BURT id?

amirm

Hi Kevin,

I have filed the bug with BURT#620223 on 7/12. Will keep you posted with the updates.

Regards,

-Amir

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public