Brocade SMI Agent 120.9.0 Release Notes v2.0: September 8, 2009

Brocade SMI Agent 120.9.
0
Release Notes v2.0
September 8, 2009
Document History
Document Title Summary of Changes Publication Date
Brocade SMI Agent 120.9.0 Release Notes v1.0 Initial Release July 24, 2009
Brocade SMI Agent 120.9.0 Release Notes v2.0 Second Release – September 9, 2009
updated FOS v6.2.x
support statement
© 2009 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade
B-wing symbol, DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the
United States and/or in other countries. All other brands, products, or service names are or may be trademarks
or service marks of, and are used to identify, products or services of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or
implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade
reserves the right to make changes to this document at any time, without notice, and assumes no responsibility
for its use. This informational document describes features that may not be currently available. Contact a
Brocade sales office for information on feature and product availability. Export of technical data contained in
this document may require an export license from the United States government.
Brocade 120.9.0 Release Notes v2.0 2 of 23

CONTENTS
Document History.............................................................................................................................................. 1
Overview ........................................................................................................................................................... 4
Release Contents Summary ........................................................................................................................... 4
Supported Client Operating Systems ............................................................................................................. 4
Server / Client .................................................................................................................................................... 4
VMWare support ............................................................................................................................................... 5
VMWare ESX server 3.5. Following are the guest operating systems tested: .................................................. 5
Note: Other virtualization software is not supported. ........................................................................................ 5
Switch Platform and Firmware Requirements ................................................................................................... 6
Recommended Brocade Fabric OS Versions ................................................................................................. 8
Scalability of the SMI Agent ......................................................................................................................... 9
Brocade SMI Agent Documentation.................................................................................................................. 9
Documentation Updates..................................................................................................................................... 9
Important Notes ................................................................................................................................................. 9
Open Defects in SMI Agent 120.9.0.................................................................................................................15
Closed Defects with Code Change in SMI Agent 120.9.0................................................................................19
Closed Defects without Code Change in SMI Agent 120.9.0...........................................................................21

Overview
The Brocade SMI Agent (SMI-A) is host-based middleware that enables application developers with
programmatic access to management facilities to Brocade fabrics.
Brocade SMI-A is a “proxy” agent that resides on a separate host, not internal to Brocade switches.
The functionality of this agent is described below.
The Brocade agent does not require any modification of or upgrade to deployed fabrics when it is
deployed. All of the support required in Brocade switches is already in place.
SMI Agent 120.9.0 provides new features and support for new platforms.
Release Contents Summary

• Support for new hardware
o Brocade 8000
• OEM Requirements
o Populate Fabric Identifier in IdentifyingDescriptions and OtherIdentifyingInfo properties of
CIM_AdminDomain class for Fabric in case of Meta SAN
o CIM_InstModification SourceInstance populated with all the properties that can be retrieved
using GetInstance
• J WBEM Server 2.7.4 Integration
Requirements
• Java JRE or JDK (version 1.5.0)
The installation program automatically installs Sun Microsystems JRE version 1. 5.0_11 under
the SMI Agent installation directory.
Supported Client Operating Systems

Brocade SMI Agent 120.9.0 is fully tested and supported on the following operating systems (32-bit
versions only):
Server / Client
Operating System Versions
Microsoft 2000 Server SP4 (x86 32-bit)

Windows
2003 Server SP2 (x86 32-bit)
Vista Business Edition SP1 (x86 32-bit)
2008 Server SP1 (x86 32-bit)
Sun Solaris 8, 9 and 10 (SPARC-platform)

Operating System Versions
Linux RedHat AS 3.0 (x86 32-bit)

RedHat AS 4.0 (x86 32-bit)
SUSE Enterprise Desktop 10.0 (x86 32-bit)
AIX 5.3
VMWare support
VMWare ESX server 3.5. Following are the guest operating systems tested:
1. Windows 2003 Server
2. RedHat Linux AS4
3. Windows 2008
Note: Other virtualization software is not supported.

Switch Platform and Firmware Requirements
The following table lists the versions of Brocade software supported in this release. Brocade
recommends using the latest software versions to get the greatest benefit from the SAN. Please refer to
the Recommended Brocade Fabric OS Versions section for greater detail.
Operating System Switch/Director
Switch Type Firmware Versions
FOS 3.2.1c Brocade 3800
FOS 4.4.x and 5.0.x Brocade 12000

