This test reports the status and speed statistics related to every WWN of the switch port. The default parameters associated with this will be displayed at the bottom of this page.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• In the HOST text box, the host name of the server for which the test is to be configured has to be specified.

• The port number through which the device exposes its SNMP MIB has to be specified in the SNMPPORT text box. The default value is 161.

• 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.

• The community string of the Cisco device has to be provided in the SNMPCOMMUNITY text box. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVERSION chosen is v3, then this parameter will not appear.

• The USERNAME 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 the MIB. Therefore, specify the name of such a user against the USERNAME parameter.

• The CONTEXT 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.

• Specify the password that corresponds to the above-mentioned USERNAME in the AUTHPASS text box. This parameter once again appears only if the SNMPVERSION selected is v3.

• Confirm the AUTHPASS by retyping it in the CONFIRM PASSWORD text box.

• The AUTHTYPE 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:

• MD5 - Message Digest Algorithm
• SHA - Secure Hash Algorithm

• The ENCRYPTFLAG appears only when v3 is selected as the SNMPVERSION. By default, the eG agent does not encrypt SNMP requests. Accordingly, the ENCRYPTFLAG is set to NO by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the YES option.

• 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:

• DES - Data Encryption Standard
• AES - Advanced Encryption Standard

• Specify the encryption password in the ENCRYPTPASSWORD text box.

• Confirm the encryption password by retyping it in the CONFIRM PASSWORD text box.

• Specify the duration (in seconds) within which the SNMP query executed by this test should time out in the TIMEOUT text box. The default is 10 seconds.

• This test reports a measure named OperStatus, which indicates the current operational state of every fibre channel port. Typically, the Cisco SAN switch assigns a state code to every port to indicate the operational state of that port - this code is in fact a number between 1 and 131. Of these 131 state codes, a few codes might indicate Critical failures, a few could indicate Major errors, a few more could denote Minor issues, and some may just report general status information.

  To indicate to the eG agent which of the 131 state codes represent Critical failures, which ones indicate Major errors, and which state codes denote Minor issues, the administrator can provide a comma-separated list of codes against the CRITICALERRORCODES, MAJORERRORCODES, and MINORERRORCODES parameters, respectively. For instance, the administrators might consider the codes 3, 6, and 7 to be critical, as they represent critical failures such as a hwfailure, a swfailure, and a linkfailure, respectively. Therefore, the CRITICALERRORCODES specification in this case will be: 3,6,7.

  The eG agent on the other hand, internally assigns a number to each of the error code specifications - 3 for Critical, 2 for Major, 1 for Minor, and 0 for Others.

  Now, assume that the SNMP MIB of the switch returns the state code 6 for a particular port. In this case, the eG agent first checks whether any of the three test parameters, namely - CRITICALERRORCODES, MAJORERRORCODES, and MINORERRORCODES - are configured with the reported state code - in the case of our example, the CRITICALERRORCODES parameter is configured with the state code 6. Once a match is found, the eG agent automatically reports the value it internally maintains for Critical error codes - i.e., the value 3 - as the value of the OperStatus measure for this port. If a match is not found - i.e., if none of the three parameters mentioned above are configured with the state code representing the current state of the port - then the eG agent automatically reports the value 0 as the value of the OperStatus measure - this is because, the eG agent automatically assumes that such a state code belongs to the Others category.

• This test reports a measure named OperStatus, which indicates the current operational state of every fibre channel port. Typically, the Cisco SAN switch assigns a state code to every port to indicate the operational state of that port - this code is in fact a number between 1 and 131. Of these 131 state codes, a few codes might indicate Critical failures, a few could indicate Major errors, a few more could denote Minor issues, and some may just report general status information.

  To indicate to the eG agent which of the 131 state codes represent Critical failures, which ones indicate Major errors, and which state codes denote Minor issues, the administrator can provide a comma-separated list of codes against the CRITICALERRORCODES, MAJORERRORCODES, and MINORERRORCODES parameters, respectively. For instance, the administrators might consider the codes 11, 12, and 13 to be major, as they represent major error conditions such as vsanInactive, adminDown, and channelAdminDown, respectively. Therefore, the MAJORERRORCODES specification in this case will be: 11,12,13.

  The eG agent on the other hand, internally assigns a number to each of the error code specifications - 3 for Critical, 2 for Major, 1 for Minor, and 0 for Others. Now, assume that the SNMP MIB of the switch returns the state code 13 for a particular port. In this case, the eG agent first checks whether any of the three test parameters, namely - CRITICALERRORCODES, MAJORERRORCODES, and MINORERRORCODES- are configured with the reported state code - in the case of our example, the MAJORERRORCODES parameter is configured with the state code 13. Once a match is found, the eG agent automatically reports the value it internally maintains for Major error codes - i.e., the value 2 - as the value of the OperStatus measure for this port. If a match is not found - i.e., if none of the three parameters mentioned above are configured with the state code representing the current state of a port - then the eG agent automatically reports the value 0 as the value of the OperStatus measure - this is because, the eG agent automatically assumes that such a state code belongs to the Others category.

• This test reports a measure named OperSatus, which indicates the current operational state of every fibre channel port. Typically, the Cisco SAN switch assigns a state code to every port to indicate the operational state of that port - this code is in fact a number between 1 and 131. Of these 131 state codes, a few codes might indicate Critical failures, a few could indicate Major errors, a few more could denote Minor issues, and some may just report general status information.

  To indicate to the eG agent which of the 131 state codes represent Critical failures, which ones indicate Major errors, and which state codes denote Minor issues, the administrator can provide a comma-separated list of codes against the CRITICALERRORCODES, MAJORERRORCODES, and MINORERRORCODES parameters, respectively. For instance, the administrators might consider the codes 25, 29, and 30 to be minor, as they represent minor error conditions such as a vsanMismatchIsolation, fcotNotPresent, and fcotVendorNotSupported, respectively. Therefore, the MINORERRORCODES specification in this case will be: 25,29,30. The eG agent on the other hand, internally assigns a number to each of the error code specifications - 3 for Critical, 2 for Major, 1 for Minor, and 0 for Others. Now, assume that the SNMP MIB of the switch returns the state code 25 for a particular port. In this case, the eG agent first checks whether any of three test parameters, namely - CRITICALERRORCODES, MAJORERRORCODES, and MINORERRORCODES- are configured with the reported state code - in the case of our example, the MINORERRORCODES parameter is configured with the state code 25. Once a match is found, the eG agent automatically reports the value it internally maintains for Minor error codes - i.e., the value 1 - as the value of the OperStatus measure for this port. If a match is not found - i.e., if none of the three parameters mentioned above are configured with the state code representing the current state of the port - then the eG agent automatically reports the value 0 as the value of the OperStatus measure - this is because, the eG agent automatically assumes that such a state code belongs to the Others category.

• 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 the DATA OVER TCP flag to Yes. By default, this flag is set to No.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the Update button will register the changes made and the selected server will move over to the CONFIGURED COMPONENTS panel.

When changing the configuration for specific servers, a ?*? beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a ?$? or contain a series of ?*?. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.