Share or add to bookmark

AddThis Social Bookmark Button

Latest comments

Authorization



  
Home Setup examples
Категории
Примеры настройки оборудования

setup examples
Hitachi AMS2000 configuration and setup example (Part 1)
This is example of starting-up procedure and basic configuration Glossary Link disk arrays Hitachi AMS2000 series. This article contains the following sections:
Arrays overview
 
Hitachi disk arrays AMS2000 series is midrange storage systems. These arrays use a 3.5 inch SAS\SATA hard drives, and can work with SSD drives. This arrays fully operates on 3G SAS protocol witch provides a high speed data transfer operations and high I/O transfers. Comparing with Fibre Channel, SAS doesn’t use loops and FC switches and makes arrays more costeffective. One array can hold up to 480 disks and can take up to 3 racks.
 
Table 1. Competitive table
 
AMS2100
AMS2300
AMS2500\ AMS2500DC
Maximum number of disk drives
159
240
480
Maximum number of Fibre Channel ports
4
8
16
Maximum number of iSCSI ports
4
4
8
SAS links
16
16
32
Upgradable to
to AMS2300
to AMS2500
No
 
Preparation for the startup
After checking all the cables in the rack of the array and connecting the array to the SAN Glossary Link network, you should set a power mode of the array. This is posible to set using a rotary switch on the front side of the Glossary Link controller shelf, as shown on Figure 1. Mode of the array must correspond to electrical sheme, lists of posible modes and descriptions listed in Table 2. Depends on the position of the switch arrays chose Glossary Link cache memory operation modes and time for switching off. Switching between modes is done only available with the system powered off.
 Figure 1. Rotary switch
Figure 1. Rotary switch
 
Table 2. Rotary switch modes
Rotary switch
Operation mode name
Operation mode
0
LOCAL
Local mode (Before shipment. When the remote adaptor is not used.)
1
---
---
2
REMOTE
Remote mode by means of the HOST AC (using a remote Glossary Link adapter)
3
---
---
4
UPS Interlock mode 1
Interlock mode 1 with an UPS exclusive for the subsystem
To set the mode, connect AC #0 and AC #1 to the UPS and an external and an external AC power supply or the PDB of the RK40 rack frame respectively.
5
UPS Interlock mode 2
Interlocking mode 2 with an UPS exclusive for the subsystem
To set the mode connect AC #0 and AC #1 to the one UPS.(*1)
6
UPS Interlock mode 3
Interlocking mode 3 with an UPS exclusive for the subsystem
To set the mode, connect each of AC #0 and AC #1 to the different UPSs. (*2)
7
---
---
8
---
---
9
---
---
   Do not set 0 and 2 when the UPS is not connected.
*1 : The duplication of the power supply system becomes unable to be done.
*2 : This cannot be used in the case of the single controller configuration.
DF-F800-VR4A is a Remote Adapter is optional part, whitch used to control power cuts and connects to a UPS monitoring server.
 
After the rotary switch is set up, you can start an array. To do this you need to power on power strip PDB at the back of the racks. Now you can start array by turning on the switch on the front panel. Then usally after about five minutes indicator READY LED, should light up green.
When doing this, when the READY LED (green) on the front of the Basic Chassis is blinking at high-speed in the dual controller configuration, the READY LED (green) on the front of the Basic Chassis lights up after it blinks at high-speed for the maximum of 30 to 50 minutes because the automatic download of the ENC firmware is operating.
 
Installing management software
Following completion of the start of array, you can start configuring it. To complete this operation you need to install array management software Hitachi Storage Navigator Modular 2, system requirements are listed in Table 3.

Table 3. System requirements
Processor
1 GHz (2 GHz or faster recommended)
Memory
At least 1 GB
Free disk space
1.5 GB
Video resolution
1024 x 768
Operation system
Microsoft® Windows® XP (Service Pack 2), 2003 Server (Service Pack 1), Windows 2000 (Service Pack 3/4); or Sun Solaris™ v8 or v9
Internet Explorer v 6.0 for Microsoft Windows operating systems or Mozilla v1.7 for Solaris operating systems
 
You should connect the ports of control array to Ethernet network or directly to the management computer. By default, the IP addresses of controllers uses foloving:
CTL #0 - 10.0.0.16; 192.168.0.16; 192.168.233.16; 172.23.211.16; 10.197.181.16
CTL #1 - 10.0.0.17; 192.168.0.17; 192.168.233.17; 172.23.211.17; 10.197.181.17 subnet mask 255.255.255.0
 
To enter the Hitachi Storage Navigator Modular 2 type in your browser following address: http://xxxx:23015/StorageNavigatorModular/ or https: / /xxxx: 23016/StorageNavigatorModular/ for the https, where xxxx - IP address of the management computer wnere Hitachi Storage Navigator Modular 2 installed. Program will prompt you to login to the program, as shown on Figure 2. When Hitachi Storage Navigator Modular 2 was newly installed, enter the temporarily registered user ID “system” and password “manager”.

Figure 2. Login window
Figure 2. Login window

The Hitachi Storage Navigator Modular 2 is activated in the Normal Mode and the main window is displayed. You can execute the display of the Hitachi Storage Navigator Modular 2 Operation Mode and state of the failure monitoring and the following functions in the main window.
For the operation of each function, refer to the page explaining each function.
• Registration of the disk array subsystem (registration, deletion, change, and properties display)
• Execution of the failure monitoring and setting of the failure monitoring option
• Change of the Operation Mode
• Display of the version
 