Brocade 24000 with FC2-16 blades
FOS 4.4.x, 5.0.x, 5.1.x, 5.2.x, and 5.3.x Brocade 3900

Brocade 3250
Brocade 3850
FOS 5.0.x, 5.1.x, 5.2.x, and 5.3.x Brocade 24000 with FC4-16 blades
FOS 5.0.x, 5.1.x, 5.2.x, 5.3.x, 6.0.x, 6.1.x, 6.2.x and Brocade 4100
6.1.2_cee Brocade 75001
Brocade 200E
Brocade 49002
Brocade 50003
Brocade AP76004
Brocade 3005
Brocade 51005
Brocade 53005
Brocade Encryption Switch7
Brocade 48000 with FC4-16, FC4-32 and FC4-482 blades
Brocade 48000 with FC8-16, FC8-32, and FC8-48 blades
Brocade 48000 with FR4-18i1
Brocade 48000 with FC4-16IP2
Brocade 48000 with FC10-64
Brocade DCX6 with FC8-16, FC8-32, and FC8-48 blades
Brocade DCX6 with FR4-18i blades
Brocade DCX6 with FC10-6 blades
Brocade DCX6 with FS8-18 blades
Brocade DCX-4S8 with FC8-16, FC8-32, and FC8-48
blades
Brocade DCX-4S8 with FR4-18i blades
Brocade DCX-4S8 with FC10-6 blades
Brocade DCX-4S8 with FS8-18 blades
Brocade 80009

Operating System Switch/Director
XPath 7.4.1e w/ SAS 2.1.3j AP7420
1 Requires FOS v5.1.0 or higher

7 Requires FOS v6.1.1_enc or higher
8 Requires FOS v6.2 or higher
9 Requires FOS v6.1.2_cee or higher
Blade Type Firmware Versions
FOS v3.2.1c Brocade 3000
FOS 5.2.x, 5.3.x, 6.0.x and 6.1.x Brocade 3014

Brocade 3016
Brocade 3016
Brocade 4020
Brocade 4016
Brocade 40241
Brocade 4018
Brocade 4012
Brocade 4424
Brocade 54102
Brocade 54802


Recommended Brocade Fabric OS Versions
Minimum Recommended firmware versions to be used as “proxy”
• Fabric OS v6.2.0g
• Fabric OS v6.1.1d
• Fabric OS v6.1.2_cee
• Fabric OS v6.1.0j
• Fabric OS v6.0.1a
Recommended firmware versions to be used as “non-proxy”

All firmware versions listed as a “proxy”, as well as:
• Fabric OS v6.0.1a
• Fabric OS v5.3.1b
• Fabric OS v5.3.0e
• Fabric OS v5.2.3
• Fabric OS v5.0.5f
• Fabric OS v3.2.1c
• XPath 7.4.1e with SAS 2.1.3j
Switches with the following firmware versions should not be used as a “proxy”:
• Fabric OS v5.x.x
• Fabric OS v4.4.x
• Fabric OS v3.2.x
• Fabric OS v2.x
• XPath OS v7.4.1e with SAS 2.1.3j
The following switches are not supported as proxy, since the highest supported firmware for these
switches does not meet the minimum requirement for proxy.
Switches Model Maximum supported Version

Brocade 3000 (HP MSA embedded) FOS v3.2.1
Brocade 3016 (IBM embedded) FOS v5.3.x
Brocade 3014 (Dell embedded) FOS v5.3.x
Brocade 3200 FOS v3.2.1c
Brocade 3800 FOS v3.2.1c
Brocade 3250 FOS v5.3.x

Scalability of the SMI Agent

The following are the scalability limits the agent is tested with:
Fabric Object SMI Class name Scalability
number
Switches Brocade_Switch 72
FC Ports in Switches Brocade_SwitchFCPort 5854
Devices Brocade_Node 5744
FC Ports in Devices Brocade_NodeFCPort 6243
Zones Brocade_Zone 6962
Zone Alias Brocade_ZoneAlias 15622
D,P or WWN Zone Brocade_ZoneMembershipSetti 22467
members ngData
Brocade SMI Agent Documentation

The following Brocade documents support these release notes:
• Brocade SMI Agent Installation Guide
This guide is for anyone who needs to install or uninstall the Brocade SMI Agent.
• Brocade SMI Agent User’s Guide
This guide is for end users who need to start, stop, and configure the Brocade SMI Agent.
• Brocade SMI Agent Developer’s Guide
This guide is for CIM application developers who are developing Brocade SMI Agent client
programs.
Refer to the MOF files for descriptions of the classes, associations, and methods.
Documentation Updates
This section provides information on last-minute additions and corrections to the
documentation.
Important Notes
This section lists the details for New Feature, changes for the release, certain scenarios, and options to be
used to resolve the issues.
• This release supports new hardware: the Brocade 8000. The existing data model will be used to
represent the FC Switch and the new FCoE model is introduced to represent the Ethernet
domain
The existing switch data model along with the new FCoE model for Ethernet domain is supported. The
regular FC functionality can be managed for this hardware based on the existing FC model for FC

switches. The Ethernet functionality can be discovered for this hardware by the new Ethernet/FCoE
model
The following is supported in SMIA 120.9.0 with respect to FCoE:
1. Discovery of the FCoE internal ports as SwitchFCPorts
2. Discovery of the Ethernet switch and Ethernet interfaces.
3. Discovery of FCoE devices as Brocade_Node
4. Discovery of device links between the FCoE switch and the devices through
Brocade_SANActiveConnection
5. Discovery of Brocade 8000 as an edge to the FCR fabric
Existing class Brocade_SANActiveConnection will be used to discover the device links through the
FCoE ports and the Brocade_Node.
Existing class Brocade_SwitchFCPortStats, Brocade_SwitchFCPortRateStats will be used to discover
the port statistics information of FCoE ports
Existing Brocade_Node class will be used to model the devices connected
• Meta SAN Fabric Identifier will be displayed in IdentifyingDescriptions and

OtherIdentifyingInfo properties of CIM_AdminDomain class
This enhancement includes the addition of a new element in the IdentifyingDescriptions and
OtherIdentifyingInfo properties of the CIM_AdminDomain class for the Fabric class.
If the managed fabric is an edge fabric having FD switches, the IdentifyingDescriptions will have
the value as 'SNIA:VF_ID,SNIA:IFR_ID' and "SNIA:DetailedType;" and OtherIdentifyingInfo will
contain the corresponding values to IdentifyingDescriptions values.
• Added flavors for Brocade_SwitchFCPort to differentiate between port types like VF ports,
internal port /external ports, ICL ports, NPIV ports, FCIP and FCR ports
PortDiscriminator property is added for Brocade_SwitchFCPort to differentiate between port
types, internal port /external ports, ICL ports, VF ports, FCIP and FCR ports.
• Attached port information for FCR port that is connected to the Edge fabric will be populated
with Edge fabric port wwn in the class Brocade_PCSNetworkPort with a property
AssociatedNodeinfo. This support requires FOS firmware version 6.2.0d or later version.
• CIM_InstModification SourceInstance will be populated with all the properties that can be
retrieved using GetInstance
The CIM_InstModification indication delivered from SMIA will have the SourceInstance property
populated with all the properties that can be retrieved using the GetInstance operation
• J WBEM Server 2.7.4 Integration
J WBEM Server 2.7.4 resolves the indication delivery delay. A long delay in indication delivery was
observed earlier whenever there were stale invalid subscriptions present in the J WBEM Server. With
the current release of J WBEM Server, indications will be delivered in a reasonable amount of time
even if there are stale indication subscriptions.
Note: It is still recommended to delete the stale indication subscriptions periodically.

