Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
milanone
New Contributor

FGT-50G-DSL VDSL sample config with CETIN provider

I am just sharing the FGT-50G VDSL config for other VDSL users connected via CETIN (the Czech Rep. provider). The config differs a bit in comparison to older xDSL FGT models. And Fortinet documentation does not provide useful samples. Data (traffic) via 802.1Q VLAN that is specific for CR enviromnemt. 

FortiGate-50G-DSL #

FortiGate-50G-DSL # get system status
Version: FortiGate-50G-DSL v7.0.17,build7592,250125 (GA.M)

FortiGate-50G-DSL # show
#config-version=FG50GD-7.0.17-FW-build0682-250125:opmode=1:vdom=0:user=admin

config system interface
edit "dsl"
set vdom "root"
set type physical
set alias "isp-physical"
set phy-mode auto
set tc-mode ptm
set annex b
set profiles 17a 30a
set lldp-reception enable
set role wan
set snmp-index 6

edit "vlan848"
set vdom "root"
set mode pppoe
set allowaccess ping
set alias "isp-logical"
set snmp-index 12
set username "xDSL"
set password ENC <pass>==
set interface "dsl"
set vlanid 848
end

FortiGate-50G-DSL #

FortiGate-50G-DSL # get system dsl status
DSL Module Status: [up]
DSL WAN IP: [213.29.50.229]
DSL Link Status: [Showtime]
DSL Standard: [ITU G.993.5(G.Vectoring),G.998.]
DSL Annex Type: [ANNEX_B]
DSL Transfer Mode: [PTM]

FortiGate-50G-DSL #

FortiGate-50G-DSL # get system interface physical dsl
== [onboard]
==[dsl]
mode: static
ip: 0.0.0.0 0.0.0.0
ipv6: ::/0
status: up
speed: 0Mbps (Duplex: half)
FEC: none
FEC_cap: none

FortiGate-50G-DSL #

FortiGate-50G-DSL # diagnose dsl
reset reset dsl [Take 0-1 arg(s)]
show Show DSL module info.
log DSL related logs.
FortiGate-50G-DSL #
FortiGate-50G-DSL # diagnose dsl show
firm-info Show DSL module firmware version.
dsl-info Show basic xDSL information.
traffic-stats Show DSL traffic statistics.
FortiGate-50G-DSL #
FortiGate-50G-DSL # diagnose dsl show firm-info
FwVer:5.12.23.107_B_A60901 HwVer:T14.F7_0.0

FortiGate-50G-DSL #

FortiGate-50G-DSL # diagnose dsl show dsl-info
DSL Module Status: [up]
DSL WAN IP: [213.29.50.229]
DSL Link Status: [Showtime]
DSL Standard: [ITU G.993.5(G.Vectoring),G.998.]
DSL Annex Type: [ANNEX_B]
DSL Transfer Mode: [PTM]
==================================================
Upstream Downstream
-----------------------------------------------------
Attain Data Rate (kbps): 51021 147247
Noise Margin (dB): 20.5 7.3
Transmit Power (dBm): 6.5 12.0
Attenuation (dB): 1.0 7.9

FortiGate-50G-DSL #
FortiGate-50G-DSL # diagnose dsl show traffic-stats
RX frame_cnt: 0000000003554b0e, RX frame_byte: 00000008feaddcad
RX broadcast: 0000000000000000, RX multicast: 0000000000000000
RX oversize: 00000000002af3e4, RX undersize: 0000000000053b3a
RX drop_cnt: 0000000000000000, RX crc_error: 0000000000010177
RX fragment: 0000000000053ae3, RX jabber: 000000000000b0ee
RX less_64: 0000000000053b3a, RX eq_64: 0000000000013440
RX 65_to_127: 00000000011fa530, RX 128_to_255: 0000000000580efc
RX 256_to_511: 00000000001d870a, RX 512_to_1023: 00000000000845b8
RX 1024_to_1518: 00000000001d870a, RX more_1518: 00000000002af3e4
================================================================
TX frame_cnt: 00000000025411b9, TX frame_byte: 00000004e25fa157
TX broadcast: 0000000000000001, TX multicast: 000000000000245d
TX drop_cnt: 0000000000000000, TX less_64: 0000000000000000
TX eq_64: 00000000000130a0, TX 65_to_127: 0000000000df2e91
TX 128_to_255: 00000000003ba975, TX 256_to_511: 0000000000219a96
TX 512_to_1023: 000000000035814e, TX 1024_to_1518: 0000000000219a96
TX more_1518: 00000000000034ca

