Configure SCP Traffic Flow

Use this workflow when your deployment includes SCP (L7-Native) traffic from Ericsson CCx vTAPs. You can deploy this workflow independently or alongside the SBI traffic flow. The SCP traffic passes through a Load Balancing (LB) application for distribution before reaching the 5G-Cloud Node for L7-Native synthesis.

Monitoring Sessions Required

Monitoring Session	V Series Node	Traffic Handled
5G-EVP	5G-EVP	All traffic, packet ordering and optional DTLS decryption
SCP	5G-SBI	SCP ingress (keys 3,17,19) + Metadata (keys 0,2) + LB + multi-tap egress
5G-Cloud	5G-Cloud	SCP synthesis (L7-Native)

Prerequisites

Before you begin, complete the following:

Deploy three V Series Nodes: 5G-EVP, 5G-SBI, and 5G-Cloud.
Create a separate monitoring domain for each V Series Node in GigaVUE‑FM.
Verify that the V Series 5GC add-on license is active.
Configure NTP servers for the 5G-EVP Node (required when packet ordering is enabled).
If you plan to use DTLS, upload the private key and certificate in GigaVUE‑FM via Inventory > Security > SSL Key.
If you plan to use multiple egress IPs on the 5G-EVP Node, configure the additional IP addresses in NetPlan on the VM. Refer to Configuring Multiple Egress IP Addresses.
Upload CSV Files for the 5G-Cloud Application
- In GigaVUE-FM, go to Inventory > VIRTUAL.
- Select your cloud platform.
- Click Settings, and then click 5G-Apps.
- Upload the FQDN, NF Instance, and User Agent CSV files.

End to End Configuration

Configure 5G-EVP Application

To configure the 5G-EVP application, drag and drop it onto the monitoring session canvas and select Details. The 5G-EVP application quick view appears. Enter or select the required information as described in the following tables.

Field	Description
Application	The name 5g-EVP appears by default.
Alias	Enter the alias name as 5gEVP.
Packet Ordering Config
Packet Ordering	Toggle to enable or disable timestamp-based packet reordering. When enabled, the 5G-EVP application sorts packets based on the observed timestamp in the PCAPng Enhanced Packet Block before forwarding them to the downstream application.
Primary NTP Server*	Enter the IP address (IPv4 or IPv6) of the primary NTP server. The 5G-EVP application requires NTP time synchronization through chronyd for millisecond-accurate clock alignment. GigaVUE-FM sends this configuration to the V Series Node during each deployment. This field is mandatory when packet ordering is enabled. Note: Visible when Packet Ordering is enabled.
Secondary NTP Server	Enter the IP address (IPv4 or IPv6) of the secondary NTP server. This field is optional. The secondary NTP server provides failover if the primary NTP server becomes unreachable. Note: Visible when Packet Ordering is enabled.
Number of Buckets	Enter the number of time buckets for sorting. Default: 100. The value of Number of Buckets × Bucket Interval must not exceed 100. For example, if Bucket Interval is 5 ms, the maximum Number of Buckets is 20. If the configured values exceed this limit, the application returns an error.
Packets per Bucket	Enter the maximum number of packets each bucket can hold. Default: 20,000.
Bucket Interval (ms)	Enter the time span (in milliseconds) for each bucket. Minimum: 1 ms. Maximum: 5 ms. Default: 1 ms. The sorting window equals Number of Buckets × Bucket Interval. For example, 100 buckets × 1 ms = a 100 ms sorting window.
Packet Outside Bucket Interval	Select the action for packets that arrive with timestamps outside the current sorting window. Forward (recommended), sends the packet to the downstream application without reordering. Discard, drops the packet at the 5G-EVP application.
Monitored Flows
Number of Egress Flows	Enter the maximum number of egress flows. Default: 512. Maximum: 16,384.
Egress Flow Timeout Value	Enter the timeout (in seconds) for egress flow entries. Default: 660.
Ingress UDPGRE Tunnel
Listening IP	Specify the tunnel's local listen IP address to receive the packet.
Listening Port	Specify the tunnel's local listening port to bind to receive the packet. Enter the UDP port number. Default: 4754 (non-secure) or 4755 (DTLS). You can enter any valid port number.
RX Thread	Specify the RX value to receive the packet. Enter a value between 1 and 16. The default value is 8.
DTLS	Select Enable to receive DTLS-encrypted traffic, or Disable for plaintext UDP-GRE traffic.
DTLS Key	Select the key alias associated with the SSL certificate used for DTLS decryption.
Egress UDP Tunnel
Tool IP	Egress Tunnels Endpoint, Destination IP address.
Tx Destination Port	Enter the destination port. This value must match the listen port on the downstream application. Default: 4754.
Tx Source IP List	Enter up to 8 source IP addresses for the egress tunnel. Configure these IPs in the VM's NetPlan before adding them here.
Tx Source Port	Enter the source port for the egress UDP-GRE tunnel.
Tx Thread	Enter the number of transmit threads. Range: 1–8.
Diagnostics
Packet Disable	Enter a protocol key value to disable processing for a specific Ericsson protocol. Default: 0.
Tx Disable	Select true to disable packet transmission (for debugging), or false for normal transmission. Default: false.
Logging
Log Level	Select the minimum severity of system events to log. Higher levels generate more detailed logs.
Packet Capture Log Level	Select the log level: all, receive, transmit, or none.
Message Log Level	Select the log level: error, warn, info, or debug. Default: error.
Log Directory	Thebpath where log files should be stored.

Monitoring Session 2: SCP Traffic (5G-SBI Node)

Create this monitoring session on the 5G-SBI V Series Node. This session handles the ingress, PCAPng processing, and load balancing for SCP traffic before forwarding it to the 5G-Cloud Node.

In GigaVUE‑FM, navigate to the monitoring domain for the 5G-SBI V Series Node.
Create a new monitoring session.

Create one UDP-GRE ingress tunnel for each SCP key value:

Key Value	Traffic Value
0,2	Metadata (domain classification)
3, 17, 19	SCP (L7-Native)

Drag and drop the first PCAPng application for metadata processing. Select Details and configure the following:

Field

Description

Application

The name Pcapng appears by default.

Alias

Enter an Alias as required.

App Mode

Set App Mode to Primary to view and configure domain related options.

Note: Primary mode is required to configure domain classification. When you set App Mode to Secondary, Domain Classification, Domain VLAN Mapping, and Flow Timeout fields are not visible.

Domain Classification

Enable the Domain Classification option to classify Ericsson vTAP traffic by domain.

Domain VLAN Mapping

● From the Domain VLAN Mapping list, select the VLAN mapping profile that maps Ericsson domains to VLAN IDs for per-domain tagging on the egress tunnel.

● Click Add New to create a new 5G-Apps configuration. Refer to Adding CSV file for IP Mapping section in 5G-Service Based Interface Application for details.

When Domain Classification is enabled, the selected Domain VLAN Mapping is used to tag packets per Ericsson domain with the configured VLAN ID (and, if applicable, a separate VLAN ID for failed SBI transactions) before sending traffic to the probes.

Flow Timeout

Set the Flow Timeout value in seconds to define how long an inactive Ericsson vTAP flow is kept before it is closed and its resources are released.

Valid range: 360-1860

Default value: 660

Link the ingress tunnels for key values 0 and 2 to this PCAPng instance.

Note: This PCAPng instance does not require an egress tunnel. Only one PCAPng instance can be set to Primary mode per monitoring session.
Drag and drop the second PCAPng application for SCP traffic. Select Details and set App Mode to Secondary.
Link the ingress tunnels for key values 3, 17, 19 to this PCAPng instance.
Drag and drop the LB (Load Balancing) application. Select Details and configure the hash field to greFlowid.
Link the SCP PCAPng instance (from Step 6) to the LB application.
Create a VXLAN egress tunnel with the Multi-Tunnel flag enabled. If Domain Classification is enabled, enable Domain Tagging on the egress tunnel.

Note: You create one egress tunnel. The system internally creates multiple taps for load distribution (minimum 1, maximum 16).
Link the LB application output to the egress tunnel.
Verify all links on the canvas:
- Ingress tunnels (key 0, 2) -> PCAPng (Primary), no egress
- Ingress tunnels (key 3, 17, 19) -> PCAPng (Secondary) -> LB -> Egress tunnel (multi-tap)
From the Actions menu, select Deploy.

Monitoring Session 3: 5G-Cloud

Create this monitoring session on the 5G-Cloud V Series Node (Linux-based).

In GigaVUE-FM, navigate to the monitoring domain for the 5G-Cloud V Series Node.
Create a new monitoring session.
Drag and drop an Ingress REP (placeholder, no configuration required).

Drag and drop the 5G-Cloud application. Select Details and configure the following:

Field

Description

Application

The name 5g-Cloud appears by default.

Alias

Enter the alias name as cloud5g.

Mode

From the drop-down list, select Ericsson SCP Transparent.

RX Tunnel

Type

Specify the tunnel type. The default is VXLAN.

Listening IP

Specify the tunnel's local listen IP address to receive the packet.

Listening Port

Specify the tunnel's local listening port to bind to receive the packet. The application will listen to the traffic coming to the specified port. Enter a value between 1 and 65535.

Source Port

Specify the tunnel destination port from where the packets will be sent. Enter a value between 1 and 65535.

VNI Id

Specify the VNI to use for the VXLAN traffic. Enter a value between 0 and 16777215. The default value is zero.

RX Thread

Specify the RX value to receive the packet. Enter a value between 1 and 16. The default value is 8.

TX Tunnel

Type

Specify the tunnel type. The available tunnel types are:

●

VXLAN

●

L2GRE

Tool IP

Specify the remote IP address to send the packet.

Destination Port

Specify the tunnel destination port to which the packet will be sent. Enter a value between 1 and 65535.

Source IP

Specify the source IP address to use when sending the packet.

Source Port

Specify the tunnel source port to bind when sending the packet. Enter a value between 1 and 65535.

VNI Id

(Applicable only when the selected tunnel type is VXLAN)

Specify the VNI to use for the VXLAN traffic. Enter a value between 0 and 16777215.

L2GRE Key

(Applicable only when the selected tunnel type is L2GRE)

Specify the key for the L2GRE tunnel type. Enter a value between 0 and 4294967295.

Advanced Setting

Tool MTU

Specify the tool port MTU.

Log Directory

Specify the path to store the log files.

Log Level

Select the severity log level of the events from the following options:

●

None

●

Fatal

●

Error

●

Notification

●

Information

●

Debug

SCP Config

FQDN Mapping

Specify the alias name created for the uploaded FQDN table CSV file.

NF Instance Mapping

Specify the alias name created for the uploaded NFID table CSV file.

User Agent Mapping

Specify the alias name created for the uploaded User Agent table CSV file.

TCP Server Ports

Specify the TCP server port or port range to allow TCP communication endpoints.

SCP Advanced Config

No. of TCP Flows

Specify the total number of concurrent TCP flows. Enter a value between 128 and 2048. The default value is 1024.

No. of Transaction Flows

Specify the total number of Transaction Stream Flows allocated for tracking active Transaction Streams. Enter a value between:

●

128 and 26000 for V Series Node of extra large form factor (total memory ≥ 32GB).

●

128 and 5500 for V Series Node of large form factor (total memory < 32GB).

The default value is 2048.

TCP Flow Timeout

Specify the TCP flow timeout ranging between 0 to 7200. The default value is 900.

SCP Transaction Timeout

Specify the SCP transaction timeout value ranging between 1 and 300. The default value is 10.

Note: The recommended timeout value is between 10 and 20 seconds. An increase in the transaction timeout value will impact the total number of transactions that can be processed in parallel.

Minimum TCP Client Port

Specify the minimum value to be used for TCP client port ranging between 1023 and 65535. The default value is 32768.

Maximum TCP Client Port

Specify the maximum value to be used for client port ranging between 1023 and 65535. The default value is 36863.

SCP Processing Threads

Specify the number of worker threads for processing In-Out packets. Enter a value between 1 and 16. The default value is 8.

TCP Client Ports per Thread

Specify the number of TCP client ports for each worker thread. Enter a value between 100 and 8000. The default value is 1000.

Header Index

Enable or disable the header indexing. The default value is disabled.

Header Compression Code

Enable or disable the header compression code. The default value is disable.

Gigamon Header

Enable or disable the Gigamon Header. The default value is Enable.

Packet Capture Level

Select the packet capture level from the drop-down list:

●

All

●

Receive

●

Transmit

●

None

5G-Cloud Log Level

Select the required 5G-Cloud CSV log level from the drop down list. The default value is None.

●

All

●

Flow

●

Message

●

Transaction

●

None

HTTP2 Monitored Flows

Number of Streams

Specify the number of monitored stream flows. Enter a value between 1024 and 16384. The default is 1024.

Request Timeout

Specify the HTTP/2 request timeout in seconds. Enter a value between 1 and 300. The default is 15 seconds.

Response Timeout

Specify the HTTP/2 response timeout in seconds. Enter a value between 1 and 300. The default is 2 seconds.

TCP Monitored Flows

Number of Flows

Specify the number of monitored TCP flows. Enter a value between:

●

1024 and 32768 for V Series Node of extra large form factor (total memory > 32GB).

●

1024 and 2048 for V Series Node of lesser form factor.

The default value is 2048.

Flow Timeout

Specify the timeout for TCP flows in seconds. Enter a value between 1 and 7200. The default value is 60 seconds.

Flow Reassembly Timeout

Specify the timeout for TCP flow reassembly in seconds. Enter a value between 1 and 7200. The default value is 500 seconds.

Drag and drop an Egress REP (placeholder, no configuration required).
Create links: Ingress REP -> 5G-Cloud -> Egress REP.
From the Actions menu, select Deploy.

Notes:

After you deploy a Monitoring Session, you cannot edit its associated 5G SBI or PCAPNG application configurations. To modify them, undeploy the Monitoring Session, update the configuration, and redeploy.

If a PCAPNG application instance is set as the Primary for a Monitoring Session, you cannot delete it while it holds that role. To delete or replace it, undeploy the Monitoring Session or reassign the Primary.

Adding CSV file for IP Mapping

To add the CSV file for IP mapping:

Go to Inventory > VIRTUAL > select your cloud platform, and then click Settings > 5G-Apps. The 5G-Apps Configuration page appears.

Click New. Enter the name for the CSV file in the Alias field.

From the Type drop-down list, select one of the following. You can also choose to download the template using the Download Template option and add the required entries.

5G-SBI Network Function Instance - Add the CSV file containing a valid NF instance ID and a valid IPv4/IPv6 address for IP mapping in 5G-Ericsson.

Header details with an example:

■ instanceID - e4d909c2-5d2f-4f7f-9bcb-12a3b6c4d789

■ ipAddress - 1.1.1.1

5G-SBI FQDN - Add the CSV file containing a valid FQDN ID and a valid IPv4/IPv6 address for IP mapping.

Header details with an example:

■ fqdnID - amf.local

■ ipAddress - 1.1.1.1

■ nfType - SCP

Domain VLAN Mapping - Add the CSV file containing a valid domain and a valid VLAN ID for IP mapping.

Refer the table below for example header details of the CSV file.

domainName

vlanID
failedSBITransactionVlanID

pc-mm

100

200

pc-sm

300

400

ccsm-5gc

500

ccsm-cnhss

600

ccrc-nrf

700

nrfagent-nrf

800

ccrc-nssf

900

ccpc-pcf

1000

ccpc-provisioning

1100

ccdm-udr-5g

1200

ccdm-provisioning

1300

ccdm-udr-legacy

1400

cces-nef

1500

cces-ees

1600

cces-apigm

1700

sc-bsf

1800

sc-scp

1900

sc-sepp

2000

others

2100

unclassified

2200

Click Choose File in File Name field to upload the CSV file into GigaVUE‑FM.

Click Validate to validate the CSV file.

Click Save to add the CSV file.

Notes:

Failed SBI Transactions are applicable only for pc-mm and pc-sm domains.

Each domain in the Domain table must use a unique VLAN ID and Failed SBI Transaction ID to allow the probes to distinguish traffic for each Ericsson domain.

Recommended VM Specifications

The configuration of the V Series application should be performed on large VMs.

V Series App

vCPUs

Memory

Disk Space

5G-EVP

20

32 GB

80 GB

5G-SBI

8

16 GB

80 GB

5G-Cloud

24

32 GB

80 GB

■ Supported Ports: 1 Management interface, 1 ingress, and 1 egress interfaces.

■ It is recommended to use SRIOV enabled drivers for better performance and higher throughput. Refer to Configure GigaVUE Fabric Components using VMware ESXi topic for more details.

FHA Dashboards for 5G Applications

After configuring the 5G-SBI application, you can monitor the statistics for Ericsson vTAP by the reports displayed in the Dashboard. To access the details, refer to FHA Dashboards for 5G Applications.

Upgrade and Migration Steps

Follow these steps to add the 5G-EVP application to an existing deployment. If you are deploying as part of a new setup, skip this section.

Upgrade GigaVUE‑FM to the current release.

Upgrade the existing 5G-SBI and 5G-Cloud V Series to the current release.

Deploy a new 5G-EVP V Series Node running the current release.

Reassign the ingress IP address from the 5G-SBI Node to the EVP Node ingress interface.

Provision a new IP address for the EVP Node egress interface.

Provision a new IP address for the 5G-SBI Node ingress interface. This must be in the same subnet as the EVP egress IP.

If the existing deployment has a source IP in the TEP configuration, remove it.

Configure the 5G-EVP monitoring session. Refer to Configure SCP Traffic Flow for field descriptions.

Update the 5G-SBI monitoring session with the new ingress IP address.

Deploy both monitoring sessions from the Actions menu in GigaVUE‑FM.

Note: The 5G-SBI to 5G-Cloud pipeline remains unchanged. No modifications are required on the 5G-Cloud Node.