nsight

Device Config Commands

Configures NSight database related parameters. Use this command to configure the data-update periodicity, number of applications posted to the NSight server for a wireless client, and the duration for which data is stored in the NSight database‘s buckets. These parameters impact the amount of data stored in the NSight DB and interval at which data is aggregated and expired within the NSight DB. For more information on data aggregation and expiration, see Usage Guidelines (Data Aggregation and Expiration).

Configure these parameters in the NSight server‘s device configuration mode.

Supported in the following platforms:

Service Platforms — NX9500, NX9600, VX9000

Syntax

nsight database [statistics|summary]

nsight database statistics [avc-update-interval|max-apps-per-client|update-interval|wireless-clients-update-interval]

nsight database statistics [avc-update-interval|update-interval|wireless-clients-update-interval] [120|30|300|60|600]

nsight database statistics max-apps-per-client <1-1000>

nsight database summary duration <1-24> <1-168> <1-2160> <24-26280>

Parameters

nsight database statistics [avc-update-interval|update-interval|wireless-clients-update-interval] 
[120|30|300|60|600]


nsight database statistics	Configures NSight database statistics related parameters
avc-update-interval	Configures the interval, in seconds, at which Application Visibility and Control (AVC) statistics is updated to the NSight database. This interval represents the rate at which AVC-related data is inserted in the NSight database‘s first bucket. This first bucket data is referred to as the RAW records. A bucket is a database collection that holds statistical data on a per RF Domain basis. For more information, see Usage Guidelines (Data Aggregation and Expiration). When configured, RF Domain managers posting AVC-related data to the NSight server receive a reply from the NSight server intimating the next update time. The NSight server calculates the ‘next update time‘ based on the avc-update-interval configured here.
update-interval	Configures the interval, in seconds, at which data is updated to the NSIght server. This interval represents the rate at which data (excluding AVC and wireless-clients related statistics) is inserted in the NSight database‘s first bucket. This first bucket data is referred to as the RAW records. A bucket is a database collection that holds statistical data on a per RF Domain basis. For more information, see Usage Guidelines (Data Aggregation and Expiration). When configured, RF Domain managers posting data to the NSight server receive a reply from the NSight server intimating the next update time. The NSight server calculates the ‘next update time‘ based on the update-interval configured here. Note: Use the ‘avc-update-interval‘ and ‘wireless-clients-update-interval‘ keywords to configure update interval for AVC-related and wireless-clients related information respectively.
wireless-clients-update-interval	Configures the interval, in seconds, at which wireless-client statistics is updated to the NSIght server. This interval represents the rate at which wireless-clients related statistics is inserted in the NSight database‘s first bucket. This first bucket data is referred to as the RAW records. A bucket is a database collection that holds statistical data on a per RF Domain basis. For more information, see Usage Guidelines (Data Aggregation and Expiration). When configured, RF Domain managers posting wireless-client related data to the NSight server receive a reply from the NSight server intimating the next update time. The NSight server calculates the ‘next update time‘ based on the wireless-clients-update-interval configured here.
[120\|30\|300\|60\|600]	The following keywords are common to all of the above parameters: 120 – Sets the data-update periodicity as 120 seconds (2 minutes) 30 – Sets the data-update periodicity as 30 seconds 300 – Sets the data-update periodicity as 300 seconds (5 minutes). This is the default setting for the ‘avc-update-interval‘ and ‘wireless-clients-update-interval‘ parameters. 60 – Sets the data-update periodicity as 60 seconds (1 minute). This is the default setting for the ‘update-interval‘ parameter. 600 – Sets the data-update periodicity as 600 seconds (10 minutes)

nsight database statistics max-apps-per-client <1-1000>


nsight database statistics	Configures NSight database statistics related parameters
max-apps-per-client	Configures the maximum number of applications per wireless-client to be posted to the NSight server within the configured data-update interval. This information is included in the AVC statistics posted by RF Domain managers to the NSIght server.
<1-1000>	Specify the number of applications posted from 1 - 1000. The default is 10 applications per wireless client.

nsight database summary duration <1-24> <1-168> <1-2160> <24-26280>


