SNMP Monitoring via snmpd Service [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Next revision    		Previous revision
    en:dpi:dpi_components:platform:mon_stat:snmpd [2024/09/26 15:29] – created - external edit 127.0.0.1en:dpi:dpi_components:platform:mon_stat:snmpd [2025/08/14 14:14] (current) – elena.krasnobryzh
    Line 1: Line 1:
     {{indexmenu_n>5}} {{indexmenu_n>5}}
    -======SNMP monitoring via snmpd service====== 
    -=====Description===== 
    -SNMP is a protocol that allows retrieving information about the SSG server for centralized monitoring of critical parameters. The snmpd service from the operating system is used for this purpose.\\  
    -**How it works:** an SNMP request is sent to the server, snmpd service retrieves the necessary information and sends it to the monitoring server. The monitoring server receives and processes this information, allowing to understand the server's status—tracking at which levels various parameters and data are located. 
      
    -The ''bngsnmp'' package contains scripts needed to form the VENDOR branch of OIDs for SNMP polling.\\ +====== SNMP Monitoring via snmpd Service ======
    -It is based on the ''snmp_passpersist'' library. Vendor branch OID: ''.1.3.6.1.4.1.43823''+
      
    -Contents of the vendor branch:+===== Description ===== 
     +SNMP is a protocol that allows retrieving information about the SSG server for centralized monitoring of critical parameters. This is implemented using the snmpd service included in the operating system.\\ 
     +**Operation principle:** An SNMP query is sent to the server, the snmpd service collects the required information and sends it to the monitoring server. The monitoring server receives and processes this information, enabling status monitoring of the server - tracking parameter levels and data. 
     + 
     +The ''bngsnmp'' package contains scripts required for building the VENDOR OID branch for SNMP polling.\\ 
     +It's based on the ''snmp_passpersist'' library. Vendor OID branch: ''.1.3.6.1.4.1.43823'' 
     + 
     +Vendor branch components:
       * CPU statistics, including core utilization by BNG processes;   * CPU statistics, including core utilization by BNG processes;
    -  * number of illegitimate drops; +  * Number of illegitimate drops; 
    -  * drop statistics on the dispatcher; +  * Dispatcher drop statistics; 
    -  * availability list of RADIUS servers (**when using a proxy or load balancer, this proxy will be shown in the statistics**); +  * RADIUS server availability list (**when using a proxy or load balancer, the proxy will be shown in statistics**); 
    -  * number of DHCP subscribers — **when the function is active**; +  * DHCP subscriber count - **with active functionality**; 
    -  * list of VRFs and active subscribers in each — **when the function is active**; +  * PPPoE, L2TP, PPP subscriber count - **with active functionality**; 
    -  * DPDK interface statistics (number of packets, errors, signal level, etc.); +  * VRF list and active subscribers in each - **with active functionality**; 
    -  * NAT statistics (list of profiles, list of pools, and number of translations for each public address) — **when the function is active**; +  * DPDK interface statistics (packet count, errors, signal level etc.); 
    -  * list of hardware modules installed on the motherboard — **if supported by the BMC controller**; +  * NAT statistics (profile list, pool list, and translation count per public address) - **with active functionality**; 
    -  * metrics from hardware sensors (voltage, power consumption, FAN RPMs) — **if supported by the BMC controller**; +  * Hardware module list installed on motherboard - **if supported by BMC controller**; 
    -  * utilization of DHCP server pools (supported __only by KEA-DHCP__ server) — **when the function is active**.+  * Hardware sensor readings (voltage, power consumption, FAN RPMs) - **if supported by BMC controller**; 
     +  * DHCP pool utilization (supported **only** with KEA-DHCP server) - **with active functionality**.
      
    -This script also overrides standard branches by adding statistics from DPDK interfaces: +This script also overrides standard branches by adding DPDK interface statistics: 
    -  * ''.1.3.6.1.2.1.2.2.1'' — 32-bit counters +  * ''.1.3.6.1.2.1.2.2.1'' - 32-bit counters 
    -  * ''.1.3.6.1.2.1.31.1.1.1'' — 64-bit counters+  * ''.1.3.6.1.2.1.31.1.1.1'' - 64-bit counters
      
    -If necessary, you can disable the override by commenting out or deleting the following lines from ''/etc/snmp/snmpd.conf'': +If needed, override can be disabled by commenting or removing these lines from ''/etc/snmp/snmpd.conf'':
    -<code bash>pass_persist    .1.3.6.1.2.1.2.2.1      /usr/local/bin/bng_snmp/vas_pp.py +
    -pass_persist    .1.3.6.1.2.1.31.1.1.1   /usr/local/bin/bng_snmp/vas_pp_hc.py</code>+
      
    -<note>{{ :dpi:dpi_components:platform:mon_stat:vasexperts-mib.mib |MIB File}}</note>+<code bash> 
     +pass_persist    .1.3.6.1.2.1.2.2.1      /usr/local/bin/bng_snmp/vaspp 
     +pass_persist    .1.3.6.1.2.1.31.1.1.1   /usr/local/bin/bng_snmp/vaspphc 
     +</code>
      
    -=====Installation===== +MIB file location after installation: ''/usr/share/snmp/mibs/VASEXPERTS-MIB.txt'' 
    -  - Installation: <code bash>yum install bngsnmp</code>+ 
     +===== Installation ===== 
     +  - Installation (net-snmp, net-snmp-utils will be installed as dependencies): <code bash>yum install bngsnmp</code>
       - Configuration: <code bash>/bin/cp -f /etc/snmp/snmpd.conf.example /etc/snmp/snmpd.conf</code>   - Configuration: <code bash>/bin/cp -f /etc/snmp/snmpd.conf.example /etc/snmp/snmpd.conf</code>
    -  - Restart the net-snmp service: <code bash>systemctl restart snmpd</code> +  - Restart net-snmp service: <code bash>systemctl restart snmpd</code> 
    -  - Disable selinux (in case of error when starting SNMP): <code bash>vi /etc/selinux/config+  - Disable selinux (if SNMP fails to start): <code bash>vi /etc/selinux/config
     ... ...
     SELINUX=disabled SELINUX=disabled
     ...</code> ...</code>
      
    -=====Checking snmpd and vendor branch functionality===== +===== Verifying snmpd and Vendor Branch Functionality ===== 
    -The snmpwalk utility allows you to check whether data is being received via SNMP: +The snmpwalk utility verifies SNMP data reception
    -  - Install snmpwalk: <code bash>dnf install net-snmp-utils</code> +
    -  - Command to check SNMP functionality: <code bash>snmpwalk -v 2c -c nokiamon localhost -On .1.3.6.1.4.1.43823</code>+
      
    -=====How to read the MIB file===== +Command to test SNMP operation: 
    -If you need to see the MIB file in a graphical representation, you can open it through the MIB Browser. It will describe the entire vendor branch and its OIDs.\\+<code bash>snmpwalk -v 2c -c nokiamon localhost -On .1.3.6.1.4.1.43823</code> 
     +The system polls once per minute, so more frequent polling is unnecessary. 
     + 
     +===== How to Read MIB File ===== 
     +To view the MIB file graphically, open it with MIB Browser. It describes the entire vendor branch and its OIDs. \\
     The example below shows: The example below shows:
       - Vendor branch file   - Vendor branch file
       - Its OID   - Its OID
    -{{:dpi:dpi_components:platform:mon_stat:mib_browser.png?nolink&800|}} 
      
    -<note>You can also create your own walk in the MIB Browser by specifying the server address</note>+{{:dpi:dpi_components:platform:mon_stat:mib_browser.png?nolink&800|}}
      
    -=====Known limitations===== +===== Known Limitations ===== 
    -On-stick device support is available starting from version 13.2-beta4.2.+On-stick device support available since version 13.2-beta4.2