Table of Contents
Advertisement
•
•
•
•
•
•
•
•
•
•
•
Job control profile for SessionControlWithJob and
ActivateZoneSetWithJob
During a commit or activate operation, it is possible that the operation takes time to complete.
Internally, the ZoningServer posts the operation to the switch through Hypertext Transfer Protocol
(HTTP), which then keeps polling the result until it receives a success or failure. The time lag
between the post and poll result depends on the zone database size on a Fabric OS.
To prevent blocking of the CIMClient, two asynchronous methods have been provided in the
Brocade_ZoneService, namely SessionControlWithJob and ActivateZoneSetWithJob. The execution
of these methods returns a Brocade_ConcreteJob instance when the CIM client commit SAN Zone
changes through SANSessionControl extrinsic call. The Brocade_ConcreteJob and
Brocade_SANZoneService are associated by Brocade_SANZoneControlOwningJobElement and
Brocade_SANZoneControlAffectedElement classes.
Even though this subprofile is used, the Brocade Network Advisor SMI Agent will not be 100
percent compliant. For example, the extrinsic method GetError() is not supported. Therefore, this
subprofile is not advertised.
Brocade Network Advisor SMI Agent Developer's Guide
53-1002169-01
If a Brocade Network Advisor client first starts zoning on a fabric (opens a zoning dialog box for
that fabric) and then an SMI client starts a transaction on the same fabric, a notification is sent
to the Brocade Network Advisor client that another user is starting zoning operations. This is a
broadcast notification to all the Brocade Network Advisor clients that currently have the zoning
dialog box open to do zoning configuration on the same fabric. This behavior is the same as
between two Brocade Network Advisor clients.
If an SMI client starts a transaction on a fabric and a Brocade Network Advisor client opens a
zoning dialog box, a notification is issued, which need not be considered. The SMI client could
be in the middle of the session changes.
If the SMI client commits first, the Brocade Network Advisor client is notified that the zone
database has been changed. The Brocade Network Advisor client has the option of ignoring or
refreshing the zone database copy. This is a warning message and there is nothing preventing
the Brocade Network Advisor client from ignoring the warning. This behavior is the same as
between two Brocade Network Advisor clients.
If a Brocade Network Advisor client commits the changes first, the SMI client's zone
transaction is aborted and an indication is sent.
If the time for which an open transaction is idle or greater than Brocade_ZoneService.Timeout
(value in seconds), the SMI client's zone transaction is aborted and an indication is sent.
Error code 32770 is mapped to Transaction_Not_Started, which is different from the host
agent where it is No_Transaction.
Error code 32772 is mapped to Transaction_Already_Started, which is different from the host
agent where it is Transaction_Already_On.
Error code 32781 is a new error code mapping to Transaction_Not_Available. This will be
returned to a CIMClient on SessionControl in the event that the zoning transaction on that
fabric is already opened by some other CIMClient.
Error code 32775 mapped to Too Many Members no longer exists.
Indication is not delivered when the client intentionally aborts a transaction.
The fabric assist zoning feature is not supported and therefore the H{<WWN>} notation for a
fabric member is not supported in the SMI Agent.
3
Fabric profile
25
Advertisement
Table of Contents
