158
</filter>
</
getoperation
>
</rpc>
The <getoperation>
parameter can be <get> or <get-bulk>. The <filter> element is used to filter data,
and it can contain module name, submodule name, table name, and column name.
•
If the module name and the submodule name are not provided, the operation retrieves the data
for all modules and submodules. If a module name or a submodule name is provided, the
operation retrieves the data for the specified module or submodule.
•
If the table name is not provided, the operation retrieves the data for all tables. If a table name is
provided, the operation retrieves the data for the specified table.
•
If only the index column is provided, the operation retrieves the data for all columns. If the index
column and other columns are provided, the operation retrieves the data for the index column
and the specified columns.
The <get> and <get-bulk> messages are similar. A <get-bulk> message carries the
count
and
index
attributes. The following is a <get-bulk> message example:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id ="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:xc="http://www.hp.com/netconf/base:1.0">
<get-bulk>
<filter type="subtree">
<top xmlns="http://www.hp.com/netconf/data:1.0"
xmlns:base="http://www.hp.com/netconf/base:1.0">
<Syslog>
<Logs xc:count="5">
<Log>
<Index>10</Index>
</Log>
</Logs>
</Syslog>
</top>
</filter>
</get-bulk>
</rpc>
The
count
attribute complies with the following rules:
•
The
count
attribute can be placed in the module node and table node. In other nodes, it cannot
be resolved.
•
When the
count
attribute is placed in the module node, a descendant node inherits this
count
attribute if the descendant node does not contain the
count
attribute.
Verifying the configuration
After receiving the get-bulk request, the device returns a response in the following format if the
operation is successful:
<?xml version="1.0"?>
<rpc-reply message-id="100"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data>
Device state and configuration data
</data>
</rpc-reply>