HP StorageWorks

Fabric OS 5.1.0brelease notes

Part number: AA-RWEEB-TEFirst edition: June 2006

Legal and notice information

© Copyright 2006 Hewlett-Packard Development Company, L.P.-NaN

The information contained herein is subject to change without notice. The only warranties for HP products and services areset forth in the express warranty statements accompanying such products and services. Nothing herein should be construedas constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

Version5.1.0b

DescriptionFabric OS 5.1.0b supports new enhancements and fixes found in previous releases, andadds support for new standalone platforms; the HP StorageWorks 4/64 SAN Switch,the HP StorageWorks 400 Multi-protocol Router, and the new B-Series Multi-protocolRouter blade for the HP StorageWorks 4/256 SAN Director.

In this release, HP delivers the first 4-Gbit/sec FC routing and FC-IP blade, which iscompatible with our HP StorageWorks 4/256 SAN Director installed base. Routing withlogical SAN (LSAN) enables secure selective sharing of resources between isolatedSANs and introduces new features around FC-IP. Each physical GbE port supports up toeight virtual tunnels and has dedicated hardware for line speed compression.

The B-Series Multi-protocol Router blade is also “encryption ready,” so that encryptionat line speed can be enabled in a future Fabric OS release. With this release, theHP StorageWorks 4/256 SAN Director is the industry’s first and only Fibre ChannelDirector that provides 4-Gbit/sec port speeds, exceptional performance and scalability,and up to 256 ports in a single domain. This high-performance architecture providesauto-speed negotiation to support legacy 1- and 2-Gbit/sec server and storage devicesas well as 4-Gbit/sec devices.

Trunking support for an aggregate of up to eight 4-Gbit/sec ports creates an Inter-SwitchLink (ISL) trunk up to 32 Gbit/sec of bandwidth. Fully compatible with existing HPStorageWorks storage offerings, the highly flexible blade format of the 4/256 SANDirector provides “pay-as-you-grow” scalability and support for multiple protocols andtransports.

Update recommendationHP strongly recommends that users upgrade to Fabric OS 5.1.0b as soon as possible.

Supersedes historyFabric OS 5.1.0 released in April, 2006

Effective dateJune, 2006

Fabric OS 5.1.0b 3

Supported product models• HP StorageWorks 4/8 SAN Switch or HP StorageWorks 4/16 SAN Switch

(SilkWorm 200E)• HP StorageWorks 4/64 SAN Switch (SilkWorm 4900)• HP StorageWorks 400 Multi-protocol Router (SilkWorm 7500)• B-Series Multi-protocol (MP) Router blade for the HP StorageWorks 4/256 SAN

Director (SilkWorm FR4-18i blade for the SilkWorm 48000 Director)• HP StorageWorks SAN Switch 2/8V (SilkWorm 3250)• HP StorageWorks SAN Switch 2/16V (SilkWorm 3850)• HP StorageWorks SAN Switch 2/32 (SilkWorm 3900)• HP StorageWorks SAN Switch 4/32 (SilkWorm 4100)• HP StorageWorks SAN Director 2/128 (SilkWorm 24000 Director)• HP StorageWorks 4/256 SAN Director (SilkWorm 48000 Director)• HP StorageWorks Multi-protocol (MP) Router (SilkWorm AP7420)

Unsupported product models• HP StorageWorks Core Switch 2/64 (SilkWorm 12000)• Brocade 4Gb SAN Switch for HP p-Class BladeSystem (SilkWorm 4012)• Brocade 4Gb SAN Switch for HP c-Class BladeSystem (SilkWorm 4024)• HP StorageWorks MSA SAN Switch 2/8 (SilkWorm 3000)

Devices supportedSee the HP StorageWorks SAN design reference guide for supported devices:http://h1800.www1.hp.com/products/storageworks/san/documentation.html.

Operating systemsSee http://www.hp.com for a list of supported operating systems.

4

EnhancementsThis section describes Fabric OS 5.1.0b enhancements.

HP StorageWorks 4/8 SAN Switch or HP StorageWorks 4/16SAN Switch

The Extended Fabrics feature in Fabric OS 5.1.0b is now supported on the 4/8 SANSwitch and 4/16 SAN Switch. Customers must purchase the optional Extended Fabricssoftware license to use this feature. When enabled, Extended Fabrics supports distancesover 100 km at 2 Gbit/sec. Trunking over distance also is supported.

Chassis configuration optionsSimilar to previous Fabric OS releases, the SAN Director 2/128 and 4/256 SANDirector chassis running Fabric OS 5.1.0b is assigned a chassis option by the user,which determines the number of domains (logical switches) on the chassis (supportedonly on the SAN Director 2/128). The B-Series MP Router blade is supported only usingchassis option 5, which is the default setting on the 4/256 SAN Director.

Chassis configuration options 3 and 4 are obsolete; if you attempt to upgrade to FabricOS 5.1.0b with chassis options 3 and 4 enabled, the upgrade will fail. With chassisoptions 3 and 4, one half of the Director chassis has Core Switch 2/64 port blades andthe other has SAN Director 2/128 port blades with SAN Director 2/128 CPs.

Device-based routing is obsolete; it was made available in Fabric OS 5.0.1 for the SANSwitch 4/32 and the 4/256 SAN Director. If device-based routing is enabled, theupgrade to Fabric OS 5.1.0b will fail. You can change the type of routing using theaptPolicy command.

The aptPolicy command enables you to configure which egress port is selected for anexchange, based on a particular policy:

• Port-based path selection (paths are chosen based on ingress port and destinationonly). This also includes user-configured paths. This is required for FICON.However, HP does not support FICON in this release of Fabric OS 5.1.0bfirmware. See http://www.hp.com for a list of currently supported features.

• Exchange-based path selection (paths are chosen based on SID, DID, and OXID).This is the default and recommended setting for all non-FICON environments.

IMPORTANT:For the 4/256 SAN Director, the aptPolicy command will not be available, unlessthe chassis has been configured to run using option 5 described in 4/256 chassisconfiguration options.

Fabric OS 5.1.0b 5

Table 1 4/256 SAN Director chassis configuration options

Option Numberofdomains

Maxportsperswitch

Routingmodule

Sup-portedCPs

Supportedportblades

Implicationsand notes

1 1 128 CER CP2 orCP4

FC2-16,FC4-16

CP4 will befaulted ifinserted intoa UniversalChassis

2 2 64/64 CER/CER

CP2 only FC2-16 only

5 1 256 RTE CP4 only FC4-16,FC4-32,B-SeriesMP Routerblade

CP4 will befaulted ifinserted intoa UniversalChassis

Legend

CER = Core Edge Routing. Port-based routing scheme, same as routing option supportedin Fabric OS 4.2.0 and 4.4.0

RTE = Advanced Routing. Exchange-based (default) or port-based routing scheme

CP2 = SAN Director 2/128 CP blade

CP4 = 4/256 SAN Director CP blade

FC2-16 = 2G, 16-port blade

FC4-16 = 4G, 16-port blade

FC4-32 = 4G, 32-port blade

B-Series MP Router blade = 4G, 16+2 routing blade

ZoningSupport for Default Zoning policies have been added to Fabric OS 5.1.0b. Typically,when you issue the cfgDisable command in a large fabric with thousands of devices,the name server indicates to all hosts that they can communicate with each other.To ensure that all devices in a fabric do not see each other during a cfgDisableoperation, you can activate a Default Zone with policy set to “no access”. If Defaultzoning policies are enabled, all cfgEnable/Disable commands and zoning changesmust be run from a switch in the fabric running Fabric OS 5.1.0b.

6

Fabric scalabilityFabric OS 5.1.0b supports the same fabric scalability as Fabric OS 5.0.1, that is,2,560 ports with 50 domains.

Security-related enhancementPassword aging, password enforcement, and password strength/history has been addedto Fabric OS 5.1.0b.

Fabric OS prerequisites and requirementsTable 2 summarizes current Fabric OS firmware versions. These are the earliestrecommended software versions that interoperate; however, HP recommends using thelatest supported software release versions to get the most benefit from the SAN.

CAUTION:HP does not support upgrades from more than two previous releases. For example,upgrading from Fabric OS v4.4.0 to v5.1.x is supported. However, upgrading from FabricOS v4.2.0 or a previous release directly to v5.1.x is not. Upgrading a switch from FabricOS v4.2.0 or earlier to v5.1.0 requires a two-step process: first upgrade to v4.4.0 orv5.0.1 and then upgrade to v5.1.0.

For a list of retired products, visit the following HP web site:

http://h18004.www1.hp.com/storage/retiredproducts.html?jumpid=reg_R1002_USEN

Fabric OS 5.1.0b 7

Table 2 Current supported Fabric OS versions

Model Earliestcompatibleversion

Secure Fabric OSenabled

Recommended version

HP StorageWorks 1 Gb 2.6.1 2.6.1 or later Fabric OS 2.6.2d

HP StorageWorks SAN Switch 2/8-EL,HP StorageWorks SAN Switch 2/16,MSA SAN Switch 2/8

3.1.0 3.2.1 or later 3.2.0a

HP StorageWorks SAN Switch 2/8V,HP StorageWorks SAN Switch2/16V, HP StorageWorksSAN Switch 2/32,HP StorageWorks SAN Director2/128

4.1.0 4.2.0 or later 5.1.0b or later

HP StorageWorks 4/8 SAN Switch4/16 SAN Switch, HP StorageWorks4/256 SAN Director

5.0.3b 5.0.1 or later 5.1.0b or later

HP StorageWorks 4/64 SAN Switch 5.1.0 5.1.0b or later 5.1.0b or later

HP StorageWorks B-series MP RouterBlade, HP StorageWorks 400MP Router

5.1.0b 5.1.0b or later 5.1.0b or later

HP StorageWorks SAN Switch 4/32 5.0.3b 5.0.1 or later 5.1.0b or later

HP StorageWorks MP Router XPath OS 7.4.1

Brocade 4Gb SAN Switchfor HP p-Class BladeSystem,HP StorageWorks Core Switch 2/64

5.0.1d 5.0.1 or later 5.0.3b

Brocade 4Gb SAN Switch for HPc-Class BladeSystem

5.0.5 5.0.5 or later 5.0.5 or later

Fabric Manager Fabric Manager 5.1.x

IMPORTANT:The B-Series MP Router blade (for use with the 4/256 Director only) must run FabricOS 5.1.0b or later. Please note, the Core Switch 2/64 does not support the B-SeriesMP Router blade.

8

Firmware updatesTo access the latest Fabric OS 5.1.0b firmware, configuration files and MIB files go tothe following HP web site:

NOTE:Some product web pages may use slightly different links.

http://www.hp.com/country/us/eng/prodserv/storage.html

To download:

1. Locate the IT storage Products section of the web page.

2. Under Networked storage, click SAN Infrastructure.

3. From the SAN Infrastructure web page, locate the SAN Infrastructure productssection.

4. Depending on your product, click Fibre Channel Switches or Multi-protocol Routers& Gateways.

5. To access Fabric OS 5.1.0b firmware and supporting files, click the appropriateB-Series product. The product overview page displays.

6. Go to the Product information section, located on the far right side of the web page.

a. Go to the Tasks for HP StorageWorks... product section. Select Downloaddrivers and software.

b. Go to the Select your product section. Select the appropriate product.

c. Go to the Select operating system section. Select Cross operating system (BIOS,Firmware, Diagnostics, etc.)

d. Scroll to the Firmware section of the web page and select the appropriatefirmware version.

e. Click the appropriate product description and then Installation Instructions forfirmware install instructions.

f. Click the Download button and follow the prompts in the File Download dialogbox.

Fabric OS 5.1.0b 9

Important notesThe following sections list important notes.

Fabric OS 5.1.0a — not released or supportedPlease note that HP never released Fabric OS 5.1.0a. All fixes that occurred in FabricOS 5.1.0a are included in this current Fabric OS 5.1.0b firmware release.

B-Series MP Router blade and 400 MP RouterThe B-Series MP Router blade for the 4/256 SAN Director provides a number of newfeatures, such as compression, multi-tunnel support, and encryption readiness. It providessixteen 4- Gbit/sec FC routing ports and 2 GbE ports for FC-IP support and LSANsupport enabled by HP’s FC-FC Routing Service. Note the following:• The B-Series MP Router blade works only with chassis configuration option 5, as

described in 4/256 chassis configuration options.• The B-Series MP Router blade provides up to eight virtual tunnels per physical GbE

port.• Compression is turned off by default and can be enabled on a per tunnel basis.• Do not install a B-Series MP Router blade into a 4/256 SAN Director before the

Director is upgraded to Fabric OS v5.1.0b.• Secure Fabric OS is not supported in the backbone fabric.

