OPBNOS R2.5
Release
  • Open Packet Broker
  • What's New?
  • Getting Started
    • Licensing
    • Limitations
    • Image Management
      • Installing OPBNOS from ONIE
      • Installing OPBNOS from USB Drive
      • Image Upgrade from OPBNOS
      • Selecting OPBNOS on next boot
      • Removing available images
      • Rebooting the Switch
    • Supported HwSku
    • Scalability
    • Downloads
  • CLI Configuration Guide
    • Configuring License
    • Configuring Hostname
    • Configuring Username
    • On-Box FlowVision
    • Configuring AAA
      • Configuring AAA
      • Configuring TACACS
      • Configuring RADIUS
    • Interface Management
      • Configuring Management Interface
      • Configuring Physical Interface
    • Link Layer Discovery Protocol (LLDP)
      • Enabling LLDP
      • Displaying LLDP Neighbors
    • Configuring Interface Description
    • Configuring Auto Negotiation
    • Configuring FEC
    • Configuring Maximum Transition Unit
    • Configuring Port Speed
    • Configuring Interface Type
    • Configuring VLAN Modes
    • Configuring Loopback Mode
    • Configuring Packet Slicing
    • Configuring Ingress VLAN
    • Configuring Egress Tagging
    • Configuring Tx-only
    • Configuring An-clause
    • Configuring PortChannel
    • Configuring LAG Hash
    • Configuring Flows and Rules
      • Configuring Network Ports
      • Configuring Tool Ports
      • Configuring Flows
      • Configuring Flow Description
      • Configuring Flow Rules (NVIDIA)
      • Configuring Flow Rules (Broadcom)
      • Configuring Flow Match Expression Rules
      • Configuring Flow UDF Rules
      • Configuring Push/Pop VLAN
      • Configuring Flow Override Action(s)
      • Display Flow Information
      • Clear Flow Counters
    • Configuring GTP Flow
    • Configuring VxLAN Flow
    • Configuring SNMP
      • Configure SNMP community
      • Configuring SNMP Trap
      • Configuring SNMP Threshold
      • Configuring SNMP User
      • Configuring SNMP Location
      • Configuring SNMP Contact
    • Configuring SYSLOG
    • Ping
    • Traceroute
    • Configuring NTP
    • Configuring Timezone
    • Configuring sFlow
    • Display Interface Information
      • Front Panel Port Mapping
    • Display System Information
      • Interface Transceiver Information
      • System Uptime
      • Reboot Cause
      • Show Environment
      • Show System Memory
      • Show Docker Memory
      • Show Services
      • Show Platform Fan
      • Show platform pcieinfo
      • Show Platform PSU
      • Show Platform SSD
      • Show Platform Summary
      • Show Platform Syseeprom
      • Show Platform Temperature
    • Configuration Management
      • Copying Files To Device
      • Copying Files From Device
      • Copying Running and Startup Configuration
      • Saving Configuration
      • Display Configuration
      • Clearing Startup configuration
    • Zero Touch Provisioning
      • DHCP Discovery
      • ZTP Boot File
      • Enable ZTP
    • Troubleshooting
  • Aviz FlowVision Graphical User Interface Guide
    • FlowVision Controller Installation
      • FV ESXi Host Installation
      • FV VirtualBox Installation
    • System
      • Viewing the Dashboard
      • Accessing System and Device Information
      • Managing Topologies
      • Managing Devices
      • Viewing System Log
      • Managing Users
      • Performing Backup and Restore
      • Viewing Audit Logs
    • Configuration
      • Configuring Ports
      • Configuring Port Groups
      • Configuring Rule Templates
      • Configuring Flows
    • Statistics
      • Viewing Port Statistics
      • Viewing Flow Statistics
    • Help
  • REST API Guide
    • FLOW
    • Interface Management
    • Port Channel
    • LLDP
    • SNMP
    • System and Platform
    • Statistics
  • Use Cases
    • For Engineers
      • VxLAN Deployment (NVIDIA)
      • GTP Deployment
      • Truncation and Load Balancing
      • Ingress VLAN and Egress Tagging
      • Loopback-mode Port
      • VLAN Mode/Tag Actions
    • Command Reference
      • Converting Network-to-Tool port
      • Configuring 1G Electrical SFP
      • Enabling FlowVision On-box Support
  • Solution Integration
    • Network Visibility and Analysis with OPB, Arkime, Elasticsearch & Kibana
      • Installation Pre-Requisites
      • Solution Components
      • Configuring OPBNOS
      • Installing Arkime
      • Installing Kibana
      • Troubleshooting
  • Support
    • How to contact Aviz Networks Support?
