Moshell Installation and Basic

Commands Instructions

Prepared by:
Nicolas Salgado Salinas

F1 Services & Solutions Chile

April 2020
7services&

Nicholas Salgado 1
 solutions

Requirements
• We must have a computer (PC) free of Cygwin, if
cygwin is installed on another, both versions will be
linked not allowing a clean execution, so it will throw
multiple reading errors and make it difficult to execute
scripts and commands.
• You must have the compressed file cygwin.rar which
can be downloaded from the following link:
https://drive.google.com/file/d/1GGx8dbwL9Ri2yPIsxRr3I25zkAo_dPNP/view?usp=sharing

• We must have RAR on our computer

Important
We must know that by using this tool we will have absolute
power over a node that is operational and providing services to the
community, so it is extremely important, before carrying out
actions on equipment, to inform and wait for authorization from
the integrator in charge of the work.

Nicholas Salgado 2
 Cygwin Installation
Cygwin is a free program that emulates the Linux command
line interface. The version that you can download from the link
mentioned above was created and modified to speed up the
installation and assembly of Moshell.
1. To begin with the assembly, it is necessary to mention that
the version you will download is completely portable, it does
not need an installer, so it is important not to modify it.
2. The file to be downloaded will be a compressed folder, so you
need to have some program that can read and edit .rar files.
3. Once the file is on your computer, it must be moved to the
root of the operating system, which is by default the C drive.

V Devices and units (3)

Local disk (C:) Opta ne (D:)

OR Yo Yo Yo
339GB available from 415GB 18.1 GB available out of 18.2 GB

4. Once in this location, we will proceed to unzip by right-clicking

on the Cygwin.rar file and selecting the “Extract here” option.

Nicholas Salgado 3
 April

Open with
WinRAR
Extract files...

Extract in cygwin\

Move to OneDrive
Edit with Notepad++

Scan with Windows Defender..

Open with...

Restore previous versions

Change name

Properties

5. This action will open a process box, which will show us

the percentage of extracted files.

6. Once the file extraction is complete, we will have our Cygwin +

Moshell version 19.0e ready to run.

This computer > Local disk (Q}

Modification date
gon
Name Tip Tamanc

e SSysReset
01-03-20201:38 File Folder File
Program Files
04-04-2020 1:31 Folder File Folder
Program Files (x86) cygwin
04-04-20201:37 File Folder
10-07-2019 16:20
cou
gh

Nicholas Salgado 4
 Running Moshell on Nodes
To start interacting with nodes you must change the IP of your
LOCAL Ethernet network card.
• Open control panel
• Select “Internet networks”
• Network and Sharing Center
• In the top left list select “Change adapter settings”
• We select ethernet network adapter
• The properties of the selected adapter will open.
• We will open the properties of “internet protocol version 4
(TCP/IPv4)
• We will select to use the following IP address
• Use the following IP address:

For DUW equipment we will use the following configuration:

(•Use the following IP address:

Requirements 2
Important 2
Cygwin Installation 3
Running Moshell on Nodes 6
Basic Commands 9
Baseband 9
DUW 10
DUS 10
Fundamental Consideration 11
Script execution 12

Nicholas Salgado 5
 For DUS equipment we will use the following configuration:

For Baseband equipment we will use the following configuration:

(•) Use the following IP address: IP address: | 169 . 254 . 2 . 1 |

Subnet Mask: | 255 ■ 255 . EITHER . O |

Default Gateway: 169 . 254 .2.2

After configuring the IP of our computer, connect locally to the

LMT port of the equipment to be intervened with a Straight Network
cable. (always keep in mind that our internet access, whether via
Wi-Fi or bam, must be disconnected).
Once connected, we will proceed to run cygwin terminal. This
will be done by double-clicking on the “cygwin.bat” file located in
the Cygwin folder of our Local Disk C.
bin cygdrive dev etc Home lib sbin tmp L usr

_7 cygwin_install.txt

By performing this action, a console terminal will open where

we must enter the following commands depending on the
equipment model to be intervened:
• moshell 169.254.1.1 (DUW)
• moshell 169.254.1.10 (DUS)
• moshell 169.254.2.2(BB5216)

Nicholas Salgado 6
 and will be appreciated as follows:
L~1$ moshell 160.254.1.1

Welcome to Moshell 19. Oe (LPA108514/1_R19E) Modified

Resource for Personal Fl services Modified by Nicolas Salgado
Salinas.
Contact: nicol as. salt@f 1. Fl.services services

#########;
WARNING: rhe moshell version currently running is more than 52 weeks old.
IT is recommended to always use The latest released moshell version.
Please download the latest version from http://newtran01.au.ao.ericsson.se/moshe 11

This execution will show us if we actually have connectivity

with node IP, as shown in the following image.

a. If “Checking ip contact” equals OK, it will indicate

whether we have contact with the unit’s IP.
b. If “Checking ip contact” equals Not OK, it will indicate
that for some reason, we do NOT have contact with the
unit's IP.
Once inside the node, the IP will be displayed followed by the
69.254.2.2* > symbol indicating that the connection has
been established.
Having contact, we can execute the lt all command to read
the entire node configuration, the MOs (Node resources) will be
assigned a number (proxy) and will be stored in an internal table in
the Moshell memory. The internal proxy table can be printed using
the pr command which will display for each MO, the LDN and the
proxy number. This is as shown in the following image.

Nicholas Salgado 7
 series &
solutions

169.254.2.2> It all
170729-16:30:49 169.254.2.2 11.Od stopfile=/tmp/2336 Please enter Username: rbs Please enter Node Password:
Sssh_pid ■ 15948
Connected to 169.254.2.2 (anagedElement-MPM290)

etching 43 MOM fragments via HTTPS

Parsi ng MOM: /home/aasenjo/moshel1_1ogfi1es/1ogs_moshel1/tempfi 1es/20170729-162955_l 476/co«n_node_mim.xml.gz Done.

Copying /home/aasenjo/moshell_logfi1es/1oos_moshell/tempiiles/2O17O729-162955_1476/c om_node_mim.xml.gz to
/home/aasenjo/jarxml/CRBS_N0DE_M0DEL_Grat_2_6_0_LratBb_l_7101_
R6AO3_LratMce_2_71OO_R6BO2_LratMp_l_71Ol_R6AO3_Lrat_l_715O_R6FOl_Wrat_7_9_9973d89bde b0d8e38ba92blb696ecc41.xml.gz
Caching MOM to: /home/aasenio/moshell_logfiles/logs_moshel1/tempfiles/20l70729-l6295 5_1476/com_node_mim.xml.cache Done.
Compressing to: /home/aasenjo/moshel1_1ogfiles/1ogs_moshell/tempfiles/20170729-16295 5_1476/com_node_mim.xml.cache.gz ...Done.
$ssh_pid ■ 2724
Connected to 169.254.2.2 ManagedElement-MPM290)
Connected to 169.254.2.2 anagedElement=MPM290)
Last MO: 6045. Loaded 6045 MOs. Total: 6046 MOs.
MPM290>

