Use cases, Introduction, Zoning – Brocade Network Advisor REST API Guide (Supporting Network Advisor 12.3.0) User Manual
Page 51: Chapter 4

Brocade Network Advisor REST API Guide
37
53-1003160-01
Chapter
4
Use Cases
In this chapter
•
•
•
Getting Traffic Flow Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
•
Getting the Top N CRC errors port summary . . . . . . . . . . . . . . . . . . . . . . . . . 44
•
•
Introduction
This chapter discusses common use cases for the Network Advisor REST API.
Zoning
Zoning is the means by which administrators partition their SAN into logical groups of devices that
can access each other.
When zoning a SAN, it is best to implement 1-to-1 zoning, where each zone contains a single
initiator and a single target. Single-initiator zoning has the advantage of eliminating host-to-host
visibility, which results in less RSCN traffic.
You can use the REST API to carry out single-initiator to single- or multiple-target zoning using the
attach/detach URIs.
To attach a single initiator with one or more targets, perform the following steps.
1. Establish a REST session with Network Advisor (refer to
).
The network consisting of the initiator and targets is assumed to be discovered in Network
Advisor. If not, you can use the Network Advisor client or the Network Advisor REST API to
discover the fabrics of interest (refer to
2. Create the InitiatorTargetsRequest.xml file with the payload information consisting of the
initiator and target WWNs and other properties defined in the REST schema of the
InitiatorTargetsRequest request object (refer to the
).
NOTE
The InitiatorTargetsRequest REST schema is published in the directory
directory.