The objective of this step is to enable your device to reach mfusion for monitoring and orchestration.
If you're using RansNet cloud hosted mfusion, by default, the device will automatically attempt to register to cloud mfusion (portal.ransnet.com) once it's online. 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 use different baudrate. Please use RJ45 serial cable with below table for baudrate setting:
Series Baudrate----------------------------------------CMG/HSG 19200HSA/UA/XE/UAP 115200Alternatively, eg. if you don't have serial console cable, RansNet devices by default allows SSHv2 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) after device is onboarded to mfusion.
If you're using static WAN connection, user below CLI to configure static IP for WAN interface and default gateway (replace the interface and default gateway IP with your provider's setting).
mbox> enableEnter enable password:mbox# configurembox(config-if-eth0)#interface eth0mbox(config-if-eth0)#enablembox(config-if-eth0)#ip address 200.13.198.166/30mbox(config-if-eth0)#exitmbox(config)#ip name-server 8.8.8.8 8.8.4.4mbox(config)#ip default-gateway 200.13.198.165mbox(config)#endmbox# write memoryUse below CLI "ip host portal.ransnet.com" command to point to your own mfusion IP, and make sure your device is able to ping to mfusion IP.
mbox> enableEnter enable password:mbox# configurembox(config)# ip host portal.ransnet.com 192.168.1.1mbox(config)#mbox(config)# do ping portal.ransnet.comPING portal.ransnet.com (192.168.1.1): 56 data bytes64 bytes from 192.168.1.1: seq=0 ttl=58 time=2.865 ms64 bytes from 192.168.1.1: seq=1 ttl=58 time=2.936 ms64 bytes from 192.168.1.1: seq=2 ttl=58 time=2.790 ms64 bytes from 192.168.1.1: seq=3 ttl=58 time=2.640 ms64 bytes from 192.168.1.1: seq=4 ttl=58 time=2.788 msRansNet devices come with self-protection mechanism - each time when a configuration is pushed from mfusion, the device will backup current working config before applying the new change. If you made mistake and pushed wrong configuration to your device, and caused the device to lose remote connectivity, the device will reboot within 15 minutes and restore back the last working config, so that you can review your previous changes and rectify the problem without losing the remote connectivity.
However, in some very rare situations, ex. device hang due to over utilization or power issue, and you've completely lost the ability to manage the device remotely. You can ask onsite staff to perform factory reset to recover the device.
Reset HSA/UA/XE/UAP to factory default
Press and hold the “Reset” button for more than 10 seconds and release the “Reset” button (it will re-flash to default firmware and reboot)
Wait for 3minutes (the device will boot up with default configuration and automatically register back to mfusion-portal.ransnet.com)
Now you can double check your device configuration on mfusion orchestrator. Once the device is back online again on mfusion, resync your configuration (it will reboot again and boot up with new working configuration).
Reset HSG Database
CMG/HSG series do not come with reset button, and usually just a power cycle of the hardware will recover. But there're cases that you need to rest database due to DB corruption. NOTE: make sure you've downloaded your DB backup before performing below steps.
Console/SSH into the device
Login to privileged mode (‘enable’ login credential)
Type ‘write erase’