(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 119
53-1003160-01
Zoning
5
Zoning
The Zoning API provides GET and POST requests for zone monitoring and administration.
When using this API, you must specify the HTTP request header “Accept” to indicate the content
type of the response payload. For POST requests, you must also specify the header “Content-type”
(for more information, refer to “Specifying content type”).
In addition to the Accept and Content-type headers, you must also specify the HTTP request
header “WSToken,” which contains the session token sent back in response to the login request
(for more information, refer to “Logging in and out”).
• “Zone DBs”
• “Zones”
• “Zone aliases”
• “Zone sets”
• “Zone transactions”
• “Zone transaction management”
• “Zoning object creation”
• “Zoning object deletion”
• “Zoning object updating”
• “Zone set activation”