This command specifies whether updates for prefixes containing the NOPEER community will be accepted by or sent to this neighbor.
| ip-address | An IPv4 or IPv6 address to add to a peer group. IPv4 addresses are specified in dotted-quad format; IPv6 addresses are specified in colon-separated format. |
| groupID | Specifies a BGP peer group name as a string of characters. If an invalid IP address is specified (for example, 256.1.1.1), it will be read as a group name. |
| bilateral | Specifies that for prefixes containing the NOPEER community attribute updates are not accepted or sent. |
| unspecified | Specifies that updates are accepted or sent for prefixes regardless of whether the prefix contains the NOPEER community attribute. The default value for peering type is unspecified. |
None.
BGP Router Configuration.
If the peering type is set to bilateral, EBGP peers will not accept or advertise routes containing the NOPEER community attribute as defined in RFC 3765.
The neighbor peering-type command provides for defining the peering type as either bilateral or unspecified for the NOPEER community attribute. If the peering type is specified as bilateral, updates for this neighbor are not accepted or sent when the community attribute is NOPEER. If the peering type is specified as unspecified, updates for this neighbor are accepted and sent when the community attribute is NOPEER.
The no neighbor peering-type command resets the peering type to the default value of unspecified for this neighbor.
The following example configures the peering type for neighbor 10.10.25.1 as bilateral:
System(su-config)->router bgp 65151 System(su-config-bgp)->bgp router-id 159.1.1.9 System(su-config-bgp)->neighbor 10.10.25.1 peering-type bilateral System(su-config-bgp)->
Print
this page
Email this topic
Feedback
View PDF
Download EPUB