OAI eNodeB usable with Magma?

[Doug A.]

Hi, I've got Magma installed and set up, and I'd like to do further testing with a USRP-based OAI eNodeB that I've previously configured.

I see mentions in your documentation about using an eNodeB without TR-069, but has anyone tried this yet? What do you think the major hurdles would be if not?

Best,

-Doug

[Anoop Tomar]

Hi Doug,

Yes this has been tried successfully. I used OAI eNB with B210 SDR
with magma to do attach and data transfer. Since OAI eNB does not
support TR69 so you need to manually configure MME IP address, TAC ,
PLMN id , EARFCN etc using OAI eNB configuration file and then first
run magma and the run OAI eNB and that will lead to successful SCTP
association establishment followed by S1Setup. After this you can
attach UE and do data xfer,.

Thanks,
Anoop

> --
> You received this message because you are subscribed to the Google Groups "magma-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to magma-dev+...@googlegroups.com.
> To post to this group, send email to magm...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/magma-dev/99fcfd5d-6043-4a54-83fd-1a6f55ec49bf%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[douglasj...@gmail.com]

Anoop,

Thanks for that info. I was wondering if I could get a bit more detail on this.

What I've done so far is to is to modify my OAI eNB conf file MME section to look like this:

    ////////// MME parameters:
    mme_ip_address      = ( { ipv4       = "192.168.60.141";
                              ipv6       = "";
                              active     = "yes";
                              preference = "ipv4";
                            }
                          );

    NETWORK_INTERFACES :
    {
        ENB_INTERFACE_NAME_FOR_S1_MME            = "lo";
        ENB_IPV4_ADDRESS_FOR_S1_MME              = "192.168.60.141";
        ENB_INTERFACE_NAME_FOR_S1U               = "lo";
        ENB_IPV4_ADDRESS_FOR_S1U                 = "127.0.0.1";
        ENB_PORT_FOR_S1U                         = 2152; # Spec 2152
    };
  }
);

Where the MME ip is the `private_network` address stated in the gateway Vagrantfile.

Then I change `magma/lte/gateway/configs/mme.yml` `s1ap_iface_name` from `eth1` to `lo`, and changed the `gateway.mconfig` `mme` section to reflect the settings in my eNB config.

Am I on the right track? What else do I need to modify what should I be looking for in the gateway logs that reflect `S1Setup`?

Thanks,

-Doug

On Friday, June 7, 2019 at 7:43:22 PM UTC-6, Anoop Tomar wrote:

Hi Doug,

Yes this has been tried successfully.  I used OAI eNB with B210 SDR
with magma to do attach and data transfer. Since OAI eNB does not
support TR69 so you need to manually configure MME IP address, TAC ,
PLMN id , EARFCN etc using OAI eNB configuration file and then first
run magma and the run OAI eNB and that will lead to successful SCTP
association establishment followed by S1Setup. After this you can
attach UE and do data xfer,.

Thanks,
Anoop

On Fri, Jun 7, 2019 at 2:42 PM Doug A. <douglasj...@gmail.com> wrote:
>
> Hi, I've got Magma installed and set up, and I'd like to do further testing with a USRP-based OAI eNodeB that I've previously configured.
>
> I see mentions in your documentation about using an eNodeB without TR-069, but has anyone tried this yet? What do you think the major hurdles would be if not?
>
> Best,
> -Doug
>
> --
> You received this message because you are subscribed to the Google Groups "magma-dev" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to magm...@googlegroups.com.

[Anoop Tomar]

Hi Doug,

Sorry for delayed response:

If you enable DEBUG log in MME then you should see following after
successful SCTP and S1AP setup

000300 Fri Jun 21 00:45:08 2019 7FE0D69B3700 DEBUG S1AP
tasks/s1ap/s1ap_mme_handlers.c :1813 Create eNB context for
assoc_id: 24
000301 Fri Jun 21 00:45:08 2019 7FE0D69B3700 DEBUG S1AP
tasks/s1ap/r10.5/s1ap_decoder.c :7227 Decoding message
S1ap_S1SetupRequestIEs
(/home/admin/build/c/oai/tasks/s1ap/r10.5/s1ap_decoder.c:7227)
000302 Fri Jun 21 00:45:08 2019 7FE0D69B3700 DEBUG S1AP
tasks/s1ap/s1ap_mme_handlers.c :0399 New s1 setup request incoming
from home eNB id: 84591a8
000303 Fri Jun 21 00:45:08 2019 7FE0D69B3700 DEBUG S1AP
tasks/s1ap/s1ap_mme_handlers.c :0497 Adding eNB to the list of
served eNBs
000304 Fri Jun 21 00:45:08 2019 7FE0D99B9700 ERROR SCTP
tasks/sctp/sctpd_downlink_client:0172 rc = 0
000305 Fri Jun 21 00:45:18 2019 7FE0DA9BB700 DEBUG MME-AP
tasks/mme_app/mme_app_statistics:0032
======================================= STATISTICS
============================================

000306 Fri Jun 21 00:45:18 2019 7FE0DA9BB700 DEBUG MME-AP
tasks/mme_app/mme_app_statistics:0036 | Current
Status| Added since last display| Removed since last display |
000307 Fri Jun 21 00:45:18 2019 7FE0DA9BB700 DEBUG MME-AP
tasks/mme_app/mme_app_statistics:0043 Connected eNBs | 1
| 1 | 0 |
000308 Fri Jun 21 00:45:18 2019 7FE0DA9BB700 DEBUG MME-AP
tasks/mme_app/mme_app_statistics:0050 Attached UEs | 0
| 0 | 0 |
000309 Fri Jun 21 00:45:18 2019 7FE0DA9BB700 DEBUG MME-AP
tasks/mme_app/mme_app_statistics:0057 Connected UEs | 0
| 0 | 0 |
000310 Fri Jun 21 00:45:18 2019 7FE0DA9BB700 DEBUG MME-AP
tasks/mme_app/mme_app_statistics:0064 Default Bearers| 0
| 0 | 0 |
000311 Fri Jun 21 00:45:18 2019 7FE0DA9BB700 DEBUG MME-AP
tasks/mme_app/mme_app_statistics:0071 S1-U Bearers | 0
| 0 | 0 |
Thanks,
Anoop

> To unsubscribe from this group and stop receiving emails from it, send an email to magma-dev+...@googlegroups.com.

> To post to this group, send email to magm...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/magma-dev/f23543b8-2cfb-4df3-97df-39ec76df7fc6%40googlegroups.com.

[tan...@gmail.com]

Hi Anoop,

I'm trying the similar setup with OAI eNB + Magma AGW and come across your post. I managed to see the successful S1AP setup. However, the connection is dropped afterward. Do you happen to know the reason? I've posted the MME log here. Thanks!

Best,

Zhaowei

000490 Fri Aug 23 20:55:54 2019 7FF76170F700 DEBUG S1AP   tasks/s1ap/s1ap_mme_handlers.c  :1948      Create eNB context for assoc_id: 50

000491 Fri Aug 23 20:55:54 2019 7FF76170F700 DEBUG S1AP   tasks/s1ap/r10.5/s1ap_decoder.c :7227      Decoding message S1ap_S1SetupRequestIEs (/home/vagrant/build/c/oai/tasks/s1ap/r10.5/s1ap_decoder.c:7227)

000492 Fri Aug 23 20:55:54 2019 7FF76170F700 DEBUG S1AP   tasks/s1ap/s1ap_mme_handlers.c  :0402      New s1 setup request incoming from eNB-Eurecom-LTEBox macro eNB id: 00e00
000493 Fri Aug 23 20:55:54 2019 7FF76170F700 DEBUG S1AP   tasks/s1ap/s1ap_mme_handlers.c  :0500      Adding eNB to the list of served eNBs

000494 Fri Aug 23 20:55:54 2019 7FF7647B4700 ERROR SCTP   tasks/sctp/sctpd_downlink_client:0172    rc = 0

000495 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0032    ======================================= STATISTICS ============================================


000496 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0036                   |   Current Status| Added since last display|  Removed since last display |

000497 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0043    Connected eNBs |          1      |      1              |             0               |

000498 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0050    Attached UEs   |          0      |         0              |             0               |

000499 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0057    Connected UEs  |          0      |       0              |             0               |

000500 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0064    Default Bearers|          0      |         0              |             0               |

000501 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0071    S1-U Bearers   |          0      |          0              |             0               |


000502 Fri Aug 23 20:55:55 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0075    ======================================= STATISTICS ============================================


000503 Fri Aug 23 20:55:57 2019 7FF76170F700 INFO  S1AP   tasks/s1ap/s1ap_mme_handlers.c  :1826      SCTP disconnection request for association id 50. Reset Flag = 0 

000504 Fri Aug 23 20:55:57 2019 7FF76170F700 INFO  S1AP   tasks/s1ap/s1ap_mme_handlers.c  :1839      SCTP disconnection request for association id 50. Reset Flag = 0.Connected UEs = 0 

000505 Fri Aug 23 20:55:57 2019 7FF76170F700 INFO  S1AP   tasks/s1ap/s1ap_mme_handlers.c  :1862      SCTP Shutdown request for association id 50. No Connected UEs.  = 0 

000506 Fri Aug 23 20:55:57 2019 7FF76170F700 INFO  S1AP   tasks/s1ap/s1ap_mme_handlers.c  :1863      Removing eNB with association id 50 

000507 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0032    ======================================= STATISTICS ============================================


000508 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0036                   |   Current Status| Added since last display|  Removed since last display |

000509 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0043    Connected eNBs |          0      |      0              |             1               |

000510 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0050    Attached UEs   |          0      |         0              |             0               |

000511 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0057    Connected UEs  |          0      |       0              |             0               |

000512 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0064    Default Bearers|          0      |         0              |             0               |

000513 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0071    S1-U Bearers   |          0      |          0              |             0               |


000514 Fri Aug 23 20:56:05 2019 7FF7657B6700 DEBUG MME-AP tasks/mme_app/mme_app_statistics:0075    ======================================= STATISTICS ===============================

[amar padmanabhan]

Can you upload the pcap?
Thanks

Amar

To unsubscribe from this group and stop receiving emails from it, send an email to magma-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/magma-dev/4fea764b-27ee-4986-a7b6-3614b34539ab%40googlegroups.com.

[tan...@gmail.com]

Hi Amar,

Thanks so much for the reply. Your question gives me the hint and I manage to solve the issue. Attached is the output of `sudo tcpdump -i any | grep sctp`. I used the `lo` interface from my OAI eNB, and as a result, the AGW tried to send SCTP packets back to a 127.0.x.x address which cannot be received by the eNB. I now modify the eNB configuration such that it uses `vboxnet2` interface with IP address 192.168.60.1. This solves the issue.

Cheers,

Zhaowei

21:19:36.654774 IP 192.168.60.1.50822 > 192.168.60.142.36412: sctp (1) [INIT] [init tag: 3480168420] [rwnd: 106496] [OS: 2] [MIS: 2] [init TSN: 2356229268] 
21:19:36.654821 IP 192.168.60.142.36412 > 192.168.60.1.50822: sctp (1) [INIT ACK] [init tag: 3542946740] [rwnd: 106496] [OS: 2] [MIS: 2] [init TSN: 3077050898] 
21:19:36.654861 IP 192.168.60.1.50822 > 192.168.60.142.36412: sctp (1) [COOKIE ECHO] 
21:19:36.654889 IP 192.168.60.142.36412 > 192.168.60.1.50822: sctp (1) [COOKIE ACK] 
21:19:36.655045 IP 192.168.60.1.50822 > 192.168.60.142.36412: sctp (1) [DATA] (B)(E) [TSN: 2356229268] [SID: 0] [SSEQ 0] [PPID S1AP] 
21:19:36.655053 IP 192.168.60.142.36412 > 192.168.60.1.50822: sctp (1) [SACK] [cum ack 2356229268] [a_rwnd 106437] [#gap acks 0] [#dup tsns 0] 
21:19:38.987899 IP 192.168.60.142.36412 > 172.18.0.1.50822: sctp (1) [HB REQ] 
21:19:39.505233 IP 192.168.60.142.36412 > 172.17.0.1.50822: sctp (1) [HB REQ] 
21:19:40.523838 IP 192.168.60.142.36412 > 192.168.129.1.50822: sctp (1) [HB REQ] 
21:19:40.523849 IP 192.168.129.1.50822 > 192.168.60.142.36412: sctp (1) [ABORT] 
21:20:02.681856 IP 192.168.60.1.50822 > 192.168.60.142.36412: sctp (1) [SHUTDOWN] 
21:20:02.681894 IP 192.168.60.142.36412 > 192.168.60.1.50822: sctp (1) [ABORT]

To unsubscribe from this group and stop receiving emails from it, send an email to magm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/magma-dev/4fea764b-27ee-4986-a7b6-3614b34539ab%40googlegroups.com.

[amar padmanabhan]

Awesome! Thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to magma-dev+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/magma-dev/c7a290ab-bc67-4fc8-acf6-6f833a8e560f%40googlegroups.com.

[Virgínia Tavares]

Hi Zhaowei
Can you tell me what exactly .conf you changed? Like what information matches between MAGMA AWG and OAI EnB. 

Thanks,
Virgínia.

[ZHAOWEI TAN]

Hi Virgínia,

You probably want to make sure the orchestrator talks to your gateway first. After that,

On eNB side, I modify the MCC and MNC config in plmn_list and tracking_area_code so that they match the config in AGW. I also modified mme_ip_address to 192.168.60.142, which is the IP for "eth1" interface of AGW. Then I changed the address in "network_interfaces" so that the local eNB binds to "vboxnet2" and "192.168.60.1".

On EPC side, I modify the MCC, MNC, and tracking area code as well so that they match those in eNB. These configs can be modified in NMS easily. I create an eNB device in NMS with the same eNB ID and TAC in your OAI eNB's config file.  Other than that I didn't touch anything as I could remember.

The SCTP connection still occasionally fails although it works most of the time. Please let me know if you still cannot make them connected or you find some other configs that I miss.

Thanks,

Zhaowei

You also have to make sure that the eNB