View Single Post
Old 02-06-2008, 19:59   #317
CrowmanUK
Inactive
 
Join Date: Apr 2008
Posts: 165
CrowmanUK has a spectacular aura about themCrowmanUK has a spectacular aura about themCrowmanUK has a spectacular aura about themCrowmanUK has a spectacular aura about them
Re: New STM/Virgin traffic managent confirmed - so that's why it's slow!

Spot on Trax, quick visit to Cisco brings this up

Quote:
Feature List

The Subscriber Traffic Management feature has the following operational features:

•Subscriber Traffic Management 1.1 (STM1.1) supports cable modems that have registered for DOCSIS 1.1 operations (using the service class/service flow ID (SFID) model).

•Up to 20 enforce-rules can be created on each CMTS.

•Separate enforce-rules can be used for downstream traffic and for upstream traffic.

•Each enforce-rule uses a subscriber's registered QoS profile to identify which users should be monitored for excessive traffic. The registered QoS profile must exist on the Cisco CMTS. If you want to manage cable modems that are using QoS profiles that were created by the cable modem, you must first manually create a QoS profile with the exact same QoS parameters on the Cisco CMTS, and then allow the cable modem to come online using the manually created profile.

•Each rule specifies the maximum number of bytes a user can transmit during a specified window.

•Subscribers who exceed the maximum bandwidth that is specified by their enforce-rule can be automatically switched to a separate enforced QoS profile that limits their network use for a customizable penalty period. The enforced QoS profile can change the guaranteed bandwidth, priority, or any other aspect of the traffic that the service provider considers an acceptable response to subscribers who violate their service agreements.

•Subscribers are automatically switched back to their registered QoS profile at the end of their penalty period. A technician at the service provider's network operations center (NOC) can also can switch them back before the penalty period expires.

•This feature also supports a no-persistence option, so that the enforced QoS profile does not remain in effect when a cable modem reboots. This option is particularly useful when the feature is initially implemented, so that the service providers can identify problem subscribers and applications, without creating a major impact on the entire user base. When repeat offenders are found, they can then be switched to an enforce-rule that does keep the enforced QoS profile in effect even when the cable modem reboots.

•Service providers can display a list of all subscribers' current usage statistics. Service providers can also display a list of just those subscribers who are overconsuming bandwidth.

•The penalty period persists across reboots of the cable modem, so subscribers cannot avoid the enforced QoS profile by resetting their modems and reregistering on the cable network. This allows service providers to set an appropriate penalty for those users that consistently exceed the maximum bandwidth they have been allocated.

•If a user that is using excessive bandwidth then decides to upgrade to a higher level of service, the service provider can reconfigure the provisioning system to assign a new QoS profile to the cable modem. The user can then reboot the cable modem and come online using the new level of service.
http://www.cisco.com/en/US/docs/cabl.../ubsubmon.html
CrowmanUK is offline   Reply With Quote