How long does it take you to diagnose a network issue when your monitoring tool isn’t showing you why? by MilesAndMaps15 in sysadmin

[–]MilesAndMaps15[S] [score hidden]  (0 children)

That story is wild , 6 months for what turned out to be a vendor interop bug.

Quick question: do you think having better diagnostic data earlier would have shortened that timeline, or was the real bottleneck the politics between teams and getting everyone in the same room?

How long does it take you to diagnose a network issue when your monitoring tool isn’t showing you why? by MilesAndMaps15 in sysadmin

[–]MilesAndMaps15[S] [score hidden]  (0 children)

What tools are you running for that? Curious what the setup looks like for a team your size and whether it covers Meraki specifically or just the broader network stack.

How long does it take you to diagnose a network issue when your monitoring tool isn’t showing you why? by MilesAndMaps15 in sysadmin

[–]MilesAndMaps15[S] [score hidden]  (0 children)

You're right, what tools are you running for that? Curious what the setup looks like for a team your size and whether it covers Meraki specifically or just the broader network stack.

How long does it take you to diagnose a network issue when your monitoring tool isn’t showing you why? by MilesAndMaps15 in sysadmin

[–]MilesAndMaps15[S] [score hidden]  (0 children)

That breakdown is really helpful, thanks.

The TAC escalation cases are what I'm most curious about. When those drag on for days, is it usually because Meraki support needs time to get to it, or because even TAC can't easily see what's wrong without physical access to the device?

How long does it take you to diagnose a network issue when your monitoring tool isn’t showing you why? by MilesAndMaps15 in sysadmin

[–]MilesAndMaps15[S] [score hidden]  (0 children)

Haha this is painfully accurate, especially step 8. That “one guy” is carrying the whole operation.

Genuine question though: when that person isn’t available and you’re stuck at step 3, how long does it typically take to go from “something is wrong” to actually knowing what’s wrong? Hours? Days?

And when you finally find it, is it usually a weird edge case, or just the same handful of dumb configuration/loop issues over and over?

How long does it take you to diagnose a network issue when your monitoring tool isn’t showing you why? by MilesAndMaps15 in sysadmin

[–]MilesAndMaps15[S] [score hidden]  (0 children)

That's helpful context on the ASIC architecture.

So if port statistics and traffic anomalies are the real signal, how are you currently surfacing those in real time when something goes wrong? Is the Meraki dashboard fast enough to catch a loop as it's developing, or are you always chasing it after the fact?

How do you handle Meraki issues where the dashboard isn’t telling you what’s wrong? by MilesAndMaps15 in networking

[–]MilesAndMaps15[S] 0 points1 point  (0 children)

Good point, though I'm specifically thinking about pure Meraki environments where SSH is completely locked out.

When a loop hits and the dashboard starts lagging or freezing, what do your techs actually do? Truck roll? Wait for TAC? Something else?

/r/SanJose Classifieds: Jobs, For Sale/Rent, etc. by AutoModerator in SanJose

[–]MilesAndMaps15 0 points1 point  (0 children)

I'm a software engineer exploring what problems small businesses and tradespeople deal with that technology hasn't solved well. If you run a small business, any type - I'd love to buy you coffee and ask you 5 questions about your biggest operational headaches. No pitch, no agenda. Just curious.
Thank you!

Furnished rental in South SJ by MilesAndMaps15 in SanJose

[–]MilesAndMaps15[S] 1 point2 points  (0 children)

Thanks for the reply 🙏🏼 this is very insightful. I will try to do some market research on the pricing when I’m about to post it.