This table lists important information you should be aware of regarding Brocade SMI Agent 120.9.0.
Area Description
Installation Since the Brocade SMI Agent uses third-party software, InstallAnywhere, for the
installation wizard, any problems that might occur as a result of a defect in the
InstallAnywhere product will be resolved only by resolution of the InstallAnywhere
defect.
iSCSI In Fabric OS v4.4.0x, when the switch is disabled, the SMI-A cannot get port
information from the switch through association calls from switch to port. It is
recommended that you upgrade these switches to Fabric OS v5.3.x or above.
FDMI and AG The HBA will register FDMI port attributes with the switch using the RPA (Register
Port Attributes) FC_CT request. If the hostname is not configured properly, all other
attributes except host name will be registered. Thus, FOS does not provide the host name
when queried for Brocade_Platform. Hence to get the Brocade_Platform instance from
SMI Agent, the host name should be configured properly on the FDMI enabled host or
AG Platform; otherwise, the SMI Agent will not respond to the Brocade_platform
query.
Fabric OS Fabric OS v5.0.1 has known timeout and memory leak issues. It is recommended that
you upgrade these switches to Fabric OS v5.3.x or above.
Provider Logging of provider exceptions and events will only be enabled when flag
Logging debug_logging=true in the start_server script and when the options are enabled in the
debug.properties file.
SFPs For non-Brocade SFPs on the Brocade DCX and Brocade DCX-4S, the value of the
(IsSFPPresent Brocade_SwitchFCPort.IsSFPPresent property does not match the value that is returned
property) in the CLI sfpshow command.
The Brocade_SwitchFCPort.IsSFPPresent property returns false, whereas the sfpshow
command returns true.
Configupload Configupload though SMI-A does not work for a 3.2.1 switch. The SMI-A issues a
NumberFormatException.
Workaround: Use another method (such as Web Tools or the CLI) to perform the
configupload.
Time Zone On a Fabric OS v5.3.x switch, if the time zone is set using the CLI tstimezone --
interactive, which uses the new time zone functionality in Fabric OS, the
Brocade_Switch.SwitchTimeZone property might not depict the correct time zone
setting. This incorrect behavior is only seen for 3 different time zones, and only when
the date is set for DST (Daylight Savings Time) for that time zone area.
o If you call SetInstance to set the value of SwitchTimeZone to 20, GetInstance
returns the value as 22. 20=(3:30hrs). 22=(4:30hrs).
GetInstance might also return the incorrect value when the time zone is set through the
CLI for the above mentioned values (20, 30, and 32).
Workaround: Use the legacy CLI tstimezone --old, which does not take into account
DST(Daylight Savings Time).

Area Description
Indications If you cannot receive indications in an IPv6 configuration, note the following:
o For a multihomed host (with both IPv6 and IPv4), if a 1.2.x client on Java 1.5 is
used for indications on a 2.x WBEM that is configured for IPv4 (PreferIPV4Stack is
set to true in JServer.properties or through the configuration tool), you must set the
following system property on the client side:
java.net.PreferIPv4Stack=true
o For a multihomed host (with both IPv6 and IPv4) or a pure IPv6 host running a 2.x
WBEM that is configured for IPv6 (PreferIPv4Stack is set to false in
JServer.properties or through the configuration tool), only a 2.x WBEM client can
be used for obtaining indications.
Connection This feature to facilitate the reconnection to another switch in the same fabric in case the
reload primary connection is down. The user should be able to configure this feature in the
SMIAgentConfig.xml by setting the connection reload flag to true and adding the
alternate connection entries to the fabric in the provider.xml.
File -
< Installed Directory > \agent\server\jserver\bin\SMIAgentConfig.xml
<connection reload=”true”/>
After adding this tag, the last five lines of the SMIAgentConfig.xml file
should look like the following (the added line is in bold):
<dbserver driver="com.sybase.jdbc2.jdbc.SybDriver" url="" username="" password=""
is_password_encrypted ="false"/>
<port_config eventing="" arr=""/>
<secureport_config eventing="" arr=""/>
<connection reload="true"/>
</agent_config>
In case of fabric segmentation also the ‘connection reload’ flag will be used to connect to
the segmented fabric. But the connection corresponding to the segmented fabric should
be added in provider.xml with ‘created_by_agent’ flag set to ‘false’.
Segmentation and If the proxy switch is disabled and then enabled, no fabric change events are sent to the
Merge client.
Password Length CIMOM has a limitation on password length of 16 characters. If a password is provided
Limitation with more than 16 characters then the password will be truncated to 16 characters. It is
recommended to provide a password less than 16 characters.
Firmware The SMI-A allows you to perform a firmware downgrade to Fabric OS v6.1.0 on a
downgrade on Brocade 7500E, even though the 7500E is not supported by this firmware version.
7500E
Do not use the SMI-A to perform firmware downgrades on the Brocade 7500E. Use the
CLI to perform the firmware downgrade, as the CLI correctly prevents a downgrade to an
unsupported firmware version

