DKT Comega CPE Operator's manual

CPE User Guide v_04_07 Page - 1
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
DKTCOMEGA CPE User Documentation

CPE User Guide v_04_07 Page - 2
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
Table of content
Introduction................................................................................................................................3
The boot process of the CPE node............................................................................................4
DHCP Settings ...................................................................................................................... 6
TFTP Settings ....................................................................................................................... 9
Custom configuration .......................................................................................................... 11
Device script commands.......................................................................................................... 13
Explanation of feature settings ................................................................................................ 19
VLAN settings ..................................................................................................................... 19
Provider mode (Double tagging, Q-in-Q)............................................................................. 21
Isolate LAN ports................................................................................................................. 22
Enable LAN......................................................................................................................... 22
Set LAN Port Speed............................................................................................................ 23
Set Port MTU size ............................................................................................................... 23
IGMP snooping ................................................................................................................... 23
Ingress rate limitation .......................................................................................................... 25
Egress rate limitation........................................................................................................... 28
Configuration of SNMP values ............................................................................................ 28
Syslog ................................................................................................................................. 28
Surveillance via SNMP........................................................................................................ 29
CATV setup......................................................................................................................... 29
Quality of Service (QoS)...................................................................................................... 30
Reboot................................................................................................................................. 32
Save configuration to flash.................................................................................................. 32
DHCP Option 82 ................................................................................................................. 33
LLDP/EDP/CDP .................................................................................................................. 34
Support for SSH .................................................................................................................. 35
VoIP ATA Plug-in module........................................................................................................ 38
DHCP/TFTP based provisioning ......................................................................................... 38
Web Interface...................................................................................................................... 39
System Parameters............................................................................................................. 39
VoIP Accounts..................................................................................................................... 44
VoIP Parameters................................................................................................................. 45
SIP Parameters................................................................................................................... 46
IPBX Parameters ................................................................................................................ 48
Regionalization.................................................................................................................... 50
Subscription Services.......................................................................................................... 56
User Configuration .............................................................................................................. 62
Feature Code Assignments (*55 - *99)................................................................................ 64
Wifi Plug-in module.................................................................................................................. 66
TFTP based provisioning .................................................................................................... 66
System Parameters............................................................................................................. 66
Appendix 1 –ATA configuration file......................................................................................... 73
Appendix 2 –Wifi configuration file.......................................................................................... 90

CPE User Guide v_04_07 Page - 3
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
Introduction
This is the documentation of the DKTCOMEGA managed CPE product line.
The hardware consists of a switch with a fiber WAN port and 4 RJ45 LAN ports.
These ports are connected together with a powerful programmable layer 2 switch.
A CPU is attached to the switch. Initial the switch is setup only to accept traffic
between the CPU and the WAN port, first in the end of the CPU boot process are
the LAN ports enabled.
As an option a VoIP (SIP based) plug-in module can be installed, which will give 2x
RJ-11 analogue phone connections.
The CPE is provisioned via DHCP/TFTP, however also SNMP can be used to for
surveillance and settings.
Following DKTCOMEGA product codes are supported:
10/100 Mbps #79204, from now on referred to as 100Mb
100/1000 Mbps #79403, from now on referred to as 1Gb
10/100 Mbps w/ VoIP #79265
100/1000 Mbps w/ VoIP #79275
100/1000 Mbps w/ VoIP + Wifi #79550, special release only!
VoIP Plug-in module #65699, for now on referred to as VoIP

CPE User Guide v_04_07 Page - 4
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
The boot process of the CPE node
The boot process is split in two:
-First the node issue a dhcp request with dhcp option 60 set to <file
name>vx_xx (where x_xx is the version number of the firmware).
-Afterwards the node start it's operation system (OS). The OS also issue a dhcp
request, with dhcp option 60 set to the version of the software.
When a new node is unpacked 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 managed node is exchanged for a configuration file. The DHCP
server hands out the configuration file depending on the firmware ID.
Bootstrap (Part of boot loader).
A small piece of code that is able to setup critical CPU specific registers such as
CPU clock, flash interface and SDRAM timing. The bootstrap code is automatically
loaded by the CPU into internal RAM of the CPU and executed. Bootstrap loads a
larger general boot-loader; U-boot.
U-boot (Part of boot loader).
This is a larger chunk of boot-loader software, which is able to setup network and
other more complex features of the CPU. U-boot use DHCP to get network setup.
U-boot is able to download firmware updates using TFTP.
Linux (Main Firmware).
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.

