Configuration of Subscriber-Aware Metadata using Ansible

This section provides information about:

■   Configuration of Subscriber-Aware Metadata using Ansible
■   Subscriber-Aware Metadata Export
■   Add SMAF and SAM exporter details.

Refer to Installation and Configuration of Subscriber Intelligence Solution using Ansible

■   System Requirement
■   Installation of Gigamon Ansible Module
■   Configuration of Pythonpath
■   Rules and Notes

Subscriber-Aware Metadata Export

To configure Subscriber-Aware Metadata (SAM) export, perform the following steps:

S.No Steps Refer to..
1. Add SMAF Credential path to ansible_inputs.json Add SMAF Credential Path
2. Create smafInfo.yml

Add SMAF Credential Path

3. Add SMAF and SAM exporter details in mobility Add SMAF and SAM exporter details
4. Create IP interface solution with metadata export application

Add SMAF and SAM exporter details

5. Configure SMAF Installation of Sub-Metadata Aggregator Function Server in Online documents.
6. Configure SAM Add SMAF and SAM exporter details

Add SMAF Credential Path

For information about ansible_inputs.json, refer to Schema.

Create smafInfo.yml

File name: fmInfo.yml

gigamon@fmreg26:~/mobilitySolution$ ls -l

-rw-r--r-- 1 ddaniel fmtaf 172 May 11 12:10 smafInfo.yml

For information about ansible_inputs.json, refer to Schema.

Add SMAF and SAM exporter details

Copy 
[IPInterfaceSolution]
IpInterfaceSolutionConfig
 
[ToolGroups]
cluster-two
cluster-one
 
[Gigastreams]
cluster-two
cluster-one
 
[GTPWhitelist]
cluster-two
cluster-one
 
[Ports]
cluster-two
cluster-one
 
[Policies]
5g_policy_1
 
[GTP]
gtp_CorrelationNode1
 
[CPN]
cpnUkLTE
 
[UPN]
upnDallas
 
[SAM]
SMAFExporter1
SMAFExporter2
 
[SMAF]
10.210.30.186
 
[Sites]
UK cpn_list='["cpnUkLTE"]' upn_list='[]' sam_list='[SMAFExporter1,SMAFExporter2]'
Dallas cpn_list='[]' upn_list='["upnDallas"]' sam_list='[]'
 
[MobilitySolution]
mobilitySolution1 cups_5g_global_policy=5g_policy_1 sites='["UK", "Dallas"]'

Create IP Interface solution

To create IP Interface solution with metadata export application:

Copy 
---
IPInterfaceSolution:
  tags:
  - tagKey: Location
    tagValues:
    - Chennai
    - Pune
  IPInterfaces:
  - alias: dev1_IpIntCpn_1
    type: network
    applications:
    - CPN
    gateway: 10.1.1.1
    interfaces:
    - 1/1/x1
    ipAddress: 10.2.3.4
    ipMask: 255.255.255.0
    clusterName: cluster-one
    mtu: 1500
  - alias: dev2_IpIntUpn_1
    type: network
    applications:
    - UPN
    gateway: 10.1.1.1
    interfaces:
    - 1/1/x2
    ipAddress: 10.2.3.100
    ipMask: 255.255.255.0
    mtu: 1500
    clusterName: cluster-one
  - alias: dev1_IpIntCpn_2 # IP Interface used to export Control JSON Records
    type: tool
    applications:
    - CONTROL_METADATA_EXPORTER
    gateway: 10.1.1.1
    interfaces:
    - 1/1/x1
    ipAddress: 10.2.3.4
    ipMask: 255.255.255.0
    clusterName: cluster-one
    mtu: 1500
  - alias: dev2_IpIntUpn_2 # IP Interface used to export User JSON Records
    type: tool
    applications:
    - USER_METADATA_EXPORTER
    gateway: 10.1.1.1
    interfaces:
    - 1/1/x2
    ipAddress: 10.2.3.100
    ipMask: 255.255.255.0
    mtu: 1500
    clusterName: cluster-one
  state: present

Configure SMAF

Refer to Installation of Sub-Metadata Aggregator Function Server Guide in Online documents.

Configure Subscriber-Aware Metadata

The following are the four scenarios that are possible in configuring Subscriber-Aware Metadata:

S.No Scenarios For more information refer to topic..
1. SAM in single Application Metadata Intelligence (AMI) engine and Non-CUPS solution Subscriber-Aware Metadata (BETA)
2. SAM in multiple AMI engines and Non-CUPS solution

Subscriber-Aware Metadata (BETA)

3. SAM in single AMI engine and CUPS solution Subscriber-Aware Metadata (BETA)
4. SAM in multiple AMI engines and CUPS solution

Subscriber-Aware Metadata (BETA)

.