bgpPeerRangeTable

Peer range table.
          
This table allows a user to configure BGP dynamic neighbors.
Instead of being configured individually in the BGP peer
table, BGP dynamic neighbors are configured as ranges of
remote addresses with associated peer groups.  Each range
is configured as a remote address prefix.  Any BGP peer with
a remote address that matches the remote address prefix
becomes a member of the associated peer group.
          
Each entry in this table configures a remote address prefix
and specifies the associated peer group.
          
DC-BGP handles incoming connections from BGP peers as
follows.
-  If the connection matches a peer configured in the
   BGP peer table then the peer is a configured peer.
-  Otherwise if the connection matches a remote address
   prefix in the BGP peer range table then the peer is
   a dynamic peer.
-  Otherwise if the listen socket is configured to accept
  all incoming connections then the connection is accepted
  and uses the default peer configuration.
-  Otherwise the connection is rejected.
          
For an incoming connection to match an entry in this table
the following conditions must all be satisfied.
-  The remote address of the incoming connection must match
  the remote address prefix of the peer range entry.
-  The row status of the peer range entry must be 'active'.
-  The admin status of the peer range entry must be 'up'.
-  The peer range entry must specify a peer group.
-  The peer group must exist.
-  The row status of the peer group must be 'active'.
-  The admin status of the peer group must be 'up'.
          
If an incoming connection doesn't satisfy all these
conditions for one peer range entry then it can still be
accepted if it matches another peer range entry or if the
listen socket is configured to accept all incoming
connections.
          
If an incoming connection matches multiple peer range
entries then the entry with the longest remote address
prefix is selected.
          
Although it is possible to configure overlapping peer ranges
with different remote address prefix lengths, this is not
recommended - peer range configuration is simpler and
clearer if peer ranges do not overlap.
          
Dynamic peers are always passive.  It is not possible to
initiate outbound connections to dynamic peers because
their addresses aren't known until they initiate an
incoming connection.
          
Deactivating a peer range entry causes BGP sessions with
matching dynamic BGP peers to be dropped.  This does not
apply to configured BGP peers with matching remote
addresses, nor to dynamic BGP peers with remote addresses
matching peer range entries with longer remote address
prefixes.

MIB

DC-BGP-MIB

OID

.1.2.826.42.1.1578918.5.65.1.10

Type

table

Status

current

Parent

bgpMib

Siblings

10

Children

1