Hi GROW,
>From an operational perspective it is really useful if you can drop a
line in the peer's syslog which covers why you shutdown a BGP session.
A common use case is to provide a reference between the shutdown event
and an emailed maintenance notification, or maybe you want to make an
emotional statement.
Fictional IOS example:
o00.frnkge02.de.bb#conf t
Enter configuration commands, one per line. End with CNTL/Z.
o00.frnkge02.de.bb(config)#router bgp 65001
o00.frnkge02.de.bb(config-router)#neighbor 129.250.6.5 shutdown
"Maintenance [V-NOC-248244242] software upgrade o00.frnkge02.de.bb"
Fictional OpenBGPD example:
[job@kiera ~]$ bgpctl neighbor down AS15562_scarlett_IPv6 "I hate you,
depeered"
request processed
[job@kiera ~]$
In the above examples, the other side might find something like this in
their logs:
Nov 16 00:20:41 frankfurt-router 589711: RP/0/RSP0/CPU0:Nov 16
00:20:41.653 : bgp[1059]: %ROUTING-BGP-5-ADJCHANGE : neighbor X.Y.Z.A Down -
Peer closing down the session (VRF: default) (AS: 35994) (Shutdown
Communication: "Maintenance [V-NOC-248244242] software upgrade
o00.frnkge02.de.bb")
or perhaps:
Nov 16 06:59:50 herpaderp bgpd[99938]: neighbor 165.254.255.1
(AS15562_scarlett_IPv4): received notification: Cease, shutdown communication:
"I hate you, depeered"
Some might wonder, why "Cease"?
The beauty of using a new Cease subcode, is that the NOTIFICATION
message type already allows extra data to be attached, so for most
implementations it will be very simple to bolt what is specified in
draft-snijders-idr-shutdown-00 on top of their existing code. In some
cases we are looking at just a handful of lines.
Out of all the moments in the lifecycle of BGP interactions, I believe
that the 'shutdown' moment is the most critical one to decorate with
some freeform text. This is low hanging fruit and as should be treated
accordingly. There other moments where one might want to chat with the
neighbor, but those are out of scope for this document, you can always
call or email them!
Previous attempts such as draft-ietf-idr-advisory-00 and
draft-ietf-idr-operational-message-00 failed to deliver for various
reasons (feature creep comes to mind), therefore we are trying to do
this as simple as possible.
Kind regards,
Job
----- Forwarded message from [email protected] -----
Date: Tue, 15 Nov 2016 21:30:15 -0800
From: [email protected]
To: Jakob Heitz <[email protected]>, Job Snijders <[email protected]>, John Scudder
<[email protected]>
Subject: New Version Notification for draft-snijders-idr-shutdown-00.txt
A new version of I-D, draft-snijders-idr-shutdown-00.txt
has been successfully submitted by Job Snijders and posted to the
IETF repository.
Name: draft-snijders-idr-shutdown
Revision: 00
Title: The Shutdown Communication BGP Cease Notification Message
subcode
Document date: 2016-11-15
Group: Individual Submission
Pages: 6
URL:
https://www.ietf.org/internet-drafts/draft-snijders-idr-shutdown-00.txt
Status: https://datatracker.ietf.org/doc/draft-snijders-idr-shutdown/
Htmlized: https://tools.ietf.org/html/draft-snijders-idr-shutdown-00
Abstract:
This document defines the BGP Cease NOTIFICATION message "Shutdown
Communication" subcode for operators to transmit a short freeform
message to describe why a BGP session was shutdown.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
----- End forwarded message -----
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
