Brocade

EIS Installation Checklist for SAN Switch (Brocade 300)

Customer

Sun Order Number:

CASE Number:

Technician:

Version EIS-DVD:

Date:

• It is recommend that the EIS web pages are checked for the latest version of this checklist prior to commencing the installation.

• It is assumed that the installation is carried out with the help of the currentEIS-DVD. See EIS web pages for current information and status.

• The idea behind this check list is to help the installer achieve a "good" installation.• It is assumed that the installer has attended the appropriate training classes.• If a Solaris host is used, it is assumed that Solaris 8 04/01 or above is used. Also,

if Solaris 8 & 9 are used, the SAN Foundation Suite (SFS) plus patches have been installed from the EIS-DVD.

• It is not intended that this checklist be handed over to the customer.• This switch is capable of Access Gateway mode. To enable/configure, please see

the Access Gateway Administrators guide located on the Brocade Partner site. (http://partner.brocade.com).NOTE: Access Gateway mode is only supported in 24-port configurations.

• Brocade USB Flash Drives are available to backup configuration and switch logs.SUN FRU: F373-0365-01.

SWITCH Serial# DomainID

Task Comment Check

PREPARATION

Site Audit complete? "Site Audit" document.

Configuration fixed and documented?

System-Preparation complete?

Review latest FIN/FCO information See EIS-web “Installation URLs”

Verify supported configuration • SunWIN #397802 “SAN 4.4 WWWW”

• SunWIN #344150 Sun StorEdge 99X0 Specific (if SE99X0 connected to the SAN).

Statement-of-Installation signed? SunWIN #359852 “SAN Cookbook”

Sun Internal and Approved Partners Only Page 1 of 10 Vn 1.0 Created: 21 May 08

http://partner.brocade.com/




Task Comment Check

UNPACKING

Delivery complete?

Collect all software CDs. Store carefully!

Allow the system to acclimatise (power off) at the customer site.Unpack outside data center to ensure no contamination/dust is released inside customer's controlled environment.

Refer to EIS standard “Acclimatisation of Sun Servers & Storage”

Collect packing material together for disposal.

Verify all packing material has been removed, i.e. nothing is blocked.

Fans & air vents must be free to operate.

Collect documentation CDs. Give to customer during handover.

ASSEMBLY

Note down the serial numbers. The serial number is in front of the switch.

Mount switch in rack, if applicable. Use Brocade Installation and Service Manual.

Provide power to the switch. Note that the customer's electrician is responsible for connecting the power lines to the in-house power grid.

Power on the switch and wait for completion.


Task Comment Check

CONFIGURING SWITCH NETWORKING SETTINGS

Establish serial console session via switch serial port.

# tip -9600 /dev/term/a

Login to switch.

Change all passwords as prompted by the switch at First login.

login:adminPasswd:password

Change passwords as follows:

adminPassword: Customer assigned

rootPassword: fibranne (Sun Internal Only)

factoryPassword: password (Sun Internal Only)

userPassword: Customer assigned

Assign IP address, netmask and gateway information to switch.

:admin> ipAddrSet(FC IP and netmask are optional)For syntax information, type “help ipAddrSet”

Verify switch networking information.

:admin> ipaddrshow

Reboot switch and end serial console session.

:admin> reboot:admin> exitEnsure switch POST completes successfully<Enter> ~. OR CTRL ] + quit

UPGRADING SWITCH FIRMWARE

Start a telnet session to the switch. # telnet <ipaddressofswitch>

Check switch's firmware version. :admin> version:admin> firmwareshow

Determine if switch firmware upgrade is necessary.

EIS-DVD: .../sun/patch/SAN-SWITCH:Patch ID: 1381481 Brocade FOS v6.1.0 patch for 200e 300 4100 4900 5000 5100 5300 7500 48000 DCX

Refer to SunWIN #397802 “SAN 4.4 WWWW” for latest information on supported firmware!

Upgrade switch firmware if required as per instructions in the patch README file.

:admin> help firmwaredownload:admin> firmwaredownload

Only required for SW3200/SW3800 switches:Reboot switch to activate new firmware.

:admin> reboot

Verify new firmware version after switch reboot.

:admin> version:admin> firmwareshow

CONFIGURING SWITCH BASIC PARAMETERS

Set the switch name. :admin> switchname “<nameofswitch>”

Set date and time. :admin> date <mmddhhmmyy>

1 Patch 138148-xx is on EIS-DVD ≥27MAY08.


Task Comment Check

Set time zone as per customer requirements.

:admin> help tstimezone]examples::admin> tstimezone -8,0(ie GMT-0800):admin> tstimezone +3,0(ie GMT+0300)

