Printable View
Does SW manage/monitor via snmp polling or what?
Tool config seems to be a problem regardless of the vendor. Our Network Defense guys have certain tools that, in combo with their conspiratorial mindset, causes them to freak out over nothing. We have had it in the past where our Network Monitoring Tools team hasn't updated our tool and so we have to scramble, only to find out nothing is wrong and they didn't do something right (if at all) when a change happens.
Never had a problem with their service, but I have had plenty of fun over the years with their billing [hahhah-no]
Tools usually aren't the problem. It's how people define them and configure them that's usually the problem. I've seen very intelligent tools after the monkey-in-the-middle rips all of the intelligence out of it.
...only to have a new tool brought in to resolve the shortcomings of the previous and get morphed right back into the same garbage you had before. Repeat.
Well, that certainly explains a lot. I thought it was just us.
May have spoke too soon, it started getting really slow shortly after I posted it was fine.Quote:
Originally Posted by hurley842002
Our entire Corp infrastructure was hit hard yesterday (HQ in Albuquerque). With bulk of the workforce out of the office, the OWA was down, and the remote VPN was overloaded.
I work for CTL in the NOC center, and it's been causing havoc and ulcers for a lot of people - but not me, fortunately, this is a hardware issue, not a fiber cut. Apparently a card (circuit pack) went haywire somewhere in the US and it affected comms to all nodes nationwide of the same manufacturer. NOC had no visibility to that network, so pinpointing the source has been a nightmare. Glad I'm not a field tech anymore!
Super irritating lag here the last few days. Recurring periods of ten minutes of channel, mixed with two minutes of buffering.
Great during a movie OR anything live.
This aligns with what we were hearing on the bridge.Quote:
Originally Posted by rondog
Per what we heard: Essentially your core architecture was engaging in behavior similar to a broadcast storm (but not a broadcast storm), spiking CPU usage on devices, failing over to another set of devices, rinse repeat.
Sounds like your vendor for hardware ain't sure why it did this either.
Any word on speculation of a virus geared toward the hardware itself to cause this behavior or just a pure hardware malady? Based on what I was hearing, it sounds distributed to your entire core, which makes a pure hardware issue highly odd.
Still no 911 service in many areas up here including where we are.