BGP peer configuration table. This table allows a user to configure individual BGP peers. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer status table (bgpPeerStatusTable). This table does not contain entries for dynamic peers. If a user configures a new BGP peer that matches an existing dynamic BGP peer then DC-BGP terminates any BGP session with the dynamic BGP peer to force it to use the new configuration. If the peer belongs to a peer group, then the peer's configuration values may be taken from either the peer MIB or the peer group MIB. Which values are used is controlled by the config_usage, config_usage2 and config_usage3 fields in the peer MIB. These fields contains a set of bit flags. These fields may themselves be overridden by per-AFI/SAFI configuration as described in the description of bgpPeerAfiSafiTable. Unless specified under the description of a MIB field below, or overridden by the bgpPeerAfiSafiTable, the following applies. - Each configuration field in the bgpPeerTable MIB has a copy in the bgpPeerGrTable MIB and a corresponding config usage flag. - If the bit flag is set, then the value in the bgpPeerGrTable MIB is used provided the MIB row exists and is active. Otherwise, the value in the bgpPeerTable MIB is used. - If the configuration field also has a per-afi-safi version in the bgpPeerAfiSafiTable MIB, then there is also a per-afi-safi version in the bgpPeergrAfiSafiTable MIB and the bit flag applies to these values as well.