You are here

Problems with tftp config files

sorry for my English, I am of Argentinean and I have difficulties with the language.
I have a problem, the cable modems takes the configuration file they get up but when I prove the speed it doesn't correspond with the limitations of speed of the files in the tftp, example next

This file I add him the key and the cable modems they get up but the speed would have to be of downstream 1000 kbits/s, but it doesn't exist it limits in the down. I wait it has not been very extensive.
Thanks

Thank you for answer, a pleasure in knowing you.
I think that modifying this file the changes take effect, sorry for my ignorance.
The cmts is not very well-known, it is mark coaxial network this runs with an operating system qnx (real time) unix based.
As ckeck the QoS profiles in my CMTS.
Coaxial Networks Web Page www.coaxialnetworks.com
They (Coaxial Networks) say what limit the traffic from the firewall of the provisioning, but this makes me think that the resources in rf are not being limited by QOS RF.
if is necesari i send pdf characteristics

// rules:
// 1) "//" C++ style comment text is ignored by config file reader.
//
// 2) settings groups must be ordered as follows:
// HeadEndMgrSettings for the application (there is (1) and only (1)
// HeadEndMgr per application)
// CONFIG_UpstreamChan
//
// 3) context with respect to class-in-progress is indicated by strings
// w/format
// BEGIN_
// such as
// BEGIN_HeadEndMgrSettings - indicates begining of HeadEndMgrSettings
// END_HeadEndMgrSettings - indicates end of HeadEndMgrSettings
//
// 4) data member names and values are indicated by strings w/format
// =
//
// the spaces between "> = <" are important!
//
// example:
// us_chan_id = 1
//
// 5) integer 's may be in normal C/C++ decimal or hex format.
//
// 6) For lines with multiple input values
// (HeadEndMgrSettings::auth_str is an examples), enter (8)
// values separated by spaces on each line. For the last line, enter
// all the values that exist, up to 8.
//
// 7) HeadEndMgrSettings::auth_str is a special case hassle since each
// is an array of bytes which may include unprintable characters,
// i.e. it cannot be represented by a character string.
//
// 8) Maximum length of input line is 80 characters.
//

len_auth_str = 0
auth_str = 0
// This is for "DOCSIS", the string that will be used at the DOCSIS 1.1 interop testing.
// There is no '\0' at the end of the string.
//len_auth_str = 6
//auth_str = 0x44 0x4f 0x43 0x53 0x49 0x53