Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1519403.1
Update Date:2018-01-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  1519403.1 :   Pillar Axiom: Failing to Discover Axiom via Axiom Storage Connect Plug-in 1.1 for Oracle VM Server for x86 3.X  


Related Items
  • Pillar Axiom 600 Storage System
  •  
  • Pillar Axiom 500 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
  •  




Created from <SR 3-6581022793>

Applies to:

Pillar Axiom 600 Storage System - Version All Versions and later
Pillar Axiom 500 Storage System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Failing to discover Axiom using Storage Connect Plug-in with "'HTTPS request failed'" errors.

Following is an example of the error reported during discovery:

Starting operation 'Storage Array Validate' on object '0004fb0000090000ee1c5af0596fa332 (AxiumPillar)'
Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_B000E Storage plugin command [storage_plugin_validate] failed for storage server [0004fb0000090000ee1c5af0596fa332] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_validate to server: mercurio failed. OVMAPI_4004E Server Failed Command: storage_plugin_validate oracle.axiom.PillarStorageArrayPlugin.PillarStorageArrayPlugin, Status: OSCPlugin.InvalidStorageArrayEx:"'HTTPS request failed'"


Cause

Problem is related to communication between Axiom and the OVM servers. Also discovery option could be another problem.
 

Solution

Please check below points as they are necessary for the plug-in connection.

I- Plug-in tries to connect to the Pillar Axiom management controller - Pilot -  via HTTPS using TCP port 8083. Please make sure this port is open for both Axiom and OVM servers. Port 8083 on the Pilot is open by default. The plug-in communicates over HTTPS on this port with the Pilot.

The port 8006 is used on server side which the Oracle VM Server listens. This port can be changed during the installation. Please make sure listening port is open on server side.

II- The Axiom Storage Connect Plug-in requires a webcli service running on the Axiom. To verify it is running, please use a web browser and navigate to URL:

https://<axiom>:8083/webcli/oneshotCLI.cgi?user=<axiomAccount>&pwd=<password>&cmd=system+-list+-details+-o+xml

 
Please replace the values between the "<>" with appropriate values. If you see an XML response, then the webcli is working correctly. Otherwise, it will need to be turned on. It can be turned on by using AxiomCLI, see below:


1- Download the most recent axiomcli bundle from the Axiom web interface
2- Log-in to the Axiom using AxiomCLI:
axiomcli login -u administrator -p [password] FQDN_or_IP_Address
3- Check status:
axiomcli webcli -list
4- Enable webcli service:
axiomcli webcli -enable

After webcli is enabled, please retry discovering the Axiom in OVM.

III- Trying to edit a default storage array option ("Unmanaged FibreChannel Storage Array") into using Axiom Storage Connect Plug-in will fail since it is an undefined behavior. The proper way to register Axiom Storage in OVM is to click on 'Register New Storage Array' option on registration screen.

For full procedure and details please check Plug-in documentation for all releases in http://docs.oracle.com/cd/E28661_05/index.htm

References

<BUG:16024078> - STORAGE CONNECT PLUG FAILING TO CONNECT TO AXIOM, HTTPS REQUEST FAILED

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback