Table Of Contents
Multipoint Wireless Support for the Cisco 2600 and Cisco 3600 Series Routers
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Specifying Alternative Boot Location (Optional)
Configuring Cable Loss (Optional)
Monitoring and Maintaining the Multipoint Wireless Configurations
Typical Subscriber-Unit Configuration
radio interface radio rf-update max-power
radio metrics-threshold code-word
show controllers radio downstream
show controllers radio upstream
show interface radio accounting
show interface radio hist-data
show interface radio hist-spec
show interface radio metrics-threshold
show interface radio snap-data
show interface radio snap-spec
show interface radio thresholds
debug radio p2mp phy cwrlog radio
Multipoint Wireless Support for the Cisco 2600 and Cisco 3600 Series Routers
The Cisco broadband fixed wireless multipoint system is an integrated solution consisting of a headend and multiple subscriber units. This document describes the fixed wireless multipoint support for the Cisco 2600 and Cisco 3600 series routers. The document provides the command-line-interface (CLI) commands that are used to configure, maintain, and troubleshoot your multipoint subscriber unit feature. The following sections are included:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
The Cisco broadband fixed wireless multipoint subscriber unit is designed to receive radio frequency (RF) signals from the headend. It also transmits a return signal to the headend. This return signal is a point-to-point signal, so a properly installed subscriber antenna must be correctly oriented with the headend antenna to which it is transmitting. For more information about the fixed wireless multipoint headend feature, see the Multipoint Support for the Cisco uBR7200 Series Universal Broadband Router document.
The fixed wireless multipoint system incorporates Vector Orthogonal Frequency Division Multiplexing (VOFDM), so it does not always depend on line-of-sight (LOS) deployment. With VOFDM, the system allows wireless operation in obstructed, non-line-of-sight (non-LOS) environments (see Figure 1) by taking advantage of multipath signals. This can be particularly useful in urban and suburban environments.
Figure 1 Multipoint Communications with Multipath and Diversity Reception
Subscriber-Unit System
Each subscriber unit system (see Figure 2) consists of the necessary cables and:
•
•
•
•
•
Note
Figure 2 Components of the Multipoint Subscriber-Unit System
Subscriber-Unit Components
The subscriber unit consists of the following components.
Router
The Cisco 2600 series modular access routers and Cisco 3600 series modular, high-density access routers are designed to allow two-way transmission of digital data using either coaxial cable or broadband fixed wireless. These routers support IP routing with a wide variety of protocols and any combination of Ethernet, Fast Ethernet, High-Speed Serial Interface (HSSI), serial, and Asynchronous Transfer Mode (ATM) media. Network interfaces reside on port adapters that provide the connection between the router and external networks. Wireless interfaces reside on modem cards and provide the connection to wireless networks.
For further information regarding the Cisco 2600 series modular access routers, refer to the Cisco 2600 Series Hardware Installation Guide and refer to the Software Configuration Guide (for Cisco 3600 series and Cisco 2600 series routers) for detailed software configuration instructions.
Network Module
The network module is installed in the network module slot of a Cisco 2600 series router or a Cisco 3600 series router. It is configured through the router's system console or through the CiscoView network management system. The network module provides the control and data interface to 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). One network module supports one or two wireless transverters (main and diversity).
For further information regarding the network module, refer to the Cisco Network Modules Hardware Installation Guide (for Cisco 3600 series and Cisco 2600 series routers) for detailed installation instructions, and the Software Configuration Guide (for Cisco 3600 series and Cisco 2600 series routers) for an overview of network module configuration procedures and information on configuring specific network modules.
Power Injector
The subscriber-unit power injector serves as an interconnection device between the network module, a -48V (+24V) DC power supply, and the wireless transverter attached to the subscriber-unit antenna. The standard power version supplies 3A. The high-power version supplies 7A.
The main purpose of this unit is to provide the wireless transverter with DC power, control signals, and IF signals to be transmitted. It also receives the incoming IF signals from the wireless transverter. In addition, the unit contains circuit breakers for the DC power.
Each power injector supports only one wireless transverter. When the subscriber unit requires a diversity antenna and transverter, a second power injector is required.
Note
Wireless Transverter
The wireless transverter is the outdoor control and data interface to the indoor subsystems. It provides up/down conversion from IF to RF frequencies and power amplification.
Note
Note
Antenna
The antenna transmits and receives the RF signals to and from the headend.
Note
Benefits
The broadband fixed wireless system provides the following benefits:
•
•
•
•
•
•
Related Features and Technologies
None
Related Documents
Headend documents:
•
•
•
•
•
Subscriber-unit documents:
•
•
•
•
Supported Platforms
The multipoint wireless feature is supported on following platforms:
•
•
•
•
•
•
•
•
Supported Standards, MIBs, and RFCs
Standards
DOCSIS 1.0 and 1.0+. The DOCSIS 1.0+ implementation is DOCSIS 1.0 with quality-of-service (QoS) support.
MIBs
This feature is supported by Cisco uBR7200 series MIBs and DOCSIS MIBs enhancing the manageability of customer infrastructures.
To obtain lists of MIBs supported by platform and Cisco IOS release and to download MIB modules, go to the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
Multipoint wireless support
Configuration Tasks
The configuration tasks for the fixed wireless multipoint subscriber-unit is automated. The following optional configuration tasks are provided:
•
•
Specifying Alternative Boot Location (Optional)
Normally, the router boots the system image from Flash memory. If you want to boot the system from an alternative location use the following steps.
Configuring Cable Loss (Optional)
Normally, the cable loss value of the cable between the wireless card and the specified wireless transverter is automatically configured, but if you want to modify the cable loss settings, use the radio cable-loss command. See radio cable-loss for syntax and description of this command.
Monitoring and Maintaining the Multipoint Wireless Configurations
This section describes the clear and show commands that are used to monitor and maintain the multipoint wireless feature.
Verifying Configuration
Step 1
Step 2
Step 3
Step 4
Configuration Examples
The following is a typical configuration example for a subscriber radio interface.
Typical Subscriber-Unit Configuration
interface Radio1/0 multipointip address 7.7.7.2 255.255.255.0docsis mac-timer t2 6000no docsis compliant bridgeradio cable-loss 1 3 3no cdp enableCommand Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
The docsis compliant bridge command enables DOCSIS-compliant transparent bridging for a radio access-router interface at startup. The docsis classifier subcommands are used to map packets into service flows using assigned priority.
The following commands are used to create a Data-over-Cable System Interface Specifications (DOCSIS) 1.1-like flow that can be assigned to DOCSIS 1.0+ best-effort or unsolicited grant service (UGS) flow.
The following commands are used to identify and configure the radio interface:
•
•
•
The following commands are used to monitor and maintain the radio interface:
•
•
•
•
•
•
•
•
•
•
•
clear radio link-metrics
To clear the link-metrics table, use the clear radio link-metrics privileged EXEC command.
clear radio slot/port link-metrics
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
Make sure that you record and analyze the link-metrics data before executing this command.
Examples
The following example shows how to clear all radio link-metrics details:
Router# clear radio 6/0 link-metricsRelated Commands
docsis compliant bridge
To enable DOCSIS-compliant transparent bridging for a radio access-router interface at startup, use the docsis compliant bridge interface configuration command. Use the no form of this command to disable DOCSIS-compliant bridging for the interface.
docsis compliant bridge
no docsis compliant bridge
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Normally, it is not necessary to enter this command in Data-over-Cable bridging applications, because DOCSIS-compliant bridging is enabled by default. If you wish to do full transparent bridging rather than DOCSIS-compliant bridging, use the no form of the command, then configure full transparent bridging using the command-line interface (CLI) commands.
Examples
The following example shows how to enable DOCSIS-compliant transparent bridging for a radio interface at startup:
Router(config)# interface radio 6/0Router(config-if)# docsis compliant bridgedocsis classifier
To create a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service (QoS) flow, use the docsis classifier global interface configuration command. Entering this command prompts the user to enter the classifier subcommands that are listed below. Use the no form of this command to disable the classifier.
docsis classifier classifier-ref subcommand
no docsis classifier classifier-ref
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Global interface configuration
Command History
Usage Guidelines
Use the DOCSIS classifier command to create classifiers that map traffic to QoS flows.
Examples
The following example enables the DOCSIS classifier mode, allowing the user to enter any of the classifier subcommands listed above:
Router(config)# docsis classifierRouter(config-classifier)#Related Commands
ether-dmac
To define a destination MAC address and mask for the classifier, use the ether-dmac DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ether-dmac dmac mask
no ether-dmac
Syntax Description
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Examples
The following example shows how to use the docsis classifier ether-dmac command:
(config)# docsis classifier 1{config-classifier)# ether-dmac 1111.2222.3333 ffff.ffff.ffffRelated Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ether-smac
To define a source MAC address for a classifier, use the ether-smac DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ether-smac smac
no ether-smac
Syntax Description
smac
Specifies the source MAC address. An Ethernet packet with a source MAC address matches this parameter if the destination MAC address is equal to smac.
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Examples
The following example shows how to enter the ether-smac command:
(config)# docsis classifier 1(config-classifier)# ether-smac 1111.2222.3333Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ether-type
To define an Ethernet type or a destination service access point (DSAP) MAC address for a classifier, use the ether-type DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ether-type {type | dsap}
no ether-type
Syntax Description
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Examples
The following example shows how to define the Ethernet type for classifier 1:
(config)# docsis classifier 1(config-classifier)# ether-type 0x0806Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ip-destination-address
To define a destination IP address and mask for a classifier, use the ip-destination-address DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ip-destination-address dest mask
no ip-destination-address
Syntax Description
Defaults
The default mask is 255.255.255.255.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
A match occurs when the dest value added to the mask value using the AND operation equals the ip-destination-address of an IP packet.
Examples
The following example shows how to define the destination IP address and mask for classifier 1:
(config)# docsis classifier 1(config-classifier)# ip-destination-address 192.1.1.1 255.255.255.255Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ip-destination-port
To define a destination IP-port range for a classifier, use the ip-destination-port DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ip-destination-port start end
no ip-destination-port
Syntax Description
start
Specifies the lowest IP port that can match the classifier. Valid range is 0 to 65,535.
end
Specifies the highest IP port that can match the classifier. Valid range is 0 to 65,535.
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
An IP packet matches a classifier if the value of start is less than or equal to the value of ip-destination-port, and if the value of end is greater than or equal to the value of ip-destination-port. If the value of end is not specified, it defaults to the value of start.
Examples
The following example shows how to define the destination IP port value for classifier 1:
(config)# docsis classifier 1(config-classifier)# ip-destination-port 23Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ip-protocol
To define an IP protocol for a classifier, use the ip-protocol DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ip-protocol protocol
no ip-protocol
Syntax Description
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
A packet matches a classifier if its IP protocol field matches the value of protocol. A protocol value of 256 matches the traffic of any IP protocol. A protocol value of 257 matches any TCP protocol or UDP traffic.
Examples
The following example shows how to define the IP protocol value for the classifier 1:
(config)# docsis classifier 1(config-classifier)# ip-protocol 257Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ip-source-address
To define a source IP address and mask for a classifier, use the ip-source-address DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ip-source-address source mask
no ip-source-address
Syntax Description
Defaults
The default mask is 255.255.255.255.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
A match occurs when the source value added to the mask value using the AND operation equals to the ip-source-address of an IP packet.
Examples
The following example shows how to define the source IP address and mask for the classifier:
(config)# docsis classifier 1(config-classifier)# ip-source-address 192.1.1.1 255.255.255.255Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ip-source-port
To define a source IP-port range for a classifier, use the ip-source-port DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ip-source-port start end
no ip-source-port
Syntax Description
start
Specifies the lowest IP port that matches the classifier. Valid range is 0 to 65,535.
end
Specifies the highest IP port that matches the classifier. Valid range is 0 to 65,535.
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
An IP packet matches a classifier if the value of start is less than or equal to the value of ip-destination-port, and if the value of end is greater than or equal to the value of ip-destination-port. If the value of end is not specified, it defaults to the value of start.
Examples
The following example shows how to define the source IP port value for the classifier:
(config)# docsis classifier 1(config-classifier)# ip-source-port 80Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
ip-type-of-service
To define an IP type of service (ToS) for a classifier, use the ip-type-of-service DOCSIS classifier configuration command. Use the no form of this command to disable this function.
ip-type-of-service low high mask
no ip-type-of-service
Syntax Description
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
A match occurs when the IP ToS byte in an IP packet added (using the AND operation) to the value of mask is greater than or equal to the value of low, and is less than or equal to the value of high.
Examples
The following example shows how to define an IP ToS for the classifier:
(config)# docsis classifier 1(config-classifier)# ip-type-of-service 3 7 fRelated Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
qos-flow
To associate a DOCSIS classifier with a quality-of-service (QoS) flow, use the qos-flow DOCSIS classifier configuration command. Use the no form of this command to disable this function.
qos-flow qos-flow-ref
no qos-flow
Syntax Description
qos-flow-ref
Specifies the number used to associate the classifier with the QoS flow that has the same qos-flow-ref number. Valid range is 1 to 65535.
Defaults
No default behavior or values.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
Use a qos-flow subcommand to associate a DOCSIS classifier to a DOCSIS QoS flow.
Examples
The following example shows how to associate DOCSIS classifier 1 to DOCSIS QoS flow of 6:
Router(config-classifier)# qos-flow 6Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a QoS flow.
rule-priority
To assign a rule priority to a classifier, use the rule-priority DOCSIS classifier configuration command. Use the no form of this command to disable this function.
rule-priority priority-num
no rule-priority
Syntax Description
priority-num
Specifies the priority level for a classifier. Valid range is 64 to 191. A higher value indicates a higher priority. The default number is 64.
Defaults
The default priority number is 64.
Command Modes
DOCSIS classifier configuration
Command History
Usage Guidelines
The rule-priority command specifies the priority order for the classifier.
Examples
The following example shows how to assign rule-priority 89 to classifier 3:
Router(config-classifier)# rule-priority 89Related Commands
docsis classifier
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
docsis qos-flow
To create a DOCSIS 1.1-like flow that can be assigned to a DOCSIS 1.0+ best-effort or unsolicited grant service (UGS) flow, use the docsis qos-flow global interface configuration command. Use the no form of this command to disable a QoS flow.
docsis qos flow qos-flow-ref subcommand
no docsis qos flow
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global interface configuration
Command History
Examples
The following example shows how to create a DOCSIS 1.1-like QoS flow:
Router(config)# docsis qos-flow 4Router(config-qos-flow)Related Commands
class-id
To assign a DOCSIS 1.0 class-of-service (CoS) request defined in the DOCSIS configuration file to a QoS flow, use the docsis qos-flow class-id interface configuration command. Use the no form of this command to disable this function.
class-id class-id
no class-id
Syntax Description
class-id
Specifies the service class identification number. Valid numbers are 1 to 16. The specified value must match the one defined in the DOCSIS configuration CoS request.
Defaults
No default behavior or default values.
Command Modes
QoS interface configuration
Command History
Examples
The following example shows how to assign a DOCSIS 1.0 class-of-service (QoS) request defined in the DOCSIS configuration file to a QoS flow:
Router(config-qos-flow)# class-id 2Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
custom-queue-list
To assign a custom queue list to an interface, use the custom-queue-list interface configuration command. Use the no form of this command to remove a specific list or all list assignments.
custom-queue-list list
no custom-queue-list
Syntax Description
Defaults
No default behavior or values.
Command Modes
QoS interface configuration
Command History
IOS Release 10.0
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
Only one queue list can be assigned per interface. Use this command in place of the priority-list command (not in addition to it). Custom queueing allows a fairness not provided with priority queueing. With custom queueing, you can control the interface's available bandwidth when it is unable to accommodate the aggregate traffic enqueued. Associated with each output queue is a configurable byte count, which specifies how many bytes of data should be delivered from the current queue by the system before the system moves on to the next queue. When a particular queue is being processed, packets are sent until the number of bytes sent exceeds the queue byte count or until the queue is empty.
Examples
In the following example, custom-queue-list 3 is assigned to DOCSIS QoS flow 4:
Router(config)# docsis qos-flow 4Router(config-qos-flow)# custom-queue-list 3Related Commands
embedded-voice
To enable embedded voice applications to create dynamic classifiers for a DOCSIS QoS flow, use the embedded-voice interface configuration command. Use the no form of this command to disable this function.
embedded-voice count
no embedded-voice
Syntax Description
Defaults
No default behaviors or values.
Command Modes
QoS interface configuration
Command History
IOS release 10.0
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
Using the embedded-voice command on a DOCSIS QoS flow identifies that the flow will be used for voice calls and classifiers should be automatically added and deleted as calls are made and terminated.
Examples
The following example shows how to enable voice call support for three voice calls on a DOCSIS QoS flow.
Router(config)# docsis qos-flow 1Router(config-qos-flow)# embedded-voice 3Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
fair-queue
To enable weighted fair queueing (WFQ) for an interface, use the fair-queue interface configuration command. Use the no form of this command to disable this function.
docsis qos-flow fair-queue [discard-threshold [dynamic-queues [reservable-queues]]]
no docsis qos-flow fair-queue
Syntax Description
Defaults
Fair queueing is enabled by default for physical interfaces whose bandwidth is less than or equal to 2.048 Mbps and that do not use the following: X.25 and Synchronous Data Link Control (SDLC) encapsulations; Link Access Procedure, Balanced (LAPB); tunnels; loopbacks; dialer; bridges; or virtual interfaces. Fair queueing is not an option for these protocols. However, if custom queueing or priority queueing is enabled for a qualifying link, it overrides fair queueing, effectively disabling it.
Additionally, fair queueing is automatically disabled if you enable the autonomous or silicon switching engine mechanisms.
Command Modes
QoS interface configuration
Command History
IOS Release 10.0
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
This command enables WFQ, where packets are classified by flow. For example, packets that have the same source IP address, destination IP address, source TCP or UDP port, destination TCP or UDP port, and protocol belong to the same flow.
When WFQ is enabled for an interface, it provides traffic priority management that automatically sorts through the individual traffic streams without requiring the user to define access lists. WFQ is enabled by specifying the docsis qos-flow fair-queue command only.
When WFQ is enabled for an interface, new messages for high-bandwidth traffic streams are discarded after the configured or default congestive discard threshold has been met. However, low-bandwidth conversations, which include control message conversations, continue to enqueue data. As a result, the fair queue can occasionally contain more messages than its configured threshold number specifies.
Examples
The following example shows how to request a fair queue with a congestive discard threshold of 64 messages, 512 dynamic queues, and 0 RSVP queues:
Router(config-qos-flow) fair-queue 64 512 0Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
grants-per-interval
To enable multiple unsolicited grants-per-interval option for a dynamic flow, use the grants-per-interval interface configuration command. Use the no form of this command to disable this function.
grants-per-interval count
no grants-per-inteval
Syntax Description
Defaults
The grants-per-interval for a DOCSIS QoS flow has a default value of 1.
Command Modes
QoS interface configuration
Command History
Usage Guidelines
For unsolicited grant service, grants-per-interval indicates the actual number of data grants-per-nominal grant interval.
Examples
The following example shows how to set the grant-per-interval for a DOCSIS QoS flow to 2:
Router(config)# docsis qos-flow 5Router(config-qos-flow)# grants-per-interval 2Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
hold-queue
To specify the hold queue limit of an interface, use the hold-queue interface configuration command. Use the no form of this command to restore the default values for an interface.
hold-queue length {out}
no hold-queue
Syntax Description
length
An integer value that specifies the maximum number of packets in the queue.
out
Specifies the output queue.
Defaults
The default output hold queue limit is 40 packets.
Command Modes
QoS interface configuration
Command History
IOS Release 10.0
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
The hold queue stores packets received from the network that are waiting to be sent to the client.
To display the current hold queue setting and the number of packets discarded because of hold queue overflows, use the show interface EXEC command.
Examples
The following example shows how to set an output queue on a DOCSIS QoS flow:
Router(config)# docsis qos-flow 1Router(config-qos-flow)# hold-queue 30Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
show interface
Displays the current hold queue setting.
inactivity
To enable inactivity detection for dynamic QoS flow, use the inactivity interface configuration command. If no packets are sent during the specified inactivity time, then the dynamic flow is deactivated. Use the no form of this command to disable this function.
inactivity minutes
no inactivity
Syntax Description
minutes
Specifies the time, in minutes, that a dynamic flow has not been active. The default is 0 minutes, which disables this function.
Defaults
This function is disabled by default.
Command Modes
Interface configuration
Command History
IOS Release 10.0
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
Use the inactivity command to deactivate a DOCSIS QoS flow if no packets are send during the specified inactivity time.
Examples
The following example shows how to send the inactivity time for DOCSIS QoS flow to 3 minutes:
Router(config)# docsis qos-flow 1Router(config-qos-flow)# inactivity 3Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
nominal-grant-interval
To specify the nominal grant-interval between successive data grant opportunities for the flow, use the nominal-grant-interval interface configuration command. Use the no form of this command to disable this function.
nominal-grant-interval microseconds
no nominal-grant-interval
Syntax Description
microseconds
Specifies the grant, in microseconds. Valid range is 1 to 2,147,483,647 microseconds. The default is 20000.
Defaults
The default nominal grant-interval is 20000 microseconds.
Command Modes
QoS interface configuration
Command History
IOS Release 10.0
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
The nominal grant-interval specifies the nominal interval between successive data grant opportunities for this DOCSIS QoS flow.
Examples
The following example shows how to set the nominal grant-interval to 25000 microseconds for DOCSIS QoS flow 3:
Router(config)# docsis qos-flow 3Router(config-qos-flow)# nominal-grant-interval 25000Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
priority-group
To assign the specified priority list to an interface, use the priority-group interface configuration command. Use the no form of this command to remove the specified priority group assignment.
priority-group list-num
no priority-group
Syntax Description
list-num
Specifies the priority group identification number assigned to the interface. Valid range is 1 to 16.
Defaults
This command is disabled by default.
Command Modes
QoS interface configuration
Command History
IOS Release 10.0
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
Only one list can be assigned per interface. Priority output queueing provides a mechanism to prioritize packets sent on an interface.
Examples
The following example shows how to assign priority-list 1 for packets that will be transmitted on DOCSIS QoS flow 2:
Router(config)# docsis qos-flow 2Router(config-qos-flow)# priority-group 1Related Commands
random-detect
To enable Weighted Random Early Detection (WRED) or Distributed WRED (DWRED), use the random-detect interface configuration command. Use the no form of this command to disable WRED.
random-detect
no random-detect
Syntax Description
This command has no arguments or keywords.
Defaults
WRED is disabled by default.
Command Modes
QoS interface configuration
Command History
Usage Guidelines
WRED is a congestion preventative mechanism that slows traffic by randomly dropping packets when congestion exists. The router automatically determines parameters to use in WRED calculations. For DOCSIS QoS flows, the changing of the parameters used in WRED calculations is not supported. The default exponential weight factor is 9.
Examples
The following example shows how to enable random-detect on DOCSIS QoS flow 4:
Router(config)# docsis qos-flow 4Router(config-qos-flow)# random-detectRelated Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
service-policy
To attach a policy map to a DOCSIS QoS flow to be used as a service policy for that interface, use the service-policy global configuration command. Use the no form of this command to remove a service policy from a DOCSIS QoS flow.
service-policy {output} policy-map
no service-policy {output} policy-map
Syntax Description
output
Attaches the specified policy map to the output interface.
policy-map
The name of a service policy map (created using the policy-map command) to be attached.
Defaults
No service policy is specified.
Command Modes
QoS interface configuration
Command History
12.0(5)T
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
You can attach a single policy map to one or more interfaces.
Currently a service policy specifies class-based weighted fair queueing (CBWFQ). The class policies comprising the policy map are then applied to packets that satisfy the class map match criteria for the class.
To successfully attach a policy map to an interface, the aggregate of the configured minimum bandwidths of the classes comprising the policy map must be less than or equal to 75 percent of the interface bandwidth.
Attaching a service policy and enabling CBWFQ on an interface renders ineffective any commands related to fancy queueing such as commands pertaining to fair queueing, custom queueing, priority queueing, and Weighted Random Early Detection (WRED). You can configure these features only after you remove the policy map from the interface.
You can modify a policy map attached to an interface, changing the bandwidth of any of the classes comprising the map. Bandwidth changes that you make to an attached policy map are effective only if the aggregate of the bandwidth amounts for all classes comprising the policy map, including the modified class bandwidth, is less than or equal to 75 percent of the interface bandwidth. If the new aggregate bandwidth amount exceeds 75 percent of the interface bandwidth, the policy map is not modified.
Examples
The following example shows how to attach policy map policy1 to DOCSIS QoS flow 5:
Router(config)# docsis qos-flow 5Router(config-qos-flow)# service-policy output policy1Related Commands
unsolicited-grant-size
To specify an unsolicited grant size for a dynamic flow, use the unsolicited-grant-size interface configuration command. Use the no form of this command to disable this function.
unsolicited-grant-size bytes
no unsolicited-grant-size
Syntax Description
Defaults
The unsolicited grant size for the unsolicited grant service is 229 bytes.
Command Modes
QoS interface configuration
Command History
Examples
The following example shows how to specify the unsolicited grant size for a dynamic QoS flow to 400 bytes:
(config)# doc qos-flow 1(config-qos-flow)# unsolicited-grant-size 400Related Commands
docsis qos-flow
Creates a DOCSIS 1.1-like classifier that can be assigned to a quality-of-service flow.
microcode cwrsu
To configure the system to load its microcode from the specified path, use the microcode cwrsu global configuration command.
microcode cwrsu [path]
Syntax Description
Defaults
The default path is slot0:/cwrsu.
Command Modes
Global configuration
Command History
Usage Guidelines
The microcode command is not normally needed when using the factory installed images.
Examples
The following example shows how to boot the system image from Flash memory:
router(config)# microcode cwrsu slot0:/cwrsuRelated Commands
microcode reload
Reloads microcode to all linecards or to the specified type of linecard.
microcode reload
To reload microcode to all the line cards or to the specified type of line card, use the microcode reload privileged EXEC command.
microcode reload {all | [type]}
Syntax Description
all
Downloads the microcode to all types of line cards on the radio interface.
type
Specifies the type of the subscriber line card.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The microcode reload command is not normally used, because the microcode is automatically loaded when the router first boots up. This command should not be used unless permitted by Cisco's technical support.
Examples
The following example shows how to reload all hardware types that support downloadable microcode:
router# microcode reloadRelated Commands
microcode cwrsu
Configures the system to load its microcode from the specified path.
radio cable-loss
To specify the effective cable loss (measured in dB) of the cable between the wireless card and the specified wireless transverter, including the power feed panel, connectors, and lightning protection, use the radio cable-loss interface configuration command. To remove the setting, use the no form of this command.
radio cable-loss {auto | antenna-num tx-loss rx-loss}
no radio cable-loss
Syntax Description
Defaults
.No default behaviors or values.
Command Modes
Interface configuration
Command History
12.0(1)XR
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
The following table provides an example of estimated cable, connector, and equipment loss for a typical installation.
Examples
In the following example, the headend Tx cable-loss was measured to be 11 dB, and the headend Rx cable-loss was measured to be 12 dB:
UBR04(config-if)# radio cable-loss 1 11 12Headend ODU Tx Attenuation Setting = 15 dB - 11 dB = 4 dBHeadend IDU Tx Attenuation Setting = 13 dB - 12 dB = 1 dBRelated Commands
show running-configuration interface radio
Displays the current configuration settings, including cable loss.
radio histogram
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 statsParams [bin-range {start end}] [duration interval] [tone {circular | average | number toneVal}] [update interval sum {true | false}]
[width {coarse | fine}]no radio histogram statsParams
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
12.0(7)XR
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
A histogram is a collection of statistics sampled over time on a burst-by-burst basis and presented as a function of bins.
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 duration 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 width parameter.
Note
Note
Examples
The following example shows how to configure a histogram specification. The histogram collection starts as soon as the command succeeds. It collects a histogram for signal to interference plus noise ratio on channel 3. The rest of the parameters are optional, and the system picks default values.
UBR04(config-if)# radio histogram sinr-ant1 3Related Commands
radio hist-display
Displays radio histograms.
radio interface hist-clear
Clears histogram data.
radio hist-display
To control the display of histogram data, use the radio hist-display interface configuration command.
radio histogram {[all] | {statsParams} on | off
Syntax Description
Defaults
By default the histogram display is on.
Command Modes
Interface configuration
Command History
12.0(7)XR
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Examples
The following example shows how to set the display of histogram data for sinr-ant1 on channel 0 to OFF:
UBR04(config-if)# radio hist-display sinr-ant1 0 offRelated Commands
radio histogram
Configures a histogram collection specification.
radio interface hist-clear
Clears histogram data.
radio interface radio mute
To mute the subscriber radio interface for a specified amount of time, use the radio interface radio mute interface configuration command.
radio interface radio slot/port mute duration
Syntax Description
slot/port
Specifies the slot and port numbers of the radio interface.
duration
Specifies the amount of time, in minutes, the radio interface will be muted. valid range is 1 to 65535 minutes.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
To mute the subscriber radio interface for a specified period, use the mute command.
Examples
The following example shows how to mute the subscriber radio interface in slot 2, port 0 for 5 minutes:
Router(config)# radio interface radio 2/0 mute 5radio interface radio rf-update max-power
To specify the maximum transmit power of the subscriber-unit transverter, use the radio interface radio rf-update max-power privileged EXEC command.
radio interface radio slot/port rf-update max-power {antenna-num} pwr-w pwr/2 pwr/4
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command enables an installer to set the maximum power levels for the subscriber-unit transverter. Normally, the maximum power levels set at the factory are sufficient and this command is not used.
Examples
The following example shows how to specify maximum power levels of the subscriber-unit transverter for antenna 1:
Router# radio interface radio 1/0 rf-update max-power 1 47 50 50radio metrics-threshold code-word
To configure thresholds that determine when a second is classified as errored second (ES), degraded second (DS), severely errored second (SES), or consecutively errored second (CSES), use the radio metrics-threshold code-word interface configuration command. This command enables the user to set threshold values for the radio link to measure how well the radio link is performing over time. Use the no form of this command to force the threshold values to the default values.
radio metrics-threshold code-word ESThresh DSThresh SESThresh CSESThresh
no radio metrics-threshold code-word
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Interface configuration
Command History
Examples
The following example configures the radio link such that:
1.
2.
3.
4.
Router(config-if)# radio metrics-threshold code-word 3 2.1 5.2 4Related Commands
radio metrics-threshold 1hour
To configure the threshold limits for ES, SES, CSES, and degraded minutes (DM), use the radio metrics-threshold 1hour interface configuration command. When these limits are exceeded in a 1-hour period, minor alarms are displayed on the console. Use the no form of this command to force the thresholds to the default values.
radio metrics-threshold 1hour ESLimit SESLimit CSESLimit DMLimit
no radio metrics-threshold 1hour
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure the link metric-threshold settings:
Router(config-if)# radio metrics-threshold 1hour 24 36 12 5Related Commands
radio self-test
To test the memory and hardware integrity of the wireless modem card, use the radio self-test interface configuration command. To configure a link without a self-test, use the no form of this command.
radio self-test
no radio self-test
Syntax Description
Defaults
Self-test is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
Self-test is executed at the time when microcodes are loaded in each of the field programmable gate arrays (FPGAs) and digital signal processes (DSPs) when the router loads or after a microcode reload command is executed. Self-test is not executed on each no shut command.
Examples
The following example shows how to download and execute self-tests each time the modem card is enabled:
UBR04(config-if)# radio self-testRelated Commands
radio snapshot
To create a snapshot specification on the modem card, use the radio snapshot interface configuration command. To delete a specification and its associated data, use the no form of this command.
radio snapshot dspNum snapshotType [syncState]
no radio snapshot dspNum
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
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 the bitwise OR data as many as four of the snapshot types.
Examples
The following example shows how to create a snapshot specification for dsprx0:
Router(config-if)# radio snapshot dsprx0 1 initial-rangingRelated Commands
radio threshold
To configure a threshold specification, use the radio threshold interface configuration command. To delete a threshold specification, use the no form of this command.
radio threshold statsParams threshType threshValue [repeat-time] [clear-time] [dsp dspNum]
no radio threshold statsParams threshType
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
The following describes how clear-time and repeat-time work for the three scenarios:
1.
2.
a.
b.
3.
a.
b.
Examples
The following examples shows how to configure threshold specification for sinr-ant1 on channel 0:
Router(config-if)# radio threshold sinr-ant1 0 high 30Related Commands
show interface radio thresholds
Displays the set of currently configured thresholds on the radio card.
radio timeline
To configure a timeline collection specification, use the radio timeline interface configuration command. To delete a timeline, use the no form of this command.
radio timeline statsParams size [dsp dspNum] [print-options {on | off}] [sampling-period value] [tone {circular | average | number toneVal}]
[Trigger threshParams ThreshType PostTrigBufmgt]no radio timeline statsParams
Syntax Description
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Usage Guidelines
A timeline is a sequence of data values collected for a specified attribute. The amount of data collected is controlled by the size parameter. The maximum size is 1000 points.
Collection starts as soon as the command succeeds and continues until the Trigger option occurs or the radio interface radio tl-stop command is executed.
Note
Examples
The following example shows how to configure a timeline specification. The collection process starts as soon as the command succeeds. It collects a timeline for sirn-ant1. The timeline is collected on channel 3. The timeline size is 600 points. The rest of the parameters are optional and the system picks default values.
UBR04# radio timeline sinr-ant1 3 600Related Commands
show controllers radio
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-num/port-num [{if | rf | fir | codec | rfsm | rxdsp | txdsp| us | ds | host |}]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify any option, all the hardware subsystem information appears. Actual output parameters depend on the hardware and implementation.
Examples
The following example shows how to display the attributes of a radio modem card:
Router# show controllers radioRelated Commands
show controllers radio downstream
To display downstream port information for a wireless modem card, use the show controllers radio downstream EXEC command. To disable this function, use the no form of this command.
show controllers radio slot/downstream-port downstream
no show controllers radio slot/downstream-port downstream
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
The following example shows how to display downstream port information in slot number 3, port number 0:
Router# show controllers radio 3/0 downstreamRadio 3/0 Downstream is upFrequency not set, Channel Width 6 MHz, 64-QAM,Symbol Rate 5.056941 MspsFEC ITU-T J.83 Annex B, R/S Interleave I=12, J=17Related Commands
show controllers radio if
To display the IF hardware information for the specified radio interface, use the show controllers radio if EXEC command. To disable this function, use the no form of this command.
show controllers slot/port radio if
no show controllers slot/port radio if
Syntax Description
Defaults
No default behaviors or values.
Command Modes
EXEC
Command History
Usage Guidelines
The following IF information is displayed:
•
•
•
Examples
The following example shows the displayed information for the IF hardware in slot number 3, port number 0:
UBR04# show controllers 3/0 radio ifIF Hardware Identification Info:Checksum: 0xc4PROM version: 0x01Card Type: 0xb0Vendor name: ciscoPart number: 800-99999-15Board number: 73-0905-09HW Rev Code: A0Serial Number: SN123456789Date Code: 122019999IF Hardware Capability Info:Capability flag1: 0x1fCapability flag2: 0x0Tx gain min: 5, max: 22, step: 4FLL nomimal freq: 5FLL minimum freq: 5FLL maximum freq: 5Rx1 gain min: 5, max: 20, step: 2Rx2 gain min: 5, max: 20, step: 2Rx frequency: 330000Tx frequency: 346000Channelization max: 0, freq: 0RX1 Cable comp: 3 dBRX2 Cable comp: 3 dBRelated Commands
show controllers radio rf
To display the RF hardware information for the specified radio interface, use the show controllers radio rf EXEC command. To disable this function, use the no form of this command.
show controllers slot/port radio rf
no show controllers slot/port radio rf
Syntax Description
Defaults
No default behaviors or values.
Command Modes
EXEC
Command History
Usage Guidelines
The following RF information is displayed:
•
•
•
Examples
The following example shows the displayed information for the RF hardware in slot number 3, port number 0:
UBR04# show controllers 3/0 radio rfRF Hardware Identification Info:Checksum: 0xfePROM version: 0x01Card Type: 0x10Vendor name: ciscoPart number: 800-11111-15Board number: 73-0909-09HW Rev Code: A0Serial Number: SN123456789Date Code: 122019999RF Hardware Capability Info:Capability flag1: 0xe0Capability flag2: 0x01Duplexer info:Band1 freq1: 0, freq2: 0Band2 freq1: 0, freq2: 0Tx insertion loss: 0Tx Lo/Hi: 0Date Code: 0Max chan. BW: 1Tx frequecy bands: 1, step: 1min: 220000, max: 460000Rx frequecy bands: 2, step: 1min1: 220000, max1: 360000min2: 410000, max2: 440000IF Tx freq: 330000IF Rx freq: 346000Freq reference: 0Tx power range min: 10, max: 23, step: 1Tx fixed gain min: 0, max: 22, step: 1Rx fixed gain min: 0, max: 22, step: 1Tx var gain min: 0, max: 22, step: 2Rx var gain min: 0, max: 22, step: 2Temp. threshold low: 4, high: 5TX Cable comp: 3 dBRF RX Frequency: 230000000 kHzRF TX Frequency: 250000000 kHzRelated Commands
show controllers radio upstream
To display upstream port information for a wireless modem card, use the show controllers radio upstream EXEC command. Use the no form of this command to disable this function.
show controllers radio slot/upstream-port upstream
no show controller radio slot/upstream-port upstream
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
The following example shows how to display information for upstream 0 in slot number 3, port number 0:
CMTS01# show controllers radio 3/0 0 upstreamRadio 3/0 Upstream 0 is upFrequency 5.008 MHz, Channel Width 0.200 MHz, QPSK Symbol Rate 0.160 MspsSpectrum Group 4Nominal Input Power Level 5 dBmV, Tx Timing Offset 0Ranging Backoff Start 16, Ranging Backoff End 16, Tx Backoff Start 16Tx Backoff End 16, Modulation Profile Group 1part_id=0x3137, rev_id=0x01, rev2_id=0xFFnb_agc_thr=0x0000, nb_agc_nom=0x0000Range Load Reg Size=0x58Request Load Reg Size=0x0EMinislot Size in number of Timebase Ticks is = 8Minislot Size in Symbols =8Bandwidth Requests = 0x0Piggyback Requests = 0x0Invalid BW Requests= 0x0Minislots Requested= 0x0Minislots Granted = 0x0Minislot Size in Bytes = 2UCD Count = 0DES Ctrl Reg#0 = C00C0C43, Reg#1 = 0Related Commands
show docsis radio error
To display the content of the DOCSIS error log, use the show docsis radio error privileged EXEC command.
show docsis radio slot/port error
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display the content of the DOCSIS error log radio modem in slot 2, port 0:
radiosu# show docsis radio 2/0 error128568.624 T05.0 Loss of Sync. Missed 5 in a row after having SYNCed at one timeRelated Commands
show docsis radio log
To display the content of the DOCSIS activity log, use the show docsis radio log privileged EXEC command.
show docsis radio slot/port log
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display the content of DOCSIS activity log for radio modem in slot 2, port 0. Note that the example below is a portion of the content that would be displayed when the command is executed.
radiosu# show docsis radio 2/0 log128450.468 CMAC_LOG_RESET_FROM_DRIVER128450.468 CMAC_LOG_STATE_CHANGEwait_for_link_up_state128465.668 CMAC_LOG_LINK_DOWN128465.668 CMAC_LOG_LINK_UP128465.668 CMAC_LOG_STATE_CHANGE128465.668 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND81/111025000/117025000/6000000128465.668 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND80/93000000/105000000/6000000128465.668 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND79/453000000/855000000/6000000128465.668 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY 0128468.084 CMAC_LOG_DS_CHANNEL_SCAN_COMPLETED128468.084 CMAC_LOG_STATE_CHANGE wait_ucd_state128468.436 CMAC_LOG_UCD_MSG_RCVD 1Related Commands
show docsis radio map
To display the content of the DOCSIS debug driver map buffer, use the show docsis radio map privileged EXEC command. Use this command in conjunction with debug docsis driver map command to display the DOCSIS MAC map frames.
show docsis radio slot/port map
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
In the following example, the first command activates debugging of DOCSIS maps that identify data on the DOCSIS interfaces. The second command displays the content of the DOCSIS debug driver map buffer for the radio modem in slot 2, port 0. Note that the content displayed is a portion of the content that would be displayed when the user enters this command.
radiosu# debug docsis driver mapradiosu#1d11h: Radio2/0: ***** MAP buffer full ******radiosu# show docsis radio 2/0 mapIOS time UChId Ucd #IE SU Time Alloc time Ack Time Rng B Data BAdvance 0 1 5 4 0x006EE380 0x006EE39F 0x006EE249 0 30 4 (31)RA/16383/0 RA/16383/10 RA/16383/20 NL/0/210 1 5 4 0x006EE395 0x006EE3B4 0x006EE25E 0 3 0 4(31)RA/16383/0 RA/16383/10 RA/16383/20 NL/0/214 1 5 4 0x006EE3AA 0x006EE3C9 0x006EE273 0 3 0 4(31)RA/16383/0 RA/16383/10 RA/16383/20 NL/0/214 1 5 4 0x006EE3BF 0x006EE3DE 0x006EE288 0 3 0 4Related Commands
show docsis radio qos
To display information about the quality-of-service (QoS) mapping of packet classifiers to DOCSIS flows, use the show docsis radio qos privileged EXEC command.
show docsis radio slot/port qos
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display information about the QoS mapping of packet classifiers to DOCSIS flows for radio modem in slot 2, port 0:
radiosu# show doc radio 2/0 qosFlow SID Flow Class SID Last Clfr Dynamic TotalRef Type State Id Status SID Match Clfrs Clfrs------ ------- -------- -- -------- --- --------- ------ ------1 Primary In Use 1 Active 141 never 0 02 Static In Use 2 Active 142 00:04:50 0 13 Dynamic Idle NA No SID 00:03:48 0 2Flow Clfr ClassifierPri Ref Id Matches Details--- ------ ------ ------- ----------100 3 1 0 IP source: 192.1.1.2IP source mask: 255.255.255.255IP dest: 201.1.1.35IP dest mask: 255.255.255.255IP Protocol: 1764 2 1 5 IP dest: 201.1.1.11IP dest mask: 255.255.255.25564 3 2 5 IP dest: 201.1.1.10IP dest mask: 255.255.255.255Related Commands
show docsis radio resets
To display the reset entries in the DOCSIS activity log buffers, use the show docsis radio resets privileged EXEC command.
show docsis radio slot/port resets
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display the reset entries in the DOCSIS activity log buffer for the radio modem in slot 2, port 0:
radiosu# show docsis radio 2/0 resetsl30067.488 CMAC_LOG_RESET_FROM_DRIVER130082.448 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED130096.412 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILEDRelated Commands
show docsis radio sid
To display information about the active DOCSIS subscriber IDs, use the show docsis radio sid privileged EXEC command.
show docsis radio slot/port sid [queue-identifier [queue]]
Syntax Description
slot/port
Specifies the slot and port numbers of the radio modem.
queue-identifier
Specifies the queue number assigned to a subscriber ID.
queue
Displays detailed queue information.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display information about the active DOCSIS subscriber ID 0 for the radio interface in slot 2, port 0:
Router# show docsis radio 2/0 sid 0 queueInterface Radio2/0[0] (SID 141)Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: weighted fairOutput queue: 0/40/64/0 (size/max total/threshold/drops)Conversations 0/1/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)The following example shows how to display summary information about the active DOCSIS subscriber ID 0 for the radio interface in slot 2, port 0:
Router# show docsis radio 2/0 sid 0Related Commands
show docsis radio state
To display detailed information about the state of the DOCSIS interface, use the show docsis radio state privileged EXEC command.
show docsis radio slot/port state
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display information about the state of the DOCSIS interface:
radiosu# show docsis radio 2/0 stateRelated Commands
show interface radio accounting
To display radio accounting information for a wireless modem card, use the show interface radio accounting privileged EXEC command.
show interface slot/downstream-port [accounting]
Syntax Description
Defaults
No default behaviors or values.
Command Modes
EXEC
Command History
Examples
The following example shows how to display the radio accounting information table for the wireless modem card in slot 6, port 0:
CMTS01# show interfaces radio 6/0 accountingRadio 6/0Protocol Pkts In Chars In Pkts Out Chars OutIP 5386 623076 5375 644712ARP 5522 231924 37 1776show interface radio alc
To display the automatic power level control (ALC) and power ranging configuration information for the downstream, use the show interface radio alc privileged command.
show interface slot/downstream-port alc
Syntax Description
Defaults
No default behaviors or values.
Command Modes
EXEC
Command History
Examples
The following example shows how to display the ALC and power ranging configuration information for the wireless modem card in slot 5, port 0:
uBR7200# show interfaces radio 5/0 alcPower Ranging: on; Automatic power Level Control: onPower SID Schedule interval = 100 ms;IF Loop Mode = standard; RF Loop Mode = fast.Power SID = 64:MAC address MSID TSID ALC Primary SID00e0.1eab.2c0b 0 0 100e0.1eb2.bb07 0 1 2show interface radio hist-data
To display histogram data, use the show interface radio hist-data EXEC command.
show interface radio slot/port hist-data statsParams
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
The following example shows how to display histogram data for sinr-ant1 on channel 0 for the radio card in slot 6, port 0:
Router# show int r6/0 hist-data sinr-ant 0Related Commands
show interface radio hist-spec
To display histogram specifications, use the show interface radio hist-spec EXEC command.
show interface radio slot/port hist-spec [statsParams]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
The following example shows how to display the histogram specification for sinr-ant1 on channel 0 for the radio card in slot 6, port 0:
Router# show int r 6/0 his-spec sinr-ant1 0Related Commands
show interface radio led
To display the status of light-emitting diodes (LEDs) on the wireless modem card and to display the events related to the major and minor LEDs, use the show interface radio led EXEC command.
show interface radio slot/port led [major-events | minor-events]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
The following is a list of the LEDs and their functions for the multipoint wireless modem card:
Examples
The following example shows how to display the status of the LEDs:
Router# show int radio 6/0 led
LED Name
Status
Enabled
GREEN
Major alarm
OFF
Minor alarm
OFF
Out of Service
OFF
Carrier
GREEN
Send Data
GREEN
Receive
GREEN
show interfaces radio metrics
To display the parameters measured during the operation of the radio link, use one of the following show interfaces radio metrics commands in privileged EXEC mode. These metrics provide a quantitative measure of how well the per subscriber link or per channel is performing over time.
Metrics that quantify how well the radio link performed after the system was powered on:
show interfaces radio slot/port link-metrics
Metrics that quantify how the link performed while the two ends of the link were synchronized:
show interface radio slot/port 1hour-metrics lm_options
show interface radio slot/port 1minute-metrics lm_options
show interface radio slot/port 1second-metrics
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
Two classes of metrics are maintained by the radio link's software and hardware for the subscriber-end. One class of metrics, link-metrics, maintains the cumulative metrics for the entire collection. The second class of metrics maintains a table of values that show the time when the two ends of the link (headend and subscriber-unit) were synchronized. The second class of metrics consists of 1hour-metrics, 1minute-metrics, and 1second-metrics.
When 1hour-metrics is specified, a table of values for the preceding 24 hours is displayed. Values are cumulative—every successive row is the sum of the corresponding values in the precious row plus the values determined for the 1-hour period represented by that row.
When 1minute-metrics is specified, a table of values for the last 60 minutes are displayed. Values are cumulative—every successive row is the sum of the corresponding values in the previous row plus the values determined for the 1-minute period represented by that row. The values displayed are identical to those displayed for 1hour-metrics, except that the period is 1 minute.
When 1second-metrics is specified, a table of values for the last 60 seconds is displayed. Values are cumulative—every successive row is the sum of the corresponding values in the previous row plus the values determined for the 1-second period represented by that row.
Table 2 provides descriptions for the values displayed for the link-metrics command:
Examples
The following example shows how to display the link metrics for the wireless modem card in slot 6, port 0 of the Cisco uBR7200 series router:
Router# show interface radio 6/0 link-metricsRadio link metrics.Collected from 16:40:06 UTC Tue Dec 11 1997to 17:06:51 UTC Tue Jan 11 2000Availability of the physical link:Available seconds (EFS+ES-SES): 2y2w4d 00:00:03 : 98.16228%Unavailable seconds (SES+SLS): 2w 00:05:00 : 1.83772%Total : 2y4w4d 00:05:03 : 100.00000%Error characteristics of the physical link:Error free seconds (EFS): 2y2w 21:33:03 : 97.75518%Errored seconds (CWerr>=1 )(ES): 3d 02:32:00 : 0.40755%Degraded seconds( 5.00000>CWerr>= 1.00000%)(DS): 04:00:00 : 0.02187%Severely errored seconds (CWerr>= 5.00000%)(SES): 00:05:00 : 0.00045%Sync Loss seconds (SLS): 2w 00:00:00 : 1.83726%Synchronization event counters:Initial Synchronization seconds : 00:04:29Time since last successful synchronization : 1w 01:00:23Time since last synchronization failure : 6w 00:01:47Synchronization attempts - Successful : 2 : Unsuccessful : 1Recovery attempts - Medium effort : 1 : High effort : 1Physical link data rates:Effective rate : 22566127Percent efficiency : 99.99652%The following example shows a sample display for the 1-hour link metrics for the wireless modem card in slot 6, port 0.
Router(config)# show interface radio 6/0 1hour-metricscaptured at 13:08:14 UTC Tue Nov 23 1999=====|=========|==========|==========|==========|==========|==========|Hour| Time | EFS | ES | SES | CSES | DM |Ago | | | | | | |=====|=========|==========|==========|==========|==========|==========|0 16:00:23 57599 1 1 0 0Table 3 provides the description for the output of the 1hour-metrics command.
The following example shows how to display the output for the 1hour-metrics command with the all option specified.
Router(config-if)# show interfaces radio 6/0 1hour-metrics allTable 4 provides the description for the additional fields of the link-metrics command when specifying the all option.
The following example shows how to display the output for the 1hour-metrics code-words command:
router# show interfaces radio 6/0 1hour-metrics code-wordsCaptured at 13:08:14 UTC Tue Nov 23 1999=====|=========|==========|==========|==========|==========|Hour| Time | Total CW | Total | SYNC Loss| Valid DP |Ago | | | Error CW | Sec | |=====|=========|==========|==========|==========|==========|0 16:00:23 57599 0 1 23The following example shows how to display the output for the 1second-metrics power command:
router# show interfaces radio 6/0 1second-metrics powerCaptured at 13:08:14 UTC Tue Nov 23 1999=====|=========|==========|==========|==========|==========|==========|==========|=======Sec | Time | Total | Total | Sec type | Max Rx | Ave Rx | Min Rx | Max Tx | Ave Tx | Min Tx | Valid DP |Ago | | CW | Err CW | | Power | Power | Power | Power | Power | Power | |=====|=========|==========|==========|==========|==========|==========|==========|=======0 16:00:23 57599 1 1 0 0Related Commands
clear radio link-metrics
Clears the link-metrics table.
show interface radio metrics-threshold
Displays the current link-metrics configuration thresholds for a radio modem.
show interface radio metrics-threshold
To display the set of currently configured thresholds on the radio card on the specified DSP, use the show interface radio metrics-threshold privileged EXEC command.
show interface radio slot/port metrics-threshold
Syntax Description
Defaults
No default behavior or values.
Command Modes
privileged EXEC
Command History
Usage Guidelines
If dspNum is not specified, the thresholds for DSP 3 appear.
Examples
The following example shows how to display the current link-metrics threshold configured for the radio modem in slot 6, port 0 of the router:
Router# show interface radio 6/0 metrics-thresholdCodeword error thresholds:Error second threshold (Units: Codeword errors) = 1Degraded second threshold (Units: Codeword errors) = 3.00000Severely errored second threshold (Units: Codeword errors) = 10.00200Consecutively Severely errored second threshold (Units: Errored seconds) = 3One hour alarm thresholds:Error Seconds(ES) (Units:seconds) = 10Severely Errored Seconds(SES) (Untis:seconds) = 1Consecutively Severely Errored Seconds(CSES) (Units seconds) = 3Degraded Minutes(DCM) (Units: minutes) = 1Related Commands
radio thresholds
Configures a threshold event specification.
show interfaces radio link-metrics
Displays the parameters measured during the operation of the radio link.
show interface radio snapshot
To display snapshot information, use the show interface radio snapshot privileged EXEC command.
show interface radio slot/port snapshot dspNum
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Examples
The following example shows how to display snapshot information for dsp1a on the modem card in slot 3, port 0:
UBR04#show interfaces radio 3/0 snapshot dsp1aRelated Commands
show interface radio snap-data
To display snapshot information, use the show interface radio snap-data privileged EXEC command.
show interface radio slot/port snap-data dspNum
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Examples
The following example shows how to display snapshot information for dsp dsp1a on the modem card in slot 3, port 0:
UBR04#show interfaces radio 3/0 snap-data dsp1aRelated Commands
show interface radio snap-spec
To display snapshot specification information, use the show interface radio snap-spec privileged EXEC command.
show interface radio slot/port snap-spec dspNum
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display snapshot specification information for dsprx0 on the modem card in slot 3, port 0:
UBR04#show interfaces radio 3/0 snap-spec dsprx0Related Commands
radio snapshot
Creates a snapshot specification.
show interface radio snap-data
Displays data captured for the snapshot specification.
show interface radio thresholds
To display the set of currently configured thresholds on the radio modem card, use the show interface radio thresholds privileged EXEC command.
show interface radio slot/port thresholds
Syntax Description
Defaults
No default behavior or values.
Command Modes
privileged EXEC
Command History
12.0(7)XR
This command was introduced.
12.1(3)XQ1
Multipoint wireless support was added.
Usage Guidelines
If dspNum is not specified, the thresholds for DSP 3 appear.
Examples
The following command displays 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 i+n 3Statistic parameter i+nchannel id 3Threshold Type downChangeThreshold Value 200Threshold Repeat Time 5Threshold Clear Time 8Index 2Default Threshold falseRelated Commands
show interface radio tl-data
To display the timeline data collected for the identified specifications, use the show interface radio lt-data privileged EXEC command.
show interface radio slot/port tl-data [statsParams]
Syntax Description
Defaults
No default behavior or values.
Command Modes
privileged EXEC
Command History
Examples
The following example shows how to display the timeline data for sinr-ant1 on channel 0 for the radio card in slot 6, port 0:
Router# show int r 6/0 tl-data sinr-ant1 0Related Commands
show interface radio tl-spec
To display the details of the currently configured timeline specifications, use the show interface radio tl-spec privileged EXEC command.
show interface radio slot/port tl-spec [statsParams]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to display the timeline specification for the radio card in slot 6, port 0:
Router# show int r 6/0 tl-specRelated Commands
Debug Commands
This section documents new debug commands. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
•
debug docsis arp
To activate debugging of Address Resolution Protocol (ARP) request messages on the DOCSIS interfaces, use the debug docsis arp command. Use the no form of this command to deactivate debugging of ARP requests.
debug docsis arp
no debug docsis arp
Syntax Description
This command has no arguments or keywords.
Defaults
Deactivated
Command History
Examples
The following example shows how to display ARP requests:
CMTS01# debug docsis arpdebug docsis err
To debug error messages that occur in the DOCSIS MAC protocol, use the debug docsis err privileged EXEC command. Use the no form of this command to disable the debugging of MAC protocol error messages.
debug docsis err
no debug docsis err
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command History
Examples
The following example shows how to enable debugging of DOCSIS error messages:
Router# debug docsis errdebug docsis keyman
To display debug messages for the traffic encryption
Guest
