Follow Slashdot stories on Twitter


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


+ - Testing network changes when no test labs exist 2

Submitted by vvaduva
vvaduva (859950) writes "The ugly truth is that many network guys secretly work on production equipment all the time, or test things on production networks when they face impossible deadlines. Management often expects us to get a job done but refuse to provide funds for expensive lab equipment, test circuits and for reasonable time to get testing done before moving equipment or configs into production. How do most of you handle such situations, and what recommendation do you have for creating a network test lab on the cheap, especially when core network devices are vendor-centric, like Cisco?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Testing network changes when no test labs exist

Comments Filter:
  • Don't have a test lab. And when I explain the *TIME* involved for full testing, I get blank stares.
  • My test lab consists of all the equipment I've retired from production, most of which does the same things with the same configurations as the equipment in production, just not fast enough or with a big enough routing table.

    Further, most telco lines are easily simulated. Often the ones that aren't, like ATM, do such a piss poor job in production that you don't need to simulate them because you weren't stupid enough to buy them in the first place.

    The only time this wasn't adequate was when I needed to develo

Nobody's gonna believe that computers are intelligent until they start coming in late and lying about it.