Unknown - The device is not being polled, so its state is unknown. Up - The device is working below the specified thresholds. Warning - The specified threshold for warning state has been Badgeĭown - No response has been received from the device or interface withinĬritical - The specified threshold for critical state has beenĪlarm - The specified threshold for alarm state has been met. You can download the chart data conversion script from this link:Įxception: Installing InterMapper on an Intel-based Mac OS X system will run the conversion process automatically as part of the installation process, if needed.NOTE: You can specify which badges you want to appear in the Intermapper User Preferences window. Similarly, you must follow the same procedure if you are migrating from Solaris/Sparc to Linux/x86. For example, if you are migrating from Mac OS on PowerPC to Windows XP or Linux/x86, you must run a conversion script manually. Note: If you are migrating from a PowerPC or Sparc system to a non-Mac Intel-based system, you must run a chart data conversion script manually. * UNIX/Linux: /var/local/InterMapper_Settings * Mac OS X: /Library/Application Support/InterMapper Settings * Windows: See note following this entry. The default location for the InterMapper Settings folder depends upon the platform where installed: On the new server, start the InterMapper service/daemon. Note: If you are migrating from a Mac OS X server, you will need to delete the 'Chart Data' alias file in the InterMapper Settings folder, and rename the InterMapper Settings -> Chart Data.noindex folder to 'Chart Data' prior to starting the InterMapper service/daemon on the new server.Ĥ. In the above command, replace with the desired InterMapper user name, which in most cases is 'intermapper'. If the new server is Linux, ensure that you set the file ownership of the InterMapper_Settings folder, using the /sbin/chown command: Some FTP servers default to TEXT mode if BINARY mode is not explicitly set, and that can result in file corruption.ģ. Note: If you transfer the InterMapper Settings folder using FTP, ensure that the transfer is made in BINARY mode. Stop the InterMapper service/daemon on the old server and copy your InterMapper Settings folder to the new platform, replacing the one created when you installed InterMapper on the new server. Install InterMapper on the new server or volume, and stop the InterMapper service/daemon when installation is complete.Ģ. Install InterMapper on the new server or volume.ġ. Some FTP servers default to TEXT mode if BINARY mode is not explicitly set, and that can result in file corruption.Ģ. Stop the InterMapper service/daemon on the old server and copy the InterMapper Settings folder to the /Library/Application Support folder on the OS X machine. In order to move InterMapper to another server or volume, please follow the platform-specific instructions below:ġ. How can I migrate InterMapper to a new server?Ī.
0 Comments
Leave a Reply. |