Table of Contents

Creating a new CCAP/CM pair

To create CCAP/CM pairs, you can either create a single CCAP/CM pair at a time, or create elements in bulk from a CSV file.

Note

The creation of CCAP pairs using the connector Harmonic CableOS is currently not supported.

Creating a single CCAP/CM pair

  1. In DataMiner Cube, go to Apps > Automation.

  2. In the pane on the left, select the script EPM_I_DOCSIS_AddNewCcapCmPair.

  3. In the lower right corner, click Execute.

    This will open a pop-up window.

  4. Click Create single.

  5. In the General step:

    1. Define the element name (mandatory field).

      Note

      The name of the collector element will consist of the defined element name with the suffix _COLLECTOR.

      Important

      Make sure the element name does not contain any forbidden characters.

    2. Select the host for the CCAP.

    3. Select the host for the collector.

  6. In the CCAP Details step:

    1. Select the desired CCAP protocol.

      At present, the following protocols are supported:

      • CISCO CMTS CCAP Platform
      • Arris E6000 CCAP Platform
      • Casa Systems CCAP Platform
      • CISCO CBR-8 CCAP Platform
      • Huawei 5688-5800 CCAP Platform

    2. Select the desired protocol version. We recommend the production version.

    3. Enter the IP address that will be used to monitor the CCAP element (mandatory field).

    4. Enter the get community string that will be used by the CCAP to poll the device.

    5. Enter the set community string that will be used by the CCAP to set information in the device.

      Note

      The solution currently does not support SNMP sets from any CCAP connector/CM collector yet. This field has been added as a placeholder for upcoming SNMP set support.

    6. Enter the get community string for the collector.

    7. Enter the set community string for the collector.

      Note

      The solution currently supports only one single community string for all the CMs monitored by the CM collector. Therefore, this community string will be used to poll all CMs monitored by the CM collector. The list of CMs polled by this CM collector comes from the associated CCAP (the CCAP pair).

    8. Enter the user and password that can be used to access the shared folder where the CSV files created by the CM collector will be stored. Domain accounts are supported.

  7. In the View Details step, select the location where the CCAP/CM pair will be added in the EPM view structure.

  8. Click Create.

The elements will be created with the following specifications:

  • CCAP:

    • Element name: The defined element name.
    • Protocol: The selected protocol.
    • Protocol version: The selected version.
    • IP address: The defined IP address.
    • Alarm template: The default alarm template.
    • Trend template: The default trend template.
    • Get community string CCAP: The defined get community string for the CCAP.
    • Set community string CCAP: The defined set community string for the CCAP.
    • Entity export directory: The same directory as is set in the back end of the host.
    • Entity import directory: The same directory as is set in the back end of the host.
    • Entity import directory type: Remote.
    • System username: The username to access the shared folder.
    • System password: The password to access the shared folder.

  • Collector:

    • Element name: The defined element name combined with the suffix "_COLLECTOR".
    • Protocol: The Generic DOCSIS CM Collector protocol.
    • Protocol version: The production version.
    • IP address: 127.0.0.1.
    • Alarm template: public.
    • Trend template: private.
    • Get community string Collector: The defined get community string for the collector.
    • Set community string Collector: The defined set community string for the collector.
    • Entity import directory: The same directory as is set in the back end of the host.
    • Entity import directory type: Remote.
    • System username: The username to access the shared folder.
    • System password: The password to access the shared folder.
Note
  • It may take some time before the elements are created. The larger the cluster, the longer it will take to create the elements.
  • If a CISCO CBR-8 element is created, OFDM information will not be polled, and the service group names will use the interface alias by default. To change this, navigate to the configuration visual page of the newly created element and update the Extra Configurations settings as needed.

Creating CCAP/CM pairs in bulk from a CSV file

  1. In DataMiner Cube, go to Apps > Automation.

  2. In the pane on the left, select the script EPM_I_DOCSIS_AddNewCcapCmPair.

  3. In the lower right corner, click Execute.

    This will open a pop-up window.

  4. Click Create bulk.

  5. Below the Create Bulk script text, enter the path of the CSV file.

    Here is an example of a CSV file with the mandatory headers and the content of each row:

    ElementName Ccap_DMA Collector_DMA Protocol IpAddress GetCommunityString SetCommunityString GetCommunityStringColl SetCommunityStringColl Network Market Hub SystemUser SystemPass
    filename1 EPM-DMA03 EPM-DMA03 CISCO CBR-8 CCAP Platform 10.11.12.11 getPublic setprivate collectorget collectorset GLOBAL NETWORK EAST MARKET 01 EAST HUB 01 US1 123
    filename2 EPM-DMA04 EPM-DMA04 CISCO CBR-8 CCAP Platform 10.11.12.12 getprivate setPublic collectorget collectorset GLOBAL NETWORK EAST MARKET 01 EAST HUB 01 US2 123
    Note
    • The CSV file must be present on the server running the DMA.
    • The CSV file has to have the following structure: ElementName*, Ccap_DMA*, Collector_DMA*, Protocol*, IpAddress*, GetCommunityString, SetCommunityString, GetCommunityStringColl, SetCommunityStringColl, Network, Market, Hub, SystemUser, SystemPass.
    • For the Protocol column, only the following values are currently accepted:
      • CISCO CMTS CCAP Platform
      • Arris E6000 CCAP Platform
      • Casa Systems CCAP Platform
      • CISCO CBR-8 CCAP Platform
      • Huawei 5688-5800 CCAP Platform
    Note

    CSV files only support commas (,) as separators and must include the headers mentioned above.

  6. Click Create Bulk.

    The elements will be created with the specifications in the CSV file of each row. The script will provision devices in bulk, processing five elements at a time.

    Note
    • Each time the script is executed, it will attempt to create five elements. If there are fewer than five elements left to create, it will create as many as possible without any issues. After the first set of elements has been created, you can execute the script again without modifying the CSV file, and it will attempt to create the next set of five elements.
    • Click the Cancel button in any window to close the Automation script at any time.

  7. When the script has been executed, carefully read the window with information about the execution.

    • If any line begins with [ERROR], this means that the creation of that particular element failed.

    • Lines beginning with [INFO] provide information about any issues encountered after the creation of the elements or confirm the successful completion of processes.

Propose changes