Search

1 to 10 of 21
Sort by

Blog Entry
FAQ: SNMP Traps and Informs

For a list of standard SNMP Version1 traps, click Standard SNMP Version 1 Traps. For a list of standard SNMP Version 2 traps, click Standard SNMP Version 2 Traps...Can I simulate traps on a device?


Discussion Post
Traps on a EX-2300 switch - BPDU - how to send a trap on enable

So we have a trap receiver set up and we are sending BPDU traps to it


Discussion Thread 5
Traps on a EX-2300 switch - BPDU - how to send a trap on enable

Focus Search - Traps on a EX-2300 switch - BPDU - how to send a trap on enable


Blog Entry
How To: Generate SNMP Traps from System Alarms

Overview Generate SNMP traps from syslog events. Description Not all Juniper Junos OS alarms automatically generate SNMP notifications (traps or informs). You can generate SNMP notifications for syslog events by using the event-options and raise-trap CLI statements in an event policy. Example Configuration An ESX switch has a warm temperature event occur, which causes an amber system alarm and the following syslog messages: Mar 2 11:04:41 switch2 alarmd[1329]: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 3 EX-PFE2 Temp Too Warm Mar 2 11:04:41 switch2 craftd[1330]: Minor alarm set, FPC 3 EX-PFE2 Temp Too Warm Mar 2 11:07:29 switch2 craftd[1330]: Minor alarm cleared, FPC 3 EX-PFE2 Temp Too Warm Mar 2 11:07:29 switch2 alarmd[1329]: Alarm cleared: FPC color=YELLOW, class=CHASSIS, reason=FPC 3 EX-PFE2 Temp Too Warm The following configuration sends SNMP traps for those syslog alarm messages: event-options ( policy alarms ( events SYSTEM; attributes-match ( system.message matches "alarm set"; ) then ( raise-trap; ) ) ) NOTE: This example assumes you have already configured your system to generate SNMP notifications. Further Reading You can find out more about event policies from the following resources: Example: Configuring Event Policies to Raise SNMP Traps Day One: Applying Junos Event Automation (p 50) #FAQ #SNMP #DayOne


Blog Entry
How-To: Raise SNMP traps using event policy

To raise an SNMP trap on occurrence of an event following configuration, use the following: 1 [edit] 2 user@host# show event-options 3 policy <policy-name> ( 4 events <event-name>; 5 then ( 6 raise-trap; 7 ) 8 ) 9 10 [edit] 11 user@host# As per the above configuration, when a specified event occurs in the system, this policy is executed and an SNMP trap will be raised


Discussion Thread 2
How to filter certain trap OIDs using SNMP v2?

Focus Search - How to filter certain trap OIDs using SNMP v2?


Discussion Post
How to filter certain trap OIDs using SNMP v2?

I'm working with an MX480 and curious if it's possible to filter out certain SNMP trap OIDs while using SNMP v2. I found a Juniper article that gives details on how to configure this for SNMP v3, but I'm lost when trying to set up this up for v2 - https://www.juniper.net/documentation/en US/junos/topics/task/configuration/snmp-best-practices-traps-and-informs-managing.html Here's a redacted example of my current config. This works well, but there's a variety of traps that I'd like to filter out, but don't want to remove the whole trap category to do so


Blog Entry
Scripting How-To: Raise SNMP traps using event policy

To raise an SNMP trap on occurrence of an event following configuration, use the following: 1 [edit] 2 user@host # show event-options 3 policy <policy-name> ( 4 events <event-name>; 5 then ( 6 raise- trap ; 7 ) 8 ) 9 10 [edit] 11 user@host # As per the above configuration, when a specified event occurs in the system, this policy is executed and an SNMP trap will be raised


Blog Entry
Scripting How-To: Sending an SNMP Alert in Case of a Routing Process Failure in EX4500 Switches

In Juniper Networks EX4500 switches, you can configure an event policy action that triggers SNMP traps. It is possible to send an SNMP trap when a routing process fails if routing process failure is a listed event in the system log


Discussion Post
If Syslog not sent

Implied logic : JunOS device determines that there's no syslog sent to remote host (last day for example) Then it generates custom syslog/SNMP trap based on this problem...#syslog #SNMP #trap