HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 16

SNMPv3 user accounts have these options: • User Name. • Password. • SNMP User Type. Either: User Access, which allows the user to view the SNMP MIB; or Trap Target, which allows the user to receive SNMP trap notifications. Trap Target uses the IP address set with the Trap Host Address option. • Authentication Type. Either: MD5 authentication; SHA (Secure Hash Algorithm) authentication; or no authentication. Authentication uses the password set with the Password option. • Privacy Type. Either: DES (Data Encryption Standard) encryption; AES (Advanced Encryption Standard) encryption; or no encryption. Encryption uses the password set with the Privacy Password option. • Privacy Password. The encryption password. • Trap Host Address. The IP address of the host system that will receive SNMP traps. Table 2 Settings for default users Name Password Roles Type Interfaces Base Prec. Units Temp. enabled Auto Sign Out Locale monitor !monitor Monitor Standard WBI, CLI 10 1 manage !manage Monitor, Manage WBI, CLI, FTP, SMI-S ftp !ftp Monitor, FTP Manage Auto Celsius 30 English min. NOTE: To secure the storage system, set a new password for each default user. Related topics • "Configuring user accounts" (page 43) About vdisks A vdisk is a virtual disk that is composed of one or more disks, and has the combined capacity of those disks. The number of disks that a vdisk can contain is determined by its RAID level. All disks in a vdisk must be the same type (enterprise SAS or midline SAS). A maximum of 64 vdisks per system can exist. A vdisk can contain different models of disks, and disks with different capacities. If you mix disks with different capacities, the smallest disk determines the logical capacity of all other disks in the vdisk, regardless of RAID level. For example, the capacity of a vdisk composed of one 500-GB disk and one 750-GB disk is equivalent to a vdisk composed of two 500-GB disks. To maximize capacity, use disks of similar size. For greatest reliability, use disks of the same size and rotational speed. Each disk has metadata that identifies whether the disk is a member of a vdisk, and identifies other members of that vdisk. This enables disks to be moved to different slots in a system; an entire vdisk to be moved to a different system; and a vdisk to be quarantined if disks are detected missing. In a single-controller system, all vdisks are owned by that controller. In a dual-controller system, when a vdisk is created the system automatically assigns the owner to balance the number of vdisks each controller owns; or, you can select the owner. Typically it does not matter which controller owns a vdisk. In a dual-controller system, when a controller fails, the partner controller assumes temporary ownership of the failed controller's vdisks and resources. If a fault-tolerant cabling configuration is used to connect the controllers to drive enclosures and hosts, both controllers' LUNs are accessible through the partner. 16 Getting started