|
|
This appendix describes the cable-specific commands that have been added or changed for the Cisco uBR924 cable access router in the Cisco IOS 12.1 T software releases. These commands are in addition to the commands that are supported in Cisco IOS Release 12.1(1). For a description of the commands in these previous releases, see the command reference documentation for Cisco IOS Release 12.1, available on CCO and the Documentation CD-ROM.
 |
Note To locate the documentation for the "related commands" mentioned in this chapter, use the Cisco IOS Release 12.1 command reference master index that is available on CCO and the Documentation CD-ROM. You can also search for the specific command online. |
The commands in this appendix are listed alphabetically:
In Cisco IOS Release 12.1(2)T and greater, certain commands are reserved for DOCSIS use and are no longer available in the CLI. See "Commands Reserved for DOCSIS Use" section.
|
Note This appendix does not describe new commands that are not specific to the Cisco uBR924 cable access router. For a description of these other commands, see the New Features in Release 12.1 T section on CCO and the Documentation CD-ROM. |
To configure the Cisco uBR924 cable access router so that it configures its Ethernet interface or Network Address Translation (NAT) address pool with an IP address supplied by the DHCP server, use the cable-modem dhcp-proxy cable interface command. To disable this feature (so that you can then manually assign an IP address to the Ethernet interface or NAT address pool), use the no cable-modem dhcp-proxy cable interface command.
cable-modem dhcp-proxy {interface ethernet number | nat pool-name} |
Note This command cannot be used when the Cisco uBR924 cable access router is configured for DOCSIS bridging. |
Syntax Description
interface ethernet number The Ethernet interface to be assigned the static IP address from the DHCP server. (Because the Cisco uBR924 router has only one Ethernet interface, the only allowable number is 0). nat pool-name The name of the NAT pool to be created using the IP address and subnet mask supplied by the DHCP server. (This is equivalent to giving the ip nat pool pool-name start-ip end-ip netmask subnet command, using the IP address and subnet mask supplied by the DHCP server.)
Note This option should be used only when the Cisco uBR924 router is configured for routing mode.
Defaults
No default behavior or values.
Command Modes
Interface configuration (cable interface only)
Command History
12.1(1)T This command was introduced for the Cisco uBR924 router.
Release
Modification
Usage Guidelines
This command is useful in two situations:
After configuring the Cisco uBR924 cable access router with the cable-modem dhcp-proxy command, reboot the router. During the DOCSIS provisioning process, the router sends a DHCP client request to obtain an IP address for the cable interface.
The router then sends a proxy DHCP request to the DHCP server using the Ethernet interface's MAC address. The DHCP server replies with a second IP address that the router assigns to either the Ethernet interface or to the NAT pool, depending on which option was used in the cable-modem dhcp-proxy command.
|
Note When replying to the proxy request for the Ethernet interface, the DHCP server should assign an IP address on the same network as the CPE devices that are attached to the router's Ethernet interface. |
Examples
The following example configures the Cisco uBR924 cable access router so that it makes a proxy DHCP request to obtain an IP address for its Ethernet interface:
ubr924(config)# int c0 ubr924(config-if)# cable-modem dhcp-proxy interface Ethernet 0
The following example creates a NAT address pool with the IP address assigned by the DHCP server; this IP address must be in the network attached to the Ethernet address (which in this case is 192.168.100.0).
ubr924(config)# ip nat inside source list 1 pool net-208 overload ubr924(config)# interface cable0 ubr924(config-if)# ip nat outside ubr924(config-if)# no cable compliant bridge ubr924(config-if)# cable-modem dhcp-proxy nat net-208 ubr924(config-if)# exit ubr924(config)# interface ethernet0 ubr924(config-if)# ip address 192.168.100.94 255.255.255.0 ubr924(config-if)# ip nat inside ubr924(config-if)# exit ubr924(config)# access-list 1 permit 192.168.100.0 0.0.0.255 ubr924(config)#
Related Commands
None.
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)XR and 12.1(1)T This command was introduced for the Cisco uBR924 router.
Release
Modification
Usage Guidelines
This command begins the display of debug messages that show the dynamic service MAC messages that are generated when a voice call is made using the dynamic SID feature. Dynamic SIDs use the following DOCSIS MAC-layer messages to create a new SID when a voice call is made and to delete it when the call is over:
|
Note Dynamic Services are described in the DOCSIS 1.1 specification (SP-RFIv1.1-I03-991105 or later revision). |
Examples
The following example enables the display of debug messages related to dynamic service operations:
ubr924# debug cable-modem mac messages dynsrv ubr924#
The following example turns off the display of debug messages related to dynamic service operations:
ubr924# no debug cable-modem mac messages dynsrv ubr924#
The following are examples of the types of debug messages that are displayed when a voice call is made. This example shows that dynamic SID 52 is created for this particular call.
DSA-REQ TLV's:
--------------
US Flow Scheduler(24):
Unsolicited Grant Size - 19:2:89
Nominal Grant Interval - 20:4:20000
Created New Dynamic Service State, Transaction_id = 3
DSA-REQ MESSAGE TLVS
--------------------
C2000026 00010010 07DF6854 00507366
23270014 00000301 0F000003 180A1302
00591404 00004E20
597.721 CMAC_LOG_DSA_REQ_MESSAGE_EVENT
DSA-REQ MESSAGE
---------------
FRAME HEADER
FC - 0xC2 == MAC Management
MAC_PARM - 0x00
LEN - 0x26
MAC MANAGEMENT MESSAGE HEADER
DA - 0010.abcd.ef00
SA - 0050.abcd.ef00
msg LEN - 14
DSAP - 0
SSAP - 0
control - 03
version - 01
type - 0F == DSA-REQ
RSVD - 0
Transaction ID - 3
597.725 CMAC_LOG_DSA_RSP_MSG_RCVD
DSA-RSP MESSAGE
---------------
FRAME HEADER
FC - 0xC2 == MAC Management
MAC_PARM - 0x00
LEN - 0x26
MAC MANAGEMENT MESSAGE HEADER
DA - 0050.abcd.ef00
SA - 0010.abcd.ef00
msg LEN - 14
DSAP - 0
SSAP - 0
control - 03
version - 01
type - 10 == DSA-RSP
RSVD - 0
Transaction ID - 3
Response - 0 == DSA-RSP-OK
SID - 52
Adding sid = 52 to sid_index = 1
597.729 CMAC_LOG_QOS_ADD_FLOW_SID 52
Related Commands
debug cable-modem mac messages Displays debug messages for other types of MAC-layer messages, including MAP messages, upstream request messages, and sync messages. show controllers cable-modem number qos Displays current statistics for each primary, secondary, and dynamic SIDs.
Command
Description
 |
