Brocade Network OS NETCONF Operations Guide v4.1.1 - Manual (Page 47)

Network OS NETCONF Operations Guide 15
53-1003231-02
Retrieving operational data
2
0
test
Retrieving operational data
In the Brocade Network OS implementation of NETCONF, two mechanisms are used for retrieving
operational data: Brocade custom RPCs and custom actions. Custom RPC and action support is
added to some of the YANG modules to support the return of specific operational data.
For a complete list of the Brocade custom RPCs and actions, and their locations, refer to the
Network OS YANG Reference Manual.
Brocade Network OS does not support retrieving operational data using the standard RPC.
Using custom RPCs
If an RPC is defined in a YANG module, you can use that RPC to return the associated namespace
information defined in its output elements. For example, to return information about port-profiles to
which interfaces are applied, you can use the RPC defined in the
brocade-port-profile-ext.yang file.
The brocade-port-profile-ext.yang file defines the structure of the RPC as
follows:
+---x get-port-profile-for-intf
+--ro input
+--ro interface-type? enumeration
+--ro interface-name? union
+--ro output
+--ro interface
+--ro interface-type? enumeration
+--ro interface-name? union
+--ro port-profile
+--ro name? common-def:name-string64
The following example shows the message and reply. The element
contains an xmlns attribute that identifies the corresponding namespace.
xmlns="urn:brocade.com:mgmt:brocade-interface-ext"/>
tengigabitethernet
9/0/53
auto-VM_Network