[go: up one dir, main page]

100% found this document useful (1 vote)
458 views29 pages

Storage Area Network: Lecture Notes

The document discusses storage area network (SAN) management. It describes that SAN management involves managing devices like host adapters, switches, and storage arrays. Management can be done either in-band, using the SAN transport, or out-of-band, using a separate network like Ethernet. SNMP is commonly used as the out-of-band management protocol to monitor and configure devices from a central location. The management hierarchy involves device managers, storage managers, and enterprise management platforms.

Uploaded by

madhura mulge
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
458 views29 pages

Storage Area Network: Lecture Notes

The document discusses storage area network (SAN) management. It describes that SAN management involves managing devices like host adapters, switches, and storage arrays. Management can be done either in-band, using the SAN transport, or out-of-band, using a separate network like Ethernet. SNMP is commonly used as the out-of-band management protocol to monitor and configure devices from a central location. The management hierarchy involves device managers, storage managers, and enterprise management platforms.

Uploaded by

madhura mulge
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 29

Lecture Notes

Storage Area Network


( Unit - IV)

Ms. Madhu G. Mulge


( M-Tech CSE )

M.B.E.'S College of Engineering, Ambejogai.

ME - CSE [SAN- Unit VI] 1


Management of SANs
Network Management :
It has one central objective: To maintain the stable transport of data across the
network infrastructure. What is done with the data after it has arrived at its destination is
usually outside the scope of traditional network management disciplines.
The transport of data
storage transport and storage data management
Storage networking shifts the focus from the server to storage and enables
storage management to address data issues apart from individual servers and
independently of the operating platform.

SANs, NT and UNIX servers can now share storage resources of a single disk array,
and management of the array's resources may exist independently.

Example: As a traditional storage management entity—of either an NT or a


UNIX environment.

ME - CSE [SAN- Unit VI] 2


Storage Network Management
Management of the SAN is a hierarchy of functions that may exist as separate
applications or as integrated management systems.

Lower layers move status and event information up through the hierarchy.

Upper layers issue commands and queries down to the appropriate agents.

The management structure is built on a foundation of managed devices that create the
SAN interconnection (host adapters, switches, and bridges).

These devices communicate to their respective device management applications via a


number of protocols.

 Primarily Simple Network Management Protocol (SNMP), SCSI Enclosure Services, or


proprietary APIs.

The device management applications, in turn, may communicate to upper-level storage


and storage resource managers, which may provide interfaces to enterprise-level systems
management platforms.

ME - CSE [SAN- Unit VI] 3


Fig : SAN management hierarchy

ME - CSE [SAN- Unit VI] 4


Storage network management is responsible for interfacing directly with interconnection
equipment.

The vendor of a managed network device supplies a console or graphical interface that, at
minimum, allows port configuration (insert/bypass) and reports basic enclosure
environmental status (power, temperature, etc ).

The feature set of a managed HBA, hub, or fabric switch is vendor-dependent. Some
products offer only basic enclosure and port status, whereas others include performance and
diagnostic utilities.

The application provided by the vendor to manage its product is a device manager.

A management utility for a host adapter card, for example, will give status, configuration,
and port statistics for the adapter, but it may not provide visibility to fabric switches or
other nodes with which it communicates.

The management of multiple storage network products implies the need for multiple
device managers, and consequently multiple management workstations or consoles to
support applications from different vendors.

Device management has software, firmware, and hardware components.


ME - CSE [SAN- Unit VI] 5
Putting a port into bypass mode from a management console, for example, requires use of
a management protocol (such as SNMP) to convey the command from the workstation to
the device.

A management agent on-board the device must then translate the bypass command into a
hardware instruction, and the hardware, in turn, must raise or lower the appropriate leads to
physically bypass the port.

Fig: Device management architecture

ME - CSE [SAN- Unit VI] 6


The controller or firmware that supports the management agent is the device's voice to
the outside world.

Communication between a device and its management workstation may occur through
the storage transport media, this is referred to as in-band management.

Alternatively, management data may be segregated from storage data traffic via an
external Ethernet, RS-232, or other interface, this is referred to as out-of-band
management.

 Out-of-band management through Ethernet normally uses the SNMP protocol, although
Telnet and Web browser HTTP (Hypertext Transfer Protocol)-based implementations are
also available.

