Adding or Deleting sFlow Collector Nodes by Modifying instances.yml
Contrail Networking Release 2011 supports adding, removing, and reconfiguring collector nodes (also known as sFlow nodes) after the system is up and running. Prior to this release, collector nodes could only be added during provisioning.
This topic describes adding or deleting flow collector nodes
to an existing Contrail cluster by modifying the instances.yml file, which gets generated when Contrail cluster is provisioned by
using Contrail Command UI. The instances.yml file is created inside /var/tmp/contrail_cluster/<contrail_cluster_id> in contrail_command container.
You can:
Add flow collector nodes to a Contrail cluster without any existing flow collector node.
Add flow collector nodes to a Contrail cluster with existing flow collector nodes.
Delete flow collector nodes from a Contrail cluster.
When a new flow collector node is added, or an existing flow
collector node is deleted by modifying the existing instances.yml file:
Ansible playbook will run to first cleanup the flow collector nodes which need to be deleted.
Then Ansible playbook will run to set up the new flow collector nodes and to rebuild the cluster.
To add flow collector nodes:
Modify the
instances.ymlfile to add flow-collector nodes.Existing cluster details are in the
instances.yml. Theappformix_flowsrole designates Contrail Insights Flows node. The following example shows a snippet of section forinstances.ymlfor existing Contrail Insights Flows node details:instances: host1: ip: 10.87.3.85 provider: bms roles: appformix_bare_host: appformix_flows:New snippet for
instances.ymlto register one more node,host2, in the Contrail Insights Flows cluster:instances: host1: ip: 10.87.3.85 provider: bms roles: appformix_flows: host2: ip: 10.87.3.86 provider: bms roles:Run the following commands to add flow collector nodes:
cd /usr/share/contrail/appformix-ansible-deployer/xflow/ . venv/bin/activate bash deploy_insights_flows.sh <instance.yml file> --cluster-id <contrail_cluster_id>
To delete nodes from the Contrail cluster:
Modify the
instances.ymlfile to delete flow collector nodes. The following example shows a snippet of section forinstances.ymlfor existing Contrail Insights Flows node details:instances: host1: ip: 10.87.3.85 provider: bms roles: appformix_bare_host: appformix_flows: host2: ip: 10.87.3.86 provider: bms roles: appformix_bare_host: appformix_flows:New snippet for
instances.ymlto deregisterhost2from the Contrail Insights Flows cluster by detaching theappformix_flowsrole fromhost2:instances: host1: ip: 10.87.3.85 provider: bms roles: appformix_bare_host: appformix_flows: host2: ip: 10.87.3.86 provider: bms roles: appformix_bare_host:Run the following commands to delete the flow collector nodes:
cd /usr/share/contrail/appformix-ansible-deployer/xflow/ . venv/bin/activate bash deploy_insights_flows.sh <instance.yml file> -cluster-id <contrail_cluster_id>
Caveats
You can provision the collectors only once before fabric onboarding.
You cannot add new Contrail Insights Flows nodes to the cluster after initial provisioning.
Currently, only sFlow targets are supported.
Contrail Insights Flows nodes can be connected to only one leaf.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.