Configuration of Subscriber-Aware Metadata using Ansible

This section provides information about:

■

■

■

■

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

To create IP Interface solution with metadata export application:

File name:IPInterfaceSolution

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

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)