25 Apr
2018
25 Apr
'18
1:47 p.m.
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
25 Apr
25 Apr
1:53 p.m.
Thank you.
On Apr 25, 2018, at 07:49, Brian Kantor
<Brian(a)BKantor.net> 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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2:01 p.m.
Thank U Brian for all the help and info in advance !!!
________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)mailman.ampr.org> on behalf of Brian
Kantor <Brian(a)BKantor.net>
Sent: Wednesday, April 25, 2018 5:47 AM
To: 44net(a)mailman.ampr.org
Subject: [44net] GW (amprgw, gw.ampr.org) downtime tomorrow evening
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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2:27 p.m.
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.
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de Brian
Kantor <Brian(a)BKantor.net>
Envoyé : 25 avril 2018 08:47
À : 44net(a)mailman.ampr.org
Objet : [44net] GW (amprgw, gw.ampr.org) downtime tomorrow evening
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
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2:31 p.m.
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.
2:33 p.m.
And you keep your sanity in shape 😉
Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows
10
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de James
Sharp <james(a)fivecats.org>
Envoyé : Wednesday, April 25, 2018 9:31:01 AM
À : 44net(a)mailman.ampr.org
Objet : Re: [44net] GW (amprgw, gw.ampr.org) downtime tomorrow evening
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.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2:49 p.m.
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.
3:02 p.m.
It is not lying. It is managing expectency.
If it takes minute, and they did not noticed the change..
Just say that you managed well and there was no bug at all in the switching.
Tada, you are a very good planner and know your stuff.. It takes 10 minute.. you are still
very good and can fix everything 😉
Remember any sufficiently advanced technology is indistinguishable from magic. And someone
that can manage that technology is a mage! 😉
Provenance : Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows
10
________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de Brian
Kantor <Brian(a)BKantor.net>
Envoyé : Wednesday, April 25, 2018 9:49:52 AM
À : AMPRNet working group
Objet : Re: [44net] GW (amprgw, gw.ampr.org) downtime tomorrow evening
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(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
3:03 p.m.
Amen Brian!
On Wed 25 Apr 2018, 14:51 Brian Kantor, <Brian(a)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(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
27 Apr
27 Apr
4:39 a.m.
New subject: GW (amprgw, gw.ampr.org) downtime
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
9:37 a.m.
New subject: GW (amprgw, gw.ampr.org) downtime
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
>
10:08 a.m.
New subject: GW (amprgw, gw.ampr.org) downtime
Thanks for everything you do for us Brian and for making sure everything keeps working as
expected.
I don't think you get credit enough for everything you do to keep AMPRNet running and
healthy
73,
Ruben - ON3RVH
-----Original Message-----
From: 44Net <44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org> On Behalf Of Brian
Kantor
Sent: vrijdag 27 april 2018 10:37
To: 44net(a)mailman.ampr.org
Subject: Re: [44net] GW (amprgw, gw.ampr.org) downtime
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
>
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2193
days inactive
2195
days old
11 comments
7 participants
participants (7)
-
Brian Kantor -
James Sharp -
John Ricketts -
John Ronan -
pete M -
R P -
Ruben ON3RVH