|
|
This feature module was incomplete at print time. As soon as all information is complete, this document will be updated.
The Cisco high-speed point-to-point broadband fixed wireless system provides a fixed, dedicated wireless link from one site to another. This link delivers full-duplex data in the licensed MMDS band (2.500 to 2.690 GHz), or unlicensed U-NII band (5.725 to 5.825 GHz).
The broadband fixed wireless system consists of a Cisco uBR7200 series universal broadband router (Cisco uBR7246 or Cisco uBR7223) and one or more wireless modem cards, each with a power feed panel, and one or two wireless transverters.
The wireless modem cards are installed in a Cisco uBR7200 series router. Each modem card is cabled to a power feed panel installed either in the same equipment rack as the router or mounted on a wall. Cables from the power feed panel are attached to one or two wireless transverters, which are installed on antenna masts. The system is managed via a command-line interface (CLI) or CiscoView.
The wireless modem card provides the control and data interface between the system's digital motherboard and the radio frequency (RF) subsystem in the wireless transverter. It also provides the up/down conversion from baseband to intermediate frequency (IF).
The wireless transverter is the control and data interface to the indoor subsystems. It provides up/down conversion from IF to RF frequencies and power amplification.
The point-to-point wireless router system is a cost effective, high bandwidth access solution.
Cisco uBR7200 Series Universal Broadband Router Wireless Modem Card and Subsystem Installation and Configuration (Part Number 78-6030-01)
uBR7200
No new or modified standards are supported by this feature.
No new or modified MIBs are supported by this feature.
No new or modified RFCs are supported by this feature.
See the following sections for configuration tasks for the point-to-point wireless router system.Each task in the list indicates if the task is optional or required.
An IF loopback confirms that the hardware is seated properly in the chassis and that the wireless modem card is functioning as expected.
Use the following commands to execute an IF loopback. These commands will shut down the radio link and initiate the IF loopback.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| UBR1(config-if)# shut | Stops the interface. | ||
| UBR1(config-if)# loopback local if | Starts the loopback. | ||
| UBR1(config-if)# no shut | Restarts the interface. |
An RF loopback confirms that the wiring to the transverter is correct, communication has been established and that the transverter appears to be operating correctly. (It does not test the duplexer, which is the final stage before the signal is sent to the antenna.) Because there is only one transmit path, the path to each transverter must be tested separately. Use the following commands:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| UBR1(config-if)# shut | Stops the interface. | ||
| UBR1(config-if)# loopback local rf main | Starts the loopback. | ||
| UBR1(config-if)# loopback local rf diversity | A loopback to the diversity transverter should be initiated if the loopback does not start (and the Carrier and Out of Service LEDs do not light). Also examine the data cable, the control cable, and the power supply for faults. | ||
| UBR1(config-if)# no shut | Restarts the interface. |
The antenna-alignment command sends a voltage proportional to the received signal strength to the transverter.
| Step | Command | Purpose | ||
|---|---|---|---|---|
| UBR2(config-if)# no shut | Turns on the transmit signal from uBR2. | ||
| UBR1(config-if)# shut | Stops the interface. | ||
| UBR1(config-if)# radio antenna-alignment | Aligns antenna on uBR1. | ||
| UBR1(config-if)# no shut | Restarts the interface. | ||
| UBR1(config-if)# no shut | Turns on the transmit signal from uBR1. | ||
| UBR2(config-if)# shut | Stops the interface. | ||
| UBR2(config-if)# radio antenna-alignment | Aligns antenna on uBR2. | ||
| UBR2(config-if)# no shut | Restarts the interface. | ||
| | Exits interface configuration mode. | ||
| | Exits global configuration mode. | ||
| UBR1# ping ip address | Tests the link on uBR1. | ||
| | Exits interface configuration mode. | ||
| | Exits global configuration mode. | ||
| UBR2# ping ip address | Tests the link on uBR2. |
These steps help determine the throughput setting by trying each setting and choosing the one that gives acceptable error performance.
To use the simplified procedure:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| | Initiates the link using the low throughput setting | ||
| | Clears the link-metrics counters. | ||
| U | Checks the error performance of the link. | ||
| UBR1(config-if)# no shut | Restarts the interface. | ||
| UBR1(config-if)# no shut | Turns on the transmit signal from uBR1. | ||
| UBR2(config-if)# shut | Stops the interface. | ||
| UBR2(config-if)# radio antenna-alignment | Aligns antenna on uBR2. | ||
| UBR2(config-if)# no shut | Restarts the interface. | ||
| | Exits interface configuration mode. | ||
| | Exits global configuration mode. | ||
| UBR1# ping ip address | Tests the link on uBR1. | ||
| | Exits interface configuration mode. | ||
| | Exits global configuration mode. | ||
| UBR2# ping ip address | Tests the link on uBR2. |
To use the expert procedure
| Step | Command | Purpose | ||
|---|---|---|---|---|
| | Initiates the link using the low throughput setting. | ||
| | Measures the multipath delay spread of the channel by examining the channel impulse response. | ||
| | Measures the SINR of the received signal by examining the constellation variance histogram. Choose the throughput setting that is appropriate for the measured multipath delay spread and SINR. See the Cisco uBR7200 Series Universal Broadband Router Wireless Modem Card and Subsystem Installation and Configuration Guide for setting values. | ||
| | Clears the link-metrics counters. | ||
|
| Tests the accuracy of the selected throughput setting by checking the error performance of the link. |
Step 1 Use the show running-configuration command in privileged EXEC mode to display the configuration currently in effect on the Cisco uBR7200 series router.
Step 2 Use the show startup-configuration command in privileged EXEC mode to display the system startup configuration.
Step 3 If you reissue the show running-configuration command, you will see that dual antenna IF loopback has been selected. This is appropriate even if you are using a single antenna system.
Step 4 If you are using two antennas and problems occur with the dual antenna command, reissue the command specifying loopback local if main or loopback local if diversity to help isolate the problem.
Step 5 It may also be helpful to run a power-on self test (POST). The POST configured to run either once or every time the link is initiated. The following commands configure a self-test to run when the first no shut command is entered.
UBR1(config-if)# shut UBR1(config-if)# radio self-test UBR1(config-if)# no shut
This section provides the following configuration examples:
Following is an example of the running configuration for the "master" end of a 6-MHz high-throughput link with a single antenna. In these examples, UBR1 and UBR2 refer to the two Cisco uBR7200 series routers used at the ends of the radio link. The wireless modem cards are assumed to be in slot 6 of each of the routers. The reference to radio 6/0 indicates that this interface occupies slot 6 and port 0.
The "slave" end of the link (UBR2) is configured in the same way except that the radio master command is omitted and the transmit and receive frequencies are reversed in the radio operating-band command.
UBR1# show running-configuration interface radio 6/0 Current configuration: ! interface Radio6/0 ip address 10.0.0.1 255.255.255.0 radio master radio receive-antennas 1 radio operating-band tx 2506.00 rx 2542.00 radio channel-setup bandwidth 6.0 throughput high radio transmit-power 15 end
This section gives an example of an RF-to-RF link operating at 6 MHz/high. This example assumes that the IF cable-loss for uBR1 and uBR2 were determined to be 5 dB and 10 dB, respectively.
The configurations for both ends of the link are shown below.
uBR1 Configuration:
UBR1# show running-configuration interface radio 6/0 Current configuration: ! interface radio6/0 ip address 10.0.0.1 255.255.255.0 radio master radio receive-antennas 1 radio operating-band tx 2506.00 rx 2542.00 radio channel-setup bandwidth 6.0 throughput high radio transmit-power 30 radio cable-loss 1 5 end
uBR2 Configuration:
UBR2# show running-configuration interface radio 6/0 Current configuration: ! interface radio6/0 ip address 10.0.0.2 255.255.255.0 radio receive-antennas 1 radio operating-band tx 2542.00 rx 2506.00 radio channel-setup bandwidth 6.0 throughput high radio transmit-power 30 radio cable-loss 1 10 end
The following example displays the configuration currently in effect on the Cisco uBR7200 series router:
UBR04#show running-configurationBuilding configuration...Current configuration: ! version 12.0 service udp-small-servers service tcp-small-servers ! hostname UBR04 ! enable password 1234FCX ! username tech07 ! interface FastEthernet0/0 no ip address no ip route-cache shutdown media-type MII ! ip name-server 192.168.168.1 ip name-server 192.168.168.181 ip name-server 192.168.168.178 ! line con 0 exec-timeout 0 0 line aux 0 line vty 0 4 password 1234FCX login local ! interface BFWRadio3/0 radio master radio channel-setup bandwidth 6.0 throughput medium radio transmit-power 22 radio cable-loss 7 radio event-threshold ...... radio dsp-statistics ....... radio codec-statistics ...... ! end
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications.
In Cisco IOS Release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expressionFollowing is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRateFor more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
To clear link metrics settings, use the clear radio interface radio privileged EXEC command. To remove the loopback, use the no form of this command.
clear radio interface radio slot/port link-metrics
slot/port | The slot and port address. |
No default behavior or values.
EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The following command will clear all radio link-metrics details:
UBR04 # clear radio interface radio 6/0 link-metrics
To place the specified module in loopback mode, use the loopback interface configuration command. To remove the loopback, use the no form of this command.
loopback [local module]
local | (Optional) Specifics that the module is local. |
module | Specifies the type of module: |
Local IF loopback
Interface configuration
| Release | Modification |
|---|---|
11.0 | This command was introduced. |
12.0(7)XR | Support for the uBR7200 router and the local keyword was added. |
If you perform a loopback of the RF module while the transverter is attached to an antenna, some transmit power will be radiated. Because of this, it is extremely important that the transmit frequency be set to your assigned and licensed MMDS frequency. If the transverter is not attached to an antenna, attach an RF termination device to the duplexer port. (For information regarding RF termination devices, refer to the Cisco Broadband Fixed Wireless Site Planning Guide.)
The following example initiates a local RF loopback:
UBR04(config-if)# loopback local rf
The following example displays the set of loopbacks currently in effect for the modem card in slot 3, port 0 of the Cisco uBR7200 series router:
UBR04# show interfaces radio 3/0
Radio3/0 is up, line protocol is up (looped)
Hardware is CWR P2P
Internet address is 10.0.0.13/24
MTU 1500 bytes, BW 44419 Kbit, DLY 11000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, loopback set
Keepalive set (10 sec)
Last input 00:00:01, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 8 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
620 packets input, 203300 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 output errors, 0 collisions, 4 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
| Command | Description |
|---|---|
show interfaces radio | Displays the set of loopbacks currently in effect for the specified modem card |
To align the receive antenna to the transmitter, use the radio antenna-alignment interface configuration command. To cancel antenna alignment mode, use the no form of this command.
radio antenna-alignment
no antenna-alignment
This command has no arguments or keywords.
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
Do not use this command during normal operation; its use will degrade the performance of the radio link.
The following example initiates antenna alignment mode during installation:
UBR04(config-if)# radio antenna-alignment
| Command | Description |
|---|---|
show running-configuration interface | Displays the current interface settings. |
To configure the Automatic Repeat Query mechanism on the wireless modem card, use the radio arq interface configuration command. To use default values, use the no form of this command.
radio arq pctBw voiceLatency dataLatency [BurstSize] [on | off] [reset]
no radio arq
pctBw | Positive number representing the highest percentage of the link bandwidth to be used for the ARQ mechanism. The value may be 1 to 5000, representing 0.01 to 50 percent of the available bandwidth. The default value is 1250. Note Regardless of the pctBw setting, link bandwidth is only consumed by ARQ when there are data errors that need to be corrected. |
voiceLatency | Positive number specifying the expected latency value for voice. Latency values are measured in milliseconds. The default value is 11 ms. |
dataLatency | Positive number specifying the expected latency value for normal data. Latency values are measured in milliseconds. The default value is 11 ms. |
BurstSize | Positive number specifying the maximum number of consecutive ARQ codewords that will be transmitted. Smaller values result in lower jitter. The default value is 16. |
11-ms latency
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
Automatic repeat query (ARQ) enables the transmitter to resend data that is received in error at the receiver. This allows the radio link to run at substantially lower error rate in RF channels with rapid fading or bursty interference.
Enabling requires a small amount of additional overhead and increases the latency of the link. However, even with small maximum latency and maximum overhead settings, enabling ARQ can dramatically improve link performance.
Use the on/off option to turn on or off the ARQ feature on the link.(If ARQ is turned off, it may be difficult to establish the radio link in adverse environments.)
Use the reset option to reset the current ARQ values to consistent settings based on the channel-parameter configuration.
The following command sets the ARQ mechanism for 0.01% of the bandwidth, a 20-millisecond latency value, and 20 consecutive ARQ codewords:
UBR04(config-if)# radio arq 1 20 20
To specify the collection interval for the histogram for uncorrected codewords, as well as how often the collected histogram data should be printed to the display screen, use the radio byteErrorHist interface configuration command. To stop collecting and displaying histrogram data, use the no form of this command.
radio byteErrorHist [collectionInterval interval] [periodic interval sum {true | false}]
no radio byteErrorHist [collectionInterval interval] [periodic interval sum {true | false}]
collectionInterval interval | Specifies, in seconds, the duration of histogram data collection. |
periodic interval | Specifies, in seconds, how often the collected histogram data will be printed to the screen. The sum option specifies whether successive histogram sets retrieved from the hardware should be added to replace the existing histogram data. Use an interval of 0 to print the data to the screen only at termination of the collection. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The following example will configure a collection interval of 1 hour and print to the screen every 30 seconds:
UBR04(config-if)# radio byteErrorHist collectionInterval 3600 periodic 30 sum false
To determine the effective cable loss (measured in dB at 400 MHz) of the cable between the wireless modem card and the specified wireless transverter, including the power feed panel, connectors, and lightning protection, use the radio cable-loss interface configuration command. To stop measuring cable loss, use the no form of this command.
radio cable-loss antenna_num positive number
no radio cable-loss
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
positive number | Positive number (less than or equal to 12 dB), reflecting effective cable loss. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The cable loss parameter cannot be set to a value greater than 12 dB. The exact cable loss value is determined by the transverter. The system checks against that value when a no shut command is entered.
The following example adjusts the effective cable loss parameter for antenna 1 to 12 dB:
UBR04(config-if)# radio cable-loss 1 12
| Command | Description |
|---|---|
show running-configuration interface radio | Displays the current radio cable loss setting. |
To adjust bandwidth and throughput to increase the reliability of the link, use the radio channel-setup interface configuration command. To reset the parameters to the defaults, use the no form of this command.
radio channel-setup bandwidth bw throughput dataThroughput {high | medium | low}
no radio channel-setup
bw | {6.0 | 12.0} |
dataThroughput | {high | medium | low} |
high (default) | At 12 MHz, maximum 44.4 Mbps |
medium | At 12 MHz, maximum 39.1 Mbps |
low | At 12 MHz, maximum 22.4 Mbps |
Bandwidth 6.0, throughput high
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
Multipath delay spread is one of two fundamental limits to the performance of a digital radio link. The other limit is the Signal to Interference plus Noise ratio (SINR) which is discussed in the Cisco uBR7200 Series Universal Broadband Router Wireless Modem Card and Subsystem Installation and Configuration Guide.
Multipath delay spread occurs when the signal arrives at the receiver via multiple paths with differing path lengths. Signals that take longer paths will arrive later than signals that take shorter paths. The delay spread is the difference between the time it takes for the shortest path signal and the longest path signal to arrive. Typically, delay spread is the longest in urban areas with many buildings acting as reflectors. Delay spread is more important when the direct path between antennas is blocked, making the delayed signals stronger relative to the direct signal.
Both 6 MHz and 12 MHz bandwidths are available. For each of these bandwidths there are three possible throughput setting: high, medium, and low. The low setting uses the most error-correction coding and can handle the most multipath delay spread. The medium setting uses less error-correction coding, but can still handle the most multipath delay spread. The high setting uses less error-correction coding and can handle less multipath delay spread.For a selected bandwidth, data throughput can be reduced to increase reliability.
This command can be entered at any time. If the link is up when it is entered, the command will take effect with the next shut/no shut. If the link is down when it is entered, the command will take effect with the next no shut.
| Command | Description |
|---|---|
shut | Stops the link (if it is up). no shut starts the link and implements any bandwidth changes. |
show running-configuration interface radio | Displays the current settings. |
To enter duplexer specifications, use the radio duplexor interface configuration command.
radio duplexor antenna_num PartNum LoPassbandRange HiPassbandRange RxPassband [low-passband | hi-passband] CLEIcode VendorName SerialNumber
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
PartNum | A string representing the duplexer's Cisco part number |
LoPassbandRange | Identifies the duplexer's low frequency range. This range is lower than the range specified in the HiPassbandRange parameter. |
HiPassbandRange | Identifies the duplexer's high frequency range. This range is higher than the range specified in the LoPassbandRange parameter. |
RxPassband | Identifies the frequency range used to receive transmissions. |
CLEIcode | Common Language Equipment Identifier code. |
VendorName | The name of the vendor of the duplexer. |
SerialNumber | Serial number of the duplexer. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The duplexer is a mechanical device that acts as a band pass filter when installed in the wireless transverter. This filter restricts the transverter to operate in a specified part of the frequency spectrum. One duplexer provides a high and low frequency specification for one wireless transverter.
You can find most of the information on the tear-off label attached to the underside of the duplexor.
To control the printing of radio histogram information to the screen, use the radio histdisplay interface configuration command.
radio histdisplay statParam antenna_num [dsp dspId] {on | off}
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain} The radio attribute whose data is to be collected as a histogram. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
dsp dspId | {dsprxla (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP 2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b) | |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
| Command | Description |
|---|---|
radio histogram | Configures a histogram collection of radio traffic on the specified interface. |
radio interface histclear | Removes radio histograms. |
To configure a histogram collection specification, use the radio histogram interface configuration command. To delete existing histogram collections, use the no form of this command.
radio histogram statParam antenna_num [dsp dspId] StartBinValue BinDelta NumBins BitShift [collectionInterval interval] [periodic interval sum {true | false}] [tone circulate | average | number tone-number]
no radio histogram statParam antenna_num [dsp dspId]
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain} The radio attribute whose data is to be collected as a histogram. |
in | (Interference + Noise) The interference plus noise power levels are computed by the hardware on a burst-by-burst basis. |
inr | (Interference + Noise Ratio) The ratio of the interference plus noise power levels captured by the first antenna to the second antenna on a burst-by-burst basis. This value is specified as a log to base 2 number. Note This parameter is available for a dual antenna system only. |
constVariance | (Constellation Variance) The average energy of the constellation error signal - the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. Constellation Variance is a measure of the Signal to Interference plus Noise ratio (SINR) for that tone. On a single antenna system, it is proportional to (SINR)-1. On a dual antenna system, it represents a composite value that is proportional to (SINR)-1. |
timingOffset | Represents the timing delay variations detected in the radio link. |
freqOffset | Represents the carrier frequency offset between the slave radio and the master radio. |
syncStatus | Represents the synchronization status. |
receivedPower | A measure of the analog signal power received by the radio system on a burst-by-burst basis. |
gainSettingsIF | Represents the IF attenuation value commanded by the automatic gain control loop. This can be captured for each antenna and for the intermediate frequency (IF) module. |
gainSettingsRF | Represents the RF attenuation value commanded by the automatic gain control loop. This can be captured for each antenna and for the radio frequency (RF) module. |
totalGain | Represents the total attenuation commanded by the automatic gain control loop. This can be captured for each antenna. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
dspId | {dsprx1a (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b)} |
StartBinValue | Any value below this value will not be stored in the histogram. Range is -231 to 232-1. |
BinDelta | The "width" of each histogram bin. For example, if the StartBinValue is 10 and BinDelta is 64, then all values in the range 10 to 74 will be in the first bin. All values from 75 to 138 will be in the second bin, and so on. Range is 2 to 2^32, and must be a power of 2. |
NumBins | The number of histogram bins to be configured for the collection. Range is 0 to 508. |
BitShift | Specifies the number of bits by which the collected data should be shifted to the right, providing a mechanism to control overflow of the values in the histogram. Range is 0 to 31. |
collectionInterval | Specifies, in seconds, the interval in which histogram data will be collected. |
periodic | Specifies, in seconds, how often the collected histogram data should be printed to the screen. The sum option specifies whether successive histogram sets retrieved from the hardware should be added to replace the existing histogram data. Specifying a statistic collection to be periodic effectively reduces the size of the NumBins to half the possible amounts. The default is periodic. If the interval is 0, output is generated only at the termination of the collection. |
tone | Identifies how the histogram sample should be computed when sampling a burst. A burst contains data samples from N frequency tones. |
circulate | Implies successive histogram data samples should use successive frequency tones. |
average | Implies successive histogram samples should average the burst data over all the frequencies and use that value. |
number | Specifies that a particular tone in the burst should be used to report the histogram data. The frequency tone is passed in as a number specified in the tone-number parameter. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
A histogram is a collection of statistics sampled over time on a burst-by-burst basis and presented as a function of Bins. The number of Bins as well as the size of Bins is user defined.
The data for the histogram is collected as soon as the command succeeds and continues until either the specification is deleted using the no option, or the specified collectionInterval expires. The collected data is printed out to the console at user-specified intervals.
A histogram statistic is created when data is sampled for every burst. For each sampled burst, the count in a specific bin is incremented. The number of bins in the histogram is specified by the NumBins parameter.
For every histogram defined, antenna_num and tone are conditional. The antenna_num is required for the attributes in, receivedPower, GainSettingsIF, gainSettingsRF, and totalGain. Tone may optionally be specified for the attributes in, inr, and constVariance.
Up to 1024 32-bit words are available for all histogram parameters on a single DSP. Each histogram requires (NumBins + 4) * 2 words. The attributes in in, inr, and constVariance can be captured on any DSP, while the others can be captured only on certain DSPs. Distributing histogram requests across DSPs provides better memory utilization. In general, it is best not to specify the DSPs without special knowledge of the system. For more information on DSPs, see the Cisco uBR7200 Series Universal Broadband Router Wireless Modem Card and Subsystem Installation and Configuration Guide.
The following example will configure a histogram specification. The histogram collection will start as soon as the command succeeds. It will collect a histogram for interference noise ratio. The histogram will be collected with starting bin of 2-4 (a starting ratio of 0.0625), bindelta of 1, 32 bins in total, and no bitshift. It will average the results on all frequency tones for each sample. The collection will continue for 1 hour, reporting data every 30 seconds and keeping the cumulative histogram.
UBR04(config-if)# radio histogram inr -4 1 32 0 collectionInterval 3600 periodic 30 tone average sum true
| Command | Description |
|---|---|
radio histdisplay | Displays radio histograms. |
radio interface histclear | Removes radio histograms. |
To add the specified image to the image repository, use the radio image-add privileged EXEC command. To delete the specified image from the repository, use the no form of this command.
radio image-add protocol://host/directory/filename
no radio image-add protocol://host/directory/filename
protocol | {mem | tftp | flash} |
host | IP address. |
directory | Directory name. (No embedded spaces accepted.) |
filename | Name of image file. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
When an image has to be downloaded according to the specified configuration, the repository is searched for an appropriate file. If found, the file is retrieved and downloaded to the hardware.
The following command selects the image displa.img at the address 192.168.33.44 to be added to the repository:
UBR04# radio image-add tftp://192.168.33.44/myDspImages/dspla.img
| Command | Description |
|---|---|
radio image-move | Moves the specified image to the beginning of the repository. |
radio image-override | Attaches the specified image file name to the specified chip. |
show radio repository | Displays the repository contents. |
To move the specified image to the beginning of the repository list of images, use the radio image-move privileged EXEC command.
radio image-move protocol://host/directory/filename
protocol | {mem | tftp | flash} |
host | IP address. |
directory | Directory name. (No embedded spaces accepted.) |
filename | Name of image file. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
When the radio card is initiated (no shut), the repository is searched for a firmware image with characteristics matching the current configuration. Once found, that image is downloaded. Moving an image to the beginning of the list ensures that the image is searched first when a configuration match is attempted.
The following example selects the image dspla.img at the address 192.168.33.44 to be moved to the start of the repository list:
UBR04# radio image-move tftp://192.168.33.44/myDspImages/dspla.img
| Command | Description |
|---|---|
radio image-add | Adds the specified image to the repository. |
radio image-override | Attaches the specified image file name to the specified chip. |
show radio repository | Displays the repository contents. |
To attach the specified image file name to the specified chip, use the radio image-override interface configuration command. To remove the override, use the no form of this command.
radio image-override chipname image
chipname | Specifies the name of a chip. |
image | Specifies the location of the image file in the form: protocol://host/directory/filename, where: |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
When an image is to be downloaded to the specified chip for which an image override is in place, the configuration logic is ignored and the override attached file is downloaded instead.
When specifying the directory name for the image file, do not use embedded spaces.
| Command | Description |
|---|---|
radio image-add | Creates a radio image. |
radio image-move | Moves the specified image to the beginning of the repository. |
show radio repository | Displays the repository contents. |
To clear collected radio histogram data, use the radio interface histclear interface configuration command.
radio interface slot/port histclear statParam antenna_num [dsp dspId]
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain} The radio attribute whose data is to be collected as a histogram. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
dspId | {dsprx1a (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b)} The DSP on which to collect the timeline data. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
| Command | Description |
|---|---|
radio histdisplay | Controls how the histogram data displays. |
radio histogram | Configures a histogram collection specification. |
To capture another snapshot on the identified DSP, use the radio interface radio snapcapture interface configuration command.
radio interface radio slot/port snapcapture dspId
slot/port | The slot and port address. |
dspId | The DSP ID: |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The snapshot specification already configured on the DSP will be used.
| Command | Description |
|---|---|
radio snapshot | Creates a snapshot specification. |
radio interface radio snapclear | Clears the data collected for the specified snapshot. |
show interfaces radio snapdata | Displays the data captured for the snapshot specification. |
To clear the data collected for the specified snapshot on the identified DSP, use the radio interface radio snapclear interface configuration command.
radio interface radio slot/port snapclear dspId
slot/port | The slot and port address. |
dspId | {dsprxla (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP 2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b) | |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
| Command | Description |
|---|---|
radio snapshot | Creates a snapshot specification. |
radio interface radio snapcapture | Captures a snapshot on the specified DSP. |
show interfaces radio snapdata | Displays the data captured for the snapshot specification |
To start a stopped timeline specification, use the radio interface radio timelineStart privileged EXEC command.
radio interface radio slot/port timelineStart statParam antenna_num [dsp dspnum]
slot/port | The slot and port of the interface. |
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF} The radio attribute whose data is to be collected as a histogram. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
dspnum | The DSP number. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
Unless an error occurs, no notifications are displayed on the console.
| Command | Description |
|---|---|
radio timeline | Configures a timeline collection specification. |
radio interface radio timelineStop | Stops a running timeline specification. |
show interfaces radio tldata | Displays timeline data for the specified card. |
show interfaces radio tlspec | Displays the details of the timeline specification. |
To stop a currently executing timeline specification, use the radio interface radio timelineStop privileged EXEC command.
radio interface radio slot/port timelineStop statParam antenna_num [dsp dspnum]
slot/port | The slot and port of the interface. |
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF} The radio attribute whose data is to be collected as a histogram. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
dspnum | The DSP number. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
| Command | Description |
|---|---|
radio timeline | Configures a timeline collection specification. |
radio interface radio timelineStart | Starts a stopped timeline specification. |
show interfaces radio tldata | Displays timeline data for the specified card. |
show interfaces radio tlspec | Displays the details of the timeline specification. |
To manually highlight specific conditions on a specified wireless modem card using the five LEDs on the card, use the radio led interface configuration command. To reset the settings of the LED to the default values, use the no form of this command.
radio led {latchLeds latchLedOptions | otherLeds otherLedOptions}
no radio led latchLeds
latchLeds | {led-major-alarm | led-minor-alarm} |
led-major-alarm | Indicates the occurrence of a major alarm in the radio subsystem. Unless the default mode is overridden, the LED will remain illuminated for the duration of the alarm. |
led-minor-alarm | Indicates the occurrence of a minor alarm in the radio subsystem. Unless the default mode is overridden, the LED will remain illuminated for the duration of the alarm. |
latchLedOptions | {latch | off | green | yellow | blinkGreen | blinkYellow | blinkBoth} |
latch | The system will turn the LED on indicating an alarm condition; the operator must turn it off by entering the radio led latchLeds latch command. Note The latch option is available only for led-major-alarm and led-minor-alarm. |
off | This forces the LED to turn off, and remain off under all conditions. |
green | Lamp test for the LED. The LED is turned green, and remains green under all conditions. |
yellow | Lamp test for the LED. The LED is turned yellow, and remains yellow under all conditions. |
blinkGreen | Blinks the LED green. |
blinkYellow | Blinks the LED yellow. |
blinkBoth | Blinks the LED alternately yellow and green. |
otherLeds | {led-carrier | led-service | led-ok} |
led-carrier | Represents the state of the radio link. This LED cannot be latched, but the operator can turn these LEDs on or off manually. |
led-service | Indicates the service availability on this radio link. This LED cannot be latched, but the operator can turn these LEDs on or off manually. This LED is operator-controlled only. |
led-ok | Indicates that the wireless modem card is on, receiving from the router midplane, and enabled for operation. This LED remains on during normal operation of the router. |
otherLedOptions | {off | green | yellow | blinkGreen | blinkYellow | blinkBoth} |
LEDs controlled by system
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
There are three categories of LEDs: alarm, user-controlled, and other LEDs, The two alarm LEDs will normally remain illuminated only for the duration of the alarm. However, this can be overridden using the latch form of the command. This command causes the LEDs to remain illuminated until the LED is cleared by again using the latch form of the command.
The led-service LED can only be controlled by entering an LED command. All the LEDs can be forced to illuminate or blink under operator control. This can be used as a "lamp test" to verify that the hardware is functional or to remotely indicate a specific wireless modem card to be examined.
The following command sets the behavior of the major alarm LED to be controlled by the system at all times:
UBR04(config-if)# no radio led led-major-alarm
| Command | Description |
|---|---|
show interfaces radio | Displays current configuration and state of the LEDs. |
To configure the wireless modem card to operate as the master radio, use the radio master interface configuration command. To force the radio card to operate as the slave, use the no form of this command.
radio master [external-clock-reference]
no radio master
external clock-reference | Option. Indicates that an external reference is being used. In slave mode the default is automatically set to internal clock reference. |
Slave mode
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The master radio acts as the frequency source; the radio designated as the slave will track to the changes in the master's frequency.
This command can be entered only when the radio link is down (shut), and will take effect only when the link is again active (no shut). Use the no version of the command to switch the modem card from master to slave mode.
The following example configures the wireless modem card to operate as the master radio with internal clock reference:
UBR04(config-if)# radio master
| Command | Description |
|---|---|
show running-configuration interface radio | Displays the current setting. |
To configure thresholds that determine when a second is classified as ES, DS, SES, or CSES for the radio link to measure how well the radio link is performing over time, use the radio metrics-threshold code-word interface configuration command. To force the thresholds back to the default values, use the no form of this command.
radio metrics-threshold code-word ESThresh DSThresh SESThresh CSESThresh
no radio metrics-threshold code-word
ESThresh | Specifies the number of codeword errors that must be detected within a 1-second interval for that second to be treated as a Errored Second. Typically, ESThresh = 1. |
DSThresh | If the number of codeword errors detected within 1 second is greater than or equal to this threshold and less than SESThresh, that second is treated as a Degraded Second. |
SESThresh | If the number of codeword errors detected within a 1-second interval is greater than or equal to this threshold, that second is treated as a Severely Errored Second. |
CSESThresh | Specifies the number of consecutive severely errored seconds that must be detected for the sequence to be treated as one consecutively Severely Errored Second. |
TBC
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
When the radio link is synchronized, the measurement parameters used are error free seconds (EFS), errored seconds (ES), severely errored seconds (SES), consecutively errored seconds (CSES), degraded seconds (DS), and degraded minutes (DM).
All link metrics are measured in terms of codewords. A codeword is a unit (228 bytes) of data transmission over the radio link. It contains user data, error counts and collation information so that successive codewords may be reconstructed at the receiving end into the transmitted data.
Use this command with care, arbitrary changes will distort the performance metrics reported for the radio link.
The following example will configure the link so that:
UBR04(config-if)# radio metrics-threshold code-word 3 30 150 4
| Command | Description |
|---|---|
show interfaces radio slot/port metrics-threshold | Shows the thresholds set for link metrics. |
radio metrics-threshold 1hour | Displays the link metrics for a one hour period. |
radio metrics-threshold 24hour | Displays the link metrics for a twenty-four hour period. |
To set threshold values for to configure limits on the ES, SES, CSES, and DM to measure how well the radio link is performing over a 24-hour period, use the radio metrics-threshold 24hour interface configuration command. To force the thresholds back to the default values, use the no form of this command.
radio metrics-threshold 24hour ESLimit SESLimit CSESLimit DMLimit
no radio metrics-threshold 24hour
ESLimit | Specifies the number of errored seconds that should be detected within the specified time period (24 operational hours), after which the ESLimit minor alarm will be generated. |
SESLimit | Specifies the number of codeword severely errored seconds that should be detected within the specified time period 24 operational hours), after which the SESLimit minor alarm will be generated. |
CSESLimit | Specifies the number of codeword consecutively severely errored seconds that should be detected within the specified time period (24 operational hours), after which the CSESLimit minor alarm will be generated. |
DMLimit | Specifies the number of codeword degraded minutes that should be detected within the specified period (24 operational hours), after which the DMLimit minor error alarm will be generated. |
TBC
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
When the radio link is synchronized, the measurement parameters used are error free seconds (EFS), errored seconds (ES), severely errored seconds (SES), consecutively errored seconds (CSES), degraded seconds (DS), and degraded minutes (DM). When these limits are exceeded in a 24-hour period, alarms will be generated to notify the user. Minor alarms are generated and displayed on the console when the specified 24-hour threshold is exceeded.
Use this command with care, arbitrary changes will distort the performance metrics reported for the radio link.
The following example will configure the link alarms so that:
UBR04(config-if)# radio metrics-threshold 24hour 24 36 12 5
| Command | Description |
|---|---|
show interfaces radio slot/port metrics-threshold | Shows the thresholds set for link metrics. |
radio metrics-threshold code-word | Configures thresholds that determine when a second is classified as ES, DS, SES, or CSES for the radio link. |
radio metrics-threshold 1hour | Displays the link metrics for the past one hour period. |
To to configure limits on the ES, SES, CSES, and Degraded Minutes (DM), use the radio metrics-threshold 1hour interface configuration command. To force the thresholds back to the default values, use the no form of this command.
radio metrics-threshold 1hour ESLimit SESLimit CSESLimit DMLimit
no radio metrics-threshold
ESLimit | Specifies the number of errored seconds that should be detected within the specified time period (1 operational hour), after which the ESLimit minor alarm will be generated. |
SESLimit | Specifies the number of codeword severely errored seconds that should be detected within the specified time period (1 operational hour), after which the SESLimit minor alarm will be generated. |
CSESLimit | Specifies the number of codeword consecutively severely errored seconds that should be detected within the specified time period (1 operational hour), after which the CSESLimit minor alarm will be generated. |
DMLimit | Specifies the number of codeword degraded minutes that should be detected within the specified period (1 operational hour), after which the DMLimit minor error alarm will be generated. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
When the radio link is synchronized, the measurement parameters used are error free seconds (EFS), errored seconds (ES), severely errored seconds (SES), consecutively errored seconds (CSES), degraded seconds (DS), and degraded minutes (DM). When these limits are exceeded in a 1-hour period, alarms will be generated to notify the user. Minor alarms are generated and displayed on the console when the specified 1-hour threshold is exceeded.
Use this command with care, arbitrary changes will distort the performance metrics reported for the radio link.
The following example will configure the link alarms so that:
UBR04(config-if)# radio metrics-threshold 1hour 6 10 3 2
| Command | Description |
|---|---|
show interfaces radio slot/port metrics-threshold | Shows the thresholds set for link metrics. |
radio metrics-threshold code-word | Configures thresholds that determine when a second is classified as ES, DS, SES, or CSES for the radio link. |
radio metrics-threshold 24hours | Displays the link metrics for the past 24 hour period. |
To specify the radio operating band and transmit/receive frequencies within the radio operating band, use the radio operating-band interface configuration command. To reset the operating band to the default values, use the no form of this command.
radio operating-band Tx transmit frequency Rx receive frequency
no radio operating-band
transmit frequency | Positive number in the range 2500.00 MHz to 2690.00 MHz (MMDS) |
receive frequency | Positive number in the range 2500.00 MHz to 2690.00 MHz (MMDS) |
TBC
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
This command can be entered at any time. If the link is up when it is entered, the command will take effect with the next shut/no shut. If the link is down when it is entered, the command will take effect with the next no shut.
Use the channel-setup parameters to select the required bandwidth and data throughput prior to specifying the operating-band.
Transmit and receive frequencies must be consistent with the bandwidth the radio has been configured to operate in using the channel-setup command, and must fall within the passband of the duplexer used in the transverter. See the Cisco uBR7200 Series Universal Broadband Router Wireless Modem Card and Subsystem Installation and Configuration Guide for center frequencies for the MMDS band, and center frequencies for the U-NII band.
For a complete list of channel designations and start, center, and end frequencies, refer to the Cisco Broadband Fixed Wireless Site Planning Guide.
The transmit frequency on the radio designated as "master" must be identical to the receive frequency on the radio designated as "slave."
The following example sets center frequencies in the MMDS band:
UBR04(config-if)# radio operating-band Tx 2533.00 Rx 2599.00
| Command | Description |
|---|---|
show running-configuration interface radio | Displays the current setting. |
To configure the baseline encryption options provided by the wireless modem card, use the radio privacy interface configuration command. To turn off privacy options, use the no form of this command.
radio privacy {enable | auth-wait-time secs | reauth-wait-time secs | auth-grace-time secs | op-wait-time secs | rekey-wait-time secs | tek-grace-time secs | auth-lifetime secs | tek-lifetime secs}
no radio privacy
auth-wait-time | The number of seconds the slave radio will wait before issuing a new authorization request to the master radio. |
reauth-wait-time | The number of seconds the slave radio will wait before issuing a new reauthorization request to the master. |
auth-grace-time | Grace time for an authorization key. The slave radio is expected to start trying to get a new authorization key beginning auth-grace-time seconds before the authorization key actually expires. |
op-wait-time | Operational wait timeout. |
rekey-wait-time | The amount of time (in seconds) that the slave radio waits before issuing a new request to the master radio for an encryption key. |
tek-grace-time | Grace time for a traffic encryption key (TEK). The slave radio is expected to start trying to get a new TEK beginning tek-grace-time seconds before the traffic encryption key actually expires. |
auth-lifetime | The lifetime (in seconds) the master radio assigns to an authorization key for the slave radio. |
tek-lifetime | The lifetime (in seconds) assigned to traffic encryption keys by the master radio. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The radio designated as "master" controls privacy authorization and encryption key distribution. The radio designated as "slave" tracks the master radio's signals. The default is on.
Use the enable option to enable baseline privacy options. Use the other options to configure timeout values. When privacy is enabled, the timeout values determine how long the master or the slave radio will wait for either authentication or encryption keys to be revalidated. If this revalidation fails, meaningful communication between master and slave radios will not be possible.
The following command will configure baseline privacy:
UBR04(config-if)# radio privacy enable
| Command | Description |
|---|---|
show running-configuration | Displays the current settings |
To configure the wireless modem card to use a specified number of receive antennas, use the radio receive-antennas interface configuration command. To disable reception, use the no form of this command.
radio receive-antennas {1 | 2}
no radio receive-antennas
1 | 2 | Specifies which antenna to use. Enter 1 (main antenna) or 2 (diversity antenna). |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
This command can be entered only when the radio link is down (shut), and will take effect when the link is again active (no shut). Use the no version of the command to set the number of receive antennas to 1 (the default value).
The following example configures the wireless modem card to use two receive antennas:
UBR04(config-if)# radio receive-antennas 2
| Command | Description |
|---|---|
show running-configuration interface radio> | Displays the current setting. |
To configure a single DSP to send the identified type of output to the serial port, use the radio scope-output privileged EXEC command. To to turn off the serial output, use the no form of this command.
radio scope-output dspId outputType
no radio scope-output dspId
dspId | {dsprxla (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP 2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b) | |
outputType | {rx-rawburst-ant1-y1n | rx-rawburst-ant1-y2n | rx-spectrum-ant1-y1k | rx-spectrum-ant1-y2k | rx-timedomainchannel-ant1-h1n | rx-timedomainchannel-ant2-h2n | rx-freqdomainchannel-ant1-h1k | rx-freqdomainchannel-ant2-h2k | rx-constellation-zhatk | tx-codec-input | tx-ifft-input | tx-round-output | sync-burst-timecost-func | sync-freq-offset-costfunc | sync-pwrsbtcffocf | sync-fll-freq-corelation | sync-fll-train-tone-corelation | sync-fll-fft-spectrum} |
slot/port | The slot and port address. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
An oscilloscope can be connected to the serial port to analyze the output of the DSP.
You can gather the output of only one DSP at a time.
The following command sends an output of type rx-timedomainchannel-ant2-h2n to the serial port:
UBR04# radio scope-output dsprx1a RxTimeDomainChannelAnt2H2n
| Command | Description |
|---|---|
show interfaces radio slot/port scope-output | Displays the attribute being directed to the scope port. |
To test the memory and hardware integrity of the wireless modem card, use the radio self-test interface configuration command. To configure a restart of the link without executing self-tests, use the no form of this command.
radio self-test [enable]
no radio self-test
enable | (Optional) causes execution of self-tests each time the card is initiated. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
Use the enable option to execute self-tests each time the card is initiated (no shut). Use the command without the enable option to perform a self-test only on the first no shut after initiation. Each time the test is performed, results are displayed on the console.
The following example shows the configuration command to download and execute self-tests each time the modem card is enabled:
UBR04(config-if)# radio self-test enable
| Command | Description |
|---|---|
show running-configuration interface radio | Displays the current settings. |
To to create a snapshot specification on the modem card, use the radio snapshot privileged configuration command. To delete a specification and its associated data, use the no form of this command.
radio snapshot dspId snapshotType
no radio snapshot dspId snapshotType
dspId | {dsprxla (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP 2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b) | |
snapshotType | Unsigned number. Up to four different snapshot types may be requested at once. When more than one snapshot is requested in a command, all snapshots will be captured from the same DSP. See snapshot type definitions below. |
rx-rawburst-ant1-y1n (0x01) | Represents a snapshot of the received signal for RF resource 1. For every sample, the real and imaginary components are captured. |
rx-rawburst-ant2-y2n (0x02) | Represents a snapshot of the received signal for RF resource 2. For every sample, the real and imaginary components are captured. |
rx-spectrum-ant1-y1k (0x04) | Represents a snapshot of the spectrum of the received signal for RF resource 1. For every sample, the real and imaginary components are captured. |
rx-spectrum-ant2-y2k (0x08) | Represents a snapshot of the spectrum of the received signal for RF resource 2. For every sample, the real and imaginary components are captured. |
rx-timedomainchannel-ant1-halon (0x10) | Represents a snapshot of the time domain channel for RF resource 1. For every sample, the real and imaginary components are captured. |
rx-timedomainchannel-ant2-h2n (0x20) | Represents a snapshot of the time domain channel for RF resource 2. For ever sample, the real and imaginary components are captured. |
rx-freqdomainchannel-ant1-hlk (0x40) | Represents a snapshot of the frequency domain channel for RF resource 1. For every sample, the real and imaginary components are captured. |
rx-freqdomainchannel-ant2-h2k (0x80) | Represents a snapshot of the frequency domain channel for RF resource 2. For every sample, the real and imaginary components are captured. |
rx-constellation-zhatk (0x100) | Represents a snapshot of the soft decisions. For every sample, the real and imaginary components are captured. |
tx-codec-input (0x200) | Represents a snapshot of input values to the Tx Code. |
tx-ifft-input (0x400) | Represents a snapshot of the IFFT signal for the transmitted data. For every sample, the real and imaginary components are captured. |
tx-round-output (0x800) | Represents a snapshot of the Rounded Constellation signal for the transmitted data. For every sample, the real and imaginary components are captured. |
sync-burst-timecost-func (0x1000) | Represents the timing cost function for Sync bursts. |
sync-freq-offset-costfunc (0x2000) | Represents a snapshot of the frequency offsets. For every sample, the real and imaginary components are captured. |
sync-pwrsbtcffocf (0x4000) | Represents a snapshot of Sync power burst. For every sample, the real and imaginary components are captured. |
sync-fll-freq-correlation (0x8000) | Represents a snapshot of Frequency correlation. For every sample, the real and imaginary components are captured. |
sync-fll-train-tone-correlation (0x10000) | Represents a snapshot of Frequency locked loops, Training tone correlation. For every sample, the real and imaginary components are captured. |
sync-fll-fft-spectrum (0x20000) | Represents a snapshot of Frequency locked loop, FFT Spectrum. For every sample, the real and imaginary components are captured. |
No default behavior or values.
Privileged configuration (TBC)
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
A snapshot is a specified amount of data captured from the wireless modem card.
When you issue a snapshot request, up to four simultaneous radio signal attributes can be captured. The four attributes are specified by adding the attribute numbers for up to four of the snapshot types identified below.
| Command | Description |
|---|---|
show interfaces radio snapshot | Displays configured snapshot information. |
show interfaces radio snapdata | Displays the data captured for the snapshot specification |
radio interface radio snapcapture | Creates a snapshot on the specified DSP. |
radio interface radio snapclear | Clears the snapshot data on the specified DSP. |
To configure a threshold event specification, use the radio threshold interface configuration command. To terminate the event-threshold setup, use the no form of this command.
radio threshold threshParam antennaNum [dsp dspId] threshType threshValue repeatTime clearTime
no radio threshold threshParam antennaNum [dsp dspId] threshType
threshParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain} |
in | (Interference + Noise) The interference plus noise power levels are computed by the hardware on a burst-by-burst basis. Note This parameter is available for a dual antenna system only. |
inr | (Interference + Noise Ratio) The ratio of the interference plus noise power levels captured by the first antenna to the second antenna on a burst-by-burst basis. This value is specified as a log to base 2 number. |
constVariance | (Constellation Variance) The average energy of the constellation error signal - the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. Constellation Variance is a measure of the Signal to Interference plus Noise ratio (SINR) for that tone. On a single antenna system, it represents (SINR)-1. On a dual antenna system, it represents a composite value providing (SINR)-1 after antenna combining. |
timingOffset | Represents the timing delay variations detected in the radio link. |
freqOffset | Represents the carrier frequency offset between the slave radio and the master radio. |
syncStatus | Represents the synchronization status. |
receivedPower | A measure of the analog signal power received by the radio system on a burst-by-burst basis. |
gainSettingsIF | Represents the IF attenuation value commanded by the automatic gain control loop. This may be captured for each antenna and for the intermediate frequency (IF) module. |
gainSettingsRF | Represents the RF attenuation value commanded by the automatic gain control loop. This may be captured for each antenna and for the radio frequency (RF) modules. |
totalGain | Represents the total attenuation commanded by the automatic gain control loop. This can be captured for each antenna. |
antennaNum | Enter either 1 (main antenna) or 2 (diversity antenna). |
dspId | {dsprx1a (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b)} |
threshType | {highThreshold | lowThreshold | upChange | downChange | posCrossing | negCrossing} |
highThreshold | The upper limit for the threshParam being monitored. |
lowThreshold | The lower limit for the threshParam being monitored. |
upChange | The positive change limit allowed for the threshParam being monitored. |
downChange | The negative change limit allowed for the threshParam being monitored. |
posCrossing | The limit that applies only when the threshParam is increasing in value. |
negCrossing | The limit that applies only when the threshParam is decreasing in value. |
threshValue | A 32-bit integral value |
repeatTime | When radio signals are monitored, they can oscillate across a specified threshold (such as highThreshold) very rapidly. In such a case, an event is generated for each crossing of the threshold, which could flood the system. The repeatTime parameter specifies the amount of time (in seconds) the system should wait, in this case, before another event of the same type is generated. |
clearTime | When radio signals oscillate across a threshold, it is often desirable to identify when the signal has stabilized. The clearTime parameter specifies how many seconds the radio signal must stay below a threshold (after crossing it once) before the system generates the clear event. |
No default behavior or values.
Interface configuration (TBC)
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
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.
For each event, the threshParam [dsp dspId] threshType eventType will be output identifying the threshold crossed.
The no radio threshold command requires the threshParam, threshType, and [dsp dspId] attributes.
The following command sequence will set up a threshold for totalGain. When the totalGain for the system on antenna2 falls below 70, the eventSet event type will be generated.
UBR04(config-if)# radio threshold totalGain 2 lowThreshold 70
| Command | Description |
|---|---|
show interfaces radio thresholds | Displays the current threshold specifications. |
To configure a timeline collection specification with the software, use the radio timeline privileged EXEC command. To delete a timeline, use the no form of this command.
radio timeline statParam antenna_num [dsp dspId] tlSize [decimationFactor df] [presummationShift pss] [print {on | off}] [tone {circular | average |
number tone-number] [trigger threshParams threshType (antenna_num) postTrigBufMgt]
no radio timeline statParam antenna_num [dsp dspnum]
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF} |
in | (Interference + Noise) The interference plus noise power levels are computed by the hardware on a burst-by-burst basis. |
inr | (Interference + Noise Ratio) The ratio of the interference plus noise power levels captured by the first antenna to the second antenna on a burst-by-burst basis. This value is specified as a log to base 2 number. Note This parameter is available for a dual antenna system only. |
constVariance | (Constellation Variance) The average energy of the constellation error signal - the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. Constellation Variance is a measure of the Signal to Interference plus Noise ratio (SINR) for that tone. On a single antenna system, it represents (SINR)-1. On a dual antenna system, it represents (SINR)-1 after antenna combining. |
timingOffset | Represents the timing delay variations detected in the radio link. |
freqOffset | This represents the carrier frequency offset between the slave radio and the master radio. |
syncStatus | Represents the synchronization status. |
receivedPower | A measure of the analog signal power received by the radio system on a burst-by-burst basis. |
gainSettingsIF | Represents the IF attenuation value commanded by the automatic gain control loop. This may be captured for each antenna and for the intermediate frequency (IF) module. |
gainSettingsRF | Represents the RF attenuation value commanded by the automatic gain control loop. This may be captured for each antenna and for the radio frequency (RF) modules. |
totalGain | Represents the total attenuation commanded by the automatic gain control loop. This can be captured for each antenna. |
dspId | {dsprx1a (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b)} The DSP on which to collect the timeline data. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). The antenna for which the timeline data should be collected. |
tlSize | Positive number representing the number of values to collect. |
decimationFactor | The rate at which data is received is high, so retrieving every successive data sample will likely provide little information (due to memory limitations). The decimation factor specifies how many successive data samples should be added together and reported as one data sample. If the decimation factor is not specified, every successive data sample is reported. |
df | {0 . . 231} |
presummationShift | If decimationFactor is specified, then successive data samples get added. This can potentially cause an overflow. The presummationShift value specifies the number of bits by which the data sample should be right-shifted before being added. Specifying a presummationShift value will result in less precise individual data samples but provides a mechanism to analyze the behavior over longer duration of time. |
pss | (0 . . 32) |
{on | off} Specifies whether or not the collected values should be printed out when the collection completes. The default is on. | |
tone | {circular | average | number tone-number} Every burst of signal data contains samples from N frequency tones. This parameter identifies which of those frequency tones should be used. |
circular | Implies successive data samples should use successive frequency tones. |
average | Implies successive data samples should average the burst data over all the N frequencies and then use that value. |
number | Specifies that data from a particular frequency in the burst should be reported. |
tone-number | for in and inr for constVariance |
trigger | Specifies when the collection has to be stopped. The threshParam threshType antenna_num parameters uniquely identify a threshold specification. When this threshold is reached, the timeline will be stopped and the data collected. |
threshParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF} |
threshType | {highThreshold | lowThreshold | upChange | downChange | posCrossing | negCrossing} |
highThreshold | An upper limit for the threshParam being monitored. |
lowThreshold | A lower limit for the threshParam being monitored. |
upChange | The positive change limit allowed for the threshParam being monitored. |
downChange | The negative change limit allowed for the threshParam being monitored. |
posCrossing | The limit that applies only when the threshParam is increasing in value. |
negCrossing | The limit that applies only when the threshParam is decreasing in value. |
postTrigBufMgt | Specifies the position of the trigger in the data collected. If it is 1, then most of the data collected prior to the trigger is returned. If it is 2, most of the data returned is captured after the occurrence of the trigger. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
A timeline is a sequence of data values collected for a specified attribute. The amount of data collected is controlled by the tlSize parameter. The maximum size is determined by the hardware memory size.
Collection starts as soon as the command succeeds, and continues until the trigger occurs or the timelineStop command is executed.
For every timeline defined, antenna_num and tone are conditional. The antenna_num is required for the attributes in, receivedPower, GainSettingsIF, gainSettingsRF, and totalGain. The tone may be optionally specified for the attributes in, inr, and constVariance.
Up to 1024 32-bit words are available for all timeline parameters on a single DSP. Each timeline requires (tlsize+1) * 2 words. The attributes in in, inr, and constVariance can be captured on any DSP, while the others can be captured only on certain DSPs. Distributing timeline requests across DSPs provides better memory utilization.
The following example configures a timeline specification. The collection process starts as soon as the command succeeds. The inr parameter will be monitored. A total of 640 values will be collected.
Of the N tones in a burst, the average value of all the tones (for the burst) is retrieved as one data sample. Each data sample will be right shifted by 2 bits. Twenty successive (right-shifted) data samples will be added together and reported as one value (of the 640 values in total).
When the threshold inr lowThreshold 2 is reached, the collection will stop and the results will be printed.
UBR04#radio timeline inr 640 dec 20 pre 2 tone average trigger inr
lowThreshold 2
| Command | Description |
|---|---|
radio interface radio timelineStart | Starts a stopped timeline specification. |
radio interface radio timelineStop | Stops a running timeline specification. |
show interfaces radio tldata | Displays timeline data for the specified card. |
show interfaces radio tlspec | Displays the details of the timeline specification. |
To configure the transverter to transmit the specified amount of power (in dBm) when in operation, use the radio transmit-power interface configuration command. To disable, use the no form of this command.
radio transmit-power power
no radio transmit-power
power | Positive number representing power stated in dBm. Transmit power range for MMDS is between 15 and 35 dBm. |
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
Maximum transmission power is limited by the capabilities of the transverter. In addition, your country's telecommunications authority (the FCC in the United States) regulates the maximum power and/or the EIRP in the MMDS and U-NII bands. It is the responsibility of the installer and operator to comply with the relevant regulations.
To support the maximum number of users in an area, keep the power as low as possible while maintaining sufficient margin and performance. Refer to the Cisco Broadband Fixed Wireless Site Planning Guide for additional information.
The following example sets the MMDS transmit power to +25 dBm:
UBR04(config-if)# radio transmit-power 25
| Command | Description |
|---|---|
show running-configuration interface radio | Displays the current setting. |
To display all or a subset of attributes of a particular modem card, use the show controllers radio privileged EXEC command.
show controllers radio slot number/port number [{if | rf | fir | codec | dsp | arq | pci | phy | driver}]
slot number | Positive integer representing the Cisco uBR7200 series slot number. |
port number | Positive integer representing the port number on that slot. |
if | (version, freq, register1) |
| version is the name, version of the module. freq is the current operating frequency. register1 is the IF Register 1. |
rf | (version, freq, power) |
| version is the name, version of the module. freq is the current operating frequency. power is the minimum, maximum power capacity. |
fir | (version, firThresh,) |
| version is the name, version of the module. firThresh is the queue threshold. |
codec | (version, rsDecodeErrThresh, rdDecodeErrBytes) |
| version is the name, version of the module. rsDecodeErrThresh is the decode error threshold. rdDecodeErrBytes are the decode error bytes |
dsp | (version) |
| version is the name, version of the module. |
arq | version, arqThresh) |
| version is the name, version of the module. arqThresh is the ARQ threshold. |
pci | (version) |
| version is the name, version of the module. |
phy | (version) |
| version is the name, version of the module. |
driver | TBC |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
If you do not specify any of the options, all the hardware subsystem(s) information will be displayed. Actual output parameters depend on the hardware and implementation.
The following example shows the output received when the pci option is specified for the modem card in slot number 3, port number 0.
UBR04# show controllers radio 3/0 pci
Interface Radio 3/0
Hardware is CW Radio Point-to-Point Line Card
throttled 0 enabled 0 disabled 0
Rx: spurious 0 framing_err 0 no_buffer 0, pause_no_err_ints 0
no_enqueue 0 no_stp 0 no_enp 0
Tx: full 0 drop 0
rx ring entries 32 tx ring entries 128
Rx ring 0x4B05A0C0 shadow 0x61399C60 head 2
Normal Latency Tx ring 0x4B05A680 shadow 0x6139A1C0 head 0 tail 0 count 0
Low Latency Tx ring 0x4B05A220 shadow 0x61399D50 head 3 tail 3 count 0
PCI Configuration Registers
Device/Vendor IDs - 0x00141137
Command/Status - 0x02000086
Latency Timer - 0x0000FF00
Base Address 0 - 0x4E000000
Max Lat - 0x000001FF
PCI Interface FPGA
dmac_control - 0x00440002
dmac_status - 0x00004000
dmac_int_status - 0x99800001
dmac_int_enable - 0x66710FF8
dmac_tx0_ring_base - 0x4B05A220
dmac_tx1_ring_base - 0x4B05A680
dmac_rx_ring_base - 0x4B05A0C0
dmac_configuration - 0x66040303
local_bus_error_status - 0x00000000
local_bus_error_address - 0x010C0000
local_bus_reset - 0x00000000
fpga_configuration_control - 0x00000000
fpga_configuration_status - 0x000000FF
Table 4 describes the fields shown in the show controllers radio display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To display the current ARQ configuration on the wireless modem card, use the show interfaces radio arq privileged EXEC command.
show interfaces radio slot/port arq
slot/port | The slot and port address. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
If none of the optional parameters are specified then all the timeline specifications on the modem card are displayed. If the statParam antenna_num combination only is specified, then the configuration setup on the default will be displayed. if the [dsp dspId] parameter is specified, then the configurations on that DSP will be displayed.
The following command will display the ARQ configuration for the modem card in slot 3, port 0:
UBR04# show interfaces radio 3/0 arq
ARQ State = on
Data Latency = 20 ms
Voice Latency = 20 ms
Maximum ARQ Bandwidth Overhead = 12.50%
Typical Bit Rate = 10845152 bits/sec
Minimum Bit Rate = 9488600 bits/sec
Burst Size = 16 codewords
Maximum Latency Jitter = 2679 usec
Table 2 describes the fields shown in the show interfaces radio arq display.
pctBW | The maximum percent link bandwidth being used for ARQ. |
dataLatency | Hardware will restrict the maximum latency for packet data to this value. |
voiceLatency | Hardware will restrict the maximum latency for voice data to this value. |
BurstSize | Currently configured burst size, in number of codewords. |
OnOff | Whether ARQ is turned on or off. |
ARQPeakBitRate | The maximum possible peak bit rate that the link can handle based on the current channel-parameter and ARQ settings. |
ARQMinBitRate | The minimum bit rate that may be seen on the link based on the current channel-parameter and ARQ settings. |
ARQMaxLatencyJitter | The maximum jitter expected on this link based on the current configuration. |
| Command | Description |
|---|---|
radio arq | Configures Automatic Repeat Query. |
To display the collected histogram data for the identified histogram specification, use the show interfaces radio histdata privileged EXEC command.
show interfaces radio slot/port histdata statparam antenna_num dsp dspnum
slot | Positive integer representing the Cisco uBR7200 series slot number. |
port | Positive integer representing the port number on that slot. |
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain | codewordError} The radio attribute whose data is to be collected as a histogram. Note If <statParam> is specified, antenna_num is conditionally required. |
in | (Interference + Noise) The interference plus noise power levels are computed by the hardware on a burst-by-burst basis. |
inr | (Interference + Noise Ratio) The ratio of the interference plus noise power levels captured by the first antenna to the second antenna on a burst-by-burst basis. This value is specified as a log to base 2 number. Note This parameter is available for a dual antenna system only. |
constVariance | (Constellation Variance) The average energy of the constellation error signal - the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. Constellation Variance is a measure of the Signal to Interference + Noise ratio (SINR) for that tone. On a single antenna system, it represents (SINR)-1. On a dual antenna system, it represents a composite value providing (SINR)-1. |
timingOffset | Represents the timing delay variations detected in the radio link. |
freqOffset | Represents the carrier frequency offset between the slave radio and the master radio. |
syncStatus | Represents the synchronization status. |
receivedPower | A measure of the analog signal power received by the radio system on a burst-by-burst basis. |
gainSettingsIF | Represents the IF attenuation value commanded by the automatic gain control loop. This can be captured for each antenna and for the intermediate frequency (IF) module. |
gainSettingsRF | Represents the RF attenuation value commanded by the automatic gain control loop. This can be captured for each antenna and for the radio frequency (RF) module. |
totalGain | Represents the total attenuation commanded by the automatic gain control loop. This can be captured for each antenna. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). Note For every threshold defined, antenna_num is conditional. The attributes in, receivedPower, GainSettingsIF, gainSettingsRF, and totalGain are applicable for antenna_num. |
dspnum | The DSP number. Note If the DSP number is not specified, the specification on the default DSP will be displayed. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The values are displayed as a BinID:Value pair. BinId represents the sample value contained in that bin. Value represents the count in the histogram bin.
The following example shows the command to display the histogram data for the histogram configured on the modem card in slot 6, port 0 of the uBR for receive DSP 1a.
UBR04#show interfaces radio 6/0 histdata inr dsp dsprx1aHistogram 4/1/8 [*=100] min=-2 avg=0157 0=<0 ** 137 0=<1 ** 115 1=<2 ** 44 2=<MAX *
Table 3 describes the fields shown in the show interfaces radio histdata display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
show interfaces radio histspec | Displays the details of the histogram specifications currently configured. |
To display the details of the histogram specifications currently configured, use the show interfaces radio histspec privileged EXEC command.
show interfaces radio slot/port histspec [statParam antenna_num [dsp dspnum]]
slot | Positive integer representing the Cisco uBR7200 series slot number. |
port | Positive integer representing the port number on that slot. |
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain} The radio attribute whose data is to be collected as a histogram. Note If the statParam is specified, antenna_num is conditionally required. |
in | (Interference + Noise) The interference plus noise power levels are computed by the hardware on a burst-by-burst basis. |
inr | (Interference + Noise Ratio) The ratio of the interference plus noise power levels captured by the first antenna to the second antenna on a burst-by-burst basis. This value is specified as a log to base 2 number. Note This parameter is available for a dual antenna system only. |
constVariance | (Constellation Variance) The average energy of the constellation error signal - the error between the received (noisy) constellation symbol and the nearest ideal constellation symbol. Constellation Variance is a measure of the Signal to Interference plus Noise ratio (SINR) for that tone. On a single antenna system, it represents (SINR)-1. On a dual antenna system, it represents a composite value providing (SINR)-1. |
timingOffset | Represents the time delay variations detected in the radio link. |
freqOffset | Represents the carrier frequency offset between the slave radio and the master radio. |
syncStatus | Represents the synchronization status. |
receivedPower | A measure of the analog signal power received by the radio system on a burst-by-burst basis. |
gainSettingsIF | Represents the IF attenuation value commanded by the automatic gain control loop. This can be captured for each antenna and for the intermediate frequency (IF) module. |
gainSettingsRF | Represents the RF attenuation value commanded by the automatic gain control loop. This can be captured for each antenna and for the radio frequency (RF) module. |
totalGain | Represents the total attenuation commanded by the automatic gain control loop. This can be captured for each antenna. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). Note For every histogram defined, antenna_num is conditional. The antenna_num is required for attributes in, receivedPower, GainSettingsIF, gainSettingsRF, and totalGain. |
dspnum | The DSP number. Note If the DSP number is not specified, the specification on the default DSP will be displayed. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
If none of the optional parameters are specified, all histogram specifications on the modem card are displayed.
The following example shows details of the histogram Constellation Variance specification configured for the modem card in slot 3, port 0 of the uBR:
UBR04# show interfaces radio 3/0 histspec constVariance
Class constVariance
Start Bin Value 0
Bin Delta 4
Number of Bins 100
Update Rate 10
Collection duration 20
Bit Shift 0
Tone Selection average
Dsp Number dsrx1a
Index 9
Periodic Sum false
Default Hist false
Display status on
Histogram Status captured
Table 4 describes the fields shown in the show interfaces radio histspec display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
show interfaces radio histdata | Displays the collected histogram data for the identified histogram specification. |
To display details of the images to be downloaded on a single chip or on all chips, use the show interfaces radio imagehdr privileged EXEC command.
show interfaces radio slot/port imagehdr [chip chipname [current | operational]]
slot/port | The slot and port address. |
chipName | A character string identifying a chip. |
current | Display the image header (details) for the image currently loaded on the chip. |
operational | Display the image header for the image that will be loaded on the chip for the current configuration. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
If a particular chip is identified, the details of the image to be loaded on that chip are displayed. If no chip name is specified, the current radio configuration is retrieved for every chip on the modem card. All the images in the repository are compared. The image that provides the closest match in capability is selected, and the details of that image are displayed.
The following example will display the image details of the chip named dsp1a currently loaded on the chip on the modem card in slot 3, port 0:
UBR04# show interfaces radio 3/0 imagehdr dsp1a current
image details TBC
Table 5 describes the fields shown in the show interfaces radio imagehdr display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To display the attribute being sent to the scope port, use the show interfaces radio histspec privileged EXEC command.
show interfaces radio slot/port scope-output
slot/port | The slot and port address. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
| Command | Description |
|---|---|
radio scope-output | Configures the specified DSP to send the specified output to the serial port. |
To display snapdata information, use the show interfaces radio snapdata privileged EXEC command.
show interfaces radio slot/port snapdata dspId
slot/port | The slot and port address. |
dspId | Specifies the DSP number. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The following example TBC:
command example TBC
Table 6 describes the fields shown in the show interfaces radio snapdata display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
radio snapshot | Creates a snapshot specification. |
radio interface radio snapclear | Clears the data collected for the specified snapshot. |
To display snapshot information, use the show interfaces radio snapshot privileged EXEC command.
show interfaces radio slot/port snapshot dspId
slot/port | The slot and port address. |
dspId | Specifies the DSP number. |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The following example TBC:
command example TBC
Table 7 describes the fields shown in the show interfaces radio snapshot display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
radio snapshot | Creates a snapshot specification. |
radio interface radio snapclear | Clears the data collected for the specified snapshot. |
show interfaces radio snapdata | Displays the data captured for the snapshot specification. |
To to display the set of currently configured thresholds on the modem card on the specified DSP, use the show interfaces radio privileged EXEC command.
show interfaces radio slot/port thresholds [dspNum]
slot/port | The slot and port address. |
dspNum | The DSP number. |
No default behavior or values.
privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
If dspNum is not specified, the thresholds for DSP 3 will be displayed.
The following command will display the set of currently configured thresholds for the modem card in slot 6, port 0 for the Receive DSP 1b:
UBR04#show interfaces radio 6/0 thresholds dsp dsprx1b Threshold Attribute in
Threshold Type downChange
Antenna Id 2
Threshold Value 200
Threshold Repeat Time 5
Threshold Clear Time 8
Threshold DSP Number dsprx1b Index 2 Default Threshold false
Table 8 describes the fields shown in the show interfaces radio thresholds display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
radio threshold | Configures a threshold event specification |
To display the timeline data collected for the identified specifications, use the show interfaces radio ltdata privileged EXEC command.
show interfaces radio slot/port tldata [statParam antenna_num [dsp dspId]]
slot/port | The slot and port address. |
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain} The radio attribute whose data is to be collected as a histogram. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
dsp dspId | {dsprxla (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP 2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b) | |
No default behavior or values.
privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
If none of the optional parameters are specified then all the timeline specifications on the modem card are displayed. If the statParam antenna_num combination only is specified, then the configuration setup on the default will be displayed. if the [dsp dspId] parameter is specified, then the configurations on that DSP will be displayed.
The following example will display the timeline inr data for the modem card installed in slot 3, port 0 of the uBR7200 series router:
UBR04# show interfaces radio 3/0 tldata inr
Number of Points Captured=100 Trigger Location=54
0 :0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
10 :0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
20 :0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
30 :0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
40 :0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
50 :FFFFFFFF FFFFFFFF 0000 0000 0000 0000 0000 0001 FFFFFFFF FFFFFFFF
60 :0000 0002 FFFFFFFF FFFFFFFF 0000 0001 0000 0000 0000 0000
70 :0000 0000 0000 0001 FFFFFFFF FFFFFFFF 0000 0000 0000 0001
80 :FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 0000 0002 FFFFFFFF FFFFFFFF 0000 0002
90 :FFFFFFFF FFFFFFFF 0000 0000 0000 0001 FFFFFFFF FFFFFFFF 0000 0000
Table 9 describes the fields shown in the show interfaces radio tldata display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
radio timeline | Configures a timeline collection specification. |
radio interface radio timelineStart | Starts a stopped timeline specification. |
radio interface radio timelineStop | Stops a running timeline specification. |
show interfaces radio tlspec | Displays the details of the timeline specification. |
To display the details of the currently configured timeline specifications, use the show interfaces radio tlspec privileged EXEC command.
show interfaces radio slot/port tlspec [statParam antenna_num [dsp dspId]]
slot/port | The slot and port address. |
statParam | {in | inr | constVariance | timingOffset | freqOffset | syncStatus | receivedPower | gainSettingsIF | gainSettingsRF | totalGain} The radio attribute whose data is to be collected as a histogram. |
antenna_num | Enter 1 (main antenna) or 2 (diversity antenna). |
dsp dspId | {dsprxla (Receive DSP 1a) | dsprx1b (Receive DSP 1b) | dsprx2a (Receive DSP 2a) | dsprx2b (Receive DSP 2b) | dsprx3a (Receive DSP 3a) | dsprx3b (Receive DSP 3b) | |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
If none of the optional parameters are specified then all the timeline specifications on the modem card are displayed. If the statParam antenna_num combination only is specified, then the configuration setup on the default will be displayed. if the [dsp dspId] parameter is specified, then the configurations on that DSP will be displayed.
The following example displays the inr timeline specification configured for the modem card in port 3, slot 0 of the uBR7200 series router:
UBR04# show interfaces radio 3/0 tlspec inr
Class inr
Resource Id 1
Buffer size 50
Number of buffers 20
Collection method 30
Tone Selection average
Stop threshold attribute in
Stop threshold type downChange
Stop antenna number 1
Print options off
Dsp Number 3
Default T1 false
Table 4 describes the fields shown in the show interfaces radio tlspec display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
radio timeline | Configures a timeline collection specification. |
radio interface radio timelineStart | Starts a stopped timeline specification. |
radio interface radio timelineStop | Stops a running timeline specification. |
show interfaces radio tldata | Displays timeline data for the specified card. |
To display the protocol-specific list of images in the repository, use the show radio repository privileged EXEC command.
show radio repository [header] [protocol]
header | Image header details associated with the list of images will also be displayed. |
protocol | {mem | tftp | flash} |
No default behavior or values.
Privileged EXEC
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The repository is a list of current configuration images. When the modem card is initiated (no shut), this list is searched and the correct image downloaded. Privileged configuration access is required.
The following example lists images related to memory:
UBR04# show radio repository mem
mem:/MyMemImages/dsp1Dual.img
mem:/MyMemImages/dsp2Dual.img
mem:/MyMemImages/dsp1Single.img
Table 4 describes the fields shown in the show interfaces radio repository display.
| Field | Description |
|---|---|
TBC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Command | Description |
|---|---|
radio image-add | Adds images to the repository. |
radio image-move | Moves the specified image to the beginning of the repository. |
radio image-override | Attaches the specified image file name to the specified chip. |
To shut down the radio link, use the shut interface configuration command. To reinstate the radio link, use the no form of this command.
shut
no shut
This command has no keywords or arguements.
No default behavior or values.
Interface configuration
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
The state of the link is displayed on the console.
The following command will shut down the radio link:
UBR04(config-if)# shut
To display debug messages for the radio link, use the debug radio EXEC command. To turn off debugging, use the no form of this command.
debug radio {lm_log | messages | phy}
no debug radio
lm_log | log [verbose] |
phy | {radioLog | cwrLog} |
radioLog | radio slot/port subModule |
slot | Positive integer representing the Cisco uBR7200 series slot number. |
port | Positive integer representing the port number on that slot. |
subModule | {cli | gal | snmp} logLevel |
cli | Tracing for radio interface CLI commands. |
gal | Tracing for the GAL (TBC) module. |
snmp | Tracing for the radio SNMP module. |
logLevel | Acceptable values are: {all | controlFlow | dataFlow | validation | verbose} |
cwrLog | cwrLog modName |
modName | Name of the module |
No default behavior or values.
| Release | Modification |
|---|---|
12.0(7)XR | This command was introduced. |
Various logLevels determine what and how much debug log output is generated.
UBR04# debug radio phy radio 3/0 snmp verbose
This command causes various physical layer entities to log debug output:
UBR04(config-if)# debug radio phy cwrLog modName
| Command | Description |
|---|---|
show debug | Displays current debug settings. |
DSP---Digital Signal Processor
MMDS---TBC
SINR---The ratio of the received strength of the desired signal to the received strength of undesired signals (noise and interference).
U-NII---TBC
Posted: Sat Dec 4 19:24:35 PST 1999
Copyright 1989-1999©Cisco Systems Inc.