Powered by GitBook
On this page
  • Configure SNMP Trap
  • SNMP Trap Logs:

Was this helpful?

  1. CLI Configuration Guide
  2. Configuring SNMP

Configuring SNMP Trap

PreviousConfigure SNMP communityNextConfiguring SNMP Threshold

Last updated 1 year ago

Was this helpful?

Configure SNMP Trap

Traps are used when the Device needs to alert the Network Management software of an event without being polled. Traps ensure that the NMS gets information if a certain event occurs on the device that needs to be recorded without being polled by the NMS first. Managed network devices will have Trap MIBs with predefined conditions built into them. It’s crucial that the Network management system has these MIBs compiled into them to receive any traps sent by the given device/s. The primary focus of this feature is to support SNMP Trap notifications and in particular, linkUp, linkDown and config change trap notifications.

Supported MIBs
  • MIBS added to support SNMP Trap

  • DISMAN-EVENT-MIB.txt

  • INET-ADDRESS-MIB.txt

  • IPV6-TC.txt

  • SNMP-FRAMEWORK-MIB.txt

  • SNMPv2-SMI.txt

  • DISMAN-SCHEDULE-MIB.txt

  • IP-FORWARD-MIB.txt

  • IPV6-UDP-MIB.txt

  • SNMP-MPD-MIB.txt

  • SNMPv2-TC.txt

  • ENTITY-MIB.txt

  • IP-MIB.txt

  • MTA-MIB.txt

  • SNMP-NOTIFICATION-MIB.txt

  • SNMPv2-TM.txt

  • HOST-RESOURCES-MIB.txt

  • IPV6-ICMP-MIB.txt

  • NETWORK-SERVICES-MIB.txt

  • SNMP-TARGET-MIB.txt

  • SNMP-VIEW-BASED-ACM-MIB.txt

  • HOST-RESOURCES-TYPES.txt

  • IPV6-MIB.txt

  • NOTIFICATION-LOG-MIB.txt

  • SNMP-USER-BASED-SM-MIB.txt

  • TCP-MIB.txt

  • IF-MIB.txt

  • IPV6-TCP-MIB.txt

  • SNMP-COMMUNITY-MIB.txt

  • SNMPv2-MIB.txt

  • UDP-MIB.txt

With these MIBs, you can trigger sending an SNMP trap to a configured SNMP-server host based on certain events. Also, GET/GETNext/WALK operations can be supported on these mibs. The linkUp and linkDown traps are sent to the configured host in the event that an interface Admin or Oper status changes from up to down or vice-versa. The configChange trap monitors NPB (MAP, rule, port-npb config) and port (Speed, MTU, FEC, Autoneg) configuration changes. A configChangeTrap PDU is sent to the host when any value in these tables are modified, added or removed.

Reference

Command

[no] snmp-server trap modify <version><ip4addr|ip6addr> [port <value>] [community

<value>]

Description

SNMP trap configuration

Parameters

Version, IPv4 or v6 Address , port, community values

Mode

CONFIG

Example

pbnoscli# configure terminal 
pbnoscli(config)# snmp-server 
  community             Community string authentication
  contact               Configure SNMP contact
  location              Configure SNMP location
  trap                  Trap configuration
  user                  SNMP user
pbnoscli(config)# snmp-server trap 
  cpu-util              CPU utilization
  disk-util             Disk utilization
  fan-util              FAN utilization
  mem-util              Memory utilization
  modify                Modify
  psu-util              PSU utilization
pbnoscli(config)# snmp-server trap modify 
  <version>             Version value
pbnoscli(config)# snmp-server trap modify 2 
  <ipaddr>              A.B.C.D
  <ip6addr>             A:B::C:D
  server-id             Server ID
pbnoscli(config)# snmp-server trap modify 2tr server-id 1 
  <ipaddr>              A.B.C.D
  <ip6addr>             A:B::C:D
pbnoscli(config)# snmp-server trap modify 2 server-id 1 10.2.2.11 port 29 community public
pbnoscli(config)# 

You can verify the configuration by using the command(s) below:

pbnoscli# show snmp-trap            
=====================================================================================
Host          Version       Dest IP         Dest Port    Community     Vrf         
=====================================================================================
1                2	   10.2.2.11         29             public     None      
pbnoscli# 

Traps are only supported on SNMPv2c

Disable PSU/FAN traps:

Below commands can be used to disable FAN/PSU traps temporarily,

Reference

Command

snmp-server trap (psu-util/fan-util) disable

Description

