Man of Honour
- Joined
- 30 Jun 2005
- Posts
- 9,515
- Location
- London Town!
I try to run ip scans on the internal network to make sure there are no mistakes but realy difficult, any suggestions?
Do it properly? If it's actually meant to be secure then it's laughably poor as a solution, you should be using 802.1x port security as a minimum, if you did that then it doesn't matter if it's connected wrong accidentally (or maliciously) as it won't work.
If it isn't deserving of that much security then you may as well run them as seperate VLANs on the same switch (and possible enforce some basic port security) because having physically separate networks like that is strictly security theatre.
If you want to repatch then waiting for VOIP is an excuse though, yeah, non VOIP phones require repatching but that's not a problem if a) you tell people how it must be done and b) enforce dire consequences on those who don't. We do hundreds of repatches a month in our datacenters and the cabinets are still pristine, because people are given to understand that not following procedures for cabling (or anything else) is a disciplinary matter. If people can't take 2 minutes to get the right length cable and do it neatly you need new people to be honest...