Metod of procedure

Onsite Integration
ESTABLISHING COMMUNICATION BETWEEN THE PC AND THE DUL
Connecting to the DUL requires a special cable and software (hyperterm and CoreFTP or Filezilla)
CONNECTING THE DUL
Connect a DUL Interface Cable (or two homemade cables) between the PC and each of the Local
Maintenance Terminal (LMT) on the DUL.
LMT A – Serial Interface – Connect DB-9-USB to  RJ45 LMT A
LMT B – Ethernet Interface– Connect PC LAN Port RJ-45  RJ45 LMT B

CONFIGURING THE SERIAL INTERFACE OF THE ON YOUR PC

Use a program as HyperTerm, to establish serial communications between the PC and the RBS (LMT A).
1. Open up HyperTerminal and configure the serial port settings properties:
• Stop Bits: 1
• Parity: None
• Baud: 9600
• Flow control: NONE
FORMAT THE C2 AND D HARD DRIVES ON THE DUL ScratchingLoad

Prior to scratch loading the basic package on to the RBs we need to wipe the drives on the DUL clean Make sure you
have the right basic package. LTE RAN L11B ICP6 - Released  Contains R19AK Basic Package
1. Insure the LMTA Interface Cable is connected and open up a Terminal Emulation Window (PuTTy, HyperTerminal,
etc.). When the terminal information window press the Enter key and you should get either a “$” prompt or it will ask for
username and password

Default username: rbs

Default password: rbs
2. Print the volumes on the DUL by typing the following command at the $ (prompt) in the serial connection window.
This will show the drives and the disk usage.

$ vols
If the /c volume is present then proceed to next step. If the /c2 volume is present then skip to step 7.
The /d volume will always be there.
3. Formatting the /d drive

$ formathd /d
Response: All data on volume will be destroyed. Continue? y/n (n):
Response: Formatting Hard Disk
Answer: y
$ reload – (if c2 – from the vols command below already exists – node is already in backup mode and there is
no need to execute this command)
4. Formatting the /c drive on the DUL

$ formathd /c or $ formathd /c2  whichever you have

Response: All data on volume will be destroyed. Continue? y/n (n):
Answer: y
$ reload --
Hit Enter
You should get either a “$” prompt or it will ask
for username.
Default username: rbs
Default password: rbs
5. Enter the following command to set the
IP address of the RBS.

$ ifconfig le0 169.254.1.10 netmask 255.255.0.0

INSTALLING THE “BASIC PACKAGE”
This procedure will transfer the software files of the basic package on your PC to the RBS. You will need to use the correct
Basic Package. LTE RAN L17A.0 - Released  Contains R19AK Basic Package
• L17A.0 CXP102051/26_R24FM
1. Ensure the LMTB Interface Cable is connected open an ftp client application. (Core FTP, FileZilla, etc)

Make sure file transfer mode is set to Binary Mode

2. Connect to the RBS with the ftp client application using IP address 169.254.1.10.

Username: rbs
Password: rbs
3. From within the ftp client application navigate to the
• RBS basic package (/d and /c2 drives) located on the PC’s hard drive
• RBS hard drive (/d and /c2 drives) location on the RBS.
4. Highlight the /d and /c2 folders from the Basic Package on the PC Hard Drive (window on the left). Drag and drop these
two folders into an open area (window on the right side)
Filezilla depiction of the transfer of the /d and /c2 basic package to the DUL.
This will take anywhere between 5 to 20 minutes. You can watch the progress of the transfer by typing $
vols at the prompt of your serial connection.
RBS ELEMENT MANAGEMENT APPLICATIONS

LMT B – Ethernet Interface– Connect PC LAN Port RJ-45  RJ45 LMT B

Download Install RBS Element Management Applications for Windows

1. Must have java 1.5 or higher installed on PC.
2. Connect a crossed Ethernet cable from your PC to the eNodeB local Ethernet port (LMT B).

3. In the network settings of your PC, set the

• IP address to 169.254.1.2,
• netmask to 255.255.0.0
• default router to 169.254.1.10.
4. Open Internet Explorer (IE) and type in
the following url address:
http://169.254.1.10/em/index.html

5. Click on Windows Download, then click Run.

