HP 6125XLG R2306-HP 6125XLG Blade Switch Network Management and Monitoring Con - Page 92

Configuring threshold monitoring, Threshold types, Triggered actions, Reaction entry

Page 92 highlights

Step 2. Create an NQA operation and enter NQA operation view. 3. Specify an NQA operation type and enter its view. 4. Configure a reaction entry. 5. Exit to system view. 6. Associate Track with NQA. 7. Associate Track with an application module. Command nqa entry admin-name operation-tag type { icmp-echo | udp-echo } reaction item-number checked-element probe-fail threshold-type consecutive consecutive-occurrences action-type trigger-only quit See High Availability Configuration Guide. See High Availability Configuration Guide. Remarks By default, no NQA operation is created. N/A By default, no reaction entry is configured. You cannot modify the content of an existing reaction entry. N/A N/A N/A Configuring threshold monitoring Threshold types An NQA operation supports the following threshold types: • average-If the average value for the monitored performance metric either exceeds the upper threshold or goes below the lower threshold, a threshold violation occurs. • accumulate-If the total number of times that the monitored performance metric is out of the specified value range reaches or exceeds the specified threshold, a threshold violation occurs. • consecutive-If the number of consecutive times that the monitored performance metric is out of the specified value range reaches or exceeds the specified threshold, a threshold violation occurs. Threshold violations for the average or accumulate threshold type are determined on a per NQA operation basis, and threshold violations for the consecutive type are determined from the time the NQA operation starts. Triggered actions The following actions may be triggered: • none-NQA displays results only on the terminal screen. • trigger-only-NQA displays results on the terminal screen, and meanwhile triggers other modules for collaboration. Reaction entry In a reaction entry, a monitored element, a threshold type, and an action to be triggered are configured to implement threshold monitoring. The state of a reaction entry can be invalid, over-threshold, or below-threshold. 86

  • 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

86
Step
Command
Remarks
2.
Create an NQA operation
and enter NQA operation
view.
nqa
entry
admin-name
operation-tag
By default, no NQA operation is
created.
3.
Specify an NQA operation
type and enter its view.
type
{
icmp-echo
|
udp-echo
}
N/A
4.
Configure a reaction entry.
reaction
item-number
checked-element
probe-fail
threshold-type consecutive
consecutive-occurrences
action-type
trigger-only
By default, no reaction entry is
configured.
You cannot modify the content of
an existing reaction entry.
5.
Exit to system view.
quit
N/A
6.
Associate Track with NQA.
See High Availability
Configuration Guide.
N/A
7.
Associate Track with an
application module.
See High Availability
Configuration Guide.
N/A
Configuring threshold monitoring
Threshold types
An NQA operation supports the following threshold types:
average
—If the average value for the monitored performance metric either exceeds the upper
threshold or goes below the lower threshold, a threshold violation occurs.
accumulate
—If the total number of times that the monitored performance metric is out of the
specified value range reaches or exceeds the specified threshold, a threshold violation occurs.
consecutive
—If the number of consecutive times that the monitored performance metric is out of the
specified value range reaches or exceeds the specified threshold, a threshold violation occurs.
Threshold violations for the average or accumulate threshold type are determined on a per NQA
operation basis, and threshold violations for the consecutive type are determined from the time the NQA
operation starts.
Triggered actions
The following actions may be triggered:
none
—NQA displays results only on the terminal screen.
trigger-only
—NQA displays results on the terminal screen, and meanwhile triggers other modules
for collaboration.
Reaction entry
In a reaction entry, a monitored element, a threshold type, and an action to be triggered are configured
to implement threshold monitoring.
The state of a reaction entry can be invalid, over-threshold, or below-threshold.