DKT Comega juma-ii series 사용자 설명서 - 페이지 5

{카테고리_이름} DKT Comega juma-ii series에 대한 사용자 설명서을 온라인으로 검색하거나 PDF를 다운로드하세요. DKT Comega juma-ii series 12 페이지. Cpe

3) CPE requests in its LINUX Boot-up process, where configuration file is requested:

Option: 1, 3, 6, 12, 43, 54, 66, 67 - Please make sure that DHCP Server responds to these option re-

quests, as it will influence on the booting sequence, if these are not correctly answered, and may cause

inproper booting of the device.

custom configuration

When the OS issue a dhcp request a filename of a configuration file can be sent to the device. This

configuration file is then downloaded by tftp during the boot process and issued instead of the default

configuration. In this way it is possible to persist settings for each customer (by mapping the hardware

address of the node and the customer number).

The server and the filename of the configuration file should be sent in respective tftp-server-name (op-

tion 66) and bootfile-name (option 67) from the dhcp server. Notice these options are different from the

bootfile/bootserver used in the bootp response.

If it is not feasible that the dhcp server distinguish the customer's configurations base on the hardware

address an alternative method can be used. The dhcp server sends out the name of a generic configura-

tion. This configuration can then include instruction to the node of fetching a node specific configure by

tftp where the requested filename is a combination of the node hardware address.

In the generic configuration script, which is common for all devices and that will provisioned during boot

up, the following instructions can be inserted:

source /etc/dhcp.vars

export WAN_MACADDR=$(ip addr show dev eth0 | grep "ether" | cut -d " " -f6 | tr -d :)

tftp -g -r my_conf_$WAN_MACADDR -l /tmp/config.sh $TFTP_SERVER

save_configuration

source /tmp/config.sh

Alternatively, if DHCP offer in the response instead just end with "/" instead of specific file-name then the device

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