Cisco Cisco Broadband Access Center Telco Wireless 3.10
8-6
Cisco Broadband Access Center for Cable Administrator’s Guide
OL-2445-02
Chapter 8 Broadband Access Center for Cable Support Tools and Advanced Concepts
Developing Template Files
•
DOCS-CABLE-DEVICE-MIB-OBSOLETE
•
CISCO-CABLE-MODEM-MIB
•
CLAB-DEF-MIB
•
PKTC-MTA-MIB
•
PKTC-SIG-MIB
•
PKTC-EVENT-MIB
Two versions of the DOCSIS MIB are loaded into the RDU:
•
DOCS-CABLE-DEVICE-MIB-OBSOLETE (experimental branch)
•
DOCS-CABLE-DEVICE-MIB (mib2 branch)
Consequently, DOCSIS MIBs must be fully qualified. Examples
illustrate both correct and
incorrect usage of option 11.
Example 8-8
Correct Use of Option 11
# Valid, uniquely identifying an OID
option 11 .experimental.docsDev.docsDevMIBObjects.docsDevNmAccessTable.docsDevNmAccess
Entry.docsDevNmAccessStatus.1, Integer, 4
# Valid, uniquely identifying a PacketCable OID
option 11 .pktcMtaDevEnabled.0, Integer, 1
Example 8-9
Incorrect Use of Option 11
# Invalid, docsDevNmAccessStatus is not uniquely identified, its in experimental and
# mib-2 branches
option 11 .docsDevNmAccessStatus.1, Integer, 4
Macro Variables
Macro variables are specified as values in templates and they let you to specify device specific option
values. When a macro variable is encountered in the template, the properties hierarchy is searched for
the macro variable name and the value of the variable is then substituted. The variable name is a custom
property, which is predefined in the RDU, and it must not contain any spaces.
values. When a macro variable is encountered in the template, the properties hierarchy is searched for
the macro variable name and the value of the variable is then substituted. The variable name is a custom
property, which is predefined in the RDU, and it must not contain any spaces.
Once the custom property is defined, it can be used in this property hierarchy:
•
System defaults
•
Technology defaults, such as DOCSIS and PacketCable
•
DHCP criteria properties
•
Class of service properties
•
Device properties
Note
Refer to the
, for additional information on
defining custom properties.
The template parser works bottom up when locating properties in the hierarchy (device first, then the
class of service, etc) and converts the template option syntax into. There are three supported syntaxes
for macro variables:
class of service, etc) and converts the template option syntax into. There are three supported syntaxes
for macro variables: