Brocade Network Advisor SMI Agent Developers Guide v12.3.0 - Manual (Page 40)

24 Brocade Network Advisor SMI Agent Developer’s Guide
53-1003159-01
Fabric profile
3
Extrinsic methods
The Brocade_ZoneService class contains the following extrinsic methods of the zone control
subprofiles:
• CreateZoneSet
• CreateZone
• CreateZoneAlias
• CreateZoneMembershipSettingData
• AddZone
• AddZoneAlias
• AddZoneMembershipSettingData
• ActivateZoneSet
• SessionControl
• ActivateZoneSetWithJob
• SessionControlWithJob
The following method is Brocade extension:
• ClearZoneDB
Zoning operation behavior
The Brocade Network Advisor SMI Agent depends on Brocade Network Advisor to support zoning.
The Brocade Network Advisor SMI Agent supports pure Fabric Operating System (FOS), mixed
fabrics, as well as pure Enterprise Operating System (EOS) fabrics.
The following are the zoning operation behaviors:
• All the operations as shown in Figure 10 are supported.
• Starting a zoning transaction is done by invoking the SessionControl method. Only one CIM
client is allowed to do zoning on a particular fabric at a time from the same Brocade Network
Advisor SMI Agent. However, with the Brocade Network Advisor SMI Agent, the transaction lock
is only local and it is not open on the switch. The operation returns Success without actually
doing anything on the switch. The same applies to the abort operation.
• Even though SMI zoning operations appear atomic in nature, the changes are delivered to the
fabric as a whole. The changes made by a CIM client are not visible to any other client, not even
on Telnet until the transaction is committed successfully.
• The operations Activate (including with job), Deactivate (including with job), and ClearZoneDB
are supported only outside the scope of a zoning transaction. If a transaction is open, then the
changes must be done before activating, deactivating, or clearing the database.
• A user is identified by Brocade Network Advisor user name only, and so a zoning transaction
opened by user1 on host1 can be used by the same user1 on some other host if it is still open.
The IP address of the host does not configure as part of the user name.
• A commit operation is successful once the zoning changes are accepted by the seed switch.
The successful completion of a commit operation does not mean that all the changes have
been propagated to the entire fabric.