Contents

Management access to mbox appliances

Getting SSH Access (CMG/HSG)

**Image 1** : CMG / HSG Default Interface Setting

Initially to connect to HSG/CMG, the user can SSH to device by connecting an Ethernet cable to Tth2 (Management Port) and PC, the port is configured with IP 10.10.10.1/24 and also to issue DHCP IP to external management PC.

Once management PC gets a DHCP IP (eg. 10.10.10.x/24), administrator can SSH to 10.10.10.1 and log in with the default ‘support’ account and the ‘enable’ login credential (Contact RansNet Account Manager).

For web access to the Management UI of HSG, the user needs to enable the ‘Security radius‘ command in the Console Terminal, See details in Console Access To Appliances and configure the below code. Then use the browser to connect, eg. https://10.10.10.1

login as: support
support@mbox's password:
mbox> enable
Enter enable password:
mbox#
mbox# configure
mbox(config)# security radius-server
mbox(config-radius)# start

Getting Console Access (CMG/HSG/UA/HSA/MAP)

To access mbox CLI, you can also use the serial console with DB9 female connector. Find below the mbox product and the Connection type cables

S/N	Host	Cable Type	Baud rate
01.	HSG	Serial (Rj45 to db9 serial console cable + USB to Serial 9-Pin Converter Cable or USB to RJ45 Console Cable)	19200
02.	CMG	Serial (db9 female to female serial console cable + USB to Serial 9-Pin Converter Cable)	19200
03.	HSA / UA	Serial (Rj45 to db9 serial console cable + USB to Serial 9-Pin Converter Cable / USB to RJ45 Console Cable)	115200
04.	MAP	Serial (Rj45 to db9 serial console cable + USB to Serial 9-Pin Converter Cable / USB to RJ45 Console Cable)	9600

Table 1 : Host Baud Rate (Product)

NOTE

HSG / CMG Host’s ethernet port ‘ETH2’ is pre-configured with IP address 10.10.10.1/24, by this you can access mbox using SSH.

Understanding Command Line Interface

You may want to access mbox Command Line Interface (CLI) to configure advanced features for complex deployment scenarios or perform in-depth troubleshooting for advanced engineers.

CLI provides an intuitive way to manage mbox configurations. There are 4 main modes:

S.no	Commands	Description
01.	`mbox>`	Unprivileged (read-only) mode. This is the default mode upon initial login (eg. login with support, through console or SSH)
02.	`mbox#`	Privileged (enabled) mode. Under read-only mode, enter “enable”, followed by an ‘enable’ password to enter enable mode.
03.	`mbox (config)#`	Configure mode. This is where we start our configuration. Type “configure” under enable mode.
04.	`mbox (config-xx)#`	Context mode. This is where you configure individual parameters for each config, eg. interface settings, DHCP scope, etc.

Table 1: CLI Modes

mbox CLI shortcuts:

There’re some interesting short-cut keys you can use to make your work easy and fast with mbox CLI.

S.No	Shortcut Keys	Description
01.	Ctrl + A	Move to Begin of the Line
02.	Ctrl + E	Move to End of the Line
03.	Ctrl + C	Clear current line
04.	Ctrl + D	Delete Character on the right of the cursor
05.	Ctrl + K	Delete everything on the right of the cursor
06.	Ctrl + U	Delete everything on the left of the cursor
07.	Ctrl + W	Delete Words on the left of the cursor
08.	Ctrl + L	Clear the screen
09.	?	shows the list of available commands
10.	no	to remove existing commands
11.	tab/space	Auto completes current command (enter enough character to make it unique)

Table 2: CLI Handy Keys

Understanding to insert SIM into HSA / UA

HSA devices support Micro SIM, Its 15mm in Length, 12mm in Width and .76mm in height
Info : Once you insert the Micro SIM, the device needs to be rebooted.

UA devices support Standard SIM (Mini SIM), Its 25mm in Length, 15mm in Width and .76mm in height
Info : Once you insert the Standard SIM, the device needs to be rebooted.

Preparing mbox for mfusion orchestration

The mfusion platform can be a VM or Physical server hosted in the cloud, or an on-premise (private) deployment that is reachable by HSG, CMG, HSA, UA, and MAP.

All RansNet devices, once come online with direct Internet access, will auto attempt to “call-home” to register with mfusion for monitoring and orchestration.

Getting Devices Online

All RansNet devices default configuration (factory default setting) has WAN (eth0) interface configured to obtain IP address from upstream DHCP server and automatically connect to Internet.

If static IP is required for WAN connection, you need to access via SSH/console to configure WAN/eth0 via CLI.

login as: support
support@mbox's password:
mbox> enable
Enter enable password:
mbox#
mbox# configure
mbox(config)# interface eth0
mbox(config-eth0)# ip address <WANIP>/prefix  (eg. 202.120.9.2/30)
mbox(config)#
mbox(config)# ip default-gateway <gateway-ip>  (eg. 202.120.9.1)
mbox(config)# ip name-server 8.8.8.8 8.8.4.4

Preparing to Register Device with mfusion

