← SSLOCSD

Clients/SSLOCSD/emails/.raw/2026/february/Re_SCADA_Network_VLAN_consult_4.md

gmail
Source
1
Chunks
4
Entities
Doc
Type

Content

Sounds good Kevin! This is a beautiful write-up, Mason. I'd agree that those are important security considerations, and that the network segmentation overall is worth doing. I'd feel more confident your solution will solve the problem if we can prove first that the latency experienced is being caused by aforementioned ARP broadcast. You mentioned the network may be experiencing a broadcast storm, this most commonly happens when a switching loop exists somewhere in the circuit (which Ethernet/IP I/O devices can inadvertently cause). Your document confirms that RSTP (Rapid Spanning Tree Protocol) is disabled on all ports. This protocol protects against Switching loops (which could very well be the cause of this latency issue). RTSP creates a loop-free logical topology, blocking redundant paths while allowing for rapid convergence. Did you guys happen to do a wireshark scan while onsite? This would give you the details on exactly what is going on (Packets Dropped, ARP Consistency, Etc.) Let me know your thoughts! *Chad Crawford* *Chief Technical Officer* SPICE Integration *805.464.4111* C-10 License: *1110179* California Small Business Certification ID: *2036507* On Thu, Feb 26, 2026 at 9:53 PM Kevin Seifert <kevin@autosysnet.com> wrote: > Chad, > > Mason worked up a highly detailed report and plan of attack for the [... earlier replies trimmed ...]

Extracted Entities

TypeKeyValueConfidenceEvidence
contact Chief Technical Officer Chad Crawford 90% Chad Crawford Chief Technical Officer SPICE Integration
contact phone number 805.464.4111 90% 805.464.4111
contact email kevin@autosysnet.com 90% Kevin Seifert <kevin@autosysnet.com>
site client name SSLOCSD 80% Client: SSLOCSD
File: Clients/SSLOCSD/emails/.raw/2026/february/Re_SCADA_Network_VLAN_consult_4.md
Updated: 2026-03-10 06:10:48.334156