H3c-technologies H3C MSR 5600 Manual de usuario Pagina 37

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 247
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 36
24
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
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 { dhcp | dlsw | dns | ftp |
http | icmp-echo | snmp | tcp |
udp-echo }
The collaboration function is not
available for the path jitter, UDP
jitter, and voice operations.
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 might be triggered:
none—NQA displays results only on the terminal screen. It does not send traps to the NMS.
trap-only—NQA displays results on the terminal screen, and meanwhile it sends traps to the NMS.
trigger-only—NQA displays results on the terminal screen, and meanwhile triggers other modules
for collaboration.
The DNS operation does not support the action of sending trap messages.
Reaction entry
In a reaction entry, a monitored element, a threshold type, and an action to be triggered are configured
to implement threshold monitoring.
Vista de pagina 36
1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 246 247

Comentarios a estos manuales

Sin comentarios