mfusion – RansNet cloud mode (portal.ransnet.com)

RansNet has a hosted cloud mfusion platform (portal.ransnet.com), shared by all customers and partners to manage RansNet appliances. Each authorized RansNet partner will be given an administrative access to RansNet mfusion. User can contact RansNet account manager for the login credentials.

Each RansNet device (factory default setting) will auto-connect to portal.ransnet.com once online. No special device configuration is required, except that we must provision the device on RansNet cloud mfusion.

This image has an empty alt attribute; its file name is •-Topology-Design-For-RansNet-Documentation-1-1-1.png — mfusion – RansNet Cloud

mfusion – On-premise mode

For enterprises who purchase and deploy mfusion as an on-premise appliance, we have to pre-provision the mbox appliance to register with on-premise mfusion IP address.

This image has an empty alt attribute; its file name is •-Topology-Design-For-RansNet-Documentation-2-1.png — mfusion – private/On-premise

login as: support
support@mbox's password:
mbox> enable
Enter enable password:
mbox#
mbox# configure
mbox(config)# ip host portal.ransnet.com <onprem-mfusion-ip>

Troubleshooting Host + mfusion provisioning issue .

Visit mfusion connectivity link to troubleshoot device and mfusion connectivity issue.

Registering MAP – RansNet Cloud / On-Premise modes

Product : MAP (Access Point)

Mbox Access Point (MAP) and Mobile Access Cloud Center (MACC) can be deployed in 3 different Mode:

MAP with Cloud MACC
- User can register MAP with RansNet Cloud MACC the Mobility Controller which is hosted in the cloud, which is shown in the below tab ‘Scenario 1‘
MAP with On-premise Hotspot Gateway (HSG)
- User can register MAP with RansNet On-premises (Local Hosted HSG) Gateway, the HSG comes with MACC built-in module. This module has to be started manually in HSG and then register the MAP with Local HSG, which is shown in the below tab ‘Scenario 2‘
MAP with Private Cloud MACC.
- User can register the MAP with RansNet MACC hosted in the customer’s private cloud.

Scenario 1: Register MAP with cloud MACC
Scenario 2: Register MAP with on-premise HSG
Scenario 3: Register with private cloud MACC

RansNet cloud HSG/MACC with a publicly accessible URL (macc.ransnet.com). By default, the MAP comes built-in default configuration where the user doesn’t have to do anything on a fresh RansNet MAP. Just power it up and once MAP gets DHCP IP address from a VLAN with direct Internet access, it will look for RansNet cloud MACC.

But for some legacy reason, You can simply bootstrap your MAP with below configs.

!
cwmp
 acs url https://macc.ransnet.com:8443/service/tr069servlet
 cpe inform interval 300
 no cpe back-up
!
log_mng set uu http://macc.ransnet.com:8080/macclog/log/upload
log_mng set upd 300
!
interface BVI 1
 ip address dhcp
!

Note

The above config is also the default config after you do factory reset of the MAP (or fresh install), which means, if the default config is not like above, just paste the above config to MAP console.

In this case, HSG will issue IP (DHCP) to MAP from management VLAN.

Add the below configure to HSG to rewrite MAP DNS (‘ip host macc.ransnet.com 2.1.2.1 rewrite‘) requests, so that when MAP tries to register with macc.ransnet.com from its default configs, the actual request goes to local HSG/MACC loopback interface IP instead.

In this case, bootstrap your MAP with default configs as in Scenario 1, then configure below related commands on local HSG.

!
interface eth1
 description "trunk to LAN"
 enable
 ip address 192.168.8.1/22
 dhcp-server
  description "Management VLAN DHCP scope"
  dns 8.8.8.8 8.8.4.4
  range 192.168.8.10 192.168.11.254
  enable
!
interface loopback
 enable
 ip address 2.1.2.1/32
!
ip dhcp-server start
!
ip host macc.ransnet.com 2.1.2.1 rewrite
!
macc start
!
firewall-dnat 20 redirect all udp dport 53 src 192.168.8.0/22
!
firewall-input 20 permit all udp dport 53 src 192.168.8.0/22
!

When customers or partners want to host their own private cloud (HSG/MACC) to manage many remote MAPs, just make sure the central/cloud HSG is accessible by all remote MAPs with a static IP address. There’re two options to bootstrap MAP:

If Local gateway is HSG/CMG/HSG, on your gateway set DNS rewrite macc.ransnet.com to your own cloud MACC IP, eg. ip host macc.ransnet.com <your-macc-ip> rewrite
- Then all the MAP behind this gateway will auto register with <your-macc-ip>.
If local gateway is third-party router, we need to explicitly tell MAP IP address of MACC. On each MAP, load in below default cwmp configs (replace the IP here with your actual cloud MACC IP)

User Access Verification
Password:
RANSNET>enable
RANSNET#configure
Enter configuration commands, one per line.  End with CNTL/Z.
RANSNET(config)#ip host macc.ransnet.com 49.128.58.74 rewrite

Provisioning Devices To mfusion

Once the orchestration is ready, the user can provision the device to the orchestration. See Provisioning device on mfusion