Installation guide

61
Cisco uBR7200 Series Universal Broadband Router Wireless Modem Card and Subsystem Installation and Configuration
78-6030-03
Command Reference
Example
The following example will configure the link so that:
• If more than 3 codeword errors are detected in a given second, that second will be treated as an
errored second.
• If the number of errors detected in one second is between 30 and 150, that second will be flagged as
a degraded second.
• If more than 150 errors are detected in one second, that second will be flagged as a severely errored
second.
• If more than 4 severely errored seconds are detected in sequence, that sequence is flagged as 1
consecutively severely errored second.
UBR04(config-if)# radio metrics-threshold code-word 3 30 150 4
The following example will configure the link alarms so that:
• If the link has 24 errored seconds in one hour, an alarm will be generated.
• If the link was severely errored more than 1 percent of the time in one hour, an alarm will be
generated.
• If the link had more than 12 consecutive severely errored second events in one hour, an alarm will
be generated.
• If the link had more than 5 degraded minutes, an alarm will be generated.
UBR04(config-if)# radio metrics-threshold 1hour 24 36 12 5
radio threshold
Use this command in interface configuration mode to configure a threshold event specification. When
the specified threshold is crossed, an event of type threshParam eventType will be generated and the
event logged to the console.
Only one threshold can be defined for each of the identified threshParam threshType [dsp dspId]
combination. When a threshold is crossed, the threshParam threshType [dsp dspId] combination
identifies the threshold specification that caused the event.
For every threshold defined, antennaNum is conditional. Antenna number is applicable for the
threshParam attributes in, receivedPower, gainSettingsIf, gainSettingsRF, and totalGain.
Note If an antenna number is used when a threshold is created, it must also be specified when it is deleted.
Use the no version of the command to terminate the event-threshold setup. The no radio threshold
command requires the threshParam, threshType, and [dsp dspId] attributes.
For each event, the threshParam [dsp dspId] threshType eventType will be output identifying the
threshold crossed.
radio threshold threshParam antennaNum [dsp dspId] threshType threshValue repeatTime clearTime
no radio threshold threshParam antennaNum [dsp dspId] threshType
Selecting the Correct Data
In most cases, the default DSP should provide acceptable results. Table 13 outlines for which DSPs the
statistical parameters are most meaningful.