close
keyboard_arrow_left
Table of Contents
- play_arrow Overview
- play_arrow Introduction to IS-IS
-
- play_arrow Monitoring and Troubleshooting Network Issues
- play_arrow Monitoring Networks
- play_arrow Troubleshooting Network Issues
- Working with Problems on Your Network
- Isolating a Broken Network Connection
- Identifying the Symptoms of a Broken Network Connection
- Isolating the Causes of a Network Problem
- Taking Appropriate Action for Resolving the Network Problem
- Evaluating the Solution to Check Whether the Network Problem Is Resolved
- play_arrow Troubleshooting IS-IS
-
- play_arrow Configuration Statements and Operational Commands
list Table of Contents
Understanding IS-IS Flood Group
date_range
24-Nov-23
IS-IS supports flood-group. This feature limits link-state packet data unit (PDU) flooding over IS-IS interfaces.
A link-state packet (LSP) that is not self-originated will be
flooded only through the interface belonging to the flood group that
has the configured area ID in the LSP. This helps minimize the routes
and topology information, thus ensuring optimal convergence. You can
segregate both Level 1 and Level 2 IS-IS routers into flood
groups by using area IDs as tags to identify a flood group. Configure
interfaces with specific area IDs to modify the flooding behavior
as per your requirements. To enable IS-IS flood group, include the flood-group flood-group-area-ID statement
at the [edit protocols isis interface] hierarchy level.