Set NTP server. :admin> help tsclockserver:admin> tsclockservser <ipaddrofserver>

Review switch license information and add additional license if necessary.

For SW200E/SW4100/SW4900, verify additional Fibre Channel port licensing if necessary.

:admin> licenseshow:admin> licenseadd <license-key>

Set Fabric Watch default temperature thresholds IF “Fabric Watch license” installed.

Reasonable data center environmental temperature range should be used to allow fabric watch alerts to be triggered.

:admin> fwconfigure1 : Environment classSelect a class => : (1..12) [12] 11 : TemperatureSelect an area => : (1..4) [4] 14 : advanced configurationSelect choice => : (1..5) [5] 43 : change threshold boundary levelSelect choice => : (1..19) [19] 32 : customEnter boundary level type => : (1..2) [2] 6 : change custom lowSelect choice => : (1..19) [19] 6Enter low threshold => : (-999999999..999999999) [0] <enter low value>7 : change custom highSelect choice => : (1..19) [19] 7Enter high threshold => : (-999999999..999999999) [64] <enter high value>19 : return to previous pageSelect choice => : (1..18) [18] 185 : return to previous pageSelect choice => : (1..5) [5] 54 : return to previous pageSelect an area => : (1..4) [4] 412 : QuitSelect a class => : (1..12) [12] 12

Enable syslog to host.

By default, all switch messages will be logged to loghost's /var/adm/messages file once syslogipadd is completed. Reference help pages of syslogipadd to edit loghost server's/etc/syslog.conf to filter switch messages to specific files on loghost server.

:admin> syslogdipshow:admin> help syslogdipadd:admin> syslogdipadd <ipaddrofserver>

CONFIGURING SWITCH FABRIC PARAMETERS


Task Comment Check

Disable switch to change fabric parameters.

:admin> switchdisable:admin> configureConfigure...

Fabric parameters (yes, y, no, n): [no] y

Set DomainID for switch.(Assign unique number for each switch in the SAN)

Domain: (1..239) [1]

Set VC Encoded Address Mode• 0 = Disable

• 1 = Enable

All switches in the SAN must use the same VC Encoded Address Mode setting to avoid fabric segmentation.

When enabled, switch utilises an address format compatible with some first-generation switches (1000 series switches). This mode is not compatible with Native PID, Core PID, or Extended PID. When disabled, Core PID is default value for Switch PID Format.

VC Encoded Address Mode: (0..1) [0](Only available in 3.x firmware switches)


Task Comment Check

Set switch PID format (all switches connecting to same SAN must use the same PID format).

0. Native PID Format (16 based, 16 port format), for fabrics with legacy low count port switches (switches with 16 ports or less).

1. Core PID Format (0 based, 256 port format), preferred mode for mixed fabrics with legacy and new switches. PID values will change when migrating from Native PID Format.

2. Extended Edge PID Format (16 based, 256 port format), used in mixed fabrics with legacy and new switches to avoid need to reboot host systems when static PID zoning (port zoning) is used. PID values will remain unchanged when migrating from Native PID Format.

If installing switch into a new SAN, then use Core PID. Otherwise if switch is joining a pre-existing SAN, then use PID format of pre-existing SAN switches.

In SAN environments migrating from Native PID to Core PID to support switches with greater than 16 ports, PIDs will change affecting configurations implementing port zoning using PID. To avoid re-zoning with new PIDs and any subsequent host reboots, consider using Extended Edge PID Format so that PID values are not changed from Native PID Format and still get support for switches with greater than 16 ports.

N/A

FOS 6.0.0 and higher only supports Core PID or PID 1

Take default settings for all other fabric parameters unless SAN environment requires custom settings.

<snip>R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] <snip>

Enable switch to activates fabric parameter changes.

:admin> switchenable

Clear any stale, conflicting zoning configurations to prevent fabric segmentations when introducing new switch to existing SAN.Skip if planning to merge zoning configurations.

:admin> cfgshow:admin> cfgdisable:admin> cfgclear:admin> cfgsave


Task Comment Check

CABLING

Install SFPs (Small Form-Factor Plugables).

Attach FC cables to switch in following order:1. ISL connections, THEN2. Host/storage connections.

CONFIGURING SWITCH ZONES

Verify all host HBAs and storage devices are connected to switch.

:admin> switchshow:admin> nsshow:admin> nscamshow

Method#1:Configure Zones via Switch Explorer's zone administrator utility.

http://<ipaddressofswitch>(Mozilla 1.4 or higher with Java Plugin 1.4.2 required for FOS v3.1.2x/4.2.0x, ensure Pop-Ups are enabled)Click on "Zone Admin" button (very small icon on lower left corner)

