Skip to main content
Versa Networks

Configure Organization Limits

  1. Last updated
  2. Save as PDF

Versa-logo-release-icon.pngFor supported software information, click here.

You can set organization-specific (tenant-specific) quality of service (QoS) limits, and you can limit the interfaces, networks, routing instances, and provider organizations for data traffic for a specific organization. For Releases 22.1.3 and later, you can configure policers on ingress interfaces. You configure organization settings for each organization in a single tenant or for a multitenant setup.

This article describes how to configure organization limits and how to monitor policers on ingress interfaces.

Configure Organization Limits

  1. In Director view:
    1. Select the Administration tab in the top menu bar.
    2. Select Appliances in the left menu bar.
    3. Select a device name in the main panel. The view changes to Appliance view.
    4. Select an organization.
  2. Select the Configuration tab in the top menu bar.
  3. Select Others > Organization > Limits in the left menu bar. The main pane displays the organizations associated with the Controller node.

    organization-limit-home.png
  4. Click an organization name in the main pane. The Edit Organization Limit popup window displays.

    organization-limit-general-tab.png
  5. Select the General tab, and then enter information for the following fields.
     
    Field Description
    Organization Name Displays the name of the organization.
    Description Enter a text description for the organization.
    DHCP Select a DHCP profile. For more information, see Configure DHCP.
    Session (Group of Fields) Enter organization limits related to sessions.
    • Rate
    		 Enter the maximum data exchange rate.
    Range: 16 through 4294967295
    Default: 1000000
    • Limit
    		 Enter the maximum number of sessions allowed. For more information, see Configure Service and Session Options.
    Range: 1 through 5000000 (5 million)
    Default: 1000000 (1 million)
    Fragment Reassembly (For Releases 22.1.1 and later.) Click to disable the reassembly of fragmented packets received by the organization. By default, fragment reassembly is enabled.
    Enterprise Names Click the add-icon.png Add icon and select the name of an enterprise that is in the organization.
    Domain Names

    Click the add-icon.png Add icon and select the name of a domain that is in the organization.
    Gateway FQDN Enter the gateway fully qualified domain name (FQDN) of the organization. Each organization can have up to eight gateway FQDNs. Each gateway FQDN must be unique.
    Group FQDN Enter the gateway group FQDN of the organization. Each organization can have up to eight gateway group FQDNs.
  6. Select the Traffic Identification tab, and enter information for the following fields.

    organization-limit-traffic-tab.png
     
    Field Description
    Interfaces Click the add-icon.png Add icon and select the name of an interface that is part of the organization.
    Networks Click the add-icon.png Add icon and select the name of a network that is part of the organization.
  7. Select the Resources tab, and enter information for the following fields.

    organization-limit-resources-tab.png
     
    Field Description
    Available Routing Instances Click the add-icon.png Add icon and select the name of a routing instance that is part of the organization.
    Owned Routing Instances Click the add-icon.png Add icon and select the name of a routing instance that is owned by the organization.
    Available Provider Organizations Click the add-icon.png Add icon and select the name of a provider organization that is available for the organization to use.
    Available Networks Click the add-icon.png Add icon and select the name of a network that is available for the organization to use.
  8. Select the Services tab, and enter information for the following fields.

    organization-limit-services-tab.png
     
    Field Description
    Available Service Node Groups Click the add-icon.png Add icon and select the name of a service node group (SNG) that is part of the organization.
    Services Click the add-icon.png Add icon and select the name of a service that is available for the organization to use.
    Available Service Node Group Cluster Click the add-icon.png Add icon and select the name of an SNG cluster service that is part of the organization.
  9. Select the QoS tab, and enter information for the following fields.

    organization-limit-qos-tab.png
     
    Field Description
    Peak Rate

    Enter the ingress peak rate in packets per second (pps) for the organization.

    Range: 1 through 4294967295 pps

    Default: None
    Peak Rate

    Enter the peak ingress rate in kilobits per second (kbps) for the organization.

    Range: 64 through 4294967295 kbps

    Default: None
    Peak Burst Size

    Enter the maximum burst size, in bytes per second.

    Range: 128 through 524288 bytes per second.

    Default: None
    Shared Interfaces (Group of Fields)  
    • Interface (Required)
    		 Select an interface in the organization on which to enable tenant-based shaper.
    • Shaping Rate (Required)

    Enter the shaping rate, in kilobytes per second (Kbps).

    Range: 8 through 10000000 Kbps
    Default: None
    • Burst Size

    Enter the burst size, in bytes.

    Range: 1000 through 4294967295 bytes
    add-icon-blue.png Add icon Click the add-icon-blue.png Add icon to add the QoS shared interface configuration for the organization.
    Ingress Interface Policer (Group of Fields)

    (For Releases 22.1.3 and later.) Configure a policer on an ingress interface. Note that when you configure an ingress interface policer, all branches must be running Releases 22.1.3 or later.
    • Interface (Required)
    		 Select an interface in the organization on which to configure the ingress policer.
    • Peak Rate (Required)

    Enter the peak ingress rate, in kilobits per second (kbps), for the tenant and interface.

    Range: 64 through 4294967295 kbps

    Default: None
    • Peak Burst Size

    Enter the maximum burst size, in bytes per second.

    Range: 128 through 524288 bytes per second.

    Default: None
    add-icon-blue.png Add icon Click the add-icon-blue.png Add icon to add the QoS ingress interface policer configuration for the organization.
  10. Click OK.

To mitigate packet drops caused by microbursts of traffic, you can issue the request system isolate-cpu enable CLI command on all branches, including the remote branch that sends traffic to the branch on which the ingress interface policer is configured. This command isolates the CPU, which optimizes the platform's performance. After you issue this command, you must reboot the device.

Monitor the Ingress Interface Policer

For Releases 22.1.3 and later.

  1. In Director view, select the Monitor tab in the top menu bar.
  2. Select the Devices tab in the horizontal menu bar.
  3. In the table in the main pane, click the name of an organization. The view changes to Appliance view.

    monitor-device-ingress-policer.png
  4. Select Networking > CoS > Ingress Interface Policer in the horizontal menu bar to monitor the ingress interface policer statistics.

    monitor-device-ingress-policer1.png

Supported Software Information

Releases 20.2 and later support all content described in this article, except:

  • Releases 22.1.1 adds support for fragment reassembly.
  • Releases 22.1.3 adds support for ingress interface policers.