HP GbE2c HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Gu - Page 138

RMON group 9—events, Configuring RMON Events (CLI example)

Page 138 highlights

3. Apply, verify, and save the configuration. RMON group 9-events The RMON Event group allows you to define events that are triggered by alarms. An event can be a log message, an SNMP trap message, or both. When an alarm is generated, it triggers a corresponding event notification. Use the /cfg/rmon/alarm x/revtidx and /fevtidx commands to correlate an event index to an alarm. RMON events use SNMP and syslogs to send notifications. Therefore, an SNMP trap host must be configured for trap event notification to work properly. RMON uses a SYSLOG host to send syslog messages. Therefore, an existing SYSLOG host (/cfg/sys/syslog) must be configured for event log notification to work properly. Each log event generates a SYSLOG of type RMON that corresponds to the event. Configuring RMON Events (CLI example) 1. Configure the RMON Event parameters. >> /cfg/rmon/event 5 (Select RMON Event 5) >> RMON Event 5# descn "SYSLOG_generation_event" >> RMON Event 5# type log >> RMON Event 5# owner "Owner_event_5" 2. Apply and save the configuration. >> RMON Alarm 5# apply >> RMON Alarm 5# save (Make your changes active) (Save for restore after reboot) This configuration creates an RMON event that sends a SYSLOG message each time it is triggered by an alarm. Remote monitoring 138

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165

Remote monitoring 138
3.
Apply, verify, and save the configuration.
RMON group 9—events
The RMON Event group allows you to define events that are triggered by alarms. An event can be a log message, an
SNMP trap message, or both.
When an alarm is generated, it triggers a corresponding event notification. Use the
/cfg/rmon/alarm
x/revtidx
and
/fevtidx
commands to correlate an event index to an alarm.
RMON events use SNMP and syslogs to send notifications. Therefore, an SNMP trap host must be configured for trap
event notification to work properly.
RMON uses a SYSLOG host to send syslog messages. Therefore, an existing SYSLOG host (
/cfg/sys/syslog
)
must be configured for event log notification to work properly. Each log event generates a SYSLOG of type RMON
that corresponds to the event.
Configuring RMON Events (CLI example)
1.
Configure the RMON Event parameters.
>> /cfg/rmon/event 5
(Select RMON Event 5)
>> RMON Event 5# descn "SYSLOG_generation_event"
>> RMON Event 5# type log
>> RMON Event 5# owner “Owner_event_5”
2.
Apply and save the configuration.
>> RMON Alarm 5# apply
(Make your changes active)
>> RMON Alarm 5# save
(Save for restore after reboot)
This configuration creates an RMON event that sends a SYSLOG message each time it is triggered by an alarm.