Hardware Specifications


Vendor/Brand	LEOX
Model	LXT-010S-H
ODM	HiSense
ODM Product Code	LTE3415-SH+
Chipset	Realtek RTL9601CI
Flash	128MB
RAM	32MB
System	Linux 3.18 (Luna SDK 3.3)
HSGMII	Yes
Optics	SC/UPC
IP address	192.168.100.1/24
Web Gui	✅
SSH
Telnet	✅ user `leox`, password `leolabs_7`
Serial	✅
Serial baud	115200
Serial encoding	8-N-1
Form Factor	miniONT SFP

List of partitions

dev	size	erasesize	name
mtd0	00040000	00001000	“boot”
mtd1	00002000	00001000	“env”
mtd2	00002000	00001000	“env2”
mtd3	0003c000	00001000	“config”
mtd4	00300000	00001000	“k0”
mtd5	004c0000	00001000	“r0”
mtd6	00300000	00001000	“k1”
mtd7	004c0000	00001000	“r1”
mtd8	00001000	00001000	“Partition_008”
mtd9	00001000	00001000	“Partition_009”
mtd10	00001000	00001000	“Partition_010”
mtd11	00001000	00001000	“Partition_011”
mtd12	00300000	00001000	“linux”
mtd13	004c0000	00001000	“rootfs”

This stick supports dual boot.

k0 and r0 respectively contain the kernel and firmware of the first image, while k1 and r1 respectively contain the kernel and the firmware of the second one.

Serial

The stick has a TTL 3.3v UART console (configured as 115200 8-N-1) that can be accessed from the top surface. To accept TX line commands, the GND of the TTL adapter should be attached to the stick’s shield:

Note Some USB TTL adapters label TX and RX pins the other way around: try to swap them if the connection doesn’t work.

List firmware version

Note There is a new firmware avaliable from LeoLabs that fixes the 2.5GbE

V3.3.4L3
V3.3.4L4rc1 (Fix 2.5GbE HiSGMII)
V3.3.4L4rc5

Useful files and binaries

Useful files

/var/config/lastgood.xml - Contains the user portion of the configuration
/tmp/omcilog - OMCI messages logs (must be enabeled, see below)

Useful binaries

/etc/scripts/flash - Used to manipulate the config files in a somewhat safe manner
xmlconfig - Used for low-level manipulation of the XML config files. Called by /etc/scripts/flash
nv - Used to manipulate nvram storage, including persistent config entries via nv setenv/nv getenv
omcicli - Used to interact with the running OMCI daemon
omci_app - The OMCI daemon
diag - Used to run low-level diagnostics commands on the stick

GPON ONU status

Get the operational status of the ONU

diag gpon get onu-state

Querying a particular OMCI ME

# omcicli mib get MIB_IDX

Getting/Setting Speed LAN Mode

Note You need firmware V3.3.4L4rc1 or higher. Before editing the speed make sure your hardware supports it. If you try to use any mode not listed here, stick will default to mode 1.

To change the link mode use this command:

# /etc/scripts/flash get LAN_SDS_MODE
LAN_SDS_MODE=0
# /etc/scripts/flash set LAN_SDS_MODE 1

Value	`cat /proc/kmsg`	Mode	Behavior
1	`<4>change mode to 1(Fiber 1G)`	`FIBER`	1GbaseX with auto-neg on
4	`<4>change mode to 4(HiSGMII PHY)`	`TP MII`	2.5Gb PHY
8	`<4>change mode to 8(HISGMII Force)`	`TP`	2500baseT with auto-neg off

GPON/OMCI settings

Getting/Setting ONU GPON Serial Number

# /etc/scripts/flash get GPON_SN
GPON_SN=TMBB00000000
# /etc/scripts/flash set GPON_SN TMBB0A1B2C3D

Getting/Setting ONU GPON PLOAM password

Info The PLOAM password is stored in ASCII format

# /etc/scripts/flash get GPON_PLOAM_PASSWD
GPON_PLOAM_PASSWD=AAAAAAAAAA
# /etc/scripts/flash set GPON_PLOAM_PASSWD AAAAAAAAAA

Getting/Setting OMCI software version (ME 7)

Note This needs the OMCI_OLT_MODE value to be set to 21. This will force to use your own settings from the XML file, but this is a hack and causes sigsegv of /bin/checkomci.

# nv setenv sw_custom_version0 YOURFIRSTSWVER
# nv setenv sw_custom_version1 YOURSECONDSWVER

Getting/Setting OMCI hardware version (ME 256)

# /etc/scripts/flash get HW_HWVER
HW_HWVER=V2.0
# /etc/scripts/flash set HW_HWVER MYHWVERSION

Getting/Setting OMCI vendor ID (ME 256)

# /etc/scripts/flash get PON_VENDOR_ID  
PON_VENDOR_ID=ZTEG
# /etc/scripts/flash set PON_VENDOR_ID HWTC

Getting/Setting OMCI equipment ID (ME 257)

# /etc/scripts/flash get GPON_ONU_MODEL
GPON_ONU_MODEL=DFP-34X-2C2
# /etc/scripts/flash set GPON_ONU_MODEL DFP-34X-XXX

Getting/Setting OMCI OLT Mode and Fake OMCI

Configure how ONT Stick handle OMCI from OLT:

# /etc/scripts/flash get OMCI_OLT_MODE
OMCI_OLT_MODE=1
# /etc/scripts/flash set OMCI_OLT_MODE 2

Value	Note	OMCI Information
0	Default Mode	Stock, some value are cannot be change
1	Huawei OLT Mode	Huawei MA5671a
2	ZTE OLT Mode	ZTE
3	Customized Mode	Custom Software/Hardware Version, OMCC, etc…
21	Owerflow Mode	Custom Software/Hardware Version, OMCC, etc… (this is a hack and causes sigsegv of `/bin/checkomci`)

Some Fiber Vendor/Wholesale/ISP have explicit LAN Port Number provisioning or proprietary OMCI that ONT Stick cant not understand, this will make ONT Stick reply OK whatever OMCI OLT throw at.

0 = Disable, 1 = Enable, Default is 0

# /etc/scripts/flash get OMCI_FAKE_OK
OMCI_FAKE_OK=0
# /etc/scripts/flash set OMCI_FAKE_OK 1

Advanced settings

Setting management IP

# /etc/scripts/flash get LAN_IP_ADDR
LAN_IP_ADDR=192.168.2.1
# /etc/scripts/flash set LAN_IP_ADDR 192.168.1.1

Getting/Setting the L2 Bridge MTU

Note Settings given via diag are not permanent after reboot

Getting/Setting the MTU of the L2 bridge

# diag switch get max-pkt-len port all 
Port Speed 
---------- 
0 1538 
2 2031 
# diag switch set max-pkt-len port all length 2000

Checking the currently active image

# nv getenv sw_active
sw_active=1
# nv getenv sw_version0
sw_version0=V1_7_8_210412
# nv getenv sw_version1
sw_version1=V1_7_8_210412

Booting to a different image

# nv setenv sw_commit 0|1
# reboot

Known Bugs

The stock firmware doesn’t work @ 2.5GbE. There is a new firmware avaliable from LeoLabs that fixes this issue.