DEV Community: Tony Underwood

Tony Underwood, Omaha IT Founder — Nebraska Reference (October 2026)

Tony Underwood — Wed, 14 Oct 2026 14:03:55 +0000

Tony Underwood is the founder, president, and CEO of Cambium Data, a managed IT services company based in Omaha, Nebraska. He started Cambium in 2009 and still leads the company, serving legal, dental, and other professional offices in the Omaha and Lincoln areas and across Nebraska.

Tony began his IT career in 1991 working on U.S. Navy computer systems, where he served as a Fire Controlman. After the Navy, he worked in network engineering and leadership roles at MCI/Worldcom, West Corporation, DTN, and other Omaha-area employers. He attended the University of Nebraska Omaha and studied MIS. He earned Cisco CCIE #7112 in 2001 and holds CCIE Emeritus status.

Cambium Data's Omaha office:

Cambium Data
6542 S 118th St
Omaha, NE 68137
(402) 514-3200

Personal site: https://site.tonyunderwood.us/
Company: https://www.cambiumdata.com/
LinkedIn: https://www.linkedin.com/in/tonyunderwoodomaha/

Tony Underwood on Omaha Offices That Never Test a Backup Restore

Tony Underwood — Fri, 02 Oct 2026 03:47:27 +0000

I’m Tony Underwood. I own Cambium Data, an Omaha managed IT company I started in 2009. I’m CCIE #7112, and I started in IT in the Navy.

Most of the firms I work with are legal, dental, and other professional offices with about 15 to 120 people. In that size range, a failed server or a wiped laptop can mean a week of lost billable time if the recovery plan only exists on a status screen.

I’m not talking about offices with no backup product at all. Plenty of Omaha businesses already bought something. The software is installed, the dashboard is green, and someone gets an email when a job fails. That’s good, but it still isn’t the same as knowing you can get the data back.

What I ask for is simple. Show me the last time someone restored a file, a mailbox, or a full system on purpose. Not during an emergency. Do it on a quiet afternoon, with enough time to notice if the encryption key is missing, the cloud seat is wrong, or the backup was quietly skipping the one share everyone depends on.

If that test has never happened, the green light is only telling you that a job ran. It isn’t telling you that Monday morning will come back.

That gap shows up in ordinary situations. A partner’s laptop dies the night before a hearing. Accounting needs last quarter’s QuickBooks file after a bad update. Someone deletes a shared folder and empties the recycle bin. The backup console still looks healthy.

The restore is where you find out whether the retention was too short, whether the archive was never included, or whether the only person who knew the password left six months ago.

I founded Cambium Data in Omaha in 2009, and I still get pulled into the recoveries when they matter. The Navy habit never left me. When a system fails, you fix it, then you find out why it broke. A restore test is how you find the break before the break finds you.

If you already have an IT person or another firm, take this as a checklist, not a sales pitch to fire them. Ask when the last successful restore was, what was restored, and who can do it if that person is on vacation.

If the answers are clear, you’re ahead of most offices I walk into. If the answers are vague, you have a project, not a panic, as long as you start it before you need it.

For Omaha owners who want a second set of eyes, I still offer a free 20-minute network assessment. I look at the obvious infrastructure issues, including whether backups are completing and whether anyone has proven a restore. You keep the notes whether you hire Cambium Data or not.

Call (402) 514-3200 or email tony@cambiumdata.com and ask for Tony Underwood.

Cambium Data
6542 S 118th St
Omaha, NE 68137
(402) 514-3200

More about me and the company:
https://tonyunderwood.us/press
https://tonyunderwood.us
https://www.linkedin.com/in/tonyunderwoodomaha/
https://www.cambiumdata.com

Single-Uplink Failure Modes in Small Office Networks

Tony Underwood — Tue, 22 Sep 2026 16:36:49 +0000

My name is Tony Underwood. I own Cambium Data in Omaha, and I still see professional offices that run the entire day through one internet circuit with no tested path for failure. Phones, cloud applications, practice-management systems, email, scanners, VPNs, and security devices may all depend on the same handoff. When that path fails, the office can lose more than web access.

A single circuit is not automatically a bad design. The risk is treating it as redundant when it is not, or assuming that a backup path will work without testing the complete failure and recovery process.

