Other Important Information

Force Upgrade Option in DHCP

When enabled, force upgrade option will upgrade the current image in the following scenario:

  • Current image on the device is not the same as the image configured in DHCP config.

  • The safe image on the device is the same as the image configured in DHCP but declared as INVALID.

The following table describes the iNode image upgrade behaviour for both force upgrade and normal download scenarios based on iNode DHCP configuration file :

Active image (running)

Secondary/Safe image

Safe ImageValid

Normal Download

Force Download

Different from DHCP config

Same as DHCP config

Yes

Switch to Safe image

Download & Switch

Different from DHCP config

Same as DHCP config

No

Stay in Current image

Download & Switch

Different from DHCP config

Different from DHCP config

Yes

Download & Switch

Download & Switch

Different from DHCP config

Different from DHCP config

No

Download & Switch

Download & Switch

Same as DHCP config

Same as DHCP config

Yes

No Action

No Action

Same as DHCP config

Same as DHCP config

No

No Action

No Action

Same as DHCP config

Different from DHCP config

Yes

No Action

No Action

Same as DHCP config

Different from DHCP config

No

No Action

No Action

For software upgrade, specific DHCP options are used to provide the iNode with the IP address of the TFTP server, Vendor identification, and image version information. The force download is one of these DHCP options. Force upgrade option can be enabled by configuring the following value: TLV 44: Sub type = 01 (Force Upgrade) length = 0x00.

The following figure shows how the contents of the configuration file is displayed using the Excentis DOCSIS Config File Editor. In this example, an IPv4 TFTP server address is also shown but it is not necessary for IPv6.

Instructions for DHCP Custom Options

SLAAC is not supported in this release. If the RPD is running a software version 5.2.x or earlier, to avail IPv6 support and download the iNode software successfully, apply the following DHCP custom options.

In addition to the standard DHCP options required by the OIB for software download, the customer must create 2 custom DHCPv6 options and an optional third option if an IPv6 prefix length other than /64 is required for the OIB.

# Define custom options to provide IPv6 Default Route, Prefix and any Static Routes:
# this is a short-term work around until you are able to receive RA messages.
option dhcp6.default-route code 214 = array of ip6-address;
option dhcp6.static-routes code 216 = array of ip6-address;
# add if OIB Prefix Length is something other than the /64 default.
option dhcp6.prefix code 215 = unsigned integer 8;

dhcp6.default-route is assigned two IPv6 address, order is important, the Gateway Router's Link-Local IPv6 address followed by it's Global IPv6 address.

dhcp6. static-routes is assigned a list of IPv6 addresses of any servers the OIB needs to reach that are within the same prefix as the OIB.

option dhcp6.prefix is the prefix length the OIB would have been assigned by the Router Advertisement message.

SLACC is not supported. The OIB's Global IP address must be assigned by the DHCPv6 server.