ok....

yesterday, in a word, SUCKED.

i have a bat phone

at least that's what i refer to our new VOIP phones. we've only handed a limited number out to people, but we continue to work on getting the background stuff installed. and today, JD was doing a few things to some of the switches. and the network blew up.

literally, blew up.

died.

crashed and burned.

pushed up daisies.

worm food.

it SUCKED.

and how. our ENTIRE network was down for just over 3 hours. and THEN it had to come down for nearly 2 hours in the evening. at least that time it was a little more expected. we were able to let users know that the network was possibly going to go down. it didn't at first, but then it did.

there are apparently some loops that needed to be addressed, and JD seems to think that our little power-over-ethernet thing that powers the WHOLLY INDEPENDENT access points was causing problems.

i don't think so, but i was getting tired and frustrated so i let it drop for the moment. the good news is we could plug them into the p-o-e switches the phones use, so he did that which seemed to make him happy. unfortunately, the customer (in this case, ME) was not happy. i'll chat with my boss about it.

do we have issues with the wiring at work? hell yeah. and as it will be falling more and more into my domain, i'll do what i can to not only sort it out, but fix it, and document it. that's something we are sorely lacking, so that will be on my list of to-do's.

at least RB was back. altho he stepped in it first thing. he had to image and prepare to deploy by end of day (he was originally told tuesday, but that changed) 10 new PCs. fortunately, the new switches allow him to ghost the PCs pretty quickly, but it's still a pain in the ass. so he stayed late. i didn't leave until nearly 730, but it was nice to get out of there. even if it was overcast, and near dark under some clouds.