Peer <AFI, SAFI> configuration table. This table allows a user to configure peer characteristics on a per AFI/SAFI basis. This table is a configuration table - all status, statistics and control fields are deprecated in favor of the BGP peer AFI/SAFI status table (bgpPeerAfiSafiStatusTable). Rows in this table cannot be created or destroyed manually. A table entry for each supported address family is created automatically when an entry in the bgpPeerTable is created. The entries are destroyed when the bgpPeerTable entry is destroyed. This table does not contain entries for dynamic peers. If the peer belongs to a peer group, then the peer's per-afi-safi configuration values may be taken from either the peer level (bgpPeerTable and bgpPeerAfiSafiTable) or the peer group level (bgpPeergrTable and bgpPeergrAfiSafiTable). Which level is used is controlled by bgpPeerAfiSafiConfigFromGr, and by the configuration usage fields in bgpPeerTable (bgpPeerConfigUsage, bgpPeerConfigUsage2 and bgpPeerConfigUsage3). Each of these fields contains a set of bit flags. bgpPeerAfiSafiConfigFromGr takes precedence, and behaves as follows. - For each configuration field in bgpPeerAfiSafiTable, a a corresponding bit is defined in bgpPeerAfiSafiConfigFromGr. - If the bit flag is set, then the configuration is taken from the peer group level. The bit flag in the configuration usage fields in bgpPeerTable is only relevant if the bgpPeerAfiSafiConfigFromGr bit is clear. The peer configuration usage fields behave as follows. - If a configuration field exists in both bgpPeerTable and the bgpPeerAfiSafiTable, then a corresponding bit flag is defined. - If the bit flag is set, then the configuration is taken from the peer group level (if the row/rows is/are active). Otherwise, the value is taken from the peer level.