VRF Feature Parameter Description: Singleran
VRF Feature Parameter Description: Singleran
VRF Feature Parameter Description: Singleran
Issue 02
Date 2021-04-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 SRAN17.1 02 (2021-04-30)..................................................................................................................................................1
1.2 SRAN17.1 01 (2021-03-05)..................................................................................................................................................1
1.3 SRAN17.1 Draft A (2020-12-29)........................................................................................................................................ 2
3 VRF.............................................................................................................................................. 5
3.1 Principles.................................................................................................................................................................................... 5
3.1.1 Basic Principles...................................................................................................................................................................... 5
3.1.2 Application Scenarios......................................................................................................................................................... 6
3.1.3 Application Limitations...................................................................................................................................................... 9
3.1.4 Networking............................................................................................................................................................................ 9
3.1.4.1 Non-Secure Networking.................................................................................................................................................9
3.1.4.2 Secure Networking...........................................................................................................................................................9
3.1.4.2.1 IPv4 Secure Networking............................................................................................................................................. 9
3.1.4.2.2 IPv6-over-IPv6 Secure Networking....................................................................................................................... 10
3.1.4.2.3 IPv4-over-IPv6 Secure Networking....................................................................................................................... 11
3.2 Network Analysis.................................................................................................................................................................. 12
3.2.1 Benefits................................................................................................................................................................................. 12
3.2.2 Impacts.................................................................................................................................................................................. 12
3.3 Requirements......................................................................................................................................................................... 13
3.3.1 Licenses................................................................................................................................................................................. 13
3.3.2 Software................................................................................................................................................................................13
3.3.3 Hardware.............................................................................................................................................................................. 14
3.3.4 Networking.......................................................................................................................................................................... 15
3.3.5 Others.................................................................................................................................................................................... 15
3.4 Operation and Maintenance............................................................................................................................................. 15
3.4.1 Data Configuration........................................................................................................................................................... 15
3.4.1.1 Data Preparation............................................................................................................................................................ 15
3.4.1.2 Using MML Commands............................................................................................................................................... 19
4 Parameters.............................................................................................................................. 22
5 Counters.................................................................................................................................. 23
6 Glossary................................................................................................................................... 24
7 Reference Documents...........................................................................................................25
1 Change History
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
Technical Changes
None
Editorial Changes
Revised descriptions in this document.
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.
3 VRF
3.1 Principles
Related Concepts
● VRF instance
The VRF index and user label on the base station side are specified by the
VRF.VRFIDX (LTE eNodeB, 5G gNodeB) and VRF.USERLABEL (LTE eNodeB,
5G gNodeB) parameters in the VRF MO, respectively. The VRF index identifies
a VRF instance on a base station. Once a VRF instance is created on a base
station, so is a routing table. The VRF instance with the index of 0 functions
as the default VRF instance and is implemented in the same way as other VRF
instances. During data transmission, if no VRF instance index is specified, data
will be transmitted through the default VRF instance.
● Interface
The base station uses the INTERFACE MO to manage both normal and VLAN
interfaces. The interface type is specified by the INTERFACE.ITFTYPE (LTE
eNodeB, 5G gNodeB) parameter. All interfaces are associated with a specified
VRF instance, which is VRF index 0 by default.
Principles
The base station, in its transmit direction, determines the destination VRF instance
based on the application layer protocol and indicates it using VRF.VRFIDX (LTE
eNodeB, 5G gNodeB).
In the receive direction of the base station, data is sent to the VLAN interface
(specified by the INTERFACE MO) corresponding to the specified VRF index before
being sent to the application layer. At the network layer, the base station uses VRF
indexes to identify and isolate packets belonging to different logical networks. At
the data link and physical layers, packets from different VRF instances are
differentiated by VLAN ID or physical port. Therefore, when VRF is enabled on
interfaces that adopt different VRF indexes (specified by INTERFACE.VRFIDX (LTE
eNodeB, 5G gNodeB)), these interfaces must also have different VLAN IDs
(specified by INTERFACE.VLANID (LTE eNodeB, 5G gNodeB)).
A 1 0 VLAN 100
B 2 1 VLAN 200
In the LTE TDD wholesale solution, there are three available network sharing
architectures: multi-operator core network (MOCN), gateway core network
(GWCN), and modified home routed (MHR). VRF can be used in MOCN and
GWCN. For details about MOCN and GWCN, see RAN Sharing in eRAN Feature
Documentation. For details about MHR, see Wholesale (TDD) in eRAN Feature
Documentation.
In network sharing solutions for LTE TDD, LTE FDD, NB-IoT, and NR, VRF can be
used in various architectures. For details, see RAN Sharing in eRAN Feature
Documentation and Multi-Operator Sharing in 5G RAN Feature Documentation.
For details about VRF deployment in the MOCN scenario, refer to the deployment
in the IPv4 non-secure networking scenario. In this scenario, only VRF and VPN are
configured on the base station and router, respectively. In the GWCN scenario,
both the base station and MME are connected to two operators' networks, and
VRF must be configured on the MME, as shown in Figure 3-3.
A 1 1 VLAN 100
B 2 2 VLAN 200
NOTE
The mappings between operators' networks and VRF instances are as follows:
● If there are no network IP address conflicts among operators' networks, their networks
can share the same default VRF instance.
● If there are network IP address conflicts among operators' networks, their subnets must
use different VRF instances.
3.1.4 Networking
and outer IPsec packets must be configured in the same VRF instance. For details,
see Figure 3-5 and Table 3-3.
NOTE
packets from outer IPsec service packets, preventing the inner service modules
protected by IPsec from network attacks.
NOTE
VRF is used to isolate inner and outer packets in IPv6 secure networking. For details, see the
description of VRF isolation in IPsec.
3.2.1 Benefits
When multiple operators share a network or network slicing is used, service
interface IP addresses need to be independently planned for each operator or slice.
This may lead to conflicts. To prevent IP address conflicts within the same VRF
instance, it is recommended that the VRF function be enabled to ensure that IP
addresses do not conflict among operators' networks or slices.
3.2.2 Impacts
Network Impacts
None
Function Impacts
Function Function Reference Description
Name Switch
Direct IPv4 None X2 and S1 Self- Direct IPv4 IPsec can only be
IPsec Management in deployed in the default VRF
NSA Networking instance.
S1 and X2 Self-
Management
NG and Xn Self-
Management
IPsec tunnel None IPsec The IPsec tunnel pair can only
pair be deployed in the default VRF
instance.
3.3 Requirements
3.3.1 Licenses
This function is a basic function and is not under license control.
3.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Prerequisite Functions
Function Function Reference Description
Name Switch
3.3.3 Hardware
Boards
Only the UMPT and UMDU boards support this function. When the UTRP or two
main control boards are used, only the default VRF instance can be deployed.
RF Modules
This function does not depend on RF modules.
3.3.4 Networking
Before IP address planning, collect the IP address information for the core network
NEs, MAE, and neighboring base stations. Ensure that there are no IP address
conflicts within a VRF instance.
The VRF function can be used when the transmission links of the S1 and X2
interfaces are configured in the endpoint mode. For details, see IP eRAN
Engineering Guide and IP NR Engineering Guide.
3.3.5 Others
None
Networking-related Parameters
When a service link is configured in endpoint mode, the VRF mapping needs to be
specified using the following parameters: EPGROUP.VRFIDX (LTE eNodeB, 5G
gNodeB) (IPv4) or EPGROUP.IPV6VRFIDX (LTE eNodeB, 5G gNodeB) (IPv6),
SCTPHOST.VRFIDX (LTE eNodeB, 5G gNodeB), SCTPPEER.VRFIDX (LTE eNodeB,
5G gNodeB), USERPLANEHOST.VRFIDX (LTE eNodeB, 5G gNodeB), and
USERPLANEPEER.VRFIDX (LTE eNodeB, 5G gNodeB).
Basic Parameters
The parameters used for VRF activation are as follows:
● VRF parameters: Table 3-6 describes the parameters used for adding a VRF
instance. The default VRF instance does not need to be added.
● VLAN interface parameters: Table 3-7 describes the parameters used for
adding a VLAN interface to a physical port.
● IPsec parameters: For details about IPsec, see IPsec. This section focuses on
the VRF mapping configuration in IPsec configurations.
For IPv4 IPsec, the IKEPEER MO is used to specify the VRF mapping. Table
3-9 describes the parameters used for function activation.
For IPv6 IPsec, the TUNNELITF MO is used to specify the VRF mapping. Table
3-10 describes the parameters used for function activation.
For details about other counters related to network monitoring for this function,
see IP eRAN Engineering Guide and IP NR Engineering Guide.
4 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter. View its information, including the
meaning, values, and impacts.
----End
5 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
----End
6 Glossary
7 Reference Documents
● IPsec
● IPv4 Transmission
● IPv6 Transmission
● Common Transmission
● X2 and S1 Self-Management in NSA Networking
● Feature parameter description documents in eRAN Feature Documentation:
– IP eRAN Engineering Guide
– Wholesale (TDD)
– S1 and X2 Self-Management
– RAN Sharing
● Feature parameter description documents in 5G RAN Feature Documentation:
– IP NR Engineering Guide
– NG and Xn Self-Management
– Multi-Operator Sharing
– Network Slicing