-
Bug
-
Resolution: Done
-
Low
-
None
-
None
-
None
In order to test for hello world xapp in Rust, I am trying to get a subscription from a simulated E2 node. However, I am observing following error with DEBUG enabled on the e2term.
{"ts":1683637419870,"crit":"DEBUG","id":"E2Terminator","mdc":{"PID":"139787897927424","POD_NAME":"deployment-ricplt-e2term-alpha-59cbfdbf76-4sb6j","CONTAINER_NAME":"container-ricplt-e2term","SERVICE_NAME":"RIC_E2_TERM","HOST_NAME":"minikube","SYSTEM_NAME":"SEP"},"msg":"PDU buffer length = 45, data = : 000600290000010032002200000033001c0000e06e676"} {"ts":1683637419870,"crit":"ERROR","id":"E2Terminator","mdc":{"PID":"139787897927424","POD_NAME":"deployment-ricplt-e2term-alpha-59cbfdbf76-4sb6j","CONTAINER_NAME":"container-ricplt-e2term","SERVICE_NAME":"RIC_E2_TERM","HOST_NAME":"minikube","SYSTEM_NAME":"SEP"},"msg":"Error 2 Decoding (unpack) E2AP PDU from RAN : "} {"ts":1683637419870,"crit":"DEBUG","id":"E2Terminator","mdc":{"PID":"139787897927424","POD_NAME":"deployment-ricplt-e2term-alpha-59cbfdbf76-4sb6j","CONTAINER_NAME":"container-ricplt-e2term","SERVICE_NAME":"RIC_E2_TERM","HOST_NAME":"minikube","SYSTEM_NAME":"SEP"},"msg":"from receive SCTP to send RMR time is 0 seconds and 446243 nanoseconds"}
The corresponding logs on the e2sim -
Unable to find source-code formatter for language: shell. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml Starting KPM processor simJSON Test <E2SM-KPM-RANfunction-Description> <ranFunction-Name> <ranFunction-ShortName>ORAN-E2SM-KPM</ranFunction-ShortName> <ranFunction-E2SM-OID>OID123</ranFunction-E2SM-OID> <ranFunction-Description>KPM monitor</ranFunction-Description> <ranFunction-Instance>1</ranFunction-Instance> </ranFunction-Name> <e2SM-KPM-RANfunction-Item> <ric-EventTriggerStyle-List> <RIC-EventTriggerStyle-List> <ric-EventTriggerStyle-Type>1</ric-EventTriggerStyle-Type> <ric-EventTriggerStyle-Name>Periodic report</ric-EventTriggerStyle-Name> <ric-EventTriggerFormat-Type>5</ric-EventTriggerFormat-Type> </RIC-EventTriggerStyle-List> </ric-EventTriggerStyle-List> <ric-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>1</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-DU Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>2</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-DU Measurement Container for the EPC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>3</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-CP Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>4</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-CP Measurement Container for the EPC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>5</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-UP Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>6</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-UP Measurement Container for the EPC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> </ric-ReportStyle-List> </e2SM-KPM-RANfunction-Item> </E2SM-KPM-RANfunction-Description> er encded is 489 after encoding message here is encoded message �ORAN-E2SM-KPM %%about to register callback for subscription for func_id 0 <E2AP-PDU> <initiatingMessage> <procedureCode>6</procedureCode> <criticality><reject/></criticality> <value> <E2nodeConfigurationUpdate> <protocolIEs> <E2nodeConfigurationUpdate-IEs> <id>50</id> <criticality><reject/></criticality> <value> <E2nodeComponentConfigAddition-List> <ProtocolIE-SingleContainer> <id>51</id> <criticality><reject/></criticality> <value> <E2nodeComponentConfigAddition-Item> <e2nodeComponentInterfaceType><ng/></e2nodeComponentInterfaceType> <e2nodeComponentID> <e2nodeComponentInterfaceTypeNG> <amf-name>nginterf</amf-name> </e2nodeComponentInterfaceTypeNG> </e2nodeComponentID> <e2nodeComponentConfiguration> <e2nodeComponentRequestPart>72 65 71 70 61 72 74</e2nodeComponentRequestPart> <e2nodeComponentResponsePart>72 65 73 70 61 72 74</e2nodeComponentResponsePart> </e2nodeComponentConfiguration> </E2nodeComponentConfigAddition-Item> </value> </ProtocolIE-SingleContainer> </E2nodeComponentConfigAddition-List> </value> </E2nodeConfigurationUpdate-IEs> </protocolIEs> </E2nodeConfigurationUpdate> </value> </initiatingMessage> </E2AP-PDU> er encded is 45 in sctp send data func data.len is 45after getting sent_len receive data1 receive data2
naman.gupta / subhash_singh Can you please upload logs from e2term and e2sim to this issue? So that I can debug this issue.
Adding my logs here
E2sim logs :
kpm0 kpm0.9 kpm2 kpm3 ret is 0 kpm4 kpm5 kpm6 this is the char array �ORAN-E2SM-KPM !!!lenth of ranfuncdesc is 15 value of this index is 32 value of this index is 192 value of this index is 79 value of this index is 82 value of this index is 65 value of this index is 78 value of this index is 45 value of this index is 77 value of this index is 0 value of this index is 32 value of this index is 102 %%about to register e2sm func desc for 0 Start E2 Agent (E2 Simulator After reading input options [SCTP] Binding client socket to source port 36422 [SCTP] Connecting to server at 10.106.115.53:36422 ... [SCTP] Connection established After starting client client_fd value is 3 looping through ran func about to call setup request encode After generating e2setup req After XER Encoding error length 0 error buf [SCTP] Sent E2-SETUP-REQUEST about to call E2ResetRequest encode [E2AP] Created E2ResetRequest before <E2AP-PDU> <initiatingMessage> <procedureCode>3</procedureCode> <criticality><reject/></criticality> <value> <ResetRequest> <protocolIEs> <ResetRequestIEs> <id>49</id> <criticality><ignore/></criticality> <value> <TransactionID>1</TransactionID> </value> </ResetRequestIEs> <ResetRequestIEs> <id>49</id> <criticality><ignore/></criticality> <value> <TransactionID>2</TransactionID> </value> </ResetRequestIEs> </protocolIEs> </ResetRequest> </value> </initiatingMessage> </E2AP-PDU> Starting KPM processor simJSON Test <E2SM-KPM-RANfunction-Description> <ranFunction-Name> <ranFunction-ShortName>ORAN-E2SM-KPM</ranFunction-ShortName> <ranFunction-E2SM-OID>OID123</ranFunction-E2SM-OID> <ranFunction-Description>KPM monitor</ranFunction-Description> <ranFunction-Instance>1</ranFunction-Instance> </ranFunction-Name> <e2SM-KPM-RANfunction-Item> <ric-EventTriggerStyle-List> <RIC-EventTriggerStyle-List> <ric-EventTriggerStyle-Type>1</ric-EventTriggerStyle-Type> <ric-EventTriggerStyle-Name>Periodic report</ric-EventTriggerStyle-Name> <ric-EventTriggerFormat-Type>5</ric-EventTriggerFormat-Type> </RIC-EventTriggerStyle-List> </ric-EventTriggerStyle-List> <ric-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>1</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-DU Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>2</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-DU Measurement Container for the EPC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>3</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-CP Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>4</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-CP Measurement Container for the EPC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>5</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-UP Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> <RIC-ReportStyle-List> <ric-ReportStyle-Type>6</ric-ReportStyle-Type> <ric-ReportStyle-Name>O-CU-UP Measurement Container for the EPC connected deployment</ric-ReportStyle-Name> <ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type> <ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type> </RIC-ReportStyle-List> </ric-ReportStyle-List> </e2SM-KPM-RANfunction-Item> </E2SM-KPM-RANfunction-Description> er encded is 489 after encoding message here is encoded message �ORAN-E2SM-KPM %%about to register callback for subscription for func_id 0 <E2AP-PDU> <initiatingMessage> <procedureCode>1</procedureCode> <criticality><reject/></criticality> <value> <E2setupRequest> <protocolIEs> <E2setupRequestIEs> <id>49</id> <criticality><reject/></criticality> <value> <TransactionID>1</TransactionID> </value> </E2setupRequestIEs> <E2setupRequestIEs> <id>3</id> <criticality><reject/></criticality> <value> <GlobalE2node-ID> <gNB> <global-gNB-ID> <plmn-id>37 34 37</plmn-id> <gnb-id> <gnb-ID> 10110101110001100111011110001 </gnb-ID> </gnb-id> </global-gNB-ID> </gNB> </GlobalE2node-ID> </value> </E2setupRequestIEs> <E2setupRequestIEs> <id>10</id> <criticality><reject/></criticality> <value> <RANfunctions-List> <ProtocolIE-SingleContainer> <id>8</id> <criticality><reject/></criticality> <value> <RANfunction-Item> <ranFunctionID>0</ranFunctionID> <ranFunctionDefinition> 20 C0 4F 52 41 4E 2D 45 32 53 4D 2D 4B 50 4D 00 00 05 4F 49 44 31 32 33 05 00 4B 50 4D 20 6D 6F 6E 69 74 6F 72 08 80 FF DC 62 0F 70 A3 00 60 00 01 01 07 00 50 65 72 69 6F 64 69 63 20 72 65 70 6F 72 74 01 05 14 01 01 1D 00 4F 2D 44 55 20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20 66 6F 72 20 74 68 65 20 35 47 43 20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74 01 01 01 01 00 01 02 1D 00 4F 2D 44 55 20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20 66 6F 72 20 74 68 65 20 45 50 43 20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74 01 01 01 01 00 01 03 1E 80 4F 2D 43 55 2D 43 50 20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20 66 6F 72 20 74 68 65 20 35 47 43 20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74 01 01 01 01 00 01 04 1E 80 4F 2D 43 55 2D 43 50 20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20 66 6F 72 20 74 68 65 20 45 50 43 20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74 01 01 01 01 00 01 05 1E 80 4F 2D 43 55 2D 55 50 20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20 66 6F 72 20 74 68 65 20 35 47 43 20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74 01 01 01 01 00 01 06 1E 80 4F 2D 43 55 2D 55 50 20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20 66 6F 72 20 74 68 65 20 45 50 43 20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74 01 01 01 01 </ranFunctionDefinition> <ranFunctionRevision>2</ranFunctionRevision> <ranFunctionOID>OID123</ranFunctionOID> </RANfunction-Item> </value> </ProtocolIE-SingleContainer> </RANfunctions-List> </value> </E2setupRequestIEs> <E2setupRequestIEs> <id>50</id> <criticality><reject/></criticality> <value> <E2nodeComponentConfigAddition-List> <ProtocolIE-SingleContainer> <id>51</id> <criticality><reject/></criticality> <value> <E2nodeComponentConfigAddition-Item> <e2nodeComponentInterfaceType><ng/></e2nodeComponentInterfaceType> <e2nodeComponentID> <e2nodeComponentInterfaceTypeNG> <amf-name>nginterf</amf-name> </e2nodeComponentInterfaceTypeNG> </e2nodeComponentID> <e2nodeComponentConfiguration> <e2nodeComponentRequestPart>72 65 71 70 61 72 74</e2nodeComponentRequestPart> <e2nodeComponentResponsePart>72 65 73 70 61 72 74</e2nodeComponentResponsePart> </e2nodeComponentConfiguration> </E2nodeComponentConfigAddition-Item> </value> </ProtocolIE-SingleContainer> </E2nodeComponentConfigAddition-List> </value> </E2setupRequestIEs> </protocolIEs> </E2setupRequest> </value> </initiatingMessage> </E2AP-PDU> er encded is 581 in sctp send data func data.len is 581after getting sent_len er encoded is 19 in sctp send data func data.len is 19after getting sent_len receive data1 receive data2 receive data3 in e2ap_handle_sctp_data() decoding... full buffer length of data 60 result 0 index is 2 showing xer of data <E2AP-PDU> <successfulOutcome> <procedureCode>1</procedureCode> <criticality><reject/></criticality> <value> <E2setupResponse> <protocolIEs> <E2setupResponseIEs> <id>49</id> <criticality><reject/></criticality> <value> <TransactionID>1</TransactionID> </value> </E2setupResponseIEs> <E2setupResponseIEs> <id>4</id> <criticality><reject/></criticality> <value> <GlobalRIC-ID> <pLMN-Identity>13 10 14</pLMN-Identity> <ric-ID> 10101010110011001110 </ric-ID> </GlobalRIC-ID> </value> </E2setupResponseIEs> <E2setupResponseIEs> <id>9</id> <criticality><reject/></criticality> <value> <RANfunctionsID-List> <ProtocolIE-SingleContainer> <id>6</id> <criticality><ignore/></criticality> <value> <RANfunctionID-Item> <ranFunctionID>0</ranFunctionID> <ranFunctionRevision>2</ranFunctionRevision> </RANfunctionID-Item> </value> </ProtocolIE-SingleContainer> </RANfunctionsID-List> </value> </E2setupResponseIEs> <E2setupResponseIEs> <id>52</id> <criticality><reject/></criticality> <value> <E2nodeComponentConfigAdditionAck-List> <ProtocolIE-SingleContainer> <id>53</id> <criticality><reject/></criticality> <value> <E2nodeComponentConfigAdditionAck-Item> <e2nodeComponentInterfaceType><ng/></e2nodeComponentInterfaceType> <e2nodeComponentID> <e2nodeComponentInterfaceTypeNG> <amf-name>nginterf</amf-name> </e2nodeComponentInterfaceTypeNG> </e2nodeComponentID> <e2nodeComponentConfigurationAck> <updateOutcome><success/></updateOutcome> </e2nodeComponentConfigurationAck> </E2nodeComponentConfigAdditionAck-Item> </value> </ProtocolIE-SingleContainer> </E2nodeComponentConfigAdditionAck-List> </value> </E2setupResponseIEs> </protocolIEs> </E2setupResponse> </value> </successfulOutcome> </E2AP-PDU> receive data1 receive data2 |
E2-term logs: