![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Technical Instruction Sure Solution 1003966.1 : Sun Storage Common Array Manager (CAM): How to Collect Performance Data for Sun Storage Arrays
PreviouslyPublishedAs 205545 In this Document
Applies to:Sun Storage 6780 Array - Version All Versions and laterSun Storage 2530 Array - Version Not Applicable and later Sun Storage 6580 Array - Version All Versions and later Sun Storage 2530-M2 Array - Version Not Applicable and later Sun Storage 6140 Array - Version All Versions and later All Platforms GoalThis document reviews the procedures for collecting performance statistics from arrays that can be managed using Sun Storage Common Array Manager (CAM). It is intended to provide an overview of the statistics collected. SolutionConfiguring Performance CollectionUsing the Browser User Interface (BUI)After starting CAM and selecting the array, performance settings may be found in the Administration tab -> Performance Monitoring. You can enable or disable monitoring as well as define two (or 3) tunables.
Set for 1, 5, or 15 minutes. At this interval, the array will be contacted for new array data for all fields, and the management software will be updated with the new statistics. Calculations for statistics will be made over this interval.
Set for 1 hour, 2 hours, 4 hours, 1 day, or forever. This setting dictates how long the Peak data will be listed in the output collected. This only affects the collection of peak data until collection is turned off.
Clicking the Set Baseline button sets the baseline time to the current array system time, and the counters will display based on the values at that time. Using the sscs CLIsscs location:
Solaris: /opt/SUNWstkcam/bin/ Linux: /opt/sun/cam/bin/ Windows: C:\Program Files\Sun\Common Array Manager\bin
Syntax:
sscs modify -a array --status on|off --poll 1|5|15 --retention forever|1HR|2R|4HR|1DAY performance Example: # sscs modify -a array --status on --poll 1 --retention 1HR
# sscs list -a array -T performance
Array: array State: On Polling Interval: 1 minute Data Retention Period: 1 hour
Syntax:
# sscs modify -a array --status on|off --poll 1|5|15 --retention forever|1HR|2R|4HR|1DAY --baseline true|false iperformance Example: # sscs modify -a array --status on --poll 5 --retention forever --baseline true iperformance
# sscs list -a array -T performance
Array: s2510-a State: On Polling Interval: 5 minutes Data Retention Period: Forever ARRAY NAME: s2510-a ====================== BASELINE STATISTICS ====================== Controller B Baseline Time: January 18, 2013 1:39:15 PM EST < . . . . >
Collecting & Viewing StatisticsCollecting array statistics using the BUI
Collecting array statistics using sscs# sscs list -a array --type array_stats performance
|
Statistic | Definition |
TOT IOPS | Total IO's Per Second over the polling interval |
Average IOPS | The average number of inputs and outputs per second over the retention period |
READ % | Percent of Total IOPS that were reads over the polling interval |
WRITE% | Percent of Total IOPS that were writes over the polling interval |
TOT DATA | Total Amount of Data transferred in KB over the polling interval |
READ | Total amount of KB read during polling period |
AVG R SIZE | Average Read Size in KB during polling period |
READS/s | Number of Reads per second during polling period |
PEAK R/s | The highest number of Reads per Second during the retention period |
WRITTEN | Total amount of KB written during the polling period |
AVG W SIZE | Average Write size in KB during polling period |
WRITES/s | Number of Writes per second during polling period |
PEAK W/s | The highest number of Writes per Second during the retention period |
CACHE% | The percentage of total I/Os that are processed with data from the cache rather than requiring a read from drive |
The following table describes the fields on the iSCSI Ethernet-MAC Performance Statistics page.
Field | Indicates |
Controller A boot time | Date and time when Controller A was last booted |
Controller B boot time | Date and time when Controller B was last booted |
MAC Transmit Statistics | |
Port | The iSCSI port used to transmit and receive data |
F | Frame Count |
B | Byte Count |
MF | Multicast frame count |
BF | Broadcast frame count |
PF | Pause frame count |
CF | Control frame count |
FDF | Frame Deferral Count |
FED | Frame excess deferral count |
FLC | Frame late collisions count |
FA | Frame abort count |
FSC | Frame single collision count |
FMC | Frame multiple collision count |
FC | Frame collisions count |
FDR | Frame Dropped Count |
JF | Jumbo Frame count |
MAC Receive Statistics | |
Port | iSCSI port used to transmit and receive data |
F | Frame Count |
B | Byte Count |
MF | Multicast Frame Count |
BF | Broadcast Frame Count |
PF | Pause Frame Count |
CF | Control Frame Count |
FLE | Frame Length error count |
FDR | Frame Dropped count |
FCRCE | Frame CRC error count |
FEE | Frame Encoding Error count |
LFE | Large frame error count |
SFE | Small frame error count |
J | Jabber count |
UCC | Unknown control frame count |
CSE | Carrier Sense error count |
Do you still have questions? You can use My Oracle Support Communities. Communities put you in touch with industry professionals like yourself. They are monitored by Oracle support engineers, so you can expect reliable and correct answers. Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.
This solution has no attachment
![]() | ![]() | ![]() | ![]() |
Copyright © 2018 Oracle, Inc. All rights reserved.
Feedback |
|||
![]() |