On 4/25/18 6:27 AM, pete M wrote:

Thanks Brian for the head up. But please dont give you such short time latitude to make the switch.

I used to do service maintenance in security system ( access control and camera system integration was my principal stuff) And when upgrading a site I always gave me 4 time the usual time I needed. Let say I planned to do the work in 15 minute, I would always advice the user that it would take 1 hours, maybe a bit more..

My user where always happy to see the job done in much less time or just in time when something went wrong ;-)

this help a lot to manage the expectation of the user.

There is notthing more exasperating to manage then a mid executive asking, is it done yet? when you work on a technical problem.

That's the Montgomery Scott rule of engineering. Double your time estimate, then when you pull it off in less time, the Captain sees you as a miracle worker.

I don't like to lie to clients. Moving a connector should only take a few minutes.

However, if they blew it on transferring the configuration from the old switch/router to the new one, it could take hours to get it fixed while they troubleshoot it. Thus there is no way to give a reasonable window and then beat it; any estimate that you're guaranteed to come in under would be several hours.

If you tell people hours and it then only takes a few minutes, you still get people bothering you with "is it done yet?" because they didn't even see the interruption and were expecting to be down for hours.

If there's one lesson I've learned in 30+ years of running networks, it's that you can't win in this game. - Brian

On Wed, Apr 25, 2018 at 01:27:45PM +0000, pete M wrote:

Thanks Brian for the head up. But please dont give you such short time latitude to make the switch.

I used to do service maintenance in security system ( access control and camera system integration was my principal stuff) And when upgrading a site I always gave me 4 time the usual time I needed. Let say I planned to do the work in 15 minute, I would always advice the user that it would take 1 hours, maybe a bit more..

My user where always happy to see the job done in much less time or just in time when something went wrong ;-)

this help a lot to manage the expectation of the user.

There is notthing more exasperating to manage then a mid executive asking, is it done yet? when you work on a technical problem.

Amen Brian!

On Wed 25 Apr 2018, 14:51 Brian Kantor, Brian@bkantor.net wrote:

I don't like to lie to clients. Moving a connector should only take a few minutes.

However, if they blew it on transferring the configuration from the old switch/router to the new one, it could take hours to get it fixed while they troubleshoot it. Thus there is no way to give a reasonable window and then beat it; any estimate that you're guaranteed to come in under would be several hours.

If you tell people hours and it then only takes a few minutes, you still get people bothering you with "is it done yet?" because they didn't even see the interruption and were expecting to be down for hours.

If there's one lesson I've learned in 30+ years of running networks, it's that you can't win in this game. - Brian

On Wed, Apr 25, 2018 at 01:27:45PM +0000, pete M wrote:

...

Thanks Brian for the head up. But please dont give you such short time

latitude to make the switch.

...

I used to do service maintenance in security system ( access control and

camera system integration was my principal stuff) And when upgrading a site I always gave me 4 time the usual time I needed. Let say I planned to do the work in 15 minute, I would always advice the user that it would take 1 hours, maybe a bit more..

...

My user where always happy to see the job done in much less time or just

in time when something went wrong ;-)

...

this help a lot to manage the expectation of the user.

There is notthing more exasperating to manage then a mid executive

asking, is it done yet? when you work on a technical problem. _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

As of 1:30 am Pacific time (GMT -7:00), everything is working again. - Brian

On Thu, Apr 26, 2018 at 08:39:47PM -0700, Brian Kantor wrote:

The network equipment changeout at UCSD did NOT go well; they are still having problems with the network 44 routing into UCSD. There is yet no estimated time to repair at this moment. I'll update you folks as I learn more.

• Brian

On Wed, Apr 25, 2018 at 05:47:15AM -0700, Brian Kantor wrote:

...

UCSD is swapping out some networking equipment and amprgw (aka gw.ampr.org, 44.0.0.1) will be unreachable for a while starting around 7pm Pacific time Thursday (tomorrow). It should take only a few minutes, but as both the connection and configuration have to be transferred to the new equipment, there is always the possibility that it will take longer or something else may go wrong.

• Brian