Communities (override list)

This table contains overrides that manipulate the Communities attributes of NLRI.

If an action applies a row of this table, all of the manipulations that this row implements are processed in the following sequence:
  1. "Clear"
  2. "Add"
  3. "Remove"




Name
Contains the name of this entry.
Clear
Determines whether the device deletes unknown communities from the NLRI.
Note: Known communities remain in place even if this option to set to "Yes".
Known communities are:
  • no-peer
  • no-export
  • no-advertise
  • no-export-subconfed
  • graceful-shutdown
Note: For more information, see RFC 1997 and RFC 3765.
Add
Specifies which communities the device adds to an NLRI. Communities are specified by means of a comma-separated list (<AS-number1>: <Value1>,<AS-number2>:<Value2>,<AS-number3>:<Value3>).
Remove
Specifies which communities the device removes from an NLRI. Communities are specified by means of a comma-separated list (<AS-number1>: <Value1>,<AS-number2>:<Value2>,<AS-number3>:<Value3>).
Note: Known communities are not removed from NLRI. Known communities are:
  • no-peer
  • no-export
  • no-advertise
  • no-export-subconfed
  • graceful-shutdown
The following input formats are available for communities:
Input format Community
1:2 Standard community
1.2.3.4:1 IPv4-specific extended community
roc:1.2.3.4:1 IPv4-specific route origin extended community (Site-of-Origin (SoO))
rtc:1.2.3.4:1 IPv4-specific route target extended community
ext2:1:2 Two-byte AS extended community
ext4:1:2 Four-byte AS extended community
roc:1:2 Two-byte AS route origin extended community (Site-of-Origin (SoO))
rtc:1:2 Two-byte AS route origin extended community
roc:ext4:1:2 Four-byte AS route origin extended community (Site-of-Origin (SoO))
Comment
Comment on this entry.

www.lancom-systems.com

LANCOM Systems GmbH | A Rohde & Schwarz Company | Adenauerstr. 20/B2 | 52146 Wuerselen | Germany | E‑Mail info@lancom.de

LANCOM Logo