HP 6125G HP 6125G & 6125G/XG Blade Switches Network Management and Mon - Page 158

reaction checked-element probe-fail (for trigger

Page 158 highlights

entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated and sent to the network management server. system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type icmp-echo [Sysname-nqa-admin-test-icmp-echo] reaction 2 checked-element probe-fail threshold-type consecutive 10 action-type trap-only reaction checked-element probe-fail (for trigger) Syntax reaction item-number checked-element probe-fail threshold-type consecutive consecutive-occurrences action-type trigger-only View undo reaction item-number DHCP, DNS, DLSw, FTP, HTTP, ICMP echo, SNMP, TCP, UDP echo operation view Default level 2: System level Parameters item-number: Specifies a reaction entry ID, in the range of 1 to 10. threshold-type: Specifies a threshold type. consecutive consecutive-occurrences: Specifies the number of consecutive probe failures since the test group starts. The value is in the range of 1 to 16. action-type: Specifies what actions to be triggered to react to certain measurement conditions. trigger-only: Triggers other modules to react to certain conditions. Description Use reaction checked-element probe-fail to configure a reaction entry for monitoring the probe results of the current test group. If the number of consecutive probe failures reaches the threshold, collaboration with other modules is triggered. You cannot edit a reaction entry. To change the attributes in a reaction entry, use undo reaction to delete this entire entry and start over. Use undo reaction to remove the specified reaction entry. By default, no reaction entries are configured. The collaboration function is not supported by UDP jitter or voice tests. Related commands: track (High Availability Command Reference). Examples # Create reaction entry 1. If probe failure occurs consecutively for 3 times, collaboration with other modules is triggered. system-view [Sysname] nqa entry admin test [Sysname-nqa-admin-test] type tcp [Sysname-nqa-admin-test-tcp] reaction 1 checked-element probe-fail threshold-type consecutive 3 action-type trigger-only 152

  • 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
  • 194
  • 195
  • 196

152
entry is set to below-threshold. Once the state of the reaction entry changes, a trap message is generated
and sent to the network management server.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] reaction 2 checked-element probe-fail threshold-type
consecutive 10 action-type trap-only
reaction checked-element probe-fail (for trigger)
Syntax
reaction
item-number
checked-element probe-fail threshold-type consecutive
consecutive-occurrences
action-type
trigger-only
undo reaction
item-number
View
DHCP, DNS, DLSw, FTP, HTTP, ICMP echo, SNMP, TCP, UDP echo operation view
Default level
2: System level
Parameters
item-number
: Specifies a reaction entry ID, in the range of 1 to 10.
threshold-type
: Specifies a threshold type.
consecutive
consecutive-occurrences
: Specifies the number of consecutive probe failures since the test
group starts. The value is in the range of 1 to 16.
action-type
: Specifies what actions to be triggered to react to certain measurement conditions.
trigger-only
: Triggers other modules to react to certain conditions.
Description
Use
reaction checked-element probe-fail
to configure a reaction entry for monitoring the probe results of
the current test group. If the number of consecutive probe failures reaches the threshold, collaboration
with other modules is triggered. You cannot edit a reaction entry. To change the attributes in a reaction
entry, use
undo reaction
to delete this entire entry and start over.
Use
undo reaction
to remove the specified reaction entry.
By default, no reaction entries are configured.
The collaboration function is not supported by UDP jitter or voice tests.
Related commands:
track
(High Availability Command Reference).
Examples
# Create reaction entry 1. If probe failure occurs consecutively for 3 times, collaboration with other
modules is triggered.
<Sysname> system-view
[Sysname] nqa entry admin test
[Sysname-nqa-admin-test] type tcp
[Sysname-nqa-admin-test-tcp] reaction 1 checked-element probe-fail threshold-type
consecutive 3 action-type trigger-only