Area Description
Connection Unable to delete the proxy entry in Configuration tool when the “Connection status”
shows as not connected.
Sometimes the wrong status message is displayed for proxy switches in the Server
configuration tool
o Logout Progress status is shown for the proxy already logged out
o Login progress status is shown for the proxy already connected
Installer - We have seen that sometimes on fresh installation, the confirmation dialog for importing
Importing configuration pops up. This is a false message. Please choose the ‘Cancel’ option. Instead
previous of choosing ‘Cancel’ if we proceed with installation then we have seen that the
configuration SMIAgentConfig.xml getting corrupted which results in SMI Agent misbehaving.
Connection It is recommended to set Number of RPC handles to ‘1’ while adding a proxy switch
entry using Configuration tool or provider.xml when there is a firewall between the
SMIAgent and the switch. This setting is especially required when there is a firewall
configuration to monitor idle connections.
Indication The indication delivery is delayed when there are stale subscriptions present. The
workaround of this issue is to cleanup the stale subscriptions. Stale subscription cleanup
utility (SubscriptionCleanup.bat) is present under
<SMI_AGENT_HOME>/agent/server/jserver/bin.
Interop mode ‘2’ In order to manage FOS switches in interop mode ‘2’ and ‘3’ and to discover the
and ‘3’ complete topology involving EOS switches, OSMS feature should be enabled on all the
EOS switches.
Topology View Brocade_TopologyView has the following issues
a) Brocade_TopologyView gives wrong attached port WWN corresponding to

EOS switch in Interop mode
b) Brocade_TopologyView gives wrong port WWNs in case of ports having port
Index greater than 255
Brocade_TopologyView instances are not updated when NPIV Virtual WWN is

added/removed

Area Description
Co-existence of The Brocade SMI(FOS) Agent can co-exist in the same host with the Brocade SMI(EOS)
FOS and EOS agent version 2.5 or above. However, when the agents co-exist on the same host they
SMI Agent need to be configured to run on the different ports.
System Requirements: 4 GB RAM or higher, 3 GHz CPU, 1 GB JVM memory size for
each agent.
There are two possible scenarios for the agents to co-exist on the same host:
CASE I
1. Install SMI(EOS) agent
2. Install SMI-A (FOS) with non-default ports (say https:6000 and http:6001)
Note: SMI-A (EOS) would run on default ports (https:5989 and http:5988) in the above
scenario.
CASEII
1. Install SMI(EOS) agent
2. Change the http and https port numbers by using the Server Configuration tool
(SCT) and restart the SMI(EOS) agent
3. Install SMI-A (FOS) with default ports
Notes:
1. SMI(EOS) agent 2.5, 2.6doesn’t provide an option to change the ports during
installation. SMI (EOS) agent 2.6.1 has an option to change only the https port
number during installation
2. If SMI-A (FOS) is installed in a host in which SMI (EOS) agent already
installed, it will register to the SLP service installed by the SMI (EOS) agent. If
any client queries the SLP service running in the host, it will list both the SMI
(EOS) and SMI (FOS) agents.
Virtual Fabric If there is already a discovered virtual fabric and a configuration change is done to
this virtual fabric, rediscovery of fabric is required to effect the changes.
For ex: Port movement from one logical switch to another logical switch
To rediscover the fabric:

1.Open Configuration Tool>Fabric Connections>Proxies
2.Select and remove the VF enabled proxy switch and click on apply
3.Add the same proxy switch and apply.

Open Defects in SMI Agent 120.9.0
Defect ID: DEFECT000230763 Technical Severity: High

Summary: Unable to get LifeCycle Indications when a port is moved from one logical switch to another in a Virtual
Fabric setup.
Symptom: Customer will not be aware of port movement from one logical switch to another in a Virtual Fabric.
Feature: PROVIDERS Function: EVENTING Probability: Medium
Found in Release: SMIA120.8.0
Defect ID: DEFECT000228130 Technical Severity: Medium

Summary: When Blade becomes Faulty, the OperationalStatus of CIM_LogicalModule and the associated Ports should
change, and the LifeCycle Indication support should be provided.
Symptom: Brocade_TopologyView instance will not get updated automatically with the operational state of the
CIM_LogicalModule.
Workaround: Use Get instance operation for Brocade_Topology view instance.
Feature: PROVIDERS Function: FRU Probability: Low

Summary: Count Mismatch between EnumerateInstances and EnumerateInstanceNames on 'Brocade_PortModule' for
Fibre Channel Router connected to Virtual Fabric
Symptom: Customer will see an incorrect number of instances of the Brocade_PortModule in a Virtual Fabric context
having one single EX-Port from a particular slot on a logical switch.
Workaround: Add one more port (a non- EX port) from the same slot to the Virtual Fabric context.
Feature: PROVIDERS Function: FCR Probability: Medium

