firmware bundles for composer 1 repository

[jlangmead]

Hi

I have the need to upload 2 x SSPs to OneView 6.6 for Synergy that uses composer 1's. As there is only 12GB of space the 2 SSPs won't fit so I have two options that I'm trying to get working.

The first is to create custom SSPs for Synergy to make them small enough to both fit into 12GB - Are custom SSP's actually supported for Synergy???

Secondly, I have been trying to configure an external repository and following the instructions in the guide. The IIS has all be configured and I can connect to the VD via a web browser without issues - to keep things simple, I've enabled anonymous access so as not to introduce the complexity of passing any credentials. As mentioned, connecting via a browser works fine but when I try to add the repository to OneView it errors saying "Unable to access files on external repository due to an internal error. Resolution Wait for some time and try again, if the problem persists, contact your authorized support representitive with a support dump"  Is anyone successfully using an external repository and was there anything needed outside of the steps in the guide - as I've been following that and it's not working for me. I am using Windows 2019 for the web server - is this perhaps an issue as the guide only seems to mention Windows 2008 and 2012 - but I would have thought it shouldn't be necessary to have to use a version of Windows is end of support life with MS.

Many thanks

[DanCernese]

This has become a challenge given the increased size of the Synergy SSPs.  Unfortunately, it is not easy or simple to create a custom SSP for Synergy.  It is supported but it is hard enough that very few attempt it.

I do recommend pursuing the external repository-- the trick is, as you found out, proper authentication and WebDAV access.  There are details in the online help (both HPE web and inside the Composer help).  I had it working with Windows 2016.. ..but that lab is gone, sorry I can't help further myself.

[jlangmead]

Thanks Dan - I'll persevere with the external repository and log a support call if necessary.

thanks

[ChrisLynch · Accepted solution]

I have a sample PowerShell script that will help you here.  Please take a look at this script provided within the HPE OneView PowerShell library.  It requires the IIS Role be installed, and will help you install the WebDav feature and configure the web site you specify.  There are parameters to the scrip that will help you provide custom values to various options, including the filesystem location, the IIS Virtual Directory Name and repo size (an Int value in MB). 

I just deployed a brand new Windows Server 2019 Standard VM (standard installation with zero customization), installed the IIS role, then ran the script and then added with WebDav server as an External Respository to both an HPE OneView 6.60 and 8.50 appliances.  Here is a screenshot from a 6.60 appliance:

[jlangmead]

Thanks Chris

We downloaded and rund the script from a vanilla VM with just IIS installed. The script run successfully and we could browse the virtual directory from other machines on the network, but it still fails to add into OneView.

We get exactly the same error we recieved when we followed the OneView guide, so this makes me think we did have it correctly configured from the information in the guide.

The error we recieve back is below - which is a little vague and we're at a loss as to how to troubleshoot this further. The error indicates an issue accessing the files rather than connecting or authenticating with the IIS server. Is there anything here we can test further??

We have logged a support call as recommeneded in the reported error and uploaded a OneViewsupport dump to HPE Support but they say they can't find any errors. 

[jlangmead]

Hi Chris

We managed to sort this in the end.

The issue was with creating a physical path for the IIS virtual directory directly in the root of a dedicated volume. Seems OneView can't accept this. We created a top level folder and then the VD under this - once ths was done we could create the external repository. 

The script works well - thanks

[ChrisLynch]

@jlangmead glad you have this resolved.