[OPSAWG] IETF 109 - OPSAWG presentation https://tools.ietf.org/html/draft-gu-opsawg-network-monitoring-igp-00

[Chenshuanglong <[e-mail]>]

hi all,

I presented network-monitoring-igp draft at IETF 109, see attached.  https://tools.ietf.org/html/draft-gu-opsawg-network-monitoring-igp-00
We suggest to use BMP to monitor IGPs to avoid setting too many monitoring protocols for different control plane protocols.
In addition, it describes the requirements for collecting IGP information, such as the use cases listed in the draft.

Use Case1：IS-IS Route Flapping
   The IS-IS Route Flapping refers to the situation that one or more routes appear and then disappear in the routing table repeatedly.
   Route flapping usually comes with massive PDUs interactions (e.g., LSP, LSP purge...), which consume excessive network bandwidth, and excessive CPU processing.
In addition, the impact is often network-wide.  The localizing of the flapping source and the identifying of root causes haven't been easy work due to various reasons.

Use Case2： IS-IS LSDB Synchronization Failure
   During the IS-IS flooding, sometimes the LSP synchronization failure happens.  The synchronization failure causes can be generally classified into three cases，(1) the LSP is not correctly advertised， (2) LSP transmission error, (3) the LSP is received but not correctly processed.

What do you think of these use cases and extended BMP protocols?

Kind Regards
Shuanglong Chen