Cisco Cisco Broadband Access Center for Cable 4.1
8-5
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
Instance Modifier
and
illustrate both correct and incorrect methods of creating separate TLVs. These are required to
enable the IOS DOCSIS modem to interpret the IOS commands as two separate commands.
Example 8-6
Correct IOS Command Line Entries
# Valid, each IOS command gets it's own TLV
option 43.8 instance 1 00-00-0C
option 43.131 instance 1 ascii "login"
option 43.8 instance 2 00-00-0C
option 43.131 instance 2 ascii "password cable"
Example 8-7
Incorrect IOS Command Line Entries
# Invalid, IOS commands are grouped into one TLV
option 43.8 00-00-0C
option 43.131 ascii "login"
option 43.131 ascii "password cable"
# Invalid, using instance on non-compound options
option 3 instance 1 1
Note
The encoding type for option 43.8 is an organizationally unique identifier (OUI). Unlike that
shown in
shown in
, this only accepts an 00-00-0C format.
Option 11 (SNMP Varbind)
You must use an object identifier (OID), when specifying DOCSIS option 11 or PacketCable option 64.
The MIB that contains the OID must be in one of the following MIBs loaded by the RDU. You must
specify as much of the OID as needed to uniquely identify it and the name or the number of the OID can
be used. The RDU automatically loads these MIBs:
The MIB that contains the OID must be in one of the following MIBs loaded by the RDU. You must
specify as much of the OID as needed to uniquely identify it and the name or the number of the OID can
be used. The RDU automatically loads these MIBs:
•
SNMPv2-SMI
•
SNMPv2-TC
•
CISCO-SMI
•
CISCO-TC
•
SNMPv2-MIB
•
RFC1213-MIB
•
IANAifType-MIB
•
IF-MIB
•
DOCS-IF-MIB
•
DOCS-BPI-MIB
•
CISCO-CABLE-SPECTRUM-MIB
•
CISCO-DOCS-EXT-MIB
•
SNMP-FRAMEWORK-MIB
•
DOCS-CABLE-DEVICE-MIB