Caution The debug commands are primarily intended for use in controlled test and troubleshooting situations with a limited volume of traffic. You should use caution when enabling debug messages because sending these messages to the console consumes system resources. Turning on too many types of debug messages can adversely affect the router's network performance, depending on what messages are being displayed and the type of traffic that is occurring. |
Syntax Description
cisco-rtp Forwards DTMF tones using the Real-Time Transport Protocol (RTP) with a Cisco proprietary payload type. h245-alphanumeric Forwards DTMF tones using the H.245 Alphanumeric User Input Indication method. This transmits each tone using a fixed duration of 500 milliseconds. Supports tones 0-9, *, #, and A-D. h245-signal Forwards DTMF tones using the H.245 Signal User Input Indication method. This transmits each tone using the original duration. Supports tones 0-9, *, #, and A-D.
Note RTP is a proprietary Cisco protocol that interoperates only between two Cisco access servers or routers running Cisco IOS images that support the RTP protocol. This typically requires Cisco IOS 12.0(5)T or later releases; see the router's release notes for complete information.
Defaults
By default, DTMF tones are transmitted inband, as part of the voice traffic.
Command Modes
Dial-peer voice configuration mode.
Command History
12.0(1)T This command was introduced. 12.0(2)XH This command was modified to include the h245-signal keyword. 12.0(5)T This command was modified for H.323 V2. 12.0(7)XR and 12.1(1)T Support was added for the Cisco uBR924 cable access router.
Release
Modification
Usage Guidelines
DTMF tones are generated when you press the keypad digits on a touch-tone phone. DTMF tones are most commonly used to dial calls, but they can also be used during a call to interact with an Interactive Voice Response (IVR) system, such as voicemail, automated banking services and so on. By default, DTMF tones are transmitted along with the regular voice traffic, but this can cause problems with some IVR systems.
In particular, IVR systems might not recognize DTMF tones when using highly compressed CODECs such as G.729 and G.723.1. These CODECs are highly optimized for voice frequencies, but they can distort DTMF tones, preventing IVR systems from recognizing the tones. To avoid this problem, use one or more of the following methods of transmitting DTMF tones in an out of band channel, separately from the voice traffic:
|
Note The Cisco RTP option is a proprietary Cisco implementation and operates only between Cisco universal access servers or routers that are running Cisco IOS Release 12.0(2)XH (or later). |
You can enable more than one DTMF relay option for a particular dial peer, to support multiple destinations that might use different methods. If you enable more than one option, and if the peer is capable of receiving DTMF in more than one of these formats, the router selects the DTMF format with the highest priority:
1. Cisco RTP (highest priority)
2. H.245 Signal
3. H.245 Alphanumeric
4. None---DTMF is sent inband
Examples
The following example configures an outgoing dial peer so that DTMF tones to that destination are transmitted using the Cisco RTP protocol, if it is supported by the remote end; otherwise, the DTMF tones are transmitted using the H.245 signaling protocol.
ubr924(config)# dial-peer voice 100 voip ubr924(config-dial-peer)# destination-pattern 555-1212 ubr924(config-dial-peer)# session target ipv4:192.168.100.110 ubr924(config-dial-peer)# dtmf-relay cisco-rtp h245-signal ubr924(config-dial-peer)# exit ubr924(config)#
The following example reconfigures the above dial peer and disables out of band DTMF signaling, so that the DTMF tones are sent inband, as part of the voice traffic:
ubr924(config)# dial-peer voice 100 voip ubr924(config-dial-peer)# no dtmf-relay ubr924(config-dial-peer)# exit ubr924(config)#
Related Commands
codec Specifies the voice coder rate of speech for a dial peer. dial-peer Enters dial peer voice configuration mode.
Command
Description
Syntax Description
ip-address Specifies the IP address (in dotted decimal notation) to be used for all outgoing H.323 traffic, which includes H.225, H.245, and RAS messages. This typically is the IP address assigned to the Ethernet interface.
Defaults
No defaults assigned. By default, H.323 traffic is transmitted with the IP address assigned to the cable interface.
Command Modes
Interface configuration
Command History
12.1(2)T This command is introduced for the Cisco uBR924 router.
Release
Modification
Usage Guidelines
The h323-gateway voip bind command can be used with any interface, but it is primarily used with the Cisco uBR924 router's Ethernet interface when configuring a virtual private network (VPN). In this configuration, the h323-gateway voip bind command configures the router so that VoIP traffic is sent using the IP address of the Ethernet interface (as opposed to the default behavior, which is to use the IP address of the default outgoing interface, which is the cable interface).
The h323-gateway voip bind command allows the enterprise network to maintain the H.323 gatekeeper and gateway in the enterprise network's address space. Without the h323-gateway voip bind command, outgoing voice traffic uses the IP address of the cable interface. This requires that the H.323 gatekeeper and gateway be maintained in the cable service provider's address space, which is not desirable if the enterprise needs to control the voice network and VPN configuration.
|
Note The h323-gateway voip bind command can be used only when the Cisco uBR924 cable access router is operating in routing mode. This command has no effect when the router is operating in DOCSIS bridging mode. |
Examples
The following example shows the Ethernet interface being configured with the IP address of 192.168.100.94, and that H.323 traffic will be transmitted using that IP address:
ubr924(config)# interface ethernet0 ubr924(config-if)# ip address 192.168.100.94 255.255.255.0 ubr924(config-if)# h323-gateway voip bind srcaddr 192.168.100.94 ubr924(config-if)#
The following example disables the H.323 binding, so that H.323 voice traffic is transmitted using the cable interface's IP address:
ubr924(config-if)# no h323-gateway voip bind srcaddr ubr924(config-if)#
Related Commands
h323-gateway voip h323-id Defines the H.323 name that identifies this Cisco uBR924 router gateway to its associated gatekeeper. h323-gateway voip id Defines the name and IP address of the gatekeeper for this gateway. h323-gateway voip interface Configures the interface as an H.323 interface. h323-gateway voip tech-prefix Defines the technology prefix that the gateway uses to register with the gatekeeper.
Command
Description
To configure the Cisco uBR924 cable access router's cable interface so that it obtains its IP address from a DHCP server at power-on provisioning, use the ip address dhcp command in interface configuration mode.
ip address dhcpSyntax Description
This command has no arguments or keywords.
Defaults
The Cisco uBR924 cable access router defaults to obtaining the cable interface's IP address from a DHCP server. This behavior is required by the DOCSIS specification and cannot be overridden.
Command Modes
Interface configuration
Command History
12.1(3)T This command was introduced for the Cisco uBR924 router and Cisco uBR910 series DSU.
Release
Modification
Usage Guidelines
This command is the default configuration for the router's cable interface. Because DOCSIS specifies that the cable interface obtain its IP address from a DHCP server available through the cable interface, this command cannot be turned off or overridden.
Examples
The following example configures the cable interface so that it obtains its IP address from a DHCP server during power-on provisioning:
uBR924(config)# interface cable0 uBR924(config-if)# ip address dhcp uBR924(config-if)# exit uBR924(config)#
Related Commands
ip address negotiated Configures the serial interface to obtain its IP address through the PPP/IPCP address negotiation.
Command
Description
Syntax Description
basic Displays only the basic status and performance pages. advance Displays all status and diagnostic pages. URL-IP-address Specifies the IP address for the Cable Monitor. This parameter, along with the URL-mask parameter, also defines the network that provides the IP address pool used by the temporary DHCP server when the cable interface goes down. URL-mask Specifies the subnet mask for the Cable Monitor. This parameter, along with the URL-IP-address parameter, also defines the network that provides the IP address pool used by the temporary DHCP server when the cable interface goes down.
Note The Cable Monitor should not be used in advanced mode without first implementing a secure password strategy on the Cisco uBR924 cable access router. Enabling the Cable Monitor in advanced mode without setting an encrypted enabled password could provide information that would allow remote users to change the router's configuration.
Defaults
For URL-IP-address, 192.168.100.1
For URL-mask, 255.255.255.0
Command Modes
Global configuration
Command History
12.1(1)T This command is introduced for the Cisco uBR924 router.
Release
Modification
Usage Guidelines
This command enables the Cable Monitor, an onboard web server that displays current status, troubleshooting, and performance information. The Cable Monitor can be accessed in two ways:
Enabling the Cable Monitor also enables the Cisco web server that is onboard the Cisco uBR924 cable access router (which is the equivalent to giving the ip http server command). However, when the Cable Monitor is enabled, all other access, including CLI access, to the onboard web server is automatically disabled.
Disabling the Cable Monitor using the no ip http cable-monitor command also automatically disables the Cisco web server (which is the equivalent of giving the no ip http server command).
The URL-IP-address and URL-mask parameters also specify that the class C private network 192.168.100.0 is the default address pool for the temporary DHCP server that activates when the cable interface goes down.
For more detailed information on using the Cable Monitor, see "Using the Cable Monitor Tool" in the Cisco uBR924 Software Configuration Guide, available on CCO and the Documentation CD-ROM.
Examples
The following example enables the Cable Monitor for advanced mode, in which all status and diagnostic pages are displayed:
ubr924(config)# ip http cable-monitor advance ubr924(config)#
The following example disables both the Cable Monitor and the Cisco web server, preventing all web server access to the Cisco uBR924 cable access router:
ubr924(config)# no ip http cable-monitor ubr924(config)#
Related Commands
ip http port Configures the TCP port number for the router's HTTP web server (the default is the well-known web server port of 80). ip http server Enables and disables the router's HTTP web server.
Command
Description
|
Note The ip http command also supports two options, access-class and authentication, that should not be used when the Cable Monitor is enabled. |
Syntax Description
number Cable interface number inside the Cisco uBR924 router (should always be 0 to indicate the first and only cable interface).
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(7)XR and 12.1(1)T This command was introduced for the Cisco uBR924 router.
Release
Modification
Usage Guidelines
This command displays the four possible stream queues, the SID associated with each queue (if the queue is currently in use), and whether the SID is the primary SID, a secondary (static) SID, or a dynamic (on demand) SID. The display also shows the packets and bytes that have been transmitted and received on each stream.
Examples
The following example displays the current QoS statistics for each of the router's four queues:
uBR924# show controllers cable-modem 0 qos
Queue SID SID SFID TX TX RX RX
Type Pkts Bytes Pkts Bytes
0 2 Primary 0 11377 2721985 12320 983969
1 52 Dynamic 52 116 13608 105 14300
2 0 NA 0 0 0 0 0
3 0 NA 0 0 0 0 0
ubr924#
Table 1 describes significant fields shown in this display.
| Field | Description |
|---|---|
Queue | One of the four possible service flow queues that exist in the Cisco uBR924 router. |
SID | Service Identifier, a 14-bit integer assigned by the CMTS to each active upstream service flow. |
SID Type | The type of SID:
|
SFID | Service Flow Identifier, a 32-bit integer assigned by the CMTS to each service flow on the Cisco uBR924 router. |
TX Pkts | The number of packets the Cisco uBR924 router has transmitted on this service flow. |
TX Bytes | The number of bytes the Cisco uBR924 router has transmitted on this service flow. |
RX Pkts | The number of packets the Cisco uBR924 router has received on this service flow. |
RX Bytes | The number of bytes the Cisco uBR924 router has received on this service flow. |
Related Commands
show controllers cable-modem number mac Displays MAC-layer statistics showing the MAC error log, the other MAC log data, the number of MAC-layer resets, and the current MAC state.
Command
Description
In Cisco IOS Release 12.1(2)T, the following commands have been removed from the CLI:
In Cisco IOS Release 12.1(2)T and greater, these commands are now reserved exclusively for DOCSIS use.
Posted: Thu Jul 20 18:38:45 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.