SNMP Configuration for Alarm MIB Support

Overview

OcNOS has an alarm data model that defines the structure and information made available to the user upon request, either through NetConf get operations or notifications.

This feature also enables checking active alarm information through SNMP operations, using SNMP get commands or SNMP traps.

Feature Characteristics

• This feature allows the system to provide alarm notifications through SNMP traps in addition to NetConf.
• The SNMP trap option is disabled by default. It can be enabled or disabled at any time using either the CLI or NetConf.
• The system also allows verification of the SNMP trap notification status (enabled or disabled) through the CLI or NetConf.

Benefits

• This feature adds an SNMP interface to the alarm data model in OcNOS.
• It provides support for snmpwalk and snmpget operations, as well as SNMP trap generation.

Prerequisites

To check alarms in OcNOS through NetConf or SNMP, FMS needs to be enabled first.

Configuration

Topology

• Enable FMS.
Copy 
OcNOS(config)# fault-management enable
• Configure the logging level for all modules to level 5.
Copy 
OcNOS(config)# logging level all 5
OcNOS(config)#commit
OcNOS(config)#

Validation

Copy 
OcNOS#show running-config fault-management
!
fault-management enable
!
OcNOS#show running-config logging
logging level all 5
!
!
OcNOS#

Use the following command to validate the configuration:

Copy 
OcNOS#show fms status 
% FMS Status: Enabled 
% FMS Node Application Status: Up 
OcNOS#

Implementation Examples

Along with FMS configuration, configure SNMP in OcNOS to test this feature.

In this example, the management VRF is used for SNMP configuration. However, it is not mandatory to use the management VRF. SNMP can also be configured on other VRFs as required.

Copy 
OcNOS(config)#snmp-server enable snmp vrf management
OcNOS(config)#snmp-server view all .1 included vrf management
OcNOS(config)#snmp-server community test vrf management
OcNOS(config)#commit
OcNOS(config)#

Execute the following command to enable or disable the transmission of alarm notifications through SNMP traps:

Copy 
OcNOS(config)#[no] snmp-server enable traps alarms
OcNOS(config)#commit
OcNOS(config)#

Validation

Copy 
OcNOS#show running-config snmp
!
…
snmp-server enable snmp vrf management
snmp-server view all .1 included vrf management
snmp-server community test vrf management
snmp-server enable traps alarms
...
!
end
OcNOS#

Execute the following command to validate the configuration.

Copy 
OcNOS#show snmp trap
-------------------------------------------------
Trap type    Description    Enabled
---------------------------------------------------
link         linkUp         no
link         linkDown       no
link         linkWithIfname no
vxlan        notification   no
mpls         notification   no
mpls         pw             no
mpls         pw delete      no
mpls-l3vpn   notification   no
ospf         notification   no
ospf6        notification   no
isis         notification   no
snmp         authentication no
mpls         rsvp           no
pim          notification   no
twamp        notification   no
syslog       notification   no
alarms       notification   yes 
vrrp         notification   no
rib          notification   no
bgp          notification   no
OcNOS#

Raise alarms in OcNOS (for example, by performing a link down and link up operation on any interface) and verify the alarm information using an SNMP client such as snmpwalk.

Copy 
root@OcNOS:~# snmpwalk -Ln -m ALL -v2c -c  test 127.0.0.1 1.3.6.1.4.1.36673.3400

To verify the transmission of alarm traps and informs, use an SNMP client tool to receive the messages. Additional configuration might be required. The host IP address should correspond to the system where the SNMP client receives the traps.

Alarm traps are not supported in SNMPv1.

Copy 
OcNOS(config)#snmp-server host 172.30.4.4 traps version 2c test vrf management host-vrf management
OcNOS(config)#commit
OcNOS(config)#
Copy 
OcNOS#show running-config snmp
!
…
snmp-server enable snmp vrf management
snmp-server view all .1 included vrf management
snmp-server community test vrf management
snmp-server host 172.30.4.4 traps version 2c test vrf management host-vrf management
snmp-server enable traps alarms
...
!
end
OcNOS#

To enable the delivery of SNMP traps to an external client at IP address 172.30.4.4, configure the host and the associated routing context using the following command:

Copy 
OcNOS(config)# snmp-server host 172.30.4.4 test vrf management host-vrf management

Raise alarms in OcNOS and verify that SNMP traps and SNMP informs are sent to the SNMP client running on the host.

