Decision Intelligence

VIPERInfrastructure

From the site to the port. And everything it depends on.

Keep location, equipment, connectivity and power together — from a national operational picture down to a single transceiver — with where each fact comes from, how current it is, and where a mapping is missing.

Open at the object Discuss a project
VIPERComponent · SW-01 Eth1/24
As of14 Oct 2026 · 11:04 UTC · Incident window · 10:05–10:35 UTC

From the site

Recorded location

  1. SiteNYC-01Harbor Operations Center
  2. BuildingBuilding BData hall
  3. RoomRoom 02Equipment room
  4. RowRow A
  5. RackR12
  6. DeviceSW-01Top-of-rack switch
  7. ModuleModule 1
  8. InterfaceEth1/24Input errors elevated 10:07–10:35
  9. TransceiverTX-24

And what it depends on

Recorded relationships

Network · recorded paths

Power · SW-01

  • PSU1 · Supply A → PDU-A · A01
  • PSU2 · Supply B → PDU-B · B01
Same PDUs as SRV-01, whose two paths converge on UPS-01

Services recorded on SW-01

  • SVC-01Records GatewayCritical
  • SVC-02Shift rosterHigh
  • SVC-03Field reports intakeStandard
  • SVC-04Internal directoryCritical
  • SVC-05Records archiveStandard

Synthetic presentation data

Building, rack and component

Open at the object.
Walk the chain when you need it.

The view opens at the component itself. The level explorer walks the same identity chain — site, building, room, row, rack, device, module, port and transceiver — and the rack turns from front to rear without renumbering a single label.

VIPERLocation and component
  • Situation
  • Network
  • Infrastructure
  • Investigations
As of14 Oct 2026 · 11:04 UTC

Rack R12 · Front

  4. 3U open
  6. 10U open
  11. 11U open

SW-01 · Front face

48 × SFP28 · 6 × QSFP28 · module 1

SW-01 · Eth1/24Attention · errors observed

Role
Primary uplink to SW-02 (recorded)
Module
Module 1 · 25 Gb/s · Up / up
Transceiver
TX-24 · SFP28 · 25GBASE-SR · SN SYN-TX-0024
Not collected in the incident window. Last reading 13 Oct 23:00, within range.
Cable
CBL-042 → PP-01 · P24
Far end (recorded)
SW-02 · Eth1/08

Observations

  • Input errors (CRC) elevatedOBS-0141 · 10:07–10:35 · MeasuredPeak 2,210 / 5 min · baseline ≤ 2
  • Link stayed up; no state changesOBS-0148 · 10:05–10:35 · Measured
  • Utilization within normal rangeOBS-0143 · 10:05–10:35 · Measured31–38 % of 25 Gb/s

Highlighting marks where evidence points. It is not a finding that this component is defective.

  • Front and rear, same identities

    Ports and bays on the front; supplies, management and zero-U PDUs on the rear. Printed labels are never mirrored.

  • Modules, ports, transceivers

    Every port, module, supply and outlet is selectable, with its role, its connection and the latest observations.

  • Only what is recorded

    Plans show recorded locations. Where a position or a cable has no record, the view says so.

Patch path and cable tracing

From the interface
to the far end.

Interface, transceiver, patch cable, panel ports, trunk channel and far end — each hop with its endpoints, its source and how it is known. Surveyed hops are drawn solid, documented-only hops dashed, and a segment nobody has mapped stays a gap.

VIPERRecorded path · Eth1/24
  • Situation
  • Network
  • Infrastructure
  • Investigations
As of14 Oct 2026 · 11:04 UTC

INC-024SVC-01 · Records Gateway

Incident window10:05–10:35 UTC

Select any hop for its endpoints, source and freshness. The primary stops at an unresolved segment into PP-02; the secondary carries a patch lead with no cable record.

Recorded path · Primary uplink

SW-01 Eth1/24 to SW-02 Eth1/08 through PP-01, TRUNK-07 channel 04 and PP-02.

  1. Row A · Rack R12

  2. Under-floor tray

  3. Row C · Rack R03

SurveyedDocumented onlyGap · no recordHighlighting marks where evidence points — it is not a finding.

InterfaceSW-01 · Eth1/24

Detail
Module 1 · SFP28 cage 24 · 25 Gb/s
Place
R12 · U40 · front
Endpoints
SW-01 module 1 ↔ TX-24
Source
Device inventory · COL-01
Basis
Surveyed 13 Oct
Freshness
Current · 11:02
Observed here
Input errors elevated 10:07–10:35 · OBS-0141

TraceRecorded to TRUNK-07 ch04. The segment into PP-02 is unresolved: LLDP names the far end, no record maps the route to it. Errors are observed at Eth1/24 only — no component on this path is established as the cause.

  • An unresolved segment, shown as one

    The primary uplink is recorded to TRUNK-07 channel 04. No record maps its rear position at PP-02: LLDP identifies the far end, not the route. The trace stops at what is known and marks the rest.

  • Documented or surveyed

    A record says where a cable should run; a survey confirms where it does. Each hop states which, with a date — and the secondary's unlabelled patch lead is marked as having no cable record.

  • A highlight is not a verdict

    Errors are measured at Eth1/24. Marking the hops beyond it says nothing about which component failed — that is for the investigation to establish, with the evidence it names.

Power dependencies

Two power paths.
One shared dependency.

Feed, UPS, PDU, outlet, cord and supply — followed past the rack where they are documented. See where separate paths converge and which services depend on them.

VIPERPower dependencies · SRV-01
  • Situation
  • Network
  • Infrastructure
  • Investigations
As of14 Oct 2026 · 11:04 UTC

Select a supply or outlet on the rack, or any node in the chain. Switch to the modeled outage to see what would be exposed — it is labelled as modeled throughout.

Rack R12 · rear

  4. 3U open
  6. 10U open
  11. 11U open

Power dependencies · SRV-01

Supply A

Supply B

Services depending on SRV-01

  • SVC-01Records GatewayNo power events
  • SVC-02Shift rosterNo power events
  • SVC-03Field reports intakeNo power events
Power supply
SRV-01 · PSU-A · 800 W · rear left
Observed
Normal · input present
Basis
Device-reported (BMC) · 11:02
Modeled outage
Input lost (modeled)

Relation to INC-024Not the cause of INC-024. Both supplies and UPS-01 reported normal throughout the incident window.

  • Separate to the panel

    Supply A and supply B run through their own cords, outlets, PDUs and breakers.

  • Shared at the UPS

    Both paths converge on UPS-01 and its feed — a dependency the rack alone does not show.

  • Observed, then modeled

    What the devices report stays apart from what a modeled outage would expose. The chain also states it is not the cause of the network incident.

Provenance and freshness

Where every fact comes from.
And what is missing.

Each hop and power element names its record or collector, how it is known and how current it is. Mappings that do not exist are listed with what they prevent and who can close them — never drawn in to make a path look complete.

VIPERProvenance · R12 · SW-01 Eth1/24
  • Situation
  • Network
  • Infrastructure
  • Investigations
As of14 Oct 2026 · 11:04 UTC

INC-024SVC-01 · Records Gateway

Incident window10:05–10:35 UTC

Recorded path · Primary uplink

SW-01 · Eth1/24 → SW-02 · Eth1/08

HopSourceBasisFreshness
SW-01 · Eth1/24R12 · U40 · frontDevice inventory · COL-01Surveyed 13 OctCurrent · 11:02
TX-24In SW-01 · Eth1/24Device inventory · COL-01Surveyed 13 OctStale · 13 Oct 23:00Optics last read 13 Oct 23:00
CBL-042R12 · front, via CM-01DCIM record · rev 14 (2 Sep)Surveyed 13 OctCurrent · 13 Oct 16:20Label verified on site
PP-01 · P24R12 · U42DCIM record · rev 14 (2 Sep)Surveyed 13 OctCurrent · 13 Oct 16:20
TRUNK-07 · ch04Under-floor tray, Row A → Row CDCIM record · rev 14 (2 Sep)DocumentedAging · 2 Sep 08:15Route recorded, not surveyed. End labels verified.
PP-02 · P08 ?R03 · U42No DCIM record for the rear position · inferred from LLDP neighbourGap · no recordNot observedSegment mapping unresolved
CBL-043R03 · frontDCIM record · rev 14 (2 Sep)Surveyed 13 OctCurrent · 13 Oct 16:20
SW-02 · Eth1/08R03 · U40 · frontDCIM record · rev 14 (2 Sep) · LLDP 10:38Surveyed 13 OctNot observedCounters outside VIPER collection scope

Power · SRV-01 supply A and shared

Device-reported, measured and recorded — kept apart

ElementObservedBasisAs of
SRV-01 · PSU-A800 W · rear leftNormal · input presentDevice-reported (BMC)11:02
CORD-A14C13–C14 · 1.5 mRecorded · surveyed 13 OctRecorded13 Oct 16:20
PDU-A · A14Outlet 14 · bank 2 · C13Not metered per outletPDU reports per-phase totals only—
PDU-AR12 rear left · 0U · 32 A6.2 A on L1Measured · per phase11:03
RPP-1 · CB-12Remote panel 1 · breaker 12 · 32 ARecordedRecorded2 Sep 08:15
UPS-01Room 02 · 80 kVA · double conversionOn mains · load 42 % · runtime estimate 17 min at current loadDevice-reported · vendor estimate11:03
FEED-1Utility feed 1 · via MSB-1PresentDevice-reported (UPS input)11:03

Missing mappings · 4

Shown as gaps — never drawn in

  • TRUNK-07 ch04 → PP-02 rear position

    Primary uplink · Row C, rack R03, U42

    LLDP names the far end; no record maps the route to it. The path is not traced end to end.

    Closed by Network records owner · NYC-01 (survey request)

  • Patch lead at PP-02 · P07

    Secondary uplink · front of R03

    The patch lead is still unlabelled. It stays a visible gap until a cable record exists.

    Closed by Network records owner · NYC-01 (cable record)

  • Per-outlet load on PDU-A A14 and PDU-B B14

    Rear of R12 · zero-U strips

    The PDUs report per-phase totals only, so an outlet’s draw is not observed.

    Closed by Facilities · metering decision

  • SW-02 · Eth1/08 counters

    Far end · outside VIPER collection scope

    Far-end errors cannot be compared with Eth1/24 until the counters are read.

    Closed by Network operations · requested in NV-024-1

Continue in VIPER.

Bring one real workflow to the evaluation.

Name the service, the environment and the workflow you want to examine. We scope the evaluation around them.

Discuss an evaluation Contact

Also seeVIPERDecision Intelligence