Follow the install instructions as they are displayed.
• Before to start the rbs configuration check and set the netx moshell parameters
• get . rbsconfig - get . autoconfig - cabx create cv and restart
 Verify the site name and the cripts
Site Install file
Initial comunication betwen RBS &OSS
IP configuration VID 101, SUBMASK 255.255.255.252 DR 10.198.192.217
DEF domain name = oss3.ericssondns.com
 
Site Basic file
• TN (Transport Network) Configuration Worksheet o Contains eNB OA&M and S1-X2 IP routing information.
o TN data is housed in xng and/or in IP control.
o The eNB TN Configuration data is Maintained by Facilities Team\
 

Site Equiped file HW config PSU PDU SCU DU RU

 
• RN (Radio Network) Configuration Worksheet o Contains RF location, cell identity, and radio configuration information
for the eNB.
o RN data is housed in Geo-Plan which can be used to create this file.
o The eNB RN configuration data is updated and Maintained by RF Design & Performance Teams
 
From the tools dropdown select Integrate RBS… to get the ball rolling.

RBS Element Manager - Start RBS Integration

RBS Element Manager - Integrate RBS
Network Configuration Data - Network configuration data is
automatically filled in. DNS server is blank.

RBS Element Manager - Network configuration data

Configuration files data – IMPORTANT: Browse to the right folder. For “Site basic configuration”
select SiteBasic.xml, and for “Site equipment configuration” Select RbsEquipment.xml.
• License key - check the checkbox. Don’t use license key file, even if present in summary file.
• Upgrade package - check the checkbox. Don’t use Upgrade Package, even if present in summary file
Browse and chose the right SiteBasic file, or RBS
integration will hang at 85% Establishing S1 Connection! Browse and chose the right RbsEquipment
RBS Element Manager - Cabinet Data
Progress view automatically starts and provides us detailed information on the integration progress. See Figure 29 on
the following page.
If the progress bar at the bottom of the progress information window hangs – DO NOT cancel the Integration. Below
are the typical activities where the RBS integration process stalls
• 25% - “Activation of IP Connectivity”. Verify the physical connection between the eNB and the CSR.
• 77% - “Notification of OSS”. Verify IP assignments and routing for OAM – eNB and OSS.
• 81% - “Activating Planned Configuration Area”. May have to manually activate.
• 85% - “Establishment of S1 Connection”. Verify routing between the eNB and MME.

If the integration stalls between 77% and 85% – check the following
Step 1. First - Is the eNB Connected and Synchronized on the OSS?
Step 2. Second - Did the Planned Configuration run successfully?
At 81%, after the node is connected and synchronized, the Planned Configuration should run. If not
a. Check in OSS - Is eNB connected and synchronized
b. Check in OSS – Did the PCA activate successfully
c. Check in eNB via Amos. Are these MO created

Create cv Rbs configuration complete

Metod of procedure
Remote Integration
• Supplies
• 1.- Ensure the right scripts were loaded
• 2.- Prechecks “RRUs, Sectors, Hardware, alarms General Healty
• Star Integration
• 3. Create PCA (MME, FDD “TN,RN”), System Synchronization
• 4.- Load License Key File LKF
• 5.- Load Relations
• 6.- Baselines
• 7.- Scanner Activation
• 8.- Post Check
• Aafter to complete any step créate CV with cvms
1.- The logicalName, the promt and the site, must match to ensure the right scripts were loaded..
SiteID> get 0

110808-13:02:54 184.140.128.46 8.0u ERBS_NODE_MODEL_A_9_54 stopfile=/tmp/21108

===============================================================================
0 ManagedElement=1
===============================================================================
ManagedElementId 1
applicationConfiguration t[0] =
faultTolerantCoreStates s[1] =
ManagedElement=1,Equipment=1,Subrack=1,Slot=1,PlugInUnit=1;Active
healthCheckResult Struct{3}
logicalName <SiteID>
mimInfo Struct{3}
>>> 1.mimName = ERBS_NODE_MODEL_A
>>> 2.mimVersion = 9.54
>>> 3.mimRelease =
mimName ERBS_NODE_MODEL_A
productName RBS6601L
productNumber
productRevision
productType Node
site <SiteID>
userLabel <SiteID>
================================================================================
Total: 1 MOs
2.- Prechecks “RRUs, Sectors, Hardware, alarms General Healty

