Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Storage Manager (STM) > Storage Manager (STM) Documentation > SRM Profiler Administrator Guide > Appendices > Configure storage arrays > Pillar provider

Pillar provider

Updated: June 16, 2017

This information is provided 'as-is' as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor's SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you.

The Pillar SMI provider is embedded in the array itself, so there is nothing a customer needs to do to install it. If a customer is running an older Pillar Axiom system that has the 512Meg Pilot hardware, the provider is by default disabled. Provider is enabled by default on systems with 2 Gig Pilots.

Pillar doesn't recommend enabling the SMI provider if the customer has the older 512 Meg Pilots and recommends that they have it upgraded to the 2 Gig versions. Customers can contact Pillar's customer support to have their systems upgraded to the 2 Gig Pilots.

The provider uses the same username/passwords that the customer has set up for their Axiom systems. Standard SLP discovery mechanism is used.

The interop namespace for the provider is /root/pg_interop, and the namespace is /root/pillar.

Upgrades for the provider are bundled with system software upgrades. Currently Pillar is SMI 1.1 certified with the 2.3 Axiom software release.

Troubleshoot Pillar

The following section list FAQs for troubleshooting a Pillar provider.

Q: Since provider is embedded in the controller, is there a way to manually start/stop the provider? If so, how?

A: You can restart the provider two different ways (force a Pilot failover, or issue disable/enable startup command for smi provider) both of which require that the Support Tool be licensed and the supporttool software be locally installed.

You can get a list of the support tool commands with: supporttool.exe help list-requests > requests.txt

For a quick syntax of any command, use: supporttool.exe template –d [command name]

Restart smi provider using one of two avail methods

Use Support Tool to force a pilot failover

This is completely non-disruptive to the data path, it issues a Linux reboot to the active Pilot, which does a failover to the passive, and in the process starts the web service and SMI-S Provider service on the standby pilot.

Do not do this if there is a storage resource modifying task in progress.

$ supporttool.exe sub -u pillar -p a1s2d3f$ -H [your pilot hostname or shared IP] ForcePilotFailure

You should get a response that looks like the following:

  • Header
  • ProtocolVersion: 0.1
  • SessionKey: 7cc6935085aac74cda7d19a1d3f250fc
  • Time: 2009-07-28T15:40:50-07:00
  • ClientData: supporttool
  • RequestStatus: Succeeded
  • Error List
  • ForcePilotFailureResponse
  • Within a minute or two, you should be able to get back into the GUI as the standby pilot begins coming up.
  • Using Support Tool to disable/enable the provider
  • suporttool.exe PerformDisableSMIStartup
  • supporttool.exe PerformEnableSMIStartup


Q: Are there log files for the provider? If so, where are they located?

A: They are located on the pilot (if you can ssh to it) under /var/log. They can be obtained via "Collect System Information" under the "Support" tab. The tar you download will have the cimserver logs.

Q: When encountering smi-s issues, what information should we collect from customer's environment?

A: The System information logs. See above on how to obtain logs

Q: Where can one find exact array model info?

A: On the GUI, the System -> Summary page will provide you with the Model Number as AX300 or AX500 etc.

Q: When getting version of the smi-s, is that the slammer, pilo, or brick version when going to Axiom One web gui under support?

A: Pilot OS is the version to use. For example, if you're asked to be on version 3.3, it should show up as 03.03.XX

Q: What's the minimum version of the provider we should attempt to ascertain data from?

A: 03.03.15

Q: Is performance information available? If so, what metrics?

A: Yes. Only LUN performance is available as of the 03.03.15 Pilot release

Note: Per email from Shaq from Pillar on 09/14/09: For the statistics - we're probably going to be limited to LUN and file system statistics for the near future. We have plans to incorporate the remaining statistics in the release 5.x timeframe but that is a ways off

Q: What Pillar licenses are required to collect valid set of smi-s data?

A: At a minimum need either Fibre Channel Protocol or iSCSI Protocol

Q: What is the default username and password for AxiomONE Storage Services Manager web gui?


administrator / pillar - for admin level privileges

pillar / a1s2d3f$ - for support level privileges

Q: What license are available for the Pillar array?

A: Licensed Features:

  • 1MB Stripe
  • CIFS
  • Clone FS
  • Clone LUN
  • Fibre Channel Protocol
  • NDMP
  • NFS
  • Pilot SSH Access [for support use]
  • Pooled RAID10
  • SNMP
  • SecureWORMfs
  • Snap FS
  • Support Tool [for support use]
  • Thin Provisioning: FS
  • Thin Provisioning: LUN
  • Virtual Tape Library
  • Volume Backup
  • Volume Copy and Backup
  • iSCSI Protocol

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified



(not set)