Figure 3. Main window
Figure 3. Main window
 
 
Hitachi Storage Navigator Modular 2 has three Active Modes, that is, the Normal Mode, Management Mode, and Maintenance Mode. In the Normal Mode, the program displays the configuration and statuses of the disk array. In the Management or Maintenance Mode, it can set the configuration of the disk array in addition to the function in the Normal Mode.
Changing the Normal Mode to the Maintenance Mode
Change the Operation Mode from the Normal Mode to the Maintenance Mode.
Check that the “mode” file exists in the following directory:\HiCommand\StorageNavigatorModular\conf.
If there is no mode file, create a mode file (without extension) and write the following letters in one line "StorageNavigatorModular". However, do not insert line feeds.
Store the created mode file in the following place:\HiCommand\StorageNavigatorModular\conf.
Put a checkmark in the array subsystem to operate on the main window, and press the [Ctrl] key, [Shift] key and the [E] key at the same time.
It is displayed as “maintenance mode” in [Operation Mode] of the upper part of the main window, and Hitachi Storage Navigator Modular 2 is operated in the maintenance mode, as shown on Figure 4.

Figure 4. Maintenance mode
Figure 4. Maintenance mode
 
 
Adding the disk array subsystem to be operated in order to operate it from the Hitachi Storage Navigator Modular 2.
Click the [Add Array] button in the “Subsystems” window of the main window. “HSNM2_Add Array Wizard” window is displayed.
Figure 5. HSNM2_Add Array Wizard
Figure 5. HSNM2_Add Array Wizard

The array subsystem register is searched. Specify a search method and a range to search by a host name or an IP address.
 Figure 6. IP address search window
Figure 6. IP address search window
 
The search result is displayed. Specify the array subsystem to register, and click the [Next] button. Enter the IP address only in the Control Unit to which the Glossary Link LAN cable is connected. If the IP address is entered in a Control Unit to which the LAN cable is not connected, an error is caused.
 Figure 7. Search result
Figure 7. Search result
Read more... Add new comment
 
HP FCoE switches and configurations (part 1)

HP Glossary Link FCoE switches and configurations

 

Description
The HP FCoE solution deploys FCoE technology in existing Ethernet and FC environments with the benefit of convergence at the server and fabric edge using CNAs and converged Glossary Link network (CN) switches.
The HP FCoE solution provides this benefit in addition to investment protection by allowing FCoE to be integrated with existing HP Fibre Channel SANs. The FCoE product set consists of the following:
• HP B-series and C-series converged network switches—Provide a bridge function from the CN to separate Ethernet and FC fabrics
• Emulex LP2100x converged network adapters (CNAs)—Converge Ethernet and FC technologies in the server over 10 GbE links to converged network switches FCoE CN switches are available from HP. Emulex LP2100x CNAs are available through the HP third-party options (3PO) program and by Emulex authorized resellers and distributors.

Benefits
This section describes some of the benefits of FCoE technology. The convergence of Ethernet and FC provides the same level of connectivity as previous technologies, but requires:
• 50% fewer switches in each server rack—Only two CN Top of Rack (ToR) switches, compared with four (two network and two FC) switches per rack with separate Ethernet and FC switches
• 50% fewer adapters per server
• 75% fewer cable connections (see Table 1)
Figure 1 illustrates a rack with 16 servers using FCoE technology compared to a rack using separate FC and Ethernet with the same level of connectivity. Similarly, Table 1 provides a comparison of cable requirements for these same racks.

Table 1 Rack cable requirements comparison

Separate FC and Ethernet networks

Converged FCoE network1

(4) 4-Gb FC cables

(4) 1-GbE NIC cables

(8) cables at 20 Gb per server

(2) 10-GbE cables

(2) cables at 20 Gb per server

Total of 128 cables for 320 Gb of connectivity

Total of 32 cables for 320 Gb of connectivity

1Using copper cables for FCoE connections further reduces the per-port connection cost versus the cost of optical SFP+ transceivers.

 

 

Figure 1 Rack cable comparison

Figure 1 Rack cable comparison


Converged network switches
The first generation of FCoE CN switches enable Ethernet and FC to coexist in a fabric and are designed as edge switches or ToR switches. Edge/ToR switches are typically deployed in redundant pairs installed at the top of a server rack (see Figure 1). By using FCoE CN switches, you reduce the number of required switches by replacing separate Ethernet and FC switches with a converged edge/ToR switch. From the edge/ ToR switch, inter-switch link (ISL) connections to the End-of-Row (EoR) FC and EoR Ethernet/IP switches provide access to the separate core layers of the FC fabric and Ethernet/IP network.
The following HP FCoE CN switches are available:
• HP StorageWorks 2408 FCoE Converged Network Switch
• HP C-series Nexus 5010 Converged Network Switch
• HP C-series Nexus 5020 Converged Network Switch

Converged network switch ports HP FCoE CN switches have two types of physical ports:
• 10 Gb Ethernet (10 GbE) ports
• 4 or 8 Gb FC ports
FC ports can be used for either ISL connections to an existing FC fabric, or connection directly to an HP storage array.
Table 2 lists the number of ports for each HP FCoE CN switch.

Table 2 Number of ports per switch

HP switch

Number of 10 GbE ports

Number of FC ports

2408 FCoE Converged Network Switch

24

8 (8 Gb/s)

C-series Nexus 5010 Converged Network Switch

20 to 26

0 to 8 (4 Gb/s)

C-series Nexus 5020 Converged Network Switch

40 to 52

0 to 16 (4 Gb/s)

 

 

