> ## 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.

# End-of-life hardware refresh: vuln scan to install date

> A vulnerability scan flags an EOL Catalyst 2960. Build the replacement BOM, request quotes from three vendors, win customer approval, schedule the install, and dispatch a field tech with the right gear.

A monthly vulnerability scan flags six Catalyst 2960-X switches at a customer's two branches as past Cisco's last day of support. The MSP needs a replacement plan that the customer will fund, sourced gear that's actually in stock, an install scheduled for an after-hours window, and a field tech booked with the new switches in their van.

## Systems involved

| System                                     | Role                                                           |
| ------------------------------------------ | -------------------------------------------------------------- |
| Tenable / Qualys / Wazuh                   | Source vulnerability scan with the EOL findings.               |
| Studio inventory                           | The six target devices with site, port count, current uplinks. |
| Cisco EOL data                             | Confirm the model's EOL/EOS dates and recommended replacement. |
| Distributor APIs (Synnex, Ingram, Westcon) | Quote and stock check across three distributors.               |
| ConnectWise PSA                            | Customer record, opportunity, project, and dispatch.           |
| Gmail                                      | Customer-facing quote, approval, and confirmation email.       |
| Google Calendar                            | Maintenance window and field tech schedule.                    |
| FedEx / DHL                                | Shipment tracking attached to the ticket.                      |

## Walkthrough

<Steps>
  <Step title="Pull the vuln scan finding into context">
    Copilot fetches the scan result via the connector. Six devices, two sites, current model, last day of support already past, recommended successor `C9200L-24P-4G-E`.
  </Step>

  <Step title="Read each device's current configuration">
    For each target device, Copilot SSHes in and captures `show inventory`, `show interface status`, current PoE budget, uplink configuration, VLAN list, and the AAA configuration. The replacement BOM has to match what's actually installed, not what was ordered three years ago.
  </Step>

  <Step title="Generate the replacement BOM">
    Copilot drafts the BOM as a Markdown table: model, accessories, transceivers (matched to the existing fiber types), power cords, rack ears, smartnet term, and a per-site quantity. Reviewed and approved by the account engineer.
  </Step>

  <Step title="Request quotes from three distributors">
    Through the distributor connectors, request stock and price for the BOM. Two come back same-day. The third needs a manual follow-up email — Copilot drafts it through Gmail.
  </Step>

  <Step title="Build the customer proposal">
    The proposal artifact bundles the EOL evidence, the BOM, the three quotes, recommended distributor, lead time, install labor, and the proposed maintenance window. Sent through Gmail with a one-page Markdown summary at the top.
  </Step>

  <Step title="Customer approval and PO">
    Customer replies with approval and a PO. Copilot files the PO into the PSA opportunity, marks it Won, and creates the project with the install tasks pre-populated.
  </Step>

  <Step title="Place the order and track the shipment">
    The distributor connector places the order. The shipment tracking number lands in the PSA project. Copilot watches the FedEx connector and posts updates to the project as the gear moves.
  </Step>

  <Step title="Schedule the install">
    Once delivery is confirmed, Copilot opens a Google Calendar event for the maintenance window, books the field tech, attaches the install runbook, and sends the customer the maintenance notice email through Gmail with the contact tree.
  </Step>

  <Step title="Pre-stage the new switch configs">
    Before the window, Copilot generates each new switch's config from the captured old-switch state, validates it against the customer's standards, and stores it in the project for the field tech to push from the console port.
  </Step>
</Steps>

## Where Studio earns its keep

* The replacement BOM is built from the actual current state of each device, not a guess from a procurement spreadsheet.
* Three distributors are quoted in parallel and the results land beside each other for a clean side-by-side decision.
* The customer proposal, the PO, the shipment, the install schedule, and the pre-staged configs all carry the same project ID end to end.
* Field-tech day one is opening the new switch with a known-good config sitting in the project, not improvising at 2 a.m.

## Related

<CardGroup cols={2}>
  <Card title="Connectors and MCP" icon="plug" href="../../connectors-and-mcp" arrow="true" cta="Add connectors">
    Distributor APIs, FedEx tracking, and Gmail are all connector calls.
  </Card>

  <Card title="Procedures" icon="workflow" href="../../procedures" arrow="true" cta="Standardize installs">
    Save the install runbook so the next refresh project drops in cleanly.
  </Card>
</CardGroup>