Cirrus Config Integration with Orion web-only Server

jodros

I have successfully Integrated Cirrus with Orion using the default website on the polling engine, however our production website resides on another server.  I have copied all files into the appropriate locations on the web-only server, which allowed the new menu items to display.  I also put in the unc path to the polling server, where Cirrus is installed, but I click on the link on the web-only server, it returns the message file does not exist.  If the same file was located on the web-only server and I told it to look for that file locally, it works, but that means I have to sync the two directories between the two servers.  I verified that the web-only server has permissions to the directory on the polling server, as well as verified that I see the web-only server logging onto the polling server within my event log.  I also tried modifying the configlisting.asp file without success.  Is there anyone at SW or anyone running a similar environment that could help me with this issue?  I would greatly appreciate it.  My only other option is to write a vb script that would copy the config-archive directory to the web-only server and schedule it to run once daily, but I would rather not have all of my configs in two locations when it isn't necessary.

 

Thanks 

jodros

I have now fixed my issue.  Even though the web server account as well as my domain account had permissions to the share on the polling server and I was able to unc from the web server, it was failing.  The security audits finally showed that while you are logged into the webpage, IIS will forward all anonymous requests as the IUSR_(machinename) account, which my polling server was rejecting.  I had to go into IIS Manager -> Websites -> right click on SolarWinds NetPerfMon -> properties -> Directory Security -> Edit Authentication and access control -> and change the username and password to a local account that was on both machines.  In doing this, it is acting as if the polling server was logging into itself to look at the share, or mimicking a single-signon environment.  I then only allowed the local account to have permissions to the share.  The text string that I entered in the Config Listing page has this format:

\\{remote machine name}\Config-Archive\${Caption}\${Caption}-Running.Config

 I did not want to have to schedule a daily task of pulling configs to keep the config-archive up to date.  I also didn't want more than 1 config saved for each device in the config-archive.  I am already saving multiple files in the SQL database, so I only wanted the most recent config for all of my devices.  I also have this configured under settings for config-archive.  I am running RTD as well, so whenever there is a config change, the file for that device is over written in the config-archive and my web-only server will always pull the most recent config for the device, WITHOUT having to locally store the files on the web-only server.

I also ran into the issue of changing the name of the device in Orion to something other than the hostname pulled down from and SNMP query.  I got around this issue by going to the Custom Property Editor and adding the SysName column to display in the settings.  Then I changed my string to pull from the SysName and not the Caption, since the Caption can be edited, but the SysName will always be the Hostname of the device.  Now that issue is fixed.  The string is below:

\\{remote machine name}\Config-Archive\${SysName}\${SysName}-Running.Config

 If anyone is thinking of running this same setup, which I highly recommend until Cirrus web console comes out, let me know and I will be happy to answer any questions that you might have.