NOTE:
All FCoE CN switch models are by design converged enhanced Ethernet (CEE) switches and are enabled for Ethernet by default. In order to be used for FCoE they must be enabled to forward FC frames to the FC ports.
HP does not support interoperability between different vendors' CN and FC switches:
• 2408 FCoE Converged Network Switch operate with B-series FC switches only.
• C-series Nexus 5010/5020 Converged Network Switches operate with other C-series MDS FC switches only.

HP StorageWorks 2408 FCoE Converged Network Switch
The 2408 FCoE Converged Network Switch is a rebranded version of the Brocade 8000 FCoE Switch (Figure 2).

Figure 2 2408 FCoE Converged Network Switch
Figure 2 2408 FCoE Converged Network Switch

Features
• Next-generation Ethernet L2/L3 switch and next-generation FC switch merged into one product
• CEE support
• Full industry-standard implementation
• Supports FCoE and FCoE Initialization Protocol (FIP)
• 24 10-GbE and 8 8-Gb/s FC ports
• Uses 1 rack unit (RU) of space
• Leverages existing Brocade fabric operating system (FOS)
• Supports the following link aggregation (LAG) on CEE ports:
• Brocade proprietary LAG
• IEEE 802.3ad – standards based LAG (default)
• Supports Brocade ISL trunking on FC ports

Considerations
• Fixed port types:
You cannot use 10 GbE ports for FC connections, and you cannot use FC ports for 10 GbE connections.
• L3 routing features are not currently supported
• 10 GbE ports support virtual F_Ports only (virtual E_Ports are not supported)

HP C-series Nexus 5010/5020 Converged Network Switches
HP resells the Cisco Nexus 5010 and 5020 Switches (Figure 3).

Figure 3 C-series Nexus 5010 and 5020 Converged Network Switches
Figure 3 C-series Nexus 5010 and 5020 Converged Network Switches
.
Features
• L2 access
• IEEE Data Center Bridging (DCB) and FCoE support
• IEEE DCB is a Cisco CEE product with additional proprietary features
• NX-OS with combined features from Cisco Internetwork Operating System (IOS) and Cisco SAN Operating System (SAN-OS)
• Cisco 5020 (2 RU)
• 40 10-GbE ports
• Two optional expansion module slots
• Up to 52 10-GbE ports, or a combination of 40 10-GbE ports and 16 FC ports
• Cisco 5010 (1 RU)
• 20 10-GbE ports
• One optional expansion module slot
• Up to 26 10-GbE ports, or a combination of 20 10-GbE ports and 8 FC ports
• Optional expansion modules:
• 6-port 10-GbE expansion module
• 8-port 4-Gb/s FC expansion module
• 4-port 4-Gb/s FC and 4-port 10-GbE expansion module

Converged network adapters
Servers with CNAs require fewer adapters per server and, therefore, 75% fewer cable connections for network and FC attachments.
HP supports the Emulex LightPulse LP21000 family of CNAs in certain ProLiant servers. For a list of servers that support CNAs, see HP ProLiant server support.
Table 3 lists the supported Emulex CNAs available as a reference sell from HP 3PO.

Table 3 CNA part numbers

HP 3PO part number1

Emulex part number

Description

A711956

LP21000-M

Single channel optical CNA (includes one SFP+ SR transceiver)2

A711954

LP21000-C

Single channel copper CNA (includes one 3-m SFP+ twinax copper cable)3

A711957

LP21002-M

Dual channel optical CNA (includes two SFP+ SR transceivers)2

A712947

LP21002-C

Dual channel copper CNA (includes two 3-m SFP+ twinax copper cables)3

A745955

LP21000-NC

Single channel copper CNA (no cable or transceiver is included)

A745954

LP21002-NC

Dual channel copper CNA (no cables or transceivers are included)

1HP sales representatives use the HP 3PO part numbers to order these parts from an Emulex-authorized distributor through the HP Vista procurement process. The parts are not labeled with an HP part number or identified as HP parts. HP supports the use of these products in HP FCoE configurations. However, customer service support for CNAs is provided by Emulex.

 

2The SFP+ SR transceiver is supported with this CNA only. It is not supported with the 2408 FCoE Converged Network Switch or C-series Nexus 5010/20 Converged Network Switch, which use a special brand of SFP+ transceiver. For more information, contact your HP support representative.

 

3The copper cable included with this CNA is supported with the C-series Nexus 5010/20 Converged Network Switch only. It is not supported with the 2408 FCoE Converged Network Switch.


Figure 4 shows an Emulex LP21002-M CNA. Other Emulex CNAs are similar in appearance.

Figure 4 Emulex LP21002-M CNA
Figure 4 Emulex LP21002-M CNA

Figure 5 shows a diagram of the internal components of a CNA.
Figure 5 CNA internal components
Figure 5 CNA internal components

Features
The CNAs have the following features:
• Emulex 4 Gb/s FC dual-port Glossary Link controller
• Dual-port 10 GbE Intel Opland 82598 NIC
• 10 GbE and FC multiplexed through a Cisco Menlo application-specific integrated circuit (AISC)

Considerations
• Requires a full-height/full-length x8 PCIe slot
• Requires 25W of power
• 1 GbE is not supported

Configuration rules
This section describes configuration rules for the HP FCoE solution. The rules are defined for the CNAs and each of the FCoE CN switch series.
Figure 6 shows a converged SAN fabric with servers using CNAs only.

Figure 6 Converged SAN fabric configuration
Figure 6 Converged SAN fabric configuration

Figure 7 shows a converged fabric that has servers with CNAs and servers with FC host bus adapters (HBAs) and network interface cards (NICs).

Figure 7 FCoE integrated with FC SAN fabric
Figure 7 FCoE integrated with FC SAN fabric

