Knowledge Base

VSOL OLT preconfiguration

VSOL OLT initial steps


In this post you'll find step by step instructions for initial OLT configuration and for setting up the IP connectivity of VSOL GPON OLTs such as the V1600G series and the V1600GT. After completing these steps, you'll be ready to connect your OLT to SmartOLT.

The V1600GS-F runs a different command line, so the commands below do not apply to it.

1Connect to the OLT

  • Ethernet / Telnet or SSH: a network cable to the AUX management port of a factory-new OLT, or the network path of an OLT you can already reach.
  • Serial / Console: a serial cable to the CONSOLE port. Use it when you do not know the IP address or remote access does not work.
Ethernet connection (Telnet or SSH)
The factory IP address of the AUX port on a VSOL GPON OLT is 192.168.8.200. If the OLT is already configured, enter its current IP address.
  1. On a factory-new OLT, connect an Ethernet cable to the AUX port. This is the out-of-band management port. It is for management only and cannot carry customer traffic. If the OLT is already reachable over your network, keep the existing cabling.
  2. When you connect directly to the factory IP, configure 192.168.8.1/255.255.255.0 on your PC, or on the MikroTik port connected to the AUX port.
  3. Verify connectivity. You should receive replies.

    ping 192.168.8.200

  4. Connect with PuTTY or from a terminal, using Telnet or SSH.

    Telnet sends everything, including the password, as plain text. Use it only on a direct cable or a trusted management network. In PuTTY, select Telnet and enter the OLT IP address.

    telnet 192.168.8.200

    SSH encrypts the session. It works only if the SSH server is enabled on the OLT and the account is allowed to log in over SSH.

    PuTTY: Enter the OLT IP address in Host Name (or IP address), select SSH, then click Open. Log in with your OLT username and password.

    Terminal (OpenSSH): Run the command below in your computer's terminal.

    ssh admin@192.168.8.200

  5. Log in with the admin account. On a factory-new OLT, use the password supplied by VSOL with the device. On an OLT that is already configured, use its existing account.
    ############################################################
    #                                                          #
    #              Welcome to GPON OLT Platform.               #
    #                                                          #
    #      Press Return to connect and config this system.     #
    #                                                          #
    ############################################################
    User Access Verification
    Login: admin
    Password:
    gpon-olt>

If you cannot log in, or Telnet and SSH do not answer, use the serial console method.

Serial / Console connection
From a PC (PuTTY)
  1. Connect the serial cable supplied with the OLT to the CONSOLE port.
  2. If your PC has no serial port, use a USB-to-serial adapter.
  3. Find the COM port of the adapter in Windows Device Manager (Windows+X), under Ports (COM & LPT).
  4. In PuTTY, select Serial, enter the COM port and the speed. Set the other values under Connection > Serial:
    • Speed: 115200, 57600 or 9600, depending on the OLT model. If the console shows garbled text or nothing, try the next speed.
    • Data bits: 8
    • Parity: None
    • Stop bits: 1
    • Flow control: None
  5. Open the session and press Enter. Log in with the OLT account.
Through a MikroTik

If your MikroTik has an RJ45 CONSOLE port, connect it to the VSOL CONSOLE port with a standard straight-through RJ45 (1:1) patch cable. This is a serial connection, so use the dedicated console ports at both ends. Open a MikroTik Terminal through WinBox or SSH over the network.

  1. Free the serial port and open the serial session:
    /system console disable [find where port=serial0]
    /system serial-terminal serial0
  2. Press Ctrl+A, release the keys, then press R to detect the baud rate automatically. Press Enter to reach the OLT console.

To close the serial session, press Ctrl+A, release the keys, then press Q.

MikroTik serial terminal documentation

Enter privileged and configuration mode

If the prompt ends with ">", enter enable and the enable password. Then enter configure terminal. All the commands below are entered in configuration mode.

gpon-olt>enable
Password:
gpon-olt#configure terminal
gpon-olt(config)#

2Check the OLT model

VSOL GPON OLTs have no boards to confirm. Check the model and the firmware version, because the commands in this guide depend on the firmware:

show version

Then look at the first lines of the configuration:

show running-config

If the configuration starts with frr version, the OLT is a V1600GS-F and the commands below do not apply to it.


3Configure a new management IP address


Select the interface of the management IP

interface aux
ip address 10.200.0.2 255.255.255.0
exit

If you connected over Ethernet using the old IP address, reconnect on the new IP address 10.200.0.2.


Add the default gateway and save the configuration:
ip route 0.0.0.0/0 10.200.0.1
write


The OLT confirms the save:

gpon-olt(config)#write
Configuration saved to /mnt/config/usrcfg.conf

The default route is entered in prefix format, 0.0.0.0/0. If the OLT already has another default route, check it with show running-config before you add this one.

Make sure the default gateway IP address 10.200.0.1 is already configured on your router.

Ping the gateway from the OLT to confirm the route works. You should receive replies.

ping 10.200.0.1

4Create a dedicated username/password

SmartOLT uses this username and password to connect to your OLT. The user needs the ADMIN role.

The enable password must be the same as the login password. SmartOLT has a single password field for VSOL and uses it for both. With different passwords, SmartOLT logs in but cannot enter privileged mode.

user add smartoltusr login-password (enter a strong password)
user role smartoltusr ADMIN enable-password (enter a strong password)
write


5Allow SmartOLT in the login access list

SmartOLT manages the OLT over Telnet or SSH and reads it over SNMP. When the login access list is enabled, the OLT drops every source that a deny rule covers. Some OLTs ship with deny rules for Telnet and SNMP. Check the list:

gpon-olt(config)#show login-access-list
Login Access List : Enable
-------------------------------------------
Action    Protocol    Source IP           Mask
------    --------    ---------           ----
Deny      snmp        0.0.0.0             0.0.0.0
Deny      telnet      0.0.0.0             0.0.0.0

If you connect SmartOLT over SSH, the OLT needs an RSA host key. If show running-config has no crypto key line, create one:

crypto key generate rsa usage-keys modulus 2048
write


If the list shows Disable, or has no deny rule for Telnet, SSH or SNMP, skip this step. Otherwise, permit the network that SmartOLT reaches the OLT from. Use ssh instead of telnet if you connect SmartOLT over SSH.

login-access-list permit telnet [NETWORK] [MASK]
login-access-list permit snmp [NETWORK] [MASK]
write

Add the SNMP rule yourself. SmartOLT tries to add it when it connects, but this does not work on every firmware.


Setup complete

At this stage, your OLT is ready to be interconnected with SmartOLT.

Open your SmartOLT site, go to Settings → OLTs → Add OLT, select VSOL and the connection protocol (Telnet or SSH), fill in the fields displayed, click Test connection, and then Save.



# Other settings (If you use SmartOLT, these are configured automatically, no need to configure them manually):

snmp-server community [READ COMMUNITY] ro
snmp-server community [WRITE COMMUNITY] rw
time zone [OFFSET]
time set year [Y] month [M] day [D] hour [h] minute [m] second [s]
ntp server 216.239.35.4 162.159.200.123
snmp-server host [SMARTOLT TRAP IP] udp-port 162 version 2c community [TRAP COMMUNITY]
alarm onu-port-los trap disable
event name user-login trap disable
event name user-logout trap disable
interface gpon 0/1
no onu auto-learn
exit


SmartOLT turns off ONU auto-learn on every PON port that has it, because SmartOLT authorizes the ONUs itself. When the login access list restricts SNMP, SmartOLT also tries to permit its own address with login-access-list permit snmp.