4.1.10 hget[c][m]/lhget[c][m] <moGroup>|<moFilter>|<proxy(s)> [<attribute-filter>] [<value1-filter>] [<value2-filter>] [<value3-filter>] etc...

Read CM/FM attribute(s) from MO(s), print horizontally one line per MO (instead of one line per attribute). Options: _ c: display the output in CSV format for easier export to excel (for instance). _ m: print all MOs in a single table instead of separate tables per MO class Example: _ hget reliableprogramuniter slot|operational print the RPU attributes admActiveSlot, admPassiveSlot and operationalMode _ hget reliableprogramuniter slot|operational slot=10 . ^2 print all RPUs that are defined on slot10 (active), any slot for passive, and 2 for the operationalmode _ hget reliableprogramuniter slot|operational !slot=10 . !^1 print all RPUs that are not defined on slot10 (active), any slot for passive, and operationalmode is not equal to 1 _ hget loadmodule type|productdata print the attributes loaderType and productData on all LoadModule MOs. Note that productData is a struct containing 5 members so the productData attribute will take up 5 columns _ hget loadmodule type|productdata@name only print the attribute loaderType and the structmember productData:productName passive, and operationalmode is not equal to 1 _ hgetm port state print all attributes matching the word "state" on all MOs matching the word "port" and display all lines in one single table instead of a separate table per MO class. For "slow" hget, use "shget/lshget": reads only one attribute at a time.

et/lkget [<moGroup>|<moFilter>|<proxy(s)>|all] Display CM/FM attributes in exportable printout format. Same as get/lget, but with a different output format to allow import of the dump into external tools like MCOM, CCT, ETRAN. For "slow" kget, use "skget/lskget": reads one attribute at a time. 4.1.12 fro/lfro[m] <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>|all] [<value-filter>] Read MO persistent data from node database via SQL. The fro/lfro command reads only the froId connecting the MAO and FRO parts of the MO. The from/lfrom command reads all MAO/FRO data of the MO. The command syntax and printout format is identical to that of the get/lget command. Examples: _ from upgradepackage=cxp9012014_r5a - print MAO/FRO persistent data for MO UpgradePackage=CXP9012014_R5A _ from 0 - print MAO/FRO persistent data for the ManagedElement MO _ fro plugin - print froId for all pluginunit MOs _ fro plugin . 5 - print the PlugInUnit MOs who have a froid matching the value 5 _ fro plugin . ^5$ - print the PlugInUnit MOs who have a froid equal to 5 _ lfro ms,slot=10,plugin sairesource > $sai - save the sairesourceid of a particular pluginunit into a variable $sai Note: If the SQL client LM (CXC1325608) is not started, the fro[m] command starts it automatically using the "sql+" command. After the session, the SQL client should be turned off using the "sql-" command. Type "h sql+" for more info.

asddkget/lkget [<moGroup>|<moFilter>|<proxy(s)>|all] Display CM/FM attributes in exportable printout format. Same as get/lget, but with a different output format to allow import of the dump into external tools like MCOM, CCT, ETRAN. For "slow" kget, use "skget/lskget": reads one attribute at a time. 4.1.12 fro/lfro[m] <moGroup>|<moFilter>|<proxy(s)>|all [<attribute-filter>|all] [<value-filter>] Read MO persistent data from node database via SQL. The fro/lfro command reads only the froId connecting the MAO and FRO parts of the MO. The from/lfrom command reads all MAO/FRO data of the MO. The command syntax and printout format is identical to that of the get/lget command.