[188579] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Best practices for sending network maintenance notifications

daemon@ATHENA.MIT.EDU (Sean Donelan)
Wed Apr 6 16:52:43 2016

X-Original-To: nanog@nanog.org
Date: Wed, 6 Apr 2016 16:52:39 -0400 (EDT)
From: Sean Donelan <sean@donelan.com>
To: nanog@nanog.org
In-Reply-To: <alpine.BSF.2.00.1604061144160.78400@prime.gushi.org>
Errors-To: nanog-bounces@nanog.org

On Wed, 6 Apr 2016, Dan Mahoney, System Admin wrote:
> My question for the group -- does anyone know if there's a "best practices" 
> for sending maint notifications like this?  An RFC sort of thing?

It falls in the category of "Doctor, it hurts when I do this.  Don't do 
that."  Even the most dense CSR managers figure it out after a few 
attempts.

The other "don't do that" is never configure Music on Hold for any NOC/SOC
lines.  Few things are more annoying than a eight hour trouble shooting 
conference bridge, and one of the dozen NOC/SOCs on the bridge hits
the Hold button.

home help back first fref pref prev next nref lref last post