The BGP FSM enters the Established state. (BgpPeerRemoteAddr=[PeerIpv4Addr], BgpPeerLastError=[PeerLastError], BgpPeerState=[PeerState],VpnInstance=[VpnInstance])
The BGP peer relationship is established.
| Trap Attribute | Description | 
|---|---|
| Alarm or Event | Event | 
| Trap Severity | Critical | 
| Mnemonic Code | PEER_ESTABLISHED_NOTIFICATION | 
| Trap OID | 1.3.6.1.2.1.15.0.1 | 
| MIB | BGP4-MIB | 
| Alarm ID | This is an event trap and does not involve alarm ID. | 
| Alarm Name | This is an event trap and does not involve alarm name. | 
| Alarm Type | This is an event trap and does not involve alarm type. | 
| Raise or Clear | This is an event trap and does not involve alarm generation or clearance. | 
| Match trap | - | 
| Parameter | Description | 
|---|---|
| PeerIpv4Addr | The address of the BGP peer. This log is reported to the NMS based on the bgpBackwardTransNotification object in the public MIB (Bgp4-mib.mib). This MIB object applies to IPv4 peers, not to IPv6 peers. As a result, this log is not reported if IPv6 peer status changes. In this case, you need to query the Established alarm on the device. | 
| PeerLastError | The value of the Error Code field in the Notification packet generated when the peer relationship is interrupted last time. The value is expressed in the format of [ErrorCode][ErrorSubCode]. [ErrorCode] refers to the error code and [ErrorSubCode] refers to the error subcode. Take the integer 35 as an example, figure 3 is the error code and figure 5 is the error subcode. For detailed information about the error code, refer to BGP Error Code. If the value is 0, it indicates that no error occurs. | 
| PeerState | The status of the BGP peer. | 
| VpnInstance | The name of the VPN instance. | 
| VB OID | VB Name | VB Index | 
|---|---|---|
| 1.3.6.1.2.1.15.3.1.7 | bgpPeerRemoteAddr | bgpPeerRemoteAddr | 
| 1.3.6.1.2.1.15.3.1.14 | bgpPeerLastError | bgpPeerRemoteAddr | 
| 1.3.6.1.2.1.15.3.1.2 | bgpPeerState | bgpPeerRemoteAddr |