Cloud Managed Networks

Hi All,

I have a Central on Premise Hardware Appliance ( HPE P52499-B21 ) that I am attempting to configure. The Cluster setup keeps failing.

I have a Fortigate Router to provide the DNS resolution for the FQDN requirements and to provide Internet access during setup.

I am trying to use {sitename.local} for the domain name. I have created all the mandatory FQDN entries on the Fortigate for the Node and Cluster.

This is a single node cluster

I can create the node, confirm network connectivity & name resolution from the CoP Appliance to the Fortigate and switch network plus the NTP Server

When I try to create the cluster, all the setting pass all the internal validation and start the creation process.

Approx 1 Hour later I end up with a message:

INITIALIZING SETUP Expecting Value Line 1 column 49 (char 48). Retrying to check Status
CLUSTER_CREATION_FAILED.  Setup-cluster has failed on this Cluster. Please run FACTORY-RESET  from the CLI Network on all nodes and the run setup cluster again.

Accessing the Cluster setup from the WebGui on my PC allows me to download the cop_setup_logs.

None of the logs seem to give any indication as to why it has failed

I have factory reset the nodes multiple times and tried unsuccessfully to recreate 

Has anyone had any problem like this before?

Anyone have a suggestion at which of the logs will tell me why it failed ?

Many Thanks

K

Please open a TAC case.

HI Willem,

Thanks for the quick response.

I thought I would report back the results as I hate finding a post matching my problem - and then no answers.

I worked with a great Aruba Engineer to sort the issue ( Hi Naveen)

Both Aruba Central On Premise Appliances were sent to me with version 2.5.8.6 from the factory.

Apparently there is something called a pingfed licence for 2.5.8.6 that has expired. It has something to do with the Single Sign On. This prevented  the Cluster Setup from completing.

Fix Process

• Get Aruba TAC to work out what the Administrator Password for the ILO is ( they only allow you reduced access copilo username)
• Download latest 2.5.8.9 ISO to your local PC
• Reinstall 2.5.8.9 via ILO & let it complete install ( you cant install the ISO without the FULL Administrator password for the Server BIOS access)
• Configure Temp Network Settings on Node
• Download 2.5.8.9 Apps Package (98GB)
• Get Aruba TAC to determine COP_shell password for node
• Upload Apps Package to Node via WinSCP (need IP and cop_shell details)
• Via CLI or ILO - "Install COP Software" 
• Reboot
• Enter Permanent Network Details 
• Run Cluster Setup ( Check all your FQDN are configured + reverse DNS on the node and Cluster)
• Take note of admin user details ( for SSO )
• Login to Virtual IP / FQDN

I am frustrated that this took more than 10 days to complete with Aruba TAC - mainly due to the fact the ARUBA doesn't trust the owner with the Administrator or COP_Shell password.

Cheers
Kahn

Thank you for sharing.

If you experience issues with TAC please contact your Aruba sales team. They can share the feedback internally.