Summary: Unable to change values of writable properties RLSServiceEnable and PortLogEnable in
Brocade_SwitchServiceCapabilities class using the CIMWorkshop tool.
Symptom: User cannot modify values of RLSServiceEnable and PortLogEnable in Brocade_SwitchServiceCapabilities
class through CIM clients.
Feature: PROVIDERS Function: ERROR HANDLING Probability: Medium

Summary: Association and reference operations fail for Brocade_TCPProtocolEndpoint CIM Object Paths.
Symptom: Customer will have traversal issues when using FCIP setup.
Feature: PROVIDERS Function: FCR Probability: Medium

Summary: CIM_ERR_FAILED for Enumerate instance operation for FDMI HBA
Symptom: Customer will see this problem when a FDMI HBA is connected to the fabric and is not registered properly.
Feature: PROVIDERS Function: FDMI Probability: Medium

Summary: Sometimes EnumerateInstanceNames and EnumerateInstances count varies for Brocade_blade connected to
M-EOS fabric.
Symptom: Enumerate instances and EnumerateInstanceNames count varies for Brocade_blade connected to M-EOS
fabric.
Feature: INTEROPERABILITY Function: DISCOVERY Probability: Medium

Summary: Provider returns instances of CIM_FCport for powered off blade, and Association/Reference operation fails
for those instances.
Symptom: FCport instances for powered off blade is returned by provider, and Association/Reference operation fails for
such instances.
Feature: PROVIDERS Function: FRU Probability: Medium

Summary: EnumerateInstance operation on Brocade_TopologyView class fails when translate domain is present in FCR
setup.
Symptom: User cannot get topology view instances properties using Enumerate instance operation in FCR setup with
translate domains.
Feature: PROVIDERS Function: PORTDISCOVERY Probability: Medium

Summary: Enumerate instance operation on brocade_switchfcportstats and brocade_switchfcportratestats classes are not
populating instances corresponding to FCoE internal ports.
Symptom: User cannot get port statistics information for FCoE internal ports using enumerate instance operation on
brocade_switchfcportstats and brocade_switchfcportratestats classes.
Workaround: Obtain statistics information by using the getinstance operation.
Feature: PROVIDERS Function: Probability: High
OTHERFABRICDISCOVERY

Summary: Alert Indication is not delivered when subscription is done with filters.
Symptom: Alert Indication is not delivered.
Workaround: User can subscribe alert indication without using filters.

Summary: Mismatch in instances and instanceNames count when the fabric is not stable.
Symptom: There is a mismatch between instance and instanceNames count for various classes like Brocade_FCPort,
Brocade_Switch when the fabric is unstable. EnumerateInstanceOperation fails for
Brocade_PCSNetworkPort
Workaround: Restart SMI Agent.
Feature: PROVIDERS Function: Probability: Low
OTHERFABRICDISCOVERY

Summary: Provider running for an extensive period sometimes fails to deliver indications.
Symptom: Sometimes provider fails to deliver indications after the provider has run without restarting for 5 to 6 days.
Workaround: Restart the server.

Summary: GetInstance operation fails for a zonemember created out of node WWN connected to another fabric, when
both fabrics are managed.
Symptom: User gets "zonemember not found" exception for a zonemember that is available.
Workaround: EnumerateInstance operation can be performed to get the zonemember instance details
Feature: PROVIDERS Function: Zoning Probability: Medium

Summary: Provider fails to return correct instances for Brocade_switchfcport, Brocade_switch, Brocade_PortinSwitch
when ports are moved from one logical switch to another logical switch
Symptom: Provider cache is not updated after assigning ports to the logical switches. Instances are not returned
correctly for Brocade_switchfcport and Brocade_portinswitch
Workaround: Restart the provider.
Feature: PROVIDERS Function: PORTDISCOVERY Probability: Medium

Summary: GetInstance operation for Brocade_PCSNetworkPort,SwitchFCPort falis for port avaiable in non-default
logical switch
Symptom: In a VirtualFabric configuration, for the ports in the non-default logical context Getinstance operation will
fail for Brocade_PCSNetworkPort class
Workaround: The properties of the Brocade_PCSNetworkPort cab be verified through EnumerateInstance Operation
Feature: PROVIDERS Function: MCSDISCOVERY Probability: Medium