The 400 MP Router, second generation of the MP Router, now integrates sixteen4-Gbit/sec FC routing ports and two GbE routing ports (VE_Ports and VEX_Ports) forsuperior FC-IP capabilities. FC-IP features include multi-tunnel support, compression, andencryption readiness. The 400 MP Router is a 1U standalone unit with N+1 powersupplies and fans. The routing capabilities are now part of Fabric OS v5.1.0b for tightintegration with the HP StorageWorks family. The 400 MP Router offers the standardFabric OS features and new and improved LSAN routing and FC-IP capabilities.

Both the B-Series MP Router blade and the 400 MP Router share the same hardware andhave exactly the same feature set, that is, 18 physical ports:

• Sixteen FC ports, which can be configured as routing ports or have layer-2,4-Gbit/sec FC capabilities.

• Two GbE ports, which are labeled “GE0” and “GE1,” can have up to eight virtualtunnels each with VE_Port or VEX_Port capabilities. Since they are IP ports andhave different capabilities, there are noticeable differences, summarized next.

10

CAUTION:When the first generation HP StorageWorks MP Router is present in the metaSAN,you must deactivate the Platform Database on all other switches in the SAN usingmsPLMgmtDeactivate.

Port typesThe B-Series MP Router blade and the 400 MP Router support the following port types:

• FC ports—F_Port, FL_Port, E_Port, and EX_Port• GbE ports—VE_Port and VEX_Port (virtual E_Port and EX_Port)

F_Ports, FL_Ports, E_PortsThere are sixteen regular 4-Gbit/sec F_Ports, FL_Ports, and E_Ports, with the same levelof support as in previous releases:

• Frame-level trunking (not supported for EX_Ports in Fabric OS 5.1.0b, DPS will beautomatically used for load balancing)

• Speed settings (1 Gbit/sec, 2 Gbit/sec, 4 Gbit/sec, and Auto)• Long distance (VC_RDY)• L_Port lockdown• G_Port lockdown• ISL R_RDY mode

EX_PortsEX_Ports connect a Router to an edge fabric. If you consider a switch in an edge fabric,an EX_Port is virtually indistinguishable from an E_Port and follows FC standards as doall other HP E_Ports. However, the Router terminates EX_Ports rather than allowingdifferent fabrics to merge as would happen on a switch with regular E_Ports. EachEX_Port presents a set of translation phantom domains representing remote fabrics, eachphantom domain with “attached” proxy devices representing devices on those fabrics.

If a port is configured as an EX_Port:

• Frame-based trunking, which is typically enabled automatically or configuredmanually using the portCfgTrunkPort command, is not supported.

• However, Dynamic Path Select (DPS), or exchange-based load-balancing, issupported on equal cost links whether they are E_Ports, EX_Ports, VE_Ports, orVEX_Ports. (Note that you can disable DPS using the aptPolicy command.)

Fabric OS 5.1.0b 11

NOTE:You cannot connect the E_Port of a switch running Fabric OS v2.x to an EX_Port on anHP StorageWorks 400 MP Router or B-Series MP Router blade.

GbE_portsSeveral new commands have been added to support GbE_Ports and several existingcommands will not work with the GbE_Ports (see “Unsupported Commands”).Frame-based trunking is not supported over GbE_Ports, but DPS (exchange-basedloadbalancing) is supported and is always on. GbE_Ports or tunnels are as long asthe cost paths are the same. (Note that you can disable DPS using the aptPolicycommand.)

GbE_Port features include:

• The GbE_Ports are set to 1-Gbit/sec speed and duplex settings cannot bechanged.

• Neither Fabric Watch nor Advanced Performance Monitoring is supported onGbE_Ports, nor are they supported on the virtual tunnel VE_Ports and VEX_Ports.

• For each FC-IP tunnel, two TCP connections are established between the endpoints. The first, running at TCP port, 3225 carries all Fibre Channel Class F(control) traffic. The second, running on TCP port 3226, carries all Fibre ChannelClass 2 and 3 (data) traffic.

VE_Ports and VEX_Ports (over GbE)VE_Ports and VEX_Ports are virtual ports (that represent each FC-IP tunnel, up to eight perGbE_Port) over the physical GbE link. VE_Ports are essentially tunneled E_Ports over anIP network via FC-IP. VEX_Ports are routed VE_Ports, just as EX_Ports are routed E_Ports.VE_Ports and VEX_Ports have the same behavior and functionality.

NOTE:At this time, you cannot connect both a VEX_Port and an EX_Port to the same edgefabric.

FICON/CUP Support

