Thanks Thanks:  8
Showing results 1 to 6 of 6

Thread: Moshell problem: MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociation"

  1. #1
    Member Reputation: 93
    Join Date
    2010-04-14
    Location
    Mexico DF
    Posts
    106


    Default Moshell problem: MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociation"

    Dear Experts,

    Do you know how to solve the problem when MO typename and FRO typename are differents??


    Many thanks,

    Ivan

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Location
    Advertising world
    Posts
    Many
     

  3. #2
    Member Reputation: 37
    Join Date
    2013-06-27
    Posts
    17


    Default Re: Moshell problem: MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociati

    Hi
    What is the issue ? is it that you can not read the MO M3uAssociation and its attributes ?
    One solution could be to change the fro table with the sqlc command and one it is done create a new CV, However that this operation is not recommended on a live node

    BR/Casa

  4. #3
    Member Reputation: 93
    Join Date
    2010-04-14
    Location
    Mexico DF
    Posts
    106


    Default Re: Moshell problem: MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociati

    Dear,

    The problem is than I'm trying to create a M3uAssociation and I got this error

    !!!! Processing failure :se.e*******.cello.moframework.FroRequestFailedException TAG :"FroRequestFailed" VARIABLES :"$MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociation", "$Request type" = "CreateFroReq: UNKNOWN RESULT CODE: 71", "$result" = "71"

    Below the Moshell commands used:

    RNCSCB03> run /home/e06262/CreateCS1.mos


    RNCSCB03>


    RNCSCB03> confb+


    Confirmation of bl/deb/set/acc commands = disabled


    RNCSCB03> gs+


    Perform a get before set = enabled


    RNCSCB03>


    RNCSCB03> cr TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=MSS_M3UA1


    130626-01:12:52 10.53.181.165 9.0g RNC_NODE_MODEL_M_1_150 stopfile=/tmp/17089


    Attribute 1 of 3, mtp3bSrsId (moRef:Mtp3bSrs):
    Enter mo LDN: Mtp3bSpItu=1,Mtp3bSrs=Mtp3bSrs_MSS_10570 #mtp3bSrsId


    Attribute 2 of 3, remoteIpAddress1 (string): 10.19.51.78 #remoteIpAddress1


    Attribute 3 of 3, sctpId (moRef:Sctp):
    Enter mo LDN: Sctp=SCTP0 #sctpId


    Following attributes are optional. Enter attribute value or "d" for default.
    Once the MO is created, these attributes cannot be changed (they are restricted).


    Attribute 1 of 7, autoStartAssociation (boolean): true #autoStartAssociation


    Attribute 2 of 7, dscp (long): 34 #dscp


    Attribute 3 of 7, localIpMask (enumRef:HomingState):
    Enter one of the following integers: 1:SINGLE_HOMED_1, 2:SINGLE_HOMED_2, 3:MULTI_HOMED: 3 #localIpMask


    Attribute 4 of 7, localPortNumber (long): 2905 #localPortNumber


    Attribute 5 of 7, remoteIpAddress2 (string): 10.19.50.78 #remoteIpAddress2


    Attribute 6 of 7, remotePortNumber (long): 1024 #remotePortNumber


    Attribute 7 of 7, role (enumRef:M3uAssociationRole):
    Enter one of the following integers: 0:CLIENT, 1:SERVER: 0 #role


    !!!! Processing failure :se.e*******.cello.moframework.FroRequestFailedException TAG :"FroRequestFailed" VARIABLES :"$MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociation", "$Request type" = "CreateFroReq: UNKNOWN RESULT CODE: 71", "$result" = "71"


    RNCSCB03> lset TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=MSS_M3UA1$ congestionAlarmThreshold 50


    130626-01:12:53 10.53.181.165 9.0g RNC_NODE_MODEL_M_1_150 stopfile=/tmp/17089


    ============================================================================================================
    Id MO congestionalarmthreshold Result
    ============================================================================================================
    ============================================================================================================
    Total: 0 MOs attempted, 0 MOs set


    RNCSCB03> lset TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=MSS_M3UA1$ userLabel M3uAssociation_MSS_M3UA1


    130626-01:12:53 10.53.181.165 9.0g RNC_NODE_MODEL_M_1_150 stopfile=/tmp/17089


    ============================================================================================================
    Id MO userlabel Result
    ============================================================================================================
    ============================================================================================================
    Total: 0 MOs attempted, 0 MOs set


    How to solve it??

    Thanks in advance,

    JB

  5. #4
    Member Reputation: 37
    Join Date
    2013-06-27
    Posts
    17


    1 out of 1 members found this post helpful.

    Default Re: Moshell problem: MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociati

    One reason for the fault is that the dscp value you are setting is not valid :
    is there any other M3uAssociation using the same Sctp=SCTP0 ? , if yes then the dscp used for that MO should be also used for the MO M3uAssociation=MSS_M3UA1 that you are trying to create.
    The reason is that dscp value is common for all M3UA association using the same SCTP endpoint.

    if that does not help, can you get the te log read logs from the node ?

  6. #5
    Member Reputation: 93
    Join Date
    2010-04-14
    Location
    Mexico DF
    Posts
    106


    Default Re: Moshell problem: MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociati

    Thanks Casa,

    There are more M3UA using the same SCTP and local port number. I'll try to delete all, then create all.

    How to get the logs in case of continue the problem?

    BR,

    Ivan

  7. #6
    Member Reputation: 37
    Join Date
    2013-06-27
    Posts
    17


    Default Re: Moshell problem: MO typename" = "M3uAssociation", "$FRO typename" = "M3UAssociati

    Hi
    you can start with $te log read command from the central mp and if you are using moshell >lh mp te log read
    Br/Casa

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •