# Cisco Tech Stories - ep 36 - Smooth Sailing Network Overhaul

Page: https://stenobird.com/podcast/cisco-podcast-network-609546/cisco-tech-stories-ep-36-smooth-sailing-network-overhaul
Text version: https://stenobird.com/podcast/cisco-podcast-network-609546/cisco-tech-stories-ep-36-smooth-sailing-network-overhaul.md
Podcast: [Cisco Podcast Network](https://stenobird.com/podcast/cisco-podcast-network-609546)
Published: 2026-07-01T18:27:54+00:00
Episode link: https://soundcloud.com/ciscopodcastnetwork/cisco-tech-stories-ep-36
Audio file: http://dts.podtrac.com/redirect.mp3/feeds.soundcloud.com/stream/2351314982-ciscopodcastnetwork-cisco-tech-stories-ep-36.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/cisco-podcast-network-609546/episodes/cisco-tech-stories-ep-36-smooth-sailing-network-overhaul
Duration seconds: 2941

## Resource

In today's episode, Cisco CX engineers and architects reveal how cruise ship networks are built and upgraded: everything from door locks and cameras to navigation and guest entertainment runs over the same segmented, secured infrastructure, and internet connectivity depends on intermittent satellite links so content must be stored locally. We follow a high‑stakes dry dock upgrade on a large cruise ship — with tight timelines, complex staging, and on‑the‑fly design changes to handle issues like NAT, multicast/PTP, MTU and firewall integration — and learn how planning, testing and rapid problem‑solving kept the ship sailing.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/cisco-podcast-network-609546/episodes/cisco-tech-stories-ep-36-smooth-sailing-network-overhaul/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/cisco-podcast-network-609546/cisco-tech-stories-ep-36-smooth-sailing-network-overhaul.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.