New and Changed Information

The following table provides an overview of the significant changes up to this current release. The table does not provide an exhaustive list of all changes or of the new features up to this release.

Table 1. New Features and Changed Behavior in Cisco APIC

Cisco APIC Release Version

Feature

Description

Release 2.0(2f)

-

This article was written. In this release, Cisco Tetration Analytics became available for beta testing.

Release 2.2(2e)

-

In this release, the first release of Cisco Tetration Analytics (release 1.102.21) became officially supported.

Installing the Cisco Tetration Analytics Agent

This task describes the steps necessary to download the Cisco Tetration Analytics sensor software for installation on the switches in the APIC cluster.

Procedure

Step 1

In the Cisco Tetration Analytics application, click the Settings icon.

Step 2

From the Settings drop-down menu, click Sensor Config.

Step 3

Click the Hardware Sensor Download tab.

Step 4

Choose the most current Version and click Download.

Step 5

Browse to the Downloads folder on your system.

Step 6

Log into APIC.
Step 7

Click Admin > Firmware > Firmware Repository.

Step 8

From the ACTIONS drop-down menu, click Upload Firmware to APIC.

Step 9

Choose the RedHat Package Manager (RPM) file from the Downloads folder.

Step 10

Click Open and Submit.

The RPM binary is available to be installed on all the switches in the cluster. From this point on, the switches communicate directly with the Cisco Tetration Analytics cluster to install updated RPM binaries as they become available.

What to do next

To determine if the installation failed on any switch, click System > Faults and search for the following text in the Sample Fault Description column: This fault occurs when the Analytics agent Image installation failed on the switch.

Overview

This article provides examples of how to configure Cisco Tetration when using the Cisco APIC. The following information applies when configuring Cisco Tetration.

  • An inband management IP address must be configured on each leaf where the Cisco Tetration agent is active.

  • Define an analytics policy and specify the destination IP address of the Cisco Tetration server.

  • Create a switch profile and include the policy group created in the previous step.

Configuring Cisco Tetration Analytics Using the GUI

Before you begin

  • Inband management IP addresses must be configured on the leafs where flows are to be sent to the Cisco Tetration server.

Procedure

Step 1

Navigate to Fabric > Fabric Policies > Policies > Analytics.

Step 2

From the ACTIONS drop-down list, choose Create Analytics Policy.

The Create Analytics Policy dialog box appears.
Step 3

Enter the following values in the Create Analytics Policy dialog box:

  1. Enter the cluster name in the Cluster field.

  2. Enter the server name in the Name field.

  3. Enter the destination IP address of the cluster in the IP field.

  4. Click Submit.

Note 

The destination port is not configurable. UDP port 5640 is always used for leaf switches and UDP port 5641 is always used for spine switches.

The DSCP is not configurable. VA (Voice Admit) is always used.
An Analytics Profile is created.
Step 4

Navigate to Fabric > Fabric Policies > Switches > Leaf Switches > Policy Groups.

Step 5

From the ACTIONS drop-down list, choose Create Leaf Switch Policy Group.

The Create Leaf Switch Policy Group dialog box appears.
Step 6

Enter the following values in the Create Leaf Switch Policy Group dialog box:

  1. Enter the policy group name in the Name field.

  2. Click the Analytics Policy drop-down arrow and choose the analytics policy.

  3. Click Submit.

A Policy Group is created.
Step 7

Navigate to Fabric > Fabric Policies > Switches > Leaf Switches > Profiles.

Step 8

From the ACTIONS drop-down list, choose Create Leaf Switch Profile.

The Create Leaf Switch Profile dialog box appears.
Step 9

Enter the following values in the Create Leaf Switch Profile dialog box:

  1. Enter a name in the Name field.

  2. In the Switch Associations table, click the + icon .

  3. Enter a value in the Name field.

  4. Enter a value in the Blocks field.

  5. Click the Policy Group drop-down and select the policy group.

  6. Click Update and Submit.

