- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- "Invalid session key" error when making HPE 3PAR A...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2023 05:17 AM - edited тАО05-25-2023 05:20 AM
тАО05-25-2023 05:17 AM - edited тАО05-25-2023 05:20 AM
"Invalid session key" error when making HPE 3PAR API calls from Linux servers
Hello all,
I'm having issues when trying to make API calls to the HPE 3PAR storage system from Linux servers. most of the times when I making a call I get an "Invalid session key" error. This problem seems to happen only on Linux environment, as the API calls work fine with Windows environment.
I have also tested making calls using both a PowerShell script and a Python script and in both cases, I encounter the "invalid session key" errors when running them on Linux servers. However, when I run these scripts on a Windows environment, everything works fine.
Any guidance or suggestions to resolve this issue would be greatly appreciated.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-25-2023 11:14 PM
тАО05-25-2023 11:14 PM
Re: "Invalid session key" error when making HPE 3PAR API calls from Linux server
Hi vmorales-2920,
I don't know much about API calls. Following may be the issues-
1) Is the key you are using configured with "In Role"
2) Is the key a valid one ?
3) Any network stoppage such as linux server might be in different subnet, network protocol or firewall is a barriar.
Regards,
Shiva_JR
Please mark as 'Accepted solution' if my post worked.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2023 09:47 AM - last edited on тАО05-28-2023 11:11 PM by Sunitha_Mod
тАО05-26-2023 09:47 AM - last edited on тАО05-28-2023 11:11 PM by Sunitha_Mod
Re: "Invalid session key" error when making HPE 3PAR API calls from Linux server
Hi shiva,
We are using the hpe3par python sdk and the package manage the session keys itself, also username and password are correct. We also check the network and it seems to be fine.
Could you explain to me what you mean if the key we're using is configured with "In Role"?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2023 07:11 PM
тАО06-05-2023 07:11 PM
Re: "Invalid session key" error when making HPE 3PAR API calls from Linux server
open a ticket with HPE support center
I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]