Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

ONTAP Hardware

Problem with Autosupport on FAS2240


We have a problem with a Netapp filler. Sometimes it doesn't send Autosupports. Service processor and controller management can't ping. We noticed that after controller restart everything returns to normal. Unfortunately controllers after restart can't boot up, it is necesseary to pull them off manually from the chassis. Then they are starting to boot because service processor is also inaccessible. Restart of service processor doesn't cause it respond for ping.
We also don't have any trouble with filler in Poland, so I think it is not a network settings problem. Maybe it's a problem with a firmware. We can't add any log because we don't have any access to service processor.





It could be a hardware issue, please call support.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
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