IMPORTANT:HP does not support FICON in this Fabric OS 5.1.0b firmware release. Seehttp://www.hp.com for a list of currently supported features.

12

The 4-Gbit/sec FC ports have the same level of support as in the previous release, FabricOS v5.0.1. As with all other port blades, if the B-Series MP Router blade is in slot 10,port 14 on the slot will be disabled when CUP is enabled.

More specifically:

• FICON is not supported over EX_Ports, VE_Ports, or VEX_Ports. Although aB-Series MP Router blade can be installed in a FICON-enabled director, FICONon the B-Series MP Router blade is not supported.

• FICON is not supported on the 400 Multi-protocol Router.

HP StorageWorks 4/64 SAN SwitchAs the latest addition to the HP StorageWorks family of switches, the 4/64 SANSwitch provides mid-range capabilities for customers who are either deploying theirfirst SAN or expanding their current SAN with lower-cost access to SAN technologythat is easy to manage The 4/64 SAN Switch provides the highest performance withhalf-a-terabit in 2U and lowest cost for 32- to 64-port switch available; allowing you toexperience the benefits of SAN solutions with the option to scale to larger fabrics on a“pay-as-you-grow” basis.

The simplicity and ease-of-use features of the 4/64 SAN Switch help increaseadministrator productivity and lower the cost of management, which can especiallybenefit organizations with limited IT expertise. In addition, the 4/64 SAN Switchleverages industry-leading 4-Gbit/sec Fibre Channel technology to provide extremelyhigh performance.

Delivering 32, 48, or 64 ports in a 2U form factor, the 4/64 SAN Switch enablessubstantial cost savings-from capital and operating expenses to overall management. Itextends the HP modular “building block” approach to developing storage networks. Thisapproach has been widely adopted by storage networking vendors and is the de factostandard in the storage networking industry. The 4/64 SAN Switch can stand up toany mission-critical test and offer significant business and performance advantages toSMBs and mid-range customers as they develop and grow.

FICON updateHP does not support IBM Fibre Connections (FICON) in this Fabric OS 5.1.0b firmwarerelease. See http://www.hp.com for a list of currently supported features.

NPIV updateHP does not currently support N-Port ID Virtualization (NPIV) in this Fabric OS 5.1.0bfirmware release. See http://www.hp.com for a list of currently supported features.

Fabric OS 5.1.0b 13

Firmware upgrades and downgradesHP does not support upgrading from more than two previous releases, for example,upgrading from Fabric OS 4.4.x to 5.1.0b is supported but upgrading from Fabric OS4.2.x or a previous release directly to 5.1.0b is not. Upgrading a switch from FabricOS v4.2.0 or earlier to v5.1.0 requires a two-step process: first upgrade to v4.4.0or v5.0.1 and then upgrade to v5.1.0.

PKI certificationIf you have purchased and are running the Secure Fabric OS option, go to the followingweb site for information on obtaining a PKI certificate:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c00027949#top

Unsupported commandsThe slotOff and slowOn commands are now obsolete; use slotPowerOff andslotPowerOn instead. The portLogPortShow command is also now obsolete.

4/256 SAN Director–CP failover/replacementBefore moving the slider UP on a CP that is being activated, observe that amber LED isnot ON for the active CP for at least 5 seconds and all LEDs are off on new inserted CP.

4/256 SAN Director–FDMI hostname supportIf you have HBAs that support FDMI exposure of host names in a fabric you will need3.2.0a and 4.4.0d to ensure that the host names are properly propagated to 5.1.0bswitches.

4/256 SAN Director–power-cyclingThe additional ports (128 to 255) require updates to certain Fabric OS versions: a)when you are running PID-2 format with a 4/256 SAN Director in the fabric and b) fora Secure Fabric OS fabric with a 4/256 SAN Director in the fabric and port numbershigher than 127 specified in DCC policies.

The minimum Fabric OS version requirements are: 2.6.2d, 3.2.0a, and 4.4.0d.

4/256 SAN Director–Proxy switchesIf you are using a Fabric OS 4.x switch as in API or SMI-S proxy to manage a 5.1.0bswitch, you must be running Fabric OS 4.4.0d, as a minimum requirement.

14

Fabric OS–diagnostics backport testThe backport test passes only in a) a pure SAN Director 2/128 Director or b) a SANDirector 2/128 system with no FC4-16 blades and under Option 5.

Do not run backport tests in any configuration other than the two listed above; usethe minicycle test instead.

