Hi there,
I was wondering if one needs to configure the "service class name" for the flows on a CMTS as well as in the config file in order to give a name to the flows (my lab has Cisco UBR). I would prefer only doing changes on my provisioning system without get concerned with my CMTSs.
I also need to know the advantages of use names in the flows, I'm implementing a solution with IPDR but I'm not sure if it would be better to use names such as: DS-DATA-2M (one for each speed offered) or a generic one such as DS-DATA (no matter the speed).
Thanks in advanced guys!
I am pretty confident that if you put service class names into config file, then these classes will need be exist on the CMTS. Otherwise the modem will go to into reject(c) or similar.
I prefer to use names over flows, as it simplifies the CM config files, and means they need to be touched less often.
Like you said, you can create classes for the various US and DS speeds that are the building blocks of the packages you sell.
You can also create some classes that are generic like PROVISIONING or SHAPED for other types of flows
Down the track if you want to alter any of the values of the class (eg speed, burst, priority etc), you can do so with a simple paste on the CMTS CLI. No need to edit/recompile every config file.
Hi Michael,
Thanks for your response. So basically your config files are as simple as they could be and the technical parameters are added based on the name of the flow?
I've got it. I just want to be sure that there is no other way than write the service class name on both the CMTS and the config file.
Well, with service class names, I know its possible to mix and match some settings in the config file vs CMTS
For example we might have a service classes like this
2M-US-BE-1
CMTS sets the speed to 2Mbps, direction upstream, scheduler type 4, prio to 1 (eg residential customers)
2M-US-BE-2
CMTS sets the speed to 2Mbps, direction upstream, scheduler type 4, prio to 2 (eg business customers)
2M-US-BE-CF
CMTS sets the speed to 2Mbps, direction upstream, scheduler type 4. Config file sets the prio. (eg special cases like business L2VPN customer)
In examples above, we are sometimes setting the priority value on the CMTS, other times not defining it in the CMTS and instead setting it in the config file
Cant say I have ever tried, but potentially this might mean you could make service classes on the CMTS and leave them empty. Put all the values in the config file?
Been a while since I tinkered with IPDR. Are you saying that IPDR is forcing you to use service-class names? Are you adding extra classes / flows so that IPDR can itemise different types of traffic ?
Is not that IPDR forces you to use Service Class Names, but if you want to use it "correctly" it would be better if you categorize your service flows, is the only way SAMIS information can be distinguished among services. I'm doing experiments to use IPDR as a Capacity Planning tool.