PCIe Hardware Topology

[ParishrutB]

Use Case

As a PE/Admin/SSR, I need to troubleshoot the connection problems so that I can fix issues with cabling and connectivity between servers and expansion drawers.

Design Review Workflow

1. Each design iteration will have a comment section
2. The section will include:
   • A title with the iteration number
   • Any description or specific feedback the designer is requesting
   • Screenshots of the workflow
3. Based on community and user feedback, we create a comment for the new iteration and repeat these steps

[ParishrutB]

Iteration 1

In the first iteration, we have made 2 concepts A and B. Both of them are being tested with internal users and experts. So far, 2/3 users have found Concept A sufficiently usable while they all preferred Concept B as it showed the I/O slots on the main rows rather than hiding them inside the expansion rows.

Concept A

Main screen

Expansion row details

Identify LEDs for a particular link ID

Reset link

Filter

---

Concept B

Other than the I/O slots being shown on the main rows, everything else is the same.

Main screen

Expansion row

[ParishrutB]

Questions to the community:

• Is this useful for you?
• Are there any details that are not shown by your systems?

What the copy be for the following:

• Link ID (may also be known as Bus ID)
• Local port , remote port

[samerhaj]

Can the location strings be customized to use implementation specific terminology?

Some implementations may prefer mappings to user serviceable location strings, using common terminologies such as slot, port, bay, riser, front/back, top/bottom, etc.. This is also consistent with the Redfish PhysicalContext schema which is used to describe components locations: https://redfish.dmtf.org/schemas/v1/PhysicalContext_v1.xml