DOCSIS Config Writer
Located in /docsis_config/docsis_config.php (line 58)
docsis_encoder | --docsis_encoder_complex | --docsis_config
Constructor
Add a Class of Service - docsis 1.0
Add Co-signer Code Verification Certificate - docsis 1.1
The Co-signer's Code Verification Cerrificat (C-CVC) for Secure Software Downloading. The CM config must contain this C-CVC and/or M-CVC in order to allow 1.1 compliant CM to download the code file from TFTP server regardless the CM is provisioned to run with BPI,BPI+, or none of them.
Add CPE Ethernet MAC Address - docsis 1.0, 1.1
Add Manufacturer Code Verification Certificate - docsis 1.1
The Manufaturer's Code Verification Cerrificat (M-CVC) for Secure Software Downloading. The CM config must contain this M-CVC and/or C-CVC in order to allow 1.1 compliant CM to download the code file from TFTP server regardless the CM is provisioned to run with BPI,BPI+, or none of them.
Add Service Not Available Response - docsis 1.0, 1.1
This configuration setting must be included in the Registration Response message if the CMTS is unable or unwilling to grant any of the requested classes of service that appeared in the Registration Request. Although the value applies only to the failed service class, the entire Registration Request must be considered to have failed (none of the class-of-service configuration settings are granted).
Confirmation codes:
Add SNMP MIB Object - docsis 1.0, 1.1
This object allows arbtrary SNMP MIB objects to be Set via the TFTP-Registration process.
The cable modem must treat this object as if it were part of an SNMP Set Request with the following caveats:
All such Sets must be treated as simultaneous.
Example values:
Add SNMP Write-Access Control - docsis 1.0, 1.1
This object makes it possible to disable SNMP "Set" access to individual MIB objets. Each instance of this object controls access to all of the writeable MIB objects whose Object ID (OID) prefix matches.
Any OID prefix may be used. The Null OID 0.0 may be used to control access to all MIB objects. (The OID 1.3.6.1 wil have the same effect.)
Set Downstream Frequency Configuration - docsis 1.0, 1.1
The receive frequency to be used by the CM. It is an override for the channel selected during scanning.
Set Downstream Packet Classifier - docsis 1.1
Set HMAC-Digest
The HMAC-Digest setting is a keyed message digest. If privacy is enabled, the HMAC-Digents Attribute must be the final Attribute in the Dynamic Service message's Attribute list. The message digest is performed over all of the Dynamic Service parameters (starting immediately after the MAC Management Message Header and up to, but not including the HMAC Digest setting), other than the HMAC-Digest, in the order in which they appear within the packet.
This parameter contains a keyed hash used for message authentication. The HMAC algorithm is defined in RFC2104. The HMAC algorithm is specified using a cryptographic hash algorithm. Baseline Privacy uses a particular version of HMAC that employs the Secure Hash Algorithm (SHA-1).
Key Sequence Number
This value shows the key sequence number of the BPI+ Authorizaion Key which is used to calculate the HMAC-Digest in case that the Privacy is enabled.
Set Maximum Number of Classifiers - docsis 1.1
This is the maximum number of Classifiers associated with admitted or active upstream Service Flows that the CM is allowed to have. Both active and inactive Classifiers are included in this count.
This is useful when using deferred activation of provisioned resources. The number of provisioned Service Flows may be high and each Service Flow might support multiple Classifiers. Provisioning represents the set of Service Flows the CM can choose between. The CMTS can control the QoS resources committed to the CM by limiting the number of Service Flows that are admitted. However, it may still be desirable to limit the number of Classifiers associated with the committed QoS resources. This parameter provides that limit.
Maximum Number of CPEs - docsis 1.0, 1.1
The maximum number of CPEs that can be granted access through a CM during a CM epoch. The CM epoch is the time between startup and hard reset of the modem. The maximum number of CPEs must be enforced by the CM.
Note: This parameter should not be confused with the number of CPE addresses a CM may learn. A modem may learn Ethernet MAC addresses up to its maximum number of CPE addresses. The maximum number of CPEs that are granted access through the modemis governed by this configuration setting.
The non-existance, or the value 0, must be intrepreted as the default value of 1.
Set Modem IP Address - docsis 1.0, 1.1
For backwards compatibility with DOCSIS v1.0. Replace by 'TFTP Server Provisioned Modem Address'.
Set Modem Capabilities - docsis 1.0, 1.1
Set Network Access - docsis 1.0, 1.1
If $value is 1, CPE attached to this CM are allowed to access the network, based on CM provisioning. If the value is 0, the CM must not forward traffic from attached CPE to the RF MAC network, but must continue to accept and generate traffic from the CM itself. The value of this field does not affect CMTS service flow operation and does not affect CMTS data forwarding operation.
Note: The intent of "NACO=0" is that the CM does not forward traffic from any attached CPE onto the cable network. (A CPE is any client device attached to the CM, regardless of how the attachment is implemented.) However, with "NACO=0", management traffic to the CM is not restricted. Specifically, with NACO off, the CM remains manageable, including sending/receiving management traffice such as (but not limited to):
In DOCSIS v1.1, with NACO off, the primary upstream and primary downstream service flows of the CM remain operational only for management traffic to and from the CM. With respect to DOCSIS v1.1 provisioning, a CMTS should ignore the NACO value and allocate any service flows that have been authorized by the provisioning server.
Set Payload Header Suppression - docsis 1.1
Set Privacy Enable - docsis 1.1
This configuation setting enables/disables Baseline Privacy on the Primary Service Flow and all other Service Flows for this CM. If a DOCSIS 1.1 CM receives this setting in a configuration file, the CM is required to forward this setting as part of the registration request regardless of whether the configuration file is DOCSIS 1.1-style or not while this setting is usually contained only in a DOCSIS 1.1 Service Flow TLVs.
Add SNMP v3 Trap (Notification Receiver) - docsis 1.1
Set Software Upgrade Filename - docsis 1.0, 1.1
Set Subscriber Management Control - docsis 1.1
Set Subscriber Management CPE IP Table - docsis 1.1
Set Subscriber Management Filter Groups - docsis 1.1
The Subscriber Management MIB allows filter groups to be assigned to a CM and CPE attached to that CM. These include two CM filter groups, upstream and downstream, and two CPE filter groups, upstream and downstream.
Set TFTP Server Provisioned Modem Address - docsis 1.0, 1.1
The IP address of the modem requesting the configuration. The purpose of this parameter is to prevent IP spoofing during registration.
Set TFTP Server Timestamp - docsis 1.0, 1.1
The sending time of the configuration file in seconds. The purpose of this parameter is to prevent replay attacks with old configuation files.
Set Software Upgrade TFTP Server - docsis 1.0, 1.1
Set Upstream Channel ID - docsis 1.0, 1.1
The upstream channel ID which the CM must use. The CM must listen on the defined downstream channel until an upstream channel description message with this ID is found. It is an override for the channel selected during initialization.
Set Upstream Packet Classifier - docsis 1.1
Inherited From docsis_encoder_complex
docsis_encoder_complex::docis_encoder_complex()
docsis_encoder_complex::encode()
Inherited From docsis_encoder
docsis_encoder::docsis_encoder()
docsis_encoder::encode()
Documentation generated on Mon, 14 Nov 2005 18:00:02 -0700 by phpDocumentor 1.3.0RC3