Closed Defects with Code Change in SMI Agent 120.9.0

Summary: Brocade_SANActiveConnection is not giving any instance corresponding to switch-to-switch
active connection.
Symptom: User cannot get active connection between switches.
Feature: PROVIDERS Function: OTHERFABRICDISCOVERY
Probability: High Risk of Fix: Low

Summary: Brocade_switchInFabric association class instances for normal fabric are not listed when managed
with another fabric (VF enabled).
Symptom: User unable to manage normal fabric.
Workaround: Need to have normal switch as proxy in the VF enabled fabric rather than having VF switch as
proxy.
Feature: PROVIDERS Function: CONNECTION
Probability: High Risk of Fix: Low

Summary: AssociatorNames operation on Brocade_ZoneMembershipSettingData shows incorrect Zone while
adding same zone member to different zones.
Symptom: Customer would misunderstand the zoning configuration while traversing from
ZoneMembershipSettingData to Zone.
Feature: PROVIDERS Function: Zoning
Probability: Medium Risk of Fix: Low

Summary: The event processed by SMI-A is incomplete if the event channel has event length greater than
1024 bytes.
Symptom: Event processed by SMI-A is incomplete.
Feature: PROVIDERS Function: EVENTING
Probability: Medium Risk of Fix: Medium

Summary: Though dynamic end-to-end monitors are not supported between 2 E-Ports, CreateNetworkPipes
method creates ConcreteJob.
Symptom: User will not get an error while trying to create network pipe between two E ports.
Feature: PROVIDERS Function: APM

Summary: Switch status change indication is only sent intermittently.
Symptom: User will see switch status change indication intermittently.
Probability: Medium Risk of Fix: High

Summary: Login failure occurs when SMIA is trying to get enclosure details for a phantom switch.
Symptom: Login fails.
Feature: PROVIDERS Function: CONNECTION

Closed Defects without Code Change in SMI Agent 120.9.0

Summary: Slptool command is failing for SMI-A 120.7.2b.
Symptom: User cannot use Slptool commands. This is blocking CTP certification.
Feature: WBEM SOLUTIONS CIMOM Function: SLP
Reason Code: Already Fixed in Release Probability: High

Summary: Getproperty operation returns incorrect values for brocade_chassis cim object path.
Symptom: The property values are not populated for Getproperty operation on brocade_chassis cim object
path.
Workaround: User should query the property with the correct case.
Feature: PROVIDERS Function: PROFILE
Reason Code: Already Fixed in Release Probability: Medium

Summary: SMI agent fails to return instances for Association and Reference operation without the filter class.
Symptom: Query will fail if it does not include the resultant or association class.
Workaround: Instances will be returned by giving the resultant and association class filters for Association
and Reference operation.
Feature: PROVIDERS Function: PROFILE
Reason Code: Not Reproducible Probability: Medium

Summary: Exception is thrown in SCT console when security and windows domain authentication is enabled
during silent installation.
Symptom: SCT will throw an Exception when Windows domain Authentication is enabled.
Workaround: Use normal installation procedure intstead of slient installation
Feature: CONFIGURATION TOOL Function: Security
Reason Code: Will Not Fix Probability: High

Summary: Configuration Tool might not allow removal of inactive connection entries.
Symptom: Proxy will be displayed with “Connection Failed” status and user will not be able to remove the
entry using the “Remove” button.
Workaround: Re-launch the configuration tool.
Feature: CONFIGURATION TOOL Function: PROXY
Reason Code: Will Not Fix Probability: Low

Summary: Proxy addition during installation will display the connection status in Config Tool as Login
Progress, even after the connection has been established to the proxy.
Symptom: Proxy address added during installation will display the status message as "Connected" after
starting the server through the Config Tool. Connection to the switch is established. The
configuration tool shows the status message as “Login Progress”. This status message doesn’t
have impact on the connection to the proxy switch.
Workaround: Customer can connect to proxy and call Enumerate Instance on Brocade_Switch to check
whether connection to proxy has been established or not.
Feature: CONFIGURATION TOOL Function: PROXY
Reason Code: Will Not Fix Probability: Medium