CNA configuration rules
Table 4 Emulex LP21000/LP21002 requirements

Item

Description

Number of CNAs per server (maximum)

• DL580-G5 and DL585-G5 support 2 CNAs

• All others support 1 CNA

Cable types

• SFP+ optical Cable types

• Copper

CEE firmware

0.5a5 or later

FC firmware

1.00x1 or later

Boot versions

• Intel NIC 13.5 or later

• Emulex FC Universal Boot Version 5.03a5/x86 BootBIOS 2.02a2 or later

FC driver versions (minimum)

• Windows 2003/2008 (x86, x64) 2.20.006

• RHEL 5 Update 2 (x86, x64) 8.2.0.33.3p

• SUSE 10 Update 2 (x86, x64) 8.2.0.29

• ESX 3.5 (x86) 7.4.0.41

NIC driver versions (minimum)

• Windows 2003/2008 (x86, x64) 1.3.10.0

• RHEL 5 Update 2 (x86, x64) 1.3.16.1

• SUSE 10 Update 2 (x86, x64) 1.3.16.5

• ESX 3.5 (x86) In Box Driver
 
Read more... Add new comment
 
HP FCoE switches and configurations (part 2)

HP Glossary Link FCoE switches and configurations (part 2)

 

FCoE CN switch configuration rules

Table 5 2408 FCoE Converged Glossary Link Network Switch fabric rules

Rule number

Description

1

A 2408 FCoE Converged Network Switch can be a standalone switch or an edge switch in a Fibre Channel fabric. To attach the switch to an existing Fibre Channel fabric as an edge switch, at least one Fibre Channel port on the FCoE CN switch must be connected to a Fibre Channel switch in the fabric (E_Port). There cannot be any other FCoE or 10 GbE CEE switches in the path to the Fibre Channel switch.

For FCoE E_Port connectivity, see the appropriate Fabric OS release notes for the minimum and recommended Fibre Channel switch firmware versions and the supported Fibre Channel switch models.

2

Server CNAs must be connected directly to FCoE CN switch CEE ports (pre-FIP support only).

3

Fibre Channel storage can be connected directly to the FCoE CN switch (F_Port) or to a Fibre Channel switch (F_Port) that is in the same fabric as the FCoE CN switch. SAN boot is not supported when storage systems are connected directly to FCoE Fibre Channel ports.

4

Supports a maximum of seven switch hops (eight switches) between a CNA and storage.

5

Supports the following CEE media types: B-series hot pluggable, 10 GbE SFP+ Short Reach (SR) and Long Reach (LR) optical transceivers, or B-series SFP+ Copper Twinax active cables.

Supports the following CNA media types: Emulex 10 GbE SFP+ Short Reach (SR) and Long Reach (LR) optical tranceivers, or B-series SFP+ Copper Twinax active cables.

6

Up to 4,000 VLANs, but only one FCoE VLAN is currently supported

7

Only FPMA is currently supported.

8

Supports existing B-series Fibre Channel rules and features except for the following: Virtual Fabrics, Admin Domains, Access Gateway, FICON, Extended Fabrics, integrated FCR, Adaptive Networking, TI Zones, M-EOS interoperability, Non-disruptive firmware upgrade, Port based zoning and QoS zoning

 

Table 6 C-series FCoE Converged Network switch fabric rules

 

Rule number

Description

1

A C-series FCoE CN switch can be a standalone switch or an edge switch in a Fibre Channel fabric. To attach the switch to an existing Fibre Channel fabric as an edge switch, at least one Fibre Channel port on the FCoE CN switch must be connected to a Fibre Channel switch in the fabric (E_Port). There cannot be any other FCoE or 10 GbE IEEE DCB switches in the path to the Fibre Channel switch.

For FCoE E_Port connectivity, the Fibre Channel switch minimum firmware version is NX-OS 4.1(1b). All C-series 4 Gb/s or 8 Gb/s switch models are supported when using the minimum firmware version.

MDS switches running SAN-OS 3.x can be in the Fibre Channel SAN but cannot be connected directly to an FCoE switch.

2

Server CNAs must be connected directly to FCoE CN switch IEEE DCB ports (pre-FIP support only).

3

Fibre Channel storage can be connected directly to the FCoE CN switch (F_Port) or to a Fibre Channel switch (F_Port) in the same fabric as the FCoE CN switch. SAN boot is not supported when storage systems are connected directly to FCoE Fibre Channel ports.

4

Supports a maximum of three switch hops (four switches) between a CNA and storage.

5

Supports the following IEEE DCB media types: C-series hot pluggable, 10 GbE SFP+ Short Reach (SR) and Long Reach (LR) optical transceivers, or C-series and Emulex SFP+ Copper Twinax passive cables.

Supports the following CNA media types: Emulex 10 GbE SFP+ Short Reach (SR) and Long Reach (LR) optical, or C-series and Emulex SFP+ Copper Twinax passive cables.

6

Supports up to 50 switches in a single physical fabric or VSAN

7

Supports up to 40 domains per VSAN

8

Supports a maximum of 250 VLANs per switch

9

Supports a maximum of 32 VSANs per switch

10

Supports a maximum of 32 zones per virtual or physical F_port (includes all VSANs)

11

Supports a maximum of 500 zone sets per switch (includes all VSANs)

12

Supports a maximum of 8,000 zone members per physical fabric (includes all VSANs)

13

Supports a maximum of 8,000 zones per switch (includes all VSANs)

14

Supports up to 52 virtual Fibre Channel interfaces per switch

 

