Dell PowerEdge VRTX Chassis Management Controller Version 1.0 for Dell PowerEd - Page 93

Configuring SNMP Trap Alert Destinations Using RACADM, IPv4, or Fully-Qualified Domain Names FQDNs.

Get Dell PowerEdge VRTX PDF manuals and user guides View all Dell PowerEdge VRTX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 93 highlights

management stations. The community string on the Chassis Overview → Network → Services page is the community string that management stations use to query the SNMP daemon on CMC. - Under Enabled , select the option corresponding to the destination IP to enable the IP address to receive the traps. You can specify up to four IP addresses. 3. Click Apply to save the settings. 4. To test whether the IP address is receiving the SNMP traps, click Send in the Test SNMP Trap column. The IP alert destinations are configured. Configuring SNMP Trap Alert Destinations Using RACADM To configure IP alert destination using RACADM: 1. Open a serial/Telnet/SSH text console to CMC and log in. NOTE: Only one filter mask may be set for both SNMP and email alerting. If you have already selected the filter mask, do not perform task 2, and go to step 3. 2. Enable alert generation: racadm config -g cfgAlerting -o cfgAlertingEnable 1 3. Specify the events filters by running the racadm eventfilters set command. a) To clear all the available alert settings, run the following command: racadm eventfilters set -c cmc.alert.all -n none b) Configure using severity as a parameter. For example, all informational events in storage category are assigned poweroff as action, and email and SNMP as notifications: racadm eventfilters set -c cmc.alert.storage.info -n email,snmp c) Configure using subcategory as a parameter. For example, all configurations under the licensing subcategory in the audit category are assigned poweroff as action and all notifications are enabled: racadm eventfilters set -c cmc.alert.audit.lic -n all d) Configure using subcategory and severity as parameters. For example, all Information events under the licensing subcategory in the audit category are assigned poweroff as action and all notifications are disabled: racadm eventfilters set -c cmc.alert.audit.lic.info -n none 4. Enable traps alerts: racadm config -g cfgTraps -o cfgTrapsEnable 1 -i where is a value between 1-4. CMC uses the index number to distinguish up to four configurable destinations for traps alerts. Destinations may be specified as appropriately formatted numeric addresses (IPv6 or IPv4), or Fully-Qualified Domain Names (FQDNs). 5. Specify a destination IP address to receive the traps alert: racadm config -g cfgTraps -o cfgTrapsAlertDestIPAddr -i where is a valid destination, and is the index value specified in step 4. 6. Specify the community name: racadm config -g cfgTraps -o cfgTrapsCommunityName -i where is the SNMP community to which the chassis belongs, and is the index value specified in steps 4 and 5. You can configure up to four destinations to receive traps alerts. To add more destinations, do the tasks in steps 2- 6. NOTE: The commands in steps 2-6 overwrites any existing settings configured for the index specified (1-4). To determine whether an index has previously-configured values, type: racadm getconfig -g cfgTraps -i . If the index is configured, values appear for the cfgTrapsAlertDestIPAddr and cfgTrapsCommunityName objects. 93

  • 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
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
management stations. The community string on the
Chassis Overview
→
Network
→
Services
page is the
community string that management stations use to query the SNMP daemon on CMC.
–
Under
Enabled
, select the option corresponding to the destination IP to enable the IP address to receive
the traps. You can specify up to four IP addresses.
3.
Click
Apply
to save the settings.
4.
To test whether the IP address is receiving the SNMP traps, click
Send
in the
Test SNMP Trap
column.
The IP alert destinations are configured.
Configuring SNMP Trap Alert Destinations Using RACADM
To configure IP alert destination using RACADM:
1.
Open a serial/Telnet/SSH text console to CMC and log in.
NOTE:
Only one filter mask may be set for both SNMP and email alerting. If you have already selected the
filter mask, do not perform task 2, and go to step 3.
2.
Enable alert generation:
racadm config -g cfgAlerting -o cfgAlertingEnable 1
3.
Specify the events filters by running the
racadm eventfilters set
command.
a)
To clear all the available alert settings, run the following command:
racadm eventfilters set -c
cmc.alert.all -n none
b)
Configure using severity as a parameter. For example, all informational events in storage category are assigned
poweroff as action, and email and SNMP as notifications:
racadm eventfilters set -c
cmc.alert.storage.info -n email,snmp
c)
Configure using subcategory as a parameter. For example, all configurations under the licensing subcategory in
the audit category are assigned poweroff as action and all notifications are enabled:
racadm
eventfilters set -c cmc.alert.audit.lic -n all
d)
Configure using subcategory and severity as parameters. For example, all Information events under the
licensing subcategory in the audit category are assigned poweroff as action and all notifications are disabled:
racadm eventfilters set -c cmc.alert.audit.lic.info -n none
4.
Enable traps alerts:
racadm config -g cfgTraps -o cfgTrapsEnable 1 -i <index>
where
<index>
is a value between 1–4. CMC uses the index number to distinguish up to four configurable
destinations for traps alerts. Destinations may be specified as appropriately formatted numeric addresses (IPv6 or
IPv4), or Fully-Qualified Domain Names (FQDNs).
5.
Specify a destination IP address to receive the traps alert:
racadm config -g cfgTraps -o cfgTrapsAlertDestIPAddr <IP address> -i <index>
where
<IP address>
is a valid destination, and
<index>
is the index value specified in step 4.
6.
Specify the community name:
racadm config -g cfgTraps -o cfgTrapsCommunityName <community name> -i
<index>
where
<community name>
is the SNMP community to which the chassis belongs, and
<index>
is the index
value specified in steps 4 and 5.
You can configure up to four destinations to receive traps alerts. To add more destinations, do the tasks in steps 2–
6.
NOTE:
The commands in steps 2–6 overwrites any existing settings configured for the index specified (1–4). To
determine whether an index has previously-configured values, type:
racadm getconfig -g
cfgTraps -i <index>
. If the index is configured, values appear for the
cfgTrapsAlertDestIPAddr
and
cfgTrapsCommunityName
objects.
93