Safety and Compliance Information
Understanding Configuration Details
PCIe Physical Slot Assignments
Shipping Kit With Single-Unit CMA Comb (Part No. 7069640)
Shipping Kit With Multi-Piece CMA (Part No. 350-1662-02)
Rackmount Kit With Single-Piece CMA Comb (Part No. 7069640)
Rackmount Kit With Multi-Piece CMA (Part No. 350-1662-02)
Determine Correct Rackmount Hardware
Mark the Rackmounting Location
Install the Rackmount Hardware
CMA Kit (Single-Piece CMA Comb, Part No. 7069793)
Install the Single-Piece CMA Comb
CMA Kit (Multi-piece CMA, Part No. 7041990)
Installing the Shipping Brace Assembly
Determine Correct Shipping Brace Fasteners
Install the Bottom Rear Shipping Brace
Remove the Bottom Rear Shipping Brace
Connecting Data and Management Cables
Powering On the Server for the First Time
Connect a Terminal or Emulator to the SER MGT Port
Power on the System for the First Time
Reach a State to Install a Fresh OS (Oracle ILOM CLI)
Reach a State to Install a Fresh OS (Oracle ILOM Web Interface)
Oracle Solaris OS Configuration Parameters
Assigning a Static IP Address to the SP
Log In to the SP (SER MGT Port)
Assign a Static IP Address to the NET MGT Port
Accessing the Server Using Oracle ILOM
Display the Oracle ILOM Prompt
Installing Auto Service Request Software
Software Requirements (ASR Manager)
Minimum Software Requirements (Oracle Exalytics In-Memory Machine T5-8 Server)
Installing ASR Manager Components
Install the Oracle Automated Service Manager Package
Install Service Tools Bundle for Oracle Solaris Only
Install the Oracle Auto Service Request Package
Configure ASR on the Server (Oracle ILOM)
Configuring ASR on the Server (Oracle Solaris 11)
Enable the HTTP Receiver on the ASR Manager
Enable HTTPS on ASR Manager (Optional)
Register Server With Oracle Solaris 11 to ASR Manager
Approve and Verify ASR Activation
Managing Oracle Solaris 11 Boot Environments
Advantages to Maintaining Multiple Boot Environments
Mount to a Different Build Environment
Reboot to the Original Boot Environment
Auto Service Request (ASR) is designed to automatically open service requests when specific Oracle SuperCluster T5-8 hardware faults occur. To enable this feature, the system components must be configured to send hardware fault telemetry to the ASR Manager software. The ASR Manager must be installed on a server that has connectivity to the system, and an outbound Internet connection using HTTPS or an HTTPS proxy.
When a hardware problem is detected, the ASR Manager submits a service request to Oracle Support Services. In many cases, Oracle Support Services can begin work on resolving the issue before the database/system administrator is even aware the problem exists.
Prior to using ASR, set up the following:
Oracle Premier Support for Systems or Oracle/Sun Limited Warranty
Technical contact responsible for the Oracle Exalytics In-Memory Machine T5-8 server
Valid shipping address for the Oracle Exalytics In-Memory Machine T5-8 server
An e-mail message is sent to both the My Oracle Support (MOS) e-mail account for Auto Service Request and the technical contact for the activated asset, notifying them of the creation of the service request.
Note - If a subscriber has not been set up, then the subsequent Auto Service Request activation will fail.
Consider the following information when using ASR:
ASR is applicable only for component faults. Not all component failures are covered, though the most common components, such as disk, fan, and power supplies are covered. For more information, see:
Click the Documentation link on this page, then refer to the “ASR Fault Coverage Information” section at the bottom of the page.
ASR is not a replacement for other monitoring mechanisms, such as SMTP, and SNMP alerts, within the customer data center. It is a complementary mechanism that expedites and simplifies the delivery of replacement hardware. ASR should not be used for downtime events in high-priority systems. For high-priority events, contact Oracle Support Services directly.
There are occasions when a service request may not be automatically filed. This can happen because of the unreliable nature of the SNMP protocol, or loss of connectivity to the ASR Manager. Oracle recommends that customers continue to monitor their systems for faults and call Oracle Support Services if they do not receive notice that a service request has been automatically filed.
Tip - Refer to the Oracle Auto Service Request web page at http://www.oracle.com/asr for more information on ASR.