<installdirectory>/bin/ibrix_event -l
•
View adesignated number of events. The command displays the 100 most recent messages
by default. Use the
-n EVENTS_COUNT
option to increase or decrease the number of events
displayed.
<installdirectory>/bin/ibrix_event -l [-n EVENTS_COUNT]
The following command displays the 25 most recent events:
<installdirectory>/bin/ibrix_event -l -n 25
Removing events from the events database table
The
ibrix_event -p
command removes events from the events table, starting with the oldest
events. The default is to remove the oldest seven days of events. To change the number of days,
include the
-o DAYS_COUNT
option.
<installdirectory>/bin/ibrix_event -p [-o DAYS_COUNT]
Monitoring cluster health
To monitor the functional health of file serving nodes and X9000 clients, execute the
ibrix_health
command. This command checks host performance in several functional areas and provides either
a summary or a detailed report of the results.
Health checks
The
ibrix_health
command runs these health checks on file serving nodes:
•
Pings remote file serving nodes that share a network with the test hosts. Remote servers that
are pingable might not be connected to a test host because of a Linux or X9000 Software
issue. Remote servers that are not pingable might be down or have a network problem.
•
If test hosts are assigned to be network interface monitors, pings their monitored interfaces to
assess the health of the connection. (For information on network interface monitoring, see
“Using network interface monitoring” (page 31)
.)
•
Determines whether specified hosts can read their physical volumes.
The
ibrix_health
command runs this health check on both file serving nodes and X9000 clients:
•
Determines whether information maps on the tested hosts are consistent with the configuration
database.
If you include the
-b
option, the command also checks the health of standby servers (if configured).
Health check reports
The summary report provides an overall health check result for all tested file serving nodes and
X9000 clients, followed by individual results. If you include the
-b
option, the standby servers for
all tested file serving nodes are included when the overall result is determined. The results will be
one of the following:
•
Passed.
All tested hosts and standby servers passed every health check.
•
Failed.
One or more tested hosts failed a health check. The health status of standby servers is
not included when this result is calculated.
•
Warning.
A suboptimal condition that might require your attention was found on one or more
tested hosts or standby servers.
The detailed report consists of the summary report and the following additional data:
•
Summary of the test results
•
Host information such as operational state, performance data, and version data
Monitoring cluster health
51
Содержание StorageWorks X9720
Страница 137: ...13 When the Configure Network dialog box reappears select bond0 Configuring a file serving node 137 ...
Страница 178: ...English notice Estonian notice Finnish notice French notice 178 Regulatory compliance and safety ...
Страница 179: ...German notice Greek notice Hungarian notice Italian notice Waste Electrical and Electronic Equipment directive 179 ...
Страница 180: ...Latvian notice Lithuanian notice Polish notice Portuguese notice 180 Regulatory compliance and safety ...
Страница 181: ...Slovakian notice Slovenian notice Spanish notice Swedish notice Waste Electrical and Electronic Equipment directive 181 ...