BgpPeerEvent

• Base type Enumeration

BGP peer events. The event 'none' implies that the peer is in initialization phase. The event 'start' implies that BGP operation has started on this peer. The event 'stop' implies that BGP operation has stopped on this peer. The event 'open' implies that BGP transport has initialized a connection open action to the peer. The event 'close' implies that BGP transport has closed the connection to the peer. The event 'openFail' implies that open connection attempt of BGP transport has failed. The event 'error' implies that BGP transport experienced a fatal error. The event 'connectionRetry' implies that the connection retry timer expired. The event 'holdTime' implies that the hold timer expired. The event 'keepAlive' implies that the keep alive timer expired. The event 'receiveOpen' implies that a BGP OPEN message was received. The event 'receiveKeepAlive' implies that a BGP KEEPALIVE was received. The event 'receiveUpdate ' implies that a BGP UPDATE was received. The event 'receiveNotify' implies that a BGP NOTIFY was received. The event 'startPassive' implies that BGP is waiting passive to hear from the other end. The event 'parseError' implies that there was a bad message received from the peer. The event 'outOfMemory' implies that there is not enough memory in the system for this peer entity. The event 'rtmLimitExceeded' implies that the route table max limit has exceeded. The event 'maxPrefixLimitExceeded' implies that the max prefixes allowed has been exceeded. The event 'maxPrefixLimitExceededLogged' implies that the max prefixes allowed has been exceeded but the peering is not dropped. The event 'outOfProtectedNHIndex' implies that protected next hop indexes has been exceeded. The event 'outOfNHIndex' implies that next hop indexes has been exceeded. The event 'labelAllocFailed' implies that label allocation failed. The event 'lspIdAllocFailed' implies that LSP Id allocation failed. The event 'peeringDownInCollisionResolution' implies that bgp peering is brought down due to collision resolution process. The event 'peeringDownInAdminShutdown' implies that bgp peering is brought down due to a shutdown of BGP peer, group or protocol. The event 'peeringDownInAdminReset' implies that bgp peering is brought down due to a clear of BGP peer, group or protocol. The event 'peeringDownInConfigChange' implies that bgp peering is brought down due to a configuration change which requires reestablishment.