FCP for the IBM eServer zSeries systems: Access to distributed storage

Adlung, I.; Banzhaf, G.; Eckert, W. J.; Kuch, G.; Mueller, Silvia Melitta; Raisch, C.

doi:10.1147/rd.464.0487

Cited by 8 publications

(7 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Overview of T10 data integrity field The FCP channel [6,7] on zEnterprise supports end-to-end data protection, as defined by recent enhancements to the SCSI standard for direct-access block devices, in particular disks, i.e., defined in the International Committee for Information Technology Standards (INCITS) documents [8,9]. This standard introduces an 8-byte data integrity field (DIF) that is appended to each data block, thus increasing the typical 512-byte SCSI block size to 520 bytes.…”

Section: Fcp End-to-end Data Protectionmentioning

confidence: 99%

IBM zEnterprise storage I/O advancements

Amann

Banzhaf

Bender³

et al. 2012

IBM J. Res. & Dev.

Self Cite

View full text Add to dashboard Cite

Section: Fcp End-to-end Data Protectionmentioning

confidence: 99%

IBM zEnterprise storage I/O advancements

Amann

Banzhaf

Bender³

et al. 2012

IBM J. Res. & Dev.

Self Cite

View full text Add to dashboard Cite

“…Users are connected to the server via a LAN using Ethernet hubs, routers, and switches. The server is then connected to a pool of storage devices, using interconnecting "fabric" [Adlung, 2002, Heath and Yakutis, 2000, Vacca, 2002. The term 'fabric' implies a network of switches.…”

Section: Typical San Configurationmentioning

confidence: 99%

“…When bandwidth is critical, and file system functionality is not [Gibson and van Meter, 2000], SAN is a more appropriate solution. SAN is a web of different storage devices sharing a dedicated, high-speed network that, as was shown in Figure 1, is connected to users and servers on a LAN [Adlung, 2002, Brinkmann et al, 2000, Heath and Yakutis, 2000, Thompson et. al., 2003].…”

Section: Clientmentioning

confidence: 99%

Storage Area Networks

Mehta

Ives

2004

CAIS

View full text Add to dashboard Cite

This paper is a tutorial on Storage Area Networks (SANs). On the face of it storage network technology might appear to be just another incremental improvement relative to current technology; i.e., faster and cheaper but otherwise nothing new. On the other hand, as with technologies such as the World Wide Web and XML, SAN can also be viewed as an exciting new window into the future applications of technology. The World Wide Web provided a global, if relatively disorganized, file structure that almost immediately transcended organization and national boundaries. XML provides a still finer level of multi-organization data structure, this time at the level of the logical data element. Storage Network technologies provide an even finer level of resolution for global storage; providing powerful tools for organizing vast repositories of data and information within a building, organization, within municipalities, across distributed organizations, and throughout the world. This paper compares SAN technology with previous storage management solutions with particular attention to promised benefits of scalability, interoperability, and high-speed LAN-free backups. The paper provides an overview of what SANs are, why invest in them, and how SANs can be managed. The paper also discusses a primary management concern, the interoperability of vendor-specific SAN solutions. Bluefin, a storage management interface and interoperability solution is also explained. The paper concludes with discussion of SAN-related trends and implications for practice and research.

show abstract

“…For SCSI IPL, the load address specifies a two-byte device number associated with the FCP channel to be used to access the FC fabric in which the IPL device resides. This device number, defined in association with the channel in the IOCDS, is not associated with a real I/O device, but rather with a pair of queues in the channel for exchanging commands and responses between the program (the machine loader in this case) and the channel [3].…”

Section: Input Parametersmentioning

confidence: 99%

“…IPL from these devices is called CCW IPL. Recently, a zSeries version of the Linux** OS and a Fibre Channel protocol (FCP) channel were introduced, enabling zSeries use of Small Computer System Interface (SCSI) FCP devices [3]. We refer to these as SCSI devices.…”

Section: Introductionmentioning

confidence: 99%

SCSI initial program loading for zSeries

Banzhaf

Brice²,

Frazier³

et al. 2004

IBM J. Res. & Dev.

Self Cite

View full text Add to dashboard Cite

This paper describes a new kind of initial program loading (IPL) for IBM zSeries ᭨ servers. The new IPL protocol expands the set of input/output devices that can be used during IPL to include Small Computer System Interface (SCSI) Fibre Channel protocol (FCP) disk devices (SCSI disks). We begin by describing several new challenges resulting from the use of SCSI disks during IPL, followed by a brief overview of new concepts we have applied to the IPL process to overcome these challenges. We continue with a step-by-step description of the processes executed during SCSI IPL, the tools used, the disk format, the parameters required, and related topics. Since SCSI IPL is supported for virtual machines instantiated by the z/VM ᭨ operating system, some unique features of this capability are described. Finally, we describe a variation of SCSI IPL that enables the contents of memory to be dumped onto a SCSI disk.

show abstract

FCP for the IBM eServer zSeries systems: Access to distributed storage

Cited by 8 publications

References 3 publications

IBM zEnterprise storage I/O advancements

IBM zEnterprise storage I/O advancements

Storage Area Networks

SCSI initial program loading for zSeries

Contact Info

Product

Resources

About