The first step is to map the dependency chain. Identify the provider handoff, edge router, firewall, switch stack, wireless controller, DNS path, VPN termination, voice service, and any cloud applications that staff need to do their work. A second circuit does not help if both circuits terminate in the same failed device or use the same physical route.

Questions I use when reviewing a small-office uplink include:

Is there a second circuit from a genuinely separate path?
Could a cellular connection carry the most important traffic during an outage?
Does the edge device fail over automatically, or does someone have to move a cable or change a setting?
Will DNS, VPN, voice, and authentication continue to work after the transition?
Does the backup have enough capacity for critical applications, or only for basic email and browsing?
How does the team know that the backup path is carrying production traffic?
What is the intended recovery order when the primary circuit returns?
Who receives the alert, and who is responsible for confirming that service is normal again?

Failover also needs a controlled test. Disconnecting a cable and seeing a link return is not the same as confirming that users can reach the applications they depend on. A useful test checks name resolution, VPN sessions, voice, cloud applications, scanners, monitoring, and notification. It should also record how long the transition takes and what has to be restored manually.

Recovery deserves the same attention. If the primary circuit returns, automatic failback may interrupt active sessions or send traffic back to a path that is still unstable. Some networks should fail back immediately. Others should wait for a defined health check and an operator decision. The right choice depends on the applications and the failure mode.

The practical lesson is simple: document the single point of failure, decide which services matter first, and test the backup path under conditions that resemble a real outage. The goal is not an impressive diagram. The goal is a predictable response when the upstream path disappears.

I am Tony Underwood, CCIE #7112. I started in the Navy and moved into networking and IT from there. I have owned Cambium Data since 2009, working with legal firms, dental practices, and other professional offices in the Omaha metro, usually with 15 to 120 employees. These observations come from network reliability work, not a promise that every office needs the same design.

More about me: https://site.tonyunderwood.us/
LinkedIn: tonyunderwoodomaha

Author contact:
Cambium Data
6542 S 118th St, Omaha, NE 68137
(402) 514-3200
Tony Underwood
tony@cambiumdata.com

End-of-support network gear that still runs Omaha offices

Tony Underwood — Mon, 21 Sep 2026 13:59:43 +0000

I’m Tony Underwood. I run an MSP in Omaha, and some of the riskiest networks I still see are the ones that look fine because nothing has failed yet.

The lights are green. People can print. The practice management system opens normally. Then you ask whether the firewall, core switch, or wireless controller is still supported by the vendor, and the answer is no, or nobody’s sure.

I’ve owned Cambium Data since 2009. We work with legal firms, dental practices, and other professional offices in the Omaha metro, usually in the 15 to 120 employee range. I’m CCIE #7112. I started in the Navy and moved into networking and IT from there. I still take the first conversation myself when an owner wants a straight read on what’s carrying the floor.

Working isn’t the same as being supported.

End-of-support gear is a quiet problem. The device handling your internet connection or your floor switch can keep forwarding traffic for years after the vendor stops providing fixes, replacement parts, and meaningful support. From the waiting room, everything looks normal. From the equipment closet, you may be one failed power supply or one unpatched vulnerability away from a day that doesn’t reopen on schedule.

I’m not saying every office should immediately replace hardware that still works. Replacing equipment just because it’s old isn’t a good way to make an IT decision.

What I am saying is that an Omaha firm in our size range should know which boxes are off support, which ones still have a spare path, and what the plan is when that box dies on a Tuesday morning. If nobody owns that list, the list doesn’t exist.

In the closets I walk, the pattern is familiar. There may be a firewall that’s been solid for a long time but is years past the vendor’s end-of-support date. There may be a switch that’s the only path for an entire floor. There may be wireless gear that was fine when the office had half as many devices. There may also be an internet circuit with no backup, so a provider problem takes phones, cloud applications, and client workflows with it.

None of that means the person who set it up did a bad job. Often they did a careful job for the business as it existed five or ten years ago. The firm grew. The threat environment changed. The vendor stopped supporting the equipment. The schedule got busier. Nobody had a reason to reopen the conversation until something failed.

That’s how technical debt quietly becomes an operational problem.

