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 ASN:<reserved value>. For example, a Socket site with a BGP neighbor that we want to apply the Socket isolated routing reserved community:
-
Cato ASN is 65001
-
LAN switch is defined with Cato Peer ASN is 65002
-
To keep routes local on the Socket, add the following BGP community to the Cato Peer BGP process: 65001:32768. This is based on the reserved value 32768 (see table below).
For example, for Cisco routers, the command would be
set community 65001:32768
, and you need to specify the Cato ASN.
For more about defining the Cato peer ASN, see Configuring BGP Neighbors for a Cato Socket.
IMPORTANT: If you use a Cato reserved BGP community, make sure to configure BGP filtering on the BGP routers to prevent advertising the Cato system range to the Sockets. Otherwise, there can be significant connectivity issues with the impacted Sockets.
The following table describes the reserved BGP communities and their functionality.
Name |
BGP Community |
Applies To |
Description |
---|---|---|---|
Socket isolated routing |
<Cato ASN>: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.