FortiGate-50G-DSL #
FortiGate-50G-DSL # diagnose dsl log display
[2025-05-29 20:14:49] client_initialization(98): client_initialization: reset Client
[2025-05-29 20:14:55] EN7517_pll_setting(55): config EN7517 pll setting
[2025-05-29 20:14:55] mdio_msg_handler_bp1(156): start writing ddr_cal.bin to client!
[2025-05-29 20:14:56] mdio_msg_handler_bp1(168): write fw finished !
[2025-05-29 20:14:56] mdio_msg_handler_bp1(203): client boot into ddr_cal!
[2025-05-29 20:14:56] host_bp2(773): host_bp2 start_addr = 1000000
[2025-05-29 20:14:56] mdio_msg_handler_bp2(640): start writing iNIC.bin to client!
[2025-05-29 20:14:56] mdio_msg_handler_bp2(642): start_addr = 1000000
[2025-05-29 20:14:56] mdio_msg_handler_bp2(644): IMAGE_ADDR = 1000000
[2025-05-29 20:14:57] mdio_msg_handler_bp2(640): start writing iNIC.bin to client!
[2025-05-29 20:14:57] mdio_msg_handler_bp2(642): start_addr = 1000000
[2025-05-29 20:14:57] mdio_msg_handler_bp2(644): IMAGE_ADDR = 1000000
[2025-05-29 20:14:58] mdio_msg_handler_bp2(662): write iNIC.bin finished !
[2025-05-29 20:14:58] mdio_msg_handler_bp2(676): client boot into iNIC.bin!
[2025-05-29 20:15:01] iNIC_server(755): start iNIC server!
[2025-05-29 20:15:01] rom_rcv_notify(226):
[2025-05-29 20:15:02] rom_rcv_rrq(327):
[2025-05-29 20:15:02] event_recv(58): start heartbeat
[2025-05-29 20:15:25] event_recv(95): heartbeat negotiation succeeds !
[2025-05-29 20:15:25] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:15:32] xdsl_config_sync(200): Start sync, config_change=3f
[2025-05-29 20:15:33] xdsl_config_sync(206): ret=0, intended to change dsl mode from [] to [Multimode]
[2025-05-29 20:15:33] xdsl_config_sync(214): ret=0, intended to change dsl annex from [] to [ANNEX_B]
[2025-05-29 20:15:33] xdsl_config_sync(222): ret=0, intended to change allowd vdsl2 profiles to [180]
[2025-05-29 20:15:34] xdsl_config_sync(231): ret=0, intended to change wan transmission mode from [] to [PTM]
[2025-05-29 20:15:39] hsm_renew_intf_ip(197): Release intf dsl dhcp/pppoe.
[2025-05-29 20:15:39] hsm_renew_intf_ip(197): Release intf vlan848 dhcp/pppoe.
[2025-05-29 20:16:15] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:16:20] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:17:38] xdsl_config_sync(200): Start sync, config_change=8
[2025-05-29 20:17:38] xdsl_config_sync(222): ret=0, intended to change allowd vdsl2 profiles to [80]
[2025-05-29 20:18:05] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:18:12] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:18:15] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:18:21] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:18:25] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:18:30] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:18:35] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:18:40] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:18:45] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:18:50] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:19:00] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:19:07] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:19:10] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:19:16] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:19:20] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:19:25] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:19:30] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:19:42] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:19:45] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:19:51] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:19:55] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:20:00] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:20:05] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:20:10] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:20:20] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:20:27] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:20:30] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:20:35] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:20:40] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:20:45] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:20:50] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:20:55] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:21:00] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:21:06] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:21:10] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:21:15] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:21:20] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:21:25] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:21:35] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:21:41] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:21:45] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:21:51] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:21:55] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:22:00] event_recv(104): EN7517 WAN Change:01
[2025-05-29 20:22:08] xdsl_config_sync(200): Start sync, config_change=8
[2025-05-29 20:22:08] xdsl_config_sync(222): ret=0, intended to change allowd vdsl2 profiles to [c0]
[2025-05-29 20:22:25] event_recv(104): EN7517 WAN Change:40
[2025-05-29 20:22:30] event_recv(104): EN7517 WAN Change:80
[2025-05-29 20:23:15] event_recv(104): EN7517 WAN Change:04
[2025-05-29 20:23:16] hsm_renew_intf_ip(204): Renew intf dsl dhcp/pppoe.
[2025-05-29 20:23:16] hsm_renew_intf_ip(204): Renew intf vlan848 dhcp/pppoe.

FortiGate-50G-DSL #

 

Note: some issues found with "set profiles", "17a" is necessary to get the link up

4 REPLIES 4
Stephen_G
Moderator
Moderator

Hello,


Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

 

If anyone has any advice to contribute, please do!


Thanks,

Stephen - Fortinet Community Team
Stephen_G
Moderator
Moderator

Hello,

 

We are still looking for someone to help you.

We will come back to you ASAP.


Regards,

Stephen - Fortinet Community Team
milanone

It is just a functional sample and experience shared to others. No help is needed.

Stephen_G

Hi milanone,

 

That's completely my mistake - I misunderstood your post. Apologies, and thank you for sharing this!

Stephen - Fortinet Community Team
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors