OLTs

The router manages Huawei MA5600T-family OLTs (MA5608T, MA5680T, MA5683T). It reaches them through the licensed OLT driver: over SNMP where the driver can, over the OLT’s CLI (telnet or SSH) otherwise.

Register an OLT

dtvsol olt add olt-1 10.10.0.2 admin --svlan 1000

• olt-1 is your name for it. 10.10.0.2 is its management address, admin the login.
• The password is asked without echo (or give --pass). It is stored encrypted, bound to this machine.
• The login is tested before anything is stored.
• --svlan is this router’s S-VLAN on the OLT. See Concepts.
• --ssh uses SSH instead of telnet. --port sets a non-standard port.
• --iptv <vlan> sets the OLT’s IPTV VLAN, used by services added with --iptv.

If the OLT belongs to another company and you rent the last mile on it, add --operator. The router then touches only its own S-VLAN and profiles, does not back the OLT up, and refuses to delete or reboot ONTs that carry another operator’s traffic. --owner marks an OLT as yours again.

For the driver’s SNMP access, give the credentials in a file, never on the command line:

cat > /root/olt-1.snmp <<'EOF'
user=dtvsol
auth=sha
auth_pass=<auth-password>
priv=aes
priv_pass=<priv-password>
EOF
dtvsol olt set olt-1 --snmp-file /root/olt-1.snmp
rm /root/olt-1.snmp

Manage the registry:

dtvsol olt list
dtvsol olt set olt-1 --comment "POP 1, rack 2"
dtvsol olt del olt-1

When one OLT is registered, every dtvsol olt command uses it. With several, add --olt <name>.

When you add an OLT that is yours, the router also points the OLT’s clock at itself (chrony on the management link). Check it with dtvsol ntp.

A baseline for a new OLT

dtvsol olt init reads the OLT’s boards and generates a whole baseline: system name, NTP, the S-VLAN on the uplinks, the IPTV VLAN, ONT autofind on every PON port, the plans’ profiles, and the router-side commands for the S-VLAN and one C-VLAN per PON port. It is a dry run by default:

dtvsol olt init --olt olt-1 --svlan 1000 --iptv 300
dtvsol olt init --olt olt-1 --svlan 1000 --iptv 300 --apply

Read the dry run’s output before you add --apply.

Push the plans

Every speed plan becomes profiles and rate tables on every registered OLT. The router does this by itself every 15 minutes and after every plan change. To run it now:

dtvsol olt sync --dry-run
dtvsol olt sync

Unused dtvsol-* objects are removed. Objects still bound to an ONT are left with a note.

Saving and backups

You do not need to save the OLT by hand. After the router changes an OLT, a timer (dtvsol-olt-maint.timer) saves it to flash once it has been quiet, and backs up its configuration. The backups are kept as a history, and you can see what changed:

dtvsol olt backup           # back up now
dtvsol olt backups          # the history, and whether each change is saved to flash
dtvsol olt diff             # what changed; or give one or two backups from the history

dtvsol olt save saves at once.

Reading the OLT

dtvsol olt info             # product, version, uptime, boards, clock
dtvsol olt autofind         # ONTs connected but not registered
dtvsol olt onus 0/1/0       # registered ONTs on a port
dtvsol olt vlans            # VLANs and the VLANs on every uplink
dtvsol olt sp               # service-ports
dtvsol olt profiles         # DBA, line and service profiles
dtvsol olt ont optical 0/1/0 7    # an ONT's light, temperature and voltage
dtvsol olt run "display board 0"  # any display command

Changing the OLT by hand

Most changes happen through services. For special cases:

dtvsol olt vlan add 300 uplinks 0/3/0 desc "IPTV"
dtvsol olt uplink add 300 0/3/1
dtvsol olt ont desc 0/1/0 7 "Example Customer"
dtvsol olt ont reboot 0/1/0 7
dtvsol olt exec "<command>" "<command>"

olt exec runs configuration commands in order and stops at the first one the OLT refuses.

Caution

olt exec sends what you type to the OLT. Check the commands on a test port first.

Every command the router sends to an OLT, with the OLT’s reply, is visible live in the monitor’s Console.

The collector and fiber warnings

Every 5 minutes the collector reads each registered OLT (over SNMP, never with a CLI login):

• each ONT’s fiber levels and state, and when it went offline and why,
• each port’s traffic counters, and each ONT’s own counters and line errors.

The monitor’s OLT tab draws from this, and the collector raises fiber warnings. The ONT’s received level is judged like this:

Received level	Meaning
above −8 dBm	too strong: add attenuation
−8 to −25 dBm	good
−25 to −27 dBm	weak: check splices
below −27 dBm	too weak

It also warns when:

• an ONT’s level is more than 2 dB lower than in the last 7 days,
• an ONT is losing data (uncorrected FEC blocks) or has many BIP errors,
• several ONTs on one port go offline together (a splitter branch?),
• every ONT on a port is offline (the feeder fiber?).

When five or more ONTs on a port share a problem, it is reported as one line for the port. ONTs offline by fiber loss for more than 7 days are listed so you can delete them if the customers are gone.

See the warnings with dtvsol alerts, in the alarm register, or in the monitor.

Checking the OLT against the router

dtvsol doctor

With an OLT registered, the doctor also checks the OLT against the router’s records: the S-VLAN, the uplinks, Option 82, and every service’s ONT and service-port.