This article discusses how to use Cato reserved BGP communities.
Cato provides a list of reserved BGP communities with hard-coded behavior for handling and processing incoming BGP prefixes from the neighboring routing devices. When Cato receives a BGP prefix marked with a reserved community, it will handle it according to the section below, Cato's Reserved BGP Communities.
This is the structure for Cato reserved communities: Cato peer AS:<reserved value>. For example, a Socket site with a BGP neighbor that we want to apply the Socket isolated routing reserved community:
-
Cato Socket site is configured with AS 65001
-
LAN switch is configured with AS 65002
-
The desired functionality is to isolate the routes on the Socket level and not to propagate the routes to the PoP, this can be achieved with the reserved value 32768 (see table below)
The reserved community for this example would be 65001:32768.
For more about defining the Cato peer AS, see Configuring BGP Neighbors for a Cato Socket.
The following table describes the reserved BGP communities and their functionality.
Name |
BGP Community |
Applies To |
Description |
---|---|---|---|
Socket isolated routing |
<Cato peer AS>:32768 |
Socket sites with Socket v15 or higher |
|
1 comment
This article is not clear and lacks an example
Please sign in to leave a comment.