Understanding the Application Settings for the Cloud CPE Selfcare Application for MX Series Routers

cCPE Selfcare Application settings enable service providers to control what their cCPE customers can view and manage in the Selfcare Portal.

Note: You must have Super Administrator privileges to configure cCPE Selfcare Application settings. For details about administering users and predefined roles in cCPE Selfcare Application, see Understanding User Administration in Cloud CPE Selfcare Application for MX Series Routers.

You can enable or disable access to features in the Selfcare Portal through Junos Space Network Management Platform user interface. If you do not want to expose certain resources in the Selfcare Portal, you can deny user access to the corresponding tasks by specifying the application settings in the Selfcare Portal.

To access cCPE Selfcare Application settings, from Junos Space Network Management Platform task pane, select Platform > Administration > Applications.

The Applications page appears in the content pane, an example of which is shown in Figure 1.

Figure 1: Example-Junos Space Network Management Platform Applications Page

To modify the application settings for cCPE Selfcare Application, either right-click on Selfcare Portal in the list of applications, or select Selfcare Portal from the list of applications on the Applications page, then select Modify Application Settings from the Actions list in the upper-right corner of the page.

The administration page is displayed, an example of which is shown in Figure 2.

Figure 2: Example-Administration Page

The administration page enables you to control what your cCPE customers can view and manage in the Selfcare Portal related to:

• Customer management
• Features
• Notifications
• SNMP

Each of these settings is described in more detail in the following sections.

Customer Management Application Settings

The customer management application settings enable you set the default password and default username prefix for all Selfcare Portal user accounts. User accounts are automatically generated when you create a customer.

To access the customer management application settings, from the administration page, select view/configure next to Customer management.

The Customer management dialog box is displayed, an example of which is shown in Figure 3.

Figure 3: Example-Customer Management Dialog Box

In the Customer management dialog box, you can specify the default prefix for all Selfcare Portal user accounts. User account names are automatically created when you create a customer in the Selfcare Portal. For example, if you create a customer called foo and the Selfcare User Prefix option is set to admin, the account name is generated as: admin@foo.

Select the Verify access link network information check box to verify the routing instance name when you create the access link. You only need to enable this option if you are using the RESTful APIs to configure access links. If you are using the Selfcare Portal to configure sites, the Selfcare Portal prepopulates these fields for you.

For more information on cCPE Selfcare Application user administration and creating customers, see Understanding User Administration in Cloud CPE Selfcare Application for MX Series Routers and Creating Customers in the Cloud CPE Selfcare Application for MX Series Routers.

Features Application Settings

The Features application settings enable you to specify which features cCPE customers can configure through the Selfcare Portal.

To access the Features application settings, from the administration page, select view/configure next to Features.

The Features dialog box is displayed, an example of which is shown in Figure 4.

Figure 4: Features Dialog Box

From the Features dialog box, you can control the following features:

• Dhcp relay gui — Specifies whether cCPE customer administrators can configure DHCP relay using the Selfcare Portal.
  • If this option is selected, cCPE customer network administrators can use the Selfcare Portal to configure DHCP relay settings.
  • If this option is not selected, cCPE customer network administrators cannot configure DHCP relay options through the Selfcare Portal.
• Dhcp server gui — Specifies whether cCPE customer network administrators can configure DHCP server using the cCPE Selfcare Portal.
  • If this option is selected, cCPE customer network administrators can use the Selfcare Portal to configure DHCP server settings.
  • If this option is not selected, cCPE customer network administrators cannot configure DHCP server options through the Selfcare Portal.
• Private address management gui — Specifies whether cCPE customer network administrators can manage private IP addresses using the Selfcare Portal.
  • If this option is selected, cCPE customer network administrators can use the Selfcare Portal to configure private IP addressing options.
  • If this option is not selected, cCPE customer network administrators cannot configure private IP addressing options using the Selfcare Portal.
• SNMP gui — Specifies whether cCPE customer network administrators can configure SNMP options using the Selfcare Portal.
  • If this option is selected, cCPE customer network administrators can use the Selfcare Portal to configure SNMP options.
  • If this option is not selected, cCPE customer network administrators cannot configure SNMP options using the Selfcare Portal.

  SDN: view/configure — Specifies whether software-defined networking (SDN) features can be configured using the Selfcare Portal. All SDN features are disabled by default. Enable or disable the following options:

  • Admin gui — Enable or disable SDN configuration capabilities in the Selfcare Portal for the service provider administrator (spadmin) account.
  • Api — Enable or disable SDN configuration capabilities in the Selfcare Portal for the RESTful APIs.
  • User gui — Enable or disable SDN configuration capabilities in the Selfcare Portal for the customer network administrators (admin@customer) account.

Notification Applications Settings

Notifications are used to synchronize the Selfcare Portal user interface with changes taking place in the network. Changes include pending configurations when they are committed in the PE router, or changes made by other users of the Selfcare Portal. cCPE Selfcare Application automatically requests subscriptions for notifications about things that affect what to display in the user interface. Because these subscriptions consume resources on the server, cCPE Selfcare Application automatically frees up subscription resources if they are idle for a certain amount of time. The Subscription idle timeout option controls this idle time.

You navigate to the Notification application settings dialog box, shown in Figure 5, by selecting view/configure next to Features on the administration page.

Figure 5: Notification Dialog Box

You can configure the following options in the Notification dialog box to limit the number of subscriptions created by the service provider user interface and per end customer:

• Max subscriptions from sp — Specifies the maximum number of subscriptions from the spadmin user account. The default is 10. Subscriptions for cCPE customer database changes and device configuration changes are counted separately (not combined together). You can specify a maximum of 10 database subscriptions and 10 configuration subscriptions from the spadmin user account.
• Max subscriptions per customer — Specifies the maximum number of subscriptions by a cCPE customer. The default is 10. Subscriptions for cCPE customer database changes and device configuration changes are counted separately (not combined together). You can specify a maximum of 10 database subscriptions and 10 configuration subscriptions from the admin@customer-name user account.

• Subscription idle timeout — Specifies how long a subscription can stay inactive before the server removes it. A subscription is inactive when there is no pulling (take-next-notification RESTful API call) from listeners. The range for the Subscription idle timeout is from 30 through 600 seconds. The default value is 120 seconds.

SNMP Application Settings

In Junos OS, an SNMP community can be bound to a specific routing instance by using the edit snmp community name routing-instance name configuration statement. If an SNMP request is received on a non-default routing instance and this routing instance is not bound to the specified SNMP community, the request is denied.

SNMP read requests from a non-default routing instance must use a community name in the format: routing-instance@community, where the routing-instance must be one of the routing instances bound to the community name. Such requests only return MIB objects pertaining to the specified routing-instance. For example, a SNMP walk on iftable with community “acme@ccperead” only returns interfaces belonging to the routing instance “acme”.

For the Selfcare Portal, all cCPE customers can use the same SNMP community name because the routing instance provides the required isolation between cCPE customers.

You navigate to the Snmp application settings dialog box, shown in Figure 6, by selecting view/configure next to Snmp on the administration page.

Figure 6: SNMP Dialog Box

In the SNMP application settings dialog box, you can specify the following SNMP settings used by cCPE customers:

• Authorization — Specify the default authorization level for the SNMP community. Possible values are:
  • ReadOnly (default)
  • ReadWrite
• Community — Specify the default SNMP Community name. The default value is: ccperead.
• View — Specify the SNMP view name.

  Note: The SNMP view must be preconfigured by service providers on the router, see SNMP Monitoring for cCPE Services Overview and Configuring SNMP cCPE Monitoring Services on MX Series Routers.