I was wondering what is the best way to avoid CM D3.0 capable from connecting in a wideband channel? I have read about TLV 43.15 in Cisco documentation, but I tried without success. I just want to have control of CMs connecting into wideband channels.
Thanks in advance.
Why are you wanting to do this? It seems a strange thing to do.
I had a look at the TLV 43.15 "Bonded channel enable". This looks like a vendor specific option which probably isnt widely supported.
Instead you could possibly use a vendor specific mib eg
Arris - arrisCmDoc30SetupDsBonding disable(0),
Cisco - saCmDsBonding disable(0),
Motorola - cmDsBondingCapable false(2)
Thanks for your reply!!!
I'm looking to do this because we sometimes accept our clients to use their own CM so I just want to ensure they aren't going to use wideband channels which are reserved for specific velocities. What do you thinK?
If you have further recommendations they're welcome!
In my opinion, the more wideband modems the better. Traffic is spread more evenly. Less chance of particular upstreams or downstreams getting maxed out.
I would just setup a config file for each tier, with the right up and down rate limit in the config file.
If the client can supply a wideband modem, that is good news not bad!
( Note : In my part of the world, all packages have a speed plus a monthly traffic quota. If a user exceeds the quota then their speed is restricted/shaped for the rest of the month. If you are selling "unlimited" packages which are defined by different speeds only (no quotas) then I can see how offering wideband might allow the customer to chew through more data in a given billing cycle (good for them but bad for you!). If I was running such a system I would consider using QoS priority levels to lower the priority on users who have used large amounts of traffic. Eg by default give all commercial customers prio 2, residential custs get prio 1. Any users who exceed some threshold of your choosing retain their same plan speed but get flicked over to a different config file which has prio 0. That way the high volume users still get network access, but they are not able to greatly impact the speeds of low volume customers ).
Hello Mbowe! In my part of the world most ISPs don't restrict the number of packages. I'm going to analyze what you were telling me about apply QoS taking into account how much BW our client has consumed.
Best regards and thanks for your response. I appreciate them.
Maybe you watch for the bonding-forbidden attribute mask for the primary service flows:
Main
{
NetworkAccess 1;
GlobalPrivacyEnable 0;
MaxCPE 2;
UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
TrafficPriority 0;
MaxRateSustained 20000000;
SchedulingType 2;
MaxTrafficBurst 24480;
MaxConcatenatedBurst 0;
IpTosOverwrite 0x0000;
GenericTLV TlvCode 32 TlvLength 4 TlvValue 0x80000000;
}
DsServiceFlow
{
DsServiceFlowRef 2;
QosParamSetType 7;
TrafficPriority 0;
MaxRateSustained 20000000;
MaxTrafficBurst 24480;
GenericTLV TlvCode 32 TlvLength 4 TlvValue 0x80000000;
}
}
The 0x80000000 is the default attribute mask for default bonding groups. TLV[24/25].32 C.2.2.5.7 Service Flow Forbidden Attribute Mask from the MULPI
The cable modem might shown as bonded online but the traffic is just go over the primary downstream/upstream so long you use the tlv in the primary service flows.
Thank you very much!!! I'm going to be trying this option and let you know the result! I also tested using the OIDs above and it resulted!
Attribute mask sounds a better solution than the vendor OIDs
Yes mbowe! I'm trying it! :) :) :) It works pretty well. Thanks for your help guys!
How can i use GenericTLV TlvCode 32 TlvLength 4 TlvValue 0x80000000; ? what is the OID for this?
sorry, I still learn about config file. I use Excentis config file editor here... it need OID.
thank you
You don't need a OID for this, because there is no OID for ServiceFlow Settings.
At the Excentis Config File Editor you can find the setting very easily:
Under the "(Euro)DOCSIS 1.1 Required Encodings" you can add the needed TLV under "Upstream|Downstream Service Flow Encodings" via select new TLV. Then you select the "Service Flow Forbidden Attribute Mask (32)" and use the value "80000000"
Thank you wittmann,
I found it. Service Flow Forbidden Attribute Mask:80000000.
Thank you... :)
Hi Mbowe,
I have already try to use Cisco - saCmDsBonding disable(0), but it doesn't work. do you have any clue? The cable modem state still w-online.
thank you