Scribd Logo
Upload

Welcome to Scribd!

  • 244 views

    RRC Coomands Field

    Uploaded by

    vignan kuruva
    The document contains commands and instructions for troubleshooting 4G network issues. It includes commands to check throughput, packet loss, outages, reset routes, check VLAN IDs, IP addresses, and frame losses. It also provides instructions for restarting nodes and RRUs, checking sync member status, blocking and unblocking sync members, and creating node group sync members in both DUS and BB nodes.

    Copyright:

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

    RRC Coomands Field

    Uploaded by

    vignan kuruva
    244 views4 pages
    The document contains commands and instructions for troubleshooting 4G network issues. It includes commands to check throughput, packet loss, outages, reset routes, check VLAN IDs, IP addresses, and frame losses. It also provides instructions for restarting nodes and RRUs, checking sync member status, blocking and unblocking sync members, and creating node group sync members in both DUS and BB nodes.

    Original Description:

    commands

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document contains commands and instructions for troubleshooting 4G network issues. It includes commands to check throughput, packet loss, outages, reset routes, check VLAN IDs, IP addresses, and frame losses. It also provides instructions for restarting nodes and RRUs, checking sync member status, blocking and unblocking sync members, and creating node group sync members in both DUS and BB nodes.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    244 views4 pages

    RRC Coomands Field

    Uploaded by

    vignan kuruva
    The document contains commands and instructions for troubleshooting 4G network issues. It includes commands to check throughput, packet loss, outages, reset routes, check VLAN IDs, IP addresses, and frame losses. It also provides instructions for restarting nodes and RRUs, checking sync member status, blocking and unblocking sync members, and creating node group sync members in both DUS and BB nodes.

    Copyright:

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

    pmx .

    pmPdcpvoldlsrb|pmPdcpvoldldrb$ -m 1 -4G traffic check

    pmr -r 206 -m 4 | grep -i Int_DlThroughput_kbps - BB - 4G throughput


    pmr -r 106 -m 4 | grep -i Int_DlThroughput_kbps - DUS - 4G throughput

    pmr -r 206 -m 4 | grep -i Int_ULpacketloss - bb - ul packet loss


    pmr -r 106 -m 4 | grep -i Int_ULpacketloss - DUS - ul packet loss

    pmx LDNKN11 pmcelldowntimeauto|pmcelldowntimeman -m 3 - 4G repeated outage

    get . txpower -40W in BB - power definition in BB

    lhsh BXP_0 restart - to RRU reset(DUS & BB)

    lhsh BXP_1 restart - to RRU reset(DUS & BB)


    lhsh BXP_2 restart - to RRU reset(DUS & BB)
    lhsh BXP_3 restart - to RRU reset(DUS & BB)
    lhsh BXP_4 restart - to RRU reset(DUS & BB)
    lhsh BXP_5 restart - to RRU reset(DUS & BB)

    get . vlan - to check vlan id's in BB


    get . vid - to check vlan id's in DUS

    get ipaccess - to get CP/UP ip in DUS

    get addressipv4 - to get CP/UP ip in BB

    pmr -m 3 (to check IUB frame losses in 3G (select 15)

    cvget cvname - for BB backup

    amos -v exclude_deprecated=1 <node ip> (login in L17Q2 BB nodes to check mixed


    mode status)

    SGW ping status for packet loss in BB node:

    mcc Router=LTEUP ping --count 50 --packetsize 9000 10.206.193.17


    mcc Router=LTEUP ping --count 50 --packetsize 9000 10.206.194.161
    mcc Router=LTEUP ping --count 50 --packetsize 9000 10.206.149.5
    mcc Router=LTEUP ping --count 50 --packetsize 9000 10.40.24.49
    mcc Router=LTEUP ping --count 50 --packetsize 9000 10.0.240.49

    MME ping status for packet loss in BB node:

    mcc Router=LTECP ping --count 3 --packetsize 9000 10.206.194.129


    mcc Router=LTECP ping --count 3 --packetsize 9000 10.152.189.249
    mcc Router=LTECP ping --count 3 --packetsize 9000 10.152.189.241
    mcc Router=LTECP ping --count 3 --packetsize 9000 10.152.189.245

    SGW ping status for packet loss in DUS node:

    lhsh 000100 EtHostMo_startPing -h 1 -d 10.206.193.17 -c 50 -s 1500


    lhsh 000100 EtHostMo_startPing -h 1 -d 10.206.194.161 -c 50 -s 1500
    lhsh 000100 EtHostMo_startPing -h 1 -d 10.206.149.5 -c 50 -s 1500
    lhsh 000100 EtHostMo_startPing -h 1 -d 10.40.24.49 -c 50 -s 1500

    MME ping status for packet loss in DUS node:

    lhsh 000100 EtHostMo_startPing -h 2 -d 10.206.194.129 -c 50 -s 1500


    lhsh 000100 EtHostMo_startPing -h 2 -d 10.152.189.249 -c 50 -s 1500
    lhsh 000100 EtHostMo_startPing -h 2 -d 10.152.189.241 -c 50 -s 1500
    lhsh 000100 EtHostMo_startPing -h 2 -d 10.152.189.245 -c 50 -s 1500

    NGS Block D Block

    Remedy 1:-

    1. Login to node. Check which RU is working as sync source in �get


    NodeGroupSyncMember=1�.

    2. Block the �lbl NodeGroupSyncMember=1� wait for 2-4 mins & deblock it �ldeb
    NodeGroupSyncMember=1�

    Remedy 2:-

    1. Login to node. Check which RU is working as sync source in �get


    NodeGroupSyncMember=1�.

    2. Check �acl NodeGroupSyncMember=1� & �acc NodeGroupSyncMember=1


    retryEntranceToNodeGroup�

    Remedy 3:-

    1. Login to node. Check which RU is working as sync source in �get


    NodeGroupSyncMember=1�.
    2. And restart the RRU only.

    Remedy 4:-

    1. Login to node. And restart the node with latest CV.

    NGS creation in DUS/DUW:

    UHY3080> cr TransportNetwork=1,Synchronization=1,NodeGroupSyncMember=1

    160929-18:09:28 10.195.113.50 16.0n RBS_NODE_MODEL_U_4_340 stopfile=/tmp/2270

    Attribute 1 of 2, syncNodePriority (long): 3

    Attribute 2 of 2, syncRiPortCandidate (sequence:structRef-SyncRiPort):


    dunumber=1,duriport=4;dunumber=1,duriport=5;dunumber=1,duriport=6

    >>> [Proxy ID = 1949] MO name


    :ManagedElement=1,TransportNetwork=1,Synchronization=1,NodeGroupSyncMember=1

    UHY3080> get 1949

    160929-18:09:53 10.195.113.50 16.0n RBS_NODE_MODEL_U_4_340 stopfile=/tmp/2270


    ===================================================================================
    ==============================
    1949
    TransportNetwork=1,Synchronization=1,NodeGroupSyncMember=1
    ===================================================================================
    ==============================
    NodeGroupSyncMemberId 1
    administrativeState 0 (LOCKED)
    localNodeInformation Struct{4}
    >>> 1.hopsFromSyncProvider = 0
    >>> 2.localStatus = 0 (UNKNOWN)
    >>> 3.neighborNodePriority = 3
    >>> 4.syncToNodeName = NO_NAME
    syncNodePriority 3
    syncProviderInformation Struct{3}
    >>> 1.spNodeName = NO_NAME
    >>> 2.spNodePriority = 3
    >>> 3.spState = 0 (UNKNOWN)
    syncRiPortCandidate t[3] =
    >>> Struct[0] has 2 members:
    >>> 1.duNumber = 1
    >>> 2.duRiPort = 4 (RI_PORT_D)
    >>> Struct[1] has 2 members:
    >>> 1.duNumber = 1
    >>> 2.duRiPort = 5 (RI_PORT_E)
    >>> Struct[2] has 2 members:
    >>> 1.duNumber = 1
    >>> 2.duRiPort = 6 (RI_PORT_F)
    syncRiPortStatus i[3] = 0 0 0 (UNKNOWN UNKNOWN UNKNOWN)
    userLabel
    ===================================================================================
    ==============================
    Total: 1 MOs

    UHY3080> deb 1949

    160929-18:09:59 10.195.113.50 16.0n RBS_NODE_MODEL_U_4_340 stopfile=/tmp/2270


    Deblock following 1 MOs ?
    ===================================================================================
    1949 TransportNetwork=1,Synchronization=1,NodeGroupSyncMember=1
    ===================================================================================
    Deblock 1 MOs. Are you Sure [y/n] ? y

    ===================================================================================
    =========================
    Id MO
    administrativeState Result
    ===================================================================================
    =========================
    1949 Synchronization=1,NodeGroupSyncMember=1 1
    >>> Set.
    ===================================================================================
    =========================
    Total: 1 MOs attempted, 1 MOs set

    UHY3080> get . nodegroup

    160929-18:10:07 10.195.113.50 16.0n RBS_NODE_MODEL_U_4_340 stopfile=/tmp/2270


    ===================================================================================
    ==============================
    MO Attribute Value
    ===================================================================================
    ==============================
    Synchronization=1 nodeGroupRole 3
    (SYNC_RECEIVER)
    Synchronization=1,NodeGroupSyncMember=1 NodeGroupSyncMemberId 1
    ===================================================================================
    ==============================
    Total: 2 MOs

    NGS creation in BB nodes:

    cr Transport=1,Synchronization=1,RadioEquipmentClock=1,NodeGroupSyncMember=1
    Equipment=1,FieldReplaceableUnit=DU-1,RiPort=D Equipment=1,FieldReplaceableUnit=DU-
    1,RiPort=E Equipment=1,FieldReplaceableUnit=DU-1,RiPort=F

    You might also like