How to monitor BGP status using SNMP?
27563
Created On 12/19/19 00:31 AM - Last Modified 09/08/21 20:33 PM
Objective
Monitor BGP status using snmp MIB.
Environment
- Any Palo Alto Firewall.
- PAN-OS 7.1 and above.
Procedure
When using SNMP, BGP status can only be monitored using SNMP Traps. SNMP Polling is currently not supported.
The Traps listed below can be used to report the BGP peer status change.
Name panROUTINGRoutedBGPPeerEnterEstablishedTrap
OID .1.3.6.1.4.1.25461.2.1.3.2.0.1531
MIB PAN-TRAPS
BGP peer session enters established state.
Name panROUTINGRoutedBGPPeerLeftEstablishedTrap
OID .1.3.6.1.4.1.25461.2.1.3.2.0.1532
MIB PAN-TRAPS
BGP peer session left established state.
Name panROUTINGRoutedBGPPeerFailedTrap
OID .1.3.6.1.4.1.25461.2.1.3.2.0.1533
MIB PAN-TRAPS
BGP peer session has failed and may restart.
Name panROUTINGRoutedBGPPeerRestartedTrap
OID .1.3.6.1.4.1.25461.2.1.3.2.0.1534
MIB PAN-TRAPS
Initiated graceful-restart with a BGP peer.
Name panROUTINGRoutedBGPPeerRestartFailedTrap
OID .1.3.6.1.4.1.25461.2.1.3.2.0.1535
MIB PAN-TRAPS
Graceful-restart with a BGP peer failed.
Name panROUTINGRoutedBGPRefreshSentTrap
OID .1.3.6.1.4.1.25461.2.1.3.2.0.1536
MIB PAN-TRAPS
ROUTE REFRESH message sent to a BGP peer.
Name panROUTINGRoutedBGPRibinRecalcTrap
OID .1.3.6.1.4.1.25461.2.1.3.2.0.1537
MIB PAN-TRAPS
An RIB-In is being recalculated as a result of changed import policy.
Additional Information
Feature Request (FR ID: 5844) is currently pending with Engineering team to implement SNMP Polling for BGP. Follow up with account team if this feature is urgently needed.