Download complete user manual (PDF). - Brocade

2
Retrieve operational Data
auto-for_iscsi
See the Network OS YANG Reference for a list of custom RPCs, a brief description of their function,
and their location.
Retrieve operational data with pagination
Some RPCs return operational data that consists of lists of entities. For example, an RPC might
return detailed information about every interface. For these kinds of applications, to make the
output manageable, pagination is supported by providing a element in the output of
the RPC.
The following example shows how the element works to provide pagination for the
RPC. In the input, you can request information about a specific VLAN, or about all
VLANs by not providing an input parameter. If you request input about all VLANs, you will first
receive information about the VLAN with the lowest VLAN ID. You can then check the
element in the output to determine whether information is available for additional VLANs. If
is true, use the value returned in as the input
parameter to the next call to . The RPC then returns the next
available VLAN. Continue until returns false.
+---x get-vlan-brief
+--ro input
| +--ro (request-type)?
| +--:(get-request)
| | +--ro vlan-id? interface:vlan-type
| +--:(get-next-request)
| +--ro last-rcvd-vlan-id? interface:vlan-type
+--ro output
+--ro vlan [vlan-id]
| +--ro vlan-id interface:vlan-type
| +--ro vlan-type? enumeration
| +--ro vlan-name? string
| +--ro vlan-state? enumeration
| +--ro interface [interface-type interface-name]
| +--ro interface-type enumeration
| +--ro interface-name union
| +--ro tag? enumeration
+--ro last-vlan-id? interface:vlan-type
+--ro has-more? boolean
The following example uses the RPC to return information about the first
VLAN. In this case, the first VLAN is VLAN 20.
rpc-reply message-id="207" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
20
static
vlan-20
active
16 Network OS NETCONF Operations Guide
53-1002565-01