HP ProLiant server support
FCoE is supported with ProLiant G5 servers with a full-height/full-length 8-lane PCIe slot using the LP21000 family of CNA modules. The server models that HP supports for use with CNAs are as follows:
• DL120-G5
• DL160-G5
• DL160-G5p
• DL165-G5
• DL165-G5p
• DL185-G5
• DL320-G5p
• DL360-G5
• DL365-G5
• DL380-G5
• DL385-G5
• DL385-G5p
• DL580-G5
• DL585-G5
• DL785-G5

Storage system support
This section describes storage system support for access from CNA-based servers. These storage systems can be attached to Fibre Channel switches in the fabric or connected to the Fibre Channel ports of an FCoE CN switch.
SAN boot is not supported when storage systems are connected to the Fibre Channel ports of an FCoE CN switch. SAN boot is supported when attached to Fibre channel switches and based on the current support listed for Fibre Channel switches.

Storage array

Glossary Link Controller software version (minimum)

MSA2000fc G2 (MSA2312fc/MSA2324fc)

M100R18

MSA2000fc (MSA2012fc/MSA2212fc)

J200P24

EVA4400

09006000

EVA4400 with embedded switch1

EVA4100/6100/8100

6.200

EVA6400/8400

09501000

XP10000/12000

50.09.78.00

XP20000/24000

60.04.04.00

1The EVA4400 with embedded switch is supported with 2408 FCoE Converged Network Switches only.

 

 

Operating system support
FCoE is supported with the following operating systems:
• Microsoft Windows 2003 (x86, x64)
• Microsoft Windows 2008 (x86, x64)
• Red Hat Enterprise Linux 5, Update 2 (x86, x64)
• SUSE Linux Enterprise Server 10, Update 2 (x86, x64)
• VMware ESX 3.5 (x86)

Boot from SAN support
Boot from SAN (BFS) is not supported for FC arrays attached to 2408 FCoE Converged Network Switches or C-series Nexus 5000 Converged Network Switches at this time. BFS is supported for FC arrays attached to standard FC switches in a fabric that includes CN switches.. This section provides information about installing BFS software.

