3
the boot process of the cpe node
Boot start-up procedure:
• The first time that the device boots, it issues a DHCP Discover with dhcp option 60 set to
DKT_F2_firstboot
. The firmware can be downloaded to the unit.
• Alternatively if firmware is present in the device, the device issues a dhcp request with dhcp
option 60 set to
DKT_F2_firmware_vXX_XX
(where XX_XX is the version number of the firmware).
When a new node is unpacked from the factory, it doesn’t contain any firmware, and before it can
be used in must be updated with the latest revision. This mean that when the node is installed at the
customer premise, it will be required to remotely update with firmware, before it will be working. It
is highly recommended to visit www.dktcomega.com -> support -> firmware for latest boot loader and
firmware revision.
The managed node depends on DHCP negotiation. Through this negotiation the firmware ID of the man
-
aged node is exchanged for a configuration file. The DHCP server hands out the configuration file depend
-
ing on the firmware ID.
Uboot.
A device power-up it will start the uboot process. The purpose is to validate if the device has the correct
firmware image (if any), and bring it onto the network using DHCP.
Linux (Device OS system).
This is the main software with full network support and features to use the complete hardware platform.
The network is configured using DHCP, and the system configuration is downloaded using TFTP.
The first bootp/dhcp request from the device can be used to remote upgrade the firmware. If a bootfile
and a bootserver is given in the bootp response then the file is downloaded via tftp and executed by the
device.
The device is configured to not pass any traffic per default, so in order to pass traffic through the switch
engine, the
switch --enable-lan
command must be provisioned to the device. Also telnet daemon must be
started, with the use of
telnetd -l /bin/sh
command in the script
At device start-up configuration is provisioned automatically. Firmware is provisioned by request, either
at first boot or when applicable
Ensures correct device settings and automatically firmware upgrade without user interaction
Firmware and configuration are provisioned by the operator
DHCP Discover, vendor class id = DKT_B2_firstboot
DHCP Offer, IP A firmware info, network info
DHCP Request, parameter list, network info + file name
DHCP ACK, respond parameter list, network info etc
TFTP Request – file name
TFTP Transfer – file name
DHCP Release – release IP address and boot
DHCP Discover, vendor class id = DKT_F2_firmware_vXX_XX,
request configuration (option 66, 67)
DHCP Offer, IP A configuration info, network info
DHCP Request, parameter list, network info + conf file
DHCP ACK, respond parameter list, conf file, network info etc
TFTP Request – conf file
TFTP Transfer – conf file
If DHCP offer end with ”/” instead of specific file-name
then CPE will try to make TFTP Request for:
<CFG_DIR>dkt_config_<MAC>.sh
<CFG_DIR>dkt_config_<Hostname>.sh
<CFG_DIR>dkt_config_<Model>.sh
<CFG_DIR>dkt_config.sh
If DHCP offer doesn’t include any firmware file name,
then the device will release the IP Address and
continue to next step, Linux start-up
B
O
O
T
LO
A
D
E
R
LI
N
UX
DHCP Server
DKT 797xx
Содержание forsete-ii series
Страница 1: ...juma forsete ii series user guide...
Страница 9: ...9...
