|
Information required to monitor storage systems
|
|
|
Collection interval
|
Select the polling interval from the drop-down list. Default: 5. Unit: Minutes
|
Connection Credentials
Telnet/SSH Username
Telnet/SSH Password
Or
Shared Credentials
|
Enter the credentials used to connect to the element through Telnet or SSH.
Or
Select shared credentials from the drop down list if you wish to use pre-defined credentials.
|
WBEM/SSSU Credentials
WBEM/SSSU Username
WBEM/SSSU Password
Or
Shared Credentials
|
Optional: Enter the WBEM or SSSU credentials if required for connection to the element.
Or
Select shared credentials from the drop down list if you wish to use pre-defined login and password.
|
[SSH] Private Key
|
Specify the path of the private key used for SSH authentication.
|
[SSH] Passphrase
|
Specify the passphrase for the above imported private key.
|
[WBEM] Transport Protocol
|
Select the transport protocol: HTTP or HTTPS to be used for connecting to the CIM server.
|
[WBEM] Port
|
Enter the WBEM port number on which runs the CIM server.
|
[WBEM] Namespace
|
Optional: Enter the WBEM namespace used to connect to the CIM server.
|
Hostname
|
Enter the hostname or IP address of the element to be monitored.
|
SNMP version
|
Specify the SNMP version to be used by BPM Express for Hardware to retrieve information from the elements: SNMP v1; SNMP v2c; SNMP v3.
|
SNMP Port
|
Port number on which the SNMP agent is running.
|
SNMP Community
|
Enter the SNMP community string required for SNMP v1/SNMP v2c.
|
[SNMP v3] Username
|
Enter the username required for SNMP v3.
|
[SNMP v3] Authentication Protocol
|
Enter the protocol required for SNMP v3 authentication.
|
[SNMP v3] Authentication Password
|
Enter the password required for SNMP v3 authentication.
|
[SNMP v3] Privacy Protocol
|
Enter the privacy protocol required for SNMP v3.
|
[SNMP v3] Privacy Password
|
Enter the privacy password required for SNMP v3.
|
Error Count Auto-reset After
|
Specify the interval in hours for a reset of the Error Count parameter.
Certain devices are monitored by counting the number of encountered errors. The Error Count parameter triggers an alert as soon as an error is detected. The Error Count parameter and its alerts are automatically reset at the specified interval to prevent a single error from continuously raising alerts.
|
Link Status auto-reset after
|
The Link Status parameter triggers an alert as soon as a link fails. The Link failure alarm is automatically cleared at specified interval. Unit: hours.
|
Missing Device Detection
|
By default, the missing device(s) will be detected and monitored. Setting the option to Disable will deactivate the detection and the monitoring of the missing device(s).
|
In case of Status parameter value is UNKNOWN
|
Select the action to be performed when Hardware Express is unable to interpret the value of the Status parameter if it is UNKNOWN.
|
Default system wattage
|
Constant value (in Watts) to be used for the "Power Consumption" parameter and the "Energy Usage" report when the system is not able to report its actual energy usage. Use this setting if you know approximately the normal power consumption of this managed element and would like to compare it with other better instrumented systems and report on the global electricity consumption of your servers.
|
Debug Mode
|
Select Yes to enable the debug mode or No disable it. Default: No
The debug output is stored in a file on the RSM server. The debug file is located at: %RSM_HOME%\RSMxx\SEN_HW\sen_hw_debug_hostname.log
|
Sudo Configuration and Execution Methods
The BMC Performance Manager Express for Hardware can be configured to use different Credentials / the sudo utility in three different ways:
1st method: Sudo
The software logs into the server using the credentials Credentials: [Telnet/SSH], it then runs the command using sudo.
To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], the section Credentials: [Execution] and Credentials: [Root] needs to be blank (no user credentials), and the option Use Sudo Utility selected. The sudo utility would need to be configured for all commands that need root and the sudo utility would also need to be in the path of the Patrol User. Select the option Use Sudo Utility.
●i.e. ●login patrol ●sudo command 2nd method: Ultra Secure Sudo
The software logs into the server using the credentials Credentials: [Telnet/SSH], then does an su to Credentials: [Execution], then runs the command using sudo.
This method is a slight modification of the 1st method, which is rarely used outside ultra secure environments. This is used when the first username does not have the rights to run the sudo.
To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], the second, non-root user, but able to run the sudo command to be entered in Credentials: [Execution], and Credentials: [Root] to be left blank. The option Use Sudo Utility needs to be selected. The sudo utility would need to be configured for all commands that need root and the sudo utility would also need to be in the path of the Patrol User. Then select the option Use Sudo Utility.
●i.e. ●login patrol ●su - secure-user ●sudo command 3rd method: Root
The software logs into the server using credentials Credentials: [Telnet/SSH], then su to Credentials: [Root] and runs the command directly.
To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], section Credentials: [Execution] left blank, and the root credentials section Credentials: [Root]. The select the option Use above Execution/Root credentials.
●i.e. ●login patrol ●su - root ●command
Related Topics
Information required to monitor Windows systems
Information required for monitoring “Other” platforms i.e. Blade chassis, management cards etc.
| 
