Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Dell EMC Configuration Guide for the S4048T–ON System 9.14.2.4

PDF

Monitoring BGP sessions via SNMP

This section covers the monitoring of BGP sessions using SNMP.

BGP SNMP support for non-default VRF uses a SNMP context to distinguish multiple BGP VRF instances within a single BGP process. SNMP context is a repository of management information that can be accessed through the SNMP agent. SNMP supports multiple contexts in a device. SNMPv3 has a context name field in its PDU, which automatically allows the context name field to be mapped to a particular VRF instance without having to be mapped to a community map. SNMPv2c context has to be mapped to a community map. A new CLI command, snmp context, under BGP context, has been introduced to perform this function.

To map the context to a VRF instance for SNMPv2c, follow these steps:
  1. Create a community and map a VRF to it. Create a context and map the context and community, to a community map.
    • sho run snmp
    • snmp-server community public ro
    • snmp-server community public ro
    • snmp-server community vrf1 ro
    • snmp-server community vrf2 ro
    • snmp-server context context1
    • snmp-server context context2
    • snmp mib community-map vrf1 context context1
    • snmp mib community-map vrf1 context context2
  2. Configure snmp context under the VRF instances.
    • sho run bgp
    • router bgp 100
    • address-family ipv4 vrf vrf1
    • snmp context context1
    • neighbor 20.1.1.1 remote-as 200
    • neighbor 20.1.1.1 no shutdown
    • exit-address-family
    • address-family ipv4 vrf vrf2
    • snmp context context2
    • timers bgp 30 90
    • neighbor 30.1.1.1 remote-as 200
    • neighbor 30.1.1.1 no shutdown
    • exit-address-family
To map the context to a VRF instance for SNMPv3, follow these steps:
  1. Create a community and map a VRF to it. Create a context and map the context and community, to a community map.
    • snmp-server community public ro
    • snmp-server community VRF1 ro
    • snmp-server community VRF2 ro
    • snmp-server context cx1
    • snmp-server context cx2
    • snmp-server group admingroup 3 auth read readview write writeview
    • snmp-server group admingroup 3 auth read readview context cx1
    • snmp-server group admingroup 3 auth read readview context cx2
    • snmp-server user admin admingroup 3 auth md5 helloworld
    • snmp mib community-map VRF1 context cx1
    • snmp mib community-map VRF2 context cx2
    • snmp-server view readview .1 included
    • snmp-server view writeview .1 included
  2. Configure snmp context under the VRF instances.
    • sho run bgp
    • router bgp 100
    • address-family ipv4 vrf vrf1
    • snmp context context1
    • neighbor 20.1.1.1 remote-as 200
    • neighbor 20.1.1.1 no shutdown
    • exit-address-family
    • address-family ipv4 vrf vrf2
    • snmp context context2
    • timers bgp 30 90
    • neighbor 30.1.1.1 remote-as 200
    • neighbor 30.1.1.1 no shutdown
    • exit-address-family

Example of SNMP Walk Output for BGP timer configured for vrf1 (SNMPv2c)

snmpwalk -v 2c -c vrf1 10.16.131.125 1.3.6.1.4.1.6027.20.1.2.3
SNMPv2-SMI::enterprises.6027.20.1.2.3.1.1.1.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 950
SNMPv2-SMI::enterprises.6027.20.1.2.3.1.1.2.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 14
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.1.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 60
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.2.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 180
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.3.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 60
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.4.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 30
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.5.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 30
SNMPv2-SMI::enterprises.6027.20.1.2.3.3.1.1.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 180
SNMPv2-SMI::enterprises.6027.20.1.2.3.3.1.2.0.1.20.1.1.2.1.20.1.1.1 = Gauge32: 60

Example of SNMP Walk Output for BGP timer configured for vrf2 (SNMPv2c)

snmpwalk -v 2c -c vrf2 10.16.131.125 1.3.6.1.4.1.6027.20.1.2.3
SNMPv2-SMI::enterprises.6027.20.1.2.3.1.1.1.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 950
SNMPv2-SMI::enterprises.6027.20.1.2.3.1.1.2.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 14
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.1.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 60
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.2.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 90
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.3.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 30
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.4.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 30
SNMPv2-SMI::enterprises.6027.20.1.2.3.2.1.5.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 30
SNMPv2-SMI::enterprises.6027.20.1.2.3.3.1.1.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 90
SNMPv2-SMI::enterprises.6027.20.1.2.3.3.1.2.0.1.30.1.1.2.1.30.1.1.1 = Gauge32: 30

Example of SNMP Walk Output for BGP timer (SNMPv3)

snmpwalk -v 3 -a md5 -A helloworld -l authNoPriv -n cx1 -u admin 10.16.143.179 1.3.6.1.4.1.6027.20.1.3.6.1.4
SNMPv2-SMI::enterprises.6027.20.1.3.6.1.4.2963474636.0.1 = Gauge32: 200
SNMPv2-SMI::enterprises.6027.20.1.3.6.1.4.2963475124.0.1 = Gauge32: 100

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\