Basic Commands
Remember that after connecting to the node we must execute
the lt all command to read all the existing configuration.

Baseband
• Basebands will usually ask you to enter a username and
password, which in both cases is “rbs”
Command Description
alt Get active node alarms
cvls Get list of CVs created in Nodo
cvms<NombreDeCV> Create CV with name to identify you.
get transport=1,ethernetport WAN port status
get . vlanid VLAN
get . ^address$ Management IP and traffic with their
get . self-denying respective DGW
WAN Gate Negotiation
set . autoNegEnable True change port negotiation to true
set . autoNegEnable False change Port negotiation to False
cvre<NombreDeCV> Reboot the unit with the selected CV

Nicholas Salgado 8
 DUW
Command Description
alt Get active node alarms
cvls Get list of CVs created in Nodo
cvms<nombredecv> Create CV with name to identify you.
get gigabit Wan port status
get ipinterface VLAN and defaultRouter
get iphostlink Remote Management IP
get ipaccesshostet IP of IUB
get . autonegotiation Wan Gate Negotiation
set . autonegotiation true change negotiation to true
set . autonegotiation false change Port negotiation to False
Will leave the selected CV in rebootable
cvset<nombredecv>
mode (when rebooting the unit it will load
this CV)
Reboot the unit with the CV that is in
acc 0 manual restart
bootable mode

DUS
Command Description
alt Get active node alarms
cvls Get list of CVs created in Nodo
cvms<nombredecv> Create CV with name to identify you.
get gigabit Wan port status
get ipinterface VLAN and defaultRouter
get iphostlink Remote Management IP
get ipaccesshostet IP of IUB
get . autonegotiation Wan Gate Negotiation
set . autonegotiation true change negotiation to true
set . autonegotiation false change Port negotiation to False
It will leave the selected CV in rebootable
cvset<nombredecv>
mode (when rebooting the unit it will load
this CV)
Reboot the unit with the CV that is in
acc 0 manual restart
bootable mode

Nicholas Salgado 9
 Fundamental Consideration
Before intervening in a node we must ask ourselves the following
question: Have you created a CV?
Being an operational node, it is 100% likely.
But… what is a CV?
As with all technological equipment, system restore points
are created to avoid losing important information in the event
of failures.
On Ericsson devices, CV is a restore point. Normally, this
will be useful for making a backup of the current configuration
of the node, prior to executing jobs, and if this intervention
fails, we can easily recover the unit by restarting it with the
created CV.
It should be noted that Switch area personnel will
create CVs before and after the intervention, so this
action should NOT be executed without authorization
from the integrator.
Each CV created must contain a name associated with the
change made or to be made, for correct identification, in case
you want to restore a configuration point, especially if more
than one change has been made.
From now on, whenever CV is mentioned during the execution of
a job, it will refer to a restore point.

Nicholas Salgado 10
 7services&
solutions

Script execution
To run scripts, they must be hosted in the root of our Moshell.
By default it is C:\cygwin\home\F1.
The scripts that are used will normally have 2 formats that will be
differentiated by the file extension, these are .mo and .mos
• Truni runs .mo files
L~] $truni
.bash history* 1. DeleteGigaBitEthernet MAM773.mo*
.bashprofile* jarxml/
-bashrc* logfiles/
. inputrc* moshe11/
. minttyrc* moshell.tar
. moshellrc* _____________ ______
.profile* moshell_install*

Examp . ssh/ moshell_logf i les/

[~]$ truni 1. Delete_GigaBitEthernet_MAM773. my I

le
• Run executes the .mos files
L~-9 run
. bash_hi story* 1. Delete_GigaBitEthernet_MAM773. mo*
. bash_prof i le* jar xml/
.bashrc* logfiles/
.inputrc* moshell/
.minttyrc* moshell.tar
.moshellrc* moshell_____200410_1908/
.profile* moshell_install*
.ssh/ moshell_logfiles/
00.MAM773_CPE_DUS_Remoto.mos* [~]$ run 00.MAM773_CPE_DUS_Remoto.mos I
Exampl
e:

Nicholas Salgado 11