Re: provider email maintenance standard

2019-08-14 Thread Andrew Dampf
I ended up writing a flask app that parses provider maintenance emails and
posts slack notifications at the start and end of the window. You can also
extend it to take actions like drain/undrain traffic during windows. Right
now the five supported providers are NTT, PacketFabric, EUNetworks, GTT,
and Zayo. The first three follow the MAINTNOTE standard. The last two were
done via bs4 and good old regex. Upcoming parsers are in the works for
Reliance, CenturyLink, and Tata.

I hope others find this useful and deploy it for their networks. Let me
know what you think and if you'd like to contribute:

Here are some screencaps:

If you know of more providers that follow the MAINTNOTE standard, please
let me know so I can add them to the parser. Thanks!

On Tue, Jun 18, 2019 at 12:38 PM Erik Sundberg 

> Back at NANOG in Chicago 2016 someone was working on a standards for
> Maintenance notifications with calendar invites attached. Not sure what
> happened with it.
> I think this was it.
> Erik Sundberg
> Sr. Network Engineer
> office 773.661.5532
> mobile   708.710.7419
> noc 866.892.0915
> 888.450.2100
> 350 N Orleans St. #1300N
> Chicago, IL 60654
> Smarter technology made simple
> -Original Message-
> From: NANOG  On Behalf Of Jay Hanke
> Sent: Tuesday, June 18, 2019 8:41 AM
> To: Job Snijders 
> Cc: North American Network Operators' Group 
> Subject: Re: provider email maintenance standard
> >
> >
> > NTT / AS 2914’s NOC follows this process to keep customers and partners
> informed about maintenances.
> Is there commercial or open source software that already has this
> implemented?
> CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files
> or previous e-mail messages attached to it may contain confidential
> information that is legally privileged. If you are not the intended
> recipient, or a person responsible for delivering it to the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution or use of any of the information contained in or attached to
> this transmission is STRICTLY PROHIBITED. If you have received this
> transmission in error please notify the sender immediately by replying to
> this e-mail. You must destroy the original transmission and its attachments
> without reading or saving in any manner. Thank you.

provider email maintenance standard

2019-06-17 Thread Andrew Dampf
Hello nanog,

I've heard second-hand there is an existing standard for provider
maintenance emails that should be followed in the form of a calendar
attachment, but I can't seem to find any information on it. Can anyone help
me with the following:

1. Does this standard exist? If so, is there somewhere I can read more
about it?
2. How many providers follow this standard?


Re: Templating/automating configuration

2017-06-07 Thread Andrew Dampf
Salt is great for generating configs based on jinja templates, and you can
use napalm in conjunction with salt to push the configs to the device on a
set schedule (typically this is done hourly). If manual changes are made to
the router, salt would override them on the next run, so it's a great way
to make sure configs are consistent.

On Tue, Jun 6, 2017 at 9:25 AM Graham Johnston 

> Short of complete SDN, for those of you that have some degree of
> configuration templating and/or automation tools what is it that you run?
> I'm envisioning some sort of tool that let's me define template snippets of
> configuration and aids in their deployment to devices. I'm okay doing the
> heaving lifting in defining everything, I'm just looking for the tool that
> stitches it together and hopefully makes things a little less error prone
> for those who aren't as adept.
> Graham Johnston
> Network Planner
> Westman Communications Group
> 204.717.2829 <(204)%20717-2829>

Re: Smokeping targets

2016-01-07 Thread Andrew Dampf
Something I found that is helpful once you've gathered a list of targets is
the following command for generating config to paste:

traceroute -w 3 [IPaddress] | grep -v "*" | grep -v "traceroute" | sed -e
's/(//g' -e 's/)//g' | awk '{ gsub(/\./,"_",$2); print " "$2"\nmenu =
"$3"\ntitle = "$2" - "$3"\nhost = "$3"\n"}'

That generates a valid output for configs to ping each hop along the way to
your destination, which can be super useful. Not all of them allow ICMP but
a decent amount do.

On Thu, Jan 7, 2016 at 10:34 AM, Brian R. Swan  wrote:

> Hi all,
> I’m setting up smokeping to try and gather some latency statistics on my
> ISP to different parts of the world.  Does there exist a list or any
> generic recommendations of different targets to config within smokeping?
> Google and searching the NANOG mailing list have failed me, and I don’t
> want to just spam random IP addresses with ICMP requests if there’s a more
> official/accepted method for doing this.
> Thanks!
> Brian

Level 3 contact

2016-01-02 Thread Andrew Dampf
Would an engineer from Level 3 please contact me off list? Thank you.