The display xpl route-filter command displays the configuration and reference information about XPL route-filters.
Parameter | Description | Value |
---|---|---|
attached |
Displays information about the route-filters that are referenced. |
- |
unattached |
Displays information about the route-filters that are not referenced. |
- |
name xpl-name |
Specifies the name of the route-filters. |
The value is a string of 1 to 200 case-sensitive characters, spaces not supported. The string can contain letters, digits, underscores (_), hyphens (-), and dots (.). It must start with a letter or digit. |
attachpoints |
Displays information about points of attachment. |
- |
uses |
Displays information about route-filters or sets that are referenced. |
- |
detail |
Displays detailed information about route-filters or sets that are referenced. |
- |
state |
Displays information about route-filter configurations and references. |
- |
Usage Scenario
To view information about XPL route-filter and route attribute set configurations and references, run the display xpl command. If a large amount of information is output, you can specify attached or unattached to filter the information. Route attribute set reference indicates that a route attribute set is referenced by a route-filter, and route-filter reference indicates that a route-filter is referenced by a routing protocol. To check the configuration and reference information about XPL route-filters, run the display xpl route-filter command.
The actual command output varies according to the device. The command output here is only an example.
<HUAWEI> display xpl route-filter name rtf1 detail
permit: 1, deny: 0
xpl route-filter rtf1
if ip route-destination in ipf1 then
apply tag 9
endif
if as-path in ap1 then
apply tag 10
endif
if community matches-any cl1 then
apply tag 11
endif
call route-filter rf2(40)
end-filter
#
xpl ip-prefix-list ipf1
2.2.2.2 32,
2.2.2.3 32
end-list
#
xpl as-path-list ap1
regular 8$
end-list
#
xpl community-list cl1
1,
2,
3
end-list
#
xpl route-filter rtf2($med1)
apply med $med1
end-filter
<HUAWEI> display xpl route-filter name rtf1 uses
route filter used:
----------------------------------------------------------
rtf2
ip-prefix list used:
------------------------------------
ipf1
as-path list used:
------------------------------------
ipf1
community list used:
------------------------------------
cl1
<HUAWEI> display xpl route-filter name r1 attachpoints
Service attachPoint ReferCnt BoundBy
bgp bgpPeerExport 1 r1
<HUAWEI> display xpl route-filter state
Attached: Applied by at least one attach point
Unattached: Not applied by any attach point
Attached
---------------------------------------------------------------
r1
Unattached
---------------------------------------------------------------
Item | Description |
---|---|
as-path list used | AS_Path sets that are referenced. |
community list used | Community sets that are referenced. |
route filter used | Route-filters that are referenced. |
ip-prefix list used | IPv4 prefix sets that are referenced. |
Service | Protocol that references the route-filter or route attribute set. |
attachPoint | Application of the route-filter in the protocol. |
ReferCnt | Number of times that the route-filter is referenced by the protocol. |
BoundBy | Name of the route-filter that is directly referenced by the protocol. |
Attached: Applied by at least one attach point | The route-filter is referenced at least once. |
Unattached: Not applied by any attach point | The route-filter or route attribute set is not referenced. |
Attached | Route-filter that is referenced. |
Unattached | Route-filter that is not referenced. |
permit | Number of routes permitted by the route-filter. The count is cumulative and increases every time a route is permitted by the route-filter. In some scenarios, verification scenario for example, duplicated counting may occur. The count is the sum of matching result of all services. If a service does not use the route-filter anymore, the count decreases. If the route-filter is reconfigured, recounting is performed. |
deny | Number of routes denied by the route-filter. The count is cumulative and increases every time a route is denied by the route-filter. In some scenarios, verification scenario for example, duplicated counting may occur. The count is the sum of matching result of all services. If a service does not use the route-filter anymore, the count decreases. If the route-filter is reconfigured, recounting is performed. |