Scribd Logo
Upload

Welcome to Scribd!

  • 4K views

    AMOS Commands

    Uploaded by

    Mohd Zalhariz Mahamad Zaihan
    This document provides commands for various diagnostic and monitoring tasks in an AMOS system. Some of the key commands include: 1. lt all to check the health and status of nodes. 2. alt to check alarms and hardware status. 3. lga to check the alarm log history. 4. license commands like license key to check the license details. 5. ue print to check users attached to cells in an eNodeB. 6. st sector and get proxy to check the status and details of sectors. 7. pmr to check traffic performance. 8. cvls and cvms commands to check and create system backups.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    AMOS Commands

    Uploaded by

    Mohd Zalhariz Mahamad Zaihan
    4K views7 pages
    This document provides commands for various diagnostic and monitoring tasks in an AMOS system. Some of the key commands include: 1. lt all to check the health and status of nodes. 2. alt to check alarms and hardware status. 3. lga to check the alarm log history. 4. license commands like license key to check the license details. 5. ue print to check users attached to cells in an eNodeB. 6. st sector and get proxy to check the status and details of sectors. 7. pmr to check traffic performance. 8. cvls and cvms commands to check and create system backups.

    Original Description:

    AMOS ERICSSON

    Original Title

    AMOS Commands (1)

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides commands for various diagnostic and monitoring tasks in an AMOS system. Some of the key commands include: 1. lt all to check the health and status of nodes. 2. alt to check alarms and hardware status. 3. lga to check the alarm log history. 4. license commands like license key to check the license details. 5. ue print to check users attached to cells in an eNodeB. 6. st sector and get proxy to check the status and details of sectors. 7. pmr to check traffic performance. 8. cvls and cvms commands to check and create system backups.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    4K views7 pages

    AMOS Commands

    Uploaded by

    Mohd Zalhariz Mahamad Zaihan
    This document provides commands for various diagnostic and monitoring tasks in an AMOS system. Some of the key commands include: 1. lt all to check the health and status of nodes. 2. alt to check alarms and hardware status. 3. lga to check the alarm log history. 4. license commands like license key to check the license details. 5. ue print to check users attached to cells in an eNodeB. 6. st sector and get proxy to check the status and details of sectors. 7. pmr to check traffic performance. 8. cvls and cvms commands to check and create system backups.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 7
    At a glance
    Powered by AI
    The document outlines various AMOS commands that can be used to monitor and troubleshoot an LTE network.

    Commands like invh, st plugin, and st GigabitEthernet can be used to check hardware status of different components.

    Commands like lt all, cedr, and st mme can be used to check user connectivity and status in different network elements.

    AMOS Commands

    1. Verify Health Check


    >lt all
    >acc 0 startHealthCheck
    >get 0 healthCheckResult

    ResultCode: Refer Library Explorer/Alex for more information.

    2. To check Alarm and Hardware Status


    >alt

    3. To check Alarm log history


    >lga
    >lga | grep –s20140501 –e 20140520 - alarm log specific time
    - check log restart

    C – Critical, M – Major, m – minor

    * Clock calibration (clearance alarm)

    4. Check License
    >license key
    >license lkf
    >license server

    5. Check UE attach to cell (eNodeB)


    >ue print -admitted

    6. Check Number of User (NodeB)


    >get radio no

    *Or can view using Node Status Analyzer


    7. Check user (In RNC)
    >lt all
    >cedr | grep <node B cell id>

    eg: SDRN12>cedr | grep RW10263_2_3

    8. View status Iub (In RNC)


    >st iub
    >get <proxy> - to view detail

    9. Check Relation (neighboring cell) (eNodeB)


    >pr relation
    >pr EUtranCellRelation

    10. Verify Hardware Status


    >invh

    11. Verify all Plugin Units


    >st plugin
    >get <proxy> - to view detail

    12. Verify Gigabit Ethernet Link Connection Status


    >st GigaBitEthernet / st giga
    >get <proxy> - to view detail

    13. To check IP Configuration in NodeB


    >stip

    ( password: rbs)

    14. To check Gigabit speed and duplex setting


    >lget giga actualSpeedDuplex
    >st giga

    (1000M FullDuplex)
    15. Check S1 interface connection (eNodeB)
    >st mme

    16. Check Sector status


    >st sector
    >get <proxy> - to view detail

    17. Check eUtranCell status (eNodeB)


    >st utrancell @ st cell (NodeB)
    >get <proxy> - to view detail

    18. Traffic Performance


    >pmr

    19. To check ENodeB product detail


    >get 0
    >get 1

    20. To check NTP Frequency Synchronization (Clocking status)


    >get Synchronization clock
    >sts
    >st IpSyncRef

    *SYSTEM CLOCK: LOCK_MODE

    21. Check DUS/RRUS HWstatus and VSWR


    >cabx
    ( password: rbs)

    Note: VSWR Value must below <1.5


    22. Check Temperature of RRUS
    >lh ru fui get temp

    Normal operating temp. 40 to +50 C

    23. Check RRUS for any faults (eNodeB)


    >lhsh BXP_0_1 fm getfaults (Cell 1)
    >lhsh BXP_1_1 fm getfaults (Cell 2)
    >lhsh BXP_2_1 fm getfaults (Cell 3)

    24. Check External Alarm port status and alarm slogan

    >lget alarmport slogan | severity


    >lst hwunit=sup-1,alarmport=[1-9]$
    >lget hwunit=sup-1,alarmport=[1-9]$ alarm slogan
    >get <pxoxy> - to display alarm details
    >set <proxy> alarm slogan ‘cps fail’ - to set alarm text
    >bl <proxy> - to block alarm port
    >deb <proxy> - to deblock alarm port

    eg: proxy =301


    bl 301 , deb 301

    25. To check and create system backup


    >cvls
    >cvms <cvname> <username> <comment>
    >cvls

    26. To Lock/Unlock MME (eNodeB)


    >st mme
    >bl mme
    >st mme
    >deb mme
    >st mme

    27. To Lock/Unlock eUtranCell (eNodeB)


    >st fdd
    >bl fdd
    >st fdd
    >deb fdd
    >st fdd

    28. To Lock/Unlock neighbouring eNodeB


    >st termpoint
    >bl termpoint
    >st termpoint
    >deb termpoint
    >st termpoint

    29. To check or reconfigure power of eNodeB


    >get . configuredOutputPower
    >set . configuredOutputPower 40
    >bl fdd
    >deb fdd
    >get . maximumTransmissionPower

    (40Watt for macro site)

    30. To Lock/Unlock RRU (eNodeB) @ RU (NodeB)


    >st rru / ru
    >bl rru
    >deb rru
    >st rru

    31. To Lock/Unlock DU
    >st du
    >bl du
    >del du

    32. To Restart RRU


    >st rru

    eg: proxy =320

    >acl 320
    >acc 320 restartunit
    >acc 320 0 manualrestart

    33. To Restart eNodeB


    >acc 0 manualrestart

    34. To check how long the site has been up and running
    >uptime

    35. To check eNodeB/NodeB restart logs


    >llog

    36. Node Performance


    >getstat

    37. Fetching and processing of node logs


    >lgd - downtime log./History of node outages.
    >lgx
    >lgs - History of node/board/program restarts.
    >lgo - History of MO write commands (set/action/create/delete)

    38. To perform S1 link ping test


    >facc ipaccesshostet ping <dst ip>

    eg: facc ipaccesshostet ping 10.223.32.1

    39. To perform continue ping test from traffic interface


    >iacrh ping –dst <destination> ip> -src <source ip> -n <count>

    eg: iacrh ping –dst 10.223.32.1 –src 10.157.80.185 –n 10


    40. To perform trace route from traffic interface
    >iacrh traceroute –dst <ip> -src <ip>

    eg: iarch traceroute –dst 10.223.32.1 –src 10.157.66.1


    (password: rbs)

    You might also like