This is an optional preparation step, before we start provisioning and managing a RansNet device.
RansNet appliances will auto call-home to mfusion for zero-touch-provisioning. By default, once the device is online through WAN connection or SIM (eg. either WAN port is plugged to a DHCP/dynamic Internet link, or an Internet SIM is inserted), the device will attempt to contact mfusion. If it's already pre-provisioned on mfusion, it will be automatically monitored and ready for orchestration.
If you're using RansNet cloud mfusion to manage the device (via portal.ransnet.com), bootstrapping is not necessary. You can proceed to "Device Provisioning" section.
However, if you're using an on-premise/private mfusion deployment, or using static WAN connection, you need to tell the device how to reach to its mfusion. That's where bootstrapping is required. You can do it via CLI commands.
Before we start using console or SSH, it's useful to understand how RansNet command line interface (CLI) works.
RansNet CLI provides an intuitive way to bootstrap RansNet devices, and you may also want to use CLI to configure advanced features for complex deployment scenarios or perform in-depth troubleshooting for advanced engineers.
CLI can only be accessed from serial console or SSH.
RansNet CLI comes in 4 operating modes:
There’re some interesting short-cut keys enable you quickly navigate through CLI.
All RansNet devices some with console port for offline access, but different series of hardware come with different baudrate. Please use RJ45 serial cable with below table for baudrate setting:
Series Baudrate
CMG/HSG 19200
HSA/UA/XE/UAP 115200
Alternatively, eg. if you don't have serial console cable, RansNet devices by default allows SSH access from LAN.
For CMG/HSG series, by default, you can use an ethernet cable to connect your PC to eth2-Port3 (Management Port). PC will be given DHCP IP 10.10.10.x/24, then you can SSH to 10.10.10.1 (default gateway IP).
For HSA/UA/XE series, connect your PC to LAN1, and after receiving DHCP IP, SSH to 192.168.8.1.
It's highly recommended to remove default SSH firewall rules (to disable SSH access) before the device goes live.
If you're using RansNet cloud hosted mfusion, by default, the device will attempt to register to cloud mfusion (portal.ransnet.com) once it's online; If you're using on-premise or private mfusion, it's necessary to tell your device where to look for mfusion IP. This is the key objective of device bootstrapping.
Use below CLI "ip host portal.ransnet.com" command to point to your own mfusion IP, and configure the necessary interface and routing commands to make sure your device is able to ping to mfusion IP.
mbox> enable
Enter enable password:
mbox# configure
mbox(config)# ip host portal.ransnet.com 192.168.1.1
mbox(config)#
mbox(config)# do ping portal.ransnet.com
PING portal.ransnet.com (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: seq=0 ttl=58 time=2.865 ms
64 bytes from 192.168.1.1: seq=1 ttl=58 time=2.936 ms
64 bytes from 192.168.1.1: seq=2 ttl=58 time=2.790 ms
64 bytes from 192.168.1.1: seq=3 ttl=58 time=2.640 ms
64 bytes from 192.168.1.1: seq=4 ttl=58 time=2.788 ms
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.640/2.803/2.936 ms
mbox(config)# end
mbox# write memory