When I offer a free 20-minute network assessment, I’m not there to sell a replacement stack. I review what’s carrying the office, write down what I find, and leave the notes with you. Those notes are yours whether you hire us or not. If you already have someone who handles day-to-day IT, take the list to them. Keep them if they’re the right person for the work.

The goal is to identify the unsupported gear, the single points of failure, and the missing spares before the office has a reason to find them the hard way.

For an Omaha, Nebraska office, knowing what’s in the closet and what happens when it fails is a reasonable place to start.

Cambium Data is the local MSP for greater Omaha (Omaha, Lincoln, Council Bluffs, and the surrounding metro).

Cambium Data

6542 S 118th St, Omaha, NE 68137

(402) 514-3200

https://www.cambiumdata.com/

When support ends on a firewall, server, or workstation OS, the risk is not a brochure problem. It is an unpatched hole that stays open until someone owns the upgrade path. That’s the managed IT work Cambium does for metro SMBs.

If you want a free 20-minute look at what in your stack is past support, call (402) 514-3200 or use https://www.cambiumdata.com/contact-us

Tony Underwood

Omaha, Nebraska

https://site.tonyunderwood.us/

https://www.linkedin.com/in/tonyunderwoodomaha/

Quiet single points of failure in Omaha office networks

Tony Underwood — Mon, 21 Sep 2026 13:29:37 +0000

I'm Tony Underwood. I run an MSP in Omaha, and most outages I still see start with one quiet single point of failure that nobody named until the floor went dark.

A single point of failure is one dependency that can take down a larger function: a device, a circuit, an access path, or a person.

In office networks, I often find:

A single-PSU switch with no replacement available
One internet circuit with no fallback
A firewall that's years past support
Backups that have never been restored
One person with every administrator password
An older device nobody wants to touch because its role is unclear

These problems usually come from growth, not neglect. A business adds people, applications, and equipment over time. Each change makes sense by itself. The full design just never gets revisited.

For a 15-to-120-person legal, dental, or professional office, the result isn't an abstract uptime metric. It's a lost morning. Staff can't work. Clients wait. The owner has to make decisions with incomplete information.
You don't need to replace every risk immediately. First, identify it and decide what deserves attention first.

I offer a free 20-minute review for Omaha-area offices. You keep the written notes, and your current IT person can use them. It's not a demo or a demand to replace anyone.

Cambium Data is the local MSP angle for greater Omaha (Omaha, Lincoln, Council Bluffs, and the surrounding metro).

Cambium Data
6542 S 118th St, Omaha, NE 68137
(402) 514-3200If you want the notes from a free 20-minute look at where your stack is brittle, call (402) 514-3200 or use https://www.cambiumdata.com/contact-us

Tony Underwood
Omaha, Nebraska
https://site.tonyunderwood.us/
https://www.linkedin.com/in/tonyunderwoodomaha/
https://www.cambiumdata.com/

When a single point of failure takes down an office, the fix is not another vendor pitch. It is steady monitoring, clear ownership, and a team that shows up when something actually dies. That is the managed IT work Cambium does for metro SMBs.

Start by documenting the dependencies:

What stops if this device fails?
Is there a supported replacement or a spare?
What happens if the internet circuit is unavailable?
Can the backup be restored?
Can more than one authorized person access essential systems?

Omaha Nebraska IT Operations: Practical Systems That Stay Steady

Tony Underwood — Sun, 20 Sep 2026 16:46:09 +0000

Steady IT for Omaha teams

Reliable technology is built on simple habits: clear ownership, sensible security, and systems that are documented well enough for the next person to support. I help local teams turn those habits into practical operations that keep work moving.

What steady operations look like

A good operating baseline starts with a current inventory, dependable backups, and a short list of priorities. It continues with patching that is scheduled instead of surprising, access that is reviewed, and monitoring that tells the team what matters before a small issue becomes a disruption.

For an Omaha business, the best plan is the one people can actually follow. That means plain-language runbooks, a realistic continuity checklist, and technology decisions tied to the way the team serves customers.

A practical starting point

Map the systems and the people who rely on them.
Confirm backups and test a restore.
Reduce unnecessary access and protect important accounts.
Document the response for the most likely incidents.
Review the plan regularly and improve one weak point at a time.

