(Supporting Network Advisor 12.3.0)
Table Of Contents
- Contents
- About This Document
- Overview of the Network Advisor REST API
- Getting Started
- Using the Brocade Network Advisor REST API
- Introduction
- Logging in and out
- Specifying content type
- Versioning (backward compatibility)
- Using the Topology API
- Using the SAN Fabric Discovery API
- Using the Traffic Flow API
- Using the Summary Data API
- Using the Events API
- Using the Zoning API
- Using the Historical Performance Data API
- Fibre Channel Routing
- Handling errors
- Use Cases
- API Reference
- Request and Response Schemas
- Topology
- SAN fabric discovery
- Summary data
- SummaryResponse
- StatusSummary
- AssetClassificationSummary
- NetworkObjectCountSummary
- EventsSummary
- BottleneckViolationsSummary
- OutOfRangeViolationsSummary
- PortHealthViolationsSummary
- VmViolationsSummary
- SummariesResponse
- PortsMonitorSummaryData
- MonitorDistributionData
- ProductsMonitorSummaryData
- FlowMonitorSummaryData
- Events
- Zoning
- Historical performance data
- Authentication and session management
Brocade Network Advisor REST API Guide 133
53-1003160-01
Zoning
5
• You can control whether to activate the zone set using the activate property (applicable for
Standard zoning only).
• LSAN zoning is supported only in the context of a backbone fabric.
• The Boolean properties in the input are case-sensitive. Only a value of “true” in the input
converts to a Boolean true. All else is Boolean false.
• Attach means engaging an initiator with targets by activating the zone. Attach is meaningful
when the activate flag is true. Using the activate flag as false is a convenience operation to
create the zone for later attach use. When activate is false, there is no actual attach but only
that of creation. Similarly, detach means disengaging an initiator from targets by deactivating
the zone. If nothing is active, then there is nothing to detach. If a zone containing the initiator
and targets exists, it will not be deleted, but will be retained in the defined configuration for
later use.
• The request schema is InitiatorTargetsRequest.