Fabric OS–diagnostics spinsilk testThe following configurations will pass the spinsilk test:

• Pure SAN Director 2/128 Director (only CP2 and FC-16 blades)• Pure 4/256 SAN Director, option 5• Pure 4/256 SAN Director, option 5 (with FC4-16 blades)

The following configurations will fail the spinsilk test; use the minicycle test instead:

• Mixed SAN Director 2/128 Director (with either CP4 or FC4-16 blades)• Pure 4/256 SAN Director, option 1

“Pure 4/256 SAN Director” refers to a Director with CP4 and FC4-16 bladesonly.

Fabric OS 5.1.0b 15

WorkaroundsTable 3 lists important information and issues and their workarounds.

Table 3 Important information and workarounds

Issue Workaround

VEX_Ports experienced down time duringhafailover in port-based routing withIOD ON and DLS OFF.

Indicate to switch driver that ELP should beengaged on VEX link before setting SFID.

Fabric Manager showed ’fup_status-countfailed’ error and incorrectly reported FWDLstatus as failed on a SAN Switch 4/32.

Send a different code that can be interpretedby Fabric Manager so that the message issuppressed until the file gets created.

Not all Fabric OS services are availablewhen the prompt becomes available duringboot up.

Wait for all the services to come up beforeusing the switch or performing zoningactions.

FW_FRU_INSERTED message is displayedtwice when a power supply FRU is insertedand powered on.

No functional impact.

Scalability: MS Platform Database notsupported in large fabrics.

In large fabrics with more than 1,000ports, it is recommended that the MSPlatform Database is disabled, it is alsorequired that the Platform DB be disabledbefore downgrading to previous versionsof Fabric OS. This can be done using themsPLMgmtDeactivate command.

TRIP CHECK If the user tries to save movethan 512 monitors using the perfCfgSavecommand, some of the monitors may be lost.

Do not issue the perfCfgSave commandwhen running more than 512 monitors.

Scalability: When the cfgDisablecommand is executed, access is enabledbetween all devices. This can cause issueswith some HBAs.

Enable default zoning using the defzone--noaccess command.

Do not try to merge fabrics with conflictingdomain IDs over a VE_Port.

Before merging two fabrics over FC-IP withVE_Ports at each end, it is recommendedthat all domain ID and zoning conflicts areresolved.

If there is an already segmented port andbackbone devices are exported to an edgefabric, a build fabric / fabric reconfigurationcan occur after running haFailover

Ensure that there are no segmented portsbefore upgrading firmware.

16

Issue Workaround

When you use the diagnosticcommands systemVerificationand diagSetBurnin, the switch or bladewill fault when the burn-in error log is full.

Clear the burn-in log beforerunning systemVerification ordiagSetBurnin.

No offline diagnostics command are HAsafe.

All offline diagnostics commands should beused only when the switch is disabled.

SFPs should not be inserted while runningPower-On Self Test (POST).

POST can fail if new SFPs are added duringPOST. SFPs should only be added while theswitch is “online” or if the switch is poweredoff.

Password policies should be changed beforedowngrading to versions previous to FabricOS 5.1

Remove any password enforced expiration ofadmin or root accounts before downgradingfirmware to 5.0.1 or lower versions.

fcrDisable command behavior when anMP Router is present in the backbone fabric.

If an MP Router is present in the backbonefabric, the command fcrDisable maytake up to 8 minutes to complete. If theMP Router is replaced by a B-Series MPRouter blade or the later 400 MP Router, thecommand completes immediately.

Spinfab issues with E_Ports If there are ISLs present on the switch thatare not used for routing (due to them havinghigher linkcosts), disable the links beforerunning spinfab.

Cannot add more than six license keys in4/256 SAN Director, as 6th license key isoverwritten by any new license keys added.

Follow this procedure when changing theWWN card: 1. Remove all the licensesusing the licenseremove commandbefore the WWN card is replaced. 2.Install new licenses for the new license IDusing the licenseadd command after theWWN card is swapped.

Standby CP IP address may not bereachable after it is set to new IP addressfrom Web Tools.

Change the IP addresses from thecommand-line interface.

The system attempts a cold recovery asexpected, but does not start. System is thenout of sync & FOS is down.

Reboot the standby CP as instructed by theresulting error message.

Firmware downgraded to 4.2.2b from 5.0.1may cause all ports to be disabled on mostswitches.

