Using the custom action mechanism – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 49

Network OS NETCONF Operations Guide
17
53-1003231-02
Retrieving operational data
2
<vlan-name>vlan-20</vlan-name>
<vlan-state>active</valan-state>
<interface>
<interface-type>tengigabitethernet</interface-type>
<interfce-name>66/0/10</interface-name>
<tag>tagged</tag>
</interface>
</vlan>
<last-vlan-id>20</last-vlan-id>
<has-more>true</has-more>
</rpc-reply>
The <has-more> field is true, so use the value returned in <last-vlan-id> as the <last-rcvd-vlan-id>
in the next call to <get-vlan-brief> to return information about the next VLAN.
<rpc message-id="208" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-vlan-brief xmlns="urn:brocade.com:mgmt:brocade-interface-ext">
<last-rcvd-vlan-id>20</last-rcvd-vlan-id>
</get-vlan-brief>
</rpc>
<rpc-reply message-id="208" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<vlan xmlns="urn:brocade.com:mgmt:brocade-interface-ext">
<vlanid>30</vlanid>
<vlan-type>static</vlan-type>
<vlan-name>vlan-30</vlan-name>
<vlan-state>active</valan-state>
<interface>
<interface-type>tengigabitethernet</interface-type>
<interfce-name>66/0/12</interface-name>
<tag>tagged</tag>
</interface>
</vlan>
<last-vlan-id>30</last-vlan-id>
<has-more>false</has-more>
</rpc-reply>
If the <has-more> field returns false, no more VLAN data can be retrieved.
Using the custom action mechanism
An action is a proprietary mechanism used for implementing operations that do not affect the
configuration datastore. Several implementations of actions exist in the Network OS
implementation for retrieving operational information. The following structure is defined in the
brocade-zone.yang module for displaying operational data related to zoning.
+--rw common-def:show
+--rw brocade-zone:zoning
+--action brocade-zone:operation-info
+--input
+--output
+--ro brocade-zone:db-max
+--ro brocade-zone:db-avail
+--ro brocade-zone:db-committed
+--ro brocade-zone:db-transaction
+--ro brocade-zone:transaction-token
+--ro brocade-zone:last-zone-changed-timestamp
+--ro brocade-zone:last-zone-committed-timestamp
The following example shows use of the <zoning>/<operation-info> action.