Cisco WAP Clients Test
For each client connected to the network via the target Cisco Wireless Accesspoint, this test reveals the authentication status and the amount of data transmitted and received. This test also reports the packets transmitted from and received by each client and also throws light on the amount of data dropped during transmission/reception. Using this test, administrators can determine the client that is tranmitting/receiving the maximum amount of data and figure out if the data/packets transmitted/received is legitimate.
Target of the test : A Cisco Wireless Accesspoint
Agent deploying the test : An external agent
Outputs of the test : One set of results for each Network:Client associated with the target Cisco Wireless Accesspoint being monitored
Parameters | Description |
---|---|
Test period |
How often should the test be executed |
Host |
The host for which the test is to be configured. |
SNMPPort |
The port at which the monitored target exposes its SNMP MIB; the default is 161. |
SNMPversion |
By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the SNMPversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list. |
SNMPCommunity |
The SNMP community name that the test uses to communicate with the firewall. This parameter is specific to SNMP v1 and v2 only. Therefore, if the snmpversion chosen is v3, then this parameter will not appear. |
Username |
This parameter appears only when v3 is selected as the SNMPVersion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against this parameter. |
Context |
This parameter appears only when v3 is selected as the SNMPVersion. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the Username provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the Username in the Context text box. By default, this parameter is set to none. |
Authpass |
Specify the password that corresponds to the above-mentioned Username. This parameter once again appears only if the SNMPversion selected is v3. |
Confirm password |
Confirm the Authpass by retyping it here. |
Authtype |
This parameter too appears only if v3 is selected as the SNMPversion. From the AuthType list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:
|
Encryptflag |
This flag appears only when v3 is selected as the SNMPversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. |
Encrypttype |
If the EncryptFlag is set to Yes, then you will have to mention the encryption type by selecting an option from the EncryptType list. SNMP v3 supports the following encryption types:
|
Encryptpassword |
Specify the encryption password here. |
Confirm Password |
Confirm the encryption password by retyping it here. |
Timeout |
Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. The default is 10 seconds. |
Data Over TCP |
By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic – for instance, certain types of data traffic or traffic pertaining to specific components – to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No. |
EngineID |
This parameter appears only when v3 is selected as the SNMPVersion. Sometimes, the test may not report metrics when AES192 or AES256 is chosen as the Encryption type. To ensure that the test report metrics consistently, administrators need to set this flag to Yes. By default, this parameter is set to No. |
Measurement | Description | Measurement Unit | Interpretation | ||||||
---|---|---|---|---|---|---|---|---|---|
is Authenticated? |
Indicates the authentication status of this client on the network associated with the access point. |
|
The values reported by this measure and their corresponding numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the above-mentioned Measure values while indicating the authentication status of each client. However, in the graph of this measure, states will be represented using their corresponding numeric equivalents - i.e., 0 or 1. |
||||||
Received packets |
Indicates the number of packets received by this client during the last measurement period. |
Packets |
Compare the value of these measures across the clients to determine the client that is transmitting / receiving the maximum / least number of packets.
|
||||||
Transmitted packets |
Indicates the number of packets transmitted by this client during the last measurement period. |
Packets |
|||||||
Received data |
Indicates the amount of data received by this client during the last measurement period. |
MB |
Compare the value of these measures across the clients to figure out the client that is transmitting / receiving the maximum / least amount of data.
|
||||||
Transmitted data |
Indicates the amount of data transmitted by this client during the last measurement period. |
MB |
|||||||
Dropped packets received |
Indicates the number of packets dropped during reception by this client during the last measurement period. |
Packets |
Compare the value of these measures across the clients to figure out the client that dropped the maximum number of packets during transmission / reception.
|
||||||
Packets dropped during transmission |
Indicates the number of packets dropped during transmission from this client during the last measurement period. |
Packets |
|||||||
Dropped data received |
Indicates the amount of data dropped during reception by this client during the last measurement period. |
MB |
Compare the value of these measures across the clients to figure out the client that dropped the maximum amount of data during transmission / reception.
|
||||||
Data dropped during transmission |
Indicates the amount of data dropped during transmission from this client during the last measurement period. |
MB |
|||||||
Received TS violate packets |
Indicates the number of packets received by this client that exceeds the normal active Traffic Stream (TS) downlink bandwidth for which the client has not been admitted. |
Packets |
|
||||||
Transmitted TS violate packets |
Indicates the number of packets transmitted from this client that exceeds the normal active Traffic Stream (TS) uplink bandwidth for which the client has not been admitted. |
Packets |
|