I am in the process of migrating our SA6000 (finally) over to the new PulseSecurePlatform, whilst the T's and C's and licensing discussions where being had I manually ported our configuration over to the DTE edition. This config came over quite easily as the 2x platforms are .. well the same. Within a few hours 2x DTE editions clustered replicated our SA6000 cluster perfectly. I have (today) exported --> imported our virtual DTE config --> SP and have found that CLUSTERING is not available in the SP edition, furthermore it did import the cluster configuration and partially recognises it.. leaving hosts in a weird position. I can see the config via;
But I cant clean it up.. the menus etc are all removed but when I select individual network interfaces I can see still the dropdown menu showing both nodes.
Other than being horrified that clustering has been taken out (yet works amazingly in DTE) I also cant work out how to strip it out, the XML segment seems to export when I try and export it.. and when I reimport with that segment removed it sees it as not overlapping and keeps it in play. The standard config file is (as most know) not editable.. so I cant remove it from that and reimport. It seems the SP edition has all the functionality there and is just menu crippled.. part of me thinks that I could just get it working just by working from the XML file only (horrible idea).
Id like to either remove all that config and/or understand if there is a virtual version that supports it.
That is correct, the SPE does not support clustering. The DTE does in recent releases. The most effective way to remove the clustering detail is to do a configuration clear from the serial console, provide IP detail, and import the user.cfg for the bulk of your configuration. For certificates, you can import those through the system.cfg import or through the certificate import interface
This is pretty much what I did last night, and it worked.. I then exported the XML and ensured it was all removed. So why would the DTE support clustering and the SP not? How do you get HA (config/session) for VMs during upgrade windows etc?
I'm not sure why that was done; I would recommend you check with your account team to see if information on why that decision was made can be made available as well as put in your request to investigate adding it to the SP version. For upgrades, I'm not sure. I believe that requires full downtime and utilization of the staged upgrade. I would recommend checking with your account team on how other sites handle this.