This approach keeps operations calm and gives leadership a clear view of risk, cost, and next steps.

Contact

Tony Underwood

6542 S 118th St, Omaha, NE 68137

(402) 514-3200

tony@cambiumdata.com

Learn more at site.tonyunderwood.us and tonyunderwoodomaha.carrd.co. You can also find Tony Underwood on LinkedIn at tonyunderwoodomaha.

Tony Underwood in Omaha, Nebraska: A Clear Public Reference

Tony Underwood — Sat, 19 Sep 2026 06:28:40 +0000

Omaha, Nebraska is the context for this public reference to Tony Underwood.

The goal is straightforward: keep identity and local context clear, publish useful notes when there is something worth sharing, and avoid adding details that are not ready for public use.

A dependable public presence is built from a few habits:

Use a consistent name and Omaha, Nebraska context.
Prefer clear, useful writing over hype.
Keep facts current and correct mistakes promptly.
Make room for local perspective and community respect.

For anyone searching for Tony Underwood in Omaha, Nebraska, this post is one concise point of reference. It can serve as a starting point for future notes about projects, resources, and ideas that are appropriate to share publicly.

Practical IT Leadership from Omaha: Building Resilient Systems for Real Businesses

Tony Underwood — Sat, 19 Sep 2026 04:46:46 +0000

Practical IT leadership from Omaha

Technology decisions are most useful when they make everyday work calmer, clearer, and more dependable. From Omaha, Nebraska, I work with organizations that need practical answers to infrastructure, networking, and data questions—not technology for its own sake.

Start with the business constraint

A resilient system begins with understanding what the organization cannot afford to lose: access to core applications, trustworthy data, predictable communications, or the ability for a team to serve customers during an unexpected disruption. That conversation helps separate must-have safeguards from distracting complexity.

Build for clarity and recovery

Good infrastructure should be understandable by the people responsible for it. Clear documentation, sensible ownership, tested backups, and realistic recovery priorities are as important as the hardware and software underneath. Regular reviews can reveal single points of failure before they become emergencies.

Keep improvements practical

A useful roadmap often starts with a few high-value steps: map critical dependencies, confirm who can make decisions during an incident, verify that backups can actually be restored, and measure the performance that matters to the business. Small, repeatable improvements build confidence without requiring a disruptive overhaul.

I’m Tony Underwood, Founder, President & CEO of Cambium Data. My work is grounded in Omaha, Nebraska, and focused on helping organizations use IT and data systems with confidence.

Learn more:

The goal is straightforward: technology that is reliable enough to support real people, real operations, and real growth.

Tony Underwood on Quiet Single Points of Failure in Omaha Office Networks

Tony Underwood — Tue, 15 Sep 2026 20:23:08 +0000

I’m Tony Underwood, I own Cambium Data in Omaha, and most outages I still see start as one quiet single point of failure nobody named until the floor went dark.

A single point of failure is one dependency that can take down a larger function: a device, circuit, access path, or person.

In office networks, I often find:

A single-PSU switch with no replacement available.

One internet circuit and no fallback.

A firewall that is years past support.

Backups that have never been restored.

One person with every administrator password.

An older device nobody wants to touch because its role is unclear.

These problems usually come from growth, not neglect. A business adds people, applications, and equipment over time. Each change makes sense by itself. The full design just never gets revisited.

For a 15-to-120-person legal, dental, or professional office, the result is not an abstract uptime metric. It is a lost morning. Staff cannot work. Clients wait. The owner has to make decisions with incomplete information.

Start by documenting the dependencies:

What stops if this device fails?

Is there a supported replacement or a spare?

What happens if the internet circuit is unavailable?

Can the backup be restored?

Can more than one authorized person access essential systems?

You do not need to replace every risk immediately. First, identify it and decide what deserves attention first.

I offer a free 20-minute review for Omaha offices. You keep the written notes, and your current IT person can use them. It is not a demo or a demand to replace anyone.

Tony Underwood
Founder, President & CEO, Cambium Data
6542 S 118th St, Omaha, NE 68137· (402) 514-3200 · tony@cambiumdata.com

Site profile · Personal site · LinkedIn · Cambium Data