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

Fortigate 80F issue with shared-port speed 100 Mbps

Hello everyone!

I am having this problem with my FGT 80F release 7.6.2F build 3462, using a Fortinet SFP model FN-TRAN-SX.
Below is my environment:
- The device connected on the WAN 2 interface only supports speed 100 full.
- Whether connected via copper or fiber the WAN 2 interface is always set speed to 100 full.

- The device connected on the WAN 2 has only one fiber NIC. The connection to WAN2 copper interface is made through media converter.

Fault description

 

In the current release, the device connected on WAN2 is only seen if it is connected in copper, while the WAN2 interface in fiber remains switched off even if we disconnect the copper cable in the branch, following output when only fiber cable is connection on WAN2 interface

 

FGT-80F-1 # diagnose hardware shared-port wan2

Get nic name: wan2 medium type 2, Copper

 

even in the case of both cables disconnected on WAN2 the output of the following command does not change, as per your documentation (ART ID 333930) we expected “AUTO” as output.
Instead we have this output:

 

FGT80F-1 # diagnose hardware shared-port wan2

Get nic name: wan2 medium type 2, Copper

 

Instead, by downgrading the device to release 7.6.0F (3401), the WAN2 Fiber interface (set speed 100full) goes up correctly but does not communicate with the device connected to it.

Connecting the copper cable in 7.6.0, it is not seen by the device at all.

From official Fortinet documentation it appears that the BUG ID 1075585 (Shared copper WAN1 and WAN2 ports remain down when the interface speed is set to 100full) has been fixed as of version 7.6.1

 

Thank everyone in advance!

FortiGate

8 REPLIES 8
HarryTran
Staff
Staff

Hi Mandalorian,
Thanks for your information.
I'll double check.
Regards,
Harry

Mandalorian
New Contributor III

Hi @HarryTran,
We look forward to your feedback.
Let me know if you need further information.

Best regards

HarryTran

Hi Mandalorian,
The issue has been raised to relevant team for investigation.

Thanks again for your information.


Regards,
Harry

Mandalorian

Hi @HarryTran,
Have you had any updates from the team ?

Best Regards

HarryTran

Hi @Mandalorian,
Hereafter is for your infor:

In 7.6.1 or later, kindly try below.
1. Make sure config the device port which is connected to FGT with 100full (not auto)
2. Set the SFP WAN1 or SFP WAN2 with 100full.
config system interface
edit "wan2"
...
set speed 100full
next
end
3. Change the SFP port into Fiber mode:
FortiGate-80F # diagnose hardware shared-port wan2 fiber
Then the interface should be UP.
Note: if you reboot the FGT or change the speed of the SFP port, you should run above command again.
Please let me know the result.

Regards,
Harry

HarryTran

Hi @Mandalorian,

Below slitch may help to set the interface back to fiber mode if the FGT is rebooted unexpectedly (example power outage).

FortiGate-80F # config system automation-action
FortiGate-80F (automation-action) # edit "Set_Fiber_Mode"
FortiGate-80F (Set_Fiber_Mode) # show
config system automation-action
    edit "Set_Fiber_Mode"
        set action-type cli-script
        set minimum-interval 10
        set script "diagnose hardware shared-port wan2 fiber"
        set accprofile "super_admin"
    next
end

FortiGate-80F # config system automation-trigger
FortiGate-80F (automation-trigger) # edit "FortiGate started"
FortiGate-80F (FortiGate started) # show
config system automation-trigger
    edit "FortiGate started"
        set event-type event-log
        set logid 32009
    next
end

FortiGate-80F # config system automation-stitch
FortiGate-80F (automation-stitch) # edit "WAN2_Fiber_Reboot"
FortiGate-80F (WAN2_Fiber_Reboot) # show
config system automation-stitch
    edit "WAN2_Fiber_Reboot"
        set trigger "FortiGate started"
        config actions
            edit 1
                set action "Set_Fiber_Mode"
                set delay 10
                set required enable
            next
        end
    next
end

 Regards,

   Harry

Mandalorian

Hi @HarryTran thanks for response
Ss soon as we have a chance, we will test what you have indicated.

If I understand correctly, any change in speed between the device and the Fortigate or any reboot or power failure will result in a disruption ?

if your proposed solution works, is there a way to permanently save the fiber connection configuration between Fortigate and device ?

Best Regards

HarryTran

Hi @Mandalorian,

Hereafter is response to your concerns:
If I understand correctly, any change in speed between the device and the Fortigate or any reboot or power failure will result in a disruption ?
--> Yes.
if your proposed solution works, is there a way to permanently save the fiber connection configuration between Fortigate and device ?
--> Please try case 2 in this tip, when the interface is down, the slitch will automatically reconfigure the interface as you want. Note that this slitch requires local log.

Regards,

Harry.

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