The configuration is pushed to the selected leafs.
The Cisco Tetration agent establishes communication with the Cisco Tetration server and starts uploading flows.

Configuring Cisco Tetration Analytics Using the REST API

Procedure

Step 1

Create the analytics policy.

Example:

<analyticsCluster name="tetration" >
<analyticsCfgSrv name="srv1" ip="10.30.30.7" >
</analyticsCfgSrv>
</analyticsCluster>
Step 2

Associate analytics with the policy group.

Example:

<fabricLeNodePGrp descr="" name="mypolicy6" ownerKey="" ownerTag="" rn="lenodepgrp-mypolicy6" status="">
   <fabricRsNodeCfgSrv rn="rsnodeProv" status="" tDn="uni/fabric/analytics/cluster-tetration/cfgsrv-srv1" />
</fabricLeNodePGrp>
Step 3

Associate the policy group with the switch.

Example:

<fabricLeafP name="leafs" rn="leprof-leafs" status="" >
    <fabricLeafS name="sw" rn="leaves-sw-typ-range" status="">
        <fabricRsLeNodePGrp rn="rsleNodePGrp" tDn="uni/fabric/funcprof/lenodepgrp-mypolicy6"/>
        <fabricNodeBlk name="switches" from_="101" to_="101" />
    </fabricLeafS>
</fabricLeafP>

Configuring Cisco Tetration Analytics Using the NX-OS Style CLI

Procedure

Step 1

configure terminal

Enters global configuration mode.

Example:

apic1# configure terminal
Step 2

analytics cluster cluster_name

Create the analytics policy.

Example:

apic1(config)# analytics cluster cluster1
Step 3

flow-exporter server_name

Configure external analytics information.

Example:

apic1(config-analytics)# flow-exporter server1
Step 4

destination ip_address

Configure the destination port.

Example:

apic1(config-analytics-cluster-exporter)# destination 192.0.2.1
Step 5

exit

Exit command mode.

Example:

# apic1(config-analytics-cluster-exporter)# exit
Step 6

exit

Exit command mode.

Example:

apic1(config-analytics)#  exit
Step 7

fabric-internal

Enters fabric internal configuration mode.

Example:

apic1(config)# fabric-internal
Step 8

template leaf-policy-group leaf_group_name

Define leaf policy group.

Example:

apic1(config-fabric-internal)# template leaf-policy-group lpg1
Step 9

inherit analytics-policy cluster cluster_name server server_name

Associate analytics policy to leaf policy group.

Example:

apic1(config-leaf-policy-group)# inherit analytics-policy cluster cluster1 server server1
Step 10

exit

Exit command mode.

Example:

apic1(config-leaf-policy-group)# exit
Step 11

leaf-profile lleaf_profile_name

Define leaf profile.

Example:

apic1(config-fabric-internal)# leaf-profile lp1
Step 12

leaf-group leaf_group_name

Define leaf group.

Example:

apic1(config-leaf-profile)# leaf-group lg1
Step 13

leaf-policy-group leaf_policy_group_name

Associate leaf policy group to leaf group.

Example:

apic1(config-leaf-group)# leaf-policy-group lpg1
Step 14

leaf leaf_group_number

Add nodes to leaf group.

Example:

apic1(config-leaf-group)# leaf 101
Step 15

show analytics

Display analytics.

Note 

The destination port is not configurable. UDP port 5640 is always used for leaf switches and UDP port 5641 is always used for spine switches.

The DSCP is not configurable. VA (Voice Admit) is always used.

Example:

apic1# show analytics
Cluster              : cluster1
  Config Server Name : server1
    Destination IP   : 192.0.2.1
    Destination Port : unspecified
    DSCP             : VA
Step 16

show running-config analytics

Display running configuration analytics.

Example:

apic1# show running-config analytics
# Command: show running-config analytics
# Time: Wed May 25 21:14:43 2016
  analytics cluster cluster1
    flow-exporter server1
      destination 192.0.2.1
      destination-port unspecified
      dscp VA
      ip-filter-action deny
      exit
    exit
apic1#