Whether or not the first AS number in the AS_PATH attribute in an UPDATE received from this peer should be checked to make sure it is the same as the AS number of the peer. This flag only applies to EBGP peers. It should be set to True unless the peer has a specific policy that means it does not prepend its AS number so that it is the first in the path. When set to 'true', DC-BGP checks the first AS number in UDPATES received from the peer. When set to 'false', DC-BGP does not check the first AS number in UDPATES received from the peer. When set to 'inherit', the fallover behavior for this peer is determined by the setting of the bgpRmEntCheckFirstAsNum field. If the peer belongs to a peer group, then the configuration is taken from either this field or the equivalent peer group field, depending on the setting of the bit in the bgpPeerConfigUsage field. The value for the peer or peer group is determined and, if this is 'inherit', then the bgpRmEntCheckFirstAsNum value is used. This field can be changed at any time. However, if the field is changed while the peer is admin_status UP, the change will only take effect after the peer has been cycled admin_status DOWN and then UP, thus forcing the peer session to be restarted. In this case, until the peer is set admin_status DOWN, the peer will be marked as out of date (as reported by the config_state field in the AMB_BGP_PEER_STATUS row for the peer).