Enable Huawei LTE modem

Forum|Forum|13 years ago
April 3, 2013
3 replies
17161 views

Hello, we are trying to enable a Huawei LTE modem as a backup line with a FGT-60C running FortiOS 4.3.12. The package of the LTE USB stick was labeled " Huawei E392" - which is a device supported by Fortinet. Unfortunately internaly the stick is detected as " Huawei E392-u12" which is NOT supported by Fortinet. Also creating a custom config did not work, when running the command " diag sys modem detect" we always get the message " modem is not attached" . Here are our parameters for the custom config: id = 1 vendor = Huawei model = E392-u12 vendor-id = 12d1 product-id = 151a class-id = ? init-string = ? Any hint for getting this device running is welcome Sincerely Harald

Best answer by Adrian_Lewis

In case you' re still having issues or someone else finds this I' ve managed to use the same modem and get it working. The E392 that is supported as of 06/09/13 is not the same one as you discovered but is one with a vendor and product ID of 12d1:1505. I created two custom 3g modem definitions, one for when it appears to the system as a CD ROM (as when you first plug it into a Windows laptop before you install the drivers). This one has an init-string which makes the device switch on its serial ports and change product-id. they are as follows:

config system 3g-modem custom      edit 1          set vendor " Huawei"           set model " E392u"           set vendor-id 12d1          set product-id 151a          set init-string " 55534243123456780000000000000011062000000100000000000000000000"       next      edit 2          set vendor " Huawei"           set model " E392u"           set vendor-id 12d1          set product-id 151b      next  end

Hope this helps someone at least. FYI - this was done and successfully tested on 5.0.4.

Carl_Wallmark

New Member

Hi Harald, This thread might give you some hints on what to do: https://forum.fortinet.com/FindPost/93930

Adrian_LewisAnswer

New Member

In case you' re still having issues or someone else finds this I' ve managed to use the same modem and get it working. The E392 that is supported as of 06/09/13 is not the same one as you discovered but is one with a vendor and product ID of 12d1:1505. I created two custom 3g modem definitions, one for when it appears to the system as a CD ROM (as when you first plug it into a Windows laptop before you install the drivers). This one has an init-string which makes the device switch on its serial ports and change product-id. they are as follows:

config system 3g-modem custom      edit 1          set vendor " Huawei"           set model " E392u"           set vendor-id 12d1          set product-id 151a          set init-string " 55534243123456780000000000000011062000000100000000000000000000"       next      edit 2          set vendor " Huawei"           set model " E392u"           set vendor-id 12d1          set product-id 151b      next  end

Hope this helps someone at least. FYI - this was done and successfully tested on 5.0.4.

steventan

New Member

Adrian Lewis wrote:
In case you' re still having issues or someone else finds this I' ve managed to use the same modem and get it working. The E392 that is supported as of 06/09/13 is not the same one as you discovered but is one with a vendor and product ID of 12d1:1505. I created two custom 3g modem definitions, one for when it appears to the system as a CD ROM (as when you first plug it into a Windows laptop before you install the drivers). This one has an init-string which makes the device switch on its serial ports and change product-id. they are as follows:
config system 3g-modem custom
 edit 1
 set vendor " Huawei" 
 set model " E392u" 
 set vendor-id 12d1
 set product-id 151a
 set init-string " 55534243123456780000000000000011062000000100000000000000000000" 
 next
 edit 2
 set vendor " Huawei" 
 set model " E392u" 
 set vendor-id 12d1
 set product-id 151b
 next
end
Hope this helps someone at least. FYI - this was done and successfully tested on 5.0.4.

Hi Adrian, just wondering how did you come up with the init-string?

Sign up

Login with SSO

Login to the community

Login with SSO