[ Pobierz całość w formacie PDF ]
focused on infrastructure-based problems and provides reduced
deployment risks through phased SAN deployment. This helps keep
investments limited to solutions and creates investment bases for
the future. Initial investments will improve the ROI when other sce-
nario investments are reduced.
You should have the following detailed results from an interview
process that define what the SAN needs to accomplish for you:
% Technical requirements document?
% Operating system to be installed?
% Patch or service pack level?
% Whether fabric HBA/controller drivers are available, and if so,
are they well tested?
% How many HBAs will it have?
% If there is more than one HBA, what software will be used to
provide failover or performance enhancements of multiple
paths?
% Private loop, public loop, or fabric connection?
% Applications that will run host databases, e-mail, data
replication, or file sharing?
% Storage requirements?
% Will storage requirements change over time?
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)
Copyright 2004 The McGraw-Hill Companies. All rights reserved.
Any use is subject to the Terms of Use as given at the website.
Configuring SANs: Dos and Don ts
Configuring SANs: Dos and Don'ts
51
% Physical dimensions? How heavy will it be?
% Does it require a rack mount? A rack kit? A shelf set?
% Management console? If so, what type is it?
% Traditional keyboard/video/mouse (KVM) combo?
% Serial connection, such as a TTY?
% Do interfaces exist? Do they need to be purchased?
% Make, model, and version information?
% How many Ethernet interfaces?
% What temperature range for operation?
% Telephone line requirements?
% Node location?
% Timeline for implementation?
% Required purchases?
% SAN design?
Answers to these questions will be used throughout the life of your
SAN. The timeline will be the framework of activities for the SAN
life cycle. These documents will be used in approval processes during
implementation and maintenance phases as SAN deliverables. If
major changes to your SAN environment are necessary, your SAN
life cycle will be repeated, and another set of documentation will
need to be produced.
Interoperability Issues
Currently, interoperability is limited. Equipment from different
manufacturers often will not work in an interoperative fashion
despite common software and hardware interfaces. Third-party test-
ing has become necessary to ensure interoperability. The Fibre
Channel market is widely accepted as the most innovative SAN
development solution at this time. Integrated software companies
play a major role in the development of SANs. System managers and
administrators need to recognize that this is a fact.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)
Copyright 2004 The McGraw-Hill Companies. All rights reserved.
Any use is subject to the Terms of Use as given at the website.
Configuring SANs: Dos and Don ts
Chapter 4
52
E-commerce is often associated with UNIX and Windows NT sys-
tems. What is overlooked is the fact that mainframes are integral to
the e-commerce supply chain. Telephone companies, shipping com-
panies, credit card companies, and banks all manage multiple main-
frames supporting e-commerce. Mainframes are involved in online
transactions before the customer clicks on a buy icon and until the
product arrives on the customer s doorstep. If data is to be synony-
mous with business, then interconnecting open-system data storage
with mainframe data storage is a primary role in the new economy.
Interconnecting open-system and mainframe storage is not easy.
Data structures, protocols, and architectures vary. Both environ-
ments are double-edged swords in relation to interoperability. Their
strengths are often their weaknesses in the SAN environment. The
nature of an open system is that it is open. The premise of the open-
system environment is that multiple vendors can build compatible
products to interoperate with one another and allow customers to
use common sets of applications and devices. Vendors may or may
not develop compatibility products contingent on the market. It is
staggering to think about the scope of open-system environments,
where chips, processors, boards, interface cards, communications
protocols, cabling, operating systems, infrastructure devices, and
applications are essential. With thousands of vendors who develop,
innovate, and deliver these products to the market, it is no wonder
that open systems can be unreliable and unstable.
Mainframes, on the other hand, are closed and proprietary by
design. The mainframe environment is stable and reliable. Few ven-
dors seem to control everything end to end. The mainframe world
achieves superior reliability and performance because the operating
systems, communications protocols, hardware, and system compo-
nents are tightly integrated.
What is done today to bridge the data storage gap between open-
system and mainframe storage? In order to connect these two [ Pobierz całość w formacie PDF ]
zanotowane.pl doc.pisz.pl pdf.pisz.pl akte20.pev.pl
focused on infrastructure-based problems and provides reduced
deployment risks through phased SAN deployment. This helps keep
investments limited to solutions and creates investment bases for
the future. Initial investments will improve the ROI when other sce-
nario investments are reduced.
You should have the following detailed results from an interview
process that define what the SAN needs to accomplish for you:
% Technical requirements document?
% Operating system to be installed?
% Patch or service pack level?
% Whether fabric HBA/controller drivers are available, and if so,
are they well tested?
% How many HBAs will it have?
% If there is more than one HBA, what software will be used to
provide failover or performance enhancements of multiple
paths?
% Private loop, public loop, or fabric connection?
% Applications that will run host databases, e-mail, data
replication, or file sharing?
% Storage requirements?
% Will storage requirements change over time?
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)
Copyright 2004 The McGraw-Hill Companies. All rights reserved.
Any use is subject to the Terms of Use as given at the website.
Configuring SANs: Dos and Don ts
Configuring SANs: Dos and Don'ts
51
% Physical dimensions? How heavy will it be?
% Does it require a rack mount? A rack kit? A shelf set?
% Management console? If so, what type is it?
% Traditional keyboard/video/mouse (KVM) combo?
% Serial connection, such as a TTY?
% Do interfaces exist? Do they need to be purchased?
% Make, model, and version information?
% How many Ethernet interfaces?
% What temperature range for operation?
% Telephone line requirements?
% Node location?
% Timeline for implementation?
% Required purchases?
% SAN design?
Answers to these questions will be used throughout the life of your
SAN. The timeline will be the framework of activities for the SAN
life cycle. These documents will be used in approval processes during
implementation and maintenance phases as SAN deliverables. If
major changes to your SAN environment are necessary, your SAN
life cycle will be repeated, and another set of documentation will
need to be produced.
Interoperability Issues
Currently, interoperability is limited. Equipment from different
manufacturers often will not work in an interoperative fashion
despite common software and hardware interfaces. Third-party test-
ing has become necessary to ensure interoperability. The Fibre
Channel market is widely accepted as the most innovative SAN
development solution at this time. Integrated software companies
play a major role in the development of SANs. System managers and
administrators need to recognize that this is a fact.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com)
Copyright 2004 The McGraw-Hill Companies. All rights reserved.
Any use is subject to the Terms of Use as given at the website.
Configuring SANs: Dos and Don ts
Chapter 4
52
E-commerce is often associated with UNIX and Windows NT sys-
tems. What is overlooked is the fact that mainframes are integral to
the e-commerce supply chain. Telephone companies, shipping com-
panies, credit card companies, and banks all manage multiple main-
frames supporting e-commerce. Mainframes are involved in online
transactions before the customer clicks on a buy icon and until the
product arrives on the customer s doorstep. If data is to be synony-
mous with business, then interconnecting open-system data storage
with mainframe data storage is a primary role in the new economy.
Interconnecting open-system and mainframe storage is not easy.
Data structures, protocols, and architectures vary. Both environ-
ments are double-edged swords in relation to interoperability. Their
strengths are often their weaknesses in the SAN environment. The
nature of an open system is that it is open. The premise of the open-
system environment is that multiple vendors can build compatible
products to interoperate with one another and allow customers to
use common sets of applications and devices. Vendors may or may
not develop compatibility products contingent on the market. It is
staggering to think about the scope of open-system environments,
where chips, processors, boards, interface cards, communications
protocols, cabling, operating systems, infrastructure devices, and
applications are essential. With thousands of vendors who develop,
innovate, and deliver these products to the market, it is no wonder
that open systems can be unreliable and unstable.
Mainframes, on the other hand, are closed and proprietary by
design. The mainframe environment is stable and reliable. Few ven-
dors seem to control everything end to end. The mainframe world
achieves superior reliability and performance because the operating
systems, communications protocols, hardware, and system compo-
nents are tightly integrated.
What is done today to bridge the data storage gap between open-
system and mainframe storage? In order to connect these two [ Pobierz całość w formacie PDF ]