CPE User Guide v_04_07 Page - 5
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
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
DHCP
Server
DKTCOMEGA
CPE
DHCP Discover –Vendor class ID (DKT_Firstboot, option 60)
DHCP Offer –IP Address + DKT_firmware info (filename, server info, etc)
TFTP Request –”filename”
TFTP transfer of firmware
DHCP Discover –configuration (option 66, 67)
DHCP Offer –configuration (filename, server info, etc)
TFTP Request –”configuration”
TFTP transfer of configuration
Ensures correct device settings and automatically firmware upgrade without user interaction
Firmware and configuration are provisioned by the operator
}
At device start-up
configuration is
provisioned automatically.
Firmware is provisioned
by request, either at first
boot or when applicable
DHCP Request –request parameter list, incl network info
DHCP Release –Release IP
address
DHCP ACK –respond parameter list, incl network info + “file name”
DHCP Request –request parameter list, incl network info
DHCP ACK –respond parameter list, incl network info + “configuration”
Bo
ot
lo
ad
er
Li
nu
x

CPE User Guide v_04_07 Page - 6
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
DHCP Settings
The CPE requires a dhcp server connected to the fiber WAN port before power on.
As an example we have used Linux Kubunto platform and installed the following
component via adept
dhcp3
tftpd
Make sure that DHCP server has its unique static IP address settings, so it doesn’t
conflict with its own leasing of IP Addresses.
It is important that the DHCP server is properly configured, and that it responds to
the DHCP options requested by the CPE. Otherwise communication with the
internal CPU of the CPE can’t be obtained.
For more information about DHCP options in dhcp3, please refer to:
http://pwet.fr/man/linux/formats/dhcp_options
1) CPE requests in its BOOTLOADER discoverer:
Option: 53, 57, 60, 55
2) DHCP Server offers in it responses:
Option: 53, 54, 51, 1, 3

CPE User Guide v_04_07 Page - 7
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
3) CPE requests in its LINUX Boot-up process, where configuration file is requested:
Option: 53, 61, 60, 50, 54, 55, 1, 3, 28, 66, 67
To edit DHCP Server Setup for dhcp3, edit the DHCP setup configuration file:
sudo kate /etc/dhcp3/dhcpd.conf
# DHCP SECTION: insert the following

CPE User Guide v_04_07 Page - 8
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
default-lease-time <SECONDS>;
# Ex: default-lease-time 600
max-lease-time <SECONDS>;
# Ex: max-lease-time 7200
# --------------FIRMWARE UPGRADE PART -----------------
class "Upgrade Firmware after boot loader upgrade" {
match if option vendor-class-identifier = "DKT_firstboot";
filename = "dkt_fw_02_01.img";
}
# DHCP request in U-boot has got an option 43 field with
bootloader/U-boot software version information (ex. the text string
"14" for revision 1.4). This information is available from boot
loader revision 2_00 and forward
---# --------------- END OF UPGRADE -------------------
# The following is needed in order for the CPE to download the
configuration. Remember to place this configuration file in TFTPBOOT
directory. Remember to assign correct eth interface, subnet/mask, IP
address range, TFTP-server name and bootfile-name below
subnet <Subnet> netmask <Subnet mask> #
Ex: subnet 192.168.1.0 netmask 255.255.255.0
{
interface <Ethernet Interface>;
# Ex. interface eth0
range <Min IP Address> <Max IP Address>;
# Ex: range 192.168.1.10 192.168.1.30
option tftp-server-name "<TFTP Server IP Address>";

CPE User Guide v_04_07 Page - 9
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
# Ex: option tftp-server-name “192.168.1.1”
option bootfile-name "<Configuration_File_Name";
# Ex: option bootfile-name “cpe_settings.txt”
option broadcast-address <Broadcast IP Address>;
# Ex: option broadcast-address 192.168.1.255
option routers <Router IP Address>;
# Ex: option routers 192.168.1.1
server-name "<Server IP Address Name>";
# Ex: server-name “192.168.1.1”
option next-server <Server IP Address Name>;
# Ex: next-server 192.168.1.1
option subnet-mask <Subnet Mask>;
# Ex: option subnet-mask 255.255.255.0
}
To restart DHCP Server
Any change in the dchp configuration implies a server reset. For the
DHCP server used for this purpose the following instruction is
necessary:
sudo /etc/init.d/dhcp3-server restart
TFTP Settings
After the DHCP server is configured a TFTP server should be configured, so
firmware image and configuration file for the CPE can be downloaded correctly.
As an example we have used Linux tftpd and xinetd
The TFTP configuration file must be edited. And a tftpboot directory must be
created in root and made accessible from CPEs
mkdir tftpboot

