DOCS-CABLE-DEVICE-MIB Table View

This table controls access to SNMP objects by network
management stations.  If the table is empty, access to
SNMP objects is unrestricted.  The objects in this table
MUST NOT persist across reboots.  The objects in this
table are only accessible from cable devices that are
not capable of operating in SNMP Coexistence mode
(RFC 3584) or in SNMPv3 mode (RFC 3410).
See the conformance section for
details.  Note that some devices are required by other
specifications (e.g., the DOCSIS OSSIv1.1 specification)
to support the legacy SNMPv1/v2c docsDevNmAccess mode
for backward compatibility.
          
This table is deprecated.  Instead, use the SNMP
coexistence MIBs from RFC 3584, the TARGET and
NOTIFICATION MIBs from RFC 3413, and
the View-Based Access Control Model (VACM) MIBs for
all SNMP protocol versions from RFC 3415.

An ordered list of filters or classifiers to apply to
IP traffic.  Filter application is ordered by the filter
index, rather than by a best match algorithm (note that
this implies that the filter table may have gaps in the
index values).  Packets that match no filters will have
policy 0 in the docsDevFilterPolicyTable applied to
them, if it exists.  Otherwise, Packets that match no
filters are discarded or forwarded according to the
setting of docsDevFilterIpDefault.
          
Any IP packet can theoretically match multiple rows of
this table.  When considering a packet, the table is
scanned in row index order (e.g., filter 10 is checked
before filter 20).  If the packet matches that filter
(which means that it matches ALL criteria for that row),
actions appropriate to docsDevFilterIpControl and
docsDevFilterPolicyId are taken.  If the packet was
discarded processing is complete.  If
docsDevFilterIpContinue is set to true, the filter
comparison continues with the next row in the table,
looking for additional matches.
          
If the packet matches no filter in the table, the packet
is accepted or dropped for further processing
according to the setting of docsDevFilterIpDefault.
If the packet is accepted, the actions specified by
policy group 0 (e.g., the rows in
docsDevFilterPolicyTable that have a value of 0 for
docsDevFilterPolicyId) are taken, if that policy
          
group exists.
          
Logically, this table is consulted twice during the
processing of any IP packet: once upon its acceptance
from the L2 entity, and once upon its transmission to
the L2 entity.  In actuality, for cable modems, IP
filtering is generally the only IP processing done for
transit traffic.  This means that inbound and outbound
filtering can generally be done at the same time with
one pass through the filter table.
          
The objects in this table are only accessible from cable
devices that are not operating in DiffServ MIB mode
(RFC 3289).  See the conformance section for details.
          
Note that some devices are required by other
specifications (e.g., the DOCSIS OSSIv1.1 specification)
to support the legacy SNMPv1/v2c docsDevFilter mode
for backward compatibility.
          
Table entries MUST NOT persist across reboots for any
device.
          
This table is deprecated.  Instead, use the DiffServ MIB
from RFC 3289.

A Table that maps between a policy group ID and a set
of pointers to policies to be applied.  All rows with
the same docsDevFilterPolicyId are part of the same
group of policy pointers and are applied in the order
in this table.  docsDevFilterPolicyTable exists to
allow multiple policy actions (referenced by policy
pointers) to be applied to any given classified packet.
The policy actions are applied in index order.
For example:
          
Index   ID    Type    Action
 1      1      TOS     1
 9      5      TOS     1
 12     1      IPSEC   3
          
This says that a packet that matches a filter with
policy id 1 first has TOS policy 1 applied (which might
set the TOS bits to enable a higher priority) and next
has the IPSEC policy 3 applied (which may result in the
packets being dumped into a secure VPN to a remote
encryptor).
          
Policy ID 0 is reserved for default actions and is
applied only to packets that match no filters in
docsDevFilterIpTable.
          
Table entries MUST NOT persist across reboots for any
device.
          
This table is deprecated.  Instead, use the DiffServ MIB
          
from RFC 3289.

Table used to describe Type of Service (TOS) bits
          
processing.
          
This table is an adjunct to the docsDevFilterIpTable
and the docsDevFilterPolicy table.  Entries in the
latter table can point to specific rows in this (and
other) tables and cause specific actions to be taken.
This table permits the manipulation of the value of the
Type of Service bits in the IP header of the matched
packet as follows:
          
Set the tosBits of the packet to
   (tosBits & docsDevFilterTosAndMask) |
   docsDevFilterTosOrMask
          
This construct allows you to do a clear and set of all
the TOS bits in a flexible manner.
          
Table entries MUST NOT persist across reboots for any
device.
          
This table is deprecated.  Instead, use the DiffServ MIB
from RFC 3289.

This table lists the IPv4 addresses seen (or permitted)
as source addresses in packets originating from the
customer interface on this device.  In addition, this
table can be provisioned with the specific addresses
permitted for the CPEs via the normal row creation
mechanisms.  Table entries MUST NOT persist across
reboots for any device.
          
N.B.  Management action can add entries in this table
and in docsDevCpeIpTable past the value of
          
docsDevCpeIpMax.  docsDevCpeIpMax ONLY restricts the
ability of the CM to add learned addresses
automatically.
          
This table is deprecated and is replaced by
docsDevCpeInetTable.