<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://akhilinturi.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://akhilinturi.com/" rel="alternate" type="text/html" /><updated>2026-10-09T18:39:01+00:00</updated><id>https://akhilinturi.com/feed.xml</id><title type="html">Akhil Inturi</title><subtitle>Data Center Connectivity Engineer in Irving, TX. Notes on hyperscale fiber, networking, career, and life.</subtitle><author><name>Akhil Inturi</name></author><entry><title type="html">Why I built a fiber link health monitor</title><link href="https://akhilinturi.com/blog/2026/10/building-a-fiber-link-health-monitor/" rel="alternate" type="text/html" title="Why I built a fiber link health monitor" /><published>2026-10-06T13:20:00+00:00</published><updated>2026-10-06T13:20:00+00:00</updated><id>https://akhilinturi.com/blog/2026/10/building-a-fiber-link-health-monitor</id><content type="html" xml:base="https://akhilinturi.com/blog/2026/10/building-a-fiber-link-health-monitor/"><![CDATA[<p>During cluster turn-up, a lot of test data gets generated and a lot of it sits in exported files. I wanted a faster way to see which links were failing, and where loss was trending the wrong way, at the rack and site level.</p>

<h2 id="what-it-does">What it does</h2>

<p>The <a href="https://github.com/AInturi18/fiber-monitor">Fiber Link Health Monitor</a> is a small pipeline that:</p>

<ol>
  <li><strong>Ingests OTDR exports</strong></li>
  <li><strong>Classifies each link</strong> as pass or fail against loss thresholds</li>
  <li><strong>Flags failing links and loss trends</strong> on a dashboard</li>
</ol>

<h2 id="the-stack">The stack</h2>

<ul>
  <li><strong>Python</strong> for parsing and classification</li>
  <li><strong>SQLite</strong> for storing results</li>
  <li><strong>Flask</strong> for the API</li>
  <li><strong>React.js</strong> for the dashboard</li>
</ul>

<h2 id="why-it-matters">Why it matters</h2>

<p>In high-density builds, the question is rarely “did we test it?” It’s “which of these hundreds of links needs attention right now?” A dashboard that answers that at a glance saves time during turn-up.</p>