CPE User Guide v_04_07 Page - 10
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
# creates tftpboot directory
chmod a+wrx tftpboot
# changes rights so directory is readable, writeable and executable
from CPEs
sudo kate /etc/xinetd.d/tftp
# starts an editor where TFTP settings can be inserted
Insert the following:
service tftp
{
protocol = udp
port = 69
# CONFIGURATION FILE SECTION: insert the following
socket_type = dgram
wait = yes
user = nobody
server = /usr/sbin/in.tftpd
server_args = /tftpboot
disable = no
}

CPE User Guide v_04_07 Page - 11
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
Custom configuration
When the OS issue a dhcp request a filename of a configuration file can be sent to
the node. 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 (option 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 customers configurations
base on the hardware address an alternativ method can be used. The dhcp server
sends out the name of a generic configuration. 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
An example of a configuration file
1
could be the following:
####################################################################
# DKT configuration
# Firmware version: 02_05
####################################################################
switch --enable-lan # enable LAN ports
# VLAN SETTINGS FOR WAN PORT
switch --set-port-802dot1q-mode=0:2
# Sets the WAN port in check mode, allows untagged on
ingress if VID (incl default) is present in VTU
switch --set-port-default-vid=0:102
# Default VLAN for WAN port
switch --add-vtu-entry 102:2:1:1:1:1:2:0
# Management VLAN, enables contact to CPU - untagged on
egress
switch --set-port-802dot1q-mode=1:3
# Sets the LAN port in secure mode
switch --set-port-802dot1q-mode=2:3
1
Please notice that text editors using Carrier Return for each line is NOT supported. The text editor should use
Line Feed for line separation.

CPE User Guide v_04_07 Page - 12
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
# Sets the LAN port in secure mode
switch --set-port-802dot1q-mode=3:3
# Sets the LAN port in secure mode
switch --set-port-802dot1q-mode=4:3
# Sets the LAN port in secure mode
switch --add-vtu-entry 104:3:2:2:1:1:2:0
# put WAN and LAN port into VLAN - untagged on egress,
IPTV VLAN
switch --set-port-default-vid=1:104
# Default VLAN for LAN port 1, IPTV VLAN
switch --set-port-default-vid=2:104
# Default VLAN for LAN port 2, IPTV VLAN
switch --add-vtu-entry 106:3:1:1:2:1:2:0
# put WAN and LAN port into VLAN - untagged on egress,
DATA VLAN
switch --set-port-default-vid=3:106
# Default VLAN for LAN port 3, DATA VLAN
switch --add-vtu-entry 105:3:1:1:1:2:2:0
# put WAN and LAN port into VLAN - untagged on egress,
VoIP VLAN
switch --set-port-default-vid=4:105
# Default VLAN for LAN port 4, VoIP VLAN
#
# QoS Settings
#Uplink rate (DATA port 3 and 4, ingress rates of 1 Mbps)
switch --set-port-ingress-rate-limit 3:0:1000:3:FC
# port=3, bucket=0, rate=1000kb/S,
bytecounter=layer3,limitaction=flowcontrol
switch --port-map-to-pirl-bucket 4:0
# join port 4 to bucket 0. Please notice that thisfeature
is NOT valid for the Gigabit CPE
#Downlink rate (Total for WAN 2Mbps)
switch --set-port-ingress-rate-limit 0:1:2000:3:FC
# port=0(WAN), bucket=0, rate=2Mb/S, bytecounter=layer3,
limitaction=flowcontrol
#
# Turn CATV module off
switch -c 0
#
# The following command enables TELNET access from WAN
telnetd -l /bin/sh
# End of DKT configuration
####################################################################

CPE User Guide v_04_07 Page - 13
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
Device script commands
The following commands are supported in the script that will be
downloaded to the CPE via TFTP during boot-up process.
This command is used to configure the switch in the unit. The command
takes one or more of the following parameters, with the syntax switch --
nn.
Please note that the commands are valid from firmware version 01_06 or
later.
Basic settings:
-s, --simple-switch
Setup port based VLAN for a simple switch.
-e, --enable-lan
Enables LAN ports so traffic can be switched between WAN and LAN.
-v, --version
Prints the firmware version number.
-h, --help
Prints this help text.
--set-arp-mirroring=PORT:enable
Enable/disable ARP mirroring to the CPU port, works from firmware
revision 02_13 and later
--get-arp-mirroring=PORT
Get state of ARP mirroring to the CPU port, works from firmware
revision 02_13 and later
CATV:
-c, --catv=(1|0)
Turns on/off the CATV module.
Unicast:
--add-uca=PORT:aa:bb:cc:dd:ee:ff
Adds the Ethernet address statically into the ATU.
--del-uca=aa:bb:cc:dd:ee:ff
Removes the Ethernet address from the ATU.
--dump-atu
Dumps the current content of the ATU, Ethernet addresses and Port
no.
Multicast:
--add-mca=PORT:aaa.bbb.ccc.ddd
Adds the IP multicast address statically to the ATU.

CPE User Guide v_04_07 Page - 14
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
--del-mca=PORT:aaa.bbb.ccc.ddd
Removes the IP multicast address from the ATU.
--enable-port-block-unknown-multicast=PORT:(1|0)
Blocks all Ethernet frames with Destination Address not present in
the ATU.
--get-enable-port-block-unknown-multicast=PORT
Prints the status of blocking all Ethernet frames with Destination
Address not present in the ATU.
--enable-port-igmp-snooping=PORT:(1|0)
Enables/disables IGMP snooping for the individual port.
--get-enable-port-igmp-snooping=PORT
Prints the status if IGMP snooping is enabled for the port.
--set-port-mtu=PORT:(0|1|2)
Sets the MTU size for the port 0…5, where 0 indicates support for
1522 bytes, 1 indicates support for 2048 bytes and 2 indicates
support for 10240 bytes
--get-port-mtu=PORT
Get the MTU size for the port
Link status:
--get-port-link-status=PORT
Gets the links status of the port
Speed and duplex mode:
--set-port-autonegotiation=PORT:(1|0)
Enable or disable autonegotation on the port
--get-port-autonegotiation=PORT
Gets the autonegotiation status of the port
--set-port-speed-
mode=PORT:(1000FD|1000HD|100FD|100HD|10FD|10HD|AUTO|FD|HD)
Sets the speed and duplex mode of the port
--get-port-speed-mode=PORT
Gets the speed and duplex mode of the port
Flow control:
--enable-port-flowcontrol=PORT:(1|0)
Enables/disables flow control on the port
--get-enable-port-flowcontrol=PORT:(1|0)
Prints the status of flow control on the port
Rate control:

CPE User Guide v_04_07 Page - 15
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
--dump-pirl-buckets
Prints the status of the PIRL buckets.
--set-port-egress-rate-limit=PORT:rate
Sets the egress rate for the port. Rate is in kbps range: 0,
128..1000000 - 0=unlimited
--get-port-egress-rate-limit=port
Display egress rate for the port.
--set-port-ingress-rate-limit=port:bucket:rate:layer:(DROP|FC)
Sets a Port Input Rate Limit(PIRL) bucket.
--get-port-ingress-rate-limit=port
Gets a list of enabled Port Input Rate Limit(PIRL) buckets.
--disable-pirl-bucket=bucket (100Mb)
--disable-pirl-bucket=port:bucket (1Gb)
Disables a PIRL bucket.
--port-map-to-pirl-bucket=port:bucket (100Mb)
Adds/maps a port to a Port Input Rate Limit(PIRL) bucket, note that
the rate limitation will be a shared between the ports.
--port-del-from-pirl-bucket=port:bucket (100Mb)
Removes a port from a Port Input Rate Limit(PIRL) bucket.
--port-enable-vid-nrl=port:enable (100Mb)
Enables/disables per port the Non rate limit for VLANs with the NRL
bit enabled.
QoS:
--set-port-ieee-tag-priority=PORT:(1|0)
Enables prioritized frames based on their IEEE priority tags
--get-port-ieee-tag-priority=PORT
Prints the status of Enable prioritized frames based on there IEEE
priority tags
--set-port-ip4ip6-priority-field=PORT:(1|0)
Enables prioritized frames based on their IP4/IP6 priority fields
--get-port-ip4ip6-priority-field=PORT
Prints the status of Enable prioritized frames based on their
IP4/IP6 priority fields
--set-port-map-rule=PORT:(1|0)
This makes IEEE tags to used priority to IP4/IP4 fields if both
exists.
--get-port-map-rule=PORT
Prints the status of if IEEE tags is prioritized over IP4/IP4 fields
if both exists.

CPE User Guide v_04_07 Page - 16
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
--set-ieee-queue-map=PRIO:QUEUE
Used to map IEEE tag priority 0-7 to internal queue 0-3.
--get-ieee-queue-map=PORT
Prints the queue of a mapped IEEE tag priority.
--set-ip4ip6-queue-map=PRIO:QUEUE
Used to map IP4/IP6 priority 0-63 to internal queue 0-3.
--get-ip4ip6-queue-map=PORT
Prints gets the queue of a mapped IP4/IP6 priority.
--set-sa-da-frame-priority-
override=PORT:SA_FRAME_PRIO_OVERRIDE:DA_FRAME_PRIO_OVERRIDE (100Mb)
Source Address(SA) or Destination Address(DA) Frame Priority
Override on an ATU match.
FRAME_PRIO_OVERRIDE=0..1
--set-sa-da-queue-priority-
override=PORT:SA_QUEUE_PRIO_OVERRIDE:DA_QUEUE_PRIO_OVERRIDE (100Mb)
Source Address(SA) or Destination Address(SA) Queue Priority
Override on an ATU match.
QUEUE_PRIO_OVERRIDE=0..1
--get-sa-da-frame-priority-override=PORT (100Mb)
Source Address(SA) or Destination Address(DA) Frame Priority
Override on an ATU match.
FRAME_PRIO_OVERRIDE=0..1
--get-sa-da-queue-priority-override=PORT (100Mb)
Source Address(SA) or Destination Address(DA) Frame Priority
Override on an ATU match.
FRAME_PRIO_OVERRIDE=0..1
--set-queue-priority=PORT:PRIORITY:ENABLE (100Mb)
Used to force queue priority for a port.
The priority will be superseeded by VTU, SA, DA or ARP priority.
PRIORITY=0..3, ENABLE=0..1
--get-queue-priority=PORT´ (100Mb)
Used to force queue priority for a port.
The priority will be superseeded by VTU, SA, DA or ARP priority.
This will return 1 if enabled, 0 if disabled.
IEEE 802.1Q VLAN:
--set-port-admit-only-tagged-frames=PORT:ENABLE
This will make sure that all frames received on the port is blocked
unless they are tagged with a VLAN ID.
--get-port-admit-only-tagged-frames=PORT
Prints the status of blocking untagged frames
# Note from firmware revision earlier than 02_05
--add-vtu-entry=VID:WAN:LAN1:LAN2:LAN3:LAN4:CPU:NRL-ENABLE
Adds an entry to the VTU table.

CPE User Guide v_04_07 Page - 17
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
# Note from firmware revision 02_05 or later
--add-vtu-entry=VID:WAN:LAN1:LAN2:LAN3:LAN4:CPU:NRL-
ENABLE[:PRIORITY]
Modes for the ports
0=egress unmodified, so the frames's VID tag will not be modified
1=not member, frames belonging to the VLAN will not be
present on the port
2=egress untagged, frames with VID tag will have this tag
stripped
3=egress tagged, frames will have the VID tag inserted
If the VID should be omitted in rate limitation, the NRL-ENABLE
should be set to 1, then PIRL bucket will be bypassed.
PRIORITY is optional parameter, a Class of Service value can be
associated to the specific VLAN. Value 0…7 is accepted. If
parameters is omitted no changes will be made to priority tag.
The parameter is only valid for firmware revision 02_05 or later.
--del-vtu-entry=VID
Removes the VTU entry for the VID.
--dump-vtu
Dumps the VTU table
--clear-vtu
Removes all entries of the VTU.
--set-port-default-vid=PORT:VID
Sets the default VLAN ID(VID) for a port.
--get-port-default-vid=PORT:VID
Prints the default VLAN ID(VID) for a port.
--set-port-force-default-vid=PORT:ENABLE
Forces the tagging of VID on all frames on the port.
--get-port-force-default-vid=PORT
Gets the status of force tagging of VID on all frames on the port.
--set-port-802dot1q-mode=PORT:MODE
Sets the IEEE 802.1Q mode for the ingress port.
Mode either
0=disable, disables IEEE 802.1Q for the port, used for port
based VLANs
1=fallback, enables IEEE 802.1Q for the port, fallback mode
2=check, enables IEEE 802.1Q for the port, check mode
3=secure, enables IEEE 802.1Q for the port, secure mode
--get-port-802dot1q-mode=PORT
Prints the 802.1Q mode for the ingress port.
Mode either
0=disable, disables IEEE 802.1Q for the port, used for port
based VLANs
1=fallback, enables IEEE 802.1Q for the port, fallback mode
2=check, enables IEEE 802.1Q for the port, check mode
3=secure, enables IEEE 802.1Q for the port, secure mode

CPE User Guide v_04_07 Page - 18
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
Port based VLAN:
--set-port-vlan-table=port:WAN_ENABLE:LAN1_ENABLE:LAN2_ENABLE:
LAN3_ENABLE:LAN4_ENABLE:CPU_ENABLE
Enable which ports are enabled for communication.
PORT_ENABLE is in the range 0..1
--get-port-vlan-table=port
Prints the port based VLAN mapping
RMON:
--get-rmon-histogram-mode
Sets the mode for the RMON counters.
0 = Rx only, 1 = Tx only, 2 = Sum of Rx and Tx.
--set-rmon-histogram-mode=MODE
Sets the mode for the RMON counters.
Mode must be between 0 and 2; 0 = Rx only, 1 = Tx only, 2 = Sum of
Rx and Tx.
--flush-all-rmon-counters
Flushes all counters on all ports.
--flush-port-rmon-counters=PORT
Flushes all counter for a single port.
--get-port-rmon-counters=PORT, Prints the RMON counters for a port.
DHCP Option 82:
supported from firmware revision 03_00 and later, in the 794xx
series (1 GbE CPE).
--set-port-dhcp-option82=PORT:enable[:<optional text>] (1Gb)
Enable or disable DHCP option 82 (DHCP relay agent).
1=enable, 0=disable
The optional text will be written in the "Option82 Agent
Circuit ID
Sub-option" field. If the optional text contains white space,
the text must be enclosed in "".
--get-port-dhcp-option82=PORT (1Gb)
Is DHCP option 82 (DHCP relay agent) enabled?
1=enable, 0=disable
"Option82 Agent Circuit ID Sub-option" text.

CPE User Guide v_04_07 Page - 19
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
Explanation of feature settings
VLAN settings
In SECURE mode, the VID for the given frame must be contained in the VTU, and
the Ingress port must be a member of the VLAN or the frame will be discarded.
In CHECK mode, the VID for the given frame must be contained in the VTU or the
frame will be discarded (the frame will not be discarded if the Ingress port is not a
memeber of the VLAN).
In FALLBACK mode, Frames are not discarded if their VID's are not contained in the
VTU. If the frame's VID is contained in the VTU, the frame is allowed to exit only
those ports that are members of the frame's VLAN; otherwise the switch 'falls back'
into Port Based VLAN mode for the frame.
Egress Tagging for a member port of a Vlan has the following three choices:
1. Unmodified
2. Untagged
3. Tagged
The default configuration defines no VLAN.
The following ports can be included in the VLAN setup:
WAN port = port <0>
LAN port 1 = port <1>
LAN port 2 = port <2>
LAN port 3 = port <3>
LAN port 4 = port <4>
CPU port = port <5>, this is the interface between the internal switch and
CPU engine (management and VoIP processor, if applicable)
Each LAN port can be setup up to tagged traffic there ingress the port with a given
vlan identifier. When the traffic egress the LAN port the vlan tag is removed. The
syntax for the command is:

CPE User Guide v_04_07 Page - 20
DKTCOMEGA
Fanoevej 6
DK-4060 Kirke Saaby
+45 4646 2626
+45 4646 2625
www.dktcomega.com
# VLAN SETTINGS FOR WAN PORT, WAN PORT WILL BE MEMBER OF ALL VLANS, SEE SETTINGS UNDER EACH VLAN
DEFINITION
switch --set-port-802dot1q-mode 0:3 # WAN port is in secure mode, allows tagged frames only
switch --add-vtu-entry 500:3:1:1:1:1:2:2:0 # puts WAN and CPU into vid 500, THIS IS MANAGEMENT VLAN
#
# VLAN SETTINGS FOR LAN PORT 1
switch --set-port-802dot1q-mode 1:3 # LAN port 1 is secure mode, allows tagged frames only
switch --add-vtu-entry 111:3:3:1:1:1:2:0 # puts WAN and LAN1 into vid 111, LAN1 is tagged on egress
switch --add-vtu-entry 121:3:3:1:1:1:2:0 # puts WAN and LAN1 into vid 121, LAN1 is tagged on egress
switch --add-vtu-entry 131:3:3:1:1:1:2:0 # puts WAN and LAN1 into vid 131, LAN1 is tagged on egress
switch --add-vtu-entry 141:3:3:1:1:1:2:0 # puts WAN and LAN1 into vid 141, LAN1 is tagged on egress
#switch --set-port-default-vid 1:111 # If untagged frames ingress on port 1, place these into VLAN 111 (first VLAN)
#
# VLAN SETTINGS FOR LAN PORT 2
switch --set-port-802dot1q-mode 2:3 # LAN port 2 is secure mode, allows tagged frames only
switch --add-vtu-entry 211:3:1:3:1:1:2:0 # puts WAN and LAN2 into vid 211, LAN2 is tagged on egress
switch --add-vtu-entry 221:3:1:3:1:1:2:0 # puts WAN and LAN2 into vid 221, LAN2 is tagged on egress
switch --add-vtu-entry 231:3:1:3:1:1:2:0 # puts WAN and LAN2 into vid 231, LAN2 is tagged on egress
switch --add-vtu-entry 241:3:1:3:1:1:2:0 # puts WAN and LAN2 into vid 241, LAN2 is tagged on egress
#switch --set-port-default-vid 2:211 # If untagged frames ingress on port 2, place these into VLAN 211 (first VLAN)
#
# VLAN SETTINGS FOR LAN PORT 3
switch --set-port-802dot1q-mode 3:3 # LAN port 3 is secure mode, allows tagged frames only
switch --add-vtu-entry 311:3:1:1:3:1:2:0 # puts WAN and LAN3 into vid 311, LAN3 is tagged on egress
switch --add-vtu-entry 321:3:1:1:3:1:2:0 # puts WAN and LAN3 into vid 321, LAN3 is tagged on egress
switch --add-vtu-entry 331:3:1:1:3:1:2:0 # puts WAN and LAN3 into vid 331, LAN3 is tagged on egress
switch --add-vtu-entry 341:3:1:1:3:1:2:0 # puts WAN and LAN3 into vid 341, LAN3 is tagged on egress
#switch --set-port-default-vid 3:311 # If untagged frames ingress on port 3, place these into VLAN 311 (first VLAN)
#
# VLAN SETTINGS FOR LAN PORT 4, DUMMY VLAN
switch --set-port-802dot1q-mode 4:3 # LAN port 4 is secure mode, allows tagged frames only
Also a combination of tagged/untagged frames that ingress a port is possible. The
following example has VLAN 211 and VLAN 221 defined for WAN and LAN port 1.
VLAN 211 will be tagged egress on WAN and LAN port 1, whereas VLAN 221 will be
tagged egress on WAN and untagged egress on LAN port 1. It is expected that VLAN
211 is tagged ingress on both WAN and LAN port 1, whereas VLAN 221 is tagged
ingress on WAN and untagged ingress on LAN port 1. All other ports are not
member of the VLANs. A management VLAN 951 is defined (untagged), which
enables communication between system operator and CPE for management
purposes (untagged).
Table of contents
Popular Gateway manuals by other brands

ADTRAN
ADTRAN 7310-8 Getting started guide

WELLTECH
WELLTECH FXSO GATEWAY H.323 3701A manual

ZyXEL Communications
ZyXEL Communications DX5510-B0 user guide

ZyXEL Communications
ZyXEL Communications ZyXEL Prestige 310 user guide

Sigenergy
Sigenergy HomeMax TP user manual

Nortel
Nortel Mediatrix 1124 Installation and setup guide