Table Of Contents
PacketCable and PacketCable Multimedia on the Cisco CMTS Routers
Prerequisites for PacketCable Operations
Restrictions for PacketCable Operations
Information About PacketCable Operations
New Emergency 911 Features in Cisco IOS Release 12.3(13a)BC
PacketCable Emergency 911 Cable Interface Line Card Prioritization
PacketCable Emergency 911 Services Listing and History
PacketCable Network Components
Two-Stage Resource Reservation Process
Dynamic Service Transaction ID Support
PacketCable Subscriber ID Support
How to Configure PacketCable Operations
Enabling PacketCable Operation
Disabling PacketCable Operation
Configuring PacketCable Operation
Enabling Both PacketCable and Non-PacketCable UGS Service Flows
Enabling PacketCable Subscriber ID Support
Verifying PacketCable Configuration
Configuring RADIUS Accounting for RKS Servers
High Availability Stateful Switchover (SSO) for PacketCable and PacketCable MultiMedia
Debugging High Availability Stateful Switchover for PacketCable and PCMM
PacketCable Client Accept Timeout
Monitoring and Maintaining PacketCable Operations
Configuration Examples for PacketCable
Typical PacketCable Configuration
Prerequisites for PacketCable Multimedia Operations
Restrictions for PacketCable Multimedia Operations
Information About PacketCable Multimedia Operations
PCMM Enhancements over PacketCable 1.x
PCMM and Additional Software Features on the Cisco CMTS
PCMM Gate Overview and PCMM Dynamic Quality of Service
PCMM Interoperability with PacketCable 1.x Voice Services Module
PCMM and Distributed Cable Interface Line Cards
How to Configure PCMM Operations
Monitoring and Maintaining PCMM Operations
Using Debug Commands with PCMM
Configuration Examples for PacketCable Multimedia
Feature Information for PacketCable and PacketCable Multimedia on the Cisco CMTS Routers
PacketCable and PacketCable Multimedia on the Cisco CMTS Routers
Revised: December 17, 2008, Cisco IOS Release 12.2(33)SCBFirst Published: Cisco IOS Release 12.2(8)BC2
Note
Cisco IOS Release 12.2(33)SCA integrates support for this feature on the Cisco CMTS routers. This feature is also supported in Cisco IOS Release 12.3BC, and this document contains information that references many legacy documents related to Cisco IOS 12.3BC. In general, any references to Cisco IOS Release 12.3BC also apply to Cisco IOS Release 12.2SC. For the latest information on Cisco CMTS router support in Cisco IOS Release 12.2SC, refer to the Cross-Platform Release Notes for Cisco Universal Broadband Routers in Cisco IOS Release 12.2SC.
This document describes how to configure the Cisco CMTS for PacketCable and PacketCable Multimedia operations over an existing Data-over-Cable Service Interface Specifications (DOCSIS) 1.1 cable network.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for PacketCable and PacketCable Multimedia on the Cisco CMTS Routers" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
PacketCable Contents
•
•
•
•
•
•
PacketCable Multimedia Contents
•
•
•
•
•
•
Additional Information
•
Prerequisites for PacketCable Operations
This section provides information about requirements for the PacketCable feature on the Cisco CMTS routers. For information about requirements for PacketCable Multimedia on the Cisco CMTS routers, see the "Prerequisites for PacketCable Multimedia Operations" section.
PacketCable Prerequisites
Cisco uBR7225VXR Router
Support for the Cisco uBR7225VXR router was introduced in Cisco IOS Release 12.2(33)SCA and later 12.2SC releases.
Cisco uBR7246VXR Router
•
•
Cisco uBR10012 Router
•
•
Table 1 shows the hardware compatibility prerequisites for this feature.
Restrictions for PacketCable Operations
PacketCable Restrictions
•
•
•
•
•
Information About PacketCable Operations
This section provides an overview and other information about PacketCable operations, the components of a PacketCable network, and how they interact with the other components of a DOCSIS cable networks.
•
•
•
•
Feature Overview
PacketCable is a program initiative from Cablelabs and its associated vendors to establish a standard way of providing packet-based, real-time video and other multimedia traffic over hybrid fiber-coaxial (HFC) cable networks. The PacketCable specification is built upon the Data-over-Cable System Interface Specifications (DOCSIS) 1.1, but it extends the DOCSIS protocol with several other protocols for use over noncable networks, such as the Internet and the public switched telephone network (PSTN).
This allows PacketCable to be an end-to-end solution for traffic that originates or terminates on a cable network, simplifying the task of providing multimedia services over an infrastructure composed of disparate networks and media types. It also provides an integrated approach to end-to-end call signaling, provisioning, quality of service (QoS), security, billing, and network management.
Cisco IOS Release 12.2(11)BC1 supports the PacketCable 1.0 specifications and the Communications Assistance for Law Enforcement Act (CALEA) intercept capabilities of the PacketCable 1.1 specifications.
New Emergency 911 Features in Cisco IOS Release 12.3(13a)BC
Cisco IOS Release 12.3(13a)BC introduces two new Emergency 911 features, supported on PacketCable 1.x and PacketCable Multimedia networks:
•
•
PacketCable Emergency 911 Cable Interface Line Card Prioritization
Cisco IOS Release 12.3(13a)BC introduces PacketCable Emergency 911 cable interface line cad prioritization on the Cisco CMTS. This feature enables cable interface line cards that are supporting an Emergency 911 call to be given automatic priority over cable interface line cards supporting non-emergency voice calls, even in the case of HCCP switchover events. In such cases, Protect HCCP line card interfaces automatically prioritize service to Emergency 911 voice calls, should Working HCCP cable interface line cards be disrupted. This feature is enabled by default in Cisco IOS release 12.3(13a)BC, and may not be disabled with manual configuration.
Note
During HCCP switchover events, cable modems recover in the following sequence in Cisco IOS release 12.3(13a)BC:
1.
2.
3.
4.
To view information about Emergency 911 voice events and cable interface line card prioritization on the Cisco CMTS, use the show hccp <int x> <int y> modem, show cable calls <bundle x> and show hccp event-history commands in privileged EXEC mode.
PacketCable Emergency 911 Services Listing and History
Cisco IOS release 12.3(1a3)BC introduces enhanced informational support for PacketCable Emergency 911 calls on the Cisco CMTS, to include the following information and related history:
•
•
•
•
This feature is enabled and supported with the following new Cisco IOS command-line interface (CLI) configuration and show commands:
•
•
•
•
•
To set the call window (in minutes) during which the Cisco CMTS maintains records of Emergency 911 calls, use the cable high-priority-call-window command in global configuration mode. To remove the call window configuration from the Cisco CMTS, use the no form of this command:
cable high-priority-call-window minutes
no cable high-priority-call-window
For additional information about these and additional commands, refer to the Cisco IOS CMTS Cable Command Reference on Cisco.com:
The following command example configures the call window on the Cisco uBR10012 router to be 1 minute in length:
Router(config)# cable high-priority-call-window 1To observe Emergency 911 calls made within the configured window, use the show cable calls command in privileged EXEC mode:
show cable calls
The following command example illustrates that one Emergency 911 call was made on the Cable8/1/1 interface on the Cisco uBR10012 router during the window set for high priority calls:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 1 1 0 0Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 1 1 0 0The following command example illustrates the change on the Cisco uBR10012 router when this Emergency 911 calls ends:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 0 0 0 1Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 0 0 0 1The following command example illustrates available information when making a voice call from the same MTA to another MTA on the same interface:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 0 2 1 1Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 0 2 1 1The following command example illustrates available information when a voice call from the same MTA to another MTA on the same interface ends:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 0 0 0 1Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 0 0 0 1The following example illustrates the show cable modem calls command on the Cisco uBR10012 router over a period of time, with changing call status information:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 R 0:39Router# scm callCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)The above example illustrates that call information disappears when a call ends. The following example illustrates a new Emergency 911 call on the Cisco CMTS:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 HV 1:30The following example illustrates a the end of the Emergency 911 call on the Cisco CMTS:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 R 0:3The following example illustrates a non-emergency voice call on the Cisco CMTS from the same MTA:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.ca36.f97d 10.10.155.25 C8/1/1/U0 5 V -0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 RV 0:30The following example illustrates a the end of the non-emergency voice call on the Cisco CMTS:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 R 0:36PacketCable Network Components
A PacketCable network contains a number of components. Some components are the same as those that exist in a DOCSIS 1.1 network, while other components are new entities that create the end-to-end infrastructure that the PacketCable network needs to establish calls. Wherever possible, the PacketCable components and protocols build on existing protocols and infrastructures to simplify implementation and interoperability.
•
•
Note
•
Note
•
Note
•
Note
•
Dynamic Quality of Service
A key feature of a PacketCable network is a dynamic quality of service (DQoS) capability that is similar to the dynamic services provided by DOCSIS 1.1. However, DOCSIS 1.1 DQoS authorizes and provisions services only in the cable network and does not reserve the resources needed to propagate a call from one endpoint to another across the network.
The PacketCable DQoS extends the DOCSIS 1.1 services across the entire network, so that resources can be dynamically authorized and provisioned from one endpoint to another. This prevents possible theft-of-service attacks and guarantees customers the services they are authorized to use.
Note
Two-Stage Resource Reservation Process
The PacketCable DQoS model uses a two-stage resource reservation process, in which resources are first reserved and then committed. This allows a bidirectional reservation process that ensures that resources are available at both endpoints of the connection before actually placing the call.
When an MTA makes a call request, the local CMTS communicates with the gate controller to authorize the call's resources. After the resources are authorized, the CMTS reserves the local resources while it negotiates with the remote end for the resources that are required at that end.
Note
When all required resources are available, the local CMTS and remote CMTS both commit the resources, allowing traffic to flow. Usage accounting and billing do not begin until the remote MTA picks up and the call is actually in progress.
The DQoS model ensures that both endpoints of a call, as well as the backbone network, have reserved the same bandwidth, and that the bandwidth is reserved only while the call is in progress. When a call terminates, all portions of the network can release the call's resources and make them available for other users.
Making a Call Using DQoS
DOCSIS 1.1 networks use service flows to implement different QoS policies, but service flows exist only within the cable network. To control the service flows and to extend them across the entire network, a PacketCable network creates and maintains "gates."
A gate is a logical entity created on the CMTS at each side of a connection that authorizes and establishes a particular DQoS traffic flow. The CMTS communicates with the gate controller to coordinate the creation of matching gates at each side of the connection.
Gates are unidirectional, so separate gates are required for the downstream and upstream traffic flows. The same gate ID, however, is usually used for the downstream and upstream gates for a call. Each CMTS maintains its own set of gates, so a bidirectional traffic flow requires four gates to be created, two gates on the local CMTS and two gates on the remote CMTS.
For a typical call, gates progress through the following stages to create a DQoS traffic flow:
1.
2.
3.
4.
5.
6.
Dynamic Service Transaction ID Support
DOCSIS 2.0 mandates unique Transaction IDs (TAIDs) across transactions. The TAIDs must be unique and not incremented. The TAIDs are assigned by the senders and sometimes the TAID timeout is mismatched between senders and receivers. This affects the uniqueness of the TAID.
A TAID can be reused when the sender finishes a transaction. Similarly, DOCSIS allows the receiver to identify a transaction by TAID without the SFID. Problems arise in DSD transaction and DSA/DSC interrupted transactions, when these two requirements are combined.
The uniqueness of TAID must be ensured to resolve the interoperability issue. This is done by making the CMTS wait until T10 to reuse the same TAID. A new TAID allocation algorithm is used to fulfill this requirement.
It creates a TAID pool to replace the existing 16-bit counter. This TAID pool is monitored by timers to track the TAID expiration. A flag is assigned to each TAID in the pool to indicate its availability. When new TAID is requested, the dynamic service process checks the availability of the TAID. If the TAID is available, it is allocated to the new service flow, else the request is rejected.
Once the TAID is allocated, the timer starts with T10 expiration time and the TAID flag is set to FALSE to indicate the unavailability of TAID. The dynamic service process keeps track of the timer. When the time expires, the timer stops and the flag is set to TRUE to indicate the availability of TAID.
The TAID pool is allocated and initialized at the process initialization. All timers associated with the TAIDs are added as leaf timers to the process' parent timer.
PacketCable Subscriber ID Support
The PacketCable Subscriber ID feature adds a Subscriber ID to all Gate Control messages and enhances error codes returned from the Cable Modem Termination System (CMTS).
Previously, the Gate ID was unique only to individual CMTS systems, with the CMTS proxying all CMS Gate control messaging through a central device which manages the CMTS connections on the behalf of the CMS. The CMS had a single Common Open Policy Service (COPS) association to the proxy device. Therefore, the Gate IDs could be duplicated when using multiple CMTS systems.
A Subscriber ID is added to each Gate Control message to disambiguate the Gate IDs between the CMS and proxy device. The Subscriber ID parameter is added to the following COPS messages:
•
•
•
•
The Subscriber ID is available at the CMS and is used in the Gate-Set messages. Additionally, the error codes returned from CMTS or its proxy are enhanced to include more specific information about gate operation failures.
To enable this feature, use the packetcable gate send-subscriberID command in global configuration mode. For more information, see the Cisco IOS CMTS Cable Command Reference Guide at the following location:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Note
Benefits
The PacketCable feature offers the following benefits to service providers and their customers:
Integrated Services on a Cable Network
PacketCable allows cable operators the ability to offer multimedia, real-time services, in addition to data connectivity, across their entire network. These services could include basic telephony with lifeline support, as well as telephony that offers competitive extended calling services. Operators can deploy new services while heavily leveraging their existing network infrastructures.
The widespread use of IP as the standard transport mechanism for data networks today is enabling many advanced Internet applications such as multimedia e-mail, real-time chat, streaming media (including music and video), and videoconferencing. The PacketCable initiative provides the network architecture for a cable operator to deliver these services quickly and economically.
Standardized Provisioning
PacketCable provides a standardized, efficient method to provision IP services for individual subscribers, because PacketCable specifications define a uniform, open, and interoperable network. Cable operators are assured of standardized provisioning and the associated lower costs of deployment.
Interoperability
Customer premises equipment (CPE) devices account for a major portion of the capital expense in deploying a VoIP solution at a cable plant. The PacketCable specifications ensure that vendors will build MTA clients that support the voice and other services that cable operators plan to deploy. Because these CPE devices are based on existing DOCSIS-compliant cable modems, time and cost of development is minimized.
Interoperability with the other components of the PacketCable network is also guaranteed because of the standards-based approach to the specifications. Any PacketCable-certified component will be able to interoperate within a network that conforms to the PacketCable standards.
Secure Architecture
Because PacketCable is built upon the security features available in DOCSIS 1.1, cable operators will be assured of networks that are secure from end to end, with a high standard of security that prevents the most common theft-of-service attacks. The comprehensive, standards-based PacketCable specifications are designed to create a network that is as secure as the public switched telephone network (PSTN).
CALEA Support
The PacketCable architecture was designed to accommodate the 1994 Communications Assistance for Law Enforcement Act (CALEA), which requires telecommunications carriers to assist law-enforcement agencies in conducting court-ordered electronic surveillance. PacketCable networks will be able to provide the two types of information that a carrier must provide, depending on the type of court order:
•
•
How to Configure PacketCable Operations
See the following sections for configuration t asks for the PacketCable feature. Each task is required unless otherwise identified as optional.
•
•
•
•
•
•
•
Enabling PacketCable Operation
To enable PacketCable operation, use the following commands beginning in user EXEC mode. This is a required procedure.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Disabling PacketCable Operation
To disable PacketCable operation, use the following commands beginning in user EXEC mode. This procedure is required only when you no longer want the Cisco CMTS to support PacketCable signaling.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring PacketCable Operation
To configure the different parameters that affect PacketCable operations, use the following commands beginning in user EXEC mode. All of these procedures are optional, because each parameter is set to a default that is appropriate for typical PacketCable operations.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Enabling Both PacketCable and Non-PacketCable UGS Service Flows
By default, when PacketCable operations are enabled using the packetcable command, cable modems must follow the PacketCable protocol when requesting Unsolicited Grant Service (UGS) service flows. This prevents DOCSIS cable modems that do not support PacketCable operations from using DOCSIS-style UGS service flows.
If you have a mixed network that contains both PacketCable and non-PacketCable DOCSIS CMs, you can use the packetcable authorize vanilla-docsis-mta command to enable both types of UGS service flows. This is an optional procedure.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Tip
Enabling PacketCable Subscriber ID Support
To include subscriber identification in GATE-OPEN and GATE-CLOSE gate control messages, use the packetcable gate send-subscriberID command in global configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Verifying PacketCable Configuration
To verify the PacketCable configuration, use the show packetcable global command in privileged EXEC mode, which displays whether PacketCable operations are enabled, as well as the values for the Element ID, the maximum number of gates, and the different CMTS-based DQoS timers.
Router# show packetcable globalPacket Cable Global configuration:Enabled : YesElement-ID: 12456Max Gates : 1048576Allow non-PacketCable UGSDefault Timer value -T0 : 30000 msecT1 : 300000 msecRouter#Configuring RADIUS Accounting for RKS Servers
To configure the Cisco CMTS so that it can communicate with the Record Keeping Servers (RKS servers) using the RADIUS protocol, use the following commands beginning in user EXEC mode. This is a required procedure.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
High Availability Stateful Switchover (SSO) for PacketCable and PacketCable MultiMedia
Cisco IOS Release 12.3(21)BC enhances high availability support that enables the synchronization of PacketCable and PacketCable MultiMedia (PCMM) gates during switchover events on the Cisco CMTS. This enhancement is enabled by default with Cisco IOS Release 12.3(21)BC and later supporting releases on the Cisco uBR10012 router and Cisco uBR7246VXR router.
This enhancement requires no additional configuration commands for line card redundancy in the Cisco N+1 Redundancy feature, nor the RPR+ Redundancy feature on the Cisco uBR10012 router. However, this functionality uses the existing per-interface HCCP commands that are used to associate the Working and Protect interfaces in the case of N+1 Redundancy.
This feature introduces a new debug command, however, to troubleshoot HCCP information specific to PacketCable and PCMM gates. The new command is debug packetcable hccp.
Debugging High Availability Stateful Switchover for PacketCable and PCMM
The new debug packetcable hccp command and procedure, introduced in Cisco IOS Release 12.3(21)BC, enables debugging and troubleshooting functions in cases where PacketCable and PCMM are supported in either or both N+1 Redundancy or RPR+ Redundancy on the Cisco CMTS. This command supports additional information displayed in the enhanced show packetcable gate summary command.
Currently after switchover, if we do a "show packetcable gate summary" we see no Gates, however, after the implementation of this feature we will see that the Gates exists. Also, after the implementation of this feature we will be able to connect to the standby LC and check if the gate information has been synchronized using the existing "show packetcable gate summary" command.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Examples
The following abbreviated example illustrates PacketCable gate synchronization information when debugging is enabled with the debug packetcable hccp command:
GateID i/f SubscriberID GC-Addr State Type SFID(us) SFID(ds)Total number of gates = 0Total Gates committed(since bootup or clear counter) = 625The following example illustrates additional information that tracks the activity as a call is made:
10:58:09: PktCbl(hccp): Grp 1 sync type=add from Cable5/0/010:58:09: PktCbl(hccp): Sync gate-add 38010 len=30810:58:10: PktCbl(hccp): Grp 1 sync type=add from Cable5/0/010:58:10: PktCbl(hccp): Sync gate-add 5242 len=30810:58:10: Pktcbl(hccp): Gate=5242 written to service flow dir US SFID=123310:58:10: Pktcbl(hccp): Gate=5242 written to service flow dir DS SFID=123410:58:10: PktCbl(hccp): Grp 1 sync type=update from Cable5/0/010:58:10: PktCbl(hccp): Sync gate-update 5242 len=2410:58:10: PktCbl(hccp): Grp 1 sync type=update from Cable5/0/010:58:10: PktCbl(hccp): Sync gate-update 5242 len=2410:58:10: Pktcbl(hccp): Gate=38010 written to service flow dir US SFID=123510:58:32: PktCbl(hccp): Parse add gate 38010 sync_len=300 from 5/0 status 210:58:32: PktCbl(hccp): Parse add gate 5242 sync_len=300 from 5/0 status 210:58:32: PktCbl(hccp): Parse update gate 5242 sync_len=1610:58:32: PktCbl(hccp): Parse update gate 5242 sync_len=1610:58:32: PktCbl(hccp): Parse update gate 38010 sync_len=1610:58:32: PktCbl(hccp): Parse update gate 38010 sync_len=1610:58:10: Pktcbl(hccp): Gate=38010 written to service flow dir DS SFID=123610:58:10: PktCbl(hccp): Grp 1 sync type=update from Cable5/0/010:58:10: PktCbl(hccp): Sync gate-update 38010 len=2410:58:10: PktCbl(hccp): Grp 1 sync type=update from Cable5/0/010:58:10: PktCbl(hccp): Sync gate-update 38010 len=2410:58:11: Pktcbl(hccp): Gate=38010 written to service flow dir US SFID=123510:58:11: Pktcbl(hccp): Gate=38010 written to service flow dir DS SFID=123610:58:11: PktCbl(hccp): Grp 1 sync type=update from Cable5/0/010:58:11: PktCbl(hccp): Sync gate-update 38010 len=2410:58:11: Pktcbl(hccp): Gate=5242 written to service flow dir US SFID=123310:58:11: Pktcbl(hccp): Gate=5242 written to service flow dir DS SFID=123410:58:11: PktCbl(hccp): Grp 1 sync type=update from Cable5/0/010:58:11: PktCbl(hccp): Sync gate-update 5242 len=2410:58:34: PktCbl(hccp): Parse update gate 38010 sync_len=1610:58:34: PktCbl(hccp): Parse update gate 5242 sync_len=16****** CALL IS ACTIVE **** SHOW GATE ON PRE *************sch_3#gateGateID i/f SubscriberID GC-Addr State Type SFID(us) SFID(ds)5242 Ca5/0/0 7.7.1.254 1.10.90.1 COMMIT DQoS 1233 123438010 Ca5/0/0 7.7.1.252 1.10.90.1 COMMIT DQoS 1235 1236Total number of gates = 2Total Gates committed(since bootup or clear counter) = 627The following example illustrates output of the show hccp command:
Router# show hccp brief
Interface Config Grp Mbr Status WaitToResync WaitToRestore
Ca5/0/0 Working 1 1 active never
Ca8/0/0 Protect 1 1 standby
Ca8/0/0 Protect 1 2 non-functional
Ca8/1/0 Protect 3 1 non-functional
Ca8/1/1 Protect 4 1 non-functional
sch_3#
Troubleshooting Tips
If the Connection between a PacketCable CMS and theCisco CMTS is not completely established, and the PacketCable CMS does not correctly terminate the session by sending a TCP FIN message, the connection otherwise shows a COPS server in the output of the show cops server command.
What to Do Next
For additional information, refer to the following documents on Cisco.com:
•
•
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
PacketCable Client Accept Timeout
Cisco IOS Release 12.3(17a)BC introduces support for setting timeout values for COPS Telnet connections on the Cisco CMTS, and for clearing COPS telnet sessions.
Network or Cisco CMTS telnet errors can cause incomplete COPS sessions to be created. This new timout timer enables the clearing and cleaning of allocated resources for the stale COPS Telnet sessions on the Cisco CMTS. This feature supports COPS for PacketCable on the Cisco CMTS.
The timeout timer applies to each COPS Telnet connection on the Cisco CMTS, and expiration of this timeout setting triggers the termination of the Telnet session and clears supporting resources on the Cisco CMTS.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Examples
The following example sets the client accept timer to 30 minutes:
Router(config)# packetcable timer client-accept 1800
Troubleshooting Tips
If the Connection between a PacketCable CMS and theCisco CMTS is not completely established, and the PacketCable CMS does not correctly terminate the session by sending a TCP FIN message, the connection otherwise shows a COPS server in the output of the show cops server command.
What to Do Next
For additional information, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Monitoring and Maintaining PacketCable Operations
To display and maintain information about current PacketCable operations, use one or more of the following commands:
Configuration Examples for PacketCable
This section provides the following configuration examples:
•
Typical PacketCable Configuration
This section provides a typical configuration for a Cisco uBR7246VXR universal broadband router that has been configured for PacketCable operations, using default parameters. To use this configuration, you must change the IP addresses for the RADIUS and RKS servers to match the addresses for the servers in your network.
!version 12.2no parser cacheno service padservice timestamps debug datetime msec localtime show-timezoneservice timestamps log datetime msec localtime show-timezoneno service password-encryptionservice internalservice udp-small-servers max-servers no-limitservice tcp-small-servers max-servers no-limit!hostname Router!no logging rate-limitaaa new-model!!aaa group server radius aserver 10.9.62.12 auth-port 1813 acct-port 1812server 10.9.62.13 auth-port 1813 acct-port 1812!aaa accounting network default start-stop group radius group aaaa session-id commonenable password <delete>!cable modulation-profile 2 request 0 16 0 8 qpsk scrambler 152 no-diff 64 fixed uw16cable modulation-profile 2 initial 5 34 0 48 qpsk scrambler 152 no-diff 128 fixed uw16cable modulation-profile 2 station 5 34 0 48 qpsk scrambler 152 no-diff 128 fixed uw16cable modulation-profile 2 short 6 75 6 8 16qam scrambler 152 no-diff 144 shortened uw8cable modulation-profile 2 long 8 220 0 8 16qam scrambler 152 no-diff 160 shortened uw8cable modulation-profile 5 request 0 16 2 8 qpsk scrambler 152 no-diff 64 fixed uw16cable modulation-profile 5 initial 5 34 0 48 qpsk scrambler 152 no-diff 128 fixed uw16cable modulation-profile 5 station 5 34 0 48 qpsk scrambler 152 no-diff 128 fixed uw16cable modulation-profile 5 short 6 78 7 8 16qam scrambler 152 no-diff 144 shortened uw16cable modulation-profile 5 long 8 220 0 8 16qam scrambler 152 no-diff 160 shortened uw16cable qos profile 5 max-burst 1200cable qos profile 5 max-downstream 2000cable qos profile 5 max-upstream 128cable qos profile 5 priority 5cable qos profile 5 privacycable qos profile 7 guaranteed-upstream 87cable qos profile 7 max-upstream 87cable qos profile 7 privacyno cable qos permission createno cable qos permission updatecable qos permission modemscable qos permission enforce 5cable time-serverno cable privacy accept-self-signed-certificateip subnet-zero!!no ip domain-lookupip domain-name cisco.comip host tftp 10.8.8.8ip host cnr 10.9.62.17!packetcablepacketcable element-id 12456!!!interface Tunnel0ip address 10.55.66.3 255.255.255.0load-interval 30tunnel source FastEthernet1/0tunnel destination 172.27.184.69!interface Tunnel10ip address 10.0.1.1 255.255.0.0!interface FastEthernet0/0ip address 10.9.60.10 255.255.0.0no ip redirectsno ip mroute-cachefull-duplex!interface FastEthernet1/0ip address 172.22.79.44 255.255.254.0no ip redirectsno ip mroute-cachefull-duplex!interface Cable3/0ip address 10.3.1.33 255.255.255.0 secondaryip address 10.4.1.1 255.255.255.0 secondaryip address 10.4.1.33 255.255.255.0 secondaryip address 10.3.1.1 255.255.255.0ip helper-address 10.9.62.17load-interval 30no keepalivecable downstream annex Bcable downstream modulation 64qamcable downstream interleave-depth 32cable downstream frequency 55500000cable upstream 0 modulation-profile 2no cable upstream 0 shutdowncable upstream 1 frequency 12000000cable upstream 1 power-level 0cable upstream 1 channel-width 3200000cable upstream 1 data-backoff automaticcable upstream 1 modulation-profile 2cable upstream 1 shutdowncable upstream 2 frequency 16000000cable upstream 2 power-level 0cable upstream 2 channel-width 3200000cable upstream 2 data-backoff automaticcable upstream 2 modulation-profile 2no cable upstream 2 shutdowncable upstream 3 frequency 20000000cable upstream 3 power-level 0cable upstream 3 channel-width 3200000cable upstream 3 data-backoff automaticcable upstream 3 modulation-profile 2no cable upstream 3 shutdowncable upstream 4 frequency 24000000cable upstream 4 power-level 0cable upstream 4 channel-width 3200000cable upstream 4 data-backoff automaticno cable upstream 4 shutdowncable upstream 5 frequency 28000000cable upstream 5 power-level 0cable upstream 5 channel-width 3200000cable upstream 5 data-backoff automaticcable upstream 5 modulation-profile 2no cable upstream 5 shutdowncable dhcp-giaddr policy!router eigrp 48849network 1.0.0.0network 10.0.0.0auto-summaryno eigrp log-neighbor-changes!ip default-gateway 10.9.0.1ip classlessip route 0.0.0.0 0.0.0.0 172.22.78.1ip route 10.8.0.0 255.255.0.0 10.9.0.1ip route 192.168.80.0 255.255.255.0 Tunnel0ip route 192.168.80.0 255.255.255.0 172.27.184.69ip route 10.255.254.254 255.255.255.255 10.9.0.1no ip http serverip pim bidir-enable!!cdp run!!radius-server host 10.9.62.12 auth-port 1813 acct-port 1812 key 0000000000000000radius-server retransmit 3radius-server vsa send accounting!line con 0exec-timeout 0 0privilege level 15line aux 0line vty 0 4session-timeout 33exec-timeout 0 0password <deleted>!ntp clock-period 17179976ntp server 1.9.35.8endPrerequisites for PacketCable Multimedia Operations
This section provides information about requirements for the PacketCable Multmedia feature on the Cisco CMTS routers. For information about requirements for the PacketCable feature on the Cisco CMTS routers, see the "Prerequisites for PacketCable Operations" section.
Cisco uBR7225VXR Router
Support for the Cisco uBR7225VXR router was introduced in Cisco IOS Release 12.2(33)SCA and later 12.2SC releases.
Cisco uBR7246VXR Router
•
Cisco uBR10012 Router
•
•
Table 2 shows the hardware compatibility prerequisites for this feature.
Restrictions for PacketCable Multimedia Operations
Beta and FCS restrictions pending confirmation and description, and the lack of Caveats cited here does not imply that such restrictions do not exist.
Information About PacketCable Multimedia Operations
PacketCable Multimedia for the Cisco CMTS is a powerful implementation of CableLabs® standards for PacketCable Multimedia and DOCSIS 1.1. PacketCable Multimedia provides enhanced Quality of Service (QoS) for multimedia applications, voice, and bandwidth-intensive services over a DOCSIS 1.1 network.
The Cisco CMTS supports DOCSIS QoS for SIP-based telephones and SIP Video Phones, Bandwidth-on-Demand applications, and network-based gaming applications, all of which place extensive bandwidth demands on the network.
At the time of publication, Cisco IOS Release 12.3(13a)BC supports the following CableLabs standards for PacketCable Multimedia:
•
•
Both of these industry standard publications are available at the following CableLabs website, with much additional information about PacketCable Multimedia:
http://www.packetcable.com/specifications/multimedia.html
This section provides information about the following aspects of PacketCable Multimedia for the Cisco CMTS and Cisco IOS Release 12.3(13a)BC, emphasizing PCMM components that are configured with the Cisco IOS command-line interface later in this document:
•
PCMM Overview
PCMM Enhancements over PacketCable 1.x
PacketCable Multimedia (PCMM) is a service delivery framework that leverages and uses as much of existing PacketCable 1.x deployments and functionality as possible. Furthermore, PCMM offers powerful enhancements to the VoIP service delivery framework with straightforward CLI implementation. The key enhancements offered by PCMM include the following:
•
•
•
•
PCMM for the Cisco CMTS introduces new or enhanced commands for PCMM configuration, testing, and monitoring. For additional information about configuring or monitoring PCMM on the Cisco CMTS, refer to the following sections:
•
•
PCMM and Additional Software Features on the Cisco CMTS
PacketCable and PCMM with Admission Control
A PacketCable or PacketCable Multimedia (PCMM) network contains a number of components that benefit from Admission Control Quality of Service. Admission Control manages and optimizes QoS for PacketCable and PCMM in these ways:
•
•
•
•
•
•
When configuring Admission Control with either PacketCable or PCMM, PacketCable or PCMM must be fully operational on the Cisco CMTS headend prior to gaining the benefits from Admission Control.
For Admission Control configuration information, refer to the following documents on Cisco.com for your software release:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_adm.html
•
PCMM and High Availability Features on the Cisco CMTS
In Cisco IOS Release 12.3(13a)BC, High Availability on the Cisco CMTS only accommodates synchronization of service flows created for the PCMM applications. There is currently no PCMM Gate synchronization that fully supports PCMM High Availability features such as HCCP N+1 Redundancy and Route Processor Redundancy Plus (RPR+) on the Cisco CMTS. Such HA functionality will be enabled for PCMM in upcoming Cisco IOS releases.
PCMM Gates
PCMM Gate Overview and PCMM Dynamic Quality of Service
A PacketCable 1.x gate defines Quality of Service (QoS) parameters and policy-based authorization for subscribers, and a specific envelope of network resources. A PacketCable 1.x gate also maintains classifiers for originating and terminating IP addresses and ports. Combined, these define and limit the associated QoS-enhanced flow.
PacketCable 1.x defines a pre-authorization model. PC gates are created and installed at the Cisco CMTS prior to network resource reservation or activation requests. This process, termed Gate Control, is managed through a COPS-based policy interface on the Cisco CMTS.
In PCMM, this COPS-based interface is enhanced for QoS life-cycle management. PCMM gates maintain service flow creation, modification and deletion functions to provide for network-based QoS. Multiple PCMM gates and service flow policies can be maintained on the Cisco CMTS at a given time, and these PCMM gates are fully interoperable with PacketCable 1.x gates.
When a cable modem subscriber requests bandwidth for a network-intensive application, the network Policy Server sends a gate-set message to the Cisco CMTS. This message contains QoS, service flow, and billing information for this subscriber. This gate profile information is maintained on the Cisco CMTS, to include PCMM gate states and PCMM state transitions.
The Cisco CMTS initiates service flows with cable modems, and optimizes DOCSIS resource availability on the Cisco CMTS for bandwidth-intensive service flows characteristic to PCMM.
PCMM Persistent Gate
Cisco IOS Release 12.3(13a)BC supports the Persistent Gate feature for PacketCable Multimedia. Persistent Gate is a feature by which PCMM gate information is maintained for cable modems that go offline. Gate information is quickly enabled once a cable modem returns online. When a cable modem returns online, the Cisco CMTS scans PCMM gates previously stored, and initiates service to the cable modem according to the respective PCMM gate. The newly re-enabled service maintains traffic support profiles for that gate, and allocates DOCSIS resources according to the newly online subscriber.
PCMM Interoperability with PacketCable 1.x Voice Services Module
The Cisco CMTS maintains the PC and PCMM Gate databases separately and independently. Information for either is available with multiple show commands.
PCMM Interfaces
PCMM optimizes the IPC handshake between the cable interface line card and the Network Processing Engine (NPE) for the Cisco uBR7246VXR router, or the Route Processor (RP) for the Cisco uBR10012 router. Additional PCMM interface changes from PacketCable 1.x include the handling for COPS interface and distributed cable interface line cards.
PCMM to COPS Interface
PCMM differs from PacketCAble 1.x in that COPS sessions on PCMM use TCP port number 3918 by default. PC uses the DQoS specification for TCP port requirements and COPS sessions.
When the PCMM module initializes for the first time, a PCMM registry is added to the cable interface line card and the route processor. The PCMM module also registers the PCMM COPS client with the COPS layer on the Cisco CMTS.
PCMM and Distributed Cable Interface Line Cards
As with PacketCable 1.x, PCMM uses IPC messages for voice support. When PCMM gates are created on the Network Processing Engine (NPE) or Route Processor (RP), the PCMM gate parameters are sent to cable interface line cards. IPC maintains all communication between the NPE or RP, and the cable interface line cards.
Event messaging is used with PCMM to support billing information based on gate-set messages. Event messaging for distributed cable interface line cards originates from the line cards, based on the success of DSX operation.
The PCMM module also registers the PCMM COPS client with the COPS layer.
How to Configure PCMM Operations
This section describes the following configuration procedures for PCMM on the Cisco CMTS.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
What to Do Next
Once PCMM is enabled on the network, much additional information and status can be gained with monitoring, debugging, or testing commands and associated procedures. Refer to the following sections in this document for additional information:
•
•
Monitoring and Maintaining PCMM Operations
This section describes two flexible procedures for monitoring and testing PCMM operations on the network, once configured with the "How to Configure PCMM Operations" section. This section contains two procedures for monitoring and maintaining PCMM operations:
•
•
Until this section is populated, refer to debug, show and test commands available in the Cisco IOS CMTS Cable Command Reference.
Using Debug Commands with PCMM
This topic describes the use of debug commands for PCMM, as supported by Cisco IOS Release 12.3(13a)BC. This sequence of debugging steps is flexible, and can be adjusted according to the troubleshooting needs for PCMM network components.
Until this section is populated, refer to debug, show and test commands available in the Cisco IOS CMTS Cable Command Reference.
Using Test Commands with PCMM
This topic describes the use of debug commands for PCMM, as supported by Cisco IOS Release 12.3(13a)BC. This sequence of testing steps is flexible, and can be adjusted according to the PCMM or network components to be tested.
Until this section is populated, refer to debug, show and test commands available in the Cisco IOS CMTS Cable Command Reference.
Configuration Examples for PacketCable Multimedia
Refer to examples available with the command documentation in the Cisco IOS CMTS Cable Command Reference.
Additional References
The following sections provide references related to the Cisco CMTS routers.
Related Documents
AAA and RADIUS Configuration
For complete information on configuring the AAA and RADIUS servers, which are required for communication with the RKS servers, refer to the Cisco IOS Security Configuration Guide, Release 12.2 at the following URL:
http://www.cisco.com/en/US/docs/ios/security/command/reference/sec_book.html
CMTS commands
Cisco IOS CMTS Cable Command Reference
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
DHCP Configuration
To configure the DHCP server onboard the Cisco CMTS, see the "Configuring DHCP" chapter in the IP Addressing Services section of the Cisco IOS IP and IP Routing Configuration Guide, Release 12.2 at the following URL:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/fipr_c.html
For information on all DHCP commands, see the "DHCP Commands" chapters in the Cisco IOS IP Addressing Services Command Reference, Release 12.2 at the following URL:
http://www.cisco.com/en/US/docs/ios/ipaddr/command/reference/iad_book.htmlDOCSIS 1.1
To configure the Cisco uBR7200 series router for DOCSIS 1.1 operations, see the the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/feature/DOCSIS11.html
NTP or SNTP Configuration
To configure the Cisco CMTS to use Network Time Protocol (NTP) or Simple Network Time Protocol (SNTP) to set its system clock, see the "Performing Basic System Management" chapter in the "System Management" section of the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2, at the following URL:
http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html
Standards
ITU X.509 V3
International Telecommunications Union (ITU) X.509 Version 3.0 standard
PKT-EM-I03-011221
PKT-SP-DQOS-I03-020116
PKT-SP-EC-MGCP-I04-011221
PacketCable™ Network-Based Call Signaling Protocol Specification
PKT-SP-ESP-I01-991229
PKT-SP-ISTP-I02-011221
PacketCable™ Internet Signaling Transport Protocol (ISTP) Specification
PKT-SP-PROV-I03-011221
PKT-SP-SEC-I05-020116
PKT-TR-ARCH-V01-991201
Note
SP-BPI+-I08-020301
Data-over-Cable Service Interface Specifications Radio Frequency Interface Specification, version 1.1
1 Not all supported standards are listed.
MIBs
No new or changed MIBs are supported by this feature.
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
1 Not all supported MIBs are listed.
RFCs
Technical Assistance
Feature Information for PacketCable and PacketCable Multimedia on the Cisco CMTS Routers
Table 3 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007-2008 Cisco Systems, Inc. All rights reserved.
Guest