nsight database summary	Configures the NSight database‘s per-bucket data storage duration
duration <1-24> <1-168> <1-2160> <24-26280>	Configures the duration for which data is stored on a per-bucket basis <1-24> – Specify the bucket 1 duration from 1 - 24 hours (i.e. 1 hour to 1 day). The default is 8 hours. <1-168> – Specify the bucket 2 duration from 1 - 168 hours (i.e. 1 hour to 7 days). The default is 24 hours. <1-2160> – Specify the bucket 3 duration from 1 - 2160 hours (i.e. 1 hour to 90 days). The default is 7 days (168 hours). <24-26280> – Specify the bucket 4 duration from 24 - 26280 hours (i.e. 1 day to 3 years). The default is 365 days (1 year). Note: A bucket is a database collection that holds statistical data for each RF Domain within the network. (Note, only those RF Domain‘s that are using an NSight policy with the NSight server host configured will post data to the NSight server. For more information, see use (rf-domain-config-mode). NSight database has four (4) buckets. The data from each bucket is aggregated and pushed to the next bucket once the data storage duration, specified for the bucket, has exceeded. For more information on data aggregation, see Usage Guidelines (Data Aggregation and Expiration).

Usage Guidelines (Data Aggregation and Expiration)

Data Aggregation:

The NSight functionality, a data analytics tool, analyzes data that is generated periodically by the nodes within the managed wireless LAN. For large WLAN networks, generating significantly large amount of data, storing data forever is neither feasible nor beneficial. Therefore, older statistics are summarized into aggregated (averaged) records. All records, for a fixed time period in past, are summarized into one record by taking an average of them. Although this causes a loss in the data‘s granularity, average numbers for any given time period is still available.

Statistical data periodically posted by RF Domain managers to the NSight server are stored in buckets (database collections) within the NSight database. There are four buckets in total. These are:

First bucket (termed as the RAW bucket) - B1
Second bucket - B2
Third bucket - B3
Fourth bucket - B4

On completion of the data storage duration, records from a bucket are aggregated (at a fixed rate) and inserted into the next bucket. The rate at which records are aggregated into the next bucket becomes the next bucket‘s granularity. For example, the B1 records (that have exceeded the data storage duration configured for B1) are aggregated (at the rate specified) and inserted into B2. Similarly, data from B2 are aggregated into B3, and from B3 to B4. The fixed rate of aggregation (or granularity) AND default storage duration for each bucket is as follows:

B1: storage duration 8 hours
B2: granularity 10 minutes / storage duration 24 hours
B3: granularity 1 hour / storage duration 7 days
B4: granularity 1 day / storage duration 1 year

Let us consider (with default update-interval settings) the growth of any one of the statistical buckets.

Since B1‘s default data storage duration is 8 hours, B1 will hold a maximum of 960 records per RF Domain after 8 hours (updated at the rate of 30 seconds).
Since B2‘s granularity is 10 minutes, every 10 minutes 20 records from the B1 will be aggregated into a single record and inserted into B2.
Since B2‘s default storage duration is 24 hours, it will contain a maximum of 144 records per RF Domain after 24 hours.
Since B3‘s granularity is 1 hour, every hour 6 records from B2 will be aggregated into a single record and inserted into B3.
Since B3‘s default storage duration is 7 days, it will contain a maximum of 168 records per RF Domain after 7 days.
Since B4‘s granularity is 1 day, every day 24 records from B3 will be aggregated into a single record and inserted into B4.
Since B4‘s default storage duration is 365 days, it will contain a maximum of 365 records per RF Domain after 1 year.

Data Expiration:

The expiration of older records (also referred to as purging or deleting of records) occurs along with data aggregation for each bucket.

Let us consider (with default data storage-duration settings) the expiration of data for any one of the statistical buckets.

As stated earlier, at the end of 8 hours B1 will have 960 records per RF Domain. After a period of 8 hours and 10 minutes, all 960 records are aggregated into 144 records and inserted into B2. To enable B1 to hold exactly 8 hours worth of data, 20 of the oldest records (corresponding to the first 10 minutes) are purged from B1 at the end of 8 hours and 10 minutes. This expiration cycle is triggered every 10 minutes.
At the end of 24 hours B2 will have 144 records per RF Domain. After a period of 24 hours and 10 minutes, one of the oldest record (corresponding to the first 10 minutes) is purged from B2. This expiration cycle is triggered every 10 minutes to enable B2 to maintain exactly 24 hours worth of data.
At the end of 7 days B3 will have 168 records per RF Domain. After a period of 7 days and one hour one of the oldest record (corresponding to the first hour) is purged from B3. This expiration cycle is triggered every 1 hour to enable B3 to maintain exactly 7 days worth of data.
At the end of 365 days B4 will have 365 records per RF Domain. After 365 days, the oldest records (corresponding to the first day) are purged from B4. This expiration cycle is triggered every 1 day to enable B4 to maintain exactly 365 days worth of data.

Example

nx9500-6C8809(config-device-B4-C7-99-6C-88-09)#nsight database statistics  avc-update-interval 120

nx9500-6C8809(config-device-B4-C7-99-6C-88-09)#nsight database statistics  update-interval 30

nx9500-6C8809(config-device-B4-C7-99-6C-88-09)#nsight database statistics  wireless-clients-update-interval 600

nx9500-6C8809(config-device-B4-C7-99-6C-88-09)#nsight database statistics  max-apps-per-client 20

nx9500-6C8809(config-device-B4-C7-99-6C-88-09)#nsight database summary duration 12 30 200 500

nx9500-6C8809(config-device-B4-C7-99-6C-88-09)#show context include-factory | include nsight
 use nsight-policy nsight-noc
 nsight database statistics update-interval 30
 nsight database statistics wireless-clients-update-interval 600
 nsight database summary duration 12 30 200 500
 nsight database statistics avc-update-interval 120
 nsight database statistics max-apps-per-mu 20
nx9500-6C8809(config-device-B4-C7-99-6C-88-09)#

Related Commands


no	Reverts the NSight database related parameters configured to default values