In-band and out-of-band solutions have their respective advantages and disadvantages,
and some products offer both to provide complementary functions.

ME - CSE [SAN- Unit VI] 7


In-Band Management
In-band management relies on the SAN transport to carry status and configuration
information between devices and a management console.

The management protocol may be SNMP-based or may be a combination of APIs that


interface to the management software application.

In a Fibre Channel SAN, you might use the common HBA API to report host bus adapter
status and use proprietary switch and storage APIs to report status and configuration
information for the fabric and targets.

In the case of an IP SAN, SNMP or API queries could be sent along the same
infrastructure as the SAN interconnection, directed at the IP addresses of management
entities within host, switch, or target devices.

In-band management simplifies SAN deployment, provided that all the devices that
require management support in-band methods.

Unfortunately, in Fibre Channel SANs some devices still require out-of-band access, so
you need an additional Ethernet network to handle SNMP traffic.

ME - CSE [SAN- Unit VI] 8


Fig: In-band management over the SAN data path

ME - CSE [SAN- Unit VI] 9


The significant drawback of any in-band management scheme is apparent when the
storage transport itself is down or disabled by excessive errors.

Because all management data must move across the storage network, loss of the
transport means loss of management visibility to the managed devices, and that negates
the ability to detect, isolate, and recover from network problems.

Thus, although in-band management fulfills a useful function under stable network
conditions, it is ill equipped to deal with catastrophic physical-layer or transport-level
events.

In large, meshed SANs, you can somewhat obviate this vulnerability by providing:
Redundant links.
Providing alternative paths for storage data and management data.
Adds cost, consumes additional ports.

ME - CSE [SAN- Unit VI] 10


Out-of-Band Management
Out-of-band management avoids in-band issues by moving all management data from
the production storage network.

out-of-band techniques typically use Ethernet for the management data path and wrap
management queries or commands in SNMP, Telnet, or Web browser HTTP protocols.

Most switches and storage targets also provide a serial RS-232 console port as an
alternative (but rarely used) access method.

Because out-of-band implementations do not rely on the SAN transport, you can still
manage host adapters, switches, and storage arrays if the fabric links are down.

Out-of-band management also facilitates integration of storage network management


with enterprise management platforms, particularly those based on IP and SNMP.

The major weakness of out-of-band network management in Fibre Channel


environments is its inability to provide auto-topology mapping and other functions that
require in-band communication between devices.

ME - CSE [SAN- Unit VI] 11


Fig: Out-of-band management requires a separate network to carry management data

ME - CSE [SAN- Unit VI] 12


The most commonly used out-of-band protocols are SNMP, HTTP, and Telnet, all of
which run over IP.

The use of IP to carry management instructions and responses lets you manage storage
network devices from anywhere in a routed IP network.

Storage network management can thus be co-located with the SAN or can be
centralized with other IP-based network management applications in an enterprise
network operating center (NOC).

ME - CSE [SAN- Unit VI] 13


SNMP
SNMP (Simple Network Management Protocol) is the predominant protocol for multi
vendor enterprise networks and is widely supported by routers and switches in wide and
local area networking.

SNMP provides a command set for soliciting status (SNMP Gets) or setting operational
parameters (SNMP Sets) of target devices.

An enterprise-wide SNMP management platform is typically run as a graphical interface


on a large UNIX or NT workstation and may poll hundreds of devices throughout the
routed network.

The management platform contains the SNMP manager; the managed router, hub, or
switch contains an SNMP agent.

Device status information may include a variety of data points: serial number, vendor ID,
enclosure status, port type, port operational state, traffic volumes, error conditions, and so
on.

This information is organized in a management information base (MIB), which is


maintained by both the management workstation and the SNMP agent within the managed
device.
ME - CSE [SAN- Unit VI] 14
For LAN and WAN management, several standard MIBs have been sanctioned by the
internetworking community through a series of RFCs.

If a vendor wishes to include additional device information that is not specified in a
standard MIB, vendor-specific parameters or status can be compiled in a proprietary
enterprise MIB or MIB extension.

Device information, status, and control variables within an MIB are organized in a
hierarchical data structure called structure of management information (SMI).

SMI defines an information tree whose branches lead to various management information
bases and whose leaves are discrete data about a device's functionality and status.

SMI notation, which is carried within an SNMP query or command, is essentially an


address pointing to the location of the data requested by the management workstation.

