switch will be stale and you will be unable to use the Brocade switch to perform provisioning or gather port performance statistics through the Brocade switch.

Any Brocade switches that are managed with the Brocade Fabric Access API provider will be quarantined after upgrading the management server. The management server retains the data for the API switches after upgrading, but you cannot do Discovery Data Collection until you migrate Brocade switches to the Brocade SMI Agent provider.

The latest build of the software requires you to upgrade some of your CIM Extensions. See ”About Upgrading Your CIM Extensions” on page 189.

You will need a new proxy server for Brocade. See the support matrix for requirements.

About Migrating Your Brocade Switches to SMI-A

After successfully upgrading the management server, any Brocade switches that use the Brocade Fabric Access API provider must be migrated to the Brocade SMI-A provider. The management server will prompt you to migrate your Brocade switches the first time you log on to the management server after the upgrade and will display the Brocade API switches that need to be migrated.

Until you migrate your Brocade switches to SMI-A, data such as topology and zoning from the Brocade switch will be stale and you will be unable to use the Brocade switch to perform provisioning or gather port performance statistics through the Brocade switch. The Brocade Fabric Access API switches are quarantined and you will have the option to migrate to the Brocade SMI-A provider at your discretion in case your SAN policy requires that you validate the new Brocade SMI Agent provider before migrating your Brocade switches.

The quarantined API-managed Brocade switches retain their historical data and that data remains intact during the migration to the SMI-A provider.

However, new data will not be collected for the quarantined Brocade switches until you migrate the switches to the SMI-A provider.

After migrating the Brocade switches to SMI-A, the Brocade SMI-A proxy server is placed in its own discovery group. This new discovery group is not part of any Discovery Data Collection schedule. If the Brocade switches were part of a Discovery Data Collection schedule prior to migration, you must manually adjust those schedules to run Discovery Data Collection for the migrated Brocade switches. If the schedules are not adjusted manually, Discovery Data Collection will not run for the migrated switches as per pre-migration schedules.

Follow these steps to migrate your Brocade switches to the Brocade SMI-A provider:

1.Download the Brocade SMI Agent v120.6.0a provider software and its Installation Guide from the Brocade website:

http://www.brocade.com/support/SMIAGENT.jsp

See the support matrix for your edition for details on the latest supported version for the management server.

2.Install the Brocade SMI Agent with a minimum version of 120.6.0a and configure the proxy servers on the server with which you will manage your Brocade access points following the

HP Storage Essentials SRM 6.0 Installation Guide 101