Oracle® Enterprise Manager System Monitoring Plug-in Metric Reference Manual for Storage Management 10g Release 2 (10.2.0.4) Part Number B28751-03 |
|
|
PDF · Mobi · ePub |
Note:
Network Appliance Filer-related metrics are not part of the System Monitoring Plug-in release. They are part of the Enterprise Manager Grid Control release.You can use the All Metrics page for a Network Appliance Filer target in the Enterprise Manager Grid Control to view the metrics that have been collected for that target by the Oracle Management Agent.
The Network Appliance Filer metrics provide description, summary, multiple threshold (where applicable), data source, and user action information for each metric.
The following abbreviations are used in this chapter:
SNMP (Simple Network Management Protocol)
MIB (Management Information Base)
Network interface statistics give a good indication of a network level performance and health of the Network Appliance Filer.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Table 4-1 10 Megabit Network Cards Statistics
Metric | Description | Data Source (SNMP MIB Object)Foot 1 |
---|---|---|
Network Received Rate (Kilobits/second) |
Rate of data received on the interface, in kilobits/sec |
Rate of ifInOctets (1.3.6.1.2.1.2.2.1.10) |
Network Sent Rate (Kilobits/second) |
Rate of data transmitted on the interface, in kilobits/sec |
Rate of ifOutOctets (1.3.6.1.2.1.2.2.1.16) |
Footnote 1 These objects return inbound traffic as bytes, rates of which will be computed as kilobits/second.
Network interface statistics give a good indication of the network level performance and health of the Network Appliance Filer.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics, their descriptions, and data sources.
Table 4-2 100 Megabit Network Cards Statistics
Metric | Description | Data Source (SNMP MIB Object)Foot 1 |
---|---|---|
Network Received Rate (Kilobits/second) |
Rate of data received on the interface, in kilobits/sec |
Rate of ifInOctets (1.3.6.1.2.1.2.2.1.10) |
Network Sent Rate (Kilobits/second) |
Rate of data transmitted on the interface, in kilobits/sec |
Rate of ifOutOctets (1.3.6.1.2.1.2.2.1.16) |
Footnote 1 These objects return inbound traffic as bytes, rates of which will be computed as kilobits/second.
Network Appliance Filer health is directly proportional to the file system usage and environmental parameters being within acceptable limits. The metrics in the Appliance Health category report on these parameters.
This metric indicates how many main unit fans, if any, have failed.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-3 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 5 Minutes |
After Every 288 Samples |
> |
Not Defined |
0 |
1 |
%value% chassis fans failed, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. Additional info - %FansFailedMessage% |
SNMP MIB object: envFailedFanCount (1.3.6.1.4.1.789.1.2.4.2)
This metric is a text message that describes the change in the working status of the main unit backplane fans.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
SNMP MIB object: envFailedFanMessage (1.3.6.1.4.1.789.1.2.4.3)
This metric indicates the current status of the Non-Volatile Random Access Memory (NVRAM) batteries.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-4 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 5 Minutes |
After Every 288 Samples |
> |
1 |
2 |
1 |
Charge in the NVRAM battery is low. Status is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
SNMP MIB object: nvramBatteryStatus (1.3.6.1.4.1.789.1.2.5.1)
This metric indicates the number of failed power supplies and power rails, if any.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-5 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 5 Minutes |
After Every 288 Samples |
> |
Not Defined |
0 |
1 |
%value% power supplies or power rails failed, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. Additional info - %PowerSuppliesFailedMessage% |
SNMP MIB object: envFailedPowerSupplyCount (1.3.6.1.4.1.789.1.2.4.4)
This metric is a text message that describes the change in the working status of the power supply and the power rails.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 5 Minutes |
SNMP MIB object: endFailedPowerSupplyMessage (1.3.6.1.4.1.789.1.2.4.5)
This metric indicates whether the hardware is currently operating above its maximum rated temperature.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-6 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 5 Minutes |
After Every 288 Samples |
> |
Not Defined |
1 |
1 |
System is operating above its maximum rated temperature. |
SNMP MIB object: envOverTemperature (1.3.6.1.4.1.789.1.2.4.1)
Common Internet File System (CIFS) protocol is used by Windows clients to access data on this Network Appliance Filer.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Table 4-7 10 Megabit Network Cards Statistics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
CIFS Bad Calls) |
||
CIFS Bad Calls Rate |
Number of Common Internet File System (CIFS) calls that were rejected |
Rate of cifsBadCalls (1.3.6.1.4.1.789.1.7.3.1.1.3) |
CIFS Calls per Second |
Rate per second of Common Internet File System (CIFS) operations performed by this Network Appliance Filer |
Rate of cifsTotalOps (1.3.6.1.4.1.789.1.7.3.1.1.1) |
CIFS Enabled? |
Indicates whether Common Internet File System (CIFS) protocol is enabled on this Network Appliance Filer. The possible values are True or False |
cifsIsEnabled (1.3.6.1.4.1.789.1.7.1.1) |
This metric represents the percentage of Common Internet File System (CIFS) calls that were rejected.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-8 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every Sample |
> |
5 |
10 |
3 |
CIFS Bad Calls are %value%%%, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
SNMP MIB object: Rate of cifsBadCalls (1.3.6.1.4.1.789.1.7.3.1.1.3)
A cluster consists of a pair of Network Appliance Filers that are connected and configured in a special way to provide fault tolerance.
This information is available only if 'Cluster Configuration Setting' is not equal to 1 (Not Licensed).
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Cluster Interconnect Status |
||
Cluster Partner Status |
||
Partner Name |
Host name of the cluster partner |
cfPartnerName (1.3.6.1.4.1.789.1.2.3.6) |
Partner System ID |
System ID of the cluster partner |
cfPartnerSysid (1.3.6.1.4.1.789.1.2.3.7) |
Reason Can't Takeover |
If the State is equal to 3 (Network Appliance Filer Cannot Takeover), then this metric elaborates about the reason. |
cfCannotTakeoverCause (1.3.6.1.4.1.789.1.2.3.3) |
State |
Network Appliance Filers Cluster state |
cfState (1.3.6.1.4.1.789.1.2.3.2) |
This metric represents the current status of the interconnect hardware.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-10 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
< |
4 |
3 |
1 |
Cluster interconnect hardware with partner %PartnerName% may be down. Status is %value%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
SNMP MIB object: cfInterconnectStatus (1.3.6.1.4.1.789.1.2.3.8)
This metric represents the status of the cluster partner, as returned by the cluster partner.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-11 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
< |
Not Defined |
2 |
1 |
Cluster partner %PartnerName% may be down. |
SNMP MIB object: cfPartnerStatus (1.3.6.1.4.1.789.1.2.3.4)
This metric category defines the metrics for CPU monitoring.
Monitoring how the CPUs are being utilized in the system provides good feedback of the system's health. Keeping certain headroom through at least 10% idle time is a good practice. Therefore it is better to set warnings at around 90% rather than 100%.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics, their descriptions, and data sources.
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
CPU Up Time (Seconds) |
Time (in seconds) that the CPU has been up since the last initialization of the computer system |
cpuUpTime (1.3.6.1.4.1.789.1.2.1.1) Note: This object returns CPU Up Time as hundredths of a second, which is converted into seconds. |
CPU Utilization (%) |
||
No. of CPUs |
Number of CPUs in the Network Appliance Filer |
cpuCount (1.3.6.1.4.1.789.1.2.1.6) |
This metric indicates the percentage of time that the CPU has been working since the last time a client requested the CPU Utilization (%) metric, for example, on the All Metrics page.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-13 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
80 |
95 |
6 |
CPU Utilization is %value%%%, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
SNMP MIB object: cpuBusyTimePerCent (1.3.6.1.4.1.789.1.2.1.3)
This metric category includes the metrics for the failed and spare disks.
This metric represents the message associated with the failed disk.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: diskFailedMessage(1.3.6.1.4.1.789.1.6.4.10)
This metric represents the number of disks that are currently broken.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-14 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
> |
0 |
Not Defined |
3 |
Appliance has at least %value% failed disk(s), crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. Additional info - %DiskFailedMessage% |
SNMP MIB object: diskFailedCount (1.3.6.1.4.1.789.1.6.4.7)
This metric represents the number of available spare disks.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-15 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
< |
2 |
1 |
3 |
Appliance has %value% spare disk(s), crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
SNMP MIB object: diskSpareCount (1.3.6.1.4.1.789.1.6.4.8)
This metric category includes the Filer Capacity metrics for all the volumes.
Note:
For all target versions, the collection frequency for each metric is every hour.The following table lists the metrics, their descriptions, and data sources.
Table 4-16 Filer Capacity Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Aggregate Capacity Allocated (%) |
Percentage of the capacity allocated, for all the aggregates |
Derived using the following:
|
Aggregate Capacity Allocated (GB) |
Capacity allocated, in gigabytes, for all the aggregates |
Derived using the following:
|
Aggregate Capacity Total (GB) |
Total capacity, in gigabytes, for all the aggregates |
Derived using the following
|
Flexible Volumes Capacity Allocated (%) |
Percentage of the capacity used, for all the flexible volumes |
Derived using the following
|
Flexible Volumes Capacity Allocated (GB) |
Allocated capacity, in gigabytes, for all the flexible volumes |
Derived using the following
|
Flexible Volumes Capacity Total (GB) |
Total capacity, in gigabytes, for all the aggregates |
Derived using the following:
|
Qtree Capacity Limit (GB) |
Limit, in gigabytes, for all the Qtrees |
Sum for all Qtrees. Derived using SNMP MIB object qrVKBytesLimit (1.3.6.1.4.1.789.1.4.5.1.5) |
Qtree Capacity Used (%) |
Percentage of capacity used, in gigabytes, for all the Qtrees |
Derived using (qtreecapacityusedgb / qtreecapacitylimitgb) * 100 |
Qtree Capacity Used (GB) |
Capacity used, in gigabytes, for all the Qtrees |
Sum of all Qtrees. Derived using SNMP MIB object qrVKBytesUsed (1.3.6.1.4.1.789.1.4.5.1.4) |
Traditional Volume Capacity Total (GB) |
Total capacity, in gigabytes, for all the volumes |
Sum of volumetotalgb for the volumes |
Traditional Volume Capacity Used (%) |
Percentage of the capacity used, in gigabytes, for all the volumes |
SNMP MIB objects:
|
Traditional Volume Capacity Used (GB) |
Capacity used, in gigabytes, for all the volumes |
Sum of volumeallocgb for the volumes |
Network interface statistics give a good indication of the network level performance and health of the Network Appliance Filer.
Note:
For all target versions, the collection frequency for each metric is every 5 minutes.The following table lists the metrics, their descriptions, and data sources.
Table 4-17 Gigabit NEtwork Cards Statistics Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Network Received Rate (Kilobits/second) |
Rate of data received on the interface, in kilobits/sec |
Rate of ifInOctets (1.3.6.1.2.1.2.2.1.10) Note: This object returns inbound traffic as bytes, rate of which will be computed as kilobits/second. |
Network Sent Rate (Kilobits/second) |
Rate of data transmitted on the interface, in kilobits/sec |
Rate of ifOutOctets (1.3.6.1.2.1.2.2.1.16) Note: This object returns outbound traffic as bytes, rate of which will be computed as kilobits/second. |
Network interface statistics give a good indication of the network level performance and health of this Network Appliance Filer.
Note:
For all target versions, the collection frequency for each metric is every hour.The following table lists the metrics, their descriptions, and data sources.
Table 4-18 Network Interfaces Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Actual Status |
Current state of the interface |
ifOperStatus (1.3.6.1.2.1.2.2.1.8) |
Bandwidth (Mbits/second) |
Estimate of the interface's current bandwidth in megabits/second |
ifSpeed (1.3.6.1.2.1.2.2.1.5) Note: This object returns Bandwidth as bits/second, which will be converted to Mbits/second |
Desired Status |
Desired state of the interface |
ifAdminStatus (1.3.6.1.2.1.2.2.1.7) |
IP Address |
Internet Protocol (IP) address of the interface |
ipAdEntAddr (1.3.6.1.2.1.4.20.1.1) |
MAC Address |
Interface's address at the protocol layer immediately 'below' the network layer in the protocol stack. MAC stands for Media Access Control. |
ifPhyAddress (1.3.6.1.2.1.2.2.1.6) |
Name |
Name of the interface |
ifDescr (1.3.6.1.2.1.2.2.1.2) |
Network Discards (%) |
||
Network Errors (%) |
||
Network Interface (Actual Status-Desired Status) |
See Section 4.10.3, "Network Interface (Actual Status-Desired Status)" |
See Section 4.10.3, "Network Interface (Actual Status-Desired Status)" |
Type |
Type of the interface |
ifType (1.3.6.1.2.1.2.2.1.3) |
Unknown Protocol Packets (%) |
This metric represents the percentage of total packets which were discarded because of the lack of buffer space.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-19 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Hour |
After Every Sample |
> |
15 |
25 |
3 |
Packets discarded at Network Interface %keyValue% are %value%%%, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Network Interface Index" object.
If warning or critical threshold values are currently set for any "Network Interface Index" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Network Interface Index" object, use the Edit Thresholds page.
SNMP MIB objects:
ifInDiscards (1.3.6.1.2.1.2.2.1.13)
ifOutDiscards (1.3.6.1.2.1.2.2.1.19)
This metric represents the percentage of total packets that contained errors and hence, had to be discarded. (There may be a problem with the interface card or cable.)
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-20 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Hour |
After Every Sample |
> |
15 |
25 |
3 |
Errors at Network Interface %keyValue% are %value%%%, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Network Interface Index" object.
If warning or critical threshold values are currently set for any "Network Interface Index" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Network Interface Index" object, use the Edit Thresholds page.
SNMP MIB objects:
ifInErrors (1.3.6.1.2.1.2.2.1.14)
ifOutErrors (1.3.6.1.2.1.2.2.1.20)
This metric represents the difference in the actual status of the interface and the desired state. This metric is equal to zero if both the states are equal, that is, Actual State = Desired State
.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-21 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Hour |
After Every Sample |
> |
Not Defined |
0 |
1 |
Network Interface %Index% failed. |
For this metric you can set different warning and critical threshold values for each "Network Interface Index" object.
If warning or critical threshold values are currently set for any "Network Interface Index" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Network Interface Index" object, use the Edit Thresholds page.
Derived as "ActualStatus-DesiredStatus" or ( ifOperStatus - ifAdminStatus )
SNMP MIB objects:
ifAdminStatus (1.3.6.1.2.1.2.2.1.7)
IfOperStatus (1.3.6.1.2.1.2.2.1.8)
This metric represents the percentage of total packets discarded because of an unknown or unsupported protocol. (Network Appliance Filer may be under a security attack.)
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-22 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every Hour |
After Every Sample |
> |
20 |
30 |
3 |
Unknown or unsupported protocol packets received at Network Interface %keyValue% are %value%%%, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Network Interface Index" object.
If warning or critical threshold values are currently set for any "Network Interface Index" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Network Interface Index" object, use the Edit Thresholds page.
SNMP MIB object: ifInUnknownProtos (1.3.6.1.2.1.2.2.1.15)
Network File System (NFS) protocol is used by UNIX clients to access data on a Network Appliance Filer. Clients send Remote Procedure Calls (RPC) to communicate with the Network Appliance Filer.
This metric represents the rate of total number of received NFS calls (v2 and v3) rejected.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-23 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every Sample |
> |
5 |
10 |
3 |
NFS Bad Calls are %value%%%, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
SNMP MIB object: Rate of nfsServBadCalls (1.3.6.1.4.1.789.1.3.1.2.2)
This metric represents the rate of total number of NFS calls (v2 and v3) received.
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: Rate of nfsCalls (1.3.6.1.4.1.789.1.3.1.2.1)
This metric category defines the metrics for Product Information monitoring. There are no default thresholds for the metrics in this category.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Table 4-24 Product Information Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Firmware Version |
Version string for the Firmware running on this platform |
productFirmwareVersion (1.3.6.1.4.1.789.1.1.6) |
Model |
Model name of this Network Appliance Filer |
productModel (1.3.6.1.4.1.789.1.1.5) |
Product Category |
Type of Network Appliance product. The possible types are: Filer, Clustered Filer, or NetCache |
sysObjectID (1.3.6.1.2.1.1.2) |
Product ID |
System ID (serial number) of the Network Appliance Filer |
productId (1.3.6.1.4.1.789.1.1.3) |
Vendor |
Vendor who supplied this Network Appliance Filer |
productVendor (1.3.6.1.4.1.789.1.1.4) |
Version |
Version of the Network Appliance Filer. The version changes for any patch update or product update to the Network Appliance Filer. |
productVersion (1.3.6.1.4.1.789.1.1.2) |
The metrics in this category are for Qtree monitoring. This information is available only if quotas are turned ON. For our purposes, Quota Type equals qtree.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Name |
Name of the Qtree |
qrVTree (1.3.6.1.4.1.789.1.4.5.1.10) |
Qtree Used (%) |
||
Quota Type |
Identifies the kind of quota for this entry. Quota Type equals three, which indicates Qtree |
qrVType (1.3.6.1.4.1.789.1.4.5.1.2) |
Total GB |
Limit in gigabytes for this Qtree |
qrVKBytesLimit (1.3.6.1.4.1.789.1.4.5.1.5) Note: This object returns Total in kilobytes, which is converted into gigabytes. |
Used GB |
Current number of gigabytes used for this Qtree |
qrVKBytesUsed (1.3.6.1.4.1.789.1.4.5.1.4) Note: This object returns Used in kilobytes, which is converted into gigabytes. |
This metric represents the percentage of space limit used for this Qtree.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-26 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
> |
95 |
98 |
1 |
Qtree %QtreeName% is %value%%% full, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Path Name" object.
If warning or critical threshold values are currently set for any "Path Name" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Path Name" object, use the Edit Thresholds page.
SNMP MIB object: Not Applicable
Redundant Array of Independent Disks (RAID) enables file access even if one disk in a RAID group is damaged. The metrics in this category report on the health of the RAID configuration.
The following table lists the metrics, their descriptions, and data sources.
Table 4-27 RAID Configuration Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Bay |
Number identifying the disk bay within the shelf where the disk is located |
raidVBay (1.3.6.1.4.1.789.1.6.2.1.20 |
Disk Status |
Status of this disk drive |
raidVStatus (1.3.6.1.4.1.789.1.6.2.1.3) |
RAID Group |
Number that identifies the RAID group within the given volume to which this disk belongs. A RAID group consists of a parity disk, up to 28 data disks, and optional spare disks. |
raidVGroup (1.3.6.1.4.1.789.1.6.2.1.13) |
Shelf |
Number identifying the shelf where the disk is located |
raidVShelf (1.3.6.1.4.1.789.1.6.2.1.19) |
Total (GB) |
Total size of this disk, in gigabytes |
raidVTotalMb (1.3.6.1.4.1.789.1.6.2.1.9) Note: This object returns Total in megabytes, which is converted into gigabytes. |
Used (GB) |
Space currently in use, in gigabytes |
raidVUsedMb (1.3.6.1.4.1.789.1.6.2.1.7) Note: This object returns Used in megabytes, which is converted into gigabytes. |
This metric category represents the Internet Control Message Protocol (ICMP) ping response of the Network Appliance Filer.
This metric indicates whether the Network Appliance Filer Host is alive and accessible.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-28 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 2 Minutes |
After Every Sample |
= |
Not Defined |
0 |
1 |
%target% is unreachable over the network or is down.Status is %value%, same as warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
Checks for the TCP ping to the Network Filer Appliance host.
This metric gives the Mean time taken to return a ping.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-29 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 2 Minutes |
After Every Sample |
> |
Not Defined |
Not Defined |
6 |
TCP Ping response is %value% miliseconds, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
The Network Appliance Filer Snapmirror technology provides asynchronous mirroring of data between filer volumes. Data on the source volume is periodically replicated to the target at a user definable time interval, with the range being from one minute to one month.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.This metric represents how far, in minutes, the destination trails behind the source.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-30 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 4 Samples |
> |
Not Defined |
Not Defined |
1 |
SnapMirror Time lag between Source:%SMSource% and Destination:%SMDestination% is %value% minutes, crossed warning (%warning_threshold%) or critical (%critical_threshold%) threshold. |
For this metric you can set different warning and critical threshold values for each unique combination of "Index", "Source", and "Destination" objects.
If warning or critical threshold values are currently set for any unique combination of "Index", "Source", and "Destination" objects, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each unique combination of "Index", "Source", and "Destination" objects, use the Edit Thresholds page.
Derived using SNMP MIB object snapmirrorLag (1.3.6.1.4.1.789.1.9.20.1.6)
The snapmirrorLag object gives the lag in 'hundredths of a second'. Smtimelag (in minutes) is derived using ( (snapmirrorLag / 100.0) / 60.0 )
This metric represents the current state of the snapmirror. The possible values are:
uninitialized
snapmirrored
broken-off
quiesced
source
unknown
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: 1.3.6.1.4.1.789.1.9.20.1.5
This metric represents the current transfer status of the snapmirror. The possible values are:
idle
transferring
pending
aborting
migrating
quiescing
resyncing
waiting
The following table shows how often the metric's value is collected.
Target Version | Collection Frequency |
---|---|
All Versions | Every 15 Minutes |
SNMP MIB object: snapmirrorStatus (1.3.6.1.4.1.789.1.9.20.1.4)
Network Appliance Filer SnapMirror software delivers the disaster recovery and data distribution solution by replicating data at high speeds over a Local Area Network (LAN) or a Wide Area Network (WAN).
SnapMirror software provides the highest possible data availability and fastest recovery for mission-critical applications. SnapMirror technology mirrors data to one or more network filers. It continually updates the mirrored data to keep it current and available for disaster recovery, offloading tape backup, read-only data distribution, testing on non production filers, online data migration, and more.
The metrics in this category report on the SnapMirror read and write rates.
Note:
For all target versions, the collection frequency for each metric is every 6 hours.The following table lists the metrics, their descriptions, and data sources.
Table 4-31 SnapMirror Load Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
SnapMirror Read Rate (Kbytes/second) |
Number of kilobytes per second read by SnapMirror. This metric is reset on reboot. |
snapmirrorReadBytes (1.3.6.1.4.1.789.1.9.11) Computed by calculating the difference over a collection interval. |
SnapMirror Write Rate (Kbytes/second) |
Number of kilobytes per second written by SnapMirror. This metric is reset on reboot. |
snapmirrorWrittenBytes (1.3.6.1.4.1.789.1.9.10) |
A snapshot is a point-in-time, read-only image of the entire file system. The metrics in the Snapshots category report on the snapshot metrics.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Reserve Available (GB) |
Space available (in gigabytes) |
dfKBytesAvail (1.3.6.1.4.1.789.1.5.4.1.5) Note: This object returns Available in kilobytes, which is converted into gigabytes. |
Reserve Total (GB) |
Total allocated capacity, in gigabytes, for this snapshot |
dfKBytesTotal (1.3.6.1.4.1.789.1.5.4.1.3) Note: This object returns Total in kilobytes, which is converted into gigabytes. |
Reserve Used (GB) |
Space (in gigabytes) in use |
dfKBytesUsed (1.3.6.1.4.1.789.1.5.4.1.4) Note: This object returns Used in kilobytes, which is converted into gigabytes. |
Snapshot Reserve Used (%) |
||
Volume Type |
Type of container (traditionalVolume, flexibleVolume, or an aggregate) |
SNMP MIB object: 1.3.6.1.4.1.789.1.5.4.1.23 (dfType) Derived as:
|
This metric represents the percentage of space used.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-33 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
> |
95 |
Not Defined |
1 |
Snapshot %keyValue% is %value%%% full, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Volume" object.
If warning or critical threshold values are currently set for any "Volume" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Volume" object, use the Edit Thresholds page.
SNMP MIB object: dfPerCentKBytesCapacity (1.3.6.1.4.1.789.1.5.4.1.6)
This metric category represents the statistics related to the spare disks in a RAID (Redundant Array of Independent Disks) group. A RAID group consists of a parity disk, up to 28 data disks, and optional spare disks.
A spare disk in an auxiliary disk used to replace other disks should they become corrupted or full. When a disk in a RAID group fails, a spare disk automatically replaces it. Spare disks are all the disks in the systems that have not been assigned to a volume.
The following table lists the metrics, their descriptions, and data sources.
Table 4-34 Spare Disks Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Disk Name |
Name of this spare disk drive |
spareDiskName (1.3.6.1.4.1.789.1.6.3.1.2) |
Spare Bay |
Number identifying the disk bay within the shelf where the disk is located |
spareBay (1.3.6.1.4.1.789.1.6.3.1.13) |
Spare Shelf |
Number identifying the shelf where the disk is located |
spareShelf (1.3.6.1.4.1.789.1.6.3.1.12 |
Spare Status |
Status of this spare drive. Examples of spare status are: spare, adding spare, bypassed, and unknown. |
spareStatus (1.3.6.1.4.1.789.1.6.3.1.3) |
Total (GB) |
Total size of this spare disk, in gigabytes |
spareTotalMb (1.3.6.1.4.1.789.1.6.3.1.7) Note: This object returns Total in megabytes, which is converted into gigabytes. |
This metric category includes the metrics that indicate the network traffic and the I/O activities of the Network Appliance Filer.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Table 4-35 System Load Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Cache Age (Minutes |
Age, in minutes, of the oldest read-only blocks in the buffer cache. This indicates how fast read operations are cycling through system memory. When the Network Appliance Filer is reading very large files (larger than the machine's memory size), buffer cache age will be very low |
miscCacheAge (1.3.6.1.4.1.789.1.2.2.23) |
Total Disk I/O Rate (KBytes/second) |
Total (read and write) bytes, to and from the disk, in Kilobytes per second |
miscHighDiskReadBytes (1.3.6.1.4.1.789.1.2.2.15) miscLowDiskReadBytes (1.3.6.1.4.1.789.1.2.2.16) miscHighDiskWriteBytes (1.3.6.1.4.1.789.1.2.2.17) miscLowDiskWriteBytes (1.3.6.1.4.1.789.1.2.2.18) |
Total Disk Read Rate (KBytes/second) |
Rate of bytes read from disk since the last boot |
miscHighDiskReadBytes (1.3.6.1.4.1.789.1.2.2.15) miscLowDiskReadBytes (1.3.6.1.4.1.789.1.2.2.16) |
Total Disk Written Rate (KBytes/second) |
Rate of bytes (Kilobytes/s) written to disk since the last reboot |
miscHighDiskWriteBytes (1.3.6.1.4.1.789.1.2.2.17) miscLowDiskWriteBytes (1.3.6.1.4.1.789.1.2.2.18) |
Total Http Operations Received Rate (Ops/second) |
Rate of HTTP operations received since the last reboot |
miscHighHttpOps (1.3.6.1.4.1.789.1.2.2.9) miscLowHttpOps (1.3.6.1.4.1.789.1.2.2.10) |
Total Network I/O Rate (KBytes/second) |
Rate of bytes received and transmitted on all the network interfaces, since the last boot |
miscHighNetRcvdBytes (1.3.6.1.4.1.789.1.2.2.11) miscLowNetRcvdBytes (1.3.6.1.4.1.789.1.2.2.12) miscHighNetSentBytes (1.3.6.1.4.1.789.1.2.2.13) miscLowNetSentBytes (1.3.6.1.4.1.789.1.2.2.14) |
Total Network Received Rate (KBytes/second) |
Rate of bytes received on all the network interfaces, since the last boot |
miscHighNetRcvdBytes (1.3.6.1.4.1.789.1.2.2.11) miscLowNetRcvdBytes (1.3.6.1.4.1.789.1.2.2.12) |
Total Network Sent Rate (KBytes/second) |
Rate of bytes transmitted on all the network interfaces, since the last boot |
miscHighNetSentBytes (1.3.6.1.4.1.789.1.2.2.13) miscLowNetSentBytes (1.3.6.1.4.1.789.1.2.2.14) |
This metric category includes the metrics representing the allocated space for each volume.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following table lists the metrics, their descriptions, and data sources.
Table 4-36 Volume Allocation Metrics
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Allocated (GB) |
Allocated space, in gigabytes, for each volume |
dfKBytesUsed (1.3.6.1.4.1.789.1.5.4.1.4) Derived as ( dfKBytesUsedl / (1024.0 * 1024.0) ) |
Total (GB) |
Total capacity, in gigabytes, for each volume |
dfKBytesTotal (1.3.6.1.4.1.789.1.5.4.1.3) Derived as ( dfKBytesTotal / (1024.0 * 1024.0) ) |
Unallocated (GB) |
Unallocated space, in gigabytes, for each volume |
dfKBytesAvail (1.3.6.1.4.1.789.1.5.4.1.5) Derived as ( dfKBytesAvail / (1024.0 * 1024.0) ) |
Volume Allocated (%) |
||
Volume Type |
Type of container (traditionalVolume, flexibleVolume, or an aggregate) |
1.3.6.1.4.1.789.1.5.4.1.23 (dfType) Derived as:
|
This metric represents the percentage of allocated space for each volume.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-37 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
> |
100 |
Not Defined |
3 |
%VolumeTypeString% %keyValue% has been over allocated by %value%%%, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Volume" object.
If warning or critical threshold values are currently set for any "Volume" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Volume" object, use the Edit Thresholds page.
Derived as ( volumeallocgb / volumetotalgb) * 100
A volume is a physical file system on a Network Appliance Filer comprising multiple disks that store client data. A Network Appliance Filer can have from one to 23 volumes. This metric category defines the metrics for Volume Monitoring.
Note:
For all target versions, the collection frequency for each metric is every 15 minutes.The following lists the metrics, their descriptions, and data sources.
Metric | Description | Data Source (SNMP MIB Object) |
---|---|---|
Available (GB) |
Space available, in gigabytes, on this volume |
dfKBytesAvail (1.3.6.1.4.1.789.1.5.4.1.5) Note: This object returns the value in kilobytes, which is converted into gigabytes. |
Files Available |
Number of files (inodes) available for use |
dfInodesFree (1.3.6.1.4.1.789.1.5.4.1.8) |
Files Used |
Number of files currently in use |
dfMaxFilesUsed (1.3.6.1.4.1.789.1.5.4.1.12 |
Files Used (%) |
||
Max Files |
Maximum number of files allowed on this volume |
dfMaxFilesAvail (1.3.6.1.4.1.789.1.5.4.1.11) |
Total (GB) |
Total capacity, in gigabytes, of this volume |
dfKBytesTotal (1.3.6.1.4.1.789.1.5.4.1.3) Note: This object returns the Total in kilobytes, which is converted into gigabytes. |
Used (GB) |
Space, in gigabytes, in use by this volume |
dfKBytesUsed (1.3.6.1.4.1.789.1.5.4.1.4) Note: This object returns the Used metric in kilobytes, which is converted into gigabytes. |
Volume Type |
Type of container (traditionalVolume, flexibleVolume, or an aggregate) |
1.3.6.1.4.1.789.1.5.4.1.23 (dfType) Derived as:
|
Volume Used (%) |
This metric represents the percentage of maximum inodes in use on this volume.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-39 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
> |
95 |
98 |
1 |
%VolumeTypeString% %keyValue% has used %value%%% files of its limit, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Volume" object.
If warning or critical threshold values are currently set for any "Volume" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Volume" object, use the Edit Thresholds page.
SNMP MIB object: dfPerCentInodeCapacity (1.3.6.1.4.1.789.1.5.4.1.9)
This metric represents the percentage of space used on this Network Appliance Filer.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-40 Metric Summary Table
Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
---|---|---|---|---|---|---|---|
All Versions |
Every 15 Minutes |
After Every 96 Samples |
> |
95 |
98 |
1 |
%VolumeTypeString% %keyValue% is %value%%% full, crossed warning (%warning_threshold%%%) or critical (%critical_threshold%%%) threshold. |
For this metric you can set different warning and critical threshold values for each "Volume" object.
If warning or critical threshold values are currently set for any "Volume" object, those thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Volume" object, use the Edit Thresholds page.
SNMP MIB object: dfPerCentKBytesCapacity (1.3.6.1.4.1.789.1.5.4.1.6)