In this section:
The SBC, like other Ribbon devices, uses SNMP traps to notify management applications of events. SNMP traps are the messages that notify a management client that an event has occurred on the SBC node. These traps are not displayed in EMA and can be viewed from RAMP or other SNMP manager configured as a trap target. In case of error scenario, a trap is initiated at the device and forwarded to RAMP or another SNMP manager for processing.
You can configure up to 32 trap targets on the SBC.
The supported configurable SNMP trap types are SNMP v1, v2, and v3.
The following command is executed in CLI to configure the SNMP traps:
% set oam snmp trapTarget myTarget ipAddress <ip address> state enabled
The page RAMPDOC2412:Fault Management was not found -- Please check/update the page name used in the MultiExcerpt-Include macro
Refer to the RAMP document Fault Management for details.
Perform the following steps to create a view:
Select Fault Manager from the Network Mgmnt roll-up (left hand side of the Users & Roles window). The Fault Manager window appears.
View Creation
In the Bars option, select Create.
Device selection for view creation
Click Save. The view is saved and displayed in the left side pane.
Saved View
Perform the following steps to view the traps:
Select the view from the Views drop-down menu. Click Open. The view is displayed.
View Traps
Double-click the Total Events bar. The Event Names appear for the selected device.
Viewing Traps
Perform the following steps to clear a trap:
Select the trap to be cleared.
Select alarm to clear
Select Clear from the Operations drop-down menu. The trap is cleared from the list.
Cleared alarm
The SBC supports following generic SNMP traps apart from the application specific traps or alarms:
The traps are triggered under specific conditions. For detailed information about these traps, refer to the relevant Trap page using the links provided in the table below.
Generic SNMP Trap Support
Generic SNMP Trap | Conditions |
---|---|
authenticationFailure - MINOR | When an SNMP request with mismatch of community name is received. |
coldStart - INFORMATIONAL | When an SNMP entity has reinitialized itself and its configuration might have been altered. |
linkDown - CRITICAL | When an SNMP entity detects that one of its communication links is down. |
linkUp - INFORMATIONAL | When an SNMP entity detects that one of its lost communication links is reinstated. |