Method#2:Configure Zones via telnet session

#telnet <ipaddressofswitch>login: adminpassword: password

Reference customer requirements, latest SAN 4.x WWWW matrix, and SAN Cookbook for best practices in implementing proper zoning configurations.

See zonehelp help pages for command usage on creating aliases, zones, and zone configurations.

:admin> zonehelp

Save and enable zoning configuration. :admin> cfgsave:admin> cfgenable <cfgname>

Verify active zones. :admin> cfgshow

Ensure that committed zone database is not nearing “Zone DB max size”.

:admin> cfgsizeZone DB max size - 127726 bytes committed - 1609 transaction - 0

Backup switch zoning configuration. :admin> help configupload:admin> configupload

Archive critical switch settings, parameters, and configurations for recovery or troubleshooting.

On host server:# script /var/tmp/supportshow.out# telnet <ipaddressofswitch>login:adminpassword: password:admin> supportshow<lots of output>:admin> exit# <cntrl-D>

The output from supportshow is stored in file /var/tmp/supportshow.out.


Task Comment Check

FOR SUN/SPARC SERVERS WITHOUT SERVERSTART (Existing Host)

These steps are only required if the switch is being added to an existing server, since a newly-installed server (using the appropriate EIS checklist) will avoid the issues below.

Insert EIS-DVD into each host & run the setup-standard script:cd ...sun/installsh setup-standard.sh

Ensure that any missing SFS (San Foundation Suite) packages are installed by setup-standard.

Ensure that current explorer etc. are available.

Verify that the Solaris & SAN patches are current.

Run SRAS/CLI from EIS-DVD on a current explorer. If SRAS/CLI shows missing/downrevved patches then consider scheduling patch update as below.

If necessary, update the Solaris & SAN patches from the EIS-DVD and reboot.

The SAN patches are only separate for Solaris 8 & 9 – for Solaris 10 the SAN patches are part of the Solaris set.

This assumes that a scheduled shutdown of the host is possible.

Solaris patches: .../sun/patch/<Vn>.

Patches for SFS from EIS-DVD:• Solaris 8 & 9: .../sun/patch/SAN• Solaris 8: .../sun/patch/SAN/8• Solaris 9: .../sun/patch/SAN/9

Task Comment Check

ACTIONS FOR SOLARIS SERVER ONLY (both new & existing host)

If new host (with ServerStart) it is assumed that the SAN Foundation Suite (SFS) plus patches has been installed from the EIS-DVD.

Verify HBA Fcode is at required level.

Fcode patches are on EIS-DVD in ...sun/patch/firmware/FCODES.

See also file HBA.txt in same directory.

luxadm fcode -p

Verify that the OS can see the Target devices.

# cfgadm -al# cfgadm -al -o show_FCP_dev

Configure access to the relevant targets. # cfgadm -c configure c [number(s)]

Review the dimensions and label if necessary.

# format


Task Comment Check

SOLARIS HOST VERIFICATIONPERFORM ONLY here for ArrayStart without ServerStart

Run explorer with the instinfo option (see relevant server checklist).

Refer also to Technical Instruction 209663 for importance of explorer data.

Run SRAS/CLI (from EIS-DVD) locally to analyse the explorer data.

cd /sun/tools/SRASsh run-sras.sh

Examine the results.If necessary repair & repeat explorer/SRAS sequence.

Examine the resulting report:

cd /var/tmp/SRASmore *EIS.Report.txt

Mail explorer file to:EMEA: [email protected]: [email protected]: [email protected]

The explorer output file is normally in directory /opt/SUNWexplo/output with filename explorer.<hostid>.<hostname>-<date>.tar.gz

If e-mail from customer site not possible please transport file to Sun office & send the e-mail from there.

VERIFICATION – Perform Always

Connectivity verification. Connected LED are on.

LUN verification. LUN(s) have been seen by the OS.

Fail-over testing (for pair of switches only).

Defined in the delivery documentation.

INSTALLATION COMPLETION

Complete documentation and hand over to customer.

Obtain customer sign-off for service completion.

Copies of the checklists are available on the EIS web pages or on the EIS-DVD. We recommend that you always check the web pages for the latest copy.

The EIS checklists are located Sun-internally at http://EIS/checklists or here for accredited Partners.

Comments & RFEs are welcome. Please use ServiceDesk (Search Problem/Service & enter "EIS")or mail to [email protected] if no SWAN access available – typically for a partner.


https://spe.sun.com/icaccess/control/DocumentSelectByType/doc=1638/checklists/checklists.html

http://EIS/checklists

Documents

Brocade