Copy 
OcNOS(config) # int xe0.2
OcNOS(config-if)# shut
OcNOS(config-if)# commit
root@rtxpv6ld03:/home/xsun1# tcpdump -i any -nn src 172.30.4.1 and  udp and dst port 162
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes

01:16:01.878619 ethertype IPv4, IP 172.30.4.1.42392 > 172.30.4.4.162:  C="test" 
V2Trap(163)  .1.3.6.1.2.1.1.3.0=10792200 
.1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.36673.2.30.0.2.2 
.1.3.6.1.4.1.36673.2.1.1.2.1.1.1=327811074 .1.3.6.1.4.1.36673.2.1.1.2.1.1.2=ec_0a_79_0c 
.1.3.6.1.4.1.36673.2.1.1.1.1.1.3=2 .1.3.6.1.2.1.1.5.0="S9600-28DX-1-5B"

01:16:01.878619 IP 172.30.4.1.42392 > 172.30.4.4.162:  C="test" V2Trap(163)  
.1.3.6.1.2.1.1.3.0=10792200 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.36673.2.30.0.2.2 
.1.3.6.1.4.1.36673.2.1.1.2.1.1.1=327811074 .1.3.6.1.4.1.36673.2.1.1.2.1.1.2=ec_0a_79_0c 
.1.3.6.1.4.1.36673.2.1.1.1.1.1.3=2 .1.3.6.1.2.1.1.5.0="S9600-28DX-1-5B"

01:16:03.760458 ethertype IPv4, IP 172.30.4.1.42392 > 172.30.4.4.162:  C="test" V2Trap(378)  
.1.3.6.1.2.1.1.3.0=10792300 
.1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.36673.3400.0.1 .1.3.6.1.2.1.1.5.0="S9600-28DX-1-5B" 
.1.3.6.1.4.1.36673.3400.1.1.1="IFMGR_IF_DOWN::xe0.2" .1.3.6.1.4.1.36673.3400.1.1.2="xe0.2" 
.1.3.6.1.4.1.36673.3400.1.1.3="S9600-28DX-1-5B [IFMGR_IF_DOWN] Interface xe0.2 changed state to down" 
.1.3.6.1.4.1.36673.3400.1.1.4=1763018041764 .1.3.6.1.4.1.36673.3400.1.1.5="Thu Nov 13 2025 07:14:01.764 UTC" 
.1.3.6.1.4.1.36673.3400.1.1.6=1 .1.3.6.1.4.1.36673.3400.1.1.7=1 
.1.3.6.1.4.1.36673.3400.1.1.8=0

01:16:03.760458 IP 172.30.4.1.42392 > 172.30.4.4.162:  C="test" V2Trap(378)  
.1.3.6.1.2.1.1.3.0=10792300 .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.36673.3400.0.1 
.1.3.6.1.2.1.1.5.0="S9600-28DX-1-5B" .1.3.6.1.4.1.36673.3400.1.1.1="IFMGR_IF_DOWN::xe0.2" 
.1.3.6.1.4.1.36673.3400.1.1.2="xe0.2" .1.3.6.1.4.1.36673.3400.1.1.3="S9600-28DX-1-5B 
[IFMGR_IF_DOWN] Interface xe0.2 changed state to down" 
.1.3.6.1.4.1.36673.3400.1.1.4=1763018041764 .1.3.6.1.4.1.36673.3400.1.1.5="Thu Nov 13 2025 07:14:01.764 UTC" 
.1.3.6.1.4.1.36673.3400.1.1.6=1 .1.3.6.1.4.1.36673.3400.1.1.7=1 .1.3.6.1.4.1.36673.3400.1.1.8=0

The following SNMP attributes must be included in all generated SNMP Traps and must be visible during an SNMP Walk whenever there are active alarms present in the system.

Copy 
ipiAlarmsAlarmId
ipiAlarmsAlarmResource
ipiAlarmsAlarmText
ipiAlarmsAlarmTimeCreated
ipiAlarmsAlarmAlarmReportedTimestamp
ipiAlarmsAlarmAlarmSeverity
ipiAlarmsAlarmTypeId

Troubleshooting

After downgrading to a previous version of OcNOS, alarm notification transmission through SNMP cannot be enabled.

Glossary

Key Terms/Acronym Description
FMS Fault Management System
MIB Management Information Base