HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Application Integration
Showing results for 
Search instead for 
Did you mean: 

Tenable Security Center on NimbleSorage

Go to solution
Occasional Contributor

Tenable Security Center on NimbleSorage

I'm planing to use Tenable Security Center on NimbleStorage. The Security Center does not allow to install the application and the database into the separated path from OS. Which leaves the only option is to attach the storage drive prior the OS boot. I will be using VmWare ESX to host Linux virtual machine for the Security Center. I was just wondering if there would be any issues to integrate with Nimble array with this scenario.

Esteemed Contributor

Re: Tenable Security Center on NimbleSorage

I don't see any issues with this configuration. You could put a second drive on a new disk, or based of your explanation you would be better to assign a single large disk and partition it as both boot and data by a logical partition. Having the large disk with multiple partitions meet your software requirements.

Occasional Contributor

Re: Tenable Security Center on NimbleSorage

The problem is Tenable Security Center does not allow to specify separated path from the application path during the install (CentOS).

I got the following response from Tenable Support as a work around for this problem:

"You can mount /opt/sc4 elsewhere, but you CANNOT use symbolic links. It will need to be a hardlink so that the host sees the partition or directory as a drive when it boots up."

Valued Contributor

Re: Tenable Security Center on NimbleSorage

Hi Alex,

You can add disks to the CentOS virtual machine through VMWare and mount them accordingly as per Tenable support have suggested. Use the appropriate VMWare datastores to host these drives or, you could use iSCSI to mount volumes directly from the Nimble array and separate the data that way (preferred). Do you anticipate the VM generating a lot of data and having a meaningful impact on the Nimble? If so, separate the data, whereas if its a small appliance chugging along in the background, it may be simpler to just keep it all contained in a single VM.

You might want to check this out for CentOS configuration:

centos configuration script.