The DOCSIS Provisioning of
Ethernet Passive Optical Network (DPoE) 1.0 is a standard for provisioning EPON
access technology using the existing DOCSIS provisioning flow. DPoE network
offers IP high speed data services equivalent to DOCSIS networks, where the
DPoE network acts like a DOCSIS CMTS. The DPoE system and DPoE Optical Network
Unit appear to act like a DOCSIS CM also known as virtual CM(vCM). Prime Cable
Provisioning uses the existing DOCSIS device type for DPoE vCM devices. DPoE
configuration files contain a mixture of DOCSIS and DPoE-specific TLVs.
From 5.3 release, PCP also supports DPoE 2.0. DPoE 2.0 specifications
augment the DPoE 1.0 specifications to provide requirements for additional
service capabilities and corresponding provisioning and network management
capabilities. This simplifies the provisioning of complex network-wide
services.
To identify a DPoE vCM, refer
to the DHCP discover data captured under Request Dictionary displayed under
Device Details page. Details similar to the following example show up and if
the text in bold appear in page, then it is DPoE vCM.
Example:
v-i-vendor-opts = enterprise-id 4491, (oro 1 2)
chaddr = 00:00:00:00:0d:12
relay-agent-info = (circuit-id 1 80:01:03:ef), (remote-id 2 00:00:00:00:0d:12), (v-i-vendor
-opts 9 enterprise-id 4491, (cmts-capabilities 1 (docsis-version 1 03:00
), (dpoe-system-version 1 01:00), (dpoe-system-pbb 4 10248294639d, 1a9eb
ee4971b, 26d07cd85ab2, 33800cf1abbb, 3b87c25dffbb, 47bd40a08f95, 4fc50b5
3a070, 5768bd554059, 591cf857aea1, 638c2d178f8f, 6d932a665ec9, 74efc6fc0
60b, 7a602d489587)))
relay-agent-circuit-id = 01:04:80:01:03:ef
client-id-created-from-mac-address = 0
dhcp-class-identifier = AIC Echo,docsis3.0:
hlen = 06
giaddr = 4.0.0.1
vendor-encapsulated-options = (device-serial-number 4 000000000d12), (hardware-version-number 5 v3.2.1
), (software-version-number 6 v1.0.2), (boot-rom-version 7 BOOT1.0), (ve
ndor-oui 8 000000), (vendor-name 10 XEROX CORPORATION), (dpoe-embedded-c
omponents-list 55 ECM)
dhcp-parameter-request-list = {1,3,6,7,12,15,51,54,4,2,67,66}
client-id = ff:00:00:00:00:00:03:00:01:00:00:00:00:0d:12
Sample DPoE Configuration file
The sample DPoE configuration files are available under the installed package at location:
-
Static file: dpoe_vcm.cm -- /opt/CSCObac/rdu/samples/docsis
-
Groovy file: example_dpoe_vcm.groovy -- /opt/CSCObac/rdu/samples/groovy
-
Template file: dpoe_vcm.tmpl -- /opt/CSCObac/rdu/templates
Note |
Prime Cable Provisioning supports provisioning of DPoE vCMs in IPv4 and IPv6 mode. Also, only downstream of computer devices from a DPoE vCMs is supported.
|
See
DPoE Option Support for the DPoE TLVs.
Differences between DPoE and DOCSIS Provisioning
The provisioning of a DPoE vCM is nearly identical to the provisioning of DOCSIS CM. This allows existing DOCSIS-based back-office systems (such as provisioning servers) to support DPoE vCM provisioning with minimal changes. However, there are minor differences between DPoE vCM and DOCSIS CM provisioning:
-
The DPoE specifications do not support IPv6 or PacketCable Voice services. Only IP (HSD) and MEF services are supported.
-
The DPoE System (CMTS) supplies additional relay agent DHCP options. The DHCPv4 Relay Agent CMTS capabilities option contains additional sub-options (sub-option 2: DPoE System Version Number and sub-option 4: DPoE System DHCPv4 PBB service option).
-
The DPoE vCM does not request ToD. The DPoE System (CMTS) supplies the time reference directly to the vCM.
-
The DPoE vCM uses the same DHCPv4 option-60 value as DOCSIS 3.0 CM (i.e., docsis3.0). By itself, the DHCPv4 option-60 value is not sufficient to identify the device as a DPoE vCM.
-
The DPoE vCM uses a new eSAFE DHCP option-43 sub-option 55 for specifying the list of eSAFE devices behind the eCM.
-
The DPoE vCM supports new configuration file TLVs not supported by DOCSIS 3.0 MULPI (i.e., TLVs [22/23].14, [22/23].14.1, [22/23].14.2, [22/23].14.5, [22/23].14.6, [22/23].15, [22/23].15.1, [22/23].15.2).
-
The DPoE vCM does not require or support all configuration file TLVs required by DOCSIS 3.0 MULPI. When the DPoE system encounters a TLV that is not supported, then the DPoE system ignores the TLV and allow the DPoE ONU to register normally.