Print this pagePrint this page

Email this topicEmail this topic

View PDFView PDF

Download EPUBDownload EPUB

cpe (privilege-exec-mode)

Enables a WiNG controller to perform certain operations on Customer Premises Equipments (CPEs) through an adopted T5 controller

A T5 controller uses the IPX operating system to manage its connected radio devices, as opposed to the WiNG operating system used by RFS wireless controllers and NX service platforms. A T5 controller, once enabled as a supported external device, provides data to WiNG to assist in a T5‘s management within a WiNG supported subnet populated by both types of devices. The CPEs are the T5 controller managed radio devices using the IPX operating system. These CPEs use a Digital Subscriber Line (DSL) as their high speed Internet access mechanism using the CPE‘s physical wallplate connection and phone jack.

Supported in the following platforms:

  • Wireless Controllers — RFS4010
  • Service Platforms — NX5500, NX7500, NX9500, NX9600, VX9000

Syntax

cpe [boot|reload|upgrade]
cpe boot system cpe [<1-24>|all] [primary|secondary] {on <T5-DEVICE-NAME>}
cpe [reload|upgrade <IMAGE-LOCATION>] cpe [<1-24>|all] {on <T5-DEVICE-NAME>}
Note

Note

These commands can also be executed on the T5 profile and device context. For more information, see T5 Profile Config Commands.

Parameters

cpe boot system cpe [<1-24>|all] [primary|secondary] {on <T5-DEVICE-NAME>}
cpe boot system Changes the image used by a CPE to boot. When reloading, the CPE uses the specified image.
cpe [<1-24>|all] Identifies the CPE(s) on which this change is implemented
  • <1-24> – Reloads only those CPEs whose IDs have been specified. Specify the ID from 1 - 24.
  • all – Reloads all CPEs
[primary|secondary] Select the next boot image
  • primary – Uses the primary image when reloading
  • secondary – Uses the secondary image when reloading
on <T5-DEVICE-NAME> Optional. Performs this operation on a specified T5 device
  • <T5-DEVICE-NAME> – Specify the T5 device‘s hostname.
 
cpe [reload|upgrade <IMAGE-LOCATION>] cpe [<1-24>|all] {on <T5-DEVICE-NAME>}
cpe [reload| upgrade <IMAGE-LOCATION>] Performs the following operations on CPEs
  • reload – Reloads the device
  • upgrade <IMAGE-LOCATION> – Upgrades the device
  • <IMAGE-LOCATION> – Specify the location of the firmware image. Both IPv4 and IPv6 addresses are supported.

    Use one of the following options to provide the location:

    IPv4 URLs:
    • tftp://<hostname|IP>[:port]/path/file
    • ftp://<user>:<passwd>@<hostname|IP>[:port]/path/file
    • sftp://<user>:<passwd>@<hostname|IP>[:port]>/path/file
    • http://<hostname|IP>[:port]/path/file cf:/path/file usb<n>:/path/file
    IPv6 URLs:
    • tftp://<hostname|[IPv6]>[:port]/path/file
    • ftp://<user>:<passwd>@<hostname|[IPv6]>[:port]/path/file
    • sftp://<user>:<passwd>@<hostname|[IPv6]>[:port]>/path/file
    • http://<hostname|[IPv6]>[:port]/path/file
Note: After specifying the operation to perform, identify the device(s).
cpe [<1-24>|all] Identifies the CPE(s) on which the operation is performed
  • <1-24> – Configures the CPE‘s ID from 1 - 24
  • all – Configures all CPEs
on <T5-DEVICE-NAME> Optional. Performs this operation on a specified T5 device
  • <T5-DEVICE-NAME> – Specify the T5 device‘s hostname.

Example

nx9500-6C8809#show t5 cpe boot on t5-ED7C6C
----------------------------------------------------------------------------------------------------
  DEVICE   PRIMARY VERSION   SECONDARY VERSION   NEXT BOOT   UPGRADE STATUS    UPGRADE PROGRESS %
----------------------------------------------------------------------------------------------------
 cpe1      5.4.2.0-010R      5.4.2.0-006B       primary     none              0 
 cpe2      5.4.2.0-010R      5.4.2.0-006B       primary     none              0 
----------------------------------------------------------------------------------------------------
nx9500-6C8809#
nx9500-6C8809#cpe boot system cpe 1 secondary on t5-ED7C6C
Updated T5 CPE system boot partition
nx9500-6C8809#
Published August 2019prev | next

Email this topicEmail this topic

Print this pagePrint this page