Continuing the series of Splunk Cluster setup articles with instructions on Installation and Setup of Ubuntu Linux for Splunk Cluster setup.
Continuing the series of Splunk Cluster setup articles with instructions on Installation of Ubuntu Linux in VMWare for Splunk Cluster setup.
Slowly gaining more experience with Splunk and realizing power of this unique app, I ventured into cluster setup for Splunk 6.1 as part of the current initiative for the client I’m working with.
Below is a quick step-by-step instructions set which I compiled mainly for myself as a documentation.
After 3 hours of sleep, around 6am on Saturday, I came back to the office to fiddle around with server one more time. No matter what I did, ODR still thought that ODM is on the network, and I’ve decided to move to the Plan B.
Plan B was to export our current OD structure via Archiving, install new OS X server on MacMini and restore from there. Little I knew how corrupted LDAP was on the original server, after all ‘hard reboots’ throughout it’s lifetime.
By around 10am, I clearly understood that Plan C is my only solution – which was exporting users from original OD and re-importing them into brand new installation of OS X. The only positive from this approach was that our users would have to change their passwords upon initial login anyway, to comply with recent implementation of IT Sec Policy, so loosing user’s passwords was not a big deal.
By around 11:30, I had all my users imported and passwords reset, but one more hiccup was waiting for me…
And here comes magical day – Friday, May 20th. All planning is done, hopefully, and we are ready for servers’ upgrade, update and reconfiguration.
So first let’s see what we have, then we’ll see what we want, and then we will see what we get…
Our current setup is:
3 XServes and one VMWare OS X Server all working very hard and therefore one XServe, which acts as Open Directory Master (ODM), AFP, SMB, DNS, DHCP and Netboot server, works very hard every day and hangs ocasionally. During those ‘hangs’ “hard reset” is required, which does the number on the server. Single sign-on process is not working anymore and every time server ‘hangs’, since it’s running DHCP and DNS services, none of the users can access Internet. So back to set-up:
- XServe 1 – Mac OS X 10.5 Server, AFP, DNS, DHCP, SMB, ODM
- XServe 2 – Mac OS X 10.4 Server, AFP, FTP, Mail, Web and FileMaker Server
- XServe 3 – Mac OS X 10.5 Server, AFP, ODR (Open Directory Replica)
- VMWare Server – Mac OS X 10.5 Server,AFP, FileMaker Server
Now in order to free up XServe 1 and ensure it’s stability and no-impact on Internet, I’m bringing MacMini into the picture, running 10.6 OS X Server which will be DNS, DHCP and ODM. XServe 1 would then be AFP, SMB server – file server.
Plus, all servers, except VMWare server, will be running 10.6 Server software to increase performance of existing hardware and utilize latest Mac technologies.