> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Dell R720 disk failure: Kayako to RMA in one workspace

> Triage a Kayako ticket, confirm a failed disk on a Dell PowerEdge R720 over iDRAC, file the warranty RMA with Dell ProSupport, and book datacenter access — without leaving Studio.

A Kayako ticket lands at 02:14 from a customer at the colo: their file server feels slow and a red LED is flashing on the chassis. The on-call MSP engineer triages from one Studio window: the ticket, Zabbix history, iDRAC, the vendor RMA email, the calendar entry for the datacenter walk, and the customer reply.

## Systems involved

| System                  | Role                                                                    |
| ----------------------- | ----------------------------------------------------------------------- |
| Kayako                  | Source ticket and final customer reply.                                 |
| Zabbix                  | Confirm the alert history and rule out a transient blip.                |
| Dell iDRAC9             | Look at storage controller, identify the failed physical disk.          |
| Dell ProSupport (Gmail) | File the RMA email with serial, service tag, slot, and error log.       |
| Google Calendar         | Book the datacenter access window with the colo's reception.            |
| Slack `#noc`            | Internal chatter and handoff to the morning shift.                      |
| Studio Memories         | Save the colo access procedure and Dell warranty pattern for next time. |

## Walkthrough

<Steps>
  <Step title="Open the ticket from Kayako">
    Copilot pulls the Kayako thread via the connector. The customer message names the host (`fs-acme-01`), notes the chassis LED, and attaches a phone photo of the front panel.
  </Step>

  <Step title="Cross-reference Zabbix">
    Copilot queries Zabbix for the same host. The disk-health trigger fired three hours ago, predicate flapped twice in the last week, and IOPS dropped 40 percent at the same time. Not a one-off.
  </Step>

  <Step title="Open the iDRAC web UI from the host">
    The Studio host entry for `fs-acme-01` already has an HTTPS protocol pointing at `idrac-fs-acme-01.colo.local` with the Keychain credential attached. One click opens it in a tab. Storage → Physical Disks shows PD 0:1:3 in Failed state, predictive failure log present.
  </Step>

  <Step title="Capture evidence into a report artifact">
    Right-click the iDRAC tab and ask Copilot to summarize. It pulls service tag, model (R720), iDRAC version, slot number, and the SMART error block into a Markdown report artifact stamped with the ticket ID.
  </Step>

  <Step title="Draft the Dell ProSupport RMA email">
    Copilot drafts the RMA email through the Gmail connector — service tag, failed slot, error log, dispatch address, on-site contact name. You review the draft, fix the contact phone, and send.
  </Step>

  <Step title="Book the datacenter access window">
    Copilot creates a Google Calendar event for the swap window, invites the colo reception desk, and adds the asset list and access PIN to the description. The event is also posted in `#noc` for visibility.
  </Step>

  <Step title="Reply to the customer in Kayako">
    Copilot drafts a status reply: failed disk confirmed, warranty RMA filed, replacement ETA from Dell, swap booked for the next window, no data loss expected (RAID6 still in degraded state). You review and send.
  </Step>

  <Step title="Save what was learned">
    Promote the iDRAC capture path to a procedure called `Dell PowerEdge disk failure triage` with arguments for hostname, ticket ID, and slot. Save a memory: "Dell ProSupport RMA emails for ACME go to `dispatch-aps@dell.example` and require the colo PO number in the subject."
  </Step>
</Steps>

## Where Studio earns its keep

* The Kayako ticket, Zabbix history, and iDRAC view sit beside each other in the same workspace — not three browser tabs and a password manager.
* Copilot reads the iDRAC storage page and writes the structured RMA email instead of you copy-pasting service tags into Gmail.
* The procedure you save means the next R720 disk failure is a one-prompt run, not an hour of triage.
* The customer reply, vendor RMA, and calendar entry all reference the same ticket ID without you typing it more than once.

## Related

<CardGroup cols={2}>
  <Card title="Connectors and MCP" icon="plug" href="../../connectors-and-mcp" arrow="true" cta="Wire it up">
    How Kayako, Zabbix, Gmail, and Calendar appear as Copilot tools.
  </Card>

  <Card title="Procedures" icon="workflow" href="../../procedures" arrow="true" cta="Save the path">
    Promote this workflow into a runbook the next on-call engineer just runs.
  </Card>
</CardGroup>