<p><em>I’ll write a deeper walkthrough of how it works in a future post.</em></p>]]></content><author><name>Akhil Inturi</name></author><category term="Projects" /><summary type="html"><![CDATA[Turning OTDR exports into a pass/fail dashboard with Python, Flask, SQLite, and React.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://akhilinturi.com/images/covers/dashboard.svg" /><media:content medium="image" url="https://akhilinturi.com/images/covers/dashboard.svg" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">What 150+ hyperscale deployments taught me about clean turnover</title><link href="https://akhilinturi.com/blog/2026/10/lessons-from-150-hyperscale-deployments/" rel="alternate" type="text/html" title="What 150+ hyperscale deployments taught me about clean turnover" /><published>2026-10-06T13:10:00+00:00</published><updated>2026-10-06T13:10:00+00:00</updated><id>https://akhilinturi.com/blog/2026/10/lessons-from-150-hyperscale-deployments</id><content type="html" xml:base="https://akhilinturi.com/blog/2026/10/lessons-from-150-hyperscale-deployments/"><![CDATA[<p>Over 150+ Meta hyperscale deployments, the goal at the end of every site is the same: hand it to the NOC with zero defects. Here’s what I’ve learned about getting there.</p>

<h2 id="1-catch-problems-on-paper-first">1. Catch problems on paper first</h2>

<p>The cheapest fix is the one made before anything is installed. I review the BOM and EDP against the design before work starts, and I adjust cabling layouts and patch panel assignments while they’re still just lines on a page.</p>

<h2 id="2-test-everything-against-the-loss-budget">2. Test everything against the loss budget</h2>

<p>Each site has hundreds of endpoints to validate: singlemode, multimode, MPO, AOC/DAC, and copper. A link that “lights up” isn’t the same as a link that passes. OTDR traces, light meter readings, and insertion and return loss numbers tell you whether it will hold up.</p>

<h2 id="3-write-the-procedure-down">3. Write the procedure down</h2>

<p>When several sites are running at once, consistency comes from MOPs and SOPs, not memory. Written procedures aligned with TIA-568, BICSI, and NEC mean every crew installs, tests, and cuts over the same way.</p>

<h2 id="4-photos-settle-arguments">4. Photos settle arguments</h2>

<p>When an installation has a deficiency, a pre/post photo package makes it clear what was wrong and that it was fixed. It keeps vendor follow-ups short and objective.</p>

<h2 id="5-as-builts-are-part-of-the-job">5. As-builts are part of the job</h2>

<p>The site isn’t done until the documentation matches what’s physically there. Accurate as-builts and turnover packages are what the next team relies on.</p>

<hr />

<p><em>More field notes coming. If you work in data center connectivity, I’d like to hear what’s worked for you.</em></p>]]></content><author><name>Akhil Inturi</name></author><category term="Data Center" /><summary type="html"><![CDATA[The habits that keep a data center connectivity build on track from EDP review to NOC sign-off.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://akhilinturi.com/images/covers/racks.svg" /><media:content medium="image" url="https://akhilinturi.com/images/covers/racks.svg" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Hello, world: why I started this site</title><link href="https://akhilinturi.com/blog/2026/10/hello-world/" rel="alternate" type="text/html" title="Hello, world: why I started this site" /><published>2026-10-06T13:00:00+00:00</published><updated>2026-10-06T13:00:00+00:00</updated><id>https://akhilinturi.com/blog/2026/10/hello-world</id><content type="html" xml:base="https://akhilinturi.com/blog/2026/10/hello-world/"><![CDATA[<p>I’m Akhil, a data center connectivity engineer based in Irving, TX. Since January 2023 I’ve worked on Meta hyperscale data center deployments, testing, validating, and documenting the fiber that connects everything inside these buildings.</p>

<p>I started this site for two reasons. I wanted one place where my resume, projects, and writing live together. And a lot of what I learn in the field never gets written down anywhere, so this is where I’ll put it.</p>

<h2 id="what-ill-write-about">What I’ll write about</h2>

<ul>
  <li><strong>Data center &amp; fiber:</strong> field lessons from deployments, testing, and turnover</li>
  <li><strong>Networking &amp; certifications:</strong> CCNA notes, the ANSI certification I’m working on, and lab work</li>
  <li><strong>Projects:</strong> tools I build, like my fiber link health monitor</li>
  <li><strong>Career:</strong> what I’m learning as I grow toward systems and connectivity engineering</li>
  <li><strong>Life &amp; updates:</strong> everything else</li>
</ul>

<p>If any of that sounds interesting, check back, or <a href="https://www.linkedin.com/in/akhil-inturi-b5ba2619a/">connect with me on LinkedIn</a>.</p>]]></content><author><name>Akhil Inturi</name></author><category term="Updates" /><summary type="html"><![CDATA[A quick intro to who I am, what I do in hyperscale data centers, and what I'll be writing about here.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://akhilinturi.com/images/covers/hello.svg" /><media:content medium="image" url="https://akhilinturi.com/images/covers/hello.svg" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">I graduated: Master’s in Technology Management</title><link href="https://akhilinturi.com/blog/2025/01/graduated-masters-lindsey-wilson/" rel="alternate" type="text/html" title="I graduated: Master’s in Technology Management" /><published>2025-01-31T15:00:00+00:00</published><updated>2025-01-31T15:00:00+00:00</updated><id>https://akhilinturi.com/blog/2025/01/graduated-masters-lindsey-wilson</id><content type="html" xml:base="https://akhilinturi.com/blog/2025/01/graduated-masters-lindsey-wilson/"><![CDATA[<p>I am thrilled to share that I have officially graduated from Lindsey Wilson College with a Master’s in Technology Management! This journey has been filled with learning, challenges, and incredible growth, and I am grateful for all the knowledge and experiences I’ve gained along the way.</p>

<p>A big thank you to my professors, mentors, friends, and family who have supported me throughout this journey. This achievement is just the beginning, and I am excited for the opportunities ahead!</p>

<p><img src="/images/graduation-2.jpg" alt="Akhil in a suit on the Lindsey Wilson College campus" /></p>

<p><em>Originally posted on <a href="https://www.linkedin.com/feed/update/urn:li:activity:7291209583220428800/">LinkedIn</a>.</em></p>]]></content><author><name>Akhil Inturi</name></author><category term="Life" /><summary type="html"><![CDATA[Officially graduated from Lindsey Wilson College with my Master's.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://akhilinturi.com/images/graduation-1.jpg" /><media:content medium="image" url="https://akhilinturi.com/images/graduation-1.jpg" xmlns:media="http://search.yahoo.com/mrss/" /></entry></feed>