BladeSystem - General
1825643 Members
3647 Online
109685 Solutions
New Discussion

Accessing SAS-BL-Switch returns “Not Authorized”

 
SOLVED
Go to solution
TheStormsOfFury
Occasional Collector

Accessing SAS-BL-Switch returns “Not Authorized”

Good morning everyone,

As the title says, we have an older C7 enclosure that recently started having issues connecting to the SAS-BL-Switch.

No firmware updates have been performed and quite some time, and we have done several different attempts to isolate the issue.

Some of the things we've tried include:

  • A full power cycle of the entire C7000 and MDS600, including Pulling all plugs and letting them discharge;
  • unseating, the primary SAS module and attempting to log into the secondary from the OA;
  • Unseating the primary OA And logging in via the second OA.

It has been a while since I've done much troubleshooting on this environment, but does anybody know where we could find a little bit more information on why it might be returning this "not authorized"?

3 REPLIES 3
BPSingh
HPE Pro

Re: Accessing SAS-BL-Switch returns “Not Authorized”

Greetings!

Please verify if this is the issue you are encountering.

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00119730en_us



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
TheStormsOfFury
Occasional Collector
Solution

Re: Accessing SAS-BL-Switch returns “Not Authorized”

@BPSingh, I'm sorry, this is what we found. I answered this on a thread over on Reddit, and forgot to post the update here.

It does appear someone updated to 4.57 without authorization. We don't know when it happened, but it did, and we rolled back and it is good.

Thank you for the response!

-TSoF

Sunitha_Mod
Honored Contributor

Re: Accessing SAS-BL-Switch returns “Not Authorized”

Hello @TheStormsOfFury,

Perfect! 

We are glad to know you were able to find the root cause of the issue, and we appreciate you keeping us updated.