Summary: CIMInstCreation indication for Brocade_Node is received multiple times when a device enters a
fabric.
Symptom: The customer would notice the CIMInstCreation indication multiple times when a node port is
enabled or a new device enters the fabric. The customer can filter out these indications.
Reason Code: Will Not Fix Probability: Medium

Summary: The response time of SMI-A slows down with multiple login and logout operations done
continuously using script.
Symptom: After doing continuous login and logout operations, SMI-A response time slows. This does not
occur while performing normal login and logout.
Feature: PROVIDERS Function: PERFORMANCE
Reason Code: Will Not Fix Probability: High

Brocade SMI Agent 120.9.0 Release Notes v2.0: September 8, 2009

Uploaded by

Copyright:

Available Formats

Brocade SMI Agent 120.9.0 Release Notes v2.0: September 8, 2009

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brocade SMI Agent 120.9.0 Release Notes v2.0: September 8, 2009

Uploaded by

Copyright:

Available Formats

Brocade SMI Agent 120.9.

Brocade 120.9.0 Release Notes v2.0 2 of 23

Brocade 120.9.0 Release Notes v2.0 3 of 23

Release Contents Summary

Supported Client Operating Systems

Operating System Versions

Microsoft 2000 Server SP4 (x86 32-bit)

Sun Solaris 8, 9 and 10 (SPARC-platform)

Brocade 120.9.0 Release Notes v2.0 4 of 23

Linux RedHat AS 3.0 (x86 32-bit)

Note: Other virtualization software is not supported.

Brocade 120.9.0 Release Notes v2.0 5 of 23

Operating System Switch/Director

Switch Type Firmware Versions

FOS 3.2.1c Brocade 3800

FOS 4.4.x and 5.0.x Brocade 12000

FOS 4.4.x, 5.0.x, 5.1.x, 5.2.x, and 5.3.x Brocade 3900

Brocade 120.9.0 Release Notes v2.0 6 of 23

XPath 7.4.1e w/ SAS 2.1.3j AP7420

1 Requires FOS v5.1.0 or higher

Blade Type Firmware Versions

FOS v3.2.1c Brocade 3000

FOS 5.2.x, 5.3.x, 6.0.x and 6.1.x Brocade 3014

1 Requires FOS v5.3.1 or higher

Brocade 120.9.0 Release Notes v2.0 7 of 23

Recommended firmware versions to be used as “non-proxy”

Switches Model Maximum supported Version

Brocade 120.9.0 Release Notes v2.0 8 of 23

Scalability of the SMI Agent

Brocade SMI Agent Documentation

Brocade 120.9.0 Release Notes v2.0 9 of 23

• Meta SAN Fabric Identifier will be displayed in IdentifyingDescriptions and

• J WBEM Server 2.7.4 Integration

Brocade 120.9.0 Release Notes v2.0 10 of 23

Brocade 120.9.0 Release Notes v2.0 11 of 23

Brocade 120.9.0 Release Notes v2.0 12 of 23

a) Brocade_TopologyView gives wrong attached port WWN corresponding to

Brocade_TopologyView instances are not updated when NPIV Virtual WWN is

Brocade 120.9.0 Release Notes v2.0 13 of 23

To rediscover the fabric:

Brocade 120.9.0 Release Notes v2.0 14 of 23

Defect ID: DEFECT000230763 Technical Severity: High

Defect ID: DEFECT000228130 Technical Severity: Medium

Defect ID: DEFECT000237122 Technical Severity: Medium

Defect ID: DEFECT000238617 Technical Severity: Medium

Brocade 120.9.0 Release Notes v2.0 15 of 23

Defect ID: DEFECT000240050 Technical Severity: Medium

Defect ID: DEFECT000240380 Technical Severity: Medium

Defect ID: DEFECT000241574 Technical Severity: Medium

Defect ID: DEFECT000242046 Technical Severity: Medium

Brocade 120.9.0 Release Notes v2.0 16 of 23

Defect ID: DEFECT000244656 Technical Severity: Medium

Defect ID: DEFECT000244837 Technical Severity: Medium

Defect ID: DEFECT000246105 Technical Severity: Medium

Brocade 120.9.0 Release Notes v2.0 17 of 23

Defect ID: DEFECT000251684 Technical Severity: Medium

Defect ID: DEFECT000255781 Technical Severity: Medium

Brocade 120.9.0 Release Notes v2.0 18 of 23

Defect ID: DEFECT000243006 Technical Severity: High