disable PSU/FAN traps temperoraly

Parameters

FAN/PSU

Mode

EXEC

pbnoscli# configure terminal
pbnoscli(config)# snmp
  snmp-server           SNMP server configuration
pbnoscli(config)# snmp-server
  community             Community string authentication
  trap                  Trap configuration
pbnoscli(config)# snmp-server trap
  cpu-util              CPU utilization
  disk-util             Disk utilization
  fan-util              FAN utilization
  mem-util              Memory utilization
  modify                Modify
  psu-util              PSU utilization
pbnoscli(config)# snmp-server trap psu-util
  disable               Disable the PSU traps
pbnoscli(config)# snmp-server trap psu-util 
  disable               Disable the PSU traps. Notify only on state change
pbnoscli(config)# snmp-server trap psu-util disable
pbnoscli(config)# snmp-server trap fan-util disable 
pbnoscli(config)# end
pbnoscli# 

By default, traps are generated every 60 seconds, which may cause unnecessary stress on memory and CPU. To mitigate this, disabling the default behaviour using the above command is recommended for disabling PSU and FAN traps.

This will result in traps being generated only when the PSU/FAN state changes, reducing the load on memory and CPU.

SNMP Trap Logs:

// As received on the SNMP server


//Disk Traps
10.4.5.244.47699 > npbsrv01.snmp: [udp sum ok]  { SNMPv2c C="Aviz" { V2Trap(55) R=755944523  system.sysUpTime.0=5574 S:1.1.4.1.0=88.2.0.3="Current Disk usage 78% falls below threshold 79%" } }
10.4.5.244.47549 > npbsrv01.snmp: [udp sum ok]  { SNMPv2c C="Aviz" { V2Trap(55) R=755944523  system.sysUpTime.0=5574 S:1.1.4.1.0=88.2.0.2="Current Disk usage 88% raised above threshold 80%" } }
10.4.5.244.47239 > npbsrv01.snmp: [udp sum ok]  { SNMPv2c C="Aviz" { V2Trap(55) R=755944523  system.sysUpTime.0=5574 S:1.1.4.1.0=88.2.0.4="Disk /dev/sda3 failed" } }

//CPU Traps
10.4.5.244.49899 > npbsrv01.snmp: [udp sum ok]  { SNMPv2c C="Aviz" { V2Trap(55) R=755944523  system.sysUpTime.0=5574 S:1.1.4.1.0=88.2.0.3="Current CPU usage 70% falling below threshold 80%" } }
10.4.5.244.35699 > npbsrv01.snmp: [udp sum ok]  { SNMPv2c C="Aviz" { V2Trap(55) R=755944523  system.sysUpTime.0=5574 S:1.1.4.1.0=88.2.0.2="Current CPU usage 88% raised above threshold 80%" } }

//Memory Traps
10.4.5.244.47689 > npbsrv01.snmp: [udp sum ok]  { SNMPv2c C="Aviz" { V2Trap(55) R=755944523  system.sysUpTime.0=5574 S:1.1.4.1.0=88.2.0.3="Current mem usage 71% falling below threshold 80%" } }
10.4.5.244.47656 > npbsrv01.snmp: [udp sum ok]  { SNMPv2c C="Aviz" { V2Trap(55) R=755944523  system.sysUpTime.0=5574 S:1.1.4.1.0=88.2.0.2="Current mem usage 88% raised above threshold 80%" } }

//PSU Traps
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(101)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.1 E:58564.2.1.1.1="PSU 2 present, status OK"

//FAN Traps
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan1 present, status OK"
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan2 present, status OK"
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan3 present, status OK"
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan4 present, status OK"
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan5 present, status OK"
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan6 present, status OK"
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan7 present, status OK"
10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(100)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="fan8 present, status OK"

10.4.4.52.32850 > npbsrv01.snmp:  V2Trap(105)  system.sysUpTime.0=42198 S:1.1.4.1.0=E:58564.2.1.1.2 E:58564.2.1.1.2="psu2_fan1 present, status OK"   

pbnoscli# show running-config 
configure terminal
!
interface mgmt
ip address 10.4.4.52/24 gateway 10.4.4.1
!
snmp-server trap modify 2 server-id 1 10.2.2.11 port 29 community public
snmp-server community public
snmp-server trap fan-util disable
snmp-server trap psu-util disable
!
pbnoscli# 
https://support.aviznetworks.com/hc/en-us/articles/6940420122637-SNMP-Overview-and-Traps-Implemented-in-OPB-REL-2-1-0support.aviznetworks.com
Aviz SNMP support