...
...
borderColor | #248D85 |
---|
bgColor | white |
---|
titleColor | white |
---|
borderWidth | 3 |
---|
titleBGColor | #248D85 |
---|
borderStyle | solid |
---|
title | Create Storage System Users |
---|
To establish an access point for BVQ, it's necessary to create user accounts on the respective systems you wish to monitor.
For instance, if you have three NetApp clusters, you'll need to create a user account on each cluster.
This procedure is applicable to all systems you aim to connect to BVQ.
After creating a specific new user on a system, proceed to set up a BVQ Scanner on your BVQ Server using that user account.
The BVQ Scanner will then establish a connection to the system to collect the requisite data.
Panel |
---|
borderColor | #248D85 |
---|
titleColor | white |
---|
borderWidth | 3 |
---|
titleBGColor | #248D85 |
---|
borderStyle | solid |
---|
title | IBM SVC preparation |
---|
|
System preparation stepsCreate a BVQ user on the SVC systemFor |
the communication of the BVQ SVC Scanner with the SVC CLI a user account on each SVC is mandatory, which should be at least member of the group 'Monitor'. Panel |
---|
|
borderColor | #248D85 |
---|
borderWidth | 3 |
---|
borderStyle | solid |
---|
|
Create a BVQ user on the system
Expand |
---|
|
With SVC CLI:
Code Block |
---|
theme | Midnight |
---|
title | SVC CLI |
---|
|
svctask mkuser -name bvq -usergrp Monitor -password P@ssw0rd |
For code level lower than 8.4 use:
Code Block |
---|
theme | Midnight |
---|
title | SVC CLI |
---|
|
svctask mkuser -name bvq -usergrp Administrator -password P@ssw0rd |
Panel |
---|
borderColor | #248D85 |
---|
borderWidth | 3 |
---|
borderStyle | solid |
---|
|
communication between a SVC system and BVQ, a user account with at least user group 'Monitor' is required on each SVC system. svctask mkuser -name bvq -usergrp Monitor -password <my_secure_password>
|
Please check if an NTP server |
Check NTP, time and time zone |
Expand |
---|
|
Check if an NTP server is configured: |
we strongly recommend to use an NTP server to synchronize the time of all systems (SVC Nodes, Windows): Code Block |
---|
theme | Midnight |
---|
title | SVC CLI |
---|
|
svcinfo lssystem | grep it is mandatory to use NTP to synchronize the time of all systems (SVC Systems and BVQ Server): svcinfo lssystem | grep 'ntp_IP_address'
Set your NTP Server: Synchronize your SVC cluster with a specific NTP server: |
Code Block |
---|
theme | Midnight |
titleSVC CLI | Server>
Adjust SVC cluster time zone: Set the time zone of your SVC cluster with: |
codetheme | Midnight |
---|
title | SVC CLI |
---|
|
360
Show SVC clock settings: Check the current time setting on your SVC: |
Code Block |
---|
theme | Midnight |
---|
title | SVC CLI Panel |
---|
borderColor | #248D85 |
---|
borderWidth | 3 |
---|
borderStyle | solid Expand |
---|
title | expand...The SVC performance statistics are generated |
regularly regularly (in intervals) by the SVC and picked up by the BVQ SVC Scanner. BVQ supports all intervals possible in the SVC (1min to 60min). We recommend to set the time interval to 1 minute. Check statistics status and frequency: Use this command to see if and how often your system collects statistics: |
Code Block |
---|
theme | Midnight |
---|
title | SVC CLI ^(statistics_status|statistics_frequency)$
|
Set Enable statistics collection: Activate collection of system statistics:
Code Block |
---|
theme | Midnight |
---|
title | SVC CLI |
---|
|
statistics_status on |
Change statistics collection frequency: Define how |
frequently the collects : Code Block |
---|
theme | Midnight |
---|
title | SVC CLI |
---|
|
statistics_frequency 1 |
Start statistics collection: Begin collecting system statistics at your defined frequency:
Code Block |
---|
theme | Midnight |
---|
title | SVC CLI |
---|
|
svctask startstats -interval 1 |
Clear I/O statistics dumps: Clean old I/O statistics data from all nodes in the SVC with this command:
Code Block |
---|
theme | Midnight |
---|
title | SVC CLI |
---|
|
svcinfo lsnode -nohdr | while read id rest ; do svctask cleardumps -prefix /dumps/iostats $id ; done |
Anchor |
---|
netapp | netapp | Panel |
---|
borderColor | #248D85 |
---|
bgColor | whiteare collected: startstats -interval <interval_in_minutes>
|
Panel |
---|
borderColor | #C2502E |
---|
titleColor | white |
---|
borderWidth | 3 |
---|
titleBGColor | #C2502E |
---|
borderStyle | solid |
---|
title | Dell EMC Unity preparation |
---|
|
A user is required for the operation of the BVQ Scanner with at least Operator role permissions. Please create this user on your Unity system prior to configuring the the BVQ Scanner. Image Added |
Panel |
---|
borderColor | #2929A9 |
---|
titleColor | white |
---|
borderWidth | 3 |
---|
titleBGColor |
---|
| #248D85#2929A9 | borderStyle | solid |
---|
title | Netapp preparation |
---|
|
A user is required for the operation of the BVQ Scanner, which should at least have readonly Role with at least 'read-only' role permissions on the ONTAP Cluster is required to operate the BVQ Scanner. Please create this user before the configuration of prior to configuring the BVQ Scanner. We recommend using the name : bvq Code Block |
---|
|
theme | Midnight |
---|
title | Ontap CLI |
---|
|
sec login create 'bvq' for this user.
sec login create -user-or-group-name
bvq
-application
http
-authentication-method
password
-role
readonly
sec login create readonly
BVQ Version < 2024.H2.1 or ONTAP version < 9.11
sec login create -user-or-group-name
bvq
-application
ontapi
-authentication-method
password
-role
readonly
Anchor |
---|
unity | unity |
...
yellow | borderWidth | 3 |
---|
titleBGColor |
---|
|
...
yellow | borderStyle | solid |
---|
title |
---|
|
...
A user is required for the operation of the BVQ Scanner, who should at least have Operator Role permissions.
Please create this user at your Unity System before the configuration of the BVQ Scanner. We recommend to name the user: bvq
Image Removed
Gather information for BVQ Scanner configuration
BVQ scanners need the following information to be configured for each Dell EMC Unity System:
...
|
Configure a user with minimum role "read_only" and API token on each array. |