To Next Page

To Previous Page

270

</top>

</filter>

</get>

</rpc>

• Table-based match

You can specify a match criterion for the row attribute filter to implement a table-based match,

for example, IP address filtering. For the table-based match to take effect, you must use this

filtering method before full match, regular expression match, and conditional match.

Table-based match applies only to multi-instance tables with namespace

http://www.hp.com/netconf/base:1.0. Support for the table-based match varies by table. For

more information, see NETCONF XML API documents.

# Copy the following text to the client to retrieve the longest data with VRF name vpn1, IP

address 1.1.1.0, and mask length 24 from the IPv4 routing table:

<rpc message-id="100" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"

xmlns:hp="http://www.hp.com/netconf/base:1.0">

<get>

<Route>

</Ipv4Routes>

</Route>

</top>

</filter>

</get>

</rpc>

Example for filtering data with regular expression match

Network requirements

Retrieve all data including colons in the Description column of the Interfaces table under the Ifmgr

module.

Configuration procedure

# Enter XML view.

<Sysname> xml

# Exchange capabilities.

urn:ietf:params:netconf:base:1.0

</capability>

</capabilities>

</hello>

# Retrieve all data including colons in the Description column of the Interfaces table under the Ifmgr

module.

<?xml version="1.0"?>

<rpc message-id="100"

HPE FlexNetwork 5510 HI Series Network Management And Monitoring Configuration Guide

Other manuals for HPE FlexNetwork 5510 HI Series