Skip to main content
NetApp Knowledge Base

SANnav API Authentication Fails After Server Reboot – rngd Service Not Running

  1. Last updated
  2. Save as PDF
Views:
45
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

SANnav 2.3.1a

Issue

  • API calls fail with authentication errors immediately after server reboot.
  • Manual login with the same account works, and resetting the password temporarily restores API functionality.
  • When rngd service is not running, API authentication fails, even though manual logins work.
  • After each SANnav server reboot, ensure that the rngd service is active. If the rngd service is not active, then proceed to the solution.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.