Network Control Module Info Sheet

Document created by gfarrar Expert on Aug 1, 2016Last modified by fran.schwarzmann on Aug 15, 2016
Version 3Show Document
  • View in full screen mode

The purpose of the Network Control Module (NCM) is to assure network performance for multi-tiered applications for which the different layers are divided among multiple Virtual Machines.  The benefit applies to all Virtual Machines that frequently communicate with one another across the network.

 

Placing VMs that talk to each other frequently on the same host improves performance

 

Additional Entities Discovered:

Type

Definition

Examples

DPod

Set of closely connected providers

Hosts that are connected to a Top of Rack network switch or the hosts in a unified fabric chassis (Cisco UCS chassis)

VPod

Set of consumers that frequently communicate over the network

Multi-tiered applications running on separate VMs

 

New commodities:

  • Flow – Represents the communication between consumers (VMs)
  • Buffer -- Memory used to compensate for difference between transmission speeds and processing

 

Commodity Relationships:

 

NCM Requirements:

  • To Create VPods:
    • NetFlow or sFlow Collector
      • Switch in the environment forwards conversations to identify VMs that frequently communicate together

 

  • To Create DPods:
    • Arista Top of Rack switches
      • Ability to create DPod via Top of Rack switch
      • Track physical port congestion to enable smarter placement of VMs
    • Or Storage and/or Fabric Control Module
      • Creates relationship of hosts and storage

 

  • To Identify Port Congestion:
    • Arista Top of Rack switches

 

  • Storage Module, Fabric Control Module, or Arista Top of Rack Switch
    • Enables the creation of DPods by grouping closely connected providers

 

  • Arista Top of Rack switches (optional)
    • Creates DPods by identifying providers connected to the switch
    • Identifies port congestion of connected providers

 

NCM Requirements

 

Entity

 

 

VPods

  • Netflow Collector
  • sFlow Collector

 

DPods

  • Storage and/or Fabric Control Module
  • Arista Top of Rack Switch

Port Buffer Congestion

  • Arista Top of Rack Switch

 

 

 

Cost of Flow (internal to VMTurbo)

Level

Relationship

VMs running on hosts

0

Intra-Host

On the same host -- ideal

1

Intra-DPod

Connected to the same Top of Rack Switch or Fabric chassis

2

Cross-DPod

Separated across the network or different Fabric chassis – least desirable

 

 

Adding a Network Target:

  • Click on Network
  • Select the appropriate Network type
  • Add Hostname/IP, Username, and Password

 

Actions and Risks:

2 people found this helpful

Attachments

    Outcomes