1. For bladed switches using disruptivefirmwaredownload to downgradeFW, i.e., type firmwaredownload-s on both CP reboot both CP afterfirmwaredownload completes. 2. Fornon-bladed switches, reboot switch secondtime after firmwaredownload completes.

Fabric OS 5.1.0b 17

Issue Workaround

When switch names with characters otherthan alphanumeric and underscore _are used, you cannot access Web Toolssubwindows for those switches, such asZoneAdmin and SwitchAdmin.

1) Rename the switch to avoid the specialcharacters. OR 2) Use the switch IP in theURL to access Web Tools, instead of usingthe switch name.

The cfgdisable command turns offzone enforcement, which generates a lotof fabric activity and is likely to be verydisruptive to devices in a large fabric.During cfgDisable, all devices haveaccess to each other. In a big fabric withmany devices, doing a cfgDisable willcause a lot of RSCN and queries, which canbe disruptive.

Enable a dummy cfg instead ofcfgDisable, which will disableaccess among the unzoned devices.

Content of help (man) pages for particularcommands may not be consistent acrossdifferent Fabric OS releases.

Use the help (man) pages specific to therelease you are working on.

Faulty power supply causes continuousremoval and insertion error/info messages

Replace the faulty power supply.

Inconsistent blade status betweenslotshow and switchshow afterfailover.

Run bladedisable/enable on theaffected blade.

Firmwarerestore operationdoes not log results in either thefirmwaredownloadstatus area orthe system error log, even though theuser may expect some indication that thefirmwarerestore command operationwas triggered.

Run firmwarerestore, andfirmwareshow to make sure thefirmware has been restored properly.

Warning message in console log doesn’treflect a new area port # in switch PIDformat 2

To locate the failed port, use a formulato convert the port # shown in the errormessage to the new area as displayed inswitchshow.

Port with 2G SFP negotiated and mistakenlycame up at 4G.

Run portdisable/portenable on thisparticular port and it should come up at 2Gagain. If trunking is enabled, it will join thetrunk group as a trunk port.

Commands using Linux command/usr/bin/less not handling pagecontinuation properly with space bar promptto continue.

Use the portlogdump command instead.

18

Issue Workaround

Diagnostics: Backport test fails with errormessage in a mix-bladed chassis

Do NOT run a backport test in anyconfiguration other than a pure SAN Switch2/128 system or a 4/256 SAN Directorsystem with no FC4-32 blades and underOption 5. Use a minicycle test instead.

Tags in older RLIR events replaced withincorrect tags from the latest RLIR event inthe Events table

Use the ficonShow RLIR command inthe command-line interface to get RLIR data.

Using 3rd party test software, F-ports andL-ports connected to a 4/8 SAN Switchor 4/16 SAN Switch disabled after loginprocess right after port reset.

Disable the switch and then enable it.

SAN Switch 4/32 unlicensed POD portsblinking in place of LED being turned off.

Run portdisable on wrongfully(unlicensed) blinking ports to stop theblinking.

Fan removal and insertion on SAN Switch4/32 causes FAN-1 to appear faulty ifinsertion rate or force is not steady.

If a fan is marked as faulty (amberflashing lamp on fan assembly) within afew seconds after insertion, it is possiblethat this is a false failure indicationdue to a momentary disconnectioncaused by uneven insertion (contactbounce). Restore the fan to an operationalstatus using the following procedure:1) Pull the fan assembly out half way2) Re-insert the fan at a moderate pace witha steady application of moderate force untilthe fan assembly seats securely.

FWD daemon no longer running afterfirmwaredownload observed whenswitchstatusshow was run, thefollowing message was displayed amongother messages: Fabric Watch Daemonis not running (maybe it hasn’t finished itsinitialization..)

Reboot the switch to start Fabric Watch.

Fully-loaded 4/256 SAN Director, a fewE-Ports and F-Ports stay in Mod_Val modefor > 11 minutes after fastboot.

Disable and enable the port which is stuckin Mod-Val state.

All trunk ports of a 4-port trunk group onboth sides of the links between a 4/256SAN Director and 24000 stuck in unknownE-port state after failover.

bladedisable/enable the affected portblade.

Fabric OS 5.1.0b 19

Issue Workaround

Ports were faulted on many E-ports fromswitchshow after running the hafailoverscript on 4/256 SAN Directors overnight.Error messages displayed on the console asfollows: CDR-1002], 32019,, WARNING,C48K_142055, Port 231 chip faulted dueto internal error. Perform slotpoweroff andslotpoweron to recover the port.

