HP 3PAR StoreServ 7400 4-node HP 3PAR Management Console 4.3.1 User's - Page 423
Maximum Transmission Unit. Maximum Transmission Unit. The greatest amount of data or packet
View all HP 3PAR StoreServ 7400 4-node manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 423 highlights
iSCSI adaptor iSCSI name iSNS LD template Logical Unit Number LUN Magazine availability matched-set VLUN template Maximum Transmission Unit mirror mirror depth mirroring MTU No One Host policy No Stale Snapshot no stale snapshots One Host policy original parent base volume parent volume parity parity set parity set position physical copy physical copy, promoting physical parent Port availability An iSCSI PCI host bus adapter (HBA) located in a controller node. The iSCSI adapter connects a controller node to a host. A value used to identify iSCSI channel devices on an arbitrated loop. Internet Storage Name Service. Protocol that allows automated discovery, management, and configuration of iSCSI. Logical disk template. The template contains a set of logical disk parameters that can be applied again and again to create logical disks or volumes with the same characteristics using the HP 3PAR Management Console. See LUN. Stands for Logical Unit Number. A number used to access a virtual volume that has been assigned to a particular host on a particular port. See also export, VLUN, and VLUN template. Creates a virtual volume that can tolerate a drive magazine failure because its RAID sets use chunklets from different drive magazines. A rule that allows a particular host connected to a particular port to see a virtual volume as a specified LUN. See also VLUN template. See MTU. One member of a group of mirrored chunklets, which is also known as a RAID 1 set. See set size. A data redundancy technique used by some RAID levels and in particular RAID 1 to provide data protection on a storage array. Maximum Transmission Unit. Maximum Transmission Unit. The greatest amount of data or "packet" size that can be transferred at one time over a particular network connection without overburdening the connection. Use when exporting a VV to multiple hosts for use by a cluster-aware application, or if using port presents VLUNs. System can halt writing data to the base volume so as to prevent loss of sync between the base volume and its snapshots. Virtual copy policy that prevents changes being written to a base volume when it does not have enough snapshot data or administration space to prevent virtual copies from becoming invalid, or stale, as a result. See also stale snapshots, virtual copy policy. Constrains the export of a volume to one host or one host cluster (when cluster names may be used as a host name.) This protects the volume from accidental export to multiple hosts which could lead to data corruption if both hosts are writing to the volume. The original base volume from which a series of virtual and/or physical copies has been created. Any volume can be the parent from which one or more virtual copies is created, but for each set of related copies there is only one original parent base volume. A virtual volume from which a virtual or physical copy is made. See also original parent base volume. A data redundancy technique used by some RAID levels and in particular RAID 5 to provide data protection on a storage array. See RAID 5 set. The group of chunklets that occupy the same position within a RAID 5 logical disk parity set. A physical copy is a snapshot that duplicates all the data from one base volume to another base volume (the destination volume) for use, should the original become unavailable. Promoting a virtual copy copies the changes from a virtual copy back onto the base volume. The source volume for a physical copy. Creates a virtual volume that can tolerate two port failures because its RAID sets use chunklets from devices on different cage loops. 423