ME - CSE [SAN- Unit VI] 15


Fig: SNMP SMI notation for a Fibre Channel loop hub device
ME - CSE [SAN- Unit VI] 16
In addition to providing the ability to actively query a device for status, SNMP allows a
device to generate a trap, or unsolicited status information.

If a preconfigured error condition or threshold is reached, the managed device will
initiate an SNMP message to the management workstation as an alert.

On the management platform, the icon representing the managed device typically turns
yellow or red, and the application may send a page or e-mail to the network operator.

Because SNMP is a protocol shared by the vendor's device management application and
third-party management platforms, SNMP traps can be directed to either one.

SNMP allow a trap to be addressed to the Open View management workstation, which
could then automatically launch the vendor's device manager for further status or diagnosis
of the problem.

Any management facility based on IP implies additional traffic on the messaging


network.

Although polling for all status information from multiple SNMP agents may generate
noticeable overhead, SNMP management applications can reduce IP traffic by relying on
traps for notification of events or by polling only for changes from an original status
check.
ME - CSE [SAN- Unit VI] 17
HTTP
Use of HTTP (Hypertext Transfer Protocol) is a management tool that leverages the
proliferation of Web browsers for managing network products.

Web-based management of network resources is being extended through the Web Based
Enterprise Management (WBEM) initiative, which makes browsers the common interface
for managing diverse network components.

An HTTP management implementation has two components: an HTTP server that
resides in firmware at the managed device, and a Web browser (such as Netscape or
Explorer) that acts as a management graphical interface.

By pointing the browser to the IP address of the managed device, the user can navigate a
series of screens to monitor device status or change device parameters.

Embedded HTTP capability is an entry-level management scheme and does not integrate
into broader management applications as easily as SNMP or SES.

Because a browser can be addressed only to one IP target at a time, the administrator
would have to open multiple instances of a browser application to manage multiple HTTP-
based devices
ME - CSE [SAN- Unit VI] 18
Embedded HTTP management does not facilitate a comprehensive view of all managed
products.

Management-by browser is therefore more suited to small SAN installations with a


single fabric to monitor.

 Recognizing that HTTP-based management has an appeal for the low end of the market,
vendors of SAN products may provide both HTTP and SNMP management options.

Even with password protection at the managed device, HTTP presents a higher security
risk than other methods.

All that is required to access an HTTP-managed device is a browser (which everyone


has) and the proper IP address (which can be hacked).

At minimum, password protection should be provided for both read-only and read/write
access, complemented by a firewall to prohibit external penetration of the customer
network.

Browser-based management can also be implemented in a client/server configuration.

ME - CSE [SAN- Unit VI] 19


A management workstation communicates with devices using SNMP and concurrently
provides an HTTP server interface to remote browser consoles.

This arrangement allows multiple remote managers to view the storage network via
browsers and overcomes the single-device limitation of embedded HTTP management.

By assigning read-only and read/write permissions, the administrator can provide
management operations for monitoring and modification controls.

Fig: Browser-based HTTP client/server


management

ME - CSE [SAN- Unit VI] 20


Telnet
Unlike typical SNMP- or HTTP-based management solutions, a Telnet implementation
is a text-only, command line interface.

The user sends a Telnet command across the IP network to the managed device (for
example, Telnet 192.168.1.1) and establishes a session.

The vendor, hopefully, has provided one or two layers of password protection, beyond
which a menu of commands is available.

Telnet is usually used only to set the device's default IP address to one that can be used
for SNMP access, but a command line interface alone is sometimes the tool of choice for
UNIX environments.

The command set available and status information that can be queried via Telnet are
vendor-dependent.

Some offer only basic configuration commands, whereas others provide commands and
queries for all functions that are available through the vendor's SNMP graphical interface.

ME - CSE [SAN- Unit VI] 21


Storage Network Management Issues
Storage network management faces several challenges previously encountered in local
and wide area networking.

In complex multi vendor, multiplatform environments, customer requirements cannot be


met with proprietary management solutions, even if a vendor offers a rich feature set for
man agreement of its own products.

Open systems exert pressure on all vendors to seek common methods cooperatively
while competing for market share with unique functionality.

This contradiction slowly and sometimes painfully works its way through standards
bodies and industry groups, with both technical and political consequences.

Because storage network management is shaped by the methods and capabilities of


