Platform for building access networks and modular network services
The 1.7.0 release adds new features and fixes some of the known issues with previous releases. Please see the test report for more information. Note that new features follow these maturity definitions as it pertains to alpha, beta, or GA.
The IPv6 pool allocation changes allow the assignment of a block of IPv6 prefixes for user devices. This feature also enables IPv6 static allocation to enable the assignment of an IPv6 prefix to an IMSI in subscriberDB. With this new implementation, Magma will support IPv4, IPv4v6, and IPv6 APN types. Documentation can be found here.
One of the focus areas for the 1.7 release of Magma is to introduce the 5G SA core network components. From the grounds up it is designed with flexibility, reusability and keeping cloud native technologies in mind. This release puts up the foundation for 5G core network technologies which will be used in upcoming releases to provide end-to-end solutions for various deployments. Since this is an alpha feature, review the known issues section of the notes and test report prior to using this feature. Documentation is available for swagger implementation and headless install and support is available in the Wavelabs 5G Slack channel. Key features include:
5G NSA bridges the connectivity gap between a 5G compatible UE and the magma core. This feature was previously released in v1.5 but enhancements and updates have been made to supplementary messages, layers and services. Further details are available here.
This feature enables containerized access gateways that are deployed via docker-compose files and orchestrated by Kubernetes. This feature can be deployed via Amazon Web Services. This is an alpha feature and can be prone to bugs. If you experience library dependency issues, backport this pull request or utilize the Slack channel. Documentation can be found here.
GPRS Tunneling Protocol echo requests are used for path management purposes and error indication messages for exception handling. Error indication messages can be used to inform the other GTP entity that there is no EPS bearer from a received user-plane packet.
Roaming support allows mobile users from one operator network to access services while visiting areas outside their network coverage. This can support multiple scenarios. Magma Partner Network uses Magma services for MME, HSS(Subscriberdb), SGW, PGW, and provides local breakout of data traffic. Roaming Partner Network uses all non-Magma services, and provides “federation” for S6a and S8 interface to support RPN users roaming to MPN network. Feature documentation can be found here.
The Domain Proxy feature is an application whose purpose is to communicate to eNodeBs with SAS, send requests to SAS, on their behalf, and maintain their desired state. Documentation can be found here.
Previously, each AGW on inbound roaming had its own GTP-U interface which means that on networks with multiple AGWs, the remote PGW will have to be configured each time a new AGW is added. To solve this, a GTP aggregator has been implemented that can be seen as a single SGW-U from the remote PGW. Documentation is available here.
This feature enhances the AGW to be able to support tracking area procedures when a UE enters a new tracking area. Prior to this, magma only supported periodic tracking area updates where the MME rejects the TAU request received with EPS update type “TA updating”.
Previous upgrade instructions published for v1.6.0 are still valid and relevant for the upgrade from v1.6.1 to v1.7.0 Upgrade Logs
The 1.6.1 release of Magma is focused on improving the product stability and addressing known issues/bugs. Please note this version was previously only a Release Candidate, but it has now been more extensively tested. For more details on the project’s improved level of release testing, please refer to the test report and TeraVM logs.
Fixes are backported. On v1.6.0, feature tests were failing to send handover notification messages over the real RAN environment.
For new gateway installations on a Ubuntu 20.04 Server, please use the following install script:
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/deploy/agw_install_ubuntu.sh
To upgrade an existing AGW, please run the following upgrade script:
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/release/upgrade_magma.sh
)
This minor release for the Magma v1.5 release contains fixes for some known issues reported for the v1.5 release. See the release page and test report for more information.
For fresh gateway installs, please use the following install scripts. Note that the install scripts vary by the OS used for the gateway.
Ubuntu Install Script
wget https://raw.githubusercontent.com/facebookincubator/magma/v1.5/lte/gateway/deploy/agw_install_ubuntu.sh
# Install Magma
chmod +x agw_install_ubuntu.sh
bash ./agw_install_ubuntu.sh
Debian Install Script
wget https://raw.githubusercontent.com/facebookincubator/magma/v1.5/lte/gateway/deploy/agw_install.sh
# Install Magma
chmod +x agw_install.sh
bash ./agw_install.sh
Repo Change - In Magma Fuji (v1.5), Magma artifacts are now hosted on the new Magma core repositories. Gateways migrating from older Magma releases should update the repo in magma list.
Ubuntu
Add the following to /etc/apt/sources.list.d/magma.list
deb https://artifactory.magmacore.org/artifactory/debian focal-1.5.3 main
# Upgrade Magma
apt update
apt upgrade magma
Debian
Add the following to /etc/apt/sources.list.d/magma.list
deb https://artifactory.magmacore.org/artifactory/debian stretch-1.5.3 main
# Upgrade Magma
apt update
apt upgrade magma -o Dpkg::Options::="--force-overwrite"
The 1.6 (Glacier Peak) Magma release includes lots of great performance and reliability improvements, adds support for some new features, enhances existing ones and adds fixes for other known issues. This release officially deprecates support for Debian and establishes Ubuntu as the only supported OS for deploying Magma. See the release page and test report for more functionality and scale information.
Inbound roaming was first launched in v1.5 to provide network mobility support by allowing mobile users from one operator network to access services while visiting areas outside their network coverage. Paging support as well as other relevant fixes have now been added to enhance the feature. See the related issues for details about other related work.
In addition to PLMN and IMEI network restriction features, Magma now supports Service Area (TAC) Restriction in beta for federated deployments. In a given PLMN, this feature allows network operators to create different service areas for which a UE is allowed or not allowed to attach to the network by configuring subscriber data on HSS with the allowed zone codes and by assigning a list of tracking area codes to each zone code using Orc8r APIs or the NMS for EPC configuration. See the related issues for details about other related work.
MME introduced congestion control that rejects attach requests with cause congestion or implicitly drops initial UE messages based on the latencies observed in message processing in S1AP and NAS layers. This feature is added to maintain the stability of MME when the message processing speed falls behind the incoming request rate from RAN side. The feature can be disabled per AGW instance or at the network level using Orc8r or NMS. The congestion thresholds can be changes by modifying the associated configurations in the mme.yml file
In Non-NAT mode, AGW is pre-configured in router mode where the AGW acts as the L3 next hop for the UE allocated subnet. Refer to the Magma AGW Non-NAT mode section of the online documentation for details.
AGW can make use of the UDP Tunnel Segmentation Offload feature available in modern NICs for GTP-U tunnel traffic. This improves dataplane throughput.
Core
Deployment
GTP-U Echo Request/Response for Inbound Roaming are not currently supported (GTP-U Echo Requests are supposed to be responded to by the AGW). If remote PGWs are configured with an inactivity timer, devices idle for longer than the S8 inactivity timer may not have a corresponding S8 bearer upon transitioning to the active state. This feature will be supported in subsequent releases. NOTE: Echo Requests/Responses are supported on GTP-C since v1.4
Subscriber database might not sync with the fresh install. Verify if there are any sync issues journalctl -fu magma@subscriberdb
and restart Magma services by issuing following commands:
service magma@* stop
service magma@magmad restart
Control_proxy service errors if using both /var/opt/ and /etc/magma.
control_proxy[6877]: 2021-07-06T23:16:24.590Z [127.0.0.1 -> streamer-controller.magma.etagecom.io,8443] "POST /magma.orc8r.Streamer/GetUpdates HTTP/2" 502 158bytes 0.051s
service magma@* stop
service magma@magmad restart
Note: Debian is no longer supported for new installations of v1.6 and beyond For new gateway installations on Ubuntu 20.04 Server, please use the following install scripts.
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/deploy/agw_install_ubuntu.sh
chmod +x agw_install_ubuntu.sh
./agw_install_ubuntu.sh
Note: Note: Debian is no longer supported for upgrades to v1.6 and beyond To upgrade an existing AGW, please run the following upgrade script.
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/release/upgrade_magma.sh
chmod +x upgrade_magma.sh
./upgrade_magma_sh
1.6.0-1625592603-1f26ba81
The Magma 1.5.2 (Fuji) minor release contains fixes for some known issues reported for the v1.5 and v1.5.1 release. See the release page and test report for more information
For fresh gateway installs, please use the following install scripts. Note that the install scripts vary by the preferred OS based on which the gateway is deployed.
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/deploy/agw_install_ubuntu.sh
chmod +x agw_install_ubuntu.sh
./agw_install_ubuntu.sh
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/deploy/agw_install.sh
chmod +x agw_install.sh
./agw_install.sh
To upgrade an existing AGW, please run the following upgrade script.
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/release/upgrade_magma.sh
chmod +x upgrade_magma.sh
./upgrade_magma_sh
Note for 1.3.3 to 1.5.2 please select ‘Yes’ to install Wireshark; this is essential for the call tracing feature.
The Magma 1.5.1 (Fuji) minor release contains fixes for some known issues reported for the v1.5 release. See the release page and test report for more information.
Please refer to the v1.5 release notes
orc8r helm chart version - 1.5.21
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/release/upgrade_magma.sh
chmod +x upgrade_magma.sh
./upgrade_magma_sh
The Magma 1.5 (Fuji) release adds support for some new features and fixes for other known issues. See the release page and test report for more information.
Roaming support allows mobile users from one operator network to access services while visiting areas outside their network coverage. The implementation considers the use case when a subscriber of a network operator MNOH (home network) tries to access LTE services while visiting an area covered by operator MNOV (visiting network) that deploys Magma EPC.
Inbound roaming extends the S6a interface and adds support for the S8 interface. Inbound Roaming requires a federated architecture to connect to MNOV, while MNOH can be Federated using HSS, or in a non-Federated using Magma HSS which is then selected dynamically by PLMN Identifier (ID)
Idle Mode Paging Support: Magma 1.5 supports IDLE to CONNECTED UE originated mode. The current implementation does NOT support IDLE to CONNECTED network originated mode (network paging)
Starting with this release, the default kernel for the AGW will be based on Ubuntu 20.04. Debian is still supported in this release but will be deprecated starting in release v1.6. This also updates Python to 3.8 and OVS to 2.14.
This feature enables support for UE mobility across multiple eNBs over S1 connections and anchored at the same AGW instance. UEs should maintain the same IP address and should experience minimal network layer (i.e., IP layer for applications on the UE) packet loss. Note that Magma does not currently support indirect data forwarding, so some packet loss may be experienced during handover (this will be added in a future release).
This feature adds the ability to restrict UEs from unauthorized PLMNs. You can configure blocked PLMNs in the AGW via a config file so during the attach process, you can grep the PLMN from UE IMSI and perform an Attach reject by including PLMN of AGW into the restricted PLMN list.
Before this release, Magma did not check whether the hardware itself (as identified by its IMEI) is a legitimate/approved device type to access the network. IMEI restriction will allow such checks via configuration and will block access for the device via it’s IMEI if it is not allowed in the network.
20K+ subscribers can now be provisioned at a time. Scaling limitations from previous releases have been addressed.
This release unifies the DB for both Orc8r and NMS. The NMS DB was migrated from MariaDB to Postgres to standardize storage engines across both systems. For network operators using Magma on AWS, there are operating costs to running both MariaDB and Postgres, over using just one or the other. The unification is to have both NMS and orc8r use the same DB to reduce operating expenses of running Magma services.
orc8r helm chart version - 1.5.21
wget https://raw.githubusercontent.com/magma/magma/master/lte/gateway/release/upgrade_magma.sh
chmod +x upgrade_magma.sh
./upgrade_magma_sh
The 1.4.0 (Etna) Magma release contains support for some new features and fixes for other known issues. See the release page and test report for more information.
Magma v1.4.0 enables stateless mode for AGW by default. This mode increases the stability against crashes in core Magma services on AGW except for sctpd. The mode also enables hitless software or configuration updates for the same core services.
Magma AGWs can now be paired together in an HA pool via new Orc8r APIs. The AGW with the higher relative capacity is designated as the primary and the other AGW designated as the secondary by the Orc8r. The recommended configuration for relative capacity for the primary AGW is 255 (maximum allowed value) and for the secondary AGW is 1. The HA feature requires that the eNBs have MME pooling support (a.k.a. S1-Flex) and operator configures the same pair of AGWs in the MME pool set up via the vendor provided management tools. With the recommended configurations, the secondary AGW in the pool is primarily utilized when the primary AGW is not reachable anymore by the eNB. When there are UEs camped on the secondary AGW, they are eventually offloaded to the primary AGW once the primary AGW is denoted as healthy by the Orc8r. If the secondary AGW and the eNB do not have routable S1-U ip addresses, the HA feature is supported only for one eNB per site. If the secondary AGW and the eNB are in the same private network, then HA feature can be utilized for multiple eNBs in the same site.
This feature allows operators to enable header enrichment for UE HTTP traffic. The AGW service adds subscriber information to HTTP requests to contextualize HTTP requests from the server. There could be privacy implications for this feature, so operators are encouraged to check local laws before using it.
util.cpp:58] sctp_bindx ADD error error (98): Address already in use
apt update
apt upgrade magma -o Dpkg::Options::="--force-overwrite"
Supported and validated setups (Static, DHCP, NAT, Non-NAT)
This minor release for Magma contains fixes for some known issues affecting the stability and usability of the 1.3, 1.3.1 and 1.3.2 releases of Durango. See the release page for more information.