Common Node Parameters

Emulators simulate the behavior and messaging of the devices required to complete the network. The Mobile Subscriber emulator is built into the test case and is defined by the parameters on the Network Devices tab and any control protocol tabs that may be provided. Other service or network nodes, such as the FA, SGSN, AAA Server, or Network Host nodes, require that you specify the physical interface, addresses, and routing that will allow them to communicate with other physical devices in the test network or node emulators in the test session.

Additional options, such as support for multiple nodes may be available depending on the emulator type. Refer to the topic for the emulator (listed under Network Devices) for more information.

Ethernet Configuration

The following parameters are typically used to define an emulator with an Ethernet interface. Additional options may be available and the parameter names may vary slightly between the types of emulators.

Physical Interface

The options in this drop-down list are the test server's enabled Ethernet interfaces, including the local port (lo).

Starting IP Address

This is the emulator's actual IP address. Enter an address from the pool of addresses associated with the Physical Interface. If multiple nodes are defined, this is the address used for the first node and it is sequentially incremented for each additional node.

IMPORTANT:

If the address, or range of addresses in the case of multiple nodes, that you provision conflict with any of the other IP addresses provisioned in the test case or test session, you will receive an error when you try to run the test.
Ensure that the interface's address pool has sufficient addresses to accommodate all of the nodes provisioned.
IP Address fields support mask greater than 8bits (/8).

MAC Address

Enable to enter a MAC Address with colon delimiters.

NOTE: Multiple MAC addresses within each test on the same eth port for each group is not allowed, GUI will block with an error.. For example, "SGW GTP Control Node" and "SGW GTP User Node" in MME Nodal will not be allowed to use the same custom MAC address when using the same eth port.

GUI will check the MAC address and pop up a warning message if it is a multicast MAC address (at the OK button). Sample test case warning below :

Default Routing

Select to allow the emulator to use the routing protocols and static routes that were configured for the test server.

Next Hop IP Address

Instead of using the test server's default route, you can force the traffic through a specific test port or set the emulator's next hop to a physical device in the test network. When you select this option, enter the IP address for the next hop in the adjacent field.

Outbound Traffic Port

Provides you with an ability to disable the normal routing function and to force packets out of the selected interface. Select an appropriate traffic port from the Outbound Traffic Port dropdown list.

^ Back to Top

Advanced Test Node Settings

You can specify the ports used by the node, enable optional error injection for Ethernet nodes with the Advanced Test Node Settings. Click the Advanced... button on the node sub-tab to open the window.

Port Selection

Select the Default Port for the node or a Specific Port. If you select Specific Port, enter the control protocol port number in the field provided.

NOTE: You cannot enter a specific UDP port for GTPv2 for the following test nodes. The port number will always be 2123 for control traffic and 2352 for user (data) traffic.

MME Nodal testing: SGW GTP Node, eNodeB User Node, Target eNodeB User Node
MME Node testing: MME GTP Node

VLAN

Select VLAN and enter the VLAN ID (1 - 4095) and User Priority (0 to 7).

You can select the VLAN and enter a VLAN ID to include a VLAN tag with the specified ID in every packet transmitted. User Priority (support for 802.1p Marking) is available in MME, PGW and SGW Test Nodes.

NOTE: VLAN enabler and VLAN ID parameters are available on the User Node tabs in several test cases including MME Nodal, SGW Nodal, SGW Node, PGW Nodal and PGW Node test cases.

Increment Vlan

Select Increment VLAN and enter the # of VLANs (1 - 4095) In the Wifi Offload gateway Nodal, range is from 2 to the number of APs. (only enabled if more than one node is selected on main panel)

In the IP application Node Test case NAS Node (Radius Protocol only) - allow up to 4000 VLANs.

NOTE: Number of Nodes must be evenly distributed by Number of VLANs. Currently available in IP Application node and Site to Site Nodal for Mobile Subscriber Node, IP Application node for NAS Node and Wifi Offload gateway Nodal for AP-WAN Node and Target AP-WAN Node.

Unique Addresses

When checked, every mobile node will be assigned an incremented address.

When not checked, the first node in every VLAN will be assigned the "Starting IP Address" and subsequent node addresses will increment within a VLAN.

Dynamic VLAN

Available only when you select VLAN in:

AAA Server Node Test Case > AAA Server Node > Advanced Settings
Network Host test case on the Emulator Configuration tab > Network Host Test Node > Advanced Settings
SGW Nodal test case, Data Traffic tab > Network Host Test Node > Advanced Settings
Wifi Offload Gateway Node > Gateway Node > Advanced Settings

When you select Dynamic VLAN, VLAN ID and Inner VLAN settings are not available.

The Dynamic VLAN feature supports receiving Dual VLANs (8100, 9100, or 8A88 tagged from the SUTs) terminated by the Network Host. A table maps the received VLAN to destination IP, and includes the VLAN from this table in the server messages sent from the Network Host.

Tcl Parameter: DynamicVlanTaggingEn

NOTE: For example, when testing with two IP Application Node test cases running against a Network Host test case, the UE's in IP Application Node test case may be provisioned with different VLAN types (single/double and Vlan Protocol ID of 0x8100/0x88a8/0x9100), and the Dynamic VLAN on the Network Host test case must be selected.

NOTE: Dynamic VLAN ID is also used to learn the MAC address from incoming ARP request, which includes source device’s MAC/IP. (ARP cache is updated when an ARP Request received includes source MAC/IP Address.)

(The destination device adds an entry to its own ARP cache containing the hardware and IP addresses of the source that sent the ARP Request. This saves the destination from needing to do an unnecessary resolution cycle).

For example, in an IP Application Node and Network Host test cases, when Data starts, IP Application Node sends ARP Request to Network Host, and one of the following two occurs depending on your set up:

If Dynamic VLAN Not selected on the Network Host	The Network Host responds to the ARP Request from the IP Application Node.
If Dynamic VLAN is selected on the Network Host	The Network Host responds, but sends no ARP Request to IP Application Node as the MAC Address is already present in the ARP cache.

Inner VLAN

SGW Nodal and Wifi Offload GW Nodal supports Q-in-Q VLAN (IEEE 802.1ad or 802.1Q) over the AP WAN Node interface when the AP Tunnel Type is None.

The Inner VLAN Tag (IEEE 802.1ad or 802.1Q) allows multiple VLAN headers to be inserted into a single frame and is available on the following test nodes:

IP Application Node test case (Test Node on Mobile Subscriber pane)
Network Host Node (Network Host Node test case and on Data Traffic tab)
DHCP Server Node
AP-WAN Node
AP-WAN Node, Target AP-WAN Node
Gateway Node, DHCP Relay Agent Node

Inner VLAN Tag

Available when you select VLAN Tag. Select Inner VLAN Tag and enter the appropriate numerical value.

Range: 1 - 4095

Default: 1

VLAN Tag Type

Available when you select Inner VLAN Tag. Select the appropriate Ethertype value in the VLAN Tag.

0x8100 Tcl value = 0 (default)
0x88a8 Tcl value = 1
0x9100 Tcl value = 2

NOTES:

The Inner Tag is the Tag is closest to the Payload portion of the frame, called C-TAG (Customer tag, with ethertype 0x8100 or 0x9100 (non-standard QinQ ethertype)).
The outer tag is the one closer/closest to the Ethernet header; its name is S-TAG (Service tag, ethertype 0x88a8).
Tag 1 is the outer tag; tag 2, the second tag, is the inner tag. The tag number has nothing to do with the order in which the tags were added, and so on. It is simply a convention.
For a single-tagged (802.1q) frame, that tag is designated tag 1 when mixed with 802.1ad tags.
In frames having more than one tag, the tags are numbered 1 to N, and appear sequentially and contiguously in the frame from Ethernet header to payload. In this case the innermost tag is the C-TAG and all other tags are S-TAGs.

Network Host Node Test Case

On the Network Host Node Emulator Configuration tab | Network Host test node, supports Inner VLAN Tag for Single Network Host test node and the IPv4/IPv6 nodes in Dual Stack mode.

L3-7 tab (all test cases with Data Traffic tab)

The Local Network Host test node supports Inner VLAN (via the Advanced button) for Single Network Host test node and the IPv4/IPv6 nodes in Dual Stack mode, when available.

Allow Zero Checksum

When IPv6 ports are selected and/or Use Alternate User Address is enabled – IP Header Checksum can be set to Zero as in accordance with RFC 6935.

The following cases are supported:

SGW Nodal: eNodeB User Node, PGW User Node

SGW Node: SGW User Node

MME Nodal: eNodeB User Node

MME Node: SGW User Node

PGW Nodal: SGW User Node

PGW Node: PGW User Node

Error Inject:

NOTE: Error Inject option is not available on User Node and Target User Node in GGSN Nodal test case.

Select the type of errors that are introduced. Packet Discard can be selected for both Outbound and Inbound packets. All other error types are only applicable to Outbound packets.

IMPORTANT:

If neither the Outbound nor Inbound rates are defined, no errors are introduced regardless of the type of error selected.
IP header error injection (Length, Checksum, and Source IP) can only be used with bearer plane traffic. The IP layer must be transported by a control protocol such as MIP or GTP.
When using Packet Discard with segmentation, you must ensure that the first part of the data packet is not being discarded, or the data transactions will not be successful.

Options:

None (0)
Packet Discard (1)
IP Total Length Set to 0 (2)
IP Checksum Corrupted (3)
Payload Checksum Corrupted (4)
Bad Source IP (5)
Out-Of-Order Delivery (6)
Duplicate Packet (7)

Default: None

If you select Bad Source IP, enter an invalid IP address in the field provided. That address will be used as the MN's IP address in outbound Data Traffic packets.

Delay (Packets): Available only when you select either Out-Of-Order Delivery or Duplicate Packet.

The Delay (Packets) is used to indicate when the duplicate or out-of-order packet are sent.

When sending duplicate packets, if you set Delay as 10, the packet will be duplicated 10 packets after the original packet.

When sending out-of-order packets, the Delay indicates how many packets to send before sending the out-of-order packet. For example, if packet #1 is to be out-of order and delay set to 5, the Wireshark shows as follows:

Packet # 2, 3, 4, 5, 6, 1, 7, 8, 9, and so on.

Range: 0 - 1000000 or less than Outbound Packets (if enable and specified).

Error Rate

Use the checkboxes to inject errors into packets traveling in the selected direction.

Outbound Packets — Errors are introduced in packets sent by the node.
Inbound Packets — Errors are introduced in packets received by the node. Only Packet Discard can be applied to inbound packets.

Define the error rate for each direction in the fields provided. If you enter 50, for example, every 50th packet is discarded (Fixed distribution) or 1 out of every 50 packets is randomly discarded (Random distribution).

MTU

Defaults to 1500, range 123 - 9300. Ensures GTP-C control message and GTP-U data traffic supports more than 1500 bytes in GGSN Nodal, GSSN Node, SGW Nodal and SGW Node test cases.

Added support for gNB User Node / Target gNB User Node in AMF Nodal, SMF Nodal and UPF Nodal test cases.

Added support for UPF N3/N9 Node in AMF Nodal (with SMF/UPF Node Emulation enabled) , SMF Nodal (with UPF Node Emulation enabled) and UPF Node test cases.

Added support for eNodeB Control Node in MME Nodal test case. This parameter is the 13rd parameter of Tcl variable EnbControlAddr.

NOTE: Maximum MTU size is limited to 2000 for 32-bit Test Servers.

IP Encapsulation

The encapsulation used by the AAL5 layer. SNAP and Classical IP (default) encapsulation are supported.

ETH Stats

Select to produce Ethernet Report Statistics for the selected ethernet port. See additional information - Ethernet Report Measurements

Use Public IP Address

Add support for using Public IP Address option to the Test Node Advanced Dialog for use in EPCs where NAT devices are between the various network elements.

Select to input Starting Address. Enter valid IP address.

There are NAT devices between each EPC network element. When EPC network element communicates with others, it will use its private IP address in IP layer as source IP address and public IP address as destination IP. NAT devices will translate public IP address into private IP address. Each network element will use public IP address in signaling message.

Force IPv6 Solicitations

Select to force additional IPv6 Solicitations. When enabled, Number of Solicitations becomes available for input. Enter 0 to 10 number of additional IPv6 solicitations. When checked, Landslide will send at least 2 neighbor solicitation messages for each IPv6 address discovery process.

Zero (0) == no additional solicitations for the base IP Address.

If Number of Solicitations > 2, then Timeout (ms) becomes available for input. Range: 0 65535 (0==off). Enter timeout value (in milliseconds) between solicitations.

Available in the following test cases as well as in the L3-7 Data Traffic Network Host Test Node:

HSS Node, IMS Node, DRA Nodal, MME Nodal, PGW Node and PGW Nodal test cases. 5G test cases : AMF Nodal, AMF Node, Service Based Nodal, Service Based Node, SMF Nodal, SMF Node, UPF Nodal, and UPF Node.

The SGW GTP User Node and SGW GTP Control Node in MME Nodal test case are using the same “Force IPv6 Solicitation” settings in SGW GTP Control Node thus the "Force IPv6 Solicitation" is not configurable in the SGW GTP User Node.

In the UPF test cases, UPF N4 GTP node and UPF N3 Node are using the same Ip Instance and since N3 is the main node, the "Force IPv6 Solicitation" is not configurable in the UPF N4 GTP Node.

^ Back to Top