individual device managers, the configuration, status, and diagnostic features of each Fibre
Channel network product are more useful if they are accessible through a common
platform.

ME - CSE [SAN- Unit VI] 22


Development of standard Fibre Channel MIBs, for example, simplifies the creation of
comprehensive network management applications and enables high-level storage
management platforms to gather data from the SAN interconnect.

A common management language also facilitates network management of the SAN. A


single enterprise may have NT, Solaris, AIX, HP-UX, and other operating systems spread
across the network.

Network management may be centralized in a NOC or may be dispersed throughout


individual business units.

To accommodate the variety of platforms on which management applications may be


run, the trend in SAN management has been toward a standardized management interface
suitable for multi vendor SANs and one that can be implemented on a variety of
management platforms.

ME - CSE [SAN- Unit VI] 23


Storage Resource Management
The SAN management hierarchy, storage resource management (SRM) applications
are a subset of more comprehensive storage management platforms.

SRM applications are available as stand-alone programs or as plug-in modules for


broader management applications.

They are written to either homogeneous or heterogeneous operating system


environments.

The primary value offered by these programs is the ability to make all distributed disk
assets visible to a single management console.

Because SRM applications are focused exclusively on storage availability and


utilization, the way that storage is physically connected to servers is largely transparent.

Therefore, SRM applications are not unique to SANs but may also encompass internal
workstation-attached, SCSI-attached, and NAS storage.

The SAN-specific features of a storage resource application surface when, via the SAN
interconnection, multiple servers have access to the same storage arrays and when the
SRM workstation itself is SAN-attached.
ME - CSE [SAN- Unit VI] 24
Storage resource management addresses these shortcomings by automating the process of
disk information retrieval and presenting a single view of all disk resources.

 SRM client software on each server periodically updates information on its assigned
volumes and directories and forwards this data to the SRM manager.

The SRM management platform, in turn, consolidates the status information from
multiple clients in a relational database and may, depending on the vendor's
implementation, provide storage policies that issue.

As with trending tools in local and wide area networks, SRM applications may also offer
enhanced capacity planning utilities that facilitate redistribution of storage resources and
provide data for accurate budget forecasts of impending storage needs.

SANs enable a storage-centric model, SRM applications can be leveraged more


effectively for optimal use of storage than can fixed SCSI configurations.

JBODs and RAIDs on a storage network, for example, offer more flexibility in
redistribution of disk space between SAN-attached servers and more easily accommodate
increases in the pool of storage without system down time.

ME - CSE [SAN- Unit VI] 25


Storage Management
Storage management (also referred to as enterprise storage management) is a broader
category of storage functions:
addition to asset tracking
Tape backup archiving
Data placement volume
File policy administration.

 A storage management application may be an umbrella, multifunctional platform,


packaged as a suite of complementary software products or as stand-alone programs
dedicated to specific management functions (such as tape backup).

As with SRM applications, storage management is facilitated by, but not dependent on,
storage area network topologies.

Vendors of storage management products, however, have become SAN proponents,


largely because of the greater flexibility provided by SANs over other storage
configurations.

The more tightly integrated these activities are within a single application, the simpler
storage administration becomes for day-to-day operations.
ME - CSE [SAN- Unit VI] 26
Storage management functions may monitor access to shared resources such as tape
libraries or optical archives, schedule non-disruptive disk de-fragmentation routines,
manage the growth and integrity of file systems, and oversee cross-platform access to
storage.

As more storage, tape, and archive systems appear on the SAN, integration is further
enhanced, because the storage management platform itself can access resources directly
without having to pass through servers.

ME - CSE [SAN- Unit VI] 27


Storage, Systems & Enterprise Management
Integration
Systems management applications consolidate the process of monitoring and controlling
network resources, and they often encompass different networks within an enterprise under
a single application umbrella.

A systems management application may be dedicated to a specific function, such as


utilization and performance of all network resources, or it may incorporate related
categories across multiple networks.

Systems management functions such as security management and fault management


span wide area, local area, and storage networks, and so they require common interfaces to
all topologies.

Enterprise management applications embrace all or most of the individual systems


disciplines and provide the most comprehensive view of all corporate network resources.

Management of storage and storage networking can be integrated into higher-level


systems and enterprise management applications.

ME - CSE [SAN- Unit VI] 28


Thank U…~!~

ME - CSE [SAN- Unit VI] 29

You might also like