Windows 2003 (x86, x64) and 2008 (x86, x64)
• BFS is supported on all supported HP servers except Windows 2008 (x86, x64) on the DL165- G5.
• The information in HP StorageWorks Booting Windows Server 2003 and Windows Server x64 Edition systems from a storage area network application notes (available on http://h18006.www1.hp.com/storage/networking/bootsan.html ) is accurate for Windows BFS on a CNA based server for Windows 2003 with the following exceptions:
• You must install a 2.20.006 BFS kit (available for download at the Emulex website http://www.emulex.com/downloads.html ).
• For Windows 2003, press F6 to prompt for the driver Glossary Link disk
• For Windows 2008, click Load Driver when prompted for the location in which to install Windows (see Figure 8).

 Figure 8 Install Windows 2008 (x86, x64)
Figure 8 Install Windows 2008 (x86, x64)

.
Red Hat Enterprise Linux 5 Update 2 (x86, x64)
• BFS is supported on all supported HP servers.
• The information in Booting Linux x86 and x86_64 systems from a Storage Area Network with Device Mapper Multipath (available at http://h18006.www1.hp.com/storage/networking/bootsan.html ) is accurate for BFS on a CNA based server with the following exceptions:
• An Emulex Driver Disk iso image is required (available for download at the Emulex website http://www.emulex.com/downloads.html ).
• Use the linux dd mpath rather than the linux mpath command to prompt to load a driver and enable multipath for the installation.

SUSE Linux Enterprise Server 10 Update 2 (x86, x64)
• BFS is supported on all supported HP servers.
• The information in Booting Linux x86 and x86_64 systems from a Storage Area Network with Device Mapper Multipath (available at http://h18006.www1.hp.com/storage/networking/bootsan.html ) is accurate for BFS on a CNA based server with the following exceptions:
• Use the Emulex Driver Disk (available for download at the Emulex website http://www.emulex.com/downloads.html ). Do not use the ISO image for Red Hat.
• Use the GUI to load the driver (Figure 9).

 Figure 9 SLES installation
Figure 9 SLES installation

Multipathing software support
Table 8 Multipathing software

Operating system

Multipathing software

Version (minimum)

Microsoft Windows 2003 (x86, x64)

Microsoft Windows 2008 (x86, x64)

HP MPIO

3.02.00

Red Hat Enterprise Linux 5, Update 2 (x86, x64)

SUSE Linux Enterprise Server 10, Update 2 (x86, x64)

Device Mapper

4.1.1

Read more... Add new comment
 
HP FCoE switches and configurations (part 3)
Quick-setup instructions
Glossary Link FCoE CN switches have dual capabilities in that they serve as both an Ethernet switch and an FC switch. You must perform a setup procedure to achieve the desired function.
If you are familiar with the FCoE CN switch vendor’s FC switches, then you are familiar with the commands required to configure that portion of the FCoE CN switch setup. The procedures in this section are intended as a quick-start guide to configuring the FCoE ports on an FCoE CN switch to access the FC ports on the FCoE CN switch and other attached FC switches.

2408 FCoE Converged Glossary Link Network Switch quick setup
This procedure is intended for users who are familiar with Brocade FC switches and have experience merging B-series FC switches into an existing FC fabric. Use this procedure to enable servers with CNAs attached to the 2408 FCoE Converged Network Switches to access devices on the attached B-series FC fabric.

IMPORTANT:
If you are not familiar with Brocade FC switches or you do not have experience merging B-series FC switches into an existing FC fabric, use the detailed instructions found in the switch user guide to set up your switch.

1. Configure Link Layer Discovery Protocol (LLDP) for FCoE (common to all CEE ports).
switch:admin> cmsh
switch# enable
switch# config terminal
switch(config)# protocol lldp
switch(conf-lldp)# advertise dcbx-fcoe-app-tlv
switch(conf-lldp)# advertise dcbx-fcoe-logical-link-tlv
switch(conf-lldp)# exit

2. Create a CEE map to carry Glossary Link LAN traffic (60%) and SAN traffic (40%) (common to all CEE ports).
switch(config)# cee-map default
switch(conf-ceemap)# priority-group-table 1 weight 40 pfc
switch(conf-ceemap)# priority-group-table 2 weight 60
switch(conf-ceemap)# priority-table 2 2 2 1 2 2 2 2
switch(conf-ceemap)# exit

3. Create an FCoE virtual LAN (VLAN) for traffic to and from the FC fabric (required for FCoE).
switch(config)# vlan classifier rule 1 proto fcoe encap ethv2
switch(config)# vlan classifier group 1 add rule 1
switch(config)# interface vlan 5 (Can be any VLAN number other than 1)
switch(conf-if-vl-5)# fcf forward
switch(conf-if-vl-5)# exit

4. Configure interfaces (required for each port being configured).
switch(config)# interface tengigabitethernet 0/0 Change Port ID
switch(config-if-te-0/0)# switchport
switch(config-if-te-0/0)# switchport mode access
switch(config-if-te-0/0)# vlan classifier activate group 1 vlan 5 FCoE Required (Step 3 VLAN)
switch(config-if-te-0/0)# qos flowcontrol pfc 3 tx on rx on
switch(config-if-te-0/0)# cee-map default
switch(config-if-te-0/0)# exit

5. Repeat Step 4 for each interface you are configuring.

6. Perform a port shutdown/no shutdown operation (required for each port for the configuration change to be enabled).
switch(config)# interface tengigabitethernet 0/0 Change Port ID
switch(config-if-te-0/0)# shutdown
switch(config-if-te-0/0)# no shutdown
switch(config-if-te-0/0)# exit

7. Repeat Step 6 for each interface you are configuring.

8. Save the running configuration to boot flash.
switch(config)# exit
switch# copy running-config startup-config
Overwrite the startup config file (y/n): y
Building configuration...
switch#

9. Verify that the CEE port link status and VLAN status are correct.
switch# show ip interface brief
Interface IP-Address Status Protocol
========= ========== ====== ========
TenGigabitEthernet 0/0 unassigned up up
switch#show vlan brief
VLAN Name State Ports
(u)-Untagged, (t)-Tagged
======= ================ ======= ===============================
1 default ACTIVE Te 0/0(u)…
5 VLAN0005 ACTIVE Te 0/0(u)…
switch# exit
switch:admin>

10. Verify the status of the FC and FCoE virtual FC ports.
BR8000-01:admin> switchshow
switchName: BR8000-01
(Deleted Output)
Area Port Media Speed State Proto
====================================
0 0 id N4 Online FC E-Port (Trunk port, master is Port 1 )
1 1 id N4 Online FC E-Port 10:00:00:05:1e:36:2a:70 "BR48-02" (Trunk master)
2 2 id N4 Online FC E-Port (Trunk port, master is Port 3 )
3 3 id N4 Online FC E-Port 10:00:00:05:1e:36:2a:70 "BR48-02" (upstream)(Trunk master)
4 4 id N8 No_Light FC
5 5 id N8 No_Light FC
6 6 id N8 No_Light FC
7 7 id N8 No_Light FC
8 8 -- 10 Online FCoE F-Port 5 NPIV public
9 9 -- 10 Online FCoE F-Port 4 NPIV public
10 10 -- 10 Online FCoE F-Port 4 NPIV public
11 11 -- 10 Online FCoE F-Port 4 NPIV public
12 12 -- 10 Online FCoE F-Port 3 NPIV public
13 13 -- 10 Online FCoE F-Port 2 NPIV public
NOTE:
Ports 8 through 13 are the virtual FC ports. To display the FCoE virtual FC devices connected to those ports, enter the following command for ports 8 through 13.
BR8000-01:admin> fcoe --loginshow 8 (Repeat for ports 9—13)
Number of connected devices: 4
=====================================================================================
===========================
Peer Type Connect Device WWN Device MAC Session MAC
FCoE Port MAC TE port
=====================================================================================
===========================
FCOE_DEVICE Direct 21:01:00:1b:32:20:fe:0c 00:c0:dd:0a:bb:35 0e:fc:00:04:08:04
00:05:1e:76:7b:00 Te 0/1
FCOE_DEVICE Direct 21:01:00:1b:32:20:1d:0d 00:c0:dd:0a:bd:b9 0e:fc:00:04:08:01
00:05:1e:76:7b:01 Te 0/3
FCOE_DEVICE Direct 10:00:00:00:c9:76:f2:b9 00:00:c9:76:f2:b9 0e:fc:00:04:08:02
00:05:1e:76:7b:02 Te 0/2
FCOE_DEVICE Direct 10:00:00:00:c9:76:f2:55 00:00:c9:76:f2:55 0e:fc:00:04:08:03
00:05:1e:76:7b:03 Te 0/0
BR8000-01:admin

HP C-series Nexus 5010/20 Converged Network Switch quick setup
This procedure is intended for users who are familiar with Cisco MDS FC switches and have experience merging C-series MDS FC switches into an existing MDS FC fabric. Use this procedure to enable servers with CNAs attached to the HP C-series Nexus 5010/20 Converged Network Switch to access devices on the attached C-series FC fabric.
IMPORTANT:
If you are not familiar with Cisco FC switches or you do not have experience merging C-series FC switches into an existing FC fabric, use the detailed instructions found in the switch user guide to set up your switch.
HP recommends that you use the virtual Fibre Channel (VFC) port assignments listed in Table 9.

Table 9 Recommended VFC port assignments

Model

Slot

Number of FCoE ports (l maximum)

VFC port assignments (recommended)

HP C-series  Nexus 5010 Converged Network Switch

1 (Standard)

20

VFC ports 1 through 20

2 (Optional expansion module slot1)

6

VFC ports 41 through 46

HP C-series Nexus 5020 Converged Network Switch

1 (Standard)

40

VFC ports 1 through 40

2 (Optional expansion module slot1)

6

VFC ports 41 through 46

3 (Optional expansion module slot1)

6

VFC ports 47 through 52

1Optional expansion module slots can contain either 10 GbE ports or FC ports.


In the following examples, FCoE is enabled on a C-series Nexus 5010 Converged Network Switch, VLAN 200 is created, and the Ethernet ports are bound to a virtual SAN (VSAN 2) from an 8-port FC expansion module. The commands are the same for the HP C-series Nexus 5020 Switch.
To establish CNA connectivity and enable login to the HP C-series Nexus 5000 Converged Network Switch, configure the IEEE DCB ports as follows:

1.Enable FCoE (disabled by default).

NOTE:
The C-series Nexus 5000 Converged Network Switch will require a reload (reboot).
Nexus5010# configure terminal
Nexus5010(config)# feature fcoe
Nexus5010(config)# 2009 Apr 1 12:05:06 Nexus5010 %$ VDC-1 %$ %PLATFORM-2-FC_LICENSE_DESIRED: FCoE/FC feature will be enabled after the configuration is saved followed by a reboot
Nexus5010(config)# exit
Nexus5010# copy running-config startup-config
[########################################] 100%
Packaging and storing to flash: \
Packaging and storing to flash: |
Packaging and storing to flash: /
Nexus5010# reload
WARNING: This command will reboot the system
Do you want to continue? (y/n) [n] y
The system is going down for reboot NOW!

2. Create a new VLAN for FCoE.
By default, all ports are in VLAN 1, however, you must use a different VLAN for FCoE. In the following example, VLAN 200 is created with access to Ethernet ports 1/1 to 1/20, and VFC ports 1–20 are also created.
NOTE:
In the last section of this example, 1/1-20 indicates that the commands that follow apply to multiple ports (in this case, ports 1/1 through 1/20). All 20 ports are set for switchport mode trunk, and switchport trunk allowed is set for VLANs 1 and 200.
Nexus5010# configure terminal
Nexus5010(config)# vlan 200
Nexus5010(config-vlan)# exit
Nexus5010(config)# exit
Nexus5010# show vlan brief
VLAN Name Status Ports
---- -------------------------------- ------- -------------------------
1 default active Eth1/1, Eth1/2, Eth1/3,
Eth1/4, Eth1/5, Eth1/6,
Eth1/7, Eth1/8, Eth1/9,
Eth1/10, Eth1/11, Eth1/12,
Eth1/13, Eth1/14, Eth1/15,
Eth1/16, Eth1/17, Eth1/18,
Eth1/19, Eth1/20
200 VLAN0200 active
Nexus5010# configure terminal
Nexus5010(config)# interface ethernet 1/1-20
Nexus5010(config-if-range)# switchport mode trunk
Nexus5010(config-if-range)# switchport trunk allowed vlan 1, 200
Nexus5010(config-if-range)# interface vfc 1-20
Nexus5010(config-if-range)# exit

3. Create a new VSAN that includes the FC and VFC ports.
By default, all ports are in VSAN 1. HP recommends that you use a different VSAN for SAN connectivity. In this example, VSAN 2 is created and includes FC ports 2/1 through 2/8 and VFC ports 1 through 20.

NOTE:
VFC ports must be FCoE ports. FC ports cannot be VFC ports.
Nexus5010(config)# vsan database
Nexus5010(config-vsan-db)# vsan 2
Nexus5010(config-vsan-db)# vsan 2 interface fc2/1-8
Nexus5010(config-vsan-db)# vsan 2 interface vfc 1-20
Nexus5010(config-vsan-db)# exit
Nexus5010(config)# exit
Nexus5010# show vsan membership
vsan 1 interfaces:
vsan 2 interfaces:
fc2/1 fc2/2 fc2/3 fc2/4 fc2/5 fc2/6 fc2/7 fc2/8
vfc1 vfc2 vfc3 vfc4 vfc5 vfc6 vfc7 vfc8
vfc9 vfc10 vfc11 vfc12 vfc13 vfc14 vfc15 vfc16
vfc17 vfc18 vfc19 vfc20
vsan 4094(isolated_vsan) interfaces:
4. Associate the VLAN with the VSAN.
In this example, VLAN 200 is associated with VSAN 2.
Nexus5010# configure terminal
Nexus5010(config)# vlan 200
Nexus5010(config-vlan)# fcoe vsan 2
Nexus5010(config-vlan)# exit
Nexus5010(config)# exit
Nexus5010# show vlan fcoe
VLAN VSAN Status
-------- -------- --------
200 2 Operational

5. Bind each VFC port to a unique Ethernet port by issuing the following commands on each port:
• interface vfc n
• bind interface ethernet slot/port
• exit

NOTE:
Depending on your switch, up to 52 VFC ports may be available.
In Example 1, VFC ports 1 through 8 are created and are bound to Ethernet ports 1/1 through 1/8, respectively. Example 2 shows a more complex configuration in which the VFC ports are not sequential.
Example 1. Creating and binding consecutive VFC ports
Nexus5010# configure terminal
Nexus5010(config)# interface vfc 1
Nexus5010(config-if)# bind interface ethernet 1/1
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 2
Nexus5010(config-if)# bind interface ethernet 1/2
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 3
Nexus5010(config-if)# bind interface ethernet 1/3
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 4
Nexus5010(config-if)# bind interface ethernet 1/4
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 5
Nexus5010(config-if)# bind interface ethernet 1/5
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 6
Nexus5010(config-if)# bind interface ethernet 1/6
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 7
Nexus5010(config-if)# bind interface ethernet 1/7
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 8
Nexus5010(config-if)# bind interface ethernet 1/8
Nexus5010(config-if)# exit
Nexus5010(config)# interface vfc 1-8
Nexus5010(config-if)# no shutdown
Nexus5010(config-if)# exit

IMPORTANT:
Example 2 is provided for reference only. It shows an alternate method of performing this step.
In Example 2, VFC ports 1 through 6, 10, and 20 through 25 are created, and each VFC port is bound to an Ethernet port. Because the VFC ports are not sequential, multiple interface vfc commands are required.
Example 2. Creating and binding nonconsecutive VFC ports
Nexus5020# configure terminal
Nexus5020(config)# interface vfc 1
Nexus5020(config-if)# bind interface ethernet 1/1
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 2
Nexus5020(config-if)# bind interface ethernet 1/2
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 3
Nexus5020(config-if)# bind interface ethernet 1/3
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 4
Nexus5020(config-if)# bind interface ethernet 1/4
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 5
Nexus5020(config-if)# bind interface ethernet 1/5
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 6
Nexus5020(config-if)# bind interface ethernet 1/6
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 10
Nexus5020(config-if)# bind interface ethernet 1/10
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 20
Nexus5020(config-if)# bind interface ethernet 1/20
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 21
Nexus5020(config-if)# bind interface ethernet 1/21
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 22
Nexus5020(config-if)# bind interface ethernet 1/22
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 23
Nexus5020(config-if)# bind interface ethernet 1/23
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 24
Nexus5020(config-if)# bind interface ethernet 1/24
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 25
Nexus5020(config-if)# bind interface ethernet 1/25
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 1-6
Nexus5020(config-if)# no shutdown
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 10
Nexus5020(config-if)# no shutdown
Nexus5020(config-if)# exit
Nexus5020(config)# interface vfc 20-25
Nexus5020(config-if)# no shutdown
Nexus5020(config-if)# exit

6. Enable the FC ports.
In this example, FC ports 2/1 through 2/8 are enabled.
Nexus5010(config)# interface fc 2/1-8
Nexus5010(config-if)# no shutdown
Nexus5010(config-if)# exit
Nexus5010(config)# exit

7. Copy the running configuration to the startup configuration location.
Nexus5010# copy running-config startup-config
[########################################] 100%

8. Copy the running configuration to a Glossary Link backup location.
Nexus5010# copy running-config ftp://10.10.20.1/backup.txt


Glossary of terms:
3PO - third-party option
CEE - converged enhanced Ethernet
CN - converged network
CNA - converged network adapter
DCB - Data Center Bridging
EoR - End of Row (switch)
FC - Fibre Channel
FCoE - Fibre Channel over Ethernet
FIP - FCoE Initialization Protocol
FOS - Fabric Operating System (Brocade)
FPMA - Fabric Provided Mac Addressing
IOS - Internetwork Operating System (Cisco)
ISL - interswitch link
LLDP - Link Layer Discovery Protocol
NIC - network interface card
RHEL - Red Hat Enterprise Linux
RU - rack unit
SAN - storage area network
SAN-OS - SAN Operating System (Cisco)
SFP+ - small form-factor pluggable, plus (transceiver)
SLES - SUSE Linux Enterprise Server
ToR - Top of Rack (switch)
unified fabric - IEEE DCB enabled network (Cisco)
VFC - virtual Fibre Channel
VLAN - virtual LAN

Read more... Add new comment
 
HP EVA Installation and setup example (Part 1)
In the first part of HP EVA Installation and setup example you can find foloving information:
Overview
Introduction to vRAID
Array structures
Glossary Link Disk group initialization
Installation Command View EVA
Read more... Add new comment
 
HP EVA Installation and setup example (Part 2)
In this chapter we continue previous part with installation and setup example of HP EVA with following paragraphs:
Power on the array
Array initialization
Read more... Add new comment
 
HP EVA Installation and setup example (Part 3)
In this chapter we continue previous part with installation and setup example of HP EVA with Glossary Link disk group and LUN creation example.
Read more... Add new comment
 
HP EVA Installation and setup example (Part 4)
 
In this chapter we continue previous part with installation and setup example of HP EVA Glossary Link disk array with adding hosts and Vdisks presentation examples.
Read more... Add new comment
 
Configuring HP Blade Enclosure с7000 with scripts (Part 1)
 
In this paragraph we will show example how to set configure HP Onboard Administrator of HP Blade Enclosure с3000\7000 with scripts, how to Glossary Link backup configuration with scripts.
Read more... Add new comment
 
Configuring HP Blade Enclosure с7000 with scripts (Part 2)
 
In this part we will show you example how to get information from the HP Blade Enclosure с7000 via Onboard Administrator.
Read more... Add new comment
 
More Articles...


All Rights Reserved 2012 http://www.fcoe.ru/

При копировании материалов, пожалуйста,
ставьте прямую ссылку на источник. Уважайте чужой труд.
 

designed by joomlafabric.com