Country/Region

- United States
- ASEAN Region
- Australia
- 中国 - China
- France
- Deutschland - Germany
- India
- Italia - Italy
- 日本 - Japan
- 대한민국 - Korea
- Россия - Russia
- España - Spain
- 台灣 - Taiwan
- United Kingdom

Contact Us
|
Country/Region
United States

# Technical Documentation

Download Software
Research a Problem
Case Management
Contract & Product Management
Technical Documentation
Documentation Archive
Report Documentation Bug
Enterprise MIBs
File Format Help
Glossary
Portable Libraries
End-of-Life Products
Contact Support
Guidelines and Policies
Security Resources
Feedback

## Documentation Search

Advanced Search | Search Tips

# neighbor capability

#### Syntax

For all capabilities except ORF:

[ no | default ] neighbor { ipAddress | ipv6Address | peerGroupName } capability
{ deprecated-dynamic-capability-negotiation | dynamic-capability-negotiation |
four-octet-as-numbers | negotiation | route-refresh | route-refresh-cisco }

For the ORF capability:

neighbor { ipAddress | ipv6Address | peerGroupName } capability orf
{ prefix-list | prefix-list-cisco } { send | receive | both }

{ no | default } neighbor { ipAddress | ipv6Address | peerGroupName } capability orf
{ prefix-list | prefix-list-cisco } [ send | receive | both ]

#### Release Information

Command introduced before JunosE Release 7.1.0.
ipv6Address variable added in JunosE Release 8.0.0.

#### Description

Controls advertisement of BGP capabilities to peers. Capability negotiation and advertisement of all capabilities, except the ORF capability, is enabled by default. The no version disables capability negotiation or prevents advertisement of the specified capability. The default version restores the default condition, advertising the capability.

#### Options

- ipAddress—IP address of BGP neighbor
- ipv6Address—IPv6 address of BGP neighbor; because IPv6 ORF prefix lists are not supported, this variable is valid for the ORF c capability only under the IPv4 address family for advertising IPv4 routes over BGP IPv6 peers
- peerGroupName—Name of BGP peer group. If you specify a BGP peer group by using the peerGroupName argument, all the members of the peer group inherit the characteristic configured with this command, unless it is overridden for a specific peer.
- negotiation—Determines whether the capabilities option is sent in the open message while establishing a session; if it is not sent, no capability negotiation is conducted with that peer
- deprecated-dynamic-capability-negotiation—Indicates support of negotiation of capabilities (sending new capabilities or removing previously negotiated capabilities) without performing a hard clear of the BGP session; the capability data field does not include a list of capabilities that can be dynamically negotiated
- dynamic-capability-negotiation—Indicates support of negotiation of capabilities (sending new capabilities or removing previously negotiated capabilities) without performing a hard clear of the BGP session; the capability data field includes a list of capabilities that can be dynamically negotiated
- four-octet-as-numbers—Indicates support of AS numbers and sub-AS numbers that are four octets in length, in the range 0–4294967295
- route-refresh—Indicates support of route-refresh messages that request the peer to resend its routes to the router, enabling the BGP speaker to apply modified or new policies to the routes when it receives them again
- route-refresh-cisco—Indicates support of Cisco-proprietary (prestandard) route-refresh messages for interoperability with older Cisco devices
- orf—Indicates support of cooperative route filtering to install a BGP speaker’s inbound route filter as an outbound route filter on the peer
- prefix-list—Installs the filter (any inbound prefix list or distribute list) as an outbound prefix list
- prefix-list-cisco—Installs the filter (any inbound prefix list or distribute list) as an outbound Cisco proprietary prefix list
- send—Sends inbound route filter to the peer to install as the outbound route filter
- receive—Accepts inbound route filter from the peer and installs it as the outbound route filter; cannot be configured for a peer group or a peer that is a member of a peer groups
- both—Sends and accepts inbound route filters with the peer for installation as the outbound route filter

#### Mode

Address Family Configuration, Router Configuration

#### Published: 2010-10-19

Help
|
My Account
|
Log Out