Perform slotpower off/on to recoverthose ports.

Standby CP keeps rebooting witherror: Failed to retrieve current chassisconfiguration option, ret=-29. System ofSAN Director 2/128 CPs, chassis configoption 2.

Power cycle the chassis to bring up both CPsin sync.

After invoking Add all ports and thenremoving some individually, you cannotrestore missing ports by invoking Add allports again.

Close the Switch Throughput Utilizationdialog and reopen it to perform the actionagain.

May get a secure switch stuck in errorstate if a secFCSFailover is attemptedwhile a fabric is busy. This will prevent seccommands from completing on the fabric- secpolicysave for example

To prevent this problem, do not attempt asecure failover while the fabric is busy forany reason. Wait for the fabric to settledown before issuing secFCSFailover.To recover from the problem, issuesecversionreset on the switch in errorstate and then merge it back into the fabric.

The fanshow command correctly shows thefan as faulty, but the Fabric Watch monitormay report both Healthy and Marginalstatus for the fan because the motor is stillattempting to spin at the correct RPM.

Use the fanshow command to provide thecorrect status for the fan.

Numerous Exchange allocation error!!messages on console, ’msd’ unexpectedlyterminates then kSWD reboots the switchduring continuous reboot of core switches.

Ensure that the principle switch is alwaysone of the high port count core switches.

RNID has switch Model Number of NAshould be 200.

Use the link incident PID to find the switchthat generated it.

20

Issue Workaround

WWN card side LED behavior does notmatch with actual blade LED when bladedisplays FAULTY (51).

replace the faulty blade and reset CP itshow faulty(51).

In a fully loaded 4/256 Director switch withall 256 F/FL ports in a single zone, theswitchenable operation takes 15 to 30minutes to complete.

Instead of using switchdisable/enable, bring down and up one slot at atime with a time gap in between.

Using dnsconfig command, DomainName field should not accept spaces sinceonly the characters up to the first space areaccepted as new domain name.

Re-enter the domain name without spacecharacters.

Fabric OS 5.1.0b 21

Fabric OS 5.1.0a fixesTable 4 lists Fabric OS 5.1.0a improvements rolled into this Fabric OS 5.1.0b release.

Table 4 Fabric OS 5.1.0a closed defects

Closed Defect Description

In interop mode, PLOGI ACC frame droppedby switch.

In a configuration with a HP StorageWorksswitch running Fabric OS v4.4.0 or laterand 3rd party switches in interop mode,device PLOGI ACC frame was dropped bythe switch.

Many zombie secure shell daemon (sshd)processes caused memory leak and switchreboot.

Switch panic console log showed 80 plussshd zombie processes on switch duringswitch panic with OOM.

In the backbone fabric, if cfgsave wasexecuted instead of cfgenable, thendevices might be imported prior to addingLSAN zones to active zone set.

During LSAN zone modification orcreation, if cfgsave was executed priorcfgenable, devices might be importedbetween edge fabrics prior to adding theLSAN zone to the active zone set.

Traffic might pause on interfabric data pathsin a metaSAN environment if a switch in anedge fabric goes offline.

In a metaSAN environment, frame loss mightoccur on datapaths originating from anedge fabric if a switch in the edge fabricwent offline.

After hafailover, changing routingpolicy from exchange to port-based causedpanic to both CPs.

When running hafailover on a 4/256Director (with traffic running), the scriptwas stopped and the routing policy waschanged from exchange to port-based.

Host cannot see target after a switch runningFabric OS 5.0.x rebooted for a very specifictarget.

If the SCSI query failed while the switch wasestablishing the session with the target afterPLOGI, the device was not considered aFCP device.

Unable to login using API to a disabledswitch using LoginAsUser.

The user could not login through SMI-A ifswitch is disabled.

FC ping between edge fabric and backbonedid not work from edge fabric when therewas more than one hop to the device in thebackbone fabric.

FC ping failed from edge fabric to backbonedepending on the connectivity of the devicein the backbone fabric.

Incorrect switch status reported when a fanwas removed.

Fabric Watch error message did not reflectthe thresholds configured.

An application using SNMPv2c receives atimeout when making an SNMP request toFabric OS 4.4.x/5.0.x switches.

Fabric OS v4.4.x and Fabric OS v5.0.x arenot SNMPv2c capable.

22