The dot1dBase Group
This is a mandatory group which contains the objects which are applicable to all types of bridges. Table 27. The dot1dBase Group.
Mib Object Object Valve Description Access
dot1dBaseBridgeAddress CCCM MAC address Hardcoded, read-only dot1dBaseNumPorts 2 (RF port, CPE port ) Hardcoded, read-only
dot1dBaseType Transparent-only(2) Hardcoded, read-only dot1dBasePortTable See the Table Below
Dot1dBasePortTable
The following table contains generic information about every port that is associated. Table 28. Dot1dBasePortTable.
Mib Object Object Valve Description Access
Dot1dBasePort 1 – for CPE port; 2 – for RF port
Read-only Dot1dBasePortIfIndex IfIndex of CPE interface (1) – for CPE
port;
IfIndex of CATV MAC interface (2) – for RF port
Read-only
Dot1dBasePortCircuit {0,0} – For a port which has a unique value of dot1dBasePortIfIndex, this object can have the value{0,0} .
Read-only
Dot1dBasePortDelayExceededD iscards
# of frames discarded by the port due to excessive transit delay through the bridge, May be 0 .
Read-only
Dot1dBasePortMtuExceededDis cards
# of frames discarded by the port due to excessive size, May be 0.
Read-only
The dot1dStp Group = Not Implemented
If a node does not implemented the Spanning Tree Protocol, this group will not be implemented. The dot1dSr Group = Not Implemented
If source routing is not supported this group will not be implemented.
The dot1dTp Group = Not implemented or limited implementation as described below:
This group contains objects that describe the entity's state with respect to transparent bridging. If transparent bridging is not supported this group will not be implemented. This group is applicable to transparent only and SRT bridges.
Table 29. The dot1dTp Group.
Mib Object Object Valve Description Access
dot1dTpLearnedEntryDiscards Supported Hardcoded, readonly dot1dTpAgingTime 1000001 Hardcoded, readonly
dot1dTpFdbEntry (Table) For transparent bridging only – read-only Table has 2 entries, see below
dot1dTpFdbAddress CPE MAC address . Hardcoded, readonly dot1dTpFdbPort 0 (port number has not been
learned)
Hardcoded, readonly dot1dTpFdbStatus 4: self(4) Hardcoded, readonly dot1dTpPortTable See Table Below
Table 30. dot1dFdbTable.
Mib Object Object Valve Description Access
dot1dTpFdbAddress CPE MAC address – for port on CATV MAC interface;
CATV MAC address – for port on CPE interface;
Hard coded, read-only
dot1dTpFdbPort 0 (port number has not been learned) for both entries
Hard coded, read-only dot1dTpFdbStatus self(4) for both entries Hard coded, read-only dot1dTpPortTable
A table that contains information about every port that is associated with the transparent bridge. Table 31. dot1dTpPortTable.
Mib Object Object Valve Description Access
Dot1dTpPortMaxInfo 1500 – Maximum size of the info(non-mac) field that the port will receive or transmit.
read-only Dot1dTpPortInFrame Counter - supported read-only Dot1dTpPortOutFrames Counter – supported read-only Dot1dTpPortInDiscards CPE = CPE Discards
MAC=MAC Discards
read-only
C.2.1 RFC-2863 ifTable MIB-Object details for CCCM
From SNMP perspective, CCCM MUST mimics the standalone CM. The generic network interface MIB on logical CPE interface MUST be supported (RFC-2863), with the following recommended values
Table 32. RFC-2863 ifTable MIB-Object details for CCCM. ifTable / ifXTable Table
Column
Implementation for CPE interface
ifIndex 1
ifDescr Up to RFC-2863 and OSSI Appendix B ifType 1 - other
ifMtu 1500 ifSpeed 10Mbit/sec ifPhysAddress Empty string
ifAdminStatus Up to RFC-2863. Setting this object to ‘disable’ causes no data flow to the PC CPE behind the modem. (Similar to the “NACO off” operation)
ifOperStatus Up to RFC-2863 and OSSI Appendix B ifLastChange Up to RFC-2863 and OSSI Appendix B ifInOctets Up to RFC-2863 and OSSI Appendix B ifInUcastPkts Up to RFC-2863 and OSSI Appendix B ifInDiscards Up to RFC-2863 and OSSI Appendix B ifInErrors Up to RFC-2863 and OSSI Appendix B ifInUnknownProtos Up to RFC-2863 and OSSI Appendix B ifOutOctets Up to RFC-2863 and OSSI Appendix B ifOutUcastPkts Up to RFC-2863 and OSSI Appendix B ifOutDiscards Up to RFC-2863 and OSSI Appendix B ifOutErrors Up to RFC-2863 and OSSI Appendix B ifName “Textual description” ifInMulticastPkts Up to RFC-2863 and OSSI Appendix B ifInBroadcastPkts Up to RFC-2863 and OSSI Appendix B ifOutMulticastPkts Up to RFC-2863 and OSSI Appendix B ifOutBroadcastPkts Up to RFC-2863 and OSSI Appendix B ifHCInOctets Up to RFC-2863 and OSSI Appendix B ifHCInUcastPkts Up to RFC-2863 and OSSI Appendix B ifHCInMulticastPkts Up to RFC-2863 and OSSI Appendix B ifHCInBroadcastPkts Up to RFC-2863 and OSSI Appendix B ifHCOutOctets Up to RFC-2863 and OSSI Appendix B ifHCOutUcastPkts Up to RFC-2863 and OSSI Appendix B ifHCOutMulticastPkts Up to RFC-2863 and OSSI Appendix B ifHCOutBroadcastPkts Up to RFC-2863 and OSSI Appendix B
ifLinkUpDownTrapEnable Up to RFC-2863 and OSSI Appendix B, enabled by default ifHighSpeed 10Mbit/sec
ifPromiscuousMode TRUE, read-only access ifConnectorPresent Always True(1)
ifAlias Up to RFC-2863 and OSSI Appendix B ifCounterDiscontinuityTime Up to RFC-2863 and OSSI Appendix B
Appendix D. Business Process Scenarios For Subscriber
Account Management
In order to develop the DOCS-OSS Subscriber Account Management Specification, it is necessary to consider high-level business processes common to cable operators and the associated operational scenarios. The following definitions represent a generic view of key processes involved. It is understood that business process terminology varies among different cable operators, distinguished by unique operating environments and target market segments
For the purpose of this document, Subscriber Account Management refers to the following business processes and terms:
Class of Service Provisioning Processes, which are involved in the automatic and dynamic provisioning and enforcement of subscribed class of policy-based service level agreements (SLAs);
Usage-Based Billing Processes, which are involved in the processing of bills based on services rendered to and consumed by paying subscriber customers.