Display GigaSMART Application Resource Usage

GigaSMART applications, such as De-duplication and inline and Passive SSL decryption, use memory resources on the GigaSMART line card or module. As new GigaSMART applications are configured, the total resources on the GigaSMART line card or module can become fully used.

Starting in software version 4.4, you can display the GigaSMART application resource usage, which provides information about the applications that use resources. With this information, you can choose to free up resources on one application to use them on another.

 

Table 1: GigaSMART Application Resource Information

Name

Format

GSgroup

The alias of the GigaSMART group associated with the GigaSMART application.

Application

The list of licensed GigaSMART applications that use resources, including Adaptive Packet Filtering (APF), de-duplication, GPRS Tunneling Protocol (GTP), NetFlow Generation, Passive SSL decryption, Adaptive Session Filtering (ASF) with buffering, and inline SSL decryption.

Other GigaSMART applications (such as flow sampling, header addition, Header Stripping, ERSPAN tunnel decapsulation, slicing, masking, and others) do not have databases that store data, therefore they do not use resources and are not displayed with the show gsgroup gsapp-resource command.

% of Total

The percentage of the total amount of memory used by each GigaSMART application.

Configured Resource

The amount of resources configured for each GigaSMART application. The valid values are as follows:

■   app-max—Indicates the maximum amount of memory configured for the application. It is a pre-allocated amount.
■   integer, such as 2—Indicates the number of sessions configured, in the units specified. M indicates millions.

Installed Resource

The amount of resources installed for each GigaSMART application.

Licensed Quantity

The amount of resources licensed for each GigaSMART application.

Units

The units, such as sessions, or millions (M) of sessions.

GigaSMART application resources are managed per GigaSMART group (gsgroup). A gsgroup can be configured with one or more GigaSMART engine ports on one or more GigaSMART line cards or modules.

For most GigaSMART applications, resources are allocated automatically, based on configuration. For some GigaSMART applications, resources are allocated when they are configured in the gsgroup. For other applications, resources are allocated when a GigaSMART operation (gsop) using the application is created. For buffer ASF however, you can explicitly configure resources, in millions of sessions.

The allocation of resources for a new application will be successful if the application is licensed and if there is sufficient space for the new application.

If there is insufficient space, then the resources need to be managed to free up memory for the new application. Managing resources includes deleting applications that are no longer used.

However, deleting a GigaSMART application does not result in the immediate deletion of application resources. Once a resource has been allocated, it remains allocated. To delete resources for APF, out-of-band or inline SSL decryption, de-duplication, and GTP, remove the configuration related to the application, then reload the GigaSMART line card or module.

To remove the configuration related to an application, delete the gsop first, then delete the gsgroup. If the gsop or gsgroup is bound to a map, you will also have to delete the map.

The resources for buffer ASF depend on the number of sessions and the type of node. For example, GigaVUE‑HC3, 5 million sessions uses 26%.

For GigaVUE‑HC3, the resources for buffer ASF for the number of sessions is as follows:

■   2 million—11% of total resources
■   3 million—16% of total resources
■   4 million—21% of total resources
■   5 million—26% of total resources

Occasionally, the GigaSMART line card or module will need to be reloaded for changes to take effect and to allocate resources accordingly. Reloading also provides applications with contiguous memory.

The following message displays at the bottom of the output of the show gsgroup gsapp-resource command when the GigaSMART line card or module needs to be reloaded:

*Resource allocation changes have been made that require GigaSMART card 2/1/1 to be reloaded in order for them to take effect.

When this message is displayed, you cannot change the configuration relating to that application until after the reload. For example, you cannot use the gsop, associated with the gsgroup, in a map.

Use the following command to reload a GigaSMART line card or module:

(config) # card slot <slot ID> down

Use the following command to bring the GigaSMART line card or module back up:

(config) # no card slot <slot ID> down