st ru Verify there are RUs defined.

st sector Verify there are Sectors defined.
st fdd Verify there are FDD MOsdefined. If not you need to synchronized the site.
st mme Verify there are mme MOs defined. If not you need to synchronized the site.
alt General alarm check
OSS Network explorer
Using OSS Common Explorer, syncrhonize the site.
Synchronize the node.
lt all Load all Mos

st fdd Verify there are FDD MOsdefined. If not you manually activate the planned configuration.

st mme Verify there are mme MOs defined. If not you manually activate the planned configuration.
3. Create PCA (MME, FDD “TN,RN”), System Synchronization
View --> Planned Configuration Administration (PCA)

New Planned Configuration (name: signum_site)

Click right click on Planned configuration you created. --> Import..

Select <SiteID>_TNBulkCM_bulkCMEngine.xml

Right click on Planned configuration you created. --> Activate..

You should get a successful message.

Click right click on Planned configuration you created. --> Import..

Select <SiteID>_RNBulkCM_bulkCMEngine.xml

You should get a successful message.

Click right click on Planned configuration you created. --> Activate..

You should get a successful message.

Delete Planned configuration you created.

Search and identify the PCA route for yours TN RN Files

CFLe0501626_PCA

/var/opt/ericsson/nms_umts_wran_bcg/files/import/CFLe0501626_TNBulkCM_bulkCMEngine.xml

/var/opt/ericsson/nms_umts_wran_bcg/files/import/CFLe0501626_RNBulkCM_bulkCMEngine.xml
Put it on Name the file route for TN RN
 List and verify the TN MME RN FDD

lt all Load all MOs

st fdd Verify there are FDD MOsdefined.
st mme
Verify there are mme MOs defined. If mme are locked, unlocked them.
deb mme
cvms PCA_activated
qdavord NIC Create a CV to save the new configuration.

If is necessary activate rollback, autocreate cv, set Rbs password

passwd;rbs;rbs set the password

cvms password_set qdavord password_set  
get . rollback  
cv rbrm basic_cv remove the basic cv form the rollback list
set ConfigurationVersion=1 rollbackOn false  
cvms RollBackOff qdavord Rollbackoff Create a CV to save the new configuration.
set ConfigurationVersion=1 autoCreatedCVIsTurnedOn True  
cvms AutoCreatedCVOn qdavord AutoCreatedCvTrue Create a CV to save the new configuration.
To ajust and synchronize node
 4.- Load License Key File LKF
Import & Load the lkf route

OSS Software Management

 
Organizer

Network --> SiteID R19AK  to L11B

Right click on SiteID. -->

R17AJ is L12A
Adjust..

Jobs Verify the job's progress, it should reach 100%

Network --> SiteID ftput /home/ericengg//PHLe0760636_120606_230034.xml /c/license/PHLe0760636_120606_230034.xml

Right click on SiteID. -->

Install License Key files.. acc 6 updateLicenseKeyFile

Jobs Verify the job's progress, it should reach 100% y

Right click on SiteID. --> 4

Adjust..

Jobs Verify the job's progress, it should reach 100% rbs

lt all Load all Mos ip
license server Verify the LKF is installed /c/license/PHLe0760636_120606_230034.xml
After the eNB is configured on the OSS the Switch will then transfer the LKF onto the
OSS, via an FTP program, so that it can be delivered and Imported into SMO (Software
Management Organizer).
Load license by moshell
Open SMO
Under licenses click on Import LKF Batch file.
Select the LKF Batch files to Import. Click Next
Verify summary of job configuration. Click Finish
Select the Jobs Icon and verify the Import License Job was completed successfully.
The license will now showed up in the list as unadjusted.
 5.- Load Neighbor Relations
Just identify the NR route and run the script with truni, and check with moshell tool with pr rela
lt all Load all MOs

Type thw word "quick" to activate the quick tool, it will show some options in a menu format. Chose the option number 4.
Otherwise, you can find the NR script on the following path:
/home/ericengg/Relations/MARKETID/ example:"/home/ericengg/Relations/DFW"
!ls *siteID*
Make a cv that includes the RND revision in the cv name after the script is loaded.

quick > truni /home/ericengg/Relations/MARKETID/SiteName_Relation.mo

NOTE1: Ignore the following errors if received:

Mo Name Taken
Mo Cardinality Violation
NOTE2: If any other errors received then correct before proceeding.

lt all Load all MOs

pr relation List the relations created.
Make a cv that includes the RND revision in the cv name after the script is loaded.
cvms Relations_Loaded e.g. cvms Relations_Loaded_R2B eusxxxx
qdavord
NOTE: The RND revision can be found as part of the relations folder name where the relation scripts are stored.
cvls Verify the CV was created.
 6.- Baseline
Just identify the Baseline route and run the script with

lt all Load all MOs

!cd
/home/ericengg/eus go to a new folder, where the SystemContants is located l ls
corp

run CVLS Release L11B L12A This script will set the primary configuration according the
MetroPCS_Baseline_ customer requirements. It also will make a cv and restart the DUL. run
L11B_REV_PA28.mos MetroPCS_Baseline_L12A_REV_PA39.mos

polk  
 7.- Scanner
Activation
Step1: Use the "pst" command to check and three other scanners are “ACTIVE
Step 2: If you don’t have 4 ACTIVE scanners, open OSS Network Explorer GUI
Step 3: Select the "Performance" menu and go to --> "Initiate Data Collection" and select "RAN Measurements"
Step 4: The "Data collection" window opens up. In the “User defined statistics profiles” tab select
"VzW_Tool_Profile_L11B" profile and right click on it and --> select "Modify profile".
Step 5:  Select "eRBS" tab and select the eNodeB you are currently integrating on the left-side and select
the button as below to add it to the right-side and click "OK"
 
Step 6: Again perform the "lt all" and then the "pst" command on the eNodeB. The scanner
“USERDEF.VzW_Tool_Profile_L16A.Profile=XXX.Continuous=Y.STATS” should now be ACTIVE
 
Step 7: Create a CV --> VzW_tool_Scanner_activated
 
Step 8: The "Data collection" window opens up.  We will now be adding the site to two Cell Trace
Profiles: ECDS_XXBLADE_L16A
 Post
lt all
st fdd
st sector
Load all MOs
Check
fdd should be unlocked / enabled
sectors should be unlocked / enabled
st ru rus should be unlocked / enabled
alt no alarms related to the rrus, sectors and fdds
get fdd cellbarred FDDs should be not barred. cellbarred i[1] = 1
get fdd cellreserved FDDs should be reserved. cellReservedForOperatorUse i[1] = 0
1st attempt
bl fdd Lock and unlock the FDDs and sectors and Rus.
bl sector
deb sector During the call tests (Integration Call Testing)
deb fdd Cells / FDD - Admin State – Unlocked
wait 5 Cells / FDD - Operational State - Enabled
st sector Cells / FDD - cellReservedForOperatorUse to 0 [RESERVED]
st fdd Cells / FDD - cellBarred - 1 [UN BARRED]
get all phy PCI=(physicalLayerCellIdGroup*3)+physicalLayerSubCellId
<SiteID> ue print -admitted

110809-16:22:14 184.140.163.234 8.0u ERBS_NODE_MODEL_B_1_52 stopfile=/tmp/27941

$ ue print -admitted
ue print -admitted CellId #UE:s #Bearers
15 0 0
16 1 1
17 0 0
The table below show the port asingned to each new HW on master DU

Port A Used by Port B Used by

A1 SCU B1 Master input (DU)
A2 PDU 1 B2 PDU 2
A3 PSU 1 B3 PSU 2
A4 PSU 3 B4 PSU 4
A5 DU B5 BFU
A6 DU B6  
A7 DU B7 PDU 3
A8   B8 PDU 4
 unlock &Lock
• Set EUtranCellFDD= administrativeState 1
• set EUtranCellFDD= cellBarred 1
• set EUtranCellFDD=MLSONCAJ0953Y_._. operationalState 1
• set EUtranCellFDD= primaryPlmnReserved false
• ldeb fdd
• MLSONCAJ0953Y> hget EUtranCellFDD= administrativeState|cellBarred|operationalState|partOfSectorPower|primaryPlmnReserved
• 171005-16:03:42 10.246.255.173 17.0g ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/1409
• =================================================================================================================
• MO administrativeState cellBarred operationalState primaryPlmnReserved
• =================================================================================================================
• EUtranCellFDD=MLSONCAJ0953Y_1_C1 1 (UNLOCKED) 1 (NOT_BARRED) 1 (ENABLED) false
• EUtranCellFDD=MLSONCAJ0953Y_2_C1 1 (UNLOCKED) 1 (NOT_BARRED) 1 (ENABLED) false
• EUtranCellFDD=MLSONCAJ0953Y_3_C1 1 (UNLOCKED) 1 (NOT_BARRED) 1 (ENABLED) false
• =================================================================================================================
• Total: 3 MOs
• Set EUtranCellFDD= administrativeState 0
• set EUtranCellFDD= cellBarred 0
• set EUtranCellFDD=MLSONCAJ0953Y_._. operationalState 0
• set EUtranCellFDD= primaryPlmnReserved true
• Bl fdd
Moshell
MO Tree and MO Naming Conventions
1 LDN - Local Distinguished Name
The MOs are organised in a hierarchical structure.
Each MO instance is uniquely identified in the node by its Local Distinguished Name (LDN).
The highest MO in a node, the so called root MO is the ManagedElement. This MO
represents the whole node.
There is only one instance of the ManagedElement MO in the node and it is referenced by the
LDN: ManagedElement=1
The string at the left of the equal sign is called the MO class (or MO type) and the string at the
right of the equal sign is called the MO identity. In the case of the root MO, the MO class is
ManagedElement and the identity is 1.
If an MO is located further down in the MO tree, the LDN must contain the MO classes and
identities of all the parents of that MO, in a sequence going from the root MO down to the MO
in question. See example below:
ManagedElement=1
ManagedElement=1,Equipment=1
ManagedElement=1,Equipment=1,Subrack=MS
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1,Program=DbmFpgaLoader
From this example, we can see that the ManagedElement has a child called Equipment=1
which has a child called Subrack=MS (representing the main subrack of the node), which has
a child called Slot=19 (representing the slot in position 19), which has a child called
PlugInUnit=1 (representing the board located in that slot), which has a child called
Program=DbmFpgaLoader (representing one of the programs loaded in that board).
RDN - Relative Distinguished Name
The string located at the far right of an LDN, just after the last comma, is called a Relative
Distinguished Name (RDN).
It is a unique way of addressing a MO instance in relation to its closest parent.
This means that there is only one MO instance with the RDN Program=DbmFpgaLoader
under the parent MO
ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1. However, there
could be another MO instance with the same RDN under a different parent MO. For instance,
there could be an MO instance with the RDN Program=DbmFpgaLoader under the parent
MO ManagedElement=1,Equipment=1,Subrack=MS,Slot=23,PlugInUnit=1.
Therefore the RDN is a relative way of addressing an MO instance.
FDN - Full Distinguished Name
When a node is connected to a Network Management System such as OSS-RC, there is a
need to uniquely address each MO within the whole network. The Full Distinguished Name
(FDN) adds a network element prefix in front of the LDN of each MO instance in order to
specify which node this MO belongs to. See the figure below, summing up the FDN/LDN/RDN
concept:
FDN (Full Distinguished Name)
<------------------------------------------------------------............................................................>
LDN (Local Distinguished Name)
<--------------................................................................>
MoClass Identity
<-----> <---> RDN (Relative Distinguished Name)
<--------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1 RDN
<-------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1 RDN
<----->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS RDN
<---------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS,Slot=19 RDN
<------------------->
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1
Network=H3GA,Utran=Rnc1,MeContext=Rbs03,ManagedElement=1,Equipment=1,Subrack=MS,Slot=19,PlugInUnit=1,Program=DbmFpgaLoader
MOM - Managed Object Model
Each MO class contains a number of attributes which are used to store configuration data or
performance measurement data.
Each MO class can also support a number of defined actions. These represent certain
operations which can be performed by the MO. A typical example is the action restart which
will cause the MO to restart the resource it is responsible for (e.g. a board, a program, etc.).
The Managed Object Model (MOM) is a reference document describing all the MO Classes
that can exist in a node (see Reference [?] for more details), together with their attributes and
actions.
The format of the MOM can be UML, XML, HTML, or MS-Word.

Moshell Functionality
MoShell is a text-based O&M client providing access to the following services:
• Configuration service (CS)
• Alarm service (AS)
• Performance management service (PM)
• Log service (LS)
• OSE shell (COLI)
• File transfer (ftp/http)
Configuration Service
Moshell supports the following 6 operations from the
configuration service:
1. GetChildren to load all or parts of the MO-tree
2. GetAttribute to read the attributes of an MO
3. CallAction to perform an action on an MO
4. SetAttribute to set (change) the value of an MO attribute
5. CreateMO to create a new MO in the node
6. DeleteMO to delete an MO from the node

Performance Management Service

Moshell supports the following operations from the
performance management service:
• List Scanners and Event Filters
• Create Scanner
• Stop Scanner
• Resume Scanner
• Delete Scanner
• Set Event Filter
 Log service
Moshell supports fetching and parsing of the following logs:
• availability log
• system log
• event log
• alarm log
• command log
• O&M security event log
• COLI log
• Hardware inventory log
• JVM events log (upgrade log)

File transfer
Moshell can download/upload files and directories to/from the node, using http, ftp
or sftp.
How to specify attribute values in set/cr/acc commands
1. For attributes of type Struct, use the following syntax:
attr1=val1,[,attr2=val2[,attr3=val3]]]...
Example:
set sid sib11 sib11repperiod=128
set mtp3bspitu sppriority prioslt=2
set mtp3bspitu sppriority prioslt=2,prioco=2
2. For attributes of type MoRef, just type the MO LDN (without ManagedElement=1). E.g.:
lset AtmPort=1221,VplTp=vp1 atmTrafficDescriptor
transportnetwork=1,atmtrafficdescriptor=C1P4500
It is also possible to skip the first parent (eg TransportNetwork, SwManagement, etc).
E.g.:
cr rncfunction=1,utrancell=30451,utranrelation=30451to305212
Attribute 1 of 1, utrancellref (moRef:UtranCell): utrancell=30521
3. For attributes of type array of MoRefs, separate each element of the array with spaces.
Eg:
set jvm admclasspath loadmodule=oms loadmodule=vbjorb ...
acc aal2pathdistributionunit=1 addPath
Parameter 1 of 1, aal2PathVccTpId (sequence-moRef-Aal2PathVccTp):
aal2pathvcctp=csa aal2pathvcctp=csb
4. For attributes of type array of Struct, separate each element of the array with
semicolons. Eg:
set rncfunction aliasPlmnIdentities
mcc=300,mnc=23,mnclength=2;mcc=345,mnc=32,mnclength=2;mcc=208,mnc=123,mnclength=3
5. For attributes of type array of integer/long/float/string/boolean, separate each element of
the array with commas. Eg:
set antfeedercable=6 ulattenuation 10,10,10,10,10,10,10,10,10
set jvm options -Xms65000k,-Dhttp.root=/c/public_html,
-Dse.ericsson.security.PropertyFileLocation=/c/java/SecurityManagement.prp
set cell=3041 ActiveOverlaidCDMAChannelList true,true,false,true
acc managedelementdata addDhcpServerAddress
Parameter 1 of 1, ipAddressArray (sequence-string): 10.1.1.3,10.1.1

6. To input an empty value:

• in set command, just leave the value field blank. Eg:
set 0 userlabel
set reliableprogramuniter admpassiveslot
• in cr command, type null or d. This is only supported for non-mandatory
(restricted) attributes, because mandatory attributes must be given a value.
• in acc command, type null. This is only supported for parameters of type MoRef
or String.
Piping

Some commands support piping, e.g. All OSE shell commands, lh, tg, str, etc.
This is usually indicated in the menu and the help for that command. Some examples are:

te log read | grep ERROR

lh mp te log read | grep ERROR
str | grep cell=30456

For other commands that don’t support piping (like MO commands), the workaround is to
save the output to a logfile then run the unix command on that logfile by using the l or !
command. Example:

l+ #open the logfile, an arbitrary name will be given

prod loadmodule #run the command
l- #close the logfile
l sort $logfile #run unix command sort on the logfile.
l grep -i basic $logfile
Note: $logfile is automatically set by MoShell to contain the name of the latest log file
created.