Incident Library
Applied filters ComponentNetwork switchOrganisationDeNAClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    At about 20:00 on a weekday, one of DeNA's largest sites reported that terminals of a customer-facing system could not communicate and business was suffering. The network group's monitoring had raised no alert.

    Trigger

    During a routine change on 15 Cisco Catalyst 2960L access switches at the site, which tidied descriptions, added VLAN definitions and added allowed VLANs on trunk ports, `no switchport trunk allowed vlan` was applied to GigabitEthernet0/15 of switch SW3, only one of the two physical ports in the LACP bundle between SW3 and SW2.

    Root cause
    Component
    Contributing factor
    Detection

    The site reported the problem at about 20:00; no monitoring alert fired, because the affected port had no interface monitoring and LACP monitoring had been removed by an earlier monitoring change.

    Remediation
    • Rolled back the switch changes without knowing the cause; service recovered when the interface setting of one switch was restored
    • Found the faulty port and confirmed there was no other impact, completing the first response at about 22:00
    Action items
    • Fix the missing interface and LACP monitoring
    • Require a review for every monitoring change
    • Block merges to the alert rule repository without a reviewer's approval
    • Enable automatic AI review on pull requests
    • Announce every network change in advance, however minor
    • Agree the work date with the site's managers and avoid the site's event days
    • Prepare rollback procedures for high-impact maintenance and for work on several devices at once
    Lessons

    Any change can cause an outage, through a mistake, an unexpected event or a bug, so changes need to be scheduled with a maintenance window agreed in advance. A change on a downstream access switch can affect the whole site. Changing many devices at once made it slow both to find the faulty device and to roll back, and the parts that can be prevented by mechanisms rather than by people's care, such as reviews and monitoring, should be enforced that way.

Check your cluster for this

This case involves Network switch. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1