Managing Consumption of Router Resources

This section describes the ways through which network administrators can manage the consumption of router resources on a Message VPN-basis. It also describes how to set resource consumption limits for endpoints and to control access to resources through client profiles.

Overbooking Router Resources

Note:  When planning how to manage router resources on a Message VPN‑basis, you should be familiar with the system-level limits for Guaranteed Message delivery (for example, the combined number of queues and topic endpoints). In addition, the maximum Guaranteed message ingress rates offered by specific Assured Deliver Blade (ADB) and router types are useful for determining what type of load the Message VPNs could encounter.

A network administrator can configure Message VPNs on the Solace router so that:

  • a full overbooking of all router resources is allowed

    This means that any Message VPN can consume all available router resources. This is the router default.

  • partial overbooking of router resources by Message VPNs is allowed

    This means that no single Message VPN may consume all resources, but their configured resource consumption limits are high enough that, in combination, they could reach the system limit.

  • no overbooking of router resources is allowed

    This means that the sum of the configured consumption limits of all Message VPNs does not permit the system limits to be exceeded.

Note:  A Solace router can support up to 500 Message VPNs simultaneously.

The following figure provides examples of full, partial, and no overbooking scenarios for the maximum permitted number of client connections for a model of 3260 appliance that has a total system limit of 9,000 simultaneous client connections:

  • Scenario A shows a fully overbooked router—the maximum permitted number of simultaneous client connections for each Message VPN is the same as maximum allowed for the entire router.
  • Scenario B shows a partially overbooked router—although no single Message VPN allows the maximum permitted number of simultaneous client connections, the limits for the Message VPNs in combination exceed the system limit.
  • Scenario C shows a router that is not overbooked—the total maximum number of permitted simultaneous client connections for the entire router cannot be exceeded even when the values for each Message VPN are combined.

Overbooking Router Resources Scenarios

Setting Consumption Limits for VPNs

Through the Solace router Command Line Interface (CLI), a network administrator can set limits for the parameters listed below to control the consumption of router resources on a per-Message VPN-basis.

Message VPN-based Limits

Resource Parameter

To set, see...

The maximum number of clients that can simultaneously connect to a Message VPN.

Note:  The number of simultaneous client allowed for a Message VPN depends on the type of Solace router.

Configuring Maximum Connections

The maximum number of local client subscriptions that can be added to a Message VPN.

Configuring Maximum Subscriptions

The maximum amount of system-level message spool disk space (in MB) that a Message VPN can use.

Note:  The default value for the amount of disk storage permitted for a Message VPN is 0. Therefore, a value must be configured after a Message VPN is created so that it can spool messages.

Configuring the Max Spool Usage

Note:  This is also configurable on a per-Guaranteed endpoint‑basis.

The maximum number of simultaneous transacted sessions allowed for a Message VPN.

Configuring the Max Number of Transacted Sessions

The maximum number of queue and topic endpoints that can be created.

Configuring the Max Number of Endpoints

The maximum number egress flows (that is, Guaranteed message client receive flows) that can be created.

Configuring the Max Number of Flows

The maximum number ingress flows (that is, Guaranteed message client publish flows) that can be created.

Configuring the Max Number of Flows

Setting Consumption Limits for Endpoints

Through the Solace CLI, a network administrator can set limits for the parameters listed below to control the consumption of router resources on a per-endpoint-basis.

Endpoint-based Limits

Resource Parameter

To set, see...

The maximum number of messages spooled to an endpoint that can be delivered to a client on a flow but remained unacknowledged the client.

The maximum message size (in bytes) permitted for the given durable message queue or topic endpoint.

The maximum amount of message spool disk space (in MB) that a queue or a topic endpoint is permitted to use.

Controlling Access to Resources With Client Profiles

For each Message VPN, network administrators can configure client profiles to control the consumption of router resources by the clients using a client username that is assigned to that client profile. The following table lists client profile parameters that affect the amount of router resources clients can consume.

Router Resources Accessed Through Client Profiles

Resource Parameter

To set, see...

The maximum number of client connections that can simultaneously connect with the same client username account.

Configuring the Max Connections Per Username

The maximum number of local client subscriptions allowed for a single client connection.

Configuring the Max Permitted Subscriptions

The maximum depth of egress per-client priority queues, as measured in work units of 2048 bytes.

Configuring Egress Priority Queues

The maximum number of topics the router can track for performing the eliding function on each client connection.

Configuring the Maximum Number of Topics to Elide

Allow or deny clients to publish Guaranteed messages.

Note:  Publishing Guaranteed messages consumes message spool resources in the Message VPN when messages are enqueued for delivery to Guaranteed Messaging consumers. You can adjust this parameter to ensure that only authorized clients are allowed to publish Guaranteed messages.

Allowing Guaranteed Message Sends

Allow or deny clients to create Guaranteed endpoints.

You can adjust this parameter to ensure that only authorized clients are allowed to create Guaranteed endpoints.

Allowing Guaranteed Endpoint Creates

The maximum number of durable and non‑durable queues and topic endpoints that can be owned by clients using the same client username.

Allowing Guaranteed Endpoint Creates

Allow or deny clients to use transacted sessions using Solace messaging APIs.

You can adjust this parameter to ensure that only authorized clients are allowed to create Guaranteed endpoints.

Allowing Transacted Sessions

The maximum number of simultaneous transacted sessions allowed for a single client connection.

Configuring the Max Number of Transacted Sessions