- Web/Chat: http://support.fusionio.com/
- Email: support@fusionio.com; please provide the following to speed up your support request:
- A detailed description of your support request.
- Your complete contact information.
- The output of the “fio-bugreport” or “fio-win-bugreport”.
- Phone: (877) 816-5740, available 6:00 AM to 6:00 PM Mountain Time, Monday through Friday
Author: paul.deluca
How do I contact Red Hat for support?
There are a couple different methods for contacting Red Hat:
- Vendor: contact your hardware vendor (ie Dell)
- Web: https://access.redhat.com/support/cases/list
- Phone: 888-733-4281, options 3, 1, 1
- Your Red Hat Network username, customer number or contract number
- A detailed description of your support request
- Your complete contact information
- The file generated by the “sosreport” command
How do I disable C-States on a Dell server?
View a step-by-step screencast of this process:
A few customers have been affected by a firmware bug that can cause instability when using Intel’s C-State power-saving functionality. If you are still experiencing instability after verifying that your server is at the most recent recommended BIOS and firmware levels, you may disable C-States using two methods:
BIOS:
- Reboot the server
- Press F2 to enter the BIOS configuration menu
- Select Processor Settings
- Scroll down to “C States” and “C1E”
- Use the arrow keys to set both to Disabled
- Press ESC repeatedly and select “Save changes and exit”
OpenManage:
- Launch the OpenManage web interface (https://IP_ADDRESS:1311/)
- Log in using your root username and password
- Select Main System Chassis -> BIOS -> Setup tab
- Select “Processor C State Control”
- Select the “Disabled” radio button -> Apply -> “Go Back to BIOS Setup Page”
- Repeat for “Processor C1-E”
- Reboot the server to apply the settings change
How do I gather CrashPlan logs?
View a step-by-step screencast of this process:
Before contacting CrashPlan for support, please gather the CrashPlan PRO client backup logs:
- (Optional) Launch the CrashPlanDesktop client
- (Optional) Double-click the CrashPlan logo in the upper right corner
- (Optional) At the prompt that appears along the bottom of the screen, type “dump all” and hit Enter
- Open a terminal session to the server and run the following commands to create an archive of the CrashPlan client logs. In this example, we’ll name the archive “crashplan_logs_20110124.tar.gz” and send it to the root user’s Desktop folder:
cd /usr/local/crashplan tar czvf /root/Desktop/crashplan_logs_20110124.tar.gz ./log
Resources:
- CrashPlan Support: How do I submit client log files to support?
How does ABS Failover work?
Epicor’s ABS Failover offering builds on the capabilities of our ABS Online Backup service to offer cost-effective Eclipse hosting in the event of a disaster.
There are a few requirements that must be met for the ABS Failover service to function:
- Eclipse must be running on the Linux or Windows platforms
- Broadband Internet connection for secure, offsite ABS Online Backup
- Cisco-compatible WAN equipment for establishing connectivity to ABS Failover server(s)
In the event of a disaster, here is a general overview of the ABS Failover process:
- Disaster causes customer’s primary Eclipse server(s) to go offline
- Customer contacts Epicor Eclipse Systems Support team
- Eclipse restores customer’s most recent ABS Online Backup to a set of failover servers
- Customer connects to ABS Failover servers and continues business