Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Activating a CPE Device

    You can activate SRX300 Services Gateway and NFX250 Network Services Platform devices in the following ways:

    • By connecting a computer to the LAN port of the device and entering the activation code through your browser
    • By specifying the activation code in Customer Portal

    You can activate a vSRX Services Gateway device by copying the configuration available in Customer Portal and pasting the configuration into the SRX Series device console. To copy the configuration in Customer Portal, click Sites > Stage-1 Config.

    To activate a device through your web browser:

    1. Connect a computer to the LAN port of the CPE device and power on the device.

      Refer to the documentation for the CPE device for more information.

    2. Open a Web browser in your computer.

      Because the CPE device is preconfigured with a management address, the browser displays the login page.

    3. Enter the activation code that you have received during the shipping process.
    4. Click OK.

      On successful authentication, the Phone-Home server pushes the initial configuration to the CPE device.

    To activate a device through Customer Portal:

    Note: If you activate the CPE device through Customer Portal, you do not need to activate it through a browser.

    1. Log in to Customer Portal.
    2. Click the Sites page in Customer Portal.

      After you use Customer Portal to add a site that uses a CPE device, the CPE device icon on the Sites page is gray if the device is inactive. When you hover over the CPE device icon on the Monitor page, you should see the message Device Status: Expected, which indicates that the device is ready to be activated. If you see the message Device Status: Undefined, contact your service provider for assistance.

    3. On the Device Status column, click Activate Device.

      The Activate Device page appears. The Activate Device page consists of Device Information and Device Activation.

    4. On Device Information page, view the site details, device details, and recipient details, and specify the activation code. For more information see, Table 1.
    5. Click Next.

      On Device Activation page, the device is activated through the following steps:

      • Detecting the device
      • Applying stage-one configuration to the device
      • Bootstrapping of device
      • Activating the device

      After each successful step, you can see a green check mark. If any of these steps fail, a red exclamation mark appears.

    6. After the activation process is complete, click OK.

      The Sites page appears. To see the device activation status, hover over the device icon on the Sites page. You see one of the following statuses:

      • EXPECTED—Device is ready for activation.
      • ACTIVE—Device is authenticated but not yet operational.
      • ACTIVATION_FAILED—Device is not authenticated.
      • GWR_SPAWNED—Device gateway component spawning is successful.
      • GWR_SPAWN_FAILED—Device gateway component spawning fails.
      • PROVISIONED—Device is operational.
      • PROVISION_FAILED—Device failed to become operational. Contact your service provider for assistance.

    Table 1: Fields on the Activate Device Page

    Field

    Description

    Site Name & Type

    View the name of the site on which the CPE device is activated.

    Connected Hub

    View the name of the hub to which the CPE device is connected.

    Device Model

    View the device model.

    Serial Number

    View the serial number of the CPE device.

    Activation Code

    Specify the activation code that your service provider supplied for the CPE device.

    Expiry Duration

    Specify how long you must wait to activate the device after it boots up. You can set a duration in the range 1 through 600 seconds. The default is 120 